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.
23 program is used to load the kernel
27 Once the kernel is booted, it behaves like the others.
32 The Plan 9 CPU servers are multi-user, so they do not request a user name
35 Proceed as for the PC terminal, but have
39 .SS SGI Challenge multiprocessor CPU Server
40 The Challenge ROM monitor can boot from the Ethernet.
41 To boot from the Ethernet, type
47 or use the ROM command
51 to that same string and type
53 To load a different file, tell
56 and to force the download to come from a particular system,
57 .BR bootp()system:file .
62 If you are running a Plan 9
66 the file name can be omitted and the
69 parameter for the machine in
71 will be downloaded by default.
73 Once the kernel is loaded,
74 it prompts for the Ethernet
75 protocol to use to reach the root file server; request the default.
78 All ARM systems are started by
80 using similar commands.
88 for the Marvell PXA168-based Guruplug Display,
90 for all Marvell Kirkwood plugs (Sheevaplug, Guruplug, Openrd, etc.),
93 for TI OMAP3 boards (IGEPv2 from ISEE, Gumstix Overo).
97 with your board's MAC address without colons,
108 file for the new CPU server.
112 cd /cfg/pxe; cp example-kw \fIMAC
118 For PXA plugs, replace
122 for OMAP boards, replace
127 be sure to edit the line for
138 to load the appropriate kernel and
140 file at suitable addresses and start the kernel.
141 For Sheevaplugs and Openrd boards,
142 type this at U-boot once:
146 # \fItype the next two lines as one\fP
147 setenv bootcmd 'bootp; bootp; tftp 0x1000 /cfg/pxe/\fIMAC\fP; bootp;
148 tftp 0x800000; go 0x800000'
152 For Guruplugs Displays,
153 do the same but type this after
158 \&'dhcp; tftpboot; tftpboot 0x1000 /cfg/pxe/\fIMAC\fP; bootz 0x500000'
161 For Kirkwood Guruplugs,
163 .LR "setenv bootcmd" :
166 \&'dhcp 0x800000; tftp 0x1000 /cfg/pxe/\fIMAC\fP; go 0x800000'
171 .LR "setenv bootcmd" :
174 \&'tftp 0x80300000 /cfg/pxe/\fIMAC\fP; dhcp 0x80310000; go 0x80310000'
177 For Gumstix Overo boards,
179 .LR "setenv bootcmd" :
182 \&'bootp 0x80310000; bootp 0x80300000 /cfg/pxe/\fIMAC\fP; go 0x80310000'
185 Thereafter, the boards will automatically boot via BOOTP and TFTP
195 Sources for the various boot programs are under