nl/boot-installer/ia64.xml

<!-- retain these comments for translator revision tracking -->
<!-- original version: 18974 untranslated -->

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

&boot-installer-intro-cd.xml;

  <note>
  <title>CD Contents</title>

<para>

There are three basic variations of Debian Install CDs.
The <emphasis>Business Card</emphasis> CD has a minimal installation
that will fit on the small form factor CD media.
It requires a network connection in order to install the rest of the
base installation and make a usable system.
The <emphasis>Network Install</emphasis> CD has all of the packages
for a base install but requires a network connection to a Debian
mirror site in order to install the
extra packages one would want for a complete system .
The set of Debian CDs can install a complete system from the wide
range of packages without needing access to the network.
</para>
  </note>

<para>

The IA-64 uses the next generation Extensible Firmware Interface (EFI)
from Intel.
Unlike the traditional x86 BIOS which knows little about the boot
device other than the partition table and Master Boot Record (MBR),
the EFI can read and write files from FAT16 or FAT32 formatted disk
partitions.
This simplifies the often arcane process of starting a system.
The system boot loader and the EFI firmware that supports it have
a full filesystem to store the files necessary for booting the
machine.
This means that the system disk on an IA-64 system has an additional
disk partition dedicated to the EFI instead of the simple MBR or boot
block on more conventional systems. 

</para><para>

The Debian CD contains a small version of the EFI partition where
<command>elilo</command>, its configuration file, the installer's kernel,
 and initial filesystem (initrd) are located.
The running system also contains an EFI partition where the necessary
files for booting the system reside.
These files are readable from the EFI Shell as described below.

</para><para>

Most of the details of how the <command>elilo</command> actually loads and
starts a system for the most part transparent to the system installer.
However, the installer must set up an EFI partition prior to installing
the base system.  Otherwise, the installation of <command>elilo</command>
will fail, rendering the system un-bootable.
The EFI partition is allocated and formatted in the partitioning step
of the installation prior to loading any packages on the system disk.
The partitioning task also verifies that a suitable EFI partition is
present before allowing the installation to proceed.

</para><para>

The EFI Boot Manager is started as the last step of the firmware
initialization.
It displays a menu list from which the user can select
an option.
Depending on the model of system and what other software has been
loaded on the system, this menu may be different from one system
to another.
There should be two menu items displayed,
<command>Boot Option Maintenance Menu</command> and
<command>EFI Shell (Built-in)</command>.
Using the first option is preferred, however, if that
option is not available or the CD for some reason does not
boot with it, use the second option.

</para>

  <warning>
  <title>IMPORTANT</title>
<para>
The EFI Boot Manager will select a default boot action, typically
the first menu choice, within a pre-set number of seconds.
This is indicated by a countdown at the bottom of the screen.
Once the timer expires and the systems starts the default action,
you will have to reboot the machine in order to continue the installation.
</para>
  </warning>

  <sect3 arch="ia64" id="bootable-cd">
  <title>Option 1: Booting from the Boot Option Maintenance Menu</title>
<para>

</para>

<itemizedlist>

<listitem><para>
Insert the CD in the DVD/CD drive and reboot the machine.
The firmware will display the EFI Boot Manager page and menu after
it completes its system initialization.
</para></listitem>

<listitem><para>
Select <command>Boot Maintenance Menu</command> from the menu
with the arrow keys and press <command>ENTER</command>.
This will display a new menu.
</para></listitem>

