linux tulip driver v.90

[Dana Hudes]

I have done ifconfig eth0 down
then waited a bit and rmmod tulip
then insmod tulip options=12
Makes no difference.
In fact I tried 
insmod tulip options=16 

and the log entry STILL says Media info at 30 ...

also the log for eth0 still says
eth0: 21041 media #0 
regardless of insmod options=12 or 16 
shortly after insmod=12 is the no link beat message

Dana Hudes

At 02:11 PM 4/15/99 -0400, you wrote:
>On Wed, 14 Apr 1999, Dana Hudes wrote:
>
>> >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
>
>> 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
>...
>> The first thing logged for eth0 on this boot cycle is
>> "eth0:21041 Media information at 30, default media 0800 (Autosense)."
>
>This is reporting the EEPROM media setting, which should always be 0x0800.
>
>> The option to force and lock on 10baseT is still not working properly.
>
>Are you using "insmod tulip options=12"?
>
>The default setting is '0', 10baseT-autosense.  It will still switch to
>10base2/AUI if link beat is lost.  You must use '12', "10baseT(forced)" to
>prevent the media type from being switched on loss of 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
>
>
>