Boot Message: 'eth0 failed' but still works?

olias · 09-06-2003, 10:14 PM

I can't figure this one out. I installed Mandrake 9.2rc1 and in the verbose boot-up screen I see...

"network:Bringing up interface eth0: failed"

But yet, my ethernet connection is working fine. I'm behind a linksys router that acts as a DHCP server and dynamically gives me an ip address.

Anybody know why I get this bogus error message and how I could fix it?

Thanks, Olias

emetib · 09-06-2003, 11:31 PM

i would take a look at your /var/log/syslog or even /var/log/messages to see if there is anything in there that might be of help.

when this error does come up, do you have to do anything at all to get it working? like checking the settings in the control center.
are you getting your hostname from the router, dhcp server. you can check this in the control center when you do the network configuration. click on auto-detect and expert and you will see what i mean.
other than that, unless it's doing an alias for you and the alias is working for some reason, i'm out of options.

good luck.

olias · 09-07-2003, 12:43 AM

I took a look at the syslog file as you sugested and it seem that the ifplug deamon is trying to load it again. What do you think...

Sep 4 23:04:02 localhost kernel: sis900.c: v1.08.06 9/24/2002
Sep 4 23:04:02 localhost kernel: eth0: Realtek RTL8201 PHY transceiver found at address 1.
Sep 4 23:04:02 localhost kernel: eth0: Using transceiver found at address 1 as default
Sep 4 23:04:02 localhost kernel: eth0: SiS 900 PCI Fast Ethernet at 0xb000, IRQ 9, 00:e0:18:7b:4b:99.
.
.
Sep 4 23:04:04 localhost kernel: eth0: Media Link On 100mbps full-duplex
Sep 4 23:04:04 localhost ifplugd(eth0)[916]: Link beat detected.
.
.

Sep 4 23:04:02 localhost network: Setting network parameters: succeeded
Sep 4 23:04:02 localhost network: Bringing up loopback interface: succeeded
Sep 4 23:04:02 localhost ifplugd(eth0)[916]: Using interface eth0/00:E0:18:7B:4B:99 with driver <sis900> (version: v1.08.06 9/24/2002)
Sep 4 23:04:02 localhost ifplugd(eth0)[916]: Using detection mode: SIOCGMIIPHY
Sep 4 23:04:02 localhost ifplugd(eth0)[916]: ifplugd 0.15 successfully initialized, link beat not detected.
Sep 4 23:04:02 localhost network: Bringing up interface eth0: failed
.
.
Sep 4 23:04:05 localhost ifplugd(eth0)[916]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
.
.
Sep 4 23:04:06 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Sep 4 23:04:07 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep 4 23:04:07 localhost dhclient: DHCPACK from 192.168.1.1
Sep 4 23:04:08 localhost dhclient: bound to 192.168.1.100 -- renewal in 42488 seconds.
Sep 4 23:04:08 localhost ifplugd(eth0)[916]: client: Determining IP information for eth0... done.
Sep 4 23:04:08 localhost ifplugd(eth0)[916]: Program executed successfully.

My hostname is just 'localhost' and that's it.

Anybody elese have this problem?

Thanks again, Olias

emetib · 09-07-2003, 01:36 AM

do a search to see if that is the correct module for your nic card. that could be one approach. i took a look at my log and see basically the same thing except without a failure.

Sep 7 00:08:59 Styx ifplugd[878]: Warning: Could not get interface address.
Sep 7 00:08:59 Styx ifplugd[878]: Using interface eth0/00:03:47:B1:24

F with driver eepro100 eepro100.c:v1.09j-t 9/29/99 Don
Sep 7 00:08:59 Styx ifplugd[878]: ifplugd 0.13 successfully initialized, link beat detected.
Sep 7 00:08:59 Styx ifplugd[878]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Sep 7 00:09:03 Styx dhclient: DHCPACK from 10.0.0.1
Sep 7 00:09:03 Styx ifplugd[878]: client: Determining IP information for eth0... done.
Sep 7 00:09:03 Styx ifplugd[878]: Program executed successfully.

