en/boot-installer/ia64.xml

<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->

  <sect2 arch="ia64"><title>Booting from a CD-ROM</title>

&boot-installer-intro-cd.xml;

  <emphasis condition="FIXME">Not yet written.</emphasis>

  </sect2>

  <sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>

&boot-installer-intro-net.xml;

<para>

Network booting an ia64 system requires two architecture-specific actions.
On the boot server, DHCP and TFTP must be configured to deliver
<command>elilo</command>.
On the client a new boot option must be defined in the EFI boot manager
to enable loading over a network.

</para>

  <sect3 arch="ia64" id="boot-tftp-server">
  <title>Configuring the Server</title>
<para>

A suitable TFTP entry for network booting an ia64 system looks something
like this:

<informalexample><screen>

host mcmuffin {
        hardware ethernet 00:30:6e:1e:0e:83;
        fixed-address 10.0.0.21;
        filename "elilo.efi";
}

</screen></informalexample>

Note that the goal is to get <command>elilo.efi</command> running on
the client.

</para><para>

Create an <filename>ia64/</filename> subdirectory in your tftpboot
directory, and populate it with the <filename>vmlinuz</filename> and
<filename>initrd.gz</filename> files from the Debian installer netboot
directory.

</para><para>

Copy <filename>elilo.efi</filename> to your tftpboot directory and
make it world readable.  This file can usually be found in the elilo
package in IA64 distributions, or in
<filename>/usr/lib/elilo</filename> or in a subdirectory of
<filename>/boot/efi</filename>.  A suitable copy is provided in the
Debian installer netboot directory.

</para><para>

Create an <filename>elilo.conf</filename> file in your tftpboot
directory.  This will
be loaded by <command>elilo.efi</command> once it is running on the
client, and controls what
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.

It is possible to have different config files for different clients by naming
them using the client's IP address in hex with the suffix
<filename>.conf</filename> instead of <filename>elilo.conf</filename>.
See documentation provided in the <classname>elilo</classname> package
for details.

</para>
  </sect3>

  <sect3 arch="ia64" id="boot-tftp-client">
  <title>Configuring the Client</title>
<para>

To configure the client to support TFTP booting, start by booting to
EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>.

<itemizedlist>
<listitem><para>

Add a boot option.

</para></listitem>
<listitem><para>

Select the line saying <guimenuitem>Load File
[Acpi()/.../Mac()]</guimenuitem> and press &enterkey;.

</para></listitem>
<listitem><para>

Name the entry <userinput>Netboot</userinput> or something similar,
save, and exit back to the boot options menu.  

</para></listitem>
</itemizedlist>

You should see the new boot option you just created, and selecting it
should initiate a DHCP query, leading to a TFTP load of
<filename>elilo.efi</filename> from the server.

</para>

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