Re: Netconfig Fail

Re: Netconfig Fail

[Peter]

Hi,

Slackware 10.1 kernel 2.4.29

My onboard LAN card on the mobo failed and I had to switch to an external LAN card.

I disabled in BIOS Ethernet onboard. Then I did netconfig. Slackware found the LAN card I entered all necessary data and the configuration went w/o any errors.
Unfortunately no I cannot connect any longer to the Internet in Slackware yet still in edora4 and DSL.

As requested by Ray
Here are the ouputs of ifconfig -a, lsmod and dmesg of the 3 different distros:

slackware ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:640 (640.0 b)  TX bytes:2360 (2.3 Kb)
          Interrupt:10 Base address:0xec00 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:784 (784.0 b)  TX bytes:784 (784.0 b)

Fedora4 ifconfig -a
eth1      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
          inet addr:192.169.232.15  Bcast:192.169.255.255  Mask:255.255.224.0
          inet6 addr: fe80::208:a1ff:fe8c:445a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:118 errors:0 dropped:0 overruns:0 frame:0
          TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:17362 (16.9 KiB)  TX bytes:8160 (7.9 KiB)
          Interrupt:10 Base address:0xec00 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1168 (1.1 KiB)  TX bytes:1168 (1.1 KiB)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

DSL ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
          inet addr:192.169.232.15  Bcast:192.169.255.255  Mask:255.255.224.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:53021 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37952 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:71131414 (67.8 MiB)  TX bytes:2597337 (2.4 MiB)
          Interrupt:10 Base address:0xec00 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:100 (100.0 B)  TX bytes:100 (100.0 B)

In the following lsmod I cut out the snd- bits since they are very long.

Slackware lsmod

Module                  Size  Used by    Not tainted
dazuko                 28372   0 (unused)
gameport                1420   0 [snd-via82xx]
lp                      6404   0 (autoclean)
parport                22824   1 (autoclean) [parport_pc lp]
pcmcia_core            39172   0
ide-scsi                9392   0
tulip                  39200   0
crc32                   2880   0 [tulip]
agpgart                45092   0 (unused)

Fedora lsmod

Module                  Size  Used by
md5                     4033  1 
ipv6                  268097  10 
parport_pc             28933  1 
lp                     13001  0 
parport                40585  2 parport_pc,lp
autofs4                29253  2 
sunrpc                167813  1 
ipt_REJECT              5569  1 
ipt_state               1857  7 
ip_conntrack           41497  1 ipt_state
iptable_filter          2881  1 
ip_tables              19521  3 ipt_REJECT,ipt_state,iptable_filter
ide_scsi               18761  0 
scsi_mod              148105  1 ide_scsi
dm_mod                 58101  0 
video                  15941  0 
button                  6609  0 
battery                 9413  0 
ac                      4805  0 
uhci_hcd               35152  0 
ehci_hcd               41037  0 
shpchp                 94405  0 
i2c_viapro              8017  0 
i2c_core               21569  1 i2c_viapro
dmfe                   23525  0 
floppy                 65269  0 
ext3                  132553  4 
jbd                    86233  1 ext3

DSL lsmod

Module                  Size  Used by    Not tainted
mousedev                3832   0 (unused)
hid                    22372   0 (unused)
input                   3168   0 [mousedev hid]
af_packet              13544   0 (autoclean) 
reiserfs              169616   1 (autoclean) 
ext3                   64452   2 (autoclean) 
jbd                    46516   2 (autoclean)  [ext3]
nls_iso8859-1           2844   0 (autoclean) 
nls_cp437               4348   0 (autoclean) 
agpgart                42660   0 (unused)
via82cxxx_audio        19448   1
ac97_codec             11916   0 [via82cxxx_audio]
uart401                 6052   0 [via82cxxx_audio]
sound                  55276   0 [via82cxxx_audio uart401]
soundcore               3428   4 [via82cxxx_audio sound]
dmfe                   11905   1
crc32                   2816   0 [dmfe]
serial                 52100   0 (autoclean) 
pcmcia_core            39840   0
rtc                     7036   0 (autoclean) 
cloop                   8740   2
ieee1394              183076   0
usb-storage            61696   0 (unused)
usb-uhci               21644   0 (unused)
usbcore                57600   1 [hid usb-storage usb-uhci]
ataraid                 6180   0
ide-cd                 28512   0
ide-scsi                8816   1

dmesg the part of showing the ethernet card:

Slackware dmesg

Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 409M
agpgart: Detected Via Apollo P4M266 chipset
agpgart: AGP aperture is 64M @ 0xe0000000
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
tulip0:  MII transceiver #1 config 3100 status 7829 advertising 01e1.
eth0: Davicom DM9102/DM9102A rev 64 at 0xec00, 00:08:A1:8C:44:5A, IRQ 10.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices

Fedora4 dmesg

FDC 0 is a post-1991 82077
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] -> GSI 10 (level, low) ->
IRQ 10
eth0: Davicom DM9102 at pci0000:00:0b.0, 00:08:a1:8c:44:5a, irq 10.
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 5 (level, low) ->
IRQ
5
PCI: Setting latency timer of device 0000:00:11.5 to 64
shpchp: shpc_init : shpc_cap_offset == 0
---snip---
eth1: no IPv6 routers present