not sure why i have the 'could not get interface address' though.
other than that, don't know.

take care.

olias · 09-07-2003, 08:33 PM

How would I search which module is getting loaded. I'm pretty sure thet right module would be sis900.

Thanks, Olias

emetib · 09-07-2003, 09:57 PM

i did a search the other day, and yes it's the right module.

i would just put it off to it being a rc, run cadidate. it's only a beta, in the final testings, so it could just be a bug.

you could go and get a pci nic, they are cheap and work wonders without any problems that i have seen. not with the 5 that i have anyway.

cheers.

highhighs · 09-08-2003, 02:02 AM

in 9.1 , this happens to me also with a usb ethernet card , it is kernel supported (pegasus2 based), and it hijackes my other nic so it is nomore usable(local lan)

olias · 09-08-2003, 09:51 PM

This just in... thanks to google.

Snipped from ---> http://www.stud.uni-hamburg.de/users...jects/ifplugd/

Quote:

When using ifplugd together with APM (and probably ACPI) suspends, strange things may happen: some network devices fail to detect the network cable for a short period of time before and after the suspend. When using the -f switch, this will be treated as "no link beat", thus the network is shutdown after a timeout. During this timeout the machine changes to suspended state. When it is resumed again, the timeout will be run out, the network is deconfigured, however, as the next cable detection succeeds, the network is configured again immediately. To fix this problem, ifplugd should be disabled before the APM suspend and enabled back after the suspend. This may be done by using apmd and adding a script to /etc/apm/{suspend,resume}.d which simply calls /etc/init.d/ifplugd suspend, resp. /etc/init.d/ifplugd resume. It might even be a good idea to shut down the network completely during suspend, this may be achieved by calling /etc/init.d/ifplugd stop and /etc/init.d/ifplugd start in the appropriate places. I strongly urge the packagers of this software for the Linux distributions to add such scripts to their packages.

I'll try it and report back, Olias

camelrider · 09-08-2003, 10:39 PM

I just read "man ifplugd"
Now, more complexity?
I still haven't figured out "devfs".

bdad · 12-31-2003, 10:23 AM

I too had this same message, I think it is related to the way ifstatus was detecting the status of the interface. I have tested one option, but not the other.

Option 1: Upgrade to the latest ifplugd. The release with 9.2 is .15, however .20 is out and available in the cooker section. I pulled it from the following: http://www.rpmfind.net//linux/RPM/co...1mdk.i586.html
This is the option I have done and it is working fine now.

Option 2: Change the following line found in /etc/ifplugd/ifplugd.conf:

Old : ARGS="-f -u0 -d10 -w -I"
New : ARGS="-fwI -u0 -d10 --api-mode=ethtool"

If you use wireless or have multiple adapters and want to apply it to only the eth0 interface, use the following:

ARGS_eth0="-fwI -u0 -d10 --api-mode=ethtool"

By running /sbin/ifstatus eth0 you should notice it attempts to detect link up 3 different ways and fails on the third. This seems to be corrected in 0.20 of the software.

Hope this helps

BDad

pzatch · 12-31-2003, 12:29 PM

Olias and any one else who has this problem.
Olias is behind a router. If everything is starts of as off then you fire up the router/ computer/ modem all at the same time you'll always get an ethernet failed singnal. This is because it takes longer for the ethernet and router to get the return handshake than it takes for the computer to ask the router for an address. The router will not give a dhcp address unless it gets one from the IP first then it only adds a subnet number to the end of the string..
Try this quick test. Turn on the modem and router one full minute before you turn on the computer next time and see how the things are detected. Since I have 4 computers hooked to my router I leave mine on all the time and I never get this error again.

olias · 12-31-2003, 05:50 PM

I've since switched to Gentoo and am using the 2.6.0 kernel. I love this distro!!! I learned so mush by using it. BTW, my router and cable modem are always on. Thanks for all the replies.

olias