[tulip] 21143 refuses full-duplex

[Pfenniger Daniel]

This is a multi-part message in MIME format.

--Boundary_(ID_BxjhQNIEKZ/SAIObkNV5GQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit

I have a series of 21140 (Lantronix) and 21143-PD cards (unknown origin). 
The 21140's understand the full duplex option but not the 21143. 

I understand that Don's latest tulip driver is more up-to-date about the 
21143 chip, but it doesn't compile in the 2.2.18 kernel, or I don't
know how to do it correctly.
(In the 2.4.0 kernel the tulip driver is split into several files.) 

What tulip-diag -ee and -mm say about the second card is joined below.

The modules.conf files has the following lines: 

alias eth0 tulip
alias eth1 tulip
options tulip full_duplex=1,1

Any clue?  I cannot retrograde to a too old kernel because the bonding 
driver for which the second card is intended doesn't work then

	Daniel

--Boundary_(ID_BxjhQNIEKZ/SAIObkNV5GQ)
Content-type: text/plain; name=tulip-diag-ee; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline; filename=tulip-diag-ee

  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 f394
  0000 0000 0000 0000 b51c 0bc9 0040 0000
  0000 0000 0000 0000 0000 0000 0000 00be
 ID block CRC 0xc5 (vs. 0xc5).
  Full contents CRC 0x263a (read as 0x00be).
 MII PHY found at address 5, status 0x782d.
  Internal autonegotiation state is 'Autonegotiation disabled'.

--Boundary_(ID_BxjhQNIEKZ/SAIObkNV5GQ)
Content-type: text/plain; name=tulip-diag-mm; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline; filename=tulip-diag-mm

 Link partner capability is 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Negotiation  completed.
  Internal autonegotiation state is 'Autonegotiation disabled'.

--Boundary_(ID_BxjhQNIEKZ/SAIObkNV5GQ)--