[tulip] link mode problems

[Pasi Kärkkäinen]

Hello!

I have the following cards:

Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001)
PCI: Found IRQ 5 for device 00:09.0
PCI: Sharing IRQ 5 with 00:04.2
tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block
tulip0:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2)
tulip0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block
tulip0:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) b
eth1: Digital DS21143 Tulip rev 65 at 0xb000, 00:C0:CA:20:3C:A5, IRQ 5.

PCI: Found IRQ 10 for device 00:0b.0
tulip1:  EEPROM default media type Autosense.
tulip1:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block
tulip1:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2)
tulip1:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block
tulip1:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block
eth2: Digital DS21143 Tulip rev 65 at 0xa400, 00:C0:CA:13:10:04, IRQ 10.


And I'm using Linux 2.4.18.

Now, the problem:

eth1 is connected with cat5 cable to 10Mbps HUB. card fails to autodetect
and set 10Mbps halfduplex.. :

Basic registers of MII PHY #32:  1000 7848 0000 0000 0061 0000 0000 0000.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x7848 ... 7848.
   Link status: not established.
   End of basic transceiver informaion.


eth2 is connected with twisted cat5 cable to another tulip-card (also
running autosensing). This link is autosensed as:

Basic registers of MII PHY #32:  1000 784c 0000 0000 0041 41e1 0000 0000.
 The autonegotiated capability is 0040.
The autonegotiated media type is 10baseT-FD.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver informaion.


Why eth1 fails to establish connection with HUB (no link in the hub either)?
Why eth2 doesn't autosense 100Mbps Fullduplex?


Anything I should try?


- Pasi Kärkkäinen

                                   ^
                                .     .
                                 Linux
                              /    -    \
                             Choice.of.the
                           .Next.Generation.