The NetBSD/acorn32 FAQ List |
This is the FAQ list for the NetBSD/acorn32 port of NetBSD.
To boot an NC is fairly straightforward using the new boot32 bootloader. On powerup the NC initialises itself and askes for its configuration on the LAN using bootp/dhcp. The easy way is to add a record to dhcpd.conf(5) for the machine and (re)start the dhcpd(8) service after adding dhcpd=YES in your rc.conf(5) file. The following will suffice for an NC machine called `elmo' as an entry (fill in the preferences) :
host elmo {
hardware ethernet 0:0:a4:11:7b:f6;
fixed-address elmo.reinoud.kasbah;
option routers 192.168.2.1;
filename "/usr/export/elmo";
option root-path "/usr/export/elmo";
}
Note that the `filename' option is needed for otherwise it sends the NC a strange file to load that fails due to `insufficient access'. Giving the home directory propably means nothing to the NC and it ignores it.
Secondly you need to export a NFS tree for the NC to work on in exports(5) and run nfsd(8) and mountd(8) by setting nfs_server=YES in your rc.conf(5) file. The following line will suffice for the NC :
/usr/export/elmo -maproot=root elmo
The final step is to place the bootloader called boot32,ffa in the directory /usr/export/elmo used in the template above and the kernel to be booted as either netbsd or netbsd.gz. The following file needs to be made and called !NFSBoot,feb :
*NFS
*RMLoad boot32
*Wimpslot -next 3000k
*WimpMode 32
*desktop *boot32 netbsd
*BASIC
To check your NC's settings and such, you can uncomment the `*desktop' line and be dropped into the BASIC interpreter to use `*' CLI commands. Using the CLI itself is not possible on the NC due to an irritating little module called `CLIProtect' that i once managed to get unplugged but its not easily done.
NetBSD/acorn32 supports all those interfaces with machine-independent podulebus drivers, and also:
RISC OS driver name | Manufacturer | NetBSD driver name |
Ether1 | Acorn | ie0 |
EtherH NIC | I-cubed | ne0 |
EtherM NIC | ANT | ne0 |
EtherH and EtherM NIC drivers are presently the best performers.
The speed of the SCSI drivers is presently relatively poor, whereas the IDE drivers perform well.
Possible causes of this problem are:
|
|