DSL dmesg

ttyS01 at 0x02f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
eth0: Davicom DM9102 at pci00:0b.0, 00:08:a1:8c:44:5a, irq 10.

That's all for now

Regards

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Ray Olszewski]

Peter -- The new NIC is not a standard tulip NIC. It is a Davicom NIC 
(see Slack's dmesg output) and needs the dmfe module, not the tulip 
module. (Yes, I know Slackware *thinks* it needs the tulip module; 
Slackware is wrong. Or perhaps you are, if you added it by hand.)

Both Fedora and DSL get it right. Look in the lsmod output from the 2 
distros that work and you will see that dmfe is present but not tulip. 
Also review the dmesg output you sent us.

Finally ... Peter, once you sent all this stuff, it took me less than a 
minute to spot the problem. I mention this because so often I ask (you 
and others) for a complete problem description, not a fragmentary one. 
It can make a real difference in ease and speed of troubleshooting.

Peter wrote:
> Hi,
> 
> Slackware 10.1 kernel 2.4.29
> 
> My onboard LAN card on the mobo failed and I had to switch to an external LAN card.
> 
> I disabled in BIOS Ethernet onboard. Then I did netconfig. Slackware found the LAN card I entered all necessary data and the configuration went w/o any errors.
> Unfortunately no I cannot connect any longer to the Internet in Slackware yet still in edora4 and DSL.
> 
> As requested by Ray
> Here are the ouputs of ifconfig -a, lsmod and dmesg of the 3 different distros:
> 
> slackware ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:640 (640.0 b)  TX bytes:2360 (2.3 Kb)
>           Interrupt:10 Base address:0xec00 
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:784 (784.0 b)  TX bytes:784 (784.0 b)
> 
> Fedora4 ifconfig -a
> eth1      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
>           inet addr:192.169.232.15  Bcast:192.169.255.255  Mask:255.255.224.0
>           inet6 addr: fe80::208:a1ff:fe8c:445a/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:118 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:17362 (16.9 KiB)  TX bytes:8160 (7.9 KiB)
>           Interrupt:10 Base address:0xec00 
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:16 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:1168 (1.1 KiB)  TX bytes:1168 (1.1 KiB)
> 
> sit0      Link encap:IPv6-in-IPv4  
>           NOARP  MTU:1480  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> 
> DSL ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
>           inet addr:192.169.232.15  Bcast:192.169.255.255  Mask:255.255.224.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:53021 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:37952 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:71131414 (67.8 MiB)  TX bytes:2597337 (2.4 MiB)
>           Interrupt:10 Base address:0xec00 
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:2 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:100 (100.0 B)  TX bytes:100 (100.0 B)
> 
> In the following lsmod I cut out the snd- bits since they are very long.
> 
> Slackware lsmod
> 
> Module                  Size  Used by    Not tainted
> dazuko                 28372   0 (unused)
> gameport                1420   0 [snd-via82xx]
> lp                      6404   0 (autoclean)
> parport                22824   1 (autoclean) [parport_pc lp]
> pcmcia_core            39172   0
> ide-scsi                9392   0
> tulip                  39200   0
> crc32                   2880   0 [tulip]
> agpgart                45092   0 (unused)
> 
> Fedora lsmod
> 
> Module                  Size  Used by
> md5                     4033  1 
> ipv6                  268097  10 
> parport_pc             28933  1 
> lp                     13001  0 
> parport                40585  2 parport_pc,lp
> autofs4                29253  2 
> sunrpc                167813  1 
> ipt_REJECT              5569  1 
> ipt_state               1857  7 
> ip_conntrack           41497  1 ipt_state
> iptable_filter          2881  1 
> ip_tables              19521  3 ipt_REJECT,ipt_state,iptable_filter
> ide_scsi               18761  0 
> scsi_mod              148105  1 ide_scsi
> dm_mod                 58101  0 
> video                  15941  0 
> button                  6609  0 
> battery                 9413  0 
> ac                      4805  0 
> uhci_hcd               35152  0 
> ehci_hcd               41037  0 
> shpchp                 94405  0 
> i2c_viapro              8017  0 
> i2c_core               21569  1 i2c_viapro
> dmfe                   23525  0 
> floppy                 65269  0 
> ext3                  132553  4 
> jbd                    86233  1 ext3
> 
> DSL lsmod
> 
> Module                  Size  Used by    Not tainted
> mousedev                3832   0 (unused)
> hid                    22372   0 (unused)
> input                   3168   0 [mousedev hid]
> af_packet              13544   0 (autoclean) 
> reiserfs              169616   1 (autoclean) 
> ext3                   64452   2 (autoclean) 
> jbd                    46516   2 (autoclean)  [ext3]
> nls_iso8859-1           2844   0 (autoclean) 
> nls_cp437               4348   0 (autoclean) 
> agpgart                42660   0 (unused)
> via82cxxx_audio        19448   1
> ac97_codec             11916   0 [via82cxxx_audio]
> uart401                 6052   0 [via82cxxx_audio]
> sound                  55276   0 [via82cxxx_audio uart401]
> soundcore               3428   4 [via82cxxx_audio sound]
> dmfe                   11905   1
> crc32                   2816   0 [dmfe]
> serial                 52100   0 (autoclean) 
> pcmcia_core            39840   0
> rtc                     7036   0 (autoclean) 
> cloop                   8740   2
> ieee1394              183076   0
> usb-storage            61696   0 (unused)
> usb-uhci               21644   0 (unused)
> usbcore                57600   1 [hid usb-storage usb-uhci]
> ataraid                 6180   0
> ide-cd                 28512   0
> ide-scsi                8816   1
> 
> dmesg the part of showing the ethernet card:
> 
> Slackware dmesg
> 
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 409M
> agpgart: Detected Via Apollo P4M266 chipset
> agpgart: AGP aperture is 64M @ 0xe0000000
> Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
> tulip0:  MII transceiver #1 config 3100 status 7829 advertising 01e1.
> eth0: Davicom DM9102/DM9102A rev 64 at 0xec00, 00:08:A1:8C:44:5A, IRQ 10.
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> 
> Fedora4 dmesg
> 
> FDC 0 is a post-1991 82077
> dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
> PCI: setting IRQ 10 as level-triggered
> ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] -> GSI 10 (level, low) ->
> IRQ 10
> eth0: Davicom DM9102 at pci0000:00:0b.0, 00:08:a1:8c:44:5a, irq 10.
> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
> PCI: setting IRQ 5 as level-triggered
> ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 5 (level, low) ->
> IRQ
> 5
> PCI: Setting latency timer of device 0000:00:11.5 to 64
> shpchp: shpc_init : shpc_cap_offset == 0
> ---snip---
> eth1: no IPv6 routers present
> 
> DSL dmesg
> 
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
> dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
> eth0: Davicom DM9102 at pci00:0b.0, 00:08:a1:8c:44:5a, irq 10.
> 
> That's all for now
> 
> Regards
> 
> Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

