1 .\" $NetBSD: boot.8,v 1.2 2004/08/12 14:43:33 wiz Exp $
3 .\" $OpenBSD: boot_hppa.8,v 1.11 2004/05/25 22:27:44 jmc Exp $
5 .\" Copyright (c) 2002, Miodrag Vallat.
6 .\" All rights reserved.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
17 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
18 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
19 .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
20 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
21 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
22 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
23 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
24 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
25 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
26 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .Nd hp700 system bootstrapping procedures
37 When powered on, after a panic, or if the system is rebooted via
43 will proceed to its initialization, and will boot an operating system
44 if autoboot is enabled.
46 .Ss Boot process description
47 System boot blocks are provided as a
49 .Pq Logical Interchange Format
50 archive, either on a disk device, or via the network, using the
54 protocols, depending on the PDC version.
58 .\" is provided for combining primary boot and a number
59 .\" of images (OS kernels or standalone binaries)
62 .\" volume suitable for booting.
64 If autoboot is enabled, the PDC will attempt to boot from the specified
69 has been specified, the PDC will then scan for bootable devices and
70 boot from the first found, after a few seconds allowing the user to
71 interrupt the boot process.
72 If autoboot is disabled, the PDC will enter interactive mode, after an
74 In all cases, it is possible to enter interactive mode by holding the
75 escape key during the selftests, or when prompted to do so to abort
76 the current operation, unless the PDC has been configured in
82 .Dq Initial System Loader
87 On all versions of the PDC except for the 712 and 725 models the
89 command (see below) will be followed by the question:
90 .Dq Interact with IPL (Y, N, or Cancel)?\*[Gt]
91 where a positive answer will invoke an interactive prompt in the
93 program later and negative will thus suppress it.
94 A cancellation will abort the boot process.
96 On the 712 and 725 models firmware an additional
98 argument should be given to the
100 command to invoke the
103 The default behaviour is a non-interactive boot process.
105 .Ss Old PDC operation
106 This version is used on the following models:
107 705, 7x0, 715/33/50/75, 725/50/75, 735, 755.
108 There are two levels of interactive commands in this version.
109 The first level is a short menu:
110 .Bd -literal -offset indent
111 b) Boot from specified device
112 s) Search for bootable device
113 a) Enter Boot Administration mode
114 x) Exit and continue boot sequence
119 which provides the following commands:
121 .Bl -tag -width "XXX" -offset indent -compact
123 boot from a device found during the scan,
124 either with its short
126 form, or a complete name specification.
127 For example, to boot from the
129 disk with id 6 off the built-in (first) controller,
133 rescan for bootable devices.
135 enter the second part of interactive mode.
137 resume an interrupted boot sequence.
141 .Dq Boot Administration
142 mode, recognizable with its
144 prompt, controls the various boot options.
145 The complete list of commands depends on the machine and PDC version.
146 The following list only mentions commands impacting the boot process.
147 .Bl -tag -width AUTOSELECT -offset indent
149 Displays or changes the autoboot setting.
150 If autoselect is set to
152 the PDC will always attempt to boot the first bootable device found in
154 .Bl -enum -offset indent -compact
161 devices connected to the built-in
164 the highest ID numbers being preferred.
173 devices connected to secondary controllers,
174 the highest ID numbers being preferred.
178 setting defines a bootable device, no device scan will occur.
180 Boots off the specified device.
183 command from the short menu above.
188 path settings may be booted with
194 Displays or changes the boot and console devices.
195 The boot device is defined as the
197 path, and another setting may be stored as the
199 path for rescue purposes.
200 For example, to define the primary boot path to the
202 disk with ID 5 connected to the built-in controller, one would enter
203 .Ic path primary Ar scsi.5
205 When invoked without parameters,
207 will list the various path settings.
210 .Ss Modern PDC operation
211 Machines equipped with 7100LC, 7200, or 7300LC CPU types are
212 usually blessed with a different kind of PDC.
213 There is only one interactive mode, with a
215 prompt, which provides both boot settings and commands.
216 The complete list of commands depends on the machine and PDC version.
217 The following list only mentions commands impacting the boot process.
218 .Bl -tag -width auto\ search -offset indent
220 Displays or changes the autoboot setting.
225 the PDC will always attempt to boot.
226 The booted device chosen will depend on the
230 Displays or changes the device scan setting.
235 the PDC will attempt to boot the first bootable device found in
237 .Bl -enum -offset indent -compact
244 devices connected to the built-in
247 the highest ID numbers being preferred.
256 devices connected to secondary controllers,
257 the highest ID numbers being preferred.
263 and the primary boot path points to a bootable device,
264 no device scan will occur.
270 will force autoboot, regardless of the
274 Boots off the specified device.
279 path settings may be booted with
285 Displays or changes the boot and console devices.
286 The boot device is defined as the
288 path, and another setting may be stored as the
290 path for rescue purposes.
291 For example, to define the primary boot path to the
293 disk with ID 5 connected to the built-in controller, one would enter
294 .Ic path pri Ar scsi.5 .
296 When invoked without parameters,
298 will list the various path settings.
301 .Ss Abnormal system termination
302 If the system crashes, it will enter the kernel debugger,
304 if it is configured in the kernel.
305 If the crash occurred during
306 initialization and the debugger is not present or is exited, the
307 kernel will halt the system.
308 If the crash occurred during normal operation and the debugger
309 is not present or is exited, the system will attempt a dump to the
310 configured dump device (which will be automatically recovered with
312 during the next multi-user boot cycle), and after the dump is complete
313 (successful or not) the kernel will attempt a reboot.
315 .Bl -tag -width /usr/mdec/xxbootxx -compact
317 network bootstrap and kernel combined image
322 .It Pa /usr/mdec/xxboot
323 primary bootstrap for
326 .It Pa /usr/mdec/boot
327 system bootstrap (usually also installed as