<listitem><para>
Select <command>Boot From a File</command> from the menu
with the arrow keys and press <command>ENTER</command>.
This will display a list of devices probed by the firmware.
You should see two menu lines containing either the label
<command>Debian Inst [Acpi ...</command> or
<command>Removable Media Boot</command>.
If you examine the rest of the menu line, you will notice that
the device and controller information should be the same.
</para></listitem>

<listitem><para>
You can choose either of the entries that refer to the CD/DVD
drive.
Select your choice with the arrow keys and press <command>ENTER</command>.
If you choose <command>Removable Media Boot</command> the machine
will immediately start the boot load sequence.
If you choose <command>Debian Inst [Acpi ...</command> instead, it
will display a directory listing of the bootable portion of the
CD, requiring you to proceed to the next (additional) step.
</para></listitem>

<listitem><para>
You will only need this step if you chose
<command>Debian Inst [Acpi ...</command>.
The directory listing will also show
<command>[Treat like Removable Media Boot]</command> on the next to
the last line.
Select this line with the arrow keys and press <command>ENTER</command>.
This will start the boot load sequence.
</para></listitem>

</itemizedlist>

<para>

These steps start the Debian boot loader which will display a
menu page for you to select a boot kernel and options.
Proceed to selecting the boot kernel and options.

</para>
  </sect3>

  <sect3 arch="ia64" id="boot-with-efi">
  <title>Option 2: Booting from the EFI Shell</title>
<para>

If, for some reason, option 1 is not successful, reboot the machine
and when the EFI Boot Manager screen appears there should be
one option called <command>EFI Shell [Built-in]</command>.
Boot the Debian Installer CD with the following steps:

</para>

<itemizedlist>

<listitem><para>
Insert the CD in the DVD/CD drive and reboot the machine.
The firmware will display the EFI Boot Manager page and menu after
it completes system initialization.
</para></listitem>

<listitem><para>
Select <command>EFI Shell</command> from the menu with the arrow keys
and press <command>ENTER</command>.
The EFI Shell will scan all of the bootable devices and display
them to the console before displaying its command prompt.
The recognized bootable partitions on devices will show a device name of
<filename>fs<emphasis>n</emphasis>:</filename>.
All other recognized partitions will be named
<filename>blk<emphasis>n</emphasis>:</filename>.
If you inserted the CD just before entering the shell, this may
take a few extra seconds as it initializes the CD drive.
</para>
</listitem>

<listitem><para>
Examine the output from the shell looking for the CDROM drive.
It is most likely the <filename>fs0:</filename> device although
other devices with bootable partitions will also show up as
<filename>fs<emphasis>n</emphasis></filename>.
</para></listitem>

<listitem><para>
Enter <command>fs<emphasis>n</emphasis>:</command> and press
<command>ENTER</command> to select that
device where <emphasis>n</emphasis> is the partition number for the
CDROM.  The shell will now display the partition number as its prompt.
</para></listitem>

<listitem><para>
Enter <command>elilo</command> and press <command>ENTER</command>.
This will start the boot load sequence.
</para></listitem>

</itemizedlist>

<para> 

As with option 1, these steps start the Debian boot loader which will
display a menu page for you to select a boot kernel and options.
You can also enter the shorter 
<command>fs<emphasis>n</emphasis>:elilo</command> command at
the shell prompt.
Proceed to selecting the boot kernel and options.

</para>

  </sect3>

  <sect3 arch="ia64" id="kernel-option-menu">
  <title>Selecting the Boot Kernel and Options</title>

<para>

The boot loader will display a form with a menu list and a text
window with a <classname>Boot:</classname> prompt.
The arrow keys select an item from the menu and any text typed
at the keyboard will appear in the text window.
There are also help screens which can be displayed by pressing
the appropriate function key.
The <classname>General</classname> help screen explains the menu
choices and the <classname>Params</classname> screen explains
the common command line options.

</para>

   <warning>
   <title>Serial Console</title>
<para>

Some IA64 platforms have both a serial console and a keyboard and
video card which can be configured in the EFI firmware to be
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
will be able to select the kernel and enter parameters but both
the display and your input will go dead as soon as the kernel starts,
requiring you to either reboot if your system does not have a keyboard
and video display installed.
</para></warning>

<para>

Consult the <classname>General</classname> help screen for the
description of the kernels and install modes most appropriate
for your installation.
You should also consult <xref linkend="boot-parms"/> below for any additional
parameters that you may want to set in the <classname>Boot:</classname>
text window.
The kernel version you choose selects the kernel version that will be
used for both the installation process and the installed system.
If you encounter kernel problems with the installation, you may also
have those same problems with the system you install.
The following two steps will select and start the install:

</para>

<itemizedlist>

<listitem><para>
Select the kernel version and installation mode most
appropriate to your needs with the arrow keys.
</para></listitem>

<listitem><para>
Enter any boot parameters by typing at the keyboard.
The text will be displayed directly in the text window.
This is where the serial console is set.
</para></listitem>

<listitem><para>
Press <command>ENTER</command>.  This will load and start the
kernel.
The kernel will display its usual initialization messages followed
by the first screen of the Debian Installer.
</para></listitem> 

</itemizedlist>

  </sect3>

<para>

Proceed to the next chapter to continue the installation where you will
set up the language locale, network, and disk partitions.

</para>
  </sect2>

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

<para>
Booting an IA64 system from the network is similar to a CD boot.
The only difference is how the installation kernel is loaded.
The EFI Boot Manager can load and start programs from servers on
the network.
Once the installation kernel is loaded and starts, the system install
will proceed thru the same steps as the CD install with the exception
that the packages of the base install will be loaded from the network
rather than the CD drive.

</para>

&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><para>

The boot loader will display its prompt after it has downloaded and
processed its configuration file.
At this point, the installation proceeds with the same steps as a
CD install.  Select a boot option as in above and when the kernel
has completed installing itself from the network, it will start the
Debian Installer.

</para><para>

Proceed to the next chapter to continue the installation where
you will set up the language locale, network, and the disk partitions.

</para>
  </sect3>
  </sect2>
1	<!-- retain these comments for translator revision tracking -->
2	<!-- original version: 18974 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 uses the next generation Extensible Firmware Interface (EFI)
30	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	the 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 the EFI instead of the simple MBR or boot
41	block on more conventional systems.
42
43	</para><para>
44
45	The Debian CD contains a small version of the EFI partition where
46	<command>elilo</command>, its configuration file, the installer's kernel,
47	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 the <command>elilo</command> actually loads and
55	starts a system for the most part 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 started 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 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 will have to reboot the machine in order to continue the installation.
90	</para>
91	</warning>
92
93	<sect3 arch="ia64" id="bootable-cd">
94	<title>Option 1: Booting from the Boot Option Maintenance Menu</title>
95	<para>
96
97	</para>
98
99	<itemizedlist>
100
101	<listitem><para>
102	Insert the CD in the DVD/CD drive and reboot the machine.
103	The firmware will display the EFI Boot Manager page and menu after
104	it completes its system initialization.
105	</para></listitem>
106
107	<listitem><para>
108	Select <command>Boot Maintenance Menu</command> from the menu
109	with the arrow keys and press <command>ENTER</command>.
110	This will display a new menu.
111	</para></listitem>
112
113	<listitem><para>
114	Select <command>Boot From a File</command> from the menu
115	with the arrow keys and press <command>ENTER</command>.
116	This will display a list of devices probed by the firmware.
117	You should see two menu lines containing either the label
118	<command>Debian Inst [Acpi ...</command> or
119	<command>Removable Media Boot</command>.
120	If you examine the rest of the menu line, you will notice that
121	the device and controller information should be the same.
122	</para></listitem>
123
124	<listitem><para>
125	You can choose either of the entries that refer to the CD/DVD
126	drive.
127	Select your choice with the arrow keys and press <command>ENTER</command>.
128	If you choose <command>Removable Media Boot</command> the machine
129	will immediately start the boot load sequence.
130	If you choose <command>Debian Inst [Acpi ...</command> instead, it
131	will display a directory listing of the bootable portion of the
132	CD, requiring you to proceed to the next (additional) step.
133	</para></listitem>
134
135	<listitem><para>
136	You will only need this step if you chose
137	<command>Debian Inst [Acpi ...</command>.
138	The directory listing will also show
139	<command>[Treat like Removable Media Boot]</command> on the next to
140	the last line.
141	Select this line with the arrow keys and press <command>ENTER</command>.
142	This will start the boot load sequence.
143	</para></listitem>
144
145	</itemizedlist>
146
147	<para>
148
149	These steps start the Debian boot loader which will display a
150	menu page for you to select a boot kernel and options.
151	Proceed to selecting the boot kernel and options.
152
153	</para>
154	</sect3>
155
156	<sect3 arch="ia64" id="boot-with-efi">
157	<title>Option 2: Booting from the EFI Shell</title>
158	<para>
159
160	If, for some reason, option 1 is not successful, reboot the machine
161	and when the EFI Boot Manager screen appears there should be
162	one option called <command>EFI Shell [Built-in]</command>.
163	Boot the Debian Installer CD with the following steps:
164
165	</para>
166
167	<itemizedlist>
168
169	<listitem><para>
170	Insert the CD in the DVD/CD drive and reboot the machine.
171	The firmware will display the EFI Boot Manager page and menu after
172	it completes system initialization.
173	</para></listitem>
174
175	<listitem><para>
176	Select <command>EFI Shell</command> from the menu with the arrow keys
177	and press <command>ENTER</command>.
178	The EFI Shell will scan all of the bootable devices and display
179	them to the console before displaying its command prompt.
180	The recognized bootable partitions on devices will show a device name of
181	<filename>fs<emphasis>n</emphasis>:</filename>.
182	All other recognized partitions will be named
183	<filename>blk<emphasis>n</emphasis>:</filename>.
184	If you inserted the CD just before entering the shell, this may
185	take a few extra seconds as it initializes the CD drive.
186	</para>
187	</listitem>
188
189	<listitem><para>
190	Examine the output from the shell looking for the CDROM drive.
191	It is most likely the <filename>fs0:</filename> device although
192	other devices with bootable partitions will also show up as
193	<filename>fs<emphasis>n</emphasis></filename>.
194	</para></listitem>
195
196	<listitem><para>
197	Enter <command>fs<emphasis>n</emphasis>:</command> and press
198	<command>ENTER</command> to select that
199	device where <emphasis>n</emphasis> is the partition number for the
200	CDROM. The shell will now display the partition number as its prompt.
201	</para></listitem>
202
203	<listitem><para>
204	Enter <command>elilo</command> and press <command>ENTER</command>.
205	This will start the boot load sequence.
206	</para></listitem>
207
208	</itemizedlist>
209
210	<para>
211
212	As with option 1, these steps start the Debian boot loader which will
213	display a menu page for you to select a boot kernel and options.
214	You can also enter the shorter
215	<command>fs<emphasis>n</emphasis>:elilo</command> command at
216	the shell prompt.
217	Proceed to selecting the boot kernel and options.
218
219	</para>
220
221	</sect3>
222
223	<sect3 arch="ia64" id="kernel-option-menu">
224	<title>Selecting the Boot Kernel and Options</title>
225
226	<para>
227
228	The boot loader will display a form with a menu list and a text
229	window with a <classname>Boot:</classname> prompt.
230	The arrow keys select an item from the menu and any text typed
231	at the keyboard will appear in the text window.
232	There are also help screens which can be displayed by pressing
233	the appropriate function key.
234	The <classname>General</classname> help screen explains the menu
235	choices and the <classname>Params</classname> screen explains
236	the common command line options.
237
238	</para>
239
240	<warning>
241	<title>Serial Console</title>
242	<para>
243
244	Some IA64 platforms have both a serial console and a keyboard and
245	video card which can be configured in the EFI firmware to be
246	the system console.
247	The EFI console is capable of displaying and accepting input from
248	both the keyboard and video and the serial port.
249	The Linux kernel will take the keyboard and video devices as its
250	default console if it detects a keyboard during its initialization.
251	You will have to enable the serial console in the EFI boot
252	manager and enter
253	<command>console=ttyS0,9600n8</command> into
254	the <classname>Boot:</classname> text window to install via
255	the serial console.
256	If you are using a serial console and forget to set it in the
257	command line, you
258	will be able to select the kernel and enter parameters but both
259	the display and your input will go dead as soon as the kernel starts,
260	requiring you to either reboot if your system does not have a keyboard
261	and video display installed.
262	</para></warning>
263
264	<para>
265
266	Consult the <classname>General</classname> help screen for the
267	description of the kernels and install modes most appropriate
268	for your installation.
269	You should also consult <xref linkend="boot-parms"/> below for any additional
270	parameters that you may want to set in the <classname>Boot:</classname>
271	text window.
272	The kernel version you choose selects the kernel version that will be
273	used for both the installation process and the installed system.
274	If you encounter kernel problems with the installation, you may also
275	have those same problems with the system you install.
276	The following two steps will select and start the install:
277
278	</para>
279
280	<itemizedlist>
281
282	<listitem><para>
283	Select the kernel version and installation mode most
284	appropriate to your needs with the arrow keys.
285	</para></listitem>
286
287	<listitem><para>
288	Enter any boot parameters by typing at the keyboard.
289	The text will be displayed directly in the text window.
290	This is where the serial console is set.
291	</para></listitem>
292
293	<listitem><para>
294	Press <command>ENTER</command>. This will load and start the
295	kernel.
296	The kernel will display its usual initialization messages followed
297	by the first screen of the Debian Installer.
298	</para></listitem>
299
300	</itemizedlist>
301
302	</sect3>
303
304	<para>
305
306	Proceed to the next chapter to continue the installation where you will
307	set up the language locale, network, and disk partitions.
308
309	</para>
310	</sect2>
311
312	<sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>
313
314	<para>
315	Booting an IA64 system from the network is similar to a CD boot.
316	The only difference is how the installation kernel is loaded.
317	The EFI Boot Manager can load and start programs from servers on
318	the network.
319	Once the installation kernel is loaded and starts, the system install
320	will proceed thru the same steps as the CD install with the exception
321	that the packages of the base install will be loaded from the network
322	rather than the CD drive.
323
324	</para>
325
326	&boot-installer-intro-net.xml;
327
328	<para>
329
330	Network booting an ia64 system requires two architecture-specific actions.
331	On the boot server, DHCP and TFTP must be configured to deliver
332	<command>elilo</command>.
333	On the client a new boot option must be defined in the EFI boot manager
334	to enable loading over a network.
335
336	</para>
337
338	<sect3 arch="ia64" id="boot-tftp-server">
339	<title>Configuring the Server</title>
340	<para>
341
342	A suitable TFTP entry for network booting an ia64 system looks something
343	like this:
344
345	<informalexample><screen>
346
347	host mcmuffin {
348	hardware ethernet 00:30:6e:1e:0e:83;
349	fixed-address 10.0.0.21;
350	filename "elilo.efi";
351	}
352
353	</screen></informalexample>
354
355	Note that the goal is to get <command>elilo.efi</command> running on
356	the client.
357
358	</para><para>
359
360	Create an <filename>ia64/</filename> subdirectory in your tftpboot
361	directory, and populate it with the <filename>vmlinuz</filename> and
362	<filename>initrd.gz</filename> files from the Debian installer netboot
363	directory.
364
365	</para><para>
366
367	Copy <filename>elilo.efi</filename> to your tftpboot directory and
368	make it world readable. This file can usually be found in the elilo
369	package in IA64 distributions, or in
370	<filename>/usr/lib/elilo</filename> or in a subdirectory of
371	<filename>/boot/efi</filename>. A suitable copy is provided in the
372	Debian installer netboot directory.
373
374	</para><para>
375
376	Create an <filename>elilo.conf</filename> file in your tftpboot
377	directory. This will
378	be loaded by <command>elilo.efi</command> once it is running on the
379	client, and controls what
380	happens next, including the choice of kernel, initrd image, etc. An
381	example file is provided in the Debian installer netboot directory, review
382	the contents and update as needed for your choice of paths, etc.
383
384	It is possible to have different config files for different clients by naming
385	them using the client's IP address in hex with the suffix
386	<filename>.conf</filename> instead of <filename>elilo.conf</filename>.
387	See documentation provided in the <classname>elilo</classname> package
388	for details.
389
390	</para>
391	</sect3>
392
393	<sect3 arch="ia64" id="boot-tftp-client">
394	<title>Configuring the Client</title>
395	<para>
396
397	To configure the client to support TFTP booting, start by booting to
398	EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>.
399
400	<itemizedlist>
401	<listitem><para>
402
403	Add a boot option.
404
405	</para></listitem>
406	<listitem><para>
407
408	Select the line saying <guimenuitem>Load File
409	[Acpi()/.../Mac()]</guimenuitem> and press &enterkey;.
410
411	</para></listitem>
412	<listitem><para>
413
414	Name the entry <userinput>Netboot</userinput> or something similar,
415	save, and exit back to the boot options menu.
416
417	</para></listitem>
418	</itemizedlist>
419
420	You should see the new boot option you just created, and selecting it
421	should initiate a DHCP query, leading to a TFTP load of
422	<filename>elilo.efi</filename> from the server.
423
424	</para><para>
425
426	The boot loader will display its prompt after it has downloaded and
427	processed its configuration file.
428	At this point, the installation proceeds with the same steps as a
429	CD install. Select a boot option as in above and when the kernel
430	has completed installing itself from the network, it will start the
431	Debian Installer.
432
433	</para><para>
434
435	Proceed to the next chapter to continue the installation where
436	you will set up the language locale, network, and the disk partitions.
437
438	</para>
439	</sect3>
440	</sect2>