1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 31616 untranslated -->
4
<sect2 arch="i386"><title>Booting from a CD-ROM</title>
6
&boot-installer-intro-cd.xml;
8
<!-- We'll comment the following section until we know exact layout -->
10
CD #1 of official Debian CD-ROM sets for &arch-title; will present a
11
<prompt>boot:</prompt> prompt on most hardware. Press
12
<keycap>F3</keycap> to see the list of kernel options available
13
from which to boot. Just type your chosen flavor name (idepci,
14
vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt
15
followed by &enterkey;.
19
If your hardware doesn't support booting of multiple images, put one
20
of the other CDs in the drive. It appears that most SCSI CD-ROM drives
21
do not support <command>isolinux</command> multiple image booting, so users
22
with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact),
27
CD's 2 through 5 will each boot a
28
different ``flavor'' depending on which CD-ROM is
29
inserted. See <xref linkend="kernel-choice"/> for a discussion of the
30
different flavors. Here's how the flavors are laid out on the
35
<term>CD 1</term><listitem><para>
37
Allows a selection of kernel images to boot from (the idepci flavor is
38
the default if no selection is made).
40
</para></listitem></varlistentry>
42
<term>CD 2</term><listitem><para>
44
Boots the <quote>vanilla</quote> flavor.
46
</para></listitem></varlistentry>
48
<term>CD 3</term><listitem><para>
50
Boots the <quote>compact</quote> flavor.
52
</para></listitem></varlistentry>
54
<term>CD 4</term><listitem><para>
56
Boots the <quote>idepci</quote> flavor.
58
</para></listitem></varlistentry>
60
<term>CD 5</term><listitem><para>
62
Boots the <quote>bf2.4</quote> flavor.
64
</para></listitem></varlistentry>
74
<!-- FIXME the documented procedure does not exactly work, commented out
77
<sect2 arch="i386" id="install-from-dos">
78
<title>Booting from a DOS partition</title>
80
&boot-installer-intro-hd.xml;
84
Boot into DOS (not Windows) without any drivers being loaded. To do
85
this, you have to press <keycap>F8</keycap> at exactly the right
86
moment (and optionally select the <quote>safe mode command prompt only</quote>
87
option). Enter the subdirectory for the flavor you chose, e.g.,
89
<informalexample><screen>
91
</screen></informalexample>.
93
Next, execute <command>install.bat</command>.
94
The kernel will load and launch the installer system.
98
Please note, there is currently a loadlin problem (#142421) which
99
precludes <filename>install.bat</filename> from being used with the
100
bf2.4 flavor. The symptom of the problem is an
101
<computeroutput>invalid compressed format</computeroutput> error.
108
<sect2 arch="i386" id="boot-initrd">
109
<title>Booting from Linux Using <command>LILO</command> or
110
<command>GRUB</command></title>
113
To boot the installer from hard disk, you must first download
114
and place the needed files as described in <xref linkend="boot-drive-files"/>.
118
If you intend to use the hard drive only for booting and then
119
download everything over the network, you should download the
120
<filename>netboot/debian-installer/i386/initrd.gz</filename> file and its
121
corresponding kernel. This will allow you to repartition the hard disk
122
from which you boot the installer, although you should do so with care.
126
Alternatively, if you intend to keep an existing partition on the hard
127
drive unchanged during the install, you can download the
128
<filename>hd-media/initrd.gz</filename> file and its kernel, as well as
129
copy a CD iso to the drive (make sure the file is named ending in
130
<literal>.iso</literal>). The installer can then boot from the drive
131
and install from the CD image, without needing the network.
135
For <command>LILO</command>, you will need to configure two
136
essential things in <filename>/etc/lilo.conf</filename>:
140
to load the <filename>initrd.gz</filename> installer at boot time;
145
have the <filename>vmlinuz</filename> kernel use a RAM disk as
151
Here is a <filename>/etc/lilo.conf</filename> example:
155
<informalexample><screen>
156
image=/boot/newinstall/vmlinuz
158
initrd=/boot/newinstall/initrd.gz
160
append="<phrase condition="sarge">devfs=mount,dall </phrase>ramdisk_size=12000"
161
</screen></informalexample>
163
For more details, refer to the
164
<citerefentry><refentrytitle>initrd</refentrytitle>
165
<manvolnum>4</manvolnum></citerefentry> and
166
<citerefentry><refentrytitle>lilo.conf</refentrytitle>
167
<manvolnum>5</manvolnum></citerefentry> man pages. Now run
168
<userinput>lilo</userinput> and reboot.
172
The procedure for <command>GRUB</command> is quite similar. Locate your
173
<filename>menu.lst</filename> in the <filename>/boot/grub/</filename>
174
directory (sometimes in the <filename>/boot/boot/grub/</filename>),
175
add the following lines:
177
<informalexample><screen>
179
kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000
180
initrd (hd0,0)/boot/newinstall/initrd.gz
181
</screen></informalexample>
183
and reboot. <phrase condition="sarge">If the boot fails, you can try adding
184
<userinput>devfs=mount,dall</userinput> to the <quote>kernel</quote> line.
189
Note that the value of the <userinput>ramdisk_size</userinput> may need to be
190
adjusted for the size of the initrd image.
191
From here on, there should be no difference between <command>GRUB</command>
192
or <command>LILO</command>.
197
<sect2 arch="i386" id="usb-boot">
198
<title>Booting from USB Memory Stick</title>
201
Let's assume you have prepared everything from <xref
202
linkend="boot-dev-select"/> and <xref linkend="boot-usb-files"/>. Now
203
just plug your USB stick into some free USB connector and reboot the
204
computer. The system should boot up, and you should be presented with
205
the <prompt>boot:</prompt> prompt. Here you can enter optional boot
206
arguments, or just hit &enterkey;.
210
In case your computer doesn't support booting from USB memory devices,
211
you can still use a single floppy to do the initial boot and then
212
switch to USB. Boot your system as described in <xref linkend="floppy-boot"/>;
213
the kernel on the boot floppy should detect your USB stick automatically.
214
When it asks for the root floppy, simply press &enterkey;. You should see
220
<sect2 arch="i386" id="floppy-boot">
221
<title>Booting from Floppies</title>
224
You will have already downloaded the floppy images you needed and
225
created floppies from the images in <xref linkend="create-floppy"/>.
226
<!-- missing-doc FIXME If you need to, you can also modify the boot floppy; see
227
<xref linkend="rescue-replace-kernel"/>. -->
231
To boot from the installer boot floppy, place it in the primary floppy
232
drive, shut down the system as you normally would, then turn it back
237
For installing from an LS-120 drive (ATAPI version) with a set of
238
floppies, you need to specify the virtual location for the floppy
239
device. This is done with the <emphasis>root=</emphasis> boot
240
argument, giving the device that the ide-floppy driver maps the device
241
to. For example, if your LS-120 drive is connected as the first IDE
242
device (master) on the second cable, you enter
243
<userinput>linux root=/dev/hdc</userinput> at the boot prompt.
244
Installation from LS-120 is only supported by 2.4 and later kernels.
248
Note that on some machines, <keycombo><keycap>Control</keycap>
249
<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not
250
properly reset the machine, so a <quote>hard</quote> reboot is recommended. If
251
you are installing from an existing operating system (e.g., from a DOS
252
box) you don't have a choice. Otherwise, please do a hard reboot when
257
The floppy disk will be accessed, and you should then see a screen
258
that introduces the boot floppy and ends with the <prompt>boot:</prompt>
263
Once you press &enterkey;, you should see the message
264
<computeroutput>Loading...</computeroutput>, followed by
265
<computeroutput>Uncompressing Linux...</computeroutput>, and
266
then a screenfull or so of information about the hardware in your
267
system. More information on this phase of the boot process can be
268
found below in <xref linkend="kernel-msgs"/>.
272
After booting from the boot floppy, the root floppy is
273
requested. Insert the root floppy and press &enterkey;, and the
274
contents are loaded into memory. The installer program
275
<command>debian-installer</command> is automatically launched.
280
<sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title>
282
&boot-installer-intro-net.xml;
286
There are various ways to do a TFTP boot on i386.
290
<sect3><title>NIC or Motherboard that support PXE</title>
293
It could be that your Network Interface Card or Motherboard provides
294
PXE boot functionality.
295
This is a <trademark class="trade">Intel</trademark> re-implementation
296
of TFTP boot. If so you may be able to configure your BIOS to boot from the
302
<sect3><title>NIC with Network BootROM</title>
305
It could be that your Network Interface Card provides
306
TFTP boot functionality.
308
</para><para condition="FIXME">
310
Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
311
Please refer to this document.
316
<sect3><title>Etherboot</title>
319
The <ulink url="http://www.etherboot.org">etherboot project</ulink>
320
provides bootdiskettes and even bootroms that do a TFTPboot.
326
<sect2 arch="i386"><title>The Boot Prompt</title>
329
When the installer boots, you should be presented with a friendly graphical
330
screen showing the Debian logo and the boot prompt:
332
<informalexample><screen>
333
Press F1 for help, or ENTER to boot:
334
</screen></informalexample>
337
you can either just press &enterkey; to boot the installer with
338
default options or enter a specific boot method and, optionally, boot
343
Information on available boot methods and on boot parameters which might
344
be useful can be found by pressing <keycap>F2</keycap> through
345
<phrase condition="sarge"><keycap>F7</keycap></phrase><phrase
346
condition="etch"><keycap>F8</keycap></phrase>. If you add any parameters to
347
the boot command line, be sure to type the boot method (the default is
348
<userinput>linux</userinput>) and a space before the first parameter (e.g.,
349
<userinput>linux debconf/priority=medium</userinput>).
353
If you are installing the system via a remote management device that
354
provides a text interface to the VGA console, you may not be able to
355
see the initial graphical splash screen upon booting the installer;
356
you may even not see the boot prompt. Examples of these devices include
357
the text console of Compaq's <quote>integrated Lights Out</quote> (iLO)
358
and HP's <quote>Integrated Remote Assistant</quote> (IRA).
359
You can blindly press F1<footnote>
363
In some cases these devices will require special escape sequences to
364
enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap>
365
<keycap>F</keycap> </keycombo>, <keycap>1</keycap>.
369
</footnote> to bypass this screen and view the help text. Once you are
370
past the splash screen and at the help text your keystrokes will be echoed
371
at the prompt as expected. To prevent the installer from using the
372
framebuffer for the rest of the installation, you will also want to add
373
<userinput>debian-installer/framebuffer=false</userinput> to the boot prompt,
374
as described in the help text.