| 1 |
bdale |
13948 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
|
|
<!-- $Id: powerpc.xml 11648 2004-03-22 00:37:46Z joeyh $ -->
|
| 3 |
|
|
|
| 4 |
|
|
<sect2 arch="ia64"><title>Booting from a CD-ROM</title>
|
| 5 |
|
|
|
| 6 |
|
|
&boot-installer-intro-cd.xml;
|
| 7 |
|
|
|
| 8 |
|
|
<emphasis>Not yet written.</emphasis>
|
| 9 |
|
|
|
| 10 |
|
|
</sect2>
|
| 11 |
|
|
|
| 12 |
|
|
<sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>
|
| 13 |
|
|
|
| 14 |
|
|
&boot-installer-intro-net.xml;
|
| 15 |
|
|
|
| 16 |
|
|
<para>
|
| 17 |
|
|
|
| 18 |
|
|
Network booting an ia64 system requires two architecture-specific actions.
|
| 19 |
|
|
On the boot server, DHCP and TFTP must be configured to deliver elilo.
|
| 20 |
|
|
On the client a new boot option must be defined in the EFI boot manager
|
| 21 |
|
|
to enable loading over a network.
|
| 22 |
|
|
|
| 23 |
|
|
</para>
|
| 24 |
|
|
<sect3 arch="ia64" id="boot-tftp-server"><title>Configuring the Server</title>
|
| 25 |
|
|
<para>
|
| 26 |
|
|
|
| 27 |
|
|
A suitable TFTP entry for network booting an ia64 system looks something
|
| 28 |
|
|
like this:
|
| 29 |
|
|
|
| 30 |
|
|
<informalexample><screen>
|
| 31 |
|
|
|
| 32 |
|
|
host mcmuffin {
|
| 33 |
|
|
hardware ethernet 00:30:6e:1e:0e:83;
|
| 34 |
|
|
fixed-address 10.0.0.21;
|
| 35 |
|
|
filename "elilo.efi";
|
| 36 |
|
|
}
|
| 37 |
|
|
|
| 38 |
|
|
</screen></informalexample>
|
| 39 |
|
|
|
| 40 |
|
|
Note that the goal is to get elilo.efi running on the client.
|
| 41 |
|
|
|
| 42 |
|
|
</para><para>
|
| 43 |
|
|
|
| 44 |
|
|
Create an ia64/ subdirectory in your tftpboot directory, and populate it with
|
| 45 |
|
|
the vmlinuz and initrd.gz files from the Debian installer netboot directory.
|
| 46 |
|
|
|
| 47 |
|
|
</para><para>
|
| 48 |
|
|
|
| 49 |
bdale |
14093 |
Copy elilo.efi to your tftpboot directory and make it world readable.
|
| 50 |
bdale |
13948 |
This file can usually be found in the elilo package in IA64 distributions,
|
| 51 |
bdale |
14093 |
or in /usr/lib/elilo or in a subdirectory of /boot/efi. A suitable copy is
|
| 52 |
|
|
provided in the Debian installer netboot directory.
|
| 53 |
bdale |
13948 |
|
| 54 |
|
|
</para><para>
|
| 55 |
|
|
|
| 56 |
|
|
Create an elilo.conf file in your tftpboot directory. This will
|
| 57 |
|
|
be loaded by elilo.efi once it is running on the client, and controls what
|
| 58 |
bdale |
14093 |
happens next, including the choice of kernel, initrd image, etc. An
|
| 59 |
|
|
example file is provided in the Debian installer netboot directory, review
|
| 60 |
|
|
the contents and update as needed for your choice of paths, etc.
|
| 61 |
bdale |
13948 |
|
| 62 |
|
|
It is possible to have different config files for different clients by naming
|
| 63 |
|
|
them using the client's IP address in hex with the suffix .conf instead of
|
| 64 |
|
|
elilo.conf. See documentation provided in the elilo package for details.
|
| 65 |
|
|
|
| 66 |
|
|
</para>
|
| 67 |
|
|
</sect3>
|
| 68 |
|
|
<sect3 arch="ia64" id="boot-tftp-client"><title>Configuring the Client</title>
|
| 69 |
|
|
<para>
|
| 70 |
|
|
To configure the client to support TFTP booting, start by booting to EFI and
|
| 71 |
|
|
entering the "Boot Option Maintenance Menu".
|
| 72 |
|
|
</para><para>
|
| 73 |
|
|
Add a boot option.
|
| 74 |
|
|
</para><para>
|
| 75 |
|
|
Select the line saying "Load File [Acpi()/.../Mac()] and press enter.
|
| 76 |
|
|
</para><para>
|
| 77 |
|
|
Name the entry "Netboot" or something similar, save, and exit back to the
|
| 78 |
|
|
boot options menu.
|
| 79 |
|
|
</para><para>
|
| 80 |
|
|
You should see the new boot option you just created, and
|
| 81 |
|
|
selecting it should initiate a DHCP query, leading to a TFTP load of elilo.efi
|
| 82 |
|
|
from the server.
|
| 83 |
|
|
|
| 84 |
|
|
</para>
|
| 85 |
|
|
|
| 86 |
|
|
</sect3>
|
| 87 |
|
|
</sect2>
|
Parent Directory
| 
Revision Log