tulip driver again
I know that this is boring and a number of my earlier reports was apparently ignored but a tulip driver "0.9.15-pre10 (Mar 8, 2002)" as used in 2.4.19-pre4 still does not really work. I know that it is fine with various clones like "Davicom" and "Lite-On PNIC", for example, but with a real tulip from DEC, PCI id 1011:0019, not a single ethernet packet is getting through.
Luckily 'de4x5' allows me to use a network but maybe this "tulip" driver should be renamed onto "anything-but-tulip"?
Michal
Quoted 6 lines · Michal Jaegermann
I know that this is boring and a number of my earlier reports was apparently ignored but a tulip driver "0.9.15-pre10 (Mar 8, 2002)" as used in 2.4.19-pre4 still does not really work. I know that it is fine with various clones like "Davicom" and "Lite-On PNIC", for example, but with a real tulip from DEC, PCI id 1011:0019, not a single ethernet packet is getting through.
There is a tulip specific discussion list, which may explain why you get ignored on this forum.
List-Id: Linux Tulip device driver list. <tulip.scyld.com>
List-Help: <mailto:[email protected]?subject=help>
Signature · 3 lines
Brian Litzinger <[email protected]> Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
Quoted 6 lines · On Thu, Mar 28, 2002 at 06:40:21PM -0800, [email protected] wrote:
Quoted 2 lines · Michal Jaegermann
I know that this is boring and a number of my earlier reports was apparently ignored
There is a tulip specific discussion list, which may explain why you get ignored on this forum.
Well, in a due time I filed pretty detailed bug reports, with dumps of PCI space from older working and non-working drivers and what not, on sourceforge where presumably a development of this driver was going. This was ignored there as well.
Michal
Quoted 7 lines · Michal Jaegermann
Quoted 5 lines · On Thu, Mar 28, 2002 at 06:40:21PM -0800, [email protected] wrote:
Quoted 3 lines · Michal Jaegermann
I know that this is boring and a number of my earlier reports was apparently ignored
Quoted 9 lines
Quoted 3 lines
There is a tulip specific discussion list, which may explain why you get ignored on this forum.
Well, in a due time I filed pretty detailed bug reports, with dumps of PCI space from older working and non-working drivers and what not, on sourceforge where presumably a development of this driver was going. This was ignored there as well.
Currently the tulip driver is very stable for a large number of chipsets, but not all of them. And there are some problems like, "calling this function with 1 as argument, and some chipsets work. calling this function with 0 as argument, and that breaks some chipsets but then other chipsets are fixed."
The temporary solution is to use the latest _stable_ version of the driver, on http://sf.net/projects/tulip/ or use the de4x5 driver. I am working on the long term solution, which is fixing the link state machine in the driver to actually be (a) sane and (b) workable for all chipsets.
This work is going to be merged into 2.5.x series _first_, then after it's proven stable merged back into 2.4.x as a solution for all. But this takes time... in the meantime, there are the temporary solutions mentioned to get you by.
Jeff
"Me too" however I managed to get mine to work by swaping PCI cards in/out and doing power off reboots. It is working on this particular boot up so I'm leaving it running.
Jeff Garzik, if you want the lspci, register dump, etc, please speak up.
David
Quoted 4 lines · Michal Jaegermann
I know that this is boring and a number of my earlier reports was apparently ignored but a tulip driver "0.9.15-pre10 (Mar 8, 2002)" as used in 2.4.19-pre4 still does not really work. I know that it is
Quoted 3 lines · David Ford
"Me too" however I managed to get mine to work by swaping PCI cards in/out and doing power off reboots. It is working on this particular boot up so I'm leaving it running.
Jeff Garzik, if you want the lspci, register dump, etc, please speak up.
Yes, please do.
The more bug reports I can receive (in private or CC'd to lkml), the better picture I get. If you have multiple tulips, feel free to email reports on those too :)
Best output is:
lspci -vvvn
dmesg, after updating drivers/net/tulip/tulip.h TULIP_DEBUG to 5,
and recompiling
tulip-diag -mmaavvveef
tulip-diag was written by Donald Becker, and is available from ftp://www.scyld.com/pub/diag/ Compiling instructions are at the end of tulip-diag.c. You should grab libmii.c as well.
Jeff