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

Diff of /trunk/installer/doc/manual/en/boot-installer/ia64.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 18974 by dannf, Wed Aug 11 10:46:40 2004 UTC revision 21882 by dannf, Mon Sep 20 06:06:05 2004 UTC
# Line 26  range of packages without needing access Line 26  range of packages without needing access
26    
27  <para>  <para>
28    
29  The IA-64 uses the next generation Extensible Firmware Interface (EFI)  The IA-64 architecture uses the next generation Extensible Firmware Interface
30  from Intel.  (EFI) from Intel.
31  Unlike the traditional x86 BIOS which knows little about the boot  Unlike the traditional x86 BIOS which knows little about the boot
32  device other than the partition table and Master Boot Record (MBR),  device other than the partition table and Master Boot Record (MBR),
33  the EFI can read and write files from FAT16 or FAT32 formatted disk  EFI can read and write files from FAT16 or FAT32 formatted disk
34  partitions.  partitions.
35  This simplifies the often arcane process of starting a system.  This simplifies the often arcane process of starting a system.
36  The system boot loader and the EFI firmware that supports it have  The system boot loader and the EFI firmware that supports it have
37  a full filesystem to store the files necessary for booting the  a full filesystem to store the files necessary for booting the
38  machine.  machine.
39  This means that the system disk on an IA-64 system has an additional  This means that the system disk on an IA-64 system has an additional
40  disk partition dedicated to the EFI instead of the simple MBR or boot  disk partition dedicated to EFI instead of the simple MBR or boot
41  block on more conventional systems.  block on more conventional systems.
42    
43  </para><para>  </para><para>
44    
45  The Debian CD contains a small version of the EFI partition where  The Debian Installer CD contains a small EFI partition where the
46  <command>elilo</command>, its configuration file, the installer's kernel,  <command>ELILO</command> bootloader, its configuration file, the installer's
47   and initial filesystem (initrd) are located.  kernel, and initial filesystem (initrd) are located.
48  The running system also contains an EFI partition where the necessary  The running system also contains an EFI partition where the necessary
49  files for booting the system reside.  files for booting the system reside.
50  These files are readable from the EFI Shell as described below.  These files are readable from the EFI Shell as described below.
51    
52  </para><para>  </para><para>
53    
54  Most of the details of how the <command>elilo</command> actually loads and  Most of the details of how <command>ELILO</command> actually loads and
55  starts a system for the most part transparent to the system installer.  starts a system are transparent to the system installer.
56  However, the installer must set up an EFI partition prior to installing  However, the installer must set up an EFI partition prior to installing
57  the base system.  Otherwise, the installation of <command>elilo</command>  the base system.  Otherwise, the installation of <command>ELILO</command>
58  will fail, rendering the system un-bootable.  will fail, rendering the system un-bootable.
59  The EFI partition is allocated and formatted in the partitioning step  The EFI partition is allocated and formatted in the partitioning step
60  of the installation prior to loading any packages on the system disk.  of the installation prior to loading any packages on the system disk.
# Line 63  present before allowing the installation Line 63  present before allowing the installation
63    
64  </para><para>  </para><para>
65    
66  The EFI Boot Manager is started as the last step of the firmware  The EFI Boot Manager is presented as the last step of the firmware
67  initialization.  initialization.
68  It displays a menu list from which the user can select  It displays a menu list from which the user can select
69  an option.  an option.
70  Depending on the model of system and what other software has been  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  loaded on the system, this menu may be different from one system
72  to another.  to another.
73  There should be two menu items displayed,  There should be at least two menu items displayed,
74  <command>Boot Option Maintenance Menu</command> and  <command>Boot Option Maintenance Menu</command> and
75  <command>EFI Shell (Built-in)</command>.  <command>EFI Shell (Built-in)</command>.
76  Using the first option is preferred, however, if that  Using the first option is preferred, however, if that
# Line 86  The EFI Boot Manager will select a defau Line 86  The EFI Boot Manager will select a defau
86  the first menu choice, within a pre-set number of seconds.  the first menu choice, within a pre-set number of seconds.
87  This is indicated by a countdown at the bottom of the screen.  This is indicated by a countdown at the bottom of the screen.
88  Once the timer expires and the systems starts the default action,  Once the timer expires and the systems starts the default action,
89  you will have to reboot the machine in order to continue the installation.  you may have to reboot the machine in order to continue the installation.
90    If the default action is th EFI Shell, you can return to the Boot Manager
91    by running <command>exit</command> at the shell prompt.
92  </para>  </para>
93    </warning>    </warning>
94    
# Line 237  the common command line options. Line 239  the common command line options.
239    
240  </para>  </para>
241    
    <warning>  
