xref: /netbsd-src/share/man/man8/man8.hppa/boot.8 (revision 01869ca4d24a86379a68731bf9706a9f0820fe4e)
1.\"	$NetBSD: boot.8,v 1.2 2017/07/03 21:31:00 wiz Exp $
2.\"
3.\"	$OpenBSD: boot_hppa.8,v 1.11 2004/05/25 22:27:44 jmc Exp $
4.\"
5.\" Copyright (c) 2002, Miodrag Vallat.
6.\" All rights reserved.
7.\"
8.\" Redistribution and use in source and binary forms, with or without
9.\" modification, are permitted provided that the following conditions
10.\" are met:
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.
16.\"
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
27.\" SUCH DAMAGE.
28.\"
29.Dd July 27, 2004
30.Dt BOOT 8 hppa
31.Os
32.Sh NAME
33.Nm boot
34.Nd hppa system bootstrapping procedures
35.Sh DESCRIPTION
36.Ss System starts
37When powered on, after a panic, or if the system is rebooted via
38.Xr reboot 8
39or
40.Xr shutdown 8 ,
41the hppa firmware
42.Pq Dq PDC
43will proceed to its initialization, and will boot an operating system
44if autoboot is enabled.
45.\"
46.Ss Boot process description
47System boot blocks are provided as a
48.Dq LIF
49.Pq Logical Interchange Format
50archive, either on a disk device, or via the network, using the
51.Em bootp
52or
53.Em rboot
54protocols, depending on the PDC version.
55.\" A small
56.\" .Xr mkboot 8
57.\" utility
58.\" is provided for combining primary boot and a number
59.\" of images (OS kernels or standalone binaries)
60.\" into one
61.\" .Dq LIF
62.\" volume suitable for booting.
63.Ss PDC concepts
64If autoboot is enabled, the PDC will attempt to boot from the specified
65.Dq boot path
66value.
67If no
68.Dq boot path
69has been specified, the PDC will then scan for bootable devices and
70boot from the first found, after a few seconds allowing the user to
71interrupt the boot process.
72If autoboot is disabled, the PDC will enter interactive mode, after an
73optional device scan.
74In all cases, it is possible to enter interactive mode by holding the
75escape key during the selftests, or when prompted to do so to abort
76the current operation, unless the PDC has been configured in
77.Dq secure mode .
78.\"
79.Ss ISL interaction
80.Dq ISL
81stands for
82.Dq Initial System Loader
83and is the
84.Nm
85program in
86.Nx .
87On all versions of the PDC except for the 712 and 725 models the
88.Dq boot
89command (see below) will be followed by the question:
90.Dq Interact with IPL (Y, N, or Cancel)?>
91where a positive answer will invoke an interactive prompt in the
92.Nm
93program later and negative will thus suppress it.
94A cancellation will abort the boot process.
95.Pp
96On the 712 and 725 models firmware an additional
97.Dq isl
98argument should be given to the
99.Dq boot
100command to invoke the
101.Nm
102interactive prompt.
103The default behaviour is a non-interactive boot process.
104.\"
105.Ss Old PDC operation
106This version is used on the following models:
107705, 7x0, 715/33/50/75, 725/50/75, 735, 755.
108There are two levels of interactive commands in this version.
109The first level is a short menu:
110.Bd -literal -offset indent
111b)   Boot from specified device
112s)   Search for bootable device
113a)   Enter Boot Administration mode
114x)   Exit and continue boot sequence
115
116Select from menu:
117.Ed
118.Pp
119which provides the following commands:
120.Pp
121.Bl -tag -width "XXX" -offset indent -compact
122.It Cm b
123boot from a device found during the scan,
124either with its short
125.Dq P#
126form, or a complete name specification.
127For example, to boot from the
128.Tn SCSI
129disk with id 6 off the built-in (first) controller,
130one would enter
131.Ic b Ar scsi.6.0 .
132.It Cm s
133rescan for bootable devices.
134.It Cm a
135enter the second part of interactive mode.
136.It Cm x
137resume an interrupted boot sequence.
138.El
139.Pp
140The
141.Dq Boot Administration
142mode, recognizable with its
143.Em BOOT_ADMIN>
144prompt, controls the various boot options.
145The complete list of commands depends on the machine and PDC version.
146The following list only mentions commands impacting the boot process.
147.Bl -tag -width AUTOSELECT -offset indent
148.It AUTOSELECT
149Displays or changes the autoboot setting.
150If autoselect is set to
151.Dq on ,
152the PDC will always attempt to boot the first bootable device found in
153this order:
154.Bl -enum -offset indent -compact
155.It
156Boot device
157.Em path
158setting.
159.It
160.Tn SCSI
161devices connected to the built-in
162.Tn SCSI
163controller,
164the highest ID numbers being preferred.
165.It
166Network
167.Em rboot
168server (see also
169.Xr rbootd 8 ) .
170.It
171Other
172.Tn SCSI
173devices connected to secondary controllers,
174the highest ID numbers being preferred.
175.El
176If the
177.Em primary path
178setting defines a bootable device, no device scan will occur.
179.It BOOT
180Boots off the specified device.
181It is similar to the
182.Ic b
183command from the short menu above.
184The
185.Dq primary
186and
187.Dq alternate
188path settings may be booted with
189.Ic boot Ar pri
190and
191.Ic boot Ar alt
192respectively.
193.It PATH
194Displays or changes the boot and console devices.
195The boot device is defined as the
196.Dq primary
197path, and another setting may be stored as the
198.Dq alternate
199path for rescue purposes.
200For example, to define the primary boot path to the
201.Tn SCSI
202disk with ID 5 connected to the built-in controller, one would enter
203.Ic path primary Ar scsi.5
204.Pp
205When invoked without parameters,
206.Ic path
207will list the various path settings.
208.El
209.\"
210.Ss Modern PDC operation
211Machines equipped with 7100LC, 7200, or 7300LC CPU types are
212usually blessed with a different kind of PDC.
213There is only one interactive mode, with a
214.Em BOOT_ADMIN>
215prompt, which provides both boot settings and commands.
216The complete list of commands depends on the machine and PDC version.
217The following list only mentions commands impacting the boot process.
218.Bl -tag -width auto\ search -offset indent
219.It Ic auto boot
220Displays or changes the autoboot setting.
221If
222.Ic auto boot
223is set to
224.Dq on ,
225the PDC will always attempt to boot.
226The booted device chosen will depend on the
227.Ic auto search
228setting.
229.It Ic auto search
230Displays or changes the device scan setting.
231If
232.Ic auto search
233is set to
234.Dq on ,
235the PDC will attempt to boot the first bootable device found in
236this order:
237.Bl -enum -offset indent -compact
238.It
239Boot device
240.Em path
241setting.
242.It
243.Tn SCSI
244devices connected to the built-in
245.Tn SCSI
246controller,
247the highest ID numbers being preferred.
248.It
249Network
250.Em bootp
251server (see also
252.Xr dhcpd 8 ) .
253.It
254Other
255.Tn SCSI
256devices connected to secondary controllers,
257the highest ID numbers being preferred.
258.El
259If
260.Ic auto search
261is set to
262.Dq off
263and the primary boot path points to a bootable device,
264no device scan will occur.
265.Pp
266Note that setting
267.Ic auto search
268to
269.Dq on
270will force autoboot, regardless of the
271.Ic auto boot
272value.
273.It Ic boot
274Boots off the specified device.
275The
276.Dq primary
277and
278.Dq alternate
279path settings may be booted with
280.Ic boot Ar pri
281and
282.Ic boot Ar alt
283respectively.
284.It Ic path
285Displays or changes the boot and console devices.
286The boot device is defined as the
287.Dq primary
288path, and another setting may be stored as the
289.Dq alternate
290path for rescue purposes.
291For example, to define the primary boot path to the
292.Tn SCSI
293disk with ID 5 connected to the built-in controller, one would enter
294.Ic path pri Ar scsi.5 .
295.Pp
296When invoked without parameters,
297.Ic path
298will list the various path settings.
299.El
300.\"
301.Ss Abnormal system termination
302If the system crashes, it will enter the kernel debugger,
303.Xr ddb 4 ,
304if it is configured in the kernel.
305If the crash occurred during
306initialization and the debugger is not present or is exited, the
307kernel will halt the system.
308If the crash occurred during normal operation and the debugger
309is not present or is exited, the system will attempt a dump to the
310configured dump device (which will be automatically recovered with
311.Xr savecore 8
312during the next multi-user boot cycle), and after the dump is complete
313(successful or not) the kernel will attempt a reboot.
314.Sh FILES
315.Bl -tag -width /usr/mdec/xxbootxx -compact
316.It Pa boot.lif
317network bootstrap and kernel combined image
318.It Pa /netbsd
319default
320.Nx
321system kernel
322.It Pa /usr/mdec/xxboot
323primary bootstrap for
324.Dq ffs
325file system
326.It Pa /usr/mdec/boot
327system bootstrap (usually also installed as
328.Pa /boot )
329.El
330.Sh SEE ALSO
331.Xr ddb 4 ,
332.Xr dhcpd 8 ,
333.Xr halt 8 ,
334.Xr init 8 ,
335.Xr installboot 8 ,
336.Xr rbootd 8 ,
337.Xr reboot 8 ,
338.Xr savecore 8 ,
339.Xr shutdown 8
340