collisions 200% of Tx on 10BaseT (21140, .90q, Samsung SC1200-TX)

[Monty]

>> Any ideas?  Do I try yet *another* tulip?
>
>PLEASE check /proc/net/dev first.  your ifconfig might simply
>be out-of-date.  it's horrible when people blame tulip clones,
>juse because there were faults in the _driver_ in the past...

Apologies for not providing 100% of the details.  The numbers from
/proc/net/dev match ifconfig (I did check that) and all my hubs light
up solid with collisions as a physical manifestation of the problem

>> SnotFish:/usr/src# /sbin/ifconfig eth0
>> eth0      Link encap:Ethernet  HWaddr 00:40:05:A5:0E:B3  
>>           inet addr:10.0.0.1  Bcast:10.255.255.255  Mask:255.0.0.0
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:150237 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:30221 errors:0 dropped:0 overruns:0 carrier:0
>>           Collisions:53584 <----(low actually; I was also uploading, 
>>                                which does not cause collisions)
>>           Interrupt:12 Base address:0xfc00 
>
>excellent sign that ifconfig is broken.

Unfortunately this is not the case here.  Other 10baseT hardware
in the same machine does not exhibit the collision behavior.  I'd just
rather be running a Tulip (as I plan to go 100baseTx in the future)
even if a 3c509 already works properly but I have to play with the
Tulip some.

I'm beginning to think the transmitter in this card may just be woogie.

Thanks for the stab in my direction ;-)  Nice to know folks are listening.

Monty