I Lee Hetherington wrote:
>
> Andrew Morton wrote:
>
> > Please do. The boot-time messages which come out of the driver
> > would be interesting. It would help if you add `debug=7' to
> > the 3c59x modprobe command line also.
>
> OK. I've included dmesg output due to modprobe with debug=7 followed by ifup
> (using pump -- problems persist with static IP as well), cat /proc/interrupts
> showing no eth0, and ifconfig eth0.
OK, that's wierd. Why on earth isn't it showing up in
/proc/interrupts? It's certainly generating Tx interrupts,
and the ISR is being called.
Is this a new NIC? 3Com have just started shipping a
new flavour of the 905c, the 3c905CX. With this device
the RxReset command takes tens of milliseconds to complete,
not tens of microseconds like all the others. This
breaks the driver. You end up being able to transmit but
not receive.
And the old media interface selection algorithms don't work
right with the 3c905CX either. We only got this sorted
a few days ago and we missed the 2.4.0 boat :(
Could you please test this 2.2 driver?
http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.2.19-pre2-2.gz
Thanks.
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 07 2001 - 21:00:22 EST