[vortex] 3cSOHO100-Tx Speed Problem
Mark Lubratt
mark.lubratt@indeq.com
Thu, 30 Nov 2000 09:45:52 -0600
Here is the information you requested.
As I said before, the module is loaded from the initrd file during boot.
The linuxrc file in the ramdrive contains:
insmod aic7xxx
insmod pci-scan
insmod 3c59x
No options were used loading the modules.
The module startup detection message is:
Nov 29 16:23:24 bill-the-cat kernel:
http://www.scyld.com/network/vortex.html
Nov 29 16:23:24 bill-the-cat kernel: eth0: 3Com 3cSOHO100-TX Hurricane at
0xfc00, 00:01:02:c0:9f:8b, IRQ 10
Nov 29 16:23:24 bill-the-cat kernel: 8K byte-wide RAM 5:3 Rx:Tx split,
autoselect/Autonegotiate interface.
Nov 29 16:23:24 bill-the-cat kernel: MII transceiver found at address 24,
status 786d.
Nov 29 16:23:24 bill-the-cat kernel: MII transceiver found at address 0,
status 786d.
Nov 29 16:23:24 bill-the-cat kernel: Enabling bus-master transmits and
whole-frame receives.
At this point, the hub and NIC lights indicate 100Mbs. Then the boot
scripts start up the network (ifcfg-eth0) and the hub and NIC lights drop to
10Mbs.
vortex-diag -v says:
vortex-diag.c:v2.03 9/26/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a 3Com 3cSOHO100-TX adapter at 0xfc00.
Indication enable is 06c6, interrupt enable is 06de.
No interrupt sources are pending.
Transceiver/media interfaces available: 100baseTx 10baseT.
Transceiver type in use: 10baseT.
MAC settings: half-duplex.
Station address set to 00:01:02:c0:9f:8b.
Configuration options 000a.
Parsing the EEPROM of a 3Com Vortex/Boomerang:
3Com Node Address 00:01:02:C0:9F:8B (used as a unique ID only).
OEM Station address 00:01:02:C0:9F:8B (used as the ethernet address).
Manufacture date (MM/DD/YYYY) 8/10/2000, division H, product CJ.
Options: none.
Vortex format checksum is incorrect (003c vs. 10b7).
Cyclone format checksum is correct (0xa1 vs. 0xa1).
Hurricane format checksum is correct (0xa1 vs. 0xa1).
MII PHY found at address 24, status 784d.
MII PHY found at address 0, status 784d.
MII PHY 0 at #24 transceiver registers:
3000 784d 0000 0000 01e1 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
0000 0080 0090 0000 0000 0005 2001 0000
0000 2040 07cf 1c11 0011 1000 0000 0000.
MII PHY 1 at #0 transceiver registers:
3000 784d 0000 0000 01e1 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
0000 0080 0090 0000 0000 0005 2001 0000
0000 2040 07cf 1c11 0011 1000 0000 0000.
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents, -ee for parsed contents,
or '-m' or '-mm' to show MII management registers.
and mii-diag -v says:
mii-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
MII PHY #24 transceiver registers:
3000 784d 0000 0000 01e1 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
0000 0080 0090 0000 0000 0005 2001 0000
0000 2040 07cf 1c11 0011 1000 0000 0000.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD
10baseT.
Able to perform Auto-negotiation, negotiation not complete.
Your link partner does not do autonegotiation, and this transceiver type
does not report the sensed link speed.
at this point, I disabled the network startup scripts and performed a cold
boot (powered off the system).
The module loaded with the same detection method.
Before starting the network, vortex-diag -v says:
vortex-diag.c:v2.03 9/26/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a 3Com 3cSOHO100-TX adapter at 0xfc00.
Indication enable is ffff, interrupt enable is ffff.
Interrupt sources are pending.
Interrupt latch indication.
Adapter Failure indication.
Tx Complete indication.
Tx Available indication.
Rx Complete indication.
Rx Early Notice indication.
Driver Intr Request indication.
Statistics Full indication.
DMA Done indication.
Download Complete indication.
Upload Complete indication.
DMA in Progress indication.
Command in Progress indication.
Transceiver/media interfaces available: 100baseT4 100baseTx 100baseFx
10baseT 10base2 AUI MII .
Transceiver type in use: undefined-15.
MAC settings: full-duplex, Large packets permitted, 802.1Q flow control,
VLT VLAN enabled.
Maximum packet size is 65535.
Station address set to ff:ff:ff:ff:ff:ff.
Configuration options ffff.
Parsing the EEPROM of a 3Com Vortex/Boomerang:
3Com Node Address FF:FF:FF:FF:FF:FF (used as a unique ID only).
OEM Station address ff:FF:FF:FF:FF:FF (used as the ethernet address).
Manufacture date (MM/DD/YYYY) 15/31/2027, division y, product yy.
Options: force full-duplex.
Vortex format checksum is incorrect (0000 vs. ffff).
Cyclone format checksum is incorrect (00 vs. 0xff).
Hurricane format checksum is incorrect (00 vs. 0xff).
***WARNING***: No MII transceivers found!
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents, -ee for parsed contents,
or '-m' or '-mm' to show MII management registers.
and mii-diag -v says:
mii-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
MII PHY #24 transceiver registers:
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff ffff.
No MII transceiver present!.
Then I ran the network startup scripts and vortex-diag -v said:
vortex-diag.c:v2.03 9/26/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a 3Com 3cSOHO100-TX adapter at 0xfc00.
Indication enable is 06c6, interrupt enable is 06de.
No interrupt sources are pending.
Transceiver/media interfaces available: 100baseTx 10baseT.
Transceiver type in use: 10baseT.
MAC settings: half-duplex.
Station address set to 00:01:02:c0:9f:8b.
Configuration options 000a.
Parsing the EEPROM of a 3Com Vortex/Boomerang:
3Com Node Address 00:01:02:C0:9F:8B (used as a unique ID only).
OEM Station address 00:01:02:C0:9F:8B (used as the ethernet address).
Manufacture date (MM/DD/YYYY) 8/10/2000, division H, product CJ.
Options: none.
Vortex format checksum is incorrect (003c vs. 10b7).
Cyclone format checksum is correct (0xa1 vs. 0xa1).
Hurricane format checksum is correct (0xa1 vs. 0xa1).
MII PHY found at address 24, status 784d.
MII PHY found at address 0, status 784d.
MII PHY 0 at #24 transceiver registers:
3000 784d 0000 0000 01e1 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
0000 0080 0090 0000 0000 0005 2001 0000
0000 2040 07cf 1c11 0011 1000 0000 0000.
MII PHY 1 at #0 transceiver registers:
3000 784d 0000 0000 01e1 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
0000 0080 0090 0000 0000 0005 2001 0000
0000 2040 07cf 1c11 0011 1000 0000 0000.
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents, -ee for parsed contents,
or '-m' or '-mm' to show MII management registers.
and mii-diag -v said:
mii-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
MII PHY #24 transceiver registers:
3000 784d 0000 0000 01e1 0000 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
0000 0080 0090 0000 0000 0005 2001 0000
0000 2040 07cf 1c11 0011 1000 0000 0000.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD
10baseT.
Able to perform Auto-negotiation, negotiation not complete.
Your link partner does not do autonegotiation, and this transceiver type
does not report the sensed link speed.
Thank you for your help, Bogdan!
If you need any other information, please let me know.
Sincerely,
Mark
-----Original Message-----
From: vortex-admin@scyld.com [mailto:vortex-admin@scyld.com]On Behalf Of
Bogdan Costescu
Sent: Wednesday, November 29, 2000 10:40 AM
To: Mark Lubratt
Cc: vortex@scyld.com
Subject: Re: [vortex] 3cSOHO100-Tx Speed Problem
On Wed, 29 Nov 2000, Mark Lubratt wrote:
> I just bought a 3cSOHO100-Tx card and I'm installing it ...
> I used vortex-diag and that said the available media types were 100baseTx
> and 10baseT, but that the card was using 10baseT. I tried usind
> 'vortex-diag -A 100baseTx' to no avail. I also used 'mii-diag eth0 -A
> 100baseTx'. Both didn't seem to work. I've also tried a different
network
> cable. Nothing seems to work.
Can you send us the detection message from driver start-up, along with the
output from 'vortex-diag -v' and 'mii-diag -v' ?
Do you specify any module options, by any chance ?
Sincerely,
Bogdan Costescu
IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu@IWR.Uni-Heidelberg.De
_______________________________________________
vortex mailing list
vortex@scyld.com
http://www.scyld.com/mailman/listinfo/vortex