On Fri, 2005-03-04 at 01:43 +0100, Alexandru Cabuz wrote: > My AMD64 sid box was running along nicely until yesterday, when after > a reboot it didn't want to connect to the internet anymore. I am using > dhcp, and when I start the client here is what I get: I've had this happen. Usually it's because discover or modprobe or whatever-the-tool-of-the-week-is has decided to load the ethernet drivers in a different order, changing the eth0->eth1 and eth1->eth0. I think there's a modprobe config file thing you can use to give drivers specific eth? names but maybe that's only on Redhat. (I don't know). -s
Attachment:
signature.asc
Description: This is a digitally signed message part