linux tulip driver v.90

[Dana Hudes]

Don,
I now have v.90z tulip driver trying to work with the SMC8432T .
I verify in /var/log/messages that indeed v.90z is loaded.
eth0: Digital DC21041 Tulip rev 33 at 0xe880, 21041 mode, .... IRQ 11

In messages time stamped after the latest boot, I continue to get the
"no 21041 10baseT link beat, Media switched to 10base2" message
followed 30 seconds later by "21041 media switched to 10baseT"
This cycle repeats again with only 10 seconds on 10base2, and continues to
do so.

The first thing logged for eth0 on this boot cycle is
"eth0:21041 Media information at 30, default media 0800 (Autosense)."

The option to force and lock on 10baseT is still not working properly.

Your assistance is appreciated.

Dana Hudes

At 12:40 AM 4/13/99 -0400, you wrote:
>On Tue, 13 Apr 1999, Dana Hudes wrote:
>
>> We first corresponded about the SMC Etherpower problem on April 5.
>> You were going to look at it in the morning. Have you had a chance
>> to do some testing, maybe find a problem?
>
>Yes.
>I spent the evening working on the old EtherPower card, and refreshed my
>memory of the problem.  The link beat indication from the 10baseT
>transceiver is not connected to the input pin provided (in an badly
>documented way).
>
>I released
>  ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/test/tulip.c
>which should fix the media lock problem, and quickly switch to 10base2 when
>10baseT link beat is lost in autosense mode.  The only problem is that
>switching back to 10baseT when in autosense-10base2 mode only happens when
>there is a transmit timeout.
>
>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
>
>
>