Hi everyone, 

I'm learning to netboot a sparcstation 10 and getting stuck with
bootparamsd.  The bootserver is NetBSD 1.5.  

/etc/bootparams looks like this:

sparc root=nfsserver:/usr/local/play/export/sparc/root gateway=192.168.1.5:0xffffff00 

because "sparc" is the name (for now) of the sparc box.  I don't know
how the "nfsserver" string is significant.  

On the sparc, I see this:

Rebooting with command: net-tpe                                       
Boot device: /iommu/sbus/ledma@f,400010:tpe/le@f,c00000  File and args: 
Lost Carrier  (transceiver cable problem?)  
Twisted pair cable problem or hub link-test disabled.
Use the PROM command "help ethernet" for more information.

ARP/RARP send failed.  Check Ethernet cable and transceiver.
13200 
>> NetBSD/sparc Secondary Boot, Revision 1.9
>> (toor@proxima, Tue Aug 21 23:18:13 CST 2001)
Booting netbsd
Using BOOTPARAMS protocol: ip address: 192.168.1.10, hostname: sparc
bootp: no reply
Using BOOTP protocol: ip address: 192.168.1.10, hostname: sparc, netmask: 255.255.255.0, gateway: 192.168.1.1
root addr=0.0.0.0 path=/
Data Access Exception
Type  help  for more information
ok 

In /var/log/messages:

Dec 30 03:35:12 lowden rarpd[3554]: received packet on ex0
Dec 30 03:35:12 lowden rarpd[3554]: sparc asked; 08:00:20:1f:97:13 replied
Dec 30 08:35:12 lowden tftpd[4451]: 192.168.1.10: read request for C0A8010A.SUN4M: success
Dec 30 03:35:13 lowden rarpd[3554]: received packet on ex0
Dec 30 03:35:13 lowden rarpd[3554]: sparc asked; 08:00:20:1f:97:13 replied
Dec 30 03:35:13 lowden rpc.bootparamd: whoami got question for 192.168.1.10
Dec 30 03:35:13 lowden rpc.bootparamd: This is host sparc
Dec 30 03:35:13 lowden rpc.bootparamd: Returning sparc       192.168.1.1
Dec 30 03:35:13 lowden rpc.bootparamd: getfile got question for "sparc" and file "root"
Dec 30 03:35:13 lowden rpc.bootparamd: getfile failed for sparc
[repeats]

My question: Does "getfile failed for sparc" really mean
rpc.bootparamd didn't find the matching line in /etc/bootparams? 
(I've tried it with and without the gateway parameter).

Many thanks, 

--jkl

PS. Notes to anyone reading the archive:

1.	The diskless howto doesn't mention that rpc.bootparamd requires
rpcbind.  

2.	I had lots of whoami problems until I restarted the bootserver. 
Apparently, rpc.bootparamd won't answer whoami properly unless it's
started by rc.