v0.91 driver released for testing

[Donald Becker]

On Sat, 17 Apr 1999, David Godfrey wrote:

> > > Apr 17 11:35:00 wang linux: eth0:  Index #1 - Media MII 100baseT4 (#15) described by a 21142 Serial PHY (2) block.
> > Is this correct?  Is the card T4-capable?  That doesn't seem very likely.
> No. I don't believe it is. None of the other cards have this value.
> > This is almost certainly an error is the EEPROM media table.

OK, the driver can't do anything about a corrupted EEPROM (although a custom
hack to tulip-diag could fix the EEPROM).

> > Load the module with "debug=3" to see the gory details of the media
> Not the identical symptoms. Another card is not put into a usable
> state by 0.91. Indeed, it is left in an unusable state and
> will not work with 0.90p afer rebooting/resetting.
> This card is in a dual-boot W95 machine - booting up W95 gets
> the card working again.

Does the card work at 100mbps with W95 or the earlier driver?
(I want to verify that this isn't a cable problem.)

> eth0: 21143 link status interrupt 41e1d2ce, CSR5 f0668010, fffbffff.
> eth0: Switching to 100baseTx-FD based on link partner advertisement 41e1.

Good.

> eth0: Using media type 100baseTx-FD, CSR12 is ce.
> eth0: 21143 link status interrupt 41e1d2cd, CSR5 f8668000, fffbffff.
> eth0: 21143 100baseTx-FD link beat good.

Good so far.

> eth0: 21143 link status interrupt 41e192cf, CSR5 f8668000, fffbffff.

Ooops, you lost 100baseTx link beat.  How quickly did this happen?

> eth0: 21143 negotiation status 41e192cf, 100baseTx-FD.

This time when you switched there just wasn't link beat. ???

Donald Becker					  becker@cesdis.gsfc.nasa.gov
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771
301-286-0882	     http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html