Subject: Please proofread: revised install docs for OF 2.0.x
To: None <port-macppc@netbsd.org>
From: Michael Wolfson <mw@costello.cnf.cornell.edu>
List: port-macppc
Date: 10/25/2000 22:57:01
Howdy,
Since I don't have access to an OF 2.0.x machine, I need y'all to give me
some feedback on this.
In particular, I need to know answers to the following questions:
Can you netboot using your internal ethernet (I ask since OF 1.0.5 can't)?
Run the following command in OF:
dev enet .properties
Does the local-mac-address variable match with what MacOS says is your MAC
address (found in TCP/IP control panel, Advanced User Mode, Info button)?
Which MAC address does your system use when netbooting?
Can you boot from a hybrid ISO/HFS CD-ROM (again, OF 1.0.5 can't)?
Do your OF settings get cleared when you boot into MacOS (they do in OF 1.0.5)?
Can you give me some examples of the OF device you use to boot from CD-ROM?
What are the default values of real-base and load-base in OF 2.0.x?
Do you need to set real-base to F00000 to load a > 3 MB kernel?
Do you need to set load-base to load ofwboot.xcf?
Thanks!
-- MW
Bootable media in Open Firmware 1.0.5 or 2.0.x
1. Discussion of what's available
There are four methods of opening a file in OF 1.0.5 and 2.0.x:
from an MS-DOS filesystem, over ethernet, from an ISO 9660 (CD-ROM)
filesystem, or from `partition zero'. In all cases except `parti-
tion zero', your system must open the `ofwboot.xcf' bootloader to
load the kernel. The `partition zero' method loads a primary boot-
loader called `bootxx' which then loads an `ofwboot' bootloader,
which then loads the kernel. The `ofwboot' bootloader is function-
ally identical to `ofwboot.xcf'.
We can almost immediately discount use of the MS-DOS filesystem, as
neither the ofwboot.xcf bootloader or the kernel can read files di-
rectly from it.
As for ethernet, you can run your entire system diskless or netboot
only the files necessary to boot (i.e. the bootloader and the in-
stallation kernel), but you must have root access on another UNIX
machine on your subnet. It seems some of the OF 1.0.5 machines do
not retrieve the BOOTP information correctly. These machines cannot
netboot.
If you do not have access to a DHCP server running NFS, then you
must load ofwboot[.xcf] either from an ISO 9660 (CD-ROM) disk or
from `partition zero'.
Once ofwboot[.xcf] has loaded, it can open a kernel from only three
sources: over ethernet (NFS), from a NetBSD filesystem (FFS), or
from a CD-ROM filesystem (ISO 9660).
The boot floppy image provided with the distribution sets has a
`partition zero' bootloader and a NetBSD filesystem with an instal-
lation kernel.
When you are first installing NetBSD you will not have any NetBSD
filesystems on your machine, unless you use the boot floppy. This
leaves one option: ISO 9660. Keep in mind that OF 1.0.5 machines
will not be boot from the ISO 9660 filesystem if you create a hybrid
HFS/ISO format CD-R.
If you will be running your system diskless (i.e. entirely over NFS,
not using any local hard drives), then you do not need to run the
installer although you may still do so.
You must run the installer to place NetBSD on a hard drive on your
macppc system.
2. The three common installation techniques (and one not)
o Create the boot floppy. Use some tool to write the boot floppy
image to a floppy disk, and boot from that. The primary boot-
loader (in `partition zero') will load `ofwboot' which will load
the installation kernel. Alternatively, you may
o Create an ISO 9660 CD-ROM. Place ofwboot.xcf and the installa-
tion kernel at the top level of the CD. You may, while you're
at it, also place the NetBSD 1.5_FOO distribution sets on the
disk. You will have OF load ofwboot.xcf from the disk, and it
will then load the installation kernel. If you do not have ac-
cess to a CD-R burner, then you must
o Boot over the ethernet. You will need to set up the DHCP daemon
in BOOTP compatable mode, the TFTP daemon, and the NFS daemons
on your netboot server. You will tell OF to boot over ethernet,
and it will send a BOOTP request, which will tell OF what your
system's IP address is, and where its bootloader can be down-
loaded via TFTP. Once OF has downloaded the bootloader via
TFTP, it will then load the installation kernel via an NFS con-
nection.
o If all else fails, write the floppy disk image If0 0If1 1If2
2If3 You will need to find a spare bootable drive (i.e. SCSI or
IDE). You'll use some tool to write the floppy disk image to
your spare drive, and boot from that drive. The floppy image
has a `partition zero' bootloader which ultimately loads the in-
stallation kernel.
3. Partitioning the drive NetBSD will be installed on
You have two options. You may use the NetBSD installer to partition
your drive and make it bootable (with a `partition zero' bootload-
er), in which case you cannot share this drive with MacOS (i.e. have
any HFS partitions on it). Alternatively, you may share this drive
with MacOS, in which case the drive will not be bootable. You will
need to load `ofwboot.xcf' from some other media (such as over the
network, from a floppy, or from a CD-ROM).
Unfortunately, the partitioning tools for NetBSD are not advanced
enough to create an HFS(+) filesystem. Therefore, if you wish to
share this drive with MacOS, you will need to use the MacOS Drive
Setup tool (versions 1.9.1 and later are known to work) to divide
the hard drive you will be using for NetBSD into the following par-
titions.
o HFS(+) must be large enough to hold the bootloader, over 100 KB.
o A/UX Root; must be at least 20 MB. Alternatively, you may de-
cide to use one partition for your entire NetBSD installation,
in which case it should be at least 200 MB.
o A/UX Swap; any size. The recommenation is 1.5 times your RAM,
although this is not strictly necessary for machines with a lot
of RAM.
o A/UX User, A/UX Free1, A/UX Free2, A/UX Free3; use these for any
additional partitions you may want to use under NetBSD
Open Firmware 1.0.5 or 2.0.x System Preparation
1. Getting to the OF prompt (easy, using MacOS)
Launch the MacOS System Disk tool. Click on `Power User (Open
Firmware)' then click on the `Advanced Options' button. Now, click
on the checkbox that says `Stop Boot at Open Firmware prompt' and
hit `OK'. Click the `Save' button and reboot your system. Now, you
should see the OF command prompt:
0 >
If your screen is black, then your model does not support using the
screen in Open Firmware. You will need to hook up a serial console
(38400 bps, 8 bits, no parity, 1 stop bit, no handshaking).
2. Getting to the OF prompt (harder, using MacOS)
If System Disk doesn't work because your version of MacOS is too old
or because System Disk says that it doesn't support your model, then
you may try using the BootVars tool.
ftp://ftp.netbsd.org/pub/NetBSD/arch/macppc/macos-
utils/bootvars/bootvars.sit.hqx
Note: BootVars does not apply the (possibly critical) NVRAM patches
that System Disk does. Expect devices to not work.
Launch the MacOS BootVars tool. Click on the `auto-boot?' check-
box, click on the `write' button, and restart.
If your screen is black, then your system has defaulted to using a
serial console. This is fairly common on these models if you do not
use the System Disk tool to set up OF. You have two options: hook
up a serial console (38400 bps, 8 bits, no parity, 1 stop bit, no
handshaking), or look up the proper output-device for your model on
the NetBSD/macppc webpages and set this variable with the MacOS
BootVars tool.
http://www.netbsd.org/Ports/macppc/models.html
Zap your PRAM so that MacOS will boot (hold down the `Command',
`Option', `p', and `r' keys when your system chimes). In BootVars,
click on the `All Variables' checkbox and type `kbd' (without the
quotes) into the `input-device' blank, and the proper device name
into the `output-device' blank. Click on the `write' button, and
restart.
If your `output-device' is /chaos/control (i.e. you have a PowerMac-
intosh 7300 - 8600 system), there is a chance that your monitor will
not sync. See
http://www.netbsd.org/Ports/macppc/SystemDisk-
tutorial/of105patch.html
Now, you should see the OF command prompt:
0 >
3. Getting to the OF prompt (without using MacOS)
If you don't have MacOS, then you need to hold down a special key
combination when your system boots.
Note: Your system will not have the (possibly critical) NVRAM
patches that System Disk applies. Expect devices to not
work.
After the chime starts, but before it stops, hold down the
`Command', `Option', `o', and `f' keys (the `Command' key looks like
a four-leaf clover or an open apple, and the `Option' key may look
like a two-way switch with four straight line segments).
Now, your machine is at the Open Firmware command prompt. If your
screen is black, then your system has defaulted to using a serial
console. This is fairly common on these models if you do not use
the System Disk tool to set up OF. You must hook up a serial con-
sole (38400 bps, 8 bits, no parity, 1 stop bit, no handshaking).
Now, you should see the OF command prompt:
0 >
Look up the proper output-device for your model on the NetBSD/macppc
webpages and set this variable at the OF prompt.
http://www.netbsd.org/Ports/macppc/models.html
Run the following commands to use your screen instead of a serial
console (replace `screen' with the correct output-device for your
model):
0 > setenv output-device screen
0 > setenv input-device kbd
0 > reset-all
Now you should see the OF prompt on your screen.
If your `output-device' is /chaos/control (i.e. you have a PowerMac-
intosh 7300 - 8600 system), there is a chance that your monitor will
not sync. See
http://www.netbsd.org/Ports/macppc/SystemDisk-
tutorial/of105patch.html
4. Setting OF up to boot NetBSD
Double-check that your system is indeed OF versions 1.x or 2.0.x:
0 > dev /openprom
0 > .properties
If it is not, then skip forward to the appropriate section for your
version of OF and do not run the following two commands. If your
system is OF 1.x or 2.0.x, then you must set some OF variables be-
fore NetBSD can boot.
0 > setenv load-base 600000
0 > setenv real-base F00000
0 > reset-all
The last command reboots your machine so that the real-base setting
takes effect.
If you will be netbooting your system, you can look up your MAC ad-
dress.
0 > dev enet .properties
[...]
local-mac-address CCCCCCCC CCCC
[...]
Note: Some early OF 1.0.5 machines had their MAC address stored
wrong on the motherboard (little- vs. big-endian problems).
The patches System Disk installs will correct this.
For future reference, when you want to boot into MacOS, type:
0 > bye
Note: All of your Open Firmware settings will be erased if you boot
into MacOS. You will need to re-enter them before booting
NetBSD again