At 10:09 AM +0900 10/27/99, Toru Nishimura wrote:
> > OK at this point I have gotten the machine to swallow both nfsnetbsd
> > and smallnet.ecoff-
> >
> > There are hundreds of lines of:
> > ?IO: LANCE  ste 0xa6b3 - - - - - - - - - - - - - - - - - - - - - - -
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > ?IO: LANCE  ste 0xa6b3
> > \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> > ?IO: LANCE  ste 0xa6b3 | | | | | | | | | | | | | | | | | | | | | | |
> > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
> > | | | | | | | |
> > ?IO: LANCE  ste 0xa6b3
> > //////////////////////////////////////////////////////////////////
> > ?IO: LANCE  ste 0xa6b3  - - - - - - - - - - - - - - - - - - - - - - -
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
>LANCE status register complains there were network transaction error
>which should not have happen in correctly configured Ethernet network.

?I have a simple dumb hub behind a MASQing linux box- a 192.168.1.x 
subnet. On the hub there is a NeXT, an iMac, a PowerBook 2400 and a 
NetBSD Mac68k Quadra. All other...

Ahh! If all other hosts respond correctly it must be the transciever- 
and was :-) (turned heartbeat on)

However then I'm stuck at
>>boot 3/tftp

-tftp boot(3) , bootp 192.168.1.1:/tftpboot/smallnet.ecoff
^Cftp load 437376

and

>>boot 3/tftp

-tftp boot(3) , bootp 192.168.1.1:/tftpboot/nfsnetbsd
^Cftp load 954672/

Then the spinning cursor stops and there's no more network activity- 
so netbooting yet for me. Ideas???

-mab


>
> > Repeated many times. I am supposing that it's waiting for the NFS
> > stuff that I have not had time to look at. I put it off when I saw
> > that I did not understand Linux's new NFS implementation without some
> > research.
>
>The messages are generated by LANCE network driver built in DECstation
>PROM monitor.  At this point NetBSD kernel is not active yet, so Linux
>NFS server implementation is not related with this errorous behavior.
>
>Tohru Nishimura