Bug 53815 - Tulip driver fails to work correctly with DFE-570TX NIC.
Summary: Tulip driver fails to work correctly with DFE-570TX NIC.
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kernel   
(Show other bugs)
Version: roswell
Hardware: i386 Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-09-19 15:37 UTC by Ben Greear
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-06-21 23:09:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ben Greear 2001-09-19 15:37:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.3-12 i686)

Description of problem:
The Tulip driver does not auto-negotiate correctly with the DFE-570-TX
4-port 10/100bt NIC.  This driver problem was fixed in later kernels,
starting around 2.4.8 I believe..  Results of this bug are lots of
carrier errors and collisions on a link that should be 100bt-FD.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Use DFE-570TX NIC with any auto-negotiating 100bt NIC/Switch.

Actual Results:  Carrier errors & collisions:  Bad auto-negotiation

Expected Results:  Sweet packet pushing at 100bt-FD.

Additional info:

Comment 1 Arjan van de Ven 2001-09-19 15:39:28 UTC
Could you try the tulip_old driver instead ?
(should be included in the latest roswell kernels)

Comment 2 Ben Greear 2001-09-19 16:16:40 UTC
I can find no tulip_old module in the 2.4.7-2 roswell kernel...

For what it's worth, the kernel's tulip driver never worked for the
DFE-570TX 4-port NIC in the entire 2.4 series up untill about 2.4.8

Comment 3 Ben Greear 2002-06-21 23:09:38 UTC
The driver works fine in RH 7.3, so I'd consider closing this bug.

Note You need to log in before you can comment on or make changes to this bug.