On Sat, 08 Oct 2005 09:01:23 -0700
Ray Olszewski <ray@comarre.com> wrote:

> Peter -- The new NIC is not a standard tulip NIC. It is a Davicom NIC 
> (see Slack's dmesg output) and needs the dmfe module, not the tulip 
> module. (Yes, I know Slackware *thinks* it needs the tulip module; 
> Slackware is wrong. Or perhaps you are, if you added it by hand.)

No slackware added it.

> Both Fedora and DSL get it right. Look in the lsmod output from the 2 
> distros that work and you will see that dmfe is present but not tulip. 
> Also review the dmesg output you sent us.
> 
> Finally ... Peter, once you sent all this stuff, it took me less than a 
> minute to spot the problem. I mention this because so often I ask (you 
> and others) for a complete problem description, not a fragmentary one. 
> It can make a real difference in ease and speed of troubleshooting.
> 
It seems it needs always someone like you to help to put on the right shoes.

Yes, I saw it myself as well when I had all the sent outputs that I need the dmfe module. When I tried to install it I got an error message. Did not catch it. Have to go over to slackware gain and will let you know.

Thanks & regards
-- 
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

Hi,

happy to report I am connected again in slackware.

When I woke-up from my Sunday afternoon nap I had the great idea of removing 
the module tulip and then inserting the module dmfe. It worked like a charm.

This is my first mail out again in slack.

Thanks again for all the help. I always seem to need someone to lift me on the 
chair.

Regards
-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

Hi,

In slackware when I try to "/sbin/modprobe dmfe" I get the following error:

Quote
/lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: init_module: No such
device
/lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: Hint: insmod errors can be
caused by incorrect module parameters, including invalid IO or IRQ
parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: insmod
/lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz failed
/lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: insmod dmfe failed
Unquote

Locate dmfe shows that the module is present. I confirmed it in mc. There is no info in dmesg or syslog.

As for init_module there is only a man page in slackware as in Fedora which I do not understand.

# locate dmfe
/lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz
/usr/src/linux-2.4.29/drivers/net/.dmfe.o.flags
/usr/src/linux-2.4.29/drivers/net/dmfe.c
/usr/src/linux-2.4.29/drivers/net/dmfe.o
/usr/src/linux-2.4.29/Documentation/networking/dmfe.txt

How to resolve? Short of looking for an ethernet card slackware can read correctly.

Regards

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[chuck gelm]

Peter wrote:
> Hi,
> 
> In slackware when I try to "/sbin/modprobe dmfe" I get the following error:
> 
> Quote
> /lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: init_module: No such
> device
> /lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: Hint: insmod errors can be
> caused by incorrect module parameters, including invalid IO or IRQ
> parameters.
>       You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: insmod
> /lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz failed
> /lib/modules/2.4.29/kernel/drivers/net/dmfe.o.gz: insmod dmfe failed
> Unquote

  Hi, Peter:

  Yep, it said 'no such device' not 'no such module', so your kernel
doesn't find the device.  Review:
http://www.linuxquestions.org/questions/history/113041
"... try another slack kernel like bareacpi.i or similar
  (especially on a laptop)..."

  You could contact the dmfe module author
(/usr/src/linux/Documentation/networking/dmfe.txt)
or report a 'bug' to Slackware.

HTH, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

Hi,

happy to report I am connected again in slackware.

When I woke-up from my Sunday afternoon nap I had the great idea of removing 
the module tulip and then inserting the module dmfe. It worked like a charm.

This is my first mail out again in slack.

Thanks again for all the help. I always seem to need someone to lift me on the
 chair.

Regards
-- 

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Netconfig Fail

[Peter]

Hi,

Slackware 10.1 kernel 2.4.29

My onboard LAN card on the mobo failed and I had to switch to an external LAN card.

I disabled in BIOS Ethernet onboard. Then I did netconfig. Slackware found the LAN card I entered all necessary data and the configuration went w/o any errors.

However, I cannot connect to the Internet. On booting after the MAC address was found it should produce the the IP address which it does not. It just sits for a while then continues booting. The same happens when I do /etc/rc.d/rc.inet1.

Ifconfig naturally shows no connection just the loop-back.

Where is the hitch?

I had no problem in Fedora4 to configure the new Lan card and in the gem Damned Small Linux distro, where I am now, the new LAN card was found w/o me doing anything.

Help for slackware appreciated.

Thanks & regards

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Ray Olszewski]

