/[d-i]/trunk/installer/doc/manual/nl/boot-installer/ia64.xml
ViewVC logotype

Contents of /trunk/installer/doc/manual/nl/boot-installer/ia64.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 22973 - (show annotations) (download) (as text)
Sun Oct 10 18:01:42 2004 UTC (8 years, 7 months ago) by fjpop-guest
File MIME type: text/xml
File size: 15802 byte(s)
Update of Dutch translation
1 <!-- retain these comments for translator revision tracking -->
2 <!-- original version: 22919 untranslated -->
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<emphasis>n</emphasis>:</filename>.
184 All other recognized partitions will be named
185 <filename>blk<emphasis>n</emphasis>:</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<emphasis>n</emphasis></filename>.
196 </para></listitem>
197
198 <listitem><para>
199 Enter <command>fs<emphasis>n</emphasis>:</command> and press
200 <command>ENTER</command> to select that
201 device where <emphasis>n</emphasis> 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<emphasis>n</emphasis>: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="kernel-option-menu">
226 <title>Selecting the Boot Kernel and Options</title>
227
228 <para>
229
230 The boot loader will display a form with a menu list and a text
231 window with a <classname>Boot:</classname> prompt.
232 The arrow keys select an item from the menu and any text typed
233 at the keyboard will appear in the text window.
234 There are also help screens which can be displayed by pressing
235 the appropriate function key.
236 The <classname>General</classname> help screen explains the menu
237 choices and the <classname>Params</classname> screen explains
238 the common command line options.
239
240 </para>
241
242 <title>Serial Console</title>
243 <para>
244 You may choose to perform an install using a monitor and keyboard
245 or using a serial connection. To use a monitor/keyboard setup,
246 select an option containing the string [VGA console]. To install
247 over a serial connection, choose an option containing the string
248 [<replaceable>BAUD</replaceable> baud serial console], where
249 <replaceable>BAUD</replaceable> is the speed of your serial console.
250 Menu items for the most typical baud rate settings on the ttyS0
251 device are preconfigured.
252 </para>
253 <para>
254 In most circumstances, you will want the installer to use the same
255 baud rate as your connection to the EFI console. If you aren't
256 sure what this setting is, you can obtain it using the command
257 <command>baud</command> at the EFI shell.
258 </para>
259 <para>
260 If there is not an option available that is configured for the serial
261 device or baud rate you would like to use, you may override the console setting
262 for one of the existing menu options. For example, to use a
263 57600 baud console over the ttyS1 device, enter
264 <command>console=ttyS1,57600n8</command> into
265 the <classname>Boot:</classname> text window.
266 </para>
267
268 <note><para>
269 Most IA-64 boxes ship with a default console setting of 9600 baud.
270 This setting is rather slow, and the normal installation process
271 will take a significant time to draw each screen. You should consider
272 either increasing the baud rate used for performing the installation,
273 or performing a Text Mode installation. See the <classname>Params</classname>
274 help menu for instructions on starting the installer in Text Mode.
275 </para></note>
276
277 <warning><para>
278 If you select the wrong console type, you
279 will be able to select the kernel and enter parameters but both
280 the display and your input will go dead as soon as the kernel starts,
281 requiring you to reboot before you can begin the installation.
282 </para></warning>
283
284 <para>
285
286 Consult the <classname>General</classname> help screen for the
287 description of the kernels and install modes most appropriate
288 for your installation.
289 You should also consult <xref linkend="boot-parms"/> below for any additional
290 parameters that you may want to set in the <classname>Boot:</classname>
291 text window.
292 The kernel version you choose selects the kernel version that will be
293 used for both the installation process and the installed system.
294 If you encounter kernel problems with the installation, you may also
295 have those same problems with the system you install.
296 The following two steps will select and start the install:
297
298 </para>
299
300 <itemizedlist>
301
302 <listitem><para>
303 Select the kernel version and installation mode most
304 appropriate to your needs with the arrow keys.
305 </para></listitem>
306
307 <listitem><para>
308 Enter any boot parameters by typing at the keyboard.
309 The text will be displayed directly in the text window.
310 This is where kernel parameters (such as serial console
311 settings) are specified.
312 </para></listitem>
313
314 <listitem><para>
315 Press <command>ENTER</command>. This will load and start the
316 kernel.
317 The kernel will display its usual initialization messages followed
318 by the first screen of the Debian Installer.
319 </para></listitem>
320
321 </itemizedlist>
322
323 </sect3>
324
325 <para>
326
327 Proceed to the next chapter to continue the installation where you will
328 set up the language locale, network, and disk partitions.
329
330 </para>
331 </sect2>
332
333 <sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>
334
335 <para>
336 Booting an IA64 system from the network is similar to a CD boot.
337 The only difference is how the installation kernel is loaded.
338 The EFI Boot Manager can load and start programs from a server on
339 the network.
340 Once the installation kernel is loaded and starts, the system install
341 will proceed thru the same steps as the CD install with the exception
342 that the packages of the base install will be loaded from the network
343 rather than the CD drive.
344
345 </para>
346
347 &boot-installer-intro-net.xml;
348
349 <para>
350
351 Network booting an ia64 system requires two architecture-specific actions.
352 On the boot server, DHCP and TFTP must be configured to deliver
353 <command>elilo</command>.
354 On the client a new boot option must be defined in the EFI boot manager
355 to enable loading over a network.
356
357 </para>
358
359 <sect3 arch="ia64" id="boot-tftp-server">
360 <title>Configuring the Server</title>
361 <para>
362
363 A suitable TFTP entry for network booting an ia64 system looks something
364 like this:
365
366 <informalexample><screen>
367
368 host mcmuffin {
369 hardware ethernet 00:30:6e:1e:0e:83;
370 fixed-address 10.0.0.21;
371 filename "debian-installer/ia64/elilo.efi";
372 }
373
374 </screen></informalexample>
375
376 Note that the goal is to get <command>elilo.efi</command> running on
377 the client.
378
379 </para><para>
380
381 Extract the <filename>netboot.tar.gz</filename> file into the directory used
382 as the root for your tftp server. Typical tftp root directories include
383 <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>.
384 This will create a <filename>debian-installer</filename> directory
385 tree containing the boot files for an IA-64 system.
386
387 </para><para>
388
389 <informalexample><screen>
390 # cd /var/lib/tftp
391 # tar xvfz /home/user/netboot.tar.gz
392 ./
393 ./debian-installer/
394 ./debian-installer/ia64/
395 [...]
396 </screen></informalexample>
397
398 The <filename>netboot.tar.gz</filename> contains an
399 <filename>elilo.conf</filename> file that should work for most configurations.
400 However, should you need to make changes to this file, you can find it in the
401 <filename>debian-installer/ia64/</filename> directory.
402
403 It is possible to have different config files for different clients by naming
404 them using the client's IP address in hex with the suffix
405 <filename>.conf</filename> instead of <filename>elilo.conf</filename>.
406 See documentation provided in the <classname>elilo</classname> package
407 for details.
408
409 </para>
410 </sect3>
411
412 <sect3 arch="ia64" id="boot-tftp-client">
413 <title>Configuring the Client</title>
414 <para>
415
416 To configure the client to support TFTP booting, start by booting to
417 EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>.
418
419 <itemizedlist>
420 <listitem><para>
421
422 Add a boot option.
423
424 </para></listitem>
425 <listitem><para>
426
427 You should see one or more lines with the text
428 <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more
429 than one of these entries exist, choose the one containing the
430 MAC address of the interface from which you'll be booting.
431 Use the arrow keys to highlight your choice, then press enter.
432
433 </para></listitem>
434 <listitem><para>
435
436 Name the entry <userinput>Netboot</userinput> or something similar,
437 save, and exit back to the boot options menu.
438
439 </para></listitem>
440 </itemizedlist>
441
442 You should see the new boot option you just created, and selecting it
443 should initiate a DHCP query, leading to a TFTP load of
444 <filename>elilo.efi</filename> from the server.
445
446 </para><para>
447
448 The boot loader will display its prompt after it has downloaded and
449 processed its configuration file.
450 At this point, the installation proceeds with the same steps as a
451 CD install. Select a boot option as in above and when the kernel
452 has completed installing itself from the network, it will start the
453 Debian Installer.
454
455 </para><para>
456
457 Proceed to the next chapter to continue the installation where
458 you will set up the language locale, network, and the disk partitions.
459
460 </para>
461 </sect3>
462 </sect2>

Properties

Name Value
svn:keywords Id

  ViewVC Help
Powered by ViewVC 1.1.5