From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) Description of problem: 3c509 - Have just upgraded to 7.1 from 6.2 - I have installed and configured the Etherlink III card and the interface comes up but cannot ping anthing - I get "network unreachable". Now, I am running Samba and when the PC first booted it registed itself and I could see it in network neighborhood from my Windows 95 PC on the same subnet but then Linux drops off the network and I cannot ping or browse. The same PC can ping using Win Me and was working OK under redHat 6.2 I have set the firewall to no security. I also get messages about TX timeout FIFO 2040 - Can anyone help ?? How reproducible: Always Steps to Reproduce: 1. Boot PC 2. Try to ping anything 3. Actual Results: "network unreachable" message Expected Results: response from other host Additional info:
Could you offer a little more info? Output of the following commands would be very useful after startup of the machine: dmesg ifconfig -a netstat -rn cat /etc/sysconfig/network-scripts/ifcfg-eth0 (assuming the card is eth0) Thanks, Read ya, Phil
smells of a driver issue, or local configuration; changing component.
Sorry guys, Can't help with any more info as I persisted for a few days then swapped the card out with a DEC DE450 and it works no problem using exact same configuration,... I'm surprised no-one else has reported a similar problem. I can put the 3Com back in if you're really interested. I have used the same NIC's in my 3 boxes for about 5 years and they are all 3c509's and have never had a problem before under any O/S, including Redhat 5.2 & 6.2, Caldera Open Linux, Slackware Linux, Windows 3.1, Windows 95/98/Me, Windows NT/2000, strange no ??
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/