[tulip] Can't get Accton EN1207 to work in 100MBit

[Donald Becker]

On Wed, 12 Sep 2001, Marcus Blomenkamp wrote:
> Am Mittwoch, 12. September 2001 16:30 schrieb Donald Becker:
> > Did you do a google search?
> 
> Yepp, lots of results pointing to this mailing list. groups.google.com also 
> showed mainly problems not solutions :-(. I thought, perhaps someone recalled 
> a very simple solution or nogo-situation.

Keep in mind that very few people post follow-ups after a problem is
fixed.  They almost always post repeat messages if the problem isn't fixed.

This board did work with the Tulip driver.

> > What driver version are you trying to use?
> > What is the detection message?

> Oh, I forgot.
> Kernels 2.4.7 + 2.4.9
> dmesg shows (after loading with options=4):
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)

You should send a bug report to Jeff Garzik.

Does the board work with the v0.92 driver series?

> tulip0: Transceiver selection forced to 10baseT-FDX.
> tulip0: Old format EEPROM on 'Accton EN1207' board.  Using substitute
> media control info.

I had to write a media table for the board, since it doesn't have one in
the EEPROM.

> tulip0:  EEPROM default media type Autosense.
> tulip0:  Index #0 - Media 10base2 (#1) described by a 21140 non-MII (0) block.
> tulip0:  Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
> tulip0:  Index #2 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) 
> block.
> tulip0:  Index #3 - Media 100baseTx (#3) described by a 21140 non-MII
> (0) block.
> tulip0:  Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) 
> block.
> eth0: Digital DS21140 Tulip rev 17 at 0xe800, 00:00:E8:15:DA:BA, IRQ 12.
> eth0: Using user-specified media 10baseT-FDX.

I'm guessing that you are currently forcing the media type.

Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993