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