apt-get screwed my network interface!
May 6, 2005 10:54 AM Subscribe
Lords of Linux! Demigods of Debian! I beseech thee. I inadvertently apt-get installed etherconf, and it nuked my ethernet interface!
posted by jojopizza to computers & internet (7 answers total)
I was doing an "apt-get upgrade apache", to get on the latest version. It presented me with a list of packages it wanted to upgrade in conjunction, and I blithely accepted. Well, it started churning away, and then it said it was installing etherconf. At this point I lost my ssh session to the server.
I drove down to the office to log on and see what was up. Logged on locally, I can see that it's not recognizing the eth0 interface anymore. Ifconfig -a just shows lo0, 127.0.0.1.
I ran "dpkg-reconfigure etherconf" and it says that the interface detector can't detect any network interfaces. Argh! After exiting from etherconf I get a message to the console: "eth0: ERROR while getting interface flags: No such device"
This nic was easily recognized by Debian when I did the initial install. It's been a few years, so I have no idea what kind it is, or where the drivers are, but I figure if I can get Debian to do whatever detection magic it did on the initial install, it will be able to recognize this card again. It's something very generic, like a Netgear, or an IBM card.
Oh, and I checked out /etc/network..
It still has eth0 listed in the interfaces, though it decided to change the ip address from .106 to .110. I changed it back and tried rebooting. No good!
Anyone got suggestions? I suppose I can reinstall Debian on another hard drive and try copying files over, but that sounds like it will be a long, dreary process.