[vortex] Problems with auto-negotiation with 3c905
=?iso-8859-1?Q?Leonardo_Rodrigues_Magalh=E3es?=
coelho@persogo.com.br
Thu, 17 May 2001 15:03:33 -0300
This is a multi-part message in MIME format.
------=_NextPart_000_001B_01C0DEE2.8AE0B010
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello Guys,
I got a running Linux Server ( Redhat 6.2 with kernel 2.2.19, 3c59x =
driver version "3c59x.c 18Feb01" - the one that cames with kernel ) with =
two 3c905B ( Cyclone ) cards. I'm having a problem that seems related to =
auto-negotiating with my 3Com 10/100 hub.
With no extra configuration ( i mean, enabling auto-negotiating on =
both boards ), I got the following:
eth0: Initial media type Autonegotiate.
eth0: MII #24 status 786d, link partner capability 40a1, setting =
half-duplex.
eth1: Initial media type Autonegotiate.
eth1: MII #24 status 786d, link partner capability 0020, setting =
half-duplex.
Eth0 is connected to 3Com hub, and eth1 is connected to a Cisco 805 =
router ( cross over cable, no hub ). According to the page =
http://www.scyld.com/diag/mii-status.html#lpar, I can conclude that eth1 =
is negotiating 10BaseT and half-duplex with the Cisco Router. That's OK =
and acceptable. Unfortunelly I couldn't understand what link partner =
capability 40a1 from eth0 means. According to the same page, status =
0x4000 would mean 'Link partner got our advertised abilities'. =
Unfortunely I can't understand what this means .... Would it mean 'We =
sent autonegotiation information to the hub, but no responde received' =
?????
Well, you should be asking ..... what's the problem anyway ?? The =
problem is that letting eth0 get autonegotiation, it works poorly. I got =
35% of packet loss pinging a local machine, running on the same hub ( =
network traffic is very low, no collision problems here ). All the =
others machine on the network works very well, so I don't know if I =
would be right on blaming the hub. Letting eth1 on autonegotiation, and =
using 10BaseT negotiated with the Router, eth1 seems to work perfeclty =
fine.
Altough, eth0 just works when I use:
options 3c59x options=3D0
on /etc/conf.modules, 'forcing' eth0 at 10BaseT.
Question ...... can this be somehow a board problem ?? Can this be =
somehow a hub problem ??? I need some advices ...
Some more informations ...... ( cat /proc/pci )
Bus 0, device 10, function 0:
Ethernet controller: 3Com 3C905B 100bTX (rev 48).
Medium devsel. IRQ 12. Master Capable. Latency=3D32. Min =
Gnt=3D10.Max Lat=3D10.
I/O at 0x9000 [0x9001].
Non-prefetchable 32 bit memory at 0xde800000 [0xde800000].
Bus 0, device 11, function 0:
Ethernet controller: 3Com 3C905B 100bTX (rev 48).
Medium devsel. IRQ 10. Master Capable. Latency=3D32. Min =
Gnt=3D10.Max Lat=3D10.
I/O at 0x8800 [0x8801].
Non-prefetchable 32 bit memory at 0xde000000 [0xde000000].
Hope hearing from you soon,
Leonardo Rodrigues
Persocom Network
------=_NextPart_000_001B_01C0DEE2.8AE0B010
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Hello =
Guys,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> I got a running =
Linux Server (=20
Redhat 6.2 with kernel 2.2.19, 3c59x driver version "3c59x.c 18Feb01" - =
the one=20
that cames with kernel ) with two 3c905B ( Cyclone ) cards. I'm having a =
problem=20
that seems related to auto-negotiating with my 3Com 10/100 =
hub.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> With no =
extra configuration=20
( i mean, enabling auto-negotiating on both boards ), I got the=20
following:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>eth0: Initial media type =
Autonegotiate.<BR>eth0:=20
MII #24 status 786d, link partner capability 40a1, setting=20
half-duplex.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>eth1: Initial media type =
Autonegotiate.<BR>eth1:=20
MII #24 status 786d, link partner capability 0020, setting=20
half-duplex.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2> Eth0 is =
connected to 3Com=20
hub, and eth1 is connected to a Cisco 805 router ( cross over cable, no =
hub ).=20
According to the page </FONT><A=20
href=3D"http://www.scyld.com/diag/mii-status.html#lpar"><FONT=20
size=3D2>http://www.scyld.com/diag/mii-status.html#lpar</FONT></A><FONT =
size=3D2>, I=20
can conclude that eth1 is negotiating 10BaseT and half-duplex with the =
Cisco=20
Router. That's OK and acceptable. Unfortunelly I couldn't understand =
what link=20
partner capability 40a1 from eth0 means. According to the same page, =
status=20
0x4000 would mean 'Link partner got our advertised abilities'. =
Unfortunely I=20
can't understand what this means .... Would it mean 'We sent =
autonegotiation=20
information to the hub, but no responde =
received' ?????</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Well, you should be =
asking .....=20
what's the problem anyway ?? The problem is that letting eth0 get=20
autonegotiation, it works poorly. I got 35% of packet loss pinging a =
local=20
machine, running on the same hub ( network traffic is very low, no =
collision=20
problems here ). All the others machine on the network works very =
well, so=20
I don't know if I would be right on blaming the hub. </FONT><FONT =
face=3DArial=20
size=3D2>Letting eth1 on autonegotiation, and using 10BaseT negotiated =
with the=20
Router, eth1 seems to work perfeclty fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Altough, eth0 just =
works when I=20
use:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>options 3c59x options=3D0</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> on =
/etc/conf.modules, 'forcing'=20
eth0 at 10BaseT.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Question ...... can =
this be=20
somehow a board problem ?? Can this be somehow a hub problem ??? I need =
some=20
advices ...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Some more =
informations ...... (=20
cat /proc/pci )</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Bus 0, device 10, =
function =20
0:<BR> Ethernet controller: 3Com 3C905B 100bTX (rev=20
48).<BR> Medium devsel. IRQ =
12. Master=20
Capable. Latency=3D32. Min Gnt=3D10.Max=20
Lat=3D10.<BR> I/O at 0x9000=20
[0x9001].<BR> Non-prefetchable 32 bit =
memory at=20
0xde800000 [0xde800000].</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR> Bus 0, device =
11,=20
function 0:<BR> Ethernet controller: 3Com 3C905B =
100bTX=20
(rev 48).<BR> Medium devsel. IRQ =
10. =20
Master Capable. Latency=3D32. Min Gnt=3D10.Max=20
Lat=3D10.<BR> I/O at 0x8800=20
[0x8801].<BR> Non-prefetchable 32 bit =
memory at=20
0xde000000 [0xde000000].</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><BR> Hope hearing =
from you=20
soon,<BR> Leonardo Rodrigues<BR> =
Persocom=20
Network<BR></FONT></DIV></BODY></HTML>
------=_NextPart_000_001B_01C0DEE2.8AE0B010--