[tulip] still trying

[Donald Becker]

On Tue, 11 Dec 2001, Marinho Barcellos wrote:

> I'm still trying to get the Conexant nic to work. Last time
> Donald Becker said:
> 
> > You must be running a full duplex link -- the Conexant chip reports
> > every transmit packet as a carrier error in full duplex mode.
> 	and later
> > To set the link to a specific speed and duplex, use the transceiver
> > setting described at
> >    http://www.scyld.com/network/tulip.html
> 
> Now I tried all possible medias, run tulip-diag and ifconfig and noted down
> the most relevant info. In brief:

What driver version are you using?
What is the detection message?
What does 'mii-diag' report?

> options=0,0	autoselect (default to 10baseT): errors=carrier>0,rx>0,tx=0



> options=9,9	MII 10baseT:errors=carrier=rx=tx=0 (Tx processing setup info)
> options=11,11	MII autoselect:errors=carrier=rx=tx=0 (Tx processing setup info)
> options=12,12	Serial 10baseT (no autosel):carrier=2*errors,errors>0,tx=rx=0
> options=13,13	MII 100baseTx: errors=carrier=rx=tx=0 (Tx processing setup info)
> options=15,15	MII 100baseT4: errors=carrier=rx=tx=0 (Tx processing setup info)

The "processing setup information" likely means that you are using a
driver that hasn't correctly initialized the chip.

>  MII PHY #1 transceiver registers:
>    2000 780d 0022 1720 0080 0000 0005 2001
>    2000 780d 0022 1720 0080 0000 0005 2001
>    2000 780d 0022 1720 0080 0000 0005 2001
>    0000 0000 0000 0000 01e1 2001 0000 8c08.
>  Basic mode control register 0x2000: Auto-negotiation disabled!
>    Speed fixed at 100 mbps, half-duplex.

This is the expected output when the speed and duplex are forced.

> I guess it should work with options=3 (100baseTx)

That sets the chip for a SYM transceiver.  It has an on-chip MII
transceiver.

> and, for 0 (autonegotiation):
> 
> tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
>  http://www.scyld.com/diag/index.html
> Index #1: Found a Conexant LANfinity adapter at 0x1400.
>  Port selection is MII, full-duplex.
>  Transmit started, Receive started, full-duplex.
>   The Rx process state is 'Waiting for packets'.
>   The Tx process state is 'Idle'.
>   The transmit threshold is 128.

This looks normal.


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