eth0
 

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:

lo Link encap:Local Loopback
inet addr: 127.0.0.1 Mask 255.0.0.0
UP LOOPBACK RUNNING MTU:16436
RX packets:106 errors: 0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped: 0 overruns:0 carrier:0
collisions:0
RX bytes13208 (12.8 KiB) TX bytes:13208 (12.8)


Any ideas? Please be specific, I'm new at this...

Thanks much.

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?

You can try:

apt-get remove

your mileage may vary.

and what exactly would i be removing? is a list generated of all the apt-get's i've done?

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:
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:

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?

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.

what happens when running
"modprobe rtl8139"
?
is it successfully loaded? do you get an error message?
you didn't answer that in the previous post...

Terribly sorry. I get the following error after running modprobe:
Sorry about that. Thanks for your interest.

ok. sounds like the module isn't compiled.
i suggest you recompile the kernel.

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.

I'm sorry, but I was out of ideas...

Are you _sure_ the module is rtl8139?
Which kernel version are you running?
Try doing a: "modprobe 8139too"

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.

thanks