Re: boot net on v210 fails to execute

Whoa! That turned out to take more effort than I had expected, but I did get
it to work. Not quite as easy as the SGI Origin 200 was. The SGI was slam
dunk.

Here's the steps for others that might attempt a netinstall on sparc64.
Perform the following on an existing OpenBSD server to act as bootserver.
1)
Edit /etc/ethers and /etc/hosts to include any relevant hostnames.
2) Edit
/etc/inetd.conf to enable tftpd, and -HUP the inetd process.
3) Create
/tftpboot and drop ofwboot.net there with (o+r) but symlink to target IP
address in hex. (just google it)
4) Create a directory for NFS export and drop
bsd.rd there (o+r).
5) Create /etc/bootparams as directed in bootparams(5).
6)
Start rarpd, portmap, rpc.bootparamd, mountd, and nfsd.
7) Check RPC service
registrations with "rpcinfo -p".
8) Check NFS exports with "showmount -e".

On
target system OFW prompt:
ok boot net bsd.rd

After a bit you should see it
first load the OpenBSD boot loader, followed by the bootparams portion, and
finally the kernel will load.

At first I thought it would be like the SGI
Origin 200, where the PROM would simply TFTP load the ramdisk image. Then I
learned that it first needs to load a bootloader, which I then thought would
perform its own TFTP load of the ramdisk image. But the bootloader is actually
expecting to find the ramdisk image over NFS, which requires rpc.bootparamd,
etc.

It's a bit counter-intuitive as I would expect SGI to be more arcane
than Sun.

--- On Sun, 11/14/10, Theo de Raadt <[email protected]>
wrote:

> From: Theo de Raadt <[email protected]>
> Subject: Re: boot
net on v210 fails to execute
> To: [email protected], [email protected]
>
Date: Sunday, November 14, 2010, 12:07 AM
> [...]
> 
> >ok boot net
> >Boot
device: /pci@1f,700000/network@2  File and
> args:
> >1000 Mbps FDX Link up
>
>Requesting Internet Address for 0:3:ba:15:ff:a6
> >The file just loaded does
not appear to be executable.
> >ok
> >
> >Running "rarpd -d xl1"
> >rarpd: got
a packet
> >rarpd: 00:03:ba:15:ff:a6
> >rarpd: reply sent
> >
> >>From
"/var/log/daemon"
> >Nov 13 22:23:39 router tftpd[5268]: 192.168.29.26: read
>
request for 'C0A81D1A'
> >
> ># pwd
> >/tftpboot
> ># ls -l 
> >total 24096
>
>lrwxr-xr-x  1 root  wheel     
>   6 Nov 12 16:05 C0A81D1A -> bsd.rd
>
>-rw-r--r--  1 root  wheel  2626510 Aug
> 16 12:07 bsd.rd
> 
> Aha!  Here's
your error.  Go read the diskless(8)
> manual page.  It will
> make it clear
that this symbolic link must be to the
> boot.net program,
> not to the
kernel.  The kernel itself will need to be
> inside a NFS-exported
>
filesystem.
> 
> That boot.net program then will be smart enough to load
>
your kernel correctly.
> Yes, it does a second rarp lookup and then finally it
does
> NFS to get the
> kernel.