On Sun, 4 Jun 2000, Niels de Koning wrote:
> > > The problem was a config-file in ENV: When I deleted that file the
> > > problem was gone! I tested this to be sure by temporarily putting the
> > > file back and it seems to be 100% reproducable.
> > > It was a 7 byte large ascii config-file called
> > > ENV:Sana2/ariadne_ii_0.config. The contents of this file was a string
> > > "10BASET"
> >
> > But does it actually work, or simply not make the LED go out?
>
> It actually works now, I probably should have mentioned that more
> clearly. :-)
>
> The documentation of the Ariadne II card I'm using mentions this configfile
> so that is why it was on my hardddisk. Why Miami (or maybe it is
> ariadne_ii.device that is causing this) would not like having this file or
> if it is only a problem on my configuration is unknown to me. The fact
> remains that I can fully reproduce it by creating such an environment
> variable at the location I mentioned...
Same here - must be a driver bug. I never set that variable before since
the autodetect functioned properly.
BTW, rebooting isn't needed to fix it. I found that expunging the driver
and then going online with the MNI driver cleared it up. The first alone
wasn't sufficient, so the driver must have left the NIC in a funny state.
Perhaps it switched it to 10Base2 mode by mistake.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
