Description of problem: Both mii-tool and ethtool indicate that there is no link on an SMSC Epic/100 83c170 (using the epic100.c driver) card, despite the fact that there is in fact a link and manual configuration of the card (either by static address assignment or dhclient) works properly. This causes the network scripts to fail. The workaround at http://www.vmware.com/support/guestnotes/doc/guestos_redhat90.html#1128831 allows the scripts to work. Version-Release number of selected component (if applicable): kernel-2.6.5-1.354 How reproducible: Always Steps to Reproduce: 1. Obtain a crappy SMC NIC 2. Attach a known good Ethernet cable (you can test this by manual configuration of the card or hand-starting dhclient) 2. run ethtool on it Actual results: ethtool reports link down Expected results: ethtool reports link up Additional info:
Created attachment 100294 [details] lspci information
(This is likely related to 120623 ... sorry for the spam, I had so much trouble getting bugzilla to play nice with my browser that I forgot to mention that.)
Unrelated I think. The "mii' bug you see ought to be fixed in the errata kernel we released. Please test and let me know
Assuming that you are referencing 2.6.6-1.435, the bug does not appear to be fixed. Both mii-tool and ethtool still report the link as down, despite the NIC being operational and in use as the host's only network interface.
fixed in the latest errata kernels ?
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. Thank you.