21140 into 100Mbps mode

[Jason Michaelson]

I've got an Osicom quad-port 10/100 card with 4 21140's that I'm trying to
get to come up in 100Mbps mode on system startup. My problem is that it
initially defaults to 10BaseT, Linux starts, I load the tulip module with
options to go to 100BaseTX, and when ifconfig configs the interfaces, the
hub port ends up partitioned. Unplugging the cable and replugging it
result in the desires 100BaseTX link, with no problems.

tha actual loading of the tulip module (options=19,19,19,19) yields the
following output:

eth0: Digital DS21140 Tulip at 0xdc00, 00 00 bc 11 61 c3, IRQ 11.
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
eth0:  Index #1 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
eth0:  Index #2 - Media 10baseT-FD (#4) described by a 21140 non-MII (0) block.
eth0:  Index #3 - Media 100baseTx-FD (#5) described by a 21140 non-MII
(0) block.
eth1: Digital DS21140 Tulip at 0xd880, 00 00 bc 11 61 c2, IRQ 11.
eth1:  EEPROM default media type Autosense.
eth1:  Index #0 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
eth1:  Index #1 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
eth1:  Index #2 - Media 10baseT-FD (#4) described by a 21140 non-MII (0) block.
eth1:  Index #3 - Media 100baseTx-FD (#5) described by a 21140 non-MII
(0) block.
eth2: Digital DS21140 Tulip at 0xd800, 00 00 bc 11 61 c1, IRQ 11.
eth2:  EEPROM default media type Autosense.
eth2:  Index #0 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
eth2:  Index #1 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
eth2:  Index #2 - Media 10baseT-FD (#4) described by a 21140 non-MII (0) block.
eth2:  Index #3 - Media 100baseTx-FD  (#5) described by a 21140 non-MII
(0) block.
eth3: Digital DS21140 Tulip at 0xd480, 00 00 bc 11 61 c0, IRQ 10.
eth3:  EEPROM default media type Autosense.
eth3:  Index #0 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
eth3:  Index #1 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
eth3:  Index #2 - Media 10baseT-FD (#4) described by a 21140 non-MII (0) block.
eth3:  Index #3 - Media 100baseTx-FD (#5) described by a 21140 non-MII  
(0) block.
eth0: Using user-specified media 100baseTx.
eth1: Using user-specified media 100baseTx.

eth0 and eth1 are the only interfaces currently in use. Since the
autosense is apparently not sensing the 100Mbps capability of the hub, I
want to now how to use tulip-diag to write out to the EEPROM to use
100BaseTx by default.

Thanks,

JDM

--------
Jason D. Michaelson          | Debian GNU/      o http://www.debian.org
mich0101@tc.umn.edu          |         __
ares0@geocities.com          |        / /    __  _  _  _  _ __  __
Jason.Michaelson@veritas.com |       / /__  / / / \// //_// \ \/ /
                             |      /____/ /_/ /_/\/ /___/  /_/\_\
http://www.tc.umn.edu/       |
~mich0101                    |   ...because lockups are for convicts...

Getting a SCSI chain working is perfectly simple if you remember that
there must be exactly three terminations: one on one end of the cable, one
on the other end, and the goat, terminated over the SCSI chain with
a silver-handled knife whilst burning *black* candles. --- Anthony
DeBoer

-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-tulip-request@beowulf.org