eth0 stopped working

[sergest]

For some strange reason my wired ethernet port stopped working when I try to boot up my Fedora kernel 2.6.22.1-41.fc7. Earlier versions of fc7 kernel stopped working as well. I see no telltale link lights on my Linksys router. The W-- XP on my dual boot system works just fine! This all happened for no reason that I can think of! Any suggestions would be welcome...
Here is the "dmesg" dump:

eth0: RealTek RTL8139 at 0xffffc200001ea000, 00:14:2a:b1:32:27, IRQ 22
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008205a. (queue head)
eth0: Tx descriptor 1 is 0008204e.
eth0: Tx descriptor 2 is 00082156.
eth0: Tx descriptor 3 is 00082046.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008205a. (queue head)
eth0: Tx descriptor 1 is 00082046.
eth0: Tx descriptor 2 is 00082156.
eth0: Tx descriptor 3 is 00082046.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00082156. (queue head)
eth0: Tx descriptor 1 is 00082156.
eth0: Tx descriptor 2 is 00082156.
eth0: Tx descriptor 3 is 00082156.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008205a. (queue head)
eth0: Tx descriptor 1 is 0008205a.
eth0: Tx descriptor 2 is 0008205a.
eth0: Tx descriptor 3 is 000820d3.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00082074. (queue head)
eth0: Tx descriptor 1 is 000820d3.
eth0: Tx descriptor 2 is 00082074.
eth0: Tx descriptor 3 is 000820d3.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00082074. (queue head)
eth0: Tx descriptor 1 is 000820c7.
eth0: Tx descriptor 2 is 000820e0.
eth0: Tx descriptor 3 is 000820cf.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 000820ce. (queue head)
eth0: Tx descriptor 1 is 000820cf.
eth0: Tx descriptor 2 is 000820ce.
eth0: Tx descriptor 3 is 000820cf.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 000820ce. (queue head)
eth0: Tx descriptor 1 is 00082118.
eth0: Tx descriptor 2 is 00082130.
eth0: Tx descriptor 3 is 000820fc.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 000820ab. (queue head)
eth0: Tx descriptor 1 is 00082117.
eth0: Tx descriptor 2 is 0008206e.
eth0: Tx descriptor 3 is 0008205a.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[serge@localhost ~]$


Had to use Windows to post this --- bummer!

[red_rob]

For some strange reason my wired ethernet port stopped working when I try to boot up my Fedora kernel 2.6.22.1-41.fc7. Earlier versions of fc7 kernel stopped working as well. I see no telltale link lights on my Linksys router. The W-- XP on my dual boot system works just fine! This all happened for no reason that I can think of! Any suggestions would be welcome...
Here is the "dmesg" dump:

eth0: RealTek RTL8139 at 0xffffc200001ea000, 00:14:2a:b1:32:27, IRQ 22
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008205a. (queue head)
eth0: Tx descriptor 1 is 0008204e.
eth0: Tx descriptor 2 is 00082156.
eth0: Tx descriptor 3 is 00082046.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008205a. (queue head)
eth0: Tx descriptor 1 is 00082046.
eth0: Tx descriptor 2 is 00082156.
eth0: Tx descriptor 3 is 00082046.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00082156. (queue head)
eth0: Tx descriptor 1 is 00082156.
eth0: Tx descriptor 2 is 00082156.
eth0: Tx descriptor 3 is 00082156.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008205a. (queue head)
eth0: Tx descriptor 1 is 0008205a.
eth0: Tx descriptor 2 is 0008205a.
eth0: Tx descriptor 3 is 000820d3.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00082074. (queue head)
eth0: Tx descriptor 1 is 000820d3.
eth0: Tx descriptor 2 is 00082074.
eth0: Tx descriptor 3 is 000820d3.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00082074. (queue head)
eth0: Tx descriptor 1 is 000820c7.
eth0: Tx descriptor 2 is 000820e0.
eth0: Tx descriptor 3 is 000820cf.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 000820ce. (queue head)
eth0: Tx descriptor 1 is 000820cf.
eth0: Tx descriptor 2 is 000820ce.
eth0: Tx descriptor 3 is 000820cf.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 000820ce. (queue head)
eth0: Tx descriptor 1 is 00082118.
eth0: Tx descriptor 2 is 00082130.
eth0: Tx descriptor 3 is 000820fc.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 000820ab. (queue head)
eth0: Tx descriptor 1 is 00082117.
eth0: Tx descriptor 2 is 0008206e.
eth0: Tx descriptor 3 is 0008205a.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[serge@localhost ~]$


