[vortex] Twofold problem with setting up 3Com PCI 3c900 Cyclone ... continued 10Mbps TPO in RedHat 6.1 system, updated to kernel 2.4.X.]

Martijn Ras martijn.ras@cable4u.nl
Wed, 20 Jun 2001 18:53:46 -0400


Heya Andrew,

Have been abroad for work most of the past few weeks so haven't had time 
to look into the problem and get the output you asked for.
Here it is, hope it's enough for you to make some sense, let me know if
you need any other info.

Rudy Zijlstra recommended using the latest DHCP client software, i
updated the DHCPClient but still have the same problem.
[root@PiAlpha  /root]# dhcpcd -? => DHCP Client
Daemon v.1.3 (latest version)
[root@PiAlpha  /root]# dhclient -? => Internet
Software Consortium DHCP Client V3.0b2pl11

ifconfig doesn't indicate any frames being received.

This is what tcpdump shows running PUMP (which ends saying Operation
failed.):
[root@PiAlpha  /root]# tcpdump
User level filter, protocol ALL, datagram packet socket
tcpdump: listening on all devices
13:42:50.994472 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x69d9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)
13:42:53.989242 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x69d9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)
13:42:59.989042 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x69d9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)
13:43:10.989043 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x69d9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)
13:43:20.990765 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x4bd9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)
13:43:23.989223 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x4bd9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)
13:43:28.989080 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x4bd9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)
13:43:37.989041 eth0 > 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x4bd9dc26 ether 0:50:da:e2:f3:c6 [|bootp] (DF)


This is what tcpdump shows when running DHCPCD:
[root@PiAlpha  /root]# tcpdump
User level filter, protocol ALL, datagram packet socket
tcpdump: listening on all devices
13:38:23.446338 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C) len=572
af8f 0000 4011 c91e 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000
13:38:23.779056 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C) len=572
af90 0000 4011 c91d 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000
13:38:24.499041 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C)
len=572
af91 0000 4011 c91c 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000
13:38:26.139085 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C)
len=572
af92 0000 4011 c91b 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000
13:38:29.379048 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C)
len=572
af93 0000 4011 c91a 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000
13:38:35.699050 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C)
len=572
af94 0000 4011 c919 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000
13:38:48.449043 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C)
len=572
af95 0000 4011 c918 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000
13:39:14.069044 eth0 > 0:0:0:0:0:0 null > 0:50:da:e2:f3:c6 sap 45 I
(s=1,r=32,C)
len=572
af96 0000 4011 c917 0000 0000 ffff ffff
0044 0043 022c 5d30 0101 0600 ef52 2252
0005 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 dae2 f3c6 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000


Here's the output of vortex-diag when the card is up and running under
kernel 2.2.16:
vortex-diag.c:v2.05 5/15/2001 Donald Becker (becker@scyld.com
)
http://www.scyld.com/diag/index.html
Index #1: Found a 3c900 Cyclone 10Mbps TPO adapter at 0xa400.
Initial window 7, registers values by window:
Window 0: 0000 0000 0000 0000 fdfd 00bf 0000 0000.
Window 1: 0000 0000 0000 0000 0000 0000 0000 2000.
Window 2: 5000 e2da c6f3 0000 0000 0000 0022 4000.
Window 3: 0000 0100 05ea 0000 0008 0800 0800 6000.
Window 4: 0000 00d0 0000 0cc8 0001 8cc0 0000 8000.
Window 5: 1ffc 0000 0000 0600 0807 06de 06c6 a000.
Window 6: 0000 0000 0000 1f00 0000 0744 0000 c000.
Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xa400
0xA410: 00000000 00000000 00000010 00000000
0xA420: 00000020 00000000 00080000 00000004
0xA430: 00000000 7e5381ad 0f5920a0 00080004
Indication enable is 06c6, interrupt enable is 06de.
No interrupt sources are pending.
Transceiver/media interfaces available: 10baseT.
Transceiver type in use: 10baseT.
MAC settings: half-duplex.
Station address set to 00:50:da:e2:f3:c6.
Configuration options 0022.
EEPROM contents (64 words, offset 0):
0x000: 0050 dae2 f3c6 9004 0036 0036 5157 6d50
0x008: c171 0000 0050 dae2 f3c6 0010 0000 0006
0x010: 22a2 0000 0000 0180 0000 0000 0000 10b7
0x018: 9004 0008 0000 0000 0000 0000 0000 0000
0x020: 0033 0000 0000 0000 0000 0000 0000 0000
0x028: 0000 0000 0000 0000 0000 0000 0000 0000
0x030: 0000 0000 0000 0000 0000 0000 0000 0000
0x038: 0000 0000 0000 0000 0000 0000 0000 0000
The word-wide EEPROM checksum is 0x73a6.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
3Com Node Address 00:50:DA:E2:F3:C6 (used as a unique ID only).
OEM Station address 00:50:DA:E2:F3:C6 (used as the ethernet address).
Manufacture date (MM/DD/YYYY) 1/22/2000, division 6, product WQ.
Options: negotiated duplex, link beat required.
Vortex format checksum is incorrect (0008 vs. 10b7).
Cyclone format checksum is correct (0x33 vs. 0x33).
Hurricane format checksum is correct (0x33 vs. 0x33).


