> Uhh, the time is now 05:23 AM, and I finally got the 2.0.24 release together.
> Could people please test this out, so that I could at least feel that I
> haven't been up this late (early) for nothing? I'm going to bed,
>
> Linus
Well, my netword card (Kingston PCI, DEC 21041 based) doesn't exactly
like the changes to tulip.c in 2.0.24 - it times out on every single
packet so the driver ends up filling the kernel log with
eth0: Enabling 10TP/BNC/AUI port
messages and not sending anything out. Commenting out the changes makes it
work again, so that's where the problem lies. Anybody with a 21041 cares
to check 2.0.24 to see if it works?
As a side comment, 2.1.6 does _not_ touch tulip.c, so it works "out of the
box" on my machine. Hmm... 2.0.24 "stable" does not work, 2.1.6 "alpha"
works fine... do I smell something fishy here? :)
Oh, and one more thing (this applies to all kernels in the 2.0 and 2.1
series): the module part of the tulip.c expects the card to use a
predefined I/O base address (0xf800 on a PC), which is not always the
case. My card, for example, uses 0xec80. I have a patch that addresses
this problems - if anybody is interested, drop me a line and I'll post it.
Ionut
--
Ionut Badulescu - Columbia College '98 E-mail:ib42@columbia.edu
Phone: (212)853-7875 Snail mail: 4A4 Wallach Hall
Fax: (212)695-5560 1116 Amsterdam Ave
PGP key available on request New York, NY 10027
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.