Description of problem: The Gigabit ethernet doesn't work at all. Version-Release number of selected component (if applicable): I'm using the latest Rawhide kernel - 2.6.27.4-79 on F10 Preview. How reproducible: All the time. Steps to Reproduce: 1. Just boot, and no workie! 2. 3. Actual results: No link light, and can't get it to come up through any commands. Expected results: Should automatically come up when a cable is plugged into it. Additional info: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded r8169 0000:0a:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 r8169 0000:0a:00.0: setting latency timer to 64 r8169 0000:0a:00.0: unknown MAC (27a00000) r8169 0000:0a:00.0: no MSI. Back to INTx. eth0: RTL8169 at 0xffffc2000064c000, 00:1e:ec:b7:43:18, XID 24a00000 IRQ 19
Perhaps you could try completely powering down the machine and boot that same kernel again. There were some r8169 reports where this seems to have helped.
I have actually tried that, and nothing is different.
kernels 2.6.27.4-86 and higher have backports of the 8169 changes from 2.6.28, which will hopefully resolve this.
So, will the final release of Fedora 10 have that kernel? Thanks.
it will have at least that version, yes. likely something even newer.
Excellent. The weird thing is, with playing around with other things, I had some repeated reboots to try out some sound configuration options on this same hardware. Just for grins I plugged the ethernet cable in, and now its working. It's a mystery, because reboots in the past did nothing. Oh, well, I'll look forward to the final release and the new kernel. Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Running Fedora 10 I experience the same problem. Looks very similair to https://bugzilla.redhat.com/show_bug.cgi?id=444966 I also see the amount of interrupts for this nic going through the roof.
*** This bug has been marked as a duplicate of bug 460747 ***