DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm running debian unstable. A week ago, about, i did an apt-get update/upgrade/dist-upgrade and afterwards, eth0 wen haywire. To make a long story short: it no longer works.
I run /etc/init.d/networking restart as root and it says:
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
exiting.
Failed to bring up eth0.
done.
So, i do ifconfig to see what it says, and it looks somewhat ok:
Your ifconfig returns that your loopback is OK, in other words, your system can talk to itself. 127.0.0.1 is local loopback. It looks like you setup is not seeing you NIC. What model and make is your NIC?
THe NIC is onboard the mother board intel #82562EZ...it used to work is the thing...before i ran the updates. I did a debian netinstall...so i know it worked...i chose an option for some packages...is there a way to undo all of the past apt actions?
try running "ifconfig -a". if eth0 doesn't show, you will have to insert the module for your nic ("modprobe <nicmodule>"). if eth0 shows in the list, check your /etc/network/interfaces file. maybe you overwrote it when upgrading. after loading the nicmodule and/or editing the interfaces-file, run "/etc/init.d/networking restart".
I get this same error, though right after installing unstable. It only happens after everything updates itself, so it does work on the first boot.
I'll try what was suggested in the above post.
Edit: Well that doesn't seem to work. Oh well. Anyway, I tried the following:
First I checked /etc/network/interfaces , which contained the following:
Code:
auto lo
iface lo inet loopback
# Thid entry was created during the Debian installation
auto eth0
iface eth0 inet dhcp
That seems to be in order, so next I tried loading the module RTL8139, as that's the chipset of my ehternet card. Then I ran /etc/init.d/networking restart, and got the following output:
Code:
reconfiguring network interfaces... cat: /var/run/dhclient.eth0.pid: No such file or directory
eth0: ERROR while getting interface flags: No such device
<snip>
I'm guessing this is the problem. /var/run/dhclient.eth0.pid does not exist.
Just to reiterate, this is a Sarge install using the new beta installer. I've tried the install multiple times, and always get the same message after the second reboot (Install boot -> apt update boot -> next boot (Now stuff is buggered))
If anyone has any suggestions that'd be wicked. Should I just wait until the devs fix this? Should I submit a bug? Is this a bug?
Last edited by Eatingdogs; 04-15-2004 at 01:18 AM.
Is the NIC connected to a network or directly to your router? If it is connected to your home network, do you have a DHCP server?
If eth0 shows up in "iptables -a" and if you want it to have a static IP address on a home network, you can try running
ifconfig eth0 192.168.0.3
(or other appropriate IP address) to manually set its address. You may have to tell ifconfig your netmask and/or broadcast settings.
Hopefully that helps. It sounds like the first phase of the install is configuring your network settings for you, and the end phase of installation is not.
Nope, sorry I'm not on a hone network, my adsl modem goes straight to the ethernet card. The dhcp server is that of my isp. Anyway, I have another clue: After the part of the bootup where it says "Detecting Hardware..." Theres a line that's something like the following:
Skipping rtl8139 assuming it is comiled into the kernel
The only thing is I'm pretty sure that driver is NOT compiled directly into the stock debian kernel, so I'm guessing it just can't ind the module for some reason.
Any more ideas?
Also, sorry for the hijack Bookspoppa, it's just that we have the exact same problem.
Really? This seems like an odd choice. I JUST installed this. It's a brand new install. The only thing that's been done with it is Install, reboot, apt updates (So net works), reboot, net doesn't work. I think the problem is with the current packages.
hey, eatingdogs, its no big deal that you imposed on this forum, but if you figure out the answer, could you please post it in detail please. I reinstalled to see if I had selected a wrong command while installing, but it did the same thing again. Please let me know what you find out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.