| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id$ -->
|
| 3 |
|
| 4 |
<sect2 arch="ia64"><title>Booting from a CD-ROM</title>
|
| 5 |
|
| 6 |
&boot-installer-intro-cd.xml;
|
| 7 |
|
| 8 |
<note>
|
| 9 |
<title>CD Contents</title>
|
| 10 |
|
| 11 |
<para>
|
| 12 |
|
| 13 |
There are three basic variations of &debian; Install CDs.
|
| 14 |
The <emphasis>Business Card</emphasis> CD has a minimal installation
|
| 15 |
that will fit on the small form factor CD media.
|
| 16 |
It requires a network connection in order to install the rest of the
|
| 17 |
base installation and make a usable system.
|
| 18 |
The <emphasis>Network Install</emphasis> CD has all of the packages
|
| 19 |
for a base install but requires a network connection to a &debian;
|
| 20 |
mirror site in order to install the
|
| 21 |
extra packages one would want for a complete system .
|
| 22 |
The set of &debian; CDs can install a complete system from the wide
|
| 23 |
range of packages without needing access to the network.
|
| 24 |
</para>
|
| 25 |
</note>
|
| 26 |
|
| 27 |
<para>
|
| 28 |
|
| 29 |
The IA-64 architecture uses the next generation Extensible Firmware Interface
|
| 30 |
(EFI) from Intel.
|
| 31 |
Unlike the traditional x86 BIOS which knows little about the boot
|
| 32 |
device other than the partition table and Master Boot Record (MBR),
|
| 33 |
EFI can read and write files from FAT16 or FAT32 formatted disk
|
| 34 |
partitions.
|
| 35 |
This simplifies the often arcane process of starting a system.
|
| 36 |
The system boot loader and the EFI firmware that supports it have
|
| 37 |
a full filesystem to store the files necessary for booting the
|
| 38 |
machine.
|
| 39 |
This means that the system disk on an IA-64 system has an additional
|
| 40 |
disk partition dedicated to EFI instead of the simple MBR or boot
|
| 41 |
block on more conventional systems.
|
| 42 |
|
| 43 |
</para><para>
|
| 44 |
|
| 45 |
The &debian; Installer CD contains a small EFI partition where the
|
| 46 |
<command>ELILO</command> bootloader, its configuration file, the installer's
|
| 47 |
kernel, and initial filesystem (initrd) are located.
|
| 48 |
The running system also contains an EFI partition where the necessary
|
| 49 |
files for booting the system reside.
|
| 50 |
These files are readable from the EFI Shell as described below.
|
| 51 |
|
| 52 |
</para><para>
|
| 53 |
|
| 54 |
Most of the details of how <command>ELILO</command> actually loads and
|
| 55 |
starts a system are transparent to the system installer.
|
| 56 |
However, the installer must set up an EFI partition prior to installing
|
| 57 |
the base system. Otherwise, the installation of <command>ELILO</command>
|
| 58 |
will fail, rendering the system un-bootable.
|
| 59 |
The EFI partition is allocated and formatted in the partitioning step
|
| 60 |
of the installation prior to loading any packages on the system disk.
|
| 61 |
The partitioning task also verifies that a suitable EFI partition is
|
| 62 |
present before allowing the installation to proceed.
|
| 63 |
|
| 64 |
</para><para>
|
| 65 |
|
| 66 |
The EFI Boot Manager is presented as the last step of the firmware
|
| 67 |
initialization.
|
| 68 |
It displays a menu list from which the user can select
|
| 69 |
an option.
|
| 70 |
Depending on the model of system and what other software has been
|
| 71 |
loaded on the system, this menu may be different from one system
|
| 72 |
to another.
|
| 73 |
There should be at least two menu items displayed,
|
| 74 |
<command>Boot Option Maintenance Menu</command> and
|
| 75 |
<command>EFI Shell (Built-in)</command>.
|
| 76 |
Using the first option is preferred, however, if that
|
| 77 |
option is not available or the CD for some reason does not
|
| 78 |
boot with it, use the second option.
|
| 79 |
|
| 80 |
</para>
|
| 81 |
|
| 82 |
<warning>
|
| 83 |
<title>IMPORTANT</title>
|
| 84 |
<para>
|
| 85 |
The EFI Boot Manager will select a default boot action, typically
|
| 86 |
the first menu choice, within a pre-set number of seconds.
|
| 87 |
This is indicated by a countdown at the bottom of the screen.
|
| 88 |
Once the timer expires and the systems starts the default action,
|
| 89 |
you may have to reboot the machine in order to continue the installation.
|
| 90 |
If the default action is the EFI Shell, you can return to the Boot Manager
|
| 91 |
by running <command>exit</command> at the shell prompt.
|
| 92 |
</para>
|
| 93 |
</warning>
|
| 94 |
|
| 95 |
<sect3 arch="ia64" id="bootable-cd">
|
| 96 |
<title>Option 1: Booting from the Boot Option Maintenance Menu</title>
|
| 97 |
<para>
|
| 98 |
|
| 99 |
</para>
|
| 100 |
|
| 101 |
<itemizedlist>
|
| 102 |
|
| 103 |
<listitem><para>
|
| 104 |
Insert the CD in the DVD/CD drive and reboot the machine.
|
| 105 |
The firmware will display the EFI Boot Manager page and menu after
|
| 106 |
it completes its system initialization.
|
| 107 |
</para></listitem>
|
| 108 |
|
| 109 |
<listitem><para>
|
| 110 |
Select <command>Boot Maintenance Menu</command> from the menu
|
| 111 |
with the arrow keys and press <command>ENTER</command>.
|
| 112 |
This will display a new menu.
|
| 113 |
</para></listitem>
|
| 114 |
|
| 115 |
<listitem><para>
|
| 116 |
Select <command>Boot From a File</command> from the menu
|
| 117 |
with the arrow keys and press <command>ENTER</command>.
|
| 118 |
This will display a list of devices probed by the firmware.
|
| 119 |
You should see two menu lines containing either the label
|
| 120 |
<command>Debian Inst [Acpi ...</command> or
|
| 121 |
<command>Removable Media Boot</command>.
|
| 122 |
If you examine the rest of the menu line, you will notice that
|
| 123 |
the device and controller information should be the same.
|
| 124 |
</para></listitem>
|
| 125 |
|
| 126 |
<listitem><para>
|
| 127 |
You can choose either of the entries that refer to the CD/DVD
|
| 128 |
drive.
|
| 129 |
Select your choice with the arrow keys and press <command>ENTER</command>.
|
| 130 |
If you choose <command>Removable Media Boot</command> the machine
|
| 131 |
will immediately start the boot load sequence.
|
| 132 |
If you choose <command>Debian Inst [Acpi ...</command> instead, it
|
| 133 |
will display a directory listing of the bootable portion of the
|
| 134 |
CD, requiring you to proceed to the next (additional) step.
|
| 135 |
</para></listitem>
|
| 136 |
|
| 137 |
<listitem><para>
|
| 138 |
You will only need this step if you chose
|
| 139 |
<command>Debian Inst [Acpi ...</command>.
|
| 140 |
The directory listing will also show
|
| 141 |
<command>[Treat like Removable Media Boot]</command> on the next to
|
| 142 |
the last line.
|
| 143 |
Select this line with the arrow keys and press <command>ENTER</command>.
|
| 144 |
This will start the boot load sequence.
|
| 145 |
</para></listitem>
|
| 146 |
|
| 147 |
</itemizedlist>
|
| 148 |
|
| 149 |
<para>
|
| 150 |
|
| 151 |
These steps start the &debian; boot loader which will display a
|
| 152 |
menu page for you to select a boot kernel and options.
|
| 153 |
Proceed to selecting the boot kernel and options.
|
| 154 |
|
| 155 |
</para>
|
| 156 |
</sect3>
|
| 157 |
|
| 158 |
<sect3 arch="ia64" id="boot-with-efi">
|
| 159 |
<title>Option 2: Booting from the EFI Shell</title>
|
| 160 |
<para>
|
| 161 |
|
| 162 |
If, for some reason, option 1 is not successful, reboot the machine
|
| 163 |
and when the EFI Boot Manager screen appears there should be
|
| 164 |
one option called <command>EFI Shell [Built-in]</command>.
|
| 165 |
Boot the &debian; Installer CD with the following steps:
|
| 166 |
|
| 167 |
</para>
|
| 168 |
|
| 169 |
<itemizedlist>
|
| 170 |
|
| 171 |
<listitem><para>
|
| 172 |
Insert the CD in the DVD/CD drive and reboot the machine.
|
| 173 |
The firmware will display the EFI Boot Manager page and menu after
|
| 174 |
it completes system initialization.
|
| 175 |
</para></listitem>
|
| 176 |
|
| 177 |
<listitem><para>
|
| 178 |
Select <command>EFI Shell</command> from the menu with the arrow keys
|
| 179 |
and press <command>ENTER</command>.
|
| 180 |
The EFI Shell will scan all of the bootable devices and display
|
| 181 |
them to the console before displaying its command prompt.
|
| 182 |
The recognized bootable partitions on devices will show a device name of
|
| 183 |
<filename>fs<replaceable>n</replaceable>:</filename>.
|
| 184 |
All other recognized partitions will be named
|
| 185 |
<filename>blk<replaceable>n</replaceable>:</filename>.
|
| 186 |
If you inserted the CD just before entering the shell, this may
|
| 187 |
take a few extra seconds as it initializes the CD drive.
|
| 188 |
</para>
|
| 189 |
</listitem>
|
| 190 |
|
| 191 |
<listitem><para>
|
| 192 |
Examine the output from the shell looking for the CDROM drive.
|
| 193 |
It is most likely the <filename>fs0:</filename> device although
|
| 194 |
other devices with bootable partitions will also show up as
|
| 195 |
<filename>fs<replaceable>n</replaceable></filename>.
|
| 196 |
</para></listitem>
|
| 197 |
|
| 198 |
<listitem><para>
|
| 199 |
Enter <command>fs<replaceable>n</replaceable>:</command> and press
|
| 200 |
<command>ENTER</command> to select that
|
| 201 |
device where <replaceable>n</replaceable> is the partition number for the
|
| 202 |
CDROM. The shell will now display the partition number as its prompt.
|
| 203 |
</para></listitem>
|
| 204 |
|
| 205 |
<listitem><para>
|
| 206 |
Enter <command>elilo</command> and press <command>ENTER</command>.
|
| 207 |
This will start the boot load sequence.
|
| 208 |
</para></listitem>
|
| 209 |
|
| 210 |
</itemizedlist>
|
| 211 |
|
| 212 |
<para>
|
| 213 |
|
| 214 |
As with option 1, these steps start the &debian; boot loader which will
|
| 215 |
display a menu page for you to select a boot kernel and options.
|
| 216 |
You can also enter the shorter
|
| 217 |
<command>fs<replaceable>n</replaceable>:elilo</command> command at
|
| 218 |
the shell prompt.
|
| 219 |
Proceed to selecting the boot kernel and options.
|
| 220 |
|
| 221 |
</para>
|
| 222 |
|
| 223 |
</sect3>
|
| 224 |
|
| 225 |
<sect3 arch="ia64" id="serial-console">
|
| 226 |
<title>Installing using a Serial Console</title>
|
| 227 |
|
| 228 |
<para>
|
| 229 |
|
| 230 |
You may choose to perform an install using a monitor and keyboard
|
| 231 |
or using a serial connection. To use a monitor/keyboard setup,
|
| 232 |
select an option containing the string [VGA console]. To install
|
| 233 |
over a serial connection, choose an option containing the string
|
| 234 |
[<replaceable>BAUD</replaceable> baud serial console], where
|
| 235 |
<replaceable>BAUD</replaceable> is the speed of your serial console.
|
| 236 |
Menu items for the most typical baud rate settings on the ttyS0
|
| 237 |
device are preconfigured.
|
| 238 |
|
| 239 |
</para><para>
|
| 240 |
|
| 241 |
In most circumstances, you will want the installer to use the same
|
| 242 |
baud rate as your connection to the EFI console. If you aren't
|
| 243 |
sure what this setting is, you can obtain it using the command
|
| 244 |
<command>baud</command> at the EFI shell.
|
| 245 |
|
| 246 |
</para><para>
|
| 247 |
|
| 248 |
If there is not an option available that is configured for the serial
|
| 249 |
device or baud rate you would like to use, you may override the console setting
|
| 250 |
for one of the existing menu options. For example, to use a
|
| 251 |
57600 baud console over the ttyS1 device, enter
|
| 252 |
<command>console=ttyS1,57600n8</command> into
|
| 253 |
the <classname>Boot:</classname> text window.
|
| 254 |
|
| 255 |
</para>
|
| 256 |
|
| 257 |
<note><para>
|
| 258 |
Most IA-64 boxes ship with a default console setting of 9600 baud.
|
| 259 |
This setting is rather slow, and the normal installation process
|
| 260 |
will take a significant time to draw each screen. You should consider
|
| 261 |
either increasing the baud rate used for performing the installation,
|
| 262 |
or performing a Text Mode installation. See the <classname>Params</classname>
|
| 263 |
help menu for instructions on starting the installer in Text Mode.
|
| 264 |
</para></note>
|
| 265 |
|
| 266 |
<warning><para>
|
| 267 |
If you select the wrong console type, you
|
| 268 |
will be able to select the kernel and enter parameters but both
|
| 269 |
the display and your input will go dead as soon as the kernel starts,
|
| 270 |
requiring you to reboot before you can begin the installation.
|
| 271 |
</para></warning>
|
| 272 |
</sect3>
|
| 273 |
|
| 274 |
<sect3 arch="ia64" id="kernel-option-menu">
|
| 275 |
<title>Selecting the Boot Kernel and Options</title>
|
| 276 |
|
| 277 |
<para>
|
| 278 |
|
| 279 |
The boot loader will display a form with a menu list and a text
|
| 280 |
window with a <classname>Boot:</classname> prompt.
|
| 281 |
The arrow keys select an item from the menu and any text typed
|
| 282 |
at the keyboard will appear in the text window.
|
| 283 |
There are also help screens which can be displayed by pressing
|
| 284 |
the appropriate function key.
|
| 285 |
The <classname>General</classname> help screen explains the menu
|
| 286 |
choices and the <classname>Params</classname> screen explains
|
| 287 |
the common command line options.
|
| 288 |
|
| 289 |
</para><para>
|
| 290 |
|
| 291 |
Consult the <classname>General</classname> help screen for the
|
| 292 |
description of the kernels and install modes most appropriate
|
| 293 |
for your installation.
|
| 294 |
You should also consult <xref linkend="boot-parms"/> below for any additional
|
| 295 |
parameters that you may want to set in the <classname>Boot:</classname>
|
| 296 |
text window.
|
| 297 |
The kernel version you choose selects the kernel version that will be
|
| 298 |
used for both the installation process and the installed system.
|
| 299 |
If you encounter kernel problems with the installation, you may also
|
| 300 |
have those same problems with the system you install.
|
| 301 |
The following two steps will select and start the install:
|
| 302 |
|
| 303 |
</para>
|
| 304 |
|
| 305 |
<itemizedlist>
|
| 306 |
|
| 307 |
<listitem><para>
|
| 308 |
Select the kernel version and installation mode most
|
| 309 |
appropriate to your needs with the arrow keys.
|
| 310 |
</para></listitem>
|
| 311 |
|
| 312 |
<listitem><para>
|
| 313 |
Enter any boot parameters by typing at the keyboard.
|
| 314 |
The text will be displayed directly in the text window.
|
| 315 |
This is where kernel parameters (such as serial console
|
| 316 |
settings) are specified.
|
| 317 |
</para></listitem>
|
| 318 |
|
| 319 |
<listitem><para>
|
| 320 |
Press <command>ENTER</command>. This will load and start the
|
| 321 |
kernel.
|
| 322 |
The kernel will display its usual initialization messages followed
|
| 323 |
by the first screen of the &debian; Installer.
|
| 324 |
</para></listitem>
|
| 325 |
|
| 326 |
</itemizedlist>
|
| 327 |
|
| 328 |
<para>
|
| 329 |
|
| 330 |
Proceed to the next chapter to continue the installation where you will
|
| 331 |
set up the language locale, network, and disk partitions.
|
| 332 |
|
| 333 |
</para>
|
| 334 |
</sect3>
|
| 335 |
</sect2>
|
| 336 |
|
| 337 |
<sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>
|
| 338 |
|
| 339 |
<para>
|
| 340 |
Booting an IA-64 system from the network is similar to a CD boot.
|
| 341 |
The only difference is how the installation kernel is loaded.
|
| 342 |
The EFI Boot Manager can load and start programs from a server on
|
| 343 |
the network.
|
| 344 |
Once the installation kernel is loaded and starts, the system install
|
| 345 |
will proceed through the same steps as the CD install with the exception
|
| 346 |
that the packages of the base install will be loaded from the network
|
| 347 |
rather than the CD drive.
|
| 348 |
|
| 349 |
</para>
|
| 350 |
|
| 351 |
&boot-installer-intro-net.xml;
|
| 352 |
|
| 353 |
<para>
|
| 354 |
|
| 355 |
Network booting an IA-64 system requires two architecture-specific actions.
|
| 356 |
On the boot server, DHCP and TFTP must be configured to deliver
|
| 357 |
<command>elilo</command>.
|
| 358 |
On the client a new boot option must be defined in the EFI boot manager
|
| 359 |
to enable loading over a network.
|
| 360 |
|
| 361 |
</para>
|
| 362 |
|
| 363 |
<sect3 arch="ia64" id="boot-tftp-server">
|
| 364 |
<title>Configuring the Server</title>
|
| 365 |
<para>
|
| 366 |
|
| 367 |
A suitable TFTP entry for network booting an IA-64 system looks something
|
| 368 |
like this:
|
| 369 |
|
| 370 |
<informalexample><screen>
|
| 371 |
host mcmuffin {
|
| 372 |
hardware ethernet 00:30:6e:1e:0e:83;
|
| 373 |
fixed-address 10.0.0.21;
|
| 374 |
filename "debian-installer/ia64/elilo.efi";
|
| 375 |
}
|
| 376 |
</screen></informalexample>
|
| 377 |
|
| 378 |
Note that the goal is to get <command>elilo.efi</command> running on
|
| 379 |
the client.
|
| 380 |
|
| 381 |
</para><para>
|
| 382 |
|
| 383 |
Extract the <filename>netboot.tar.gz</filename> file into the directory used
|
| 384 |
as the root for your tftp server. Typical tftp root directories include
|
| 385 |
<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>.
|
| 386 |
This will create a <filename>debian-installer</filename> directory
|
| 387 |
tree containing the boot files for an IA-64 system.
|
| 388 |
|
| 389 |
</para><para>
|
| 390 |
|
| 391 |
<informalexample><screen>
|
| 392 |
# cd /var/lib/tftp
|
| 393 |
# tar xvfz /home/user/netboot.tar.gz
|
| 394 |
./
|
| 395 |
./debian-installer/
|
| 396 |
./debian-installer/ia64/
|
| 397 |
[...]
|
| 398 |
</screen></informalexample>
|
| 399 |
|
| 400 |
The <filename>netboot.tar.gz</filename> contains an
|
| 401 |
<filename>elilo.conf</filename> file that should work for most configurations.
|
| 402 |
However, should you need to make changes to this file, you can find it in the
|
| 403 |
<filename>debian-installer/ia64/</filename> directory.
|
| 404 |
|
| 405 |
It is possible to have different config files for different clients by naming
|
| 406 |
them using the client's IP address in hex with the suffix
|
| 407 |
<filename>.conf</filename> instead of <filename>elilo.conf</filename>.
|
| 408 |
See documentation provided in the <classname>elilo</classname> package
|
| 409 |
for details.
|
| 410 |
|
| 411 |
</para>
|
| 412 |
</sect3>
|
| 413 |
|
| 414 |
<sect3 arch="ia64" id="boot-tftp-client">
|
| 415 |
<title>Configuring the Client</title>
|
| 416 |
<para>
|
| 417 |
|
| 418 |
To configure the client to support TFTP booting, start by booting to
|
| 419 |
EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>.
|
| 420 |
|
| 421 |
<itemizedlist>
|
| 422 |
<listitem><para>
|
| 423 |
|
| 424 |
Add a boot option.
|
| 425 |
|
| 426 |
</para></listitem>
|
| 427 |
<listitem><para>
|
| 428 |
|
| 429 |
You should see one or more lines with the text
|
| 430 |
<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more
|
| 431 |
than one of these entries exist, choose the one containing the
|
| 432 |
MAC address of the interface from which you'll be booting.
|
| 433 |
Use the arrow keys to highlight your choice, then press enter.
|
| 434 |
|
| 435 |
</para></listitem>
|
| 436 |
<listitem><para>
|
| 437 |
|
| 438 |
Name the entry <userinput>Netboot</userinput> or something similar,
|
| 439 |
save, and exit back to the boot options menu.
|
| 440 |
|
| 441 |
</para></listitem>
|
| 442 |
</itemizedlist>
|
| 443 |
|
| 444 |
You should see the new boot option you just created, and selecting it
|
| 445 |
should initiate a DHCP query, leading to a TFTP load of
|
| 446 |
<filename>elilo.efi</filename> from the server.
|
| 447 |
|
| 448 |
</para><para>
|
| 449 |
|
| 450 |
The boot loader will display its prompt after it has downloaded and
|
| 451 |
processed its configuration file.
|
| 452 |
At this point, the installation proceeds with the same steps as a
|
| 453 |
CD install. Select a boot option as in above and when the kernel
|
| 454 |
has completed installing itself from the network, it will start the
|
| 455 |
&debian; Installer.
|
| 456 |
|
| 457 |
</para><para>
|
| 458 |
|
| 459 |
Proceed to the next chapter to continue the installation where
|
| 460 |
you will set up the language locale, network, and disk partitions.
|
| 461 |
|
| 462 |
</para>
|
| 463 |
</sect3>
|
| 464 |
</sect2>
|
Parent Directory
| 
Revision Log