My mistake on the subject line, the card is physically marked as a
3c905C, the system is treating it as a 3c59x which I believe is correct
after reading through the docs regarding the driver.
There were some comments about possibly the ethernet port being bad. I
dropped an Intel Pro 100 card in the machine, used the same port, same
cable and it came up as 100 full. Also to avoid the duplex/speed
negotiation I forced the switch (Cisco Catalyst 2924XL) to 100 full with
the 3com card, when I did this the 3com card didn't talk at all.
There are no errors in /var/log/messages relating to a failure of the
card, only messages are what I would call standard startup messages with
one exception. There are messages in the log from when I attempted to
use mii-tool. The messages are:
Dec 18 17:57:21 xyzzy1 kernel: 3c59x: Unknown symbol mii_ethtool_sset
Dec 18 17:57:21 xyzzy1 kernel: 3c59x: Unknown symbol mii_link_ok
Dec 18 17:57:21 xyzzy1 kernel: 3c59x: Unknown symbol mii_nway_restart
Dec 18 17:57:21 xyzzy1 kernel: 3c59x: Unknown symbol generic_mii_ioctl
Dec 18 17:57:21 xyzzy1 kernel: 3c59x: Unknown symbol mii_ethtool_gset
I wouldn't be surprised if its a bad or flaky network card,
unfortunately I don't have a Windoze machine that I can put it in to
test it.
TIA, Jeff
Jeffrey Ross wrote:
[snip]
00:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
(rev 6c)
Is the card physically marked 3c905B, but being detected as a 3c905C?
The 3c905B's used to have a problem with Kudzu (it's in bugzilla if you
search for 3c59x). IIRC it would leave traces in /var/log/messages. In
any case you can try disabling kudzu and rebooting to see if that fixes
it.
