> Does it work reliably with 2.0.30? All of the time outs and
> problem reports I have seen wrt. 2.0.30 have been with the v0.30
> 3c59x driver.
Um, I don't know, actually. I'm still using 2.0.29 because I rely
on AFS and Derek Atkins doesn't want to rebuild the module for
2.0.30.
I can't wait until CODA takes over the world...
(He's testing a Linux patch which may fix some cache
corruption problems we've been seeing, and which he intends to
submit towards 2.0.31 if all goes well.)
I _do_ know that version 0.40 of the driver does not send any
packets on my system.
So, because v0.30 is the only version of the driver which works for
you under 2.0.29 I should hold out on putting v0.40 into 2.0.31 until
you find out why it doesn't work on your 2.0.29 system? If you're not
willing to find out what the situation is with a 2.0.30 kernel, I'm
going to put v0.40 into my patch sets for 2.0.31 since that is what
all the stunning success reports for 2.0.30 are for, and that is what
I must work on, reports from people using the driver under 2.0.30.
Don't like it, bite me... %-)
---------------------------------------------////
Yow! 11.26 MB/s remote host TCP bandwidth & ////
199 usec remote TCP latency over 100Mb/s ////
ethernet. Beat that! ////
-----------------------------------------////__________ o
David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><