WTF!? "lo: unknown interface: No such device"

Praxxus

In trying to upgrade udev on a system, I seem to have left things in a bit of a confused state. The system iteslf is a 2x Opteron SunFire v20z, with two Broadcom BCM5704 (tg3) Gbit NICs. When I compile the tg3 module into the kernel, it boots up with lo and eth1. Trying to bring up eth0 gets an "unknown interface" error.

When I compile tg3 as a module, eth0 and eth1 come up like they should, but lo is missing! How the hell does that happen? /etc/init.d/net.lo start gets me:

rsa4046 · Posted: Thu Sep 14, 2006 4:26 am Post subject:

did you run etc-update after updating baselayout? I broke my net.lo by neglecting to run etc-update after the update.

Praxxus · Posted: Thu Sep 14, 2006 4:14 pm Post subject:

Yup. etc-update, env-update, source /etc/profile . . . you name it. None of it helped.

Since posting this, I have "tricked" the server into working. I combined the working elements for eth0 and eth1 (compiled tg3 in as a module) and the working elements for lo (compile network driver in as module) and compiled the dummy and tun/tap drivers into the kernel. Now lo, eth0, and eth1 all come up at boot time like they should.

That is a retarded workaround.
_________________
My glaucoma just got worse!

isomer · n00b Joined: 27 May 2003 Posts: 19 Location: Canada, eh?

Same problem. I accidentally upgraded to an ~x86 udev, and then downgraded back to the stable one. The ~arch install left a bunch of rules in /etc/udev/rules.d that don't work. I replaced them with the ones that were there before (yay backups!) and everything started working again on the next boot. Phew.

Hope this helps....