Cogent EM110 10/100 autosense problem
Darren Price
dp@shaw.wave.ca
Sat Jul 11 00:25:54 1998
I sent this a few days ago, no response yet...
so maybe the group can help.. the only update is that I've now ordered,
recieved, and installed Redhat 5.1, and the problem is identical.
--
Date: Sat Jul 11 00:25:54 1998
To: siekas@mailhost.tcs.tulane.edu
From: Darren Price <dp@shaw.wave.ca
Subject: Help, if you please.
Bcc: darren.price@telus.com
Okay, this is the problem:
I've got Redhat 4.2 [old, I know] and i'm using the latest tulip.c, and
can't get a cogent em110 to switch to 10BaseT from 100BaseT. The link
light goes active, but no pings, no connectivity of any kind [which is
typical with 100BaseT settings or autosensing failure]. The card is good,
it works under NT, 95 and DOS.
These are the relevant files:
conf.modules
--
alias scsi_hostadapter aic7xxx
alias eth0 tulip
options tulip options=12 debug=1
output of tulip-diag
--
tulip-diag.c:v1.03 5/20/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Chip Index #1: Found a DC21140 Tulip card at PCI bus 0, device 10 I/O 0xd000.
Digital DS21140 Tulip chip registers at 0xd000:
fff84800 ffffffff ffffffff 00f3f028 00f3f228 fc660000 e3842002 ffffebef
fffe0000 ffffdff0 ffffffff fffe0000 ffffff81 ffffffff 1c09fdc0 fffffec8
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
Transmit started, Receive started, half-duplex.
The transmit threshold is 128.
Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
An old-style EEPROM layout was found.
The old-style layout does not contain transceiver control information.
This board may not work, or may work only with a subset of transceiver
options or data rates.
tulip-diag.c:v1.03 5/20/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Chip Index #1: Found a DC21140 Tulip card at PCI bus 0, device 10 I/O 0xd000.
An old-style EEPROM layout was found.
The old-style layout does not contain transceiver control information.
This board may not work, or may work only with a subset of transceiver
options or data rates.
***WARNING***: No MII transceivers found!
tulip-diag.c:v1.03 5/20/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Chip Index #1: Found a DC21140 Tulip card at PCI bus 0, device 10 I/O 0xd000.
An old-style EEPROM layout was found.
The old-style layout does not contain transceiver control information.
This board may not work, or may work only with a subset of transceiver
options or data rates.
output of /var/logs/messages
--
Jul 6 19:28:46 snark kernel: tulip.c:v0.10 8/11/95
becker@cesdis.gsfc.nasa.gov
Jul 6 19:28:46 snark kernel: +0.72 4/17/96
http://www.dsl.tutics.tut.ac.jp/~linux/tulip
Jul 6 19:28:46 snark kernel: +0.01 10/24/96 mjacob@feral.com (2.1.7)
Jul 6 19:28:46 snark kernel: eth0: cogent_em110 (DEC 21140 Tulip) at
0xd000, 00:00:92:96:12:6f, IRQ 9
Jul 6 19:28:46 snark kernel: eth0: enabling 10baseT port.
[updated driver after this, previous driver didn't even cause the link on
the hub to go on, after, below, it did, but still no lights active on the
ethernet card]
Jul 6 21:25:48 snark kernel: tulip.c:v0.89H 5/23/98
becker@cesdis.gsfc.nasa.gov
Jul 6 21:25:48 snark kernel: eth0: Digital DS21140 Tulip at 0xd000, 00 00
92 96 12 6f, IRQ 9.
Jul 6 21:25:48 snark kernel: eth0: Old format EEPROM on 'Cogent EM100'
board. Using substitute media control info.
Jul 6 21:25:48 snark kernel: eth0: EEPROM default media type Autosense.
Jul 6 21:25:48 snark kernel: eth0: Index #0 - Media 100baseFx (#7)
described by a 21140 non-MII (0) block.
Jul 6 21:25:48 snark kernel: eth0: Index #1 - Media 100baseFx-FD (#8)
described by a 21140 non-MII (0) block.
Jul 6 21:25:48 snark kernel: eth0: Index #2 - Media 100baseTx (#3)
described by a 21140 non-MII (0) block.
Jul 6 21:25:48 snark kernel: PCI latency timer (CFLT) is 0x20, PCI
command is 0007.
Jul 6 21:26:34 snark kerneld: started, pid=965, qid=256
Jul 6 21:27:15 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:28:05 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:29:37 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:30:42 snark kerneld: started, pid=1167, qid=384
Jul 6 21:30:53 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:31:09 snark kerneld: started, pid=1204, qid=512
Jul 6 21:31:13 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:31:38 snark kerneld: started, pid=1238, qid=640
Jul 6 21:31:41 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:32:09 snark kerneld: started, pid=1275, qid=768
Jul 6 21:32:12 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:32:32 snark kerneld: started, pid=1309, qid=896
Jul 6 21:33:46 snark kerneld: started, pid=1322, qid=1024
Jul 6 21:33:57 snark kernel: eth0: Using user-specified media 100baseTx.
Jul 6 21:34:19 snark kerneld: started, pid=1356, qid=1152
Jul 6 21:34:23 snark kernel: eth0: Using user-specified media 100baseTx.
As you can see, I tried a multitude of tulip options settings in the
conf.modules file, [0,9, and 12] restarted kerneld, de-activated and
re-activated the interface, but to no avail.
Any ideas? Or should I just throw out the card for something newer?
Let me know..
Thanks
dp