Hi,

    Now we've got the serial console to work on our 3/60, we've run into
another problem.  We get to this stage:

nfs_boot: using network interface 'le0'
nfs_boot: client_addr=0xc0000203 
nfs_boot: server_addr=0xc0000201
nfs_boot: hostname=idiosyncracy

then it just repeats

RPC timeout for server 0xc0000201

   The server is a Linux box running kernel 1.3.20 and using a very recent
slackware install.  It's running rpc.portmap, rpc.mountd and rpc.nfsd and
the correct directories are exported to the 3/60 read-write.  

   I've run tcpdump to try and see what's happening and I'm seeing this:

14:43:17.982247 idiosyncracy.strange.org.1023 > erratic.strange.org.701: udp 64
14:43:17.982247 erratic.strange.org.701 > idiosyncracy.strange.org.1023: udp 84
14:43:17.992247 idiosyncracy.strange.org.1023 > erratic.strange.org.sunrpc: udp
56
14:43:17.992.747 > idiosyncracy.strange.org.1023: udp 60
14:43:18.002247 idiosyncracy.strange.org.1023 > erratic.strange.org.sunrpc: udp
56
14:43:18.002247 erratic.strange.org.sunrpc > idiosyncracy.strange.org.1023: udp
28
14:43:18.012248 idiosyncracy.strange.org.1023 > erratic.strange.org.701: udp 64
14:43:19.002264 idiosyncracy.strange.org.1023 > erratic.strange.org.701: udp 64
14:43:21.002298 idiosyncracy.strange.org.1023 > erratic.strange.org.701: udp 64

  The last few requests are what's failing.  What's on port 701?  (Or
rather, should be on 701?)  Is it just a random port # used in the nfs
conversation?

  Any suggestions would be GREATLY appreciated :)

  Thanks,

   Ben and Bev

PS I'll write something about how I got this to boot once it actually is
booting :)

-- 
   __   _                                    Ben Walter  <bjw@gnu.ai.mit.edu>
  / /  (_)__  __ ____  __
 / /__/ / _ \/ // /\ \/ /  . . .  t h e   c h o i c e   o f   a
/____/_/_//_/\_,_/ /_/\_\              G N U   g e n e r a t i o n . . .