Peter wrote:
> Hi,
> 
> Slackware 10.1 kernel 2.4.29
> 
> My onboard LAN card on the mobo failed and I had to switch to an external LAN card.
> 
> I disabled in BIOS Ethernet onboard. Then I did netconfig. Slackware found the LAN card I entered all necessary data and the configuration went w/o any errors.

Just to be clear ... the relevant kernel module does identify the card 
and create the eth0 interface. Right? (One way to check: use "ifconfig 
-a", which  will list *all* interfaces, while "ifconfig" by itself only 
lists *configured* interfaces.)

At this point, I'm still uncertain as to whether the kernel module is 
failing to find the NIC, or the NIC is failing to get an IP address.

> However, I cannot connect to the Internet. On booting after the MAC address was found it should produce the the IP address which it does not. It just sits for a while then continues booting. The same happens when I do /etc/rc.d/rc.inet1.

"produce"? Do you mean you get an IP address via DHCP? Via PPPoE? (These 
days, home broadband connections rarely come with static IP addresses, 
so I surmise you don't have one of those rarities.)

In any case, troubleshooting is easier if we know how it is *supposed* 
to work.

> Ifconfig naturally shows no connection just the loop-back.

See above.

> Where is the hitch?

Round up the usual suspects ...

What kernel module is involved?

What happens if you modprobe it from the command line?

Does lsmod show it as loaded?

What happens if you "ifup eth0" from the command line?

> I had no problem in Fedora4 to configure the new Lan card and in the gem Damned Small Linux distro, where I am now, the new LAN card was found w/o me doing anything.

This is all good, since it means that the card should work, and we just 
need to spot the detail where you have (or Slackware has) something 
wrong. It also should eliminate the possibility of MAC-address 
authentication causing a problem.

Is there any possibility of a mechanical problem (a bad cable, say)? 
That is, aside from the distro change, was *everything* else *exactly* 
the same in your Slackware failure as in your Fedora and DSL successes? 
I'm assuming that you ran both other distros on the same system (same 
mobo), not with (say) the same NIC in a different mobo ... but please 
correct me if I've assumed too much here.

What are the details behind your writing above that "I entered all 
necessary data"? Since (apparently) you did not have to enter anything 
in the DSL test, and maybe not in the Fedora test either, this would at 
least appear to be a possible source of differences.

> Help for slackware appreciated.
> 
> Thanks & regards
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

On Thu, 06 Oct 2005 00:33:04 -0700
Ray Olszewski <ray@comarre.com> wrote:

> Peter wrote:
> > Hi,
> > 
> > Slackware 10.1 kernel 2.4.29
> > 
> > My onboard LAN card on the mobo failed and I had to switch to an external
LAN card.
> > 
> > I disabled in BIOS Ethernet onboard. Then I did netconfig. Slackware found
the LAN card I entered all necessary data and the configuration went w/o any
errors.
> 
> Just to be clear ... the relevant kernel module does identify the card 
> and create the eth0 interface. Right? (One way to check: use "ifconfig 
> -a", which  will list *all* interfaces, while "ifconfig" by itself only 
> lists *configured* interfaces.)
> 
This is in slackware
 /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1896 (1.8 Kb)  TX bytes:4720 (4.6 Kb)
          Interrupt:10 Base address:0xec00 

w/o the -a flag above will not show

and in fedora4 w/o -a flag. Note the second line missing in slack.

eth1      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
          inet addr:192.169.232.15  Bcast:192.169.255.255  Mask:255.255.224.0
          inet6 addr: fe80::208:a1ff:fe8c:445a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:145 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:26493 (25.8 KiB)  TX bytes:11880 (11.6 KiB)
          Interrupt:10 Base address:0xec00


