1.\" $OpenBSD: boot_hppa.8,v 1.7 2003/07/10 08:30:36 jmc Exp $ 2.\" 3.\" Copyright (c) 2002, Miodrag Vallat. 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 15.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 16.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 17.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 18.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 19.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 20.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 21.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 23.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 24.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 25.\" SUCH DAMAGE. 26.\" 27.Dd October 16, 2002 28.Dt BOOT_HPPA 8 hppa 29.Os 30.Sh NAME 31.Nm boot_hppa 32.Nd hppa system bootstrapping procedures 33.Sh DESCRIPTION 34.Ss System starts 35When powered on, after a panic, or if the system is rebooted via 36.Xr reboot 8 37or 38.Xr shutdown 8 , 39the hppa firmware 40.Pq Dq PDC 41will proceed to its initialization, and will boot an operating system 42if autoboot is enabled. 43.\" 44.Ss Boot process description 45System boot blocks are provided as a 46.Dq LIF 47.Pq Logical Interchange Format 48archive, either on a disk device, or via the network, using the 49.Em bootp 50or 51.Em rboot 52protocols, depending on the PDC version. 53.Ss PDC concepts 54If autoboot is enabled, the PDC will attempt to boot from the specified 55.Dq boot path 56value. 57If no 58.Dq boot path 59has been specified, the PDC will then scan for bootable devices and 60boot from the first found, after a few seconds allowing the user to 61interrupt the boot process. 62If autoboot is disabled, the PDC will enter interactive mode, after an 63optional device scan. 64In all cases, it is possible to enter interactive mode by holding the 65escape key during the selftests, or when prompted to do so to abort 66the current operation, unless the PDC has been configured in 67.Dq secure mode . 68.\" 69.Ss ISL interaction 70.Dq ISL 71stands for 72.Dq Initial System Loader 73and is the 74.Xr boot 8 75program in 76.Ox . 77On all versions of the PDC except for the 712 models the 78.Dq boot 79command (see below) will be followed by the question: 80.Dq Interact with IPL (Y, N, or Cancel)?> 81where a positive answer will invoke an interactive prompt in the 82.Xr boot 8 83program later and negative will thus suppress it. 84A cancellation will abort the boot process. 85.Pp 86On the 712 models firmware an additional 87.Dq isl 88argument should be given to the 89.Dq boot 90command to invoke the 91.Xr boot 8 92interactive prompt. 93With the default behaviour being a non-interactive boot process. 94.\" 95.Ss Old PDC operation 96PDC ROM v1.4 and below are easily recognizable, 97as they will start with a text banner. 98There are two levels of interactive commands in this version. 99The first level is a short menu: 100.Bd -literal -offset indent 101b) Boot from specified device 102s) Search for bootable device 103a) Enter Boot Administration mode 104x) Exit and continue boot sequence 105 106Select from menu: 107.Ed 108.Pp 109which provides the following commands: 110.Bl -tag -width "XXX" -offset indent -compact 111.Pp 112.It Cm b 113boot from a device found during the scan, 114either with its short 115.Dq P# 116form, or a complete name specification. 117For example, to boot from the 118.Tn SCSI 119disk with id 6 off the built-in (first) controller, 120one would enter 121.Ic b Ar scsi.6.0 . 122.It Cm s 123rescan for bootable devices. 124.It Cm a 125enter the second part of interactive mode. 126.It Cm x 127resume an interrupted boot sequence. 128.El 129.Pp 130The 131.Dq Boot Administration 132mode, recognizable with its 133.Em BOOT_ADMIN> 134prompt, controls the various boot options. 135The complete list of commands depends on the machine and PDC version. 136The following list only mentions commands impacting the boot process. 137.Bl -tag -width AUTOSELECT -offset indent 138.It AUTOSELECT 139Displays or changes the autoboot setting. 140If autoselect is set to 141.Dq on , 142the PDC will always attempt to boot the first bootable device found in 143this order: 144.Bl -enum -offset indent -compact 145.It 146Boot device 147.Em path 148setting. 149.It 150.Tn SCSI 151devices connected to the built-in 152.Tn SCSI 153controller, 154the highest ID numbers being preferred. 155.It 156Network 157.Em rboot 158server. 159.It 160Other 161.Tn SCSI 162devices connected to secondary controllers, 163the highest ID numbers being preferred. 164.El 165If the 166.Em primary path 167setting defines a bootable device, no device scan will occur. 168.It BOOT 169Boots off the specified device. 170It is similar to the 171.Ic b 172command from the short menu above. 173The 174.Dq primary 175and 176.Dq alternate 177path settings may be booted with 178.Ic boot Ar pri 179and 180.Ic boot Ar alt 181respectively. 182.It PATH 183Displays or changes the boot and console devices. 184The boot device is defined as the 185.Dq primary 186path, and another setting may be stored as the 187.Dq alternate 188path for rescue purposes. 189For example, to define the primary boot path to the 190.Tn SCSI 191disk with ID 5 connected to the built-in controller, one would enter 192.Ic path primary Ar scsi.5 193.Pp 194When invoked without parameters, 195.Ic path 196will list the various path settings. 197.El 198.\" 199.Ss Modern PDC operation 200PDC ROM 1.5 and above will start with a small graphics window at the 201screen center (unless you are using a serial console). 202There is only one interactive mode, with a 203.Em BOOT_ADMIN> 204prompt, which provides both boot settings and commands. 205The complete list of commands depends on the machine and PDC version. 206The following list only mentions commands impacting the boot process. 207.Bl -tag -width auto\ search -offset indent 208.It Ic auto boot 209Displays or changes the autoboot setting. 210If 211.Ic auto boot 212is set to 213.Dq on , 214the PDC will always attempt to boot. 215The booted device chosen will depend on the 216.Ic auto search 217setting. 218.It Ic auto search 219Displays or changes the device scan setting. 220If 221.Ic auto search 222is set to 223.Dq on , 224the PDC will attempt to boot the first bootable device found in 225this order: 226.Bl -enum -offset indent -compact 227.It 228Boot device 229.Em path 230setting. 231.It 232.Tn SCSI 233devices connected to the built-in 234.Tn SCSI 235controller, 236the highest ID numbers being preferred. 237.It 238Network 239.Em bootp 240server. 241.It 242Other 243.Tn SCSI 244devices connected to secondary controllers, 245the highest ID numbers being preferred. 246.El 247If 248.Ic auto search 249is set to 250.Dq off 251and the primary boot path points to a bootable device, 252no device scan will occur. 253.Pp 254Note that setting 255.Ic auto search 256to 257.Dq on 258will force autoboot, regardless of the 259.Ic auto boot 260value. 261.It Ic boot 262Boots off the specified device. 263The 264.Dq primary 265and 266.Dq alternate 267path settings may be booted with 268.Ic boot Ar pri 269and 270.Ic boot Ar alt 271respectively. 272.It Ic path 273Displays or changes the boot and console devices. 274The boot device is defined as the 275.Dq primary 276path, and another setting may be stored as the 277.Dq alternate 278path for rescue purposes. 279For example, to define the primary boot path to the 280.Tn SCSI 281disk with ID 5 connected to the built-in controller, one would enter 282.Ic path pri Ar scsi.5 283.Pp 284When invoked without parameters, 285.Ic path 286will list the various path settings. 287.El 288.\" 289.Ss Boot process options 290The 291.Ox 292hppa boot loader program is extensively described in a separate document, 293.Xr boot 8 . 294.Ss Abnormal system termination 295If the system crashes, it will enter the kernel debugger, 296.Xr ddb 4 , 297if it is configured in the kernel. 298If the crash occurred during 299initialization and the debugger is not present or is exited, the 300kernel will halt the system. 301If the crash occurred during normal operation and the debugger 302is not present or is exited, the system will attempt a dump to the 303configured dump device (which will be automatically recovered with 304.Xr savecore 8 305during the next multi-user boot cycle), and after the dump is complete 306(successful or not) the kernel will attempt a reboot. 307.Sh FILES 308.Bl -tag -width boot.lif -compact 309.It Pa /bsd 310default system kernel 311.It Pa boot.lif 312network bootstrap and kernel combined image 313.\" .It Pa /usr/mdec/boot 314.\" system bootstrap (usually also installed as 315.\" .Pa /boot ) 316.El 317.Sh SEE ALSO 318.Xr ddb 4 , 319.Xr boot 8 , 320.Xr halt 8 , 321.Xr init 8 , 322.\" .Xr installboot 8 , 323.Xr reboot 8 , 324.Xr savecore 8 , 325.Xr shutdown 8 326