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 Alpha PCs must be booted via TFTP using the SRM console.
33 If the system has ARC firmware instead, SRM may be downloaded from
36 http://www.compaq.com/
39 You must configure the SRM firmware to load the file
40 .BR /alpha/bootalphapc .
41 The following commands may be used (replace
43 with the name of your ethernet device, if different):
47 set boot_file /alpha/bootalphapc
49 set ewa0_inet_init bootp
50 set ewa0_protocols BOOTP
53 This secondary bootstrap program will first load the file
54 .BR /alpha/conf/ <IP-address>
55 (substituting the IP address of the system as obtained via bootp).
56 This file is expected to be in
59 .B /alpha/conf/10.0.0.2
60 may be used as a template).
61 It then loads the kernel via tftp, using the value of
63 to tell it which file to load; this should be
67 The Plan 9 CPU servers are multi-user, so they do not request a user name
70 Proceed as for the PC terminal, but load
72 .SS Alpha PC CPU Server
73 Proceed as for the Alpha PC terminal, but use
77 .SS SGI Challenge multiprocessor CPU Server
78 The Challenge ROM monitor can boot from the Ethernet.
79 To boot from the Ethernet, type
85 or use the ROM command
89 to that same string and type
91 To load a different file, tell
94 and to force the download to come from a particular system,
95 .BR bootp()system:file .
100 If you are running a Plan 9
104 the file name can be omitted and the
105 file specified by the
107 parameter for the machine in
109 will be downloaded by default.
111 Once the kernel is loaded,
112 it prompts for the Ethernet
113 protocol to use to reach the root file server; request the default.
116 All ARM systems are started by
118 using similar commands.
126 for the Marvell PXA168-based Guruplug Display,
128 for all Marvell Kirkwood plugs (Sheevaplug, Guruplug, Openrd, etc.),
131 for TI OMAP3 boards (IGEPv2 from ISEE, Gumstix Overo).
135 with your board's MAC address without colons,
146 file for the new CPU server.
150 cd /cfg/pxe; cp example-kw \fIMAC
156 For PXA plugs, replace
160 for OMAP boards, replace
165 be sure to edit the line for
176 to load the appropriate kernel and
178 file at suitable addresses and start the kernel.
179 For Sheevaplugs and Openrd boards,
180 type this at U-boot once:
184 # \fItype the next two lines as one\fP
185 setenv bootcmd 'bootp; bootp; tftp 0x1000 /cfg/pxe/\fIMAC\fP; bootp;
186 tftp 0x800000; go 0x800000'
190 For Guruplugs Displays,
191 do the same but type this after
196 \&'dhcp; tftpboot; tftpboot 0x1000 /cfg/pxe/\fIMAC\fP; bootz 0x500000'
199 For Kirkwood Guruplugs,
201 .LR "setenv bootcmd" :
204 \&'dhcp 0x800000; tftp 0x1000 /cfg/pxe/\fIMAC\fP; go 0x800000'
209 .LR "setenv bootcmd" :
212 \&'tftp 0x80300000 /cfg/pxe/\fIMAC\fP; dhcp 0x80310000; go 0x80310000'
215 For Gumstix Overo boards,
217 .LR "setenv bootcmd" :
220 \&'bootp 0x80310000; bootp 0x80300000 /cfg/pxe/\fIMAC\fP; go 0x80310000'
223 Thereafter, the boards will automatically boot via BOOTP and TFTP
233 Sources for the various boot programs are under