> At this point, I'm still uncertain as to whether the kernel module is 
> failing to find the NIC, or the NIC is failing to get an IP address.
> 
> > However, I cannot connect to the Internet. On booting after the MAC
address was found it should produce the the IP address which it does not. It
just sits for a while then continues booting. The same happens when I do
/etc/rc.d/rc.inet1.
> 
> "produce"? Do you mean you get an IP address via DHCP? Via PPPoE? (These 
> days, home broadband connections rarely come with static IP addresses, 
> so I surmise you don't have one of those rarities.)

Well on booting /etc/rc.d/rc.inet1 gives this output:
dhcpcd: MAC address = 00:08:a1:8c:44:5a
after which it then would show the IPaddress, now it just sits for a while.

In /var/log/debug I found:

 broadcasting DHCP_REQUEST for 192.169.231.250 
Oct  7 07:58:11 Peter dhcpcd[2293]: timed out waiting for DHCP_ACK response 
Oct  7 07:58:11 Peter dhcpcd[2293]: broadcasting DHCP_DISCOVER

whereas when I still could connect with onboard LAN card:

 DHCP_ACK received from  (192.169.224.1) 
Oct  2 12:17:51 localhost dhcpcd[104]: sending DHCP_REQUEST for 192.169.232.12
to 192.169.224.1 
> 
> 
> > Where is the hitch?
> 
> Round up the usual suspects ...
> 
> What kernel module is involved?
> 
> What happens if you modprobe it from the command line?
> 
> Does lsmod show it as loaded?

The LAN card is Davicom Semiconducter Inc, DEC Tulip,
and lsmod shows that those modules for the card are loaded:

/sbin/lsmod
tulip                  39200   0
crc32                  2880   0 [tulip]

> 
> What happens if you "ifup eth0" from the command line?

No such program in slackware.
> 
> > I had no problem in Fedora4 to configure the new Lan card and in the gem
> > Damned Small Linux distro, where I am now, the new LAN card was found w/o me
> > doing anything.
> 
> This is all good, since it means that the card should work, and we just 
> need to spot the detail where you have (or Slackware has) something 
> wrong. It also should eliminate the possibility of MAC-address 
> authentication causing a problem.
> 
> Is there any possibility of a mechanical problem (a bad cable, say)? 
> That is, aside from the distro change, was *everything* else *exactly* 
> the same in your Slackware failure as in your Fedora and DSL successes? 
> I'm assuming that you ran both other distros on the same system (same 
> mobo), not with (say) the same NIC in a different mobo ... but please 
> correct me if I've assumed too much here.

Yes Slackware, Fedora and DSL all run on the same machine, same mobo, same LAN card, same cables, same et all. DSL is on a second HD.

> What are the details behind your writing above that "I entered all 
> necessary data"? Since (apparently) you did not have to enter anything 
> in the DSL test, and maybe not in the Fedora test either, this would at 
> least appear to be a possible source of differences.

Yes neither in Fedora nor in DSL had I to enter anything. In Fedora I just
had to activate eth1, eth0 was taken by the onboard LAN card.

In slackware one runs the program netconfig where one first has to enter a
host name, I always enter Peter,  then the domain name in this case
meridiantelekoms.com then one is asked to use a DHCP server to configure
ethernet, press enter for yes and the configuration is finished or used to be
when the onboard LAN card was still working.

This is in the rc.inet1.conf after running netconfig for the new LAN card. 

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

This has not changed from when onboard LAN card was working. All the other eth(1-3) show only ="" for all entries.

Chuck said
> Try '/etc/rc.d/rc.inet1 stop && /etc/rc.d/rc.inet1'.
>  e.g. 'stop' before you 'start'.

I tried it a few times first thing.

 cat /etc/resolv.conf
search meridiantelekoms.com
nameserver 203.87.128.3
nameserver 203.84.191.216
nameserver 203.87.128.4

both in Fedora and DSL. In slackware naturally only 'search meridiantelekoms.com' shows since there is no connection.

> > 
> > Thanks & regards

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Ray Olszewski]

OK, Peter. Thanks for the added detail. I see one interesting thing.

Peter wrote:
[...]
>  broadcasting DHCP_REQUEST for 192.169.231.250 
> Oct  7 07:58:11 Peter dhcpcd[2293]: timed out waiting for DHCP_ACK response 
> Oct  7 07:58:11 Peter dhcpcd[2293]: broadcasting DHCP_DISCOVER
> 
> whereas when I still could connect with onboard LAN card:
> 
>  DHCP_ACK received from  (192.169.224.1) 
> Oct  2 12:17:51 localhost dhcpcd[104]: sending DHCP_REQUEST for 192.169.232.12
> to 192.169.224.1 