Had to use Windows to post this --- bummer!

It happened to me also, the exact same situation, even NIC, dual boot, the router... Exact match to my problems. Im stumped as well.. SOMEBODY help!!! LOL Cuz the effort for me to see this tthrough is well worth it.

[red_rob]

The only workaround I have for this , is for me to enter my BIOS, and toggle the LAN options, exit, and f7 initiates eth(0)... Its primitive, but for now its working.. Sergest , since you have a match for my hardware , perhaps you might give it a try, provided that your BIOS version is similar to mine also ... But Im still puzzled as to why this is happening.. f7 lists the device correctly, so Im failing to recognize the reasons why the connection is inconsistent.. Sometimes my green LED indicator is on , othertimes the Ethernet ( actual physical piece) light isnt blinking. Error is reported similarly at f7 boot screen eth(0) = FAILED .....

[sergest]

Thanks for the advice, but BIOS trick did not work for me. It is frustrating when something ceases to work for no apparent reason. I will try tomorrow with Knoppix or another live CD just to see if it is a Fedora issue.

[oziris]

I have the same problem and I have a realtek card. Any solution yet?

[red_rob]

Apparently not yet.. I havent spent a whole lot of time networking with f7 due to my NIC issue... I heard about another guy , similar issue, but he installed a cheapie, functioning, PCI-card NIC, tested, and fired up.... Some basic doer's are fairly reasonable in price, however provided that you have the time and PCI compatible card controller... Im starting to think there will be a fix soon, since it seems to be an imcompability with hardware type issue.. In the meantime, Im looking for device driver- file- translator - type - method so I can load a Windows driver file at setup for f7, or something to the effect of conversion so f7 uses the driver.. Anyone know a method or utility that will achieve this????

[sergest]

Well trying to boot Knoppix failed, the boot just hung up, so I do not know if Knoppix would have been able to activate the interface chip. I never had a problem while running FC5, when I upgraded(?) to FC6 it would occasionally stick, but until recently FC7 worked fine.

I did run Windows XP update recently and also uploaded a driver update for the Realtek chip. I think that my problem with Fedora may have started since then. I wonder if the Windows driver upon shutdown puts the NIC into some sort of state where the Linux driver has a problem with activating it from a cold start/reboot. Anyway I am out of ideas.....

Putting in a NIC card and disabling the on-board interface should work, but one simply SHOULD NOT have to do it!

I think I will try to boot Ubuntu 7.04 and see what it does.

[sergest]

OK, I have solved(?) my problem with eth0 under Linux! After booting Knoppix, Ubuntu and Mandriva live CDs and noticing that none of them seemed to be able to wake up and use the Realtek interface (although they all detected it and reported it as present and working), I decided that Windows must have caused the problem! I went back to Hardware manager in Windows and rolled back the Realtek driver from the latest update to the previous one circa 2003. Bingo, when I restarted the computer with Linux the eth0 was back and working. Watching the network LAN lights on my router I can see that the new Windows driver turns off the data stream (lights go out), while the old one does NOT. Linux drivers do not seem to able to wake up the slumbering NIC from its Windows induced coma, while XP has no problems.

Evil, evil Microsoft strikes again, will the Linux knights ride out and meet the challenge?

Meanwhile at least the damn thing is working.

[red_rob]

OK. I can confirm that one. The driver rollback solved exactly what I needed.. Thanks bud ! Oh, and I really shouldnt get started on the evil and sadistic corporate machine that is M$.... The world looks great thru f7. Good thread...

[blue13130]

I had the same problem and the XP rollback solved it for me also. Thanks for the help.

[Melio]

what happens if you booted with debian, and now you have the same issue. how does one fix this WITHOUT using windows?

[oziris]

Windows driver does something to ethernet card. Unplug your computer from electricity; just in case press power button (capacitors). Plug it back in and ethernet should work like a charm.

[Iron_Mike]

Known bug, upgrade the kernel........

[hood]

I had the exact problem, can be solved by enable "WakeOnLan after shutdown" in XP network card driver, details here:

http://forums.fedoraforum.org/forum/...tus+c07f+media

[scotty38]

Stop it please the site's busy enough as it is.... :-)