242     <title>Serial Console</title>     <title>Serial Console</title>
243  <para>  <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  Some IA64 platforms have both a serial console and a keyboard and  <warning><para>
278  video card which can be configured in the EFI firmware to be  If you select the wrong console type, you
 the system console.  
 The EFI console is capable of displaying and accepting input from  
 both the keyboard and video and the serial port.  
 The Linux kernel will take the keyboard and video devices as its  
 default console if it detects a keyboard during its initialization.  
 You will have to enable the serial console in the EFI boot  
 manager and enter  
 <command>console=ttyS0,9600n8</command> into  
 the <classname>Boot:</classname> text window to install via  
 the serial console.  
 If you are using a serial console and forget to set it in the  
 command line, you  
279  will be able to select the kernel and enter parameters but both  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,  the display and your input will go dead as soon as the kernel starts,
281  requiring you to either reboot if your system does not have a keyboard  requiring you to reboot before you can begin the installation.
 and video display installed.  
282  </para></warning>  </para></warning>
283    
284  <para>  <para>
# Line 287  appropriate to your needs with the arrow Line 307  appropriate to your needs with the arrow
307  <listitem><para>  <listitem><para>
308  Enter any boot parameters by typing at the keyboard.  Enter any boot parameters by typing at the keyboard.
309  The text will be displayed directly in the text window.  The text will be displayed directly in the text window.
310  This is where the serial console is set.  This is where kernel parameters (such as serial console
311    settings) are specified.
312  </para></listitem>  </para></listitem>
313    
314  <listitem><para>  <listitem><para>
# Line 314  set up the language locale, network, and Line 335  set up the language locale, network, and
335  <para>  <para>
336  Booting an IA64 system from the network is similar to a CD boot.  Booting an IA64 system from the network is similar to a CD boot.
337  The only difference is how the installation kernel is loaded.  The only difference is how the installation kernel is loaded.
338  The EFI Boot Manager can load and start programs from servers on  The EFI Boot Manager can load and start programs from a server on
339  the network.  the network.
340  Once the installation kernel is loaded and starts, the system install  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  will proceed thru the same steps as the CD install with the exception
# Line 347  like this: Line 368  like this:
368  host mcmuffin {  host mcmuffin {
369          hardware ethernet 00:30:6e:1e:0e:83;          hardware ethernet 00:30:6e:1e:0e:83;
370          fixed-address 10.0.0.21;          fixed-address 10.0.0.21;
371          filename "elilo.efi";          filename "debian-installer/ia64/elilo.efi";
372  }  }
373    
374  </screen></informalexample>  </screen></informalexample>
# Line 357  the client. Line 378  the client.
378    
379  </para><para>  </para><para>
380    
381  Create an <filename>ia64/</filename> subdirectory in your tftpboot  Extract the <filename>netboot.tar.gz</filename> file into the directory used
382  directory, and populate it with the <filename>vmlinuz</filename> and  as the root for your tftp server.  Typical tftp root directories include
383  <filename>initrd.gz</filename> files from the Debian installer netboot  <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>.
384  directory.  This will create a <filename>debian-installer</filename> directory
385    tree containing the boot files for an IA-64 system.
386    
387  </para><para>  </para><para>
388    
389  Copy <filename>elilo.efi</filename> to your tftpboot directory and  <informalexample><screen>
390  make it world readable.  This file can usually be found in the elilo  # cd /var/lib/tftp
391  package in IA64 distributions, or in  # tar xvfz /home/user/netboot.tar.gz
392  <filename>/usr/lib/elilo</filename> or in a subdirectory of  ./
393  <filename>/boot/efi</filename>.  A suitable copy is provided in the  ./debian-installer/
394  Debian installer netboot directory.  ./debian-installer/ia64/
395    [...]
396  </para><para>  </screen></informalexample>
397    
398  Create an <filename>elilo.conf</filename> file in your tftpboot  The <filename>netboot.tar.gz</filename> contains an
399  directory.  This will  <filename>elilo.conf</filename> file that should work for most configurations.
400  be loaded by <command>elilo.efi</command> once it is running on the  However, should you need to make changes to this file, you can find it in the
401  client, and controls what  <filename>debian-installer/ia64/</filename> directory.
 happens next, including the choice of kernel, initrd image, etc.  An  
 example file is provided in the Debian installer netboot directory, review  
 the contents and update as needed for your choice of paths, etc.  
402    
403  It is possible to have different config files for different clients by naming  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  them using the client's IP address in hex with the suffix
# Line 405  Add a boot option. Line 424  Add a boot option.
424  </para></listitem>  </para></listitem>
425  <listitem><para>  <listitem><para>
426    
427  Select the line saying <guimenuitem>Load File  You should see one or more lines with the text
428  [Acpi()/.../Mac()]</guimenuitem> and press &enterkey;.  <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>  </para></listitem>
434  <listitem><para>  <listitem><para>
Legend:
Removed from v.18974  
changed lines
  Added in v.21882
  ViewVC Help
Powered by ViewVC 1.1.5