Re: 3c595 Vortex problems - no 100mbps, no full-duplex

On Sat, 17 Aug 2002, Kevin wrote:

> 	I loooked through the list archives and found were people were having
> similar problems

What similar problems were people having?  Do you have a message URL?

> I have a 3c595 Vortex
> card that just won't run 100/full-duplex.

What options are you passing?

> I have the 3c59xcfg utility from
> 3com and have tried configuring the card at 100/full and to auto-nego

Errrmmm, the latter is unlikely: the 3c595 does not support
autonegotiation.  The 3c595 is old: it predates autonegotiation.

Also, since it was one of the very first PCI adapters, it's performance
is not very good by modern standards.  You will see high CPU loading.

> I've also tried loading the module forcing
> 100/full, but that doesn't work either.

It should...

> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:0b.0: 3Com PCI 3c595 Vortex 100baseTx at 0xc400. Vers LK1.1.16

Yes, this is an old 3c595.

> 00:0b.0: Overriding PCI latency timer (CFLT) setting of 32, new value is
> 248.

This is required to work around a bug in the chip.

> 00:0b.0:  Media override to transceiver type 4 (100baseTX).

This should set the speed to 100baseTx, regardless if the link partner.

> ./mii-diag eth1:
> Basic registers of MII PHY #0:  0000 ffff 0000 ffff 0000 ffff 0000 ffff.

This won't return useful information: that driver version does not
emulate MII management registers.

[[ If you are willing to try an experimental change, I've added MII
   emulation to the 0.99Xe driver
      ftp://ftp.scyld.com/pub/network/test/3c59x.c
 ]]

> ./vortex-diag -a eth1:
> 
> vortex-diag.c:v2.06 4/18/2002 Donald Becker ([email protected])
>  http://www.scyld.com/diag/index.html
> Index #1: Found a 3Com 3c595 Vortex 10/100baseTx adapter at 0xc400.
> The Vortex chip may be active, so FIFO registers will not be read.
...
>  Indication enable is 0000, interrupt enable is 0000.
...
>  Transceiver/media interfaces available:  100baseTx 10baseT.
> Transceiver type in use:  10baseT.
>  MAC settings: half-duplex.


The card isn't running and is at the default setting: has the driver
been loaded? 

> ./vortex-diag -e eth1:
...
> Saved EEPROM settings of a 3Com Vortex/Boomerang:
...
>  Options: negotiated duplex, link beat required.

The card isn't set to force the media type.

> when loading the module with debug=9 I get in messages:
...
> Aug 17 10:09:52 zee kernel:   64K word-wide RAM 1:1 Rx:Tx split,
> autoselect/10baseT interface.

Nope, no forced media type.

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993

_______________________________________________
vortex mailing list
[email protected]
http://www.scyld.com/mailman/listinfo/vortex