[vortex] 3com 3c59x problems with Fedora2
Mladen Martinčević
martincevic_m at yahoo.com
Tue Aug 30 00:21:04 PDT 2005
Hi to all.
Maybe this will look strange, because lots of posts
about this similiar problem. But no solutions for now
works for me.
Situation:
Fedora 2 with 2.6.5 kernel
three 3com nics :
03:02.0 Ethernet controller: 3Com Corporation
3c905C-TX/TX-M [Tornado] (rev 78)
03:03.0 Ethernet controller: 3Com Corporation
3c905C-TX/TX-M [Tornado] (rev 78)
04:02.0 Ethernet controller: 3Com Corporation
3c905C-TX/TX-M [Tornado] (rev 78)
Two of those nic-s eth0, eth1 are connected on local
network. the third one eth2 is connected to Cisco
router wich is direct link to internet :)
Problems with eth2 are similiar to previously problems
:
Aug 30 09:25:07 chaos1 kernel: eth2: Transmit error,
Tx status register 82.
Aug 30 09:25:07 chaos1 kernel: Probably a duplex
mismatch. See Documentation/networking/vortex.txt
Aug 30 09:25:07 chaos1 kernel: Flags; bus-master 1,
dirty 125449(9) current 125449(9)
Aug 30 09:25:07 chaos1 kernel: Transmit list
00000000 vs. 5f6ea7a0.
Aug 30 09:25:07 chaos1 kernel: 0: @5f6ea200 length
800001ce status 000101ce
Aug 30 09:25:07 chaos1 kernel: 1: @5f6ea2a0 length
8000005a status 0001005a
Aug 30 09:25:07 chaos1 kernel: 2: @5f6ea340 length
80000036 status 00010036
Aug 30 09:25:07 chaos1 kernel: 3: @5f6ea3e0 length
800005ea status 000105ea
Aug 30 09:25:07 chaos1 kernel: 4: @5f6ea480 length
800000be status 000100be
Aug 30 09:25:07 chaos1 kernel: 5: @5f6ea520 length
800005ea status 000105ea
Aug 30 09:25:07 chaos1 kernel: 6: @5f6ea5c0 length
80000036 status 00010036
Aug 30 09:25:07 chaos1 kernel: 7: @5f6ea660 length
800005ea status 000105ea
Aug 30 09:25:07 chaos1 kernel: 8: @5f6ea700 length
8000006e status 8001006e
Aug 30 09:25:07 chaos1 kernel: 9: @5f6ea7a0 length
80000036 status 00010036
Aug 30 09:25:07 chaos1 kernel: 10: @5f6ea840 length
80000036 status 00010036
Aug 30 09:25:07 chaos1 kernel: 11: @5f6ea8e0 length
80000036 status 00010036
Aug 30 09:25:07 chaos1 kernel: 12: @5f6ea980 length
80000082 status 00010082
Aug 30 09:25:07 chaos1 kernel: 13: @5f6eaa20 length
8000019a status 0001019a
Aug 30 09:25:07 chaos1 kernel: 14: @5f6eaac0 length
8000005a status 0001005a
Aug 30 09:25:07 chaos1 kernel: 15: @5f6eab60 length
80000036 status 00010036
mii-tool :
eth0: negotiated 100baseTx-FD flow-control, link ok
eth1: negotiated 100baseTx-FD flow-control, link ok
eth2: no autonegotiation, 10baseT-HD, link ok
mii-tool -v :
eth2: no autonegotiation, 10baseT-HD, link ok
product info: vendor 00:10:5a, model 0 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD
10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD
10baseT-HD flow-control
link partner: 10baseT-HD
I dont know if autonegoitation is problem or maybe the
cisco router is working on half-duplex wich is
confusing my NIC.
I also tryed loading options in /etc/modprobe.conf
alias eth2 3c59x options=0x203
or just forsing full-duplex but none of thees
solutions worked for me.
Maybe to change all nics? :)
If someone can help me solving this problem!
Thanks
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
More information about the vortex
mailing list