Bug 61337 - tulip driver still does not send any packets
Summary: tulip driver still does not send any packets
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: alpha
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Copeland
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-18 01:49 UTC by Michal Jaegermann
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-03-18 10:15:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2002-03-18 01:49:51 UTC
Description of Problem:

'pcitable' for kudzu and on a ram disk say:

0x1011	0x0019	"tulip"	"DEC|DECchip 21142/43"

I happen to have a chip with this PCI id in my test machine and current
tulip drivers _do not work_ with it (as reported already a number of times).
Actually it is even worse.  A module will load and an interface will start
but not a single packet will go through in either direction.  If this
interface will be configured for DHCP then on a startup it will wait
patiently for a response which will never come.

There were times when 'tulip', before it got "improved", worked fine with
this card but not for quite a while.  Current 'de4x5' driver does work
in that sense that an interface not only goes up but one can even send
some traffic through it.

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

kernel-2.4.9-24

Comment 1 Phil Copeland 2002-08-12 18:46:44 UTC
Current 7.2 release

Phil
=--=


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