[vortex] Problems forcing a 3c905 card's media type

[Shane Wegner]

On Mon, Aug 21, 2000 at 09:36:10PM +0200, Bogdan Costescu wrote:
> 
> On Mon, 21 Aug 2000, Shane Wegner wrote:
> 
> > Hi,
> > 
> > I am using Linux 2.2.17pre13 and am having some trouble forcing the media
> > type.  There seems to be conflicting documentation on this point.  One
> > source says options=12 should set to 100basetx full duplex.  Another says
> > options=8 full_duplex=1 is correct.  In any case, the mii-diag program still
> 
> Can you please specify which are the 2 docs that say these ?

Well linux/Documentation/networking/vortex.txt doesn't even mention the
full_duplex option.  It indicated options=12 is correct.  However,
http://www.scyld.com/network/vortex.html does mention the full_duplex option
and recommends using it.

> 
> > insists I'm in 10baset mode and indeed it's not transmiting at 100mbps.
> 
> options=8 full_duplex=1 should work. Can you send us the output from
> vortex-diag -v ?

I was going by vortex-diag -a but here are both.

continuum:~# insmod 3c59x options=8 full_duplex=1
Using /lib/modules/2.2.17pre13/net/3c59x.o
continuum:~# dmest |tail -5
su: dmest: command not found
continuum:~# dmesg |tail -5
3c59x.c:v0.99H 24Jun00 Donald Becker and others
http://www.scyld.com/network/vortex.html
eth0: 3Com 3c905B Cyclone 100baseTx at 0xd400,  00:10:5a:80:35:3c, IRQ 11
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  Media override to transceiver type 0 (10baseT).
  Enabling bus-master transmits and whole-frame receives.
continuum:~# ~shane/bin/vortex-diag -v
vortex-diag.c:v2.02 7/1/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a 3c905B Cyclone 100baseTx adapter at 0xd400.
 Indication enable is 0000, interrupt enable is 0000.
 No interrupt sources are pending.
 Transceiver/media interfaces available:  100baseTx 10baseT.
Transceiver type in use:  Autonegotiate.
 MAC settings: half-duplex.
 Station address set to 00:10:5a:80:35:3c.
 Configuration options 000a.
Parsing the EEPROM of a 3Com Vortex/Boomerang:
 3Com Node Address 00:10:5A:80:35:3C (used as a unique ID only).
 OEM Station address 00:10:5A:80:35:3C (used as the ethernet address).
 Manufacture date (MM/DD/YYYY) 7/21/1999, division 6, product QP.
Options: none.
  Vortex format checksum is incorrect (0087 vs. 10b7).
  Cyclone format checksum is correct (0xef vs. 0xef).
  Hurricane format checksum is correct (0xef vs. 0xef).
 MII PHY found at address 1, status 3000.
 MII PHY found at address 2, status 3000.
 MII PHY found at address 3, status 3000.
 MII PHY found at address 4, status 3000.
 MII PHY 0 at #1 transceiver registers:
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000.
 MII PHY 1 at #2 transceiver registers:
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000.
 MII PHY 2 at #3 transceiver registers:
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000.
 MII PHY 3 at #4 transceiver registers:
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000
   3000 3000 3000 3000 3000 3000 3000 3000.
 Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
  or '-m' or '-mm' to show MII management registers.

> Anyway, do you really need to force 100baseTx FD ? If the partner supports
> it, the driver should set it without any command line options through
> autonegotiation "magic".

I thought the same thing and it's kind of a long story.  To summarize. 
Bought switch performed half as well as hub (dlink dss8+ 10/100mbps btw). 
Called tech support and there explanation was that 3com's cards didn't do
autonegotiation correctly.  Forcing all cards to 100mbps full duplex should
solve the problem.  Whether this is correct or not I don't know but I'd like
to give them the benefit of the doubt.

Cheers,
Shane


> 
> Sincerely,
> 
> Bogdan Costescu
> 
> IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
> Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
> Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
> E-mail: Bogdan.Costescu@IWR.Uni-Heidelberg.De

-- 
Shane Wegner: shane@cm.nu
Personal website: http://www.cm.nu/~shane/