1 .\" Copyright (c) 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software written and contributed
5 .\" to Berkeley by William Jolitz.
7 .\" Almost completely rewritten for FreeBSD 2.1 by Joerg Wunsch.
9 .\" Substantially revised for FreeBSD 3.1 by Robert Nordier.
11 .\" Redistribution and use in source and binary forms, with or without
12 .\" modification, are permitted provided that the following conditions
14 .\" 1. Redistributions of source code must retain the above copyright
15 .\" notice, this list of conditions and the following disclaimer.
16 .\" 2. Redistributions in binary form must reproduce the above copyright
17 .\" notice, this list of conditions and the following disclaimer in the
18 .\" documentation and/or other materials provided with the distribution.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" @(#)boot_i386.8 8.2 (Berkeley) 4/19/94
44 .Nd system bootstrapping procedures
46 .Sy Power fail and crash recovery .
47 Normally, the system will reboot itself at power-up or after crashes.
48 An automatic consistency check of the file systems will be performed,
49 and unless this fails, the system will resume multi-user operations.
52 Most i386 PCs attempt to boot first from floppy disk drive 0 (sometimes
53 known as drive A:) and, failing that, from hard disk drive 0 (sometimes
54 known as drive C:, or as drive 0x80 to the BIOS).
56 you to change this default sequence, and may also include a CD-ROM
57 drive as a boot device.
59 By default, a three-stage bootstrap is employed, and control is
60 automatically passed from the boot blocks (bootstrap stages one and
61 two) to a separate third-stage bootstrap program,
63 This third stage provides more sophisticated control over the booting
64 process than it is possible to achieve in the boot blocks, which are
65 constrained by occupying limited fixed space on a given disk or slice.
67 However, it is possible to dispense with the third stage altogether,
68 either by specifying a kernel name in the boot block parameter
73 is set, by hitting a key during a brief pause (while one of the characters
82 Booting will also be attempted at stage two, if the
83 third stage cannot be loaded.
85 Make note of the fact that
89 partition. As a result, slices which are missing an
91 parition require user intervention during the boot process.
93 The remainder of this subsection deals only with the boot blocks.
96 program is documented separately.
98 After the boot blocks have been loaded,
99 you should see a prompt similar to the following:
102 Default: 0:ad(0,a)/boot/loader
106 The automatic boot will attempt to load
110 of either the floppy or the hard disk.
111 This boot may be aborted by typing any character on the keyboard
115 At this time, the following input will be accepted:
116 .Bl -tag -width indent
118 Give a short listing of the files in the root directory of the default
119 boot device, as a hint about available boot files.
122 may also be specified as the last segment of a path, in which case
123 the listing will be of the relevant subdirectory.)
127 .Ar bios_drive : interface ( unit , Oo Ar slice , Oc Ar part )
130 .Op Fl aCcDdghmnPprsv
132 Specify boot file and flags.
133 .Bl -tag -width indent
135 The drive number as recognized by the BIOS.
136 0 for the first drive, 1 for the second drive, etc.
138 The type of controller to boot from.
139 Note that the controller is required
140 to have BIOS support since the BIOS services are used to load the
143 The supported interfaces are:
145 .Bl -tag -width "adXX" -compact
147 ST506, IDE, ESDI, RLL disks on a WD100[2367] or lookalike
150 5 1/4" or 3 1/2" High density floppies
152 SCSI disk on any supported SCSI controller
157 The unit number of the drive on the interface being used.
158 0 for the first drive, 1 for the second drive, etc.
159 .It Oo Ar slice , Oc Ns Ar part
160 The partition letter inside the
165 By convention, only partition
167 contains a bootable image.
168 If sliced disks are used
169 .Pq Dq fdisk partitions ,
172 (1 for the first slice, 2 for the second slice, etc.\&)
173 can be booted from, with the default (if not specified) being the active slice
174 or, otherwise, the first
179 is specified as 0, the first
183 slice) is booted from.
185 The pathname of the file to boot (relative to the root directory
186 on the specified partition).
189 Symbolic links are not supported (hard links are).
190 .It Fl aCcDdghmnPprsv
193 .Bl -tag -width "-CXX" -compact
195 during kernel initialization,
196 ask for the device to mount as the root file system.
200 run UserConfig to modify hardware parameters for the loaded
202 If the kernel was built with one of
203 .Dv USERCONFIG , INTRO_USERCONFIG , VISUAL_USERCONFIG
205 remain in UserConfig regardless of any
207 commands present in the script.
209 toggle single and dual console configurations.
211 configuration the console will be either the internal display
212 or the serial port, depending on the state of the
215 In the dual console configuration,
216 both the internal display and the serial port will become the console
217 at the same time, regardless of the state of the
220 However, the dual console configuration takes effect only during
222 Once the kernel is loaded, the console specified
225 option becomes the only console.
227 enter the DDB kernel debugger
230 as early as possible in kernel initialization.
232 use the GDB remote debugging protocol.
234 toggle internal and serial consoles.
235 You can use this to switch
237 For instance, if you boot from the internal console,
240 option to force the kernel to use the serial port as its
242 Alternatively, if you boot from the serial port,
243 you can use this option to force the kernel to use the internal display
244 as the console instead.
245 The serial port driver
247 has a flag to override this option.
248 If that flag is set, the serial port will always be used as the console,
251 option described here.
258 ignore key press to interrupt boot before
263 If no keyboard is found, the
267 options are automatically set.
269 pause after each attached device during the device probing phase.
271 use the statically configured default for the device containing the
275 Normally, the root file system is on the device
276 that the kernel was loaded from.
278 boot into single-user mode; if the console is marked as
282 the root password must be entered.
284 be verbose during device probing (and later).
289 You may put a BIOS drive number, a controller type, a unit number,
290 a partition, a kernel file name, and any valid option in
293 Enter them in one line just as you type at the
297 .Bl -tag -width /boot/loader -compact
299 parameters for the boot blocks (optional)
301 first stage bootstrap file
303 second stage bootstrap file
305 third stage bootstrap
306 .It Pa /boot/kernel/kernel
308 .It Pa /boot/kernel.old/kernel
309 typical non-default kernel (optional)
323 When disk-related errors occur, these are reported by the second-stage
324 bootstrap using the same error codes returned by the BIOS, for example
325 .Dq Disk error 0x1 (lba=0x12345678) .
326 Here is a partial list of these error codes:
328 .Bl -tag -width "0x80" -compact
332 Address mark not found
338 DMA attempt across 64K boundary
342 Uncorrectable CRC/ECC error
352 On older machines, or otherwise where EDD support (disk packet
353 interface support) is not available, all boot-related files and
354 structures (including the kernel) that need to be accessed during the
355 boot phase must reside on the disk at or below cylinder 1023 (as the
356 BIOS understands the geometry).
359 is reported by the second-stage bootstrap, it generally means that this
360 requirement has not been adhered to.
364 format used by this version of
367 different from that of other architectures.
369 Due to space constraints, the keyboard probe initiated by the
371 option is simply a test that the BIOS has detected an
376 keyboard (with no F11 and F12 keys, etc.) is attached, the probe will