Subject: net boot problems
To: None <port-sparc@netbsd.org>
From: David Laight <david@l8s.co.uk>
List: port-sparc
Date: 02/01/2003 11:23:48
I'm trying to get my sparc system to netboot netbsd off my x86 box.

Fixing one thing after another has got me past the kernel file
being opened using nfs, but it isn't being read to completion.

The system claims to be a SUN4M, has 64Mb of memory and will
boot Solaris 8 of its hard disk.  It isn't a sun box...

The sparc system (teepee) console says:

ok boot net
Boot device: /iommu/sbus/ledma@4,8400010/le@4,8c00000  File and args: 
Automatic network cable selection succeeded : Using TP Ethernet Interface 14a00 
Server IP address: 192.168.0.1 
Client IP address: 192.168.0.20 
>> NetBSD/sparc Secondary Boot, Revision 1.13
>> (dsl@snowdrop, Wed Jan 29 23:20:55 GMT 2003)
Booting netbsd
bootp: no reply
Automatic network cable selection succeeded : Using TP Ethernet Interface 
Using BOOTPARAMS protocol: ip address: 192.168.0.20, hostname: teepee.l8s.co.uk
root addr=192.168.0.1 path=/sparc_root
bootp: no reply
Using BOOTP protocol: ip address: 192.168.0.20, hostname: teepee.l8s.co.uk, netmask: 255.255.255.0, gateway: 192.168.0.1
root addr=192.168.0.1 path=/sparc_root
Can't open NFS network connection on `/iommu@0,10000000/sbus@0,10001000/ledma@4,8400010/le@4,8c00000'
open netbsd: Unknown error: code 60
: trying netbsd.gz...
....

I've run tcpdump, the 'bootp: no reply' are about 30 seconds, 4 messages:
teepee.1023 > 255.255.255.255.sunrpc: [udp sum ok] udp 96 (ttl 64, id 0, len 124)

After the 'Using BOOTPARMS protocol' message, there is a bit of nfs traffic,
	lookup fh 2048,1/2 "netbsd"		this is GENERIC
	read fh 2048,1/3 1024 bytes @ 0
	read fh 2048,1/3 1024 bytes @ 1024
	read fh 2048,1/3 1024 bytes @ 2048
	read fh 2048,1/3 1024 bytes @ 3072
	read fh 2048,1/3 64 bytes @ 52
	read fh 2048,1/3 440 bytes @ 3071820
All the responses are 'ok'.

It then times out bootp again, then 4 packets:
0.0.0.0.1020 > snowdrop.1021: [udp sum ok] udp 76 (ttl 64, id 0, len 104)

The 'Can't open NFS network connection...' messages don't generate any
network traffic.

Thoughts?

	David

-- 
David Laight: david@l8s.co.uk