In the first entry, Slackware's dhcpcd is asking any DHCP server to 
assign to it IP address 192.169.231.250. In principle this is OK; 
normally, it would mean that the system has previously received this 
address assignment and wants to get the same address again. (My LAN 
machines, the ones on DHCP that is, do this same thing when they renew 
addresses.) When it gets no response, it then asks (the DHCP_DISCOVER) 
for any DHCP server to respond as available to give *any* addresses. You 
don't quote what happens next, but I'm guessing it's another "timed out 
waiting" message ... maybe several, since DHCP clients are normally very 
persistent in looking for servers.

But the second (on-mobo NIC) part of the report identifies a *different* 
DHCP server as the one it is getting an acknowledgment from. (Am I 
correct in assuming this is also from a Slackware log, BTW?)

To figure out what is going on, you want to look at other stuff that is 
near these messages but that you didn't quote to us in your reply.

In the on-mobo-NIC case, look before what you sent us to see if the DHCP 
  client there is sending DHCP_REQUEST to 192.169.224.1 or if the 
DHCP_ACK here is a response to a DHCP_DISCOVER.

In the PCI-NIC case, first check the timestamp you left off the first 
(DHCP_REQUEST) message to see if it is far enough before 07:58:11 to 
observe the time lag you see. Then see if anything is logged in response 
to the DHCP_DISCOVER message that dhcpcd sends out.

Then check for corresponding log entries in the Fedora and DSL runs, to 
see how they are actually finding their DHCP servers.

Then, using some version of your setup that gets an IP address, find out 
if the DHCP server Slackware wants to use is ping'able.

The core of your problem is that in the Slackware case, you don't get a 
response to a DHCP_DISCOVER message ... which would be a DHCP server 
identifying itself to you as a source of address assignments.

Why this happens depends in part on what you find when you check the 
things I mention above.

One other thing. You wrote:

> nd in fedora4 w/o -a flag. Note the second line missing in slack.
> 
> eth1      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
>           inet addr:192.169.232.15  Bcast:192.169.255.255  Mask:255.255.224.0
>           inet6 addr: fe80::208:a1ff:fe8c:445a/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:145 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:26493 (25.8 KiB)  TX bytes:11880 (11.6 KiB)
>           Interrupt:10 Base address:0xec00

What is interesting to me is not that the second line is present (it is 
what I would expect, the difference between a configured and an 
unconfigured interface), but that Fedora thinks your pci NIC is eth1, 
not eth0. Does that version have an eth0 (it must; use the -a flag to 
find out about it)? What is it? Can we see its ifconfig -a report?

I really don't know what this difference means, but it does make me 
doubt whether the two cases (Fedora and Slack) are really the same in 
*all* respects other than the choice of distro.

Oh yes, last thing. In Slackware, you report:

> This is in slackware
>  /sbin/ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:08:A1:8C:44:5A  
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:12 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:1896 (1.8 Kb)  TX bytes:4720 (4.6 Kb)
>           Interrupt:10 Base address:0xec00 

Note there are RX packets and bytes, so the system is receiving 
something, on a guess some response to its broadcast packets. In the 
worst case, run a sniffer (ethereal, tcpdump) on the system while trying 
to get a DHCP assignment.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[chuck gelm]

Hi, Peter & Ray:

  Peter, if you add this line to /etc/rc.d/syslog.conf,

local0.*     /var/log/dhcpcd.log

  then when you 'dhcpcd -d eth[01] it will put debug lines
  into /var/log/dhcpcd.log  (See 'man dhcpcd')

> Yes neither in Fedora nor in DSL had I to enter anything. In Fedora I just
> had to activate eth1, eth0 was taken by the onboard LAN card.

  It seems to me that Fedora is finding your add-on PCI card and
assigning it eth0, yet Slackware is assigning it eth1 !?

  I expected, since you disabled the on-board ether device,
all distributions would only find a 'eth0'.

  So, if Slackware assigns it 'eth1' and your rc.inet1.conf assigns
DHCP to eth0, it will not work.

  Run dhcpcd from a console. If Slackware sees your PCI NIC as eth1;
dhcpcd eth1

  If that works, you can either edit rc.inet1.conf or add
'dhcpcd eth1' to rc.local.

HTH, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Ray Olszewski]

chuck gelm wrote:
[...]
>> Yes neither in Fedora nor in DSL had I to enter anything. In Fedora I 
>> just
>> had to activate eth1, eth0 was taken by the onboard LAN card.
> 
> 
>  It seems to me that Fedora is finding your add-on PCI card and
> assigning it eth0, yet Slackware is assigning it eth1 !?
> 
>  I expected, since you disabled the on-board ether device,
> all distributions would only find a 'eth0'.
> 
>  So, if Slackware assigns it 'eth1' and your rc.inet1.conf assigns
> DHCP to eth0, it will not work.
> 
>  Run dhcpcd from a console. If Slackware sees your PCI NIC as eth1;
> dhcpcd eth1
> 
>  If that works, you can either edit rc.inet1.conf or add
> 'dhcpcd eth1' to rc.local.
> 

Chuck -- I think you read Peter's message backwards. The ifconfig output 
he posted said (as I read it) that *Slackware* assigned the NIC to eth0, 
while *Fedora* assigned it to eth1. Not the other way aound. (I'm 
assuming, of course, that Peter is able to distinguish the 2 NICs 
correctly, presumably by having noted their MAC addresses.)

