Red Hat Bugzilla – Bug 55714
(NET TULIP)bug in tulip 0.9.15 in Accton 1207C
Last modified: 2013-07-02 22:05:11 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)
Description of problem:
The 0.9.15 driver as included in the updated 2.4.9 kernel doesn't work
with this card.
It works fine with 0.9.14 as used in RedHat kernels 2.4.2 and 2.4.3.
Nov 3 10:35:43 mx0 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Nov 3 10:35:43 mx0 kernel: eth0: 21140 transmit timed out, status
f0660000, SIA 000000c6 ffff0000 fffbff7f 8ff0c008, resetting...
Nov 3 10:35:43 mx0 kernel: eth0: transmit timed out, switching to
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install later kernel with this card Accton 1207C
2. You won't get a packet out.
Actual Results: No network access
Expected Results: Network should work
Sourceforge lists 0.9.14 http://sourceforge.net/projects/tulip/ as the
latest stable version but it appears that 0.9.15 was included in the
kernel sources at about 2.4.5.
Search for tulip 0.9.15 on Google and you'll see this isn't the only card
having this problem.
We've verified this on two systems both 7.1 upgraded to latest 2.4.9 RH
One is an old Pentium the other is a Dual PIII L440GX based system.
Additionally this card always had detection problems. With the older
driver we specify append="ether=0,0,5,eth0" in lilo.conf to make it 100FD
so part of the problem may be the card but that doesn't help much.
Please try the "tulip_old" driver; it's the 0.9.14 driver....
Looks like it works fine.
(As expected really as it's the driver that worked. )
Sorry I should have noticed you had left the old driver in the source tree.
If I had I wouldn't have raised the bugzilla entry.
I guess we'll just have to remember to update modules.conf after updating the
Thanks for your prompt response.
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
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/