Here's the output of vortex-diag when the card is malfunctioning under
kernel 2.4.4:
vortex-diag.c:v2.05 5/15/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a 3c900 Cyclone 10Mbps TPO adapter at 0xa400.
Initial window 7, registers values by window:
Window 0: 0000 0000 0000 0000 fdfd 00bf 0000 0000.
Window 1: 0000 0000 0000 0000 0000 0000 0000 2000.
Window 2: 5000 e2da c6f3 0000 0000 0000 0022 4000.
Window 3: 0000 0180 05ea 0000 0008 0800 0800 6000.
Window 4: 0000 00d0 8000 0048 0001 8880 0000 8000.
Window 5: 1ffc 0000 0000 0600 0807 0000 06c6 a000.
Window 6: 0000 0000 0000 0000 0000 0000 0000 c000.
Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xa400
0xA410: 00000000 00000000 00000055 00000000
0xA420: 00000020 00000000 00080000 00000004
0xA430: 00000000 32cacd36 00000000 00080004
Indication enable is 06c6, interrupt enable is 0000.
No interrupt sources are pending.
Transceiver/media interfaces available: 10baseT.
Transceiver type in use: Autonegotiate.
MAC settings: half-duplex.
Station address set to 00:50:da:e2:f3:c6.
Configuration options 0022.
EEPROM contents (64 words, offset 0):
0x000: 0050 dae2 f3c6 9004 0036 0036 5157 6d50
0x008: c171 0000 0050 dae2 f3c6 0010 0000 0006
0x010: 22a2 0000 0000 0180 0000 0000 0000 10b7
0x018: 9004 0008 0000 0000 0000 0000 0000 0000
0x020: 0033 0000 0000 0000 0000 0000 0000 0000
0x028: 0000 0000 0000 0000 0000 0000 0000 0000
0x030: 0000 0000 0000 0000 0000 0000 0000 0000
0x038: 0000 0000 0000 0000 0000 0000 0000 0000
The word-wide EEPROM checksum is 0x73a6.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
3Com Node Address 00:50:DA:E2:F3:C6 (used as a unique ID only).
OEM Station address 00:50:DA:E2:F3:C6 (used as the ethernet address).
Manufacture date (MM/DD/YYYY) 1/22/2000, division 6, product WQ.
Options: negotiated duplex, link beat required.
Vortex format checksum is incorrect (0008 vs. 10b7).
Cyclone format checksum is correct (0x33 vs. 0x33).
Hurricane format checksum is correct (0x33 vs. 0x33).


Here's the output of mii-diag when the card is up and running under
kernel 2.2.16:
mii-diag.c:v2.02 5/21/2001 Donald Becker (becker@scyld.com
)
http://www.scyld.com/diag/index.html
Using the default interface 'eth0'.
Basic mode control register 0x0100: Auto-negotiation disabled, with
Speed fixed at 10 mbps, full-duplex.
Basic mode status register 0x1809 ... 180d.
Link status: previously broken, but now reestablished.
This transceiver is capable of 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation not complete.
Your link partner is generating 10baseT link beat (no autonegotiation).
End of basic transceiver informaion.

MII PHY #24 transceiver registers:
0100 180d 0000 0000 0061 0020 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000


Here's the output of mii-diag when the card is malfunctioning under
kernel 2.4.4:
mii-diag.c:v2.02 5/21/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Using the default interface 'eth0'.
Basic mode control register 0x1100: Auto-negotiation enabled.
You have link beat, and everything is working OK.
This transceiver is capable of 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation complete.
Your link partner is generating 10baseT link beat (no autonegotiation).
End of basic transceiver informaion.

MII PHY #24 transceiver registers:
1100 182d 0000 0000 0061 0020 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000

Mazzel,

Martijn.