OFWBOOT(8) | System Manager's Manual (MacPPC) | OFWBOOT(8) |
ofwboot |
The information in this man page should only serve as a guideline for users. Apple has made many revisions to Open Firmware, and the earlier versions had many problems and inconsistencies. You may find that a boot command that works on one model will not work on another.
In this man page, only one Open Firmware command will be described, boot, because it is used to pass arguments to ofwboot. The Open Firmware boot command takes up to three arguments:
boot [boot-device [boot-file]] [options]
A typical example, from a PowerBook (FireWire), isboot-device:[partition-num],[bootloader-filename]
Note that colon (`:') delimits the device to the left, and comma (`,') separates the boot loader filename from the first part. For Open Firmware versions before 3, the primary bootloader is installed in partition “zero”, and it is not necessary to specify the bootloader-filename. For Open Firmware version 3, you must specify the bootloader-filename./pci@f2000000/mac-io@17/ata-4@1f000/@0:9,ofwboot.xcf
Open Firmware stores aliases to common devices in NVRAM. In the example above, /pci@f2000000/mac-io@17/ata-4@1f000/@0 is the path on a PowerBook (FireWire) to the built-in ATA/100 hard drive. Use the devalias command in Open Firmware to print out a list of common device names on a particular model. The command above could then be simplified to:
hd:9,ofwboot.xcf
boot-loader-file-name is usually ofwboot.xcf. (See also the FILES section for further discussion.)
If omitted, the Open Firmware variable boot-device is used.
For systems with Open Firmware versions less than 3 which are set up using sysinst, the boot-file argument is not necessary. Systems with Open Firmware version 3 may need to specify the boot-file.
The syntax is similar to the boot-device argument:
This is a little different, since a kernel-name may be specified without listing a boot-file-device and partition-num. Additionally, a boot-file-device and partition-num may need to be specified, while using the default kernel-name.[boot-file-device:partition-num/][kernel-name]
If no kernel-name is specified, the primary bootloader will try to find kernels named either netbsd or netbsd.gz on the boot-device or (if specified) boot-file-device.
0 > boot hd:,ofwboot.xcf
0 > boot hd:,ofwboot.xcf netbsd -s
0 > boot cd:,\ofwboot.xcf netbsd.macppc
0 > boot scsi/sd@3:0,OFWBOOT.XCF NETBSD.MACPPC
0 > boot fd:0
0 > boot enet:0
0 > boot enet:0 ultra1:0
0 > boot hd:,\\:tbxi
0 > boot hd:10,\\:tbxi
DEFAULT CATCH!, code=FF00300 at %SRR0: FF80AD38 %SRR1: 00001070Could be “device not found” or I/O errors on the device. The numbers are just for example.
Can't LOAD from this deviceOpen Firmware found the device, but it is not supported by load.
0 > boot yy:0/netbsd RESETing to change Configuration!yy:0 doesn't exist, so Open Firmware ignores the string and uses the default parameters to boot MacOS; the MacOS boot routine then clears some of the Open Firmware variables.
0 > boot ata/ata-disk@0:9 specified partition is not bootable okAs it says.
0 > boot ata/ata-disk@0:0 >> NetBSD/macppc OpenFirmware Boot, Revision 1.3 >> (root@nazuha, Fri Jun 8 22:21:55 JST 2001) no active package3337696/and hangs: See the real-base part in the FAQ.
INSTALL.html
Early PowerMacintosh systems (particularly the 7500) seem to have problems with netbooting. Adding an arp entry at the tftp server with
may resolve this problem (see arp(8)).arp -s booting-host-name its-ethernet-address
0 > boot CLAIM failed okOnce boot failed, successive boots may not be possible. You need to type reset-all or power-cycle to initialize Open Firmware.
August 18, 2001 | NetBSD 6.1 |