> I don't know what the cause of this problem is, but apparently
> others have seen the same or a similar problem with different
> hardware, so this may not be a driver bug but a more general
> "kernel bug".  I've not had the time to dig deeper into this;
> sorry.


I had confusion that seems similar when I was trying to install NetBSD 
on at Alpha.  It was my first contact with NetBSD so I could easily 
have done something silly.  It had a 21143 Tulip chip.

I was using -current from a few weeks ago.

Here is what I remember.  I can probably run a few experiments if 
that will help.

When I was initially running at 10 megabits, trying to install things 
via FTP, the driver would print some complaint asking me if the cable 
was unplugged, or something close to that.  It did that roughly every 
second.  I couldn't get to the outside world.  If I ran ping to my 
NetBSD machine from another machine, everything worked.  If I stoped 
the ping the messages came back.  I haven't seen similar problems 
at 100 megabits.  (I stopped worrying about this after I switched 
to 100 and started making progress.)