eth0 not started--startup dependency weirdness

[nuke]

This started happening recently, but I'm not sure when, since I don't reboot very often.

As startup is happening, I see the 'Starting network interface lo' message, but no corresponding output for eth0, even though I do have a net.eth0 symlink to net.lo in /etc/init.d/. Then several services complain that they can't start because net.eth0 failed to start. The thing is, by the time the machine is up, net.eth0 is up, even though I never saw any message about it.

I have net.eth0 in the default runlevel.

When I shut down, I see the corresponding "Shutting down eth0" message in addition to the one for lo.

If I hit 'i' during startup to go interactive, and just hit '1' ('start this service') for each of the services (I still never see the net.eth0 one), all the services start successfully, so I'm guessing there's some kind of race condition with net.eth0 and the things that depend on it.

Any ideas? I see from the baselayout changelog that the way networking dependencies work has changed recently.

Thanks.

[jmbsvicetto]

Hi.

If you updated your system recently, including baselayout, did you remember to update the config files?
Look at rc-update show | grep net. Did you compile the driver for your nic into the kernel or as a module? If you did as a module, are you loading it on /etc/modules.autoload.d/kernel-2.6?
_________________
Jorge.

Your twisted, but hopefully friendly daemon.
AMD64 / x86 / Sparc Gentoo
Help answer || emwrap.sh

[nuke]

If you did as a module, are you loading it on /etc/modules.autoload.d/kernel-2.6?

I hadn't been, so I tried that, and it did the trick.

I thought that coldplug would take care of loading the ethernet module for me, is there something I can do to coax it into doing so?

Thanks for the tip!
[/i]