p Once a bootloader is present in the volume header, it may be executed directly by the PROM either manually, or at boot time using the .Dq OSLoader PROM environment variable. The .Nx bootloader will obtain the kernel filename to boot from the PROM or EEPROM. This is specified by setting the PROM environment variable .Dq OSLoadFilename to an appropriate value. For instance, .Dq /netbsd.ecoff .
p For example, the following will configure the PROM to use the bootloader .Dq aoutboot to load the kernel .Dq netbsd.old
p .Dl Ic setenv OSLoader aoutboot .Dl Ic setenv OSLoadFilename netbsd.old .Sh Network Booting The system firmware will obtain an IP address, TFTP server address, and an optional filename from the BOOTP server and download it via TFTP. The PROM's configurable network address environment variable .Dq netaddr must match the address provided by the BOOTP server.
p An example BOOTP entry for .Xr dhcpd 8 follows:
p d -unfilled -offset indent host indigo3k { hardware ethernet 08:00:69:42:42:42; fixed-address 192.168.0.2; option host-name "indigo3k.foo"; #filename "/netbsd.ecoff"; next-server 192.168.0.1; option root-path "/export/indigo3k/root"; server-name "192.168.0.1"; } .Ed
p To boot a kernel named .Dq netbsd.ecoff the user would type: .Dl Ic boot -f bootp():/netbsd.ecoff
p See .Xr dhcpd.conf 5 for more information on configuring .Xr dhcpd 8 as a BOOTP server. .Sh SEE ALSO .Xr dhcpd.conf 5 , .Xr dhcpd 8 , .Xr sgimips/sgivol 8 .Sh CAVEATS Some older PROM revisions do not support loading of ELF images. The build system automatically prepares ECOFF versions, which are correctly interpreted. .Sh BUGS .Nx does not support booting from disk on systems lacking an ARCS-compatible firmware (presently supported systems include Personal Iris and Indigo R3000). It is possible to work around this by creating a sufficiently large volume header and placing the kernel in it, or by network booting.
p Some firmware revisions have a bug, which precludes them from communicating with TFTP servers using ports above 32767. When using .Nx as the TFTP server, this problem may be worked around as follows:
p .Dl Ic sysctl -w net.inet.ip.anonportmin=20000 .Dl Ic sysctl -w net.inet.ip.anonportmax=32767
p Another bug exists in some firmware revisions, which precludes the PROM from communicating with TFTP servers that employ PMTU (Path MTU) discovery. This bug may be worked around by disabling PMTU on the TFTP server. This does not presently affect .Nx servers.
p This man page is horribly incomplete.