bellis wrote:
>
> ...
> but initially I had 2
> 3c905B "Cyclone" eth cards configured and everything would work for a bit
> but eventually both cards would hang:
> eth1: transmit timed out, tx_status 00 status e000.
Oh spit. Not that one again.
I've been working this driver hard for the past couple of weeks.
Fingers crossed, these problems are now ironed out.
Could you please try today's version?
http://www.uow.edu.au/~andrewm/3c59x.c-2.2
There is a (now incomplete) list of changes at
http://www.uow.edu.au/~andrewm/linux/16-apr-00-ann.txt
> This is using the default 3c59x driver. I then downloaded the 3c90x
> driver from 3com, rebuilt the kernel without the 3c59x driver, build the
> 3c90x driver as a module, insmod etc, and the system would hard lock
> shortly after inserting the module, power off (unplug machine) required to
> reboot.
hmm.. This is the first problem report I've seen for 3com's driver. It
is a very different piece of software. Sounds like it's OK with a
single NIC.
> Next I have removed one of the 3com cards, put in an intel ether
> express Pro 10/100, recompiled the kernel for eepro and 3c59x support.
> Everything seems to work ok, but I'm getting alot of
>
> Apr 19 11:31:42 proxy2 kernel: br0: retransmitting tcn bpdu
Can't help on this one.
--
-akpm-
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