So the main thing that this means is that Peter is being inexact when he 
says yes to my question: Was everything else the same (across the 3 
tests)? I note now, in what you posted (and I requote above), that Peter 
says he did NOT disable (in the BIOS) the on-mobo NIC for the Fedora test.

As usual with these problems, the devil is in the details, and as is too 
often the case, we have here the added problem of needing to get the 
details reported correctly before we can do useful troubleshooting.

At this stage, I'd suggest that Peter repost his trouble report from the 
beginning, this time putting in all the relevant details (e.g., 
complete, unedited "ifconfig -a" output from all 3 tests; complete, 
unedited "lsmod" results from all 3 tests; complete "dmesg" output 
regarding NIC detection from all 3 tests; and complete dhcpcd, or 
whatever DHCP client the others use, logging from all 3 tests) ... and 
this time doing all 3 tests with the on-mobo NIC disabled in BIOS and 
EVERYTHING ELSE, except choice of distro, the same across all 3 tests.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

On Fri, 07 Oct 2005 10:23:24 -0700
Ray Olszewski <ray@comarre.com> wrote:

> chuck gelm wrote:
> [...]
> >> Yes neither in Fedora nor in DSL had I to enter anything. In Fedora I 
> >> just
> >> had to activate eth1, eth0 was taken by the onboard LAN card.
> > 
> > 
> >  It seems to me that Fedora is finding your add-on PCI card and
> > assigning it eth0, yet Slackware is assigning it eth1 !?
> > 
> >  I expected, since you disabled the on-board ether device,
> > all distributions would only find a 'eth0'.
> > 
> >  So, if Slackware assigns it 'eth1' and your rc.inet1.conf assigns
> > DHCP to eth0, it will not work.
> > 
> >  Run dhcpcd from a console. If Slackware sees your PCI NIC as eth1;
> > dhcpcd eth1
> > 
> >  If that works, you can either edit rc.inet1.conf or add
> > 'dhcpcd eth1' to rc.local.
> > 
> 
> Chuck -- I think you read Peter's message backwards. The ifconfig output 
> he posted said (as I read it) that *Slackware* assigned the NIC to eth0, 
> while *Fedora* assigned it to eth1. Not the other way aound. (I'm 
> assuming, of course, that Peter is able to distinguish the 2 NICs 
> correctly, presumably by having noted their MAC addresses.)
> 
> So the main thing that this means is that Peter is being inexact when he 
> says yes to my question: Was everything else the same (across the 3 
> tests)? I note now, in what you posted (and I requote above), that Peter 
> says he did NOT disable (in the BIOS) the on-mobo NIC for the Fedora test.

> As usual with these problems, the devil is in the details, and as is too 
> often the case, we have here the added problem of needing to get the 
> details reported correctly before we can do useful troubleshooting.
> 
> At this stage, I'd suggest that Peter repost his trouble report from the 
> beginning, this time putting in all the relevant details (e.g., 
> complete, unedited "ifconfig -a" output from all 3 tests; complete, 
> unedited "lsmod" results from all 3 tests; complete "dmesg" output 
> regarding NIC detection from all 3 tests; and complete dhcpcd, or 
> whatever DHCP client the others use, logging from all 3 tests) ... and 
> this time doing all 3 tests with the on-mobo NIC disabled in BIOS and 
> EVERYTHING ELSE, except choice of distro, the same across all 3 tests.
> 

OK I will try to get it all together. Jumping from distro to distro hoping staying online which I was not this morning for 4 hours.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

On Fri, 07 Oct 2005 07:20:53 -0400
chuck gelm <chuck@gelm.net> wrote:

> Hi, Peter & Ray:
> 
>   Peter, if you add this line to /etc/rc.d/syslog.conf,
> 
> local0.*     /var/log/dhcpcd.log

Does not like the command: command not found.

If I separate local 0.* I get: "not valid identifier"

> 
>   then when you 'dhcpcd -d eth[01] it will put debug lines
>   into /var/log/dhcpcd.log  (See 'man dhcpcd')

Saw it, unfortunately it does not work.

> > Yes neither in Fedora nor in DSL had I to enter anything. In Fedora I just
> > had to activate eth1, eth0 was taken by the onboard LAN card.
> 
>   It seems to me that Fedora is finding your add-on PCI card and
> assigning it eth0, yet Slackware is assigning it eth1 !?
> 
>   I expected, since you disabled the on-board ether device,
> all distributions would only find a 'eth0'.
> 
>   So, if Slackware assigns it 'eth1' and your rc.inet1.conf assigns
> DHCP to eth0, it will not work.

Slackware assigns eth0, not eth1. It is Fedora which still reads both since info stored in a file, activates then eth1 correctly for the external LAN card.
 
>   Run dhcpcd from a console. If Slackware sees your PCI NIC as eth1;
> dhcpcd eth1

Running dhcpcd eth0 from the consoles does nothing. Just sits for a while and returns to command mode.

