On Sun, Mar 29, 2009 at 10:14 AM, widux <wi...@web.de> wrote: > Am Sonntag, 29. März 2009 11:05:10 schrieb Magnus Therning: >> After being away on holiday for 3 weeks I ran a major "apt-get update" >> on my (amd64) Sid system this morning. After the update I rebooted >> and noticed that my eth0 is gone. Here's what I see when run >> "/etc/init.d/networking restart" (minus the DHCP copyright notice): >> >> SIOCSIFADDR: No such device >> eth0: ERROR while getting interface flags: No such device >> eth0: ERROR while getting interface flags: No such device >> Bind socket to interface: No such device >> Failed to bring up eth0. >> done. >> >> I installed "discover" and saw eth0 come back, but go away at the next >> reboot again, not to be seen again. >> >> I've checked that the correct kernel module for the network card is >> loaded (e1000e). >> >> How do I get my eth0 back again? >> >> /M >> >> -- >> Magnus Therning (OpenPGP: 0xAB4DFBA4) >> magnus＠therning．org Jabber: magnus＠therning．org >> http://therning.org/magnus identi.ca|twitter: magthe > Hi, > > I read about this issue on sid systems in the sidux forums - seems that it > is caused by udev in the last dist-upgrade: > http://sidux.com/PNphpBB2-viewtopic-t-15382.html > I do not know if this helps you...
That seems to do the trick indeed. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
