From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3)
Description of problem:
My Gigabit net card (NetGear GA311) wont work with Fedora Core 2.
At first it seems to startup just fine using the ifup command. But
there isn't any link (Noticed on switch).
During boot of the machine my switch is marking for a link (100Mbit),
but that is before Linux is loaded. When Linux is starting up the link
Then I noticed that on the console display every 10 sec. it displays
r8169: eth2: Reset RTL8169s PHY.
The eth2 is (of course) the correct net card.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ifup eth2 - on my system :-)
Actual Results: Net card won't work (no link).
Message on console: r8169: eth2: Reset RTL8169s PHY every 10 seconds.
Expected Results: Net card should work and error messages should be gone.
Can you specify the last revision of the kernel which was
functionnal for your network adapter ?
A description of the host system + lspci -vx output will be welcome.
Created attachment 105472 [details]
Output from lspci -vx
This is the first time I'm using this netcard. It's a new one.
The lspci info is of course added by your request.
Btw. I found out that by setting the netcard to run only at 10Mbit by
attach it to an old hub, the message on the console is gone and i can
actually use the netcard. Unfortunally at the "speed" at 10Mbit :(
I have checked the sources of the kernel 2.6.8-1.521 and it lags a
bit wrt link management for the r8169 driver.
You can try to apply
It contains an upgrade to the current 2.6.9 code which seems
decently stable and will provide a few extra functions to manage the
link via 'ethtool'.
Please report success/failure.
Btw I am not sure that you want to have the 8169 on the same irq
line than your scsi adapter (especially as it is shared a lot).
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.