>   If that works, you can either edit rc.inet1.conf or add
> 'dhcpcd eth1' to rc.local.
> 
> HTH, Chuck


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[chuck gelm]

Peter:

  Please adjust your system clock.
Your clock may be more than 5 hours ahead.
My email viewer is sorting your emails after Ray's responses.
:-|
Regards, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

On Fri, 07 Oct 2005 07:36:31 -0400
chuck gelm <chuck@gelm.net> wrote:

> Peter:
> 
>   Please adjust your system clock.
> Your clock may be more than 5 hours ahead.
> My email viewer is sorting your emails after Ray's responses.
> :-|
> Regards, Chuck

My clock is correctly set for the local time which is +8 from UTC (GMT).

Since I run from DSL I see when giving command date I get

Sat Oct  8 11:35:15 EDT 2005.

I don't know what the EDT part stands for. I think in slack it is PHT which is correct.

Regards
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Ray Olszewski]

Peter wrote:
> On Fri, 07 Oct 2005 07:36:31 -0400
> chuck gelm <chuck@gelm.net> wrote:
> 
> 
>>Peter:
>>
>>  Please adjust your system clock.
>>Your clock may be more than 5 hours ahead.
>>My email viewer is sorting your emails after Ray's responses.
>>:-|
>>Regards, Chuck
> 
> 
> My clock is correctly set for the local time which is +8 from UTC (GMT).
> 
> Since I run from DSL I see when giving command date I get
> 
> Sat Oct  8 11:35:15 EDT 2005.
> 
> I don't know what the EDT part stands for. I think in slack it is PHT which is correct.

EDT normally stands for Eastern Daylight Time, Eastern being the time 
zone for the East Coast of the United States. It is UT-4, not the UT+8 
you want. And that interpretation is consistent with what your mail 
software is actually sending, for example:

	Date: Sat, 8 Oct 2005 11:43:22 -0400

So even if your local time looks correct to you, your time *zone* is 
wrong, and that will cause e-mail (which always specifies both the local 
time and the UT offset) to appear wrong in any e-mail client that 
reports time based on either the recipient's local time zone or UT.

I'm not familiar with the designation "PHT", but since it is UT+8 and 
your mail server is "mail.meridian.ph", I'm guessing it refers to the 
Philippines.

To check what your computer thinks UT currently is, run "date -u". If it 
is wrong but your local time looks right, that is another indication of 
a timezone error.




-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[Peter]

On Wed, 5 Oct 2005 22:04:14 -0500
David Fierbaugh <david@fierbaugh.org> wrote:

> 
> Are you connecting to a home router, or to a cable/dsl modem?
> 
> Some cable/dsl services watch the MAC address, and won't allow connections 
> from any other network card.
> 

I have a broadband connection and had no problem with netconfig and the onboard LAN card.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[David Fierbaugh]

On Thursday 06 October 2005 09:54 am, Peter wrote:
> On Wed, 5 Oct 2005 22:04:14 -0500
>
> David Fierbaugh <david@fierbaugh.org> wrote:
> > Are you connecting to a home router, or to a cable/dsl modem?
> >
> > Some cable/dsl services watch the MAC address, and won't allow
> > connections from any other network card.
>
> I have a broadband connection and had no problem with netconfig and the
> onboard LAN card. -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

Have you tried booting knoppix? It is often helpful to try it out, and then 
you might be able to tell if it's a hardware problem, or software setup 
issue.

if it works under knoppix, try issueing a lsmod from the command line to find 
out what modules are loaded. Then, rmmod the ones that might be the network 
card, until it stops working, write that one down, reboot and try modprobing 
it to see if that makes the card work.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Netconfig Fail

[chuck gelm]

Peter wrote:
> Hi,
> 
> Slackware 10.1 kernel 2.4.29

  I have this same distribution in a few workstations here at home.

> My onboard LAN card on the mobo failed and I had to switch to an external LAN card.
> 
> I disabled in BIOS Ethernet onboard. Then I did netconfig. 

  What did you do with 'netconfig' ?

> Slackware found the LAN card I entered all necessary data and the configuration went w/o any errors.

  What did you enter?

> However, I cannot connect to the Internet. 
 > on booting after the MAC address was found
 > it should produce the the IP address which it does not.
 > It just sits for a while then continues booting.

  What is 'it' ?

 > The same happens when I do /etc/rc.d/rc.inet1.

  Try '/etc/rc.d/rc.inet1 stop && /etc/rc.d/rc.inet1'.
  e.g. 'stop' before you 'start'.
  But, really, I would like to see how you configured your
  interface first.

> Ifconfig naturally shows no connection just the loop-back.
> 
> Where is the hitch?

  	I need:
  What you entered into 'netconfig' and this should match your
  /etc/rc.d/rc.inet1.conf file.

  The output of 'ifconfig -a'.

HTH, Chuck

> I had no problem in Fedora4 to configure the new Lan card and in the gem Damned Small Linux distro,
  where I am now, the new LAN card was found w/o me doing anything.
> 
> Help for slackware appreciated.
> 
> Thanks & regards
> 
> Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs