3 booting \- bootstrapping procedures
7 This manual page collects the incantations required to bootstrap Plan 9 machines.
8 Some of the information here is specific to the installation at Bell Labs;
11 If a CPU server is up, BOOTP/DHCP and TFTP will run from there;
12 if not, the necessary files and services must be available on a separate machine,
13 such as a Unix system, to use these protocols for bootstrapping.
17 to understand what happens after the kernel is loaded.
19 To bootstrap a diskless terminal or a CPU server, a file server must be running.
20 PCs can boot from a floppy disk or any FAT16 partition.
21 On all the terminals, typing two control-T's followed by a lower-case
24 other methods of rebooting are mentioned for some machines.
26 To boot a PC, it is necessary to get
31 There are many ways to do this. A Plan 9 boot floppy prepared by
37 when the PC is reset or powered on.
38 Other methods are described in
41 then locates and loads a Plan 9 kernel, using configuration information
46 configuration partition or on a DOS file system.
51 Once the kernel is booted, it behaves like the others.
56 Alpha PCs must be booted via TFTP using the SRM console.
57 If the system has ARC firmware instead, SRM may be downloaded from
60 http://www.compaq.com/
63 You must configure the SRM firmware to load the file
64 .BR /alpha/bootalphapc .
65 The following commands may be used (replace
67 with the name of your ethernet device, if different):
71 set boot_file /alpha/bootalphapc
73 set ewa0_inet_init bootp
74 set ewa0_protocols BOOTP
77 This secondary bootstrap program will first load the file
78 .BR /alpha/conf/ <IP-address>
79 (substituting the IP address of the system as obtained via bootp).
80 This file is expected to be in
83 .B /alpha/conf/10.0.0.2
84 may be used as a template).
85 It then loads the kernel via tftp, using the value of
87 to tell it which file to load; this should be
91 The Plan 9 CPU servers are multi-user, so they do not request a user name
93 On the CPU servers, typing a control-P on the console reboots the machine.
95 Proceed as for the PC terminal, but load
99 .SS Alpha PC CPU Server
100 Proceed as for the Alpha PC terminal, but use
104 .SS SGI Challenge multiprocessor CPU Server
105 The Challenge ROM monitor can boot from the Ethernet.
106 To boot from the Ethernet, type
112 or use the ROM command
116 to that same string and type
118 To load a different file, tell
121 and to force the download to come from a particular system,
122 .BR bootp()system:file .
127 If you are running a Plan 9
131 the file name can be omitted and the
132 file specified by the
134 parameter for the machine in
136 will be downloaded by default.
138 Once the kernel is loaded,
139 it prompts for the Ethernet
140 protocol to use to reach the root file server; request the default.
143 All ARM systems are started by
145 using similar commands.
153 for the Marvell PXA168-based Guruplug Display,
155 for all Marvell Kirkwood plugs (Sheevaplug, Guruplug, Openrd, etc.),
158 for TI OMAP3 boards (IGEPv2 from ISEE, Gumstix Overo).
162 with your board's MAC address without colons,
173 file for the new CPU server.
177 cd /cfg/pxe; cp example-kw \fIMAC
183 For PXA plugs, replace
187 for OMAP boards, replace
192 be sure to edit the line for
203 to load the appropriate kernel and
205 file at suitable addresses and start the kernel.
206 For Sheevaplugs and Openrd boards,
207 type this at U-boot once:
211 # \fItype the next two lines as one\fP
212 setenv bootcmd 'bootp; bootp; tftp 0x1000 /cfg/pxe/\fIMAC\fP; bootp;
213 tftp 0x800000; go 0x800000'
217 For Guruplugs Displays,
218 do the same but type this after
223 \&'dhcp; tftpboot; tftpboot 0x1000 /cfg/pxe/\fIMAC\fP; bootz 0x500000'
226 For Kirkwood Guruplugs,
228 .LR "setenv bootcmd" :
231 \&'dhcp 0x800000; tftp 0x1000 /cfg/pxe/\fIMAC\fP; go 0x800000'
236 .LR "setenv bootcmd" :
239 \&'tftp 0x80300000 /cfg/pxe/\fIMAC\fP; dhcp 0x80310000; go 0x80310000'
242 For Gumstix Overo boards,
244 .LR "setenv bootcmd" :
247 \&'bootp 0x80310000; bootp 0x80300000 /cfg/pxe/\fIMAC\fP; go 0x80310000'
250 Thereafter, the boards will automatically boot via BOOTP and TFTP
260 Sources for the various boot programs are under