1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 16879 untranslated -->
4
<sect2 arch="i386"><title>Booting from a CD-ROM</title>
6
&boot-installer-intro-cd.xml;
10
You may need to configure your hardware as indicated in
11
<xref linkend="boot-dev-select"/>. Then put the CD-ROM into the drive,
12
and reboot. The system should boot up, and you should be presented
13
with the <prompt>boot:</prompt> prompt. Here you can enter your
14
boot arguments, or just hit &enterkey;.
18
<!-- We'll comment the following section until we know exact layout -->
20
CD #1 of official Debian CD-ROM sets for &arch-title; will present a
21
<prompt>boot:</prompt> prompt on most hardware. Press
22
<keycap>F3</keycap> to see the list of kernel options available
23
from which to boot. Just type your chosen flavor name (idepci,
24
vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt
25
followed by &enterkey;.
29
If your hardware doesn't support booting of multiple images, put one
30
of the other CDs in the drive. It appears that most SCSI CD-ROM drives
31
do not support <command>isolinux</command> multiple image booting, so users
32
with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact),
37
CD's 2 through 5 will each boot a
38
different ``flavor'' depending on which CD-ROM is
39
inserted. See <xref linkend="kernel-choice"/> for a discussion of the
40
different flavors. Here's how the flavors are laid out on the
45
<term>CD 1</term><listitem><para>
47
Allows a selection of kernel images to boot from (the idepci flavor is
48
the default if no selection is made).
50
</para></listitem></varlistentry>
52
<term>CD 2</term><listitem><para>
54
Boots the `vanilla' flavor.
56
</para></listitem></varlistentry>
58
<term>CD 3</term><listitem><para>
60
Boots the `compact' flavor.
62
</para></listitem></varlistentry>
64
<term>CD 4</term><listitem><para>
66
Boots the `idepci' flavor.
68
</para></listitem></varlistentry>
70
<term>CD 5</term><listitem><para>
72
Boots the `bf2.4' flavor.
74
</para></listitem></varlistentry>
82
If your system can't boot directly from CD-ROM, or you simply can't
83
seem to get it to work, don't despair; you can simply run
84
<command>E:\install\boot.bat</command> under DOS (replace
85
<userinput>E:</userinput> with whatever drive letter DOS assigns to
86
your CD-ROM drive) to start the installation process. Then, skip down
87
to <xref linkend="init-config"/>.
91
Also, if you're going to be installing from a FAT (DOS) partition, you
92
have the option of booting the installer from the hard disk. See
93
<xref linkend="install-from-dos"/> for more information on
94
installing via this method.
101
<sect2 arch="i386" id="install-from-dos">
102
<title>Booting from a DOS partition</title>
104
&boot-installer-intro-hd.xml;
108
Boot into DOS (not Windows) without any drivers being loaded. To do
109
this, you have to press <keycap>F8</keycap> at exactly the right
110
moment (and optionally select the `safe mode command prompt only'
111
option). Enter the subdirectory for the flavor you chose, e.g.,
113
<informalexample><screen>
115
cd c:\current\compact
117
</screen></informalexample>.
119
Next, execute <command>install.bat</command>.
120
The kernel will load and launch the installer system.
124
Please note, there is currently a loadlin problem (#142421) which
125
precludes <filename>install.bat</filename> from being used with the
126
bf2.4 flavor. The symptom of the problem is an
127
<computeroutput>invalid compressed format</computeroutput> error.
133
<sect2 arch="i386" id="boot-initrd">
134
<title>Booting from linux using <command>LILO</command> or
135
<command>GRUB</command></title>
138
For <command>LILO</command>, you will need to configure two
139
essentials things in <filename>/etc/lilo.conf</filename>:
143
to load the <filename>initrd.gz</filename> installer at boot time;
148
have the <filename>vmlinuz</filename> kernel use a RAM disk as
154
Here is a <filename>/etc/lilo.conf</filename> example:
158
<informalexample><screen>
160
image=/boot/newinstall/vmlinuz
162
initrd=/boot/newinstall/initrd.gz
164
append="devfs=mount,dall"
166
</screen></informalexample>
168
For more details, refer to the
169
<citerefentry><refentrytitle>initrd</refentrytitle>
170
<manvolnum>4</manvolnum></citerefentry> and
171
<citerefentry><refentrytitle>lilo.conf</refentrytitle>
172
<manvolnum>5</manvolnum></citerefentry> man pages. Now run
173
<userinput>lilo</userinput> and reboot.
177
The procedure for <command>GRUB</command> is quite similar. Locate your
178
<filename>menu.lst</filename> in the <filename>/boot/grub/</filename>
179
directory (sometimes in the <filename>/boot/boot/grub/</filename>),
180
add the following lines:
182
<informalexample><screen>
185
kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram devfs=mount,dall
186
initrd (hd0,0)/boot/newinstall/initrd.gz
188
</screen></informalexample>
190
and reboot. Please note, that you may need an additional parameter
191
<userinput>ramdisk_size=<replaceable>size in KB</replaceable></userinput>,
192
depending on the image you are booting. From now on, there should be
193
no difference between <command>GRUB</command> or <command>LILO</command>.
197
You can trace the <filename>initrd</filename> magic at work several
198
times during the boot.
203
before the kernel has even been loaded, <command>LILO</command>
204
displays a much longer <computeroutput>Loading
205
<replaceable>imagelabel</replaceable>......</computeroutput> line with
206
more dots than usual, showing the progression of the RAM disk image
212
You should see the <computeroutput>RAM disk driver
213
initialized</computeroutput>
214
notice, near the real time clock initialization, proving that your
215
kernel supports the RAM disk feature.
220
Finally, if you don't see <computeroutput>RAMDISK: ext2 filesystem
221
found at block 0</computeroutput> immediately after the partition
222
checks, it's probably because
223
your kernel miss the <filename>initrd</filename> feature.
228
</para><para condition="FIXME">
230
You should now see the debian installer running. If you do not use any
231
removable medium, you want to check very early that your network
232
connection is working and <emphasis>before</emphasis> irreversibly
233
partitioning your hard disk. So you maybe need to
234
<userinput>insmod</userinput> some additional kernel modules for this,
235
for instance for your network interface. It's time
236
<emphasis>not</emphasis> to follow the order of steps suggested by
237
<command>debian-installer</command>. Leap directly to <userinput>Mount a
238
Previously-Initialized Partition</userinput>, and mount the partition
239
where you stored the modules that you extracted from
240
<filename>drivers.tgz</filename> (<xref linkend="files-lilo"></xref>).
244
<!-- Ideally, configure Device Driver Modules should support the
245
following (insmod-ing from the hard-disk) and not only from a floppy.
246
That would avoid the need to open a shell -->
250
Then switch to an other virtual terminal and use a shell (see
251
<xref linkend="shell"/>) to find drivers
252
in the just mounted <filename>/target</filename>
253
directory. <userinput>insmod</userinput> the ones you need.
257
Go to <xref linkend="netcfg"/> in the
258
<command>debian-installer</command> installer menus, and
259
<userinput>ping</userinput> your favorite debian mirror at last.
264
Use <userinput>Unmount a Partition</userinput> if you have mounted one
266
paragraph, safely go back to the partitioning steps at the start of
267
<command>debian-installer</command> and follow the regular procedure,
268
with the network as a bonus. At this stage, it is even possible
269
(only a bit risky) to completely wipe out all the previous partitions
270
on your hard drive for a very clean installation. The only risk is that
271
your hard drive will be un-bootable for a short period of time.
276
<sect2 arch="i386" id="usb-boot">
277
<title>Booting from USB memory stick</title>
280
Lets assume you have prepared everything from <xref
281
linkend="boot-dev-select"/> and <xref linkend="boot-usb-files"/>. Now
282
just plug your USB stick into some free USB connector and reboot the
283
computer. The system should boot up, and you should be presented with
284
the <prompt>boot:</prompt> prompt. Here you can enter optional boot
285
arguments, or just hit &enterkey;.
289
In case your computer doesn't support booting from USB memory devices,
290
you can still use a single floppy to do the initial boot and then
291
switch to USB. Advance according to <xref linkend="floppy-boot"/>; the
292
kernel on boot floppy should detect your USB stick automatically. When
293
it asks for the root floppy, simply press &enterkey;. You should see
299
<sect2 arch="i386" id="floppy-boot">
300
<title>Booting from Floppies</title>
303
You will have already downloaded the floppy images you needed and
304
created floppies from the images in <xref linkend="create-floppy"/>.
305
If you need to, you can also modify the boot floppy; see
306
<xref linkend="rescue-replace-kernel"/>.
310
To boot from the installer boot floppy, place it in the primary floppy
311
drive, shut down the system as you normally would, then turn it back
316
For installing from a LS-120 drive (ATAPI version) with a set of
317
floppies, you need to specify the virtual location for the floppy
318
device. This is done with the <emphasis>root=</emphasis> boot
319
argument, giving the device that the ide-floppy driver maps the device
320
to. For example, if your LS-120 drive is connected as the first IDE
321
device (master) on the second cable, you enter
322
<userinput>linux root=/dev/hdc</userinput> at the boot prompt.
323
Installation from LS-120 is only supported by 2.4 and later kernels.
327
Note that on some machines, <keycombo><keycap>Control</keycap>
328
<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not
329
properly reset the machine, so a ``hard'' reboot is recommended. If
330
you are installing from an existing operating system (e.g., from a DOS
331
box) you don't have a choice. Otherwise, please do a hard reboot when
336
The floppy disk will be accessed, and you should then see a screen
337
that introduces the boot floppy and ends with the <prompt>boot:</prompt>
342
You can do two things at the <prompt>boot:</prompt> prompt. You can
343
press the function keys <keycap>F1</keycap> through
344
<keycap>F10</keycap> to view a few pages of helpful information, or
345
you can boot the system.
349
Information on boot parameters which might be useful can be found by
350
pressing <keycap>F4</keycap> through <keycap>F7</keycap>. If you add any
352
the boot command line, be sure to type the boot method (the default is
353
<userinput>linux</userinput>) and a space before the first parameter (e.g.,
354
<userinput>linux floppy=thinkpad</userinput>). If you simply press &enterkey;,
355
that's the same as typing <userinput>linux</userinput> without any special
360
Once you press &enterkey;, you should see the message
361
<computeroutput>Loading...</computeroutput>, followed by
362
<computeroutput>Uncompressing Linux...</computeroutput>, and
363
then a screenful or so of information about the hardware in your
364
system. More information on this phase of the boot process can be
365
found below in <xref linkend="kernel-msgs"/>.
369
After booting from the boot floppy, the root floppy is
370
requested. Insert the root floppy and press &enterkey;, and the
371
contents are loaded into memory. The installer program
372
<command>debian-installer</command> is automatically launched.
377
<sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title>
379
&boot-installer-intro-net.xml;
383
There are various ways to do a TFTP boot on i386.
387
<sect3><title>Etherboot</title>
390
The <ulink url="http://www.etherboot.org">etherboot project</ulink>
391
provides bootdiskettes and even bootroms that do a TFTPboot.
396
<sect3><title>NIC with network bootROM</title>
399
It could be that your Network Interface Card provides
400
TFTP boot functionality.
402
</para><para condition="FIXME">
404
Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
405
Please refer to this document.
410
<sect3><title>NIC or Motherboard that support PXE</title>
413
It could be that your Network Interface Card or Motherboard provides
414
PXE boot functionality.
415
Which is a <trademark class="trade">Intel</trademark> re-implemention
418
</para><para condition="FIXME">
420
Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
421
Please refer to this document.
423
<!-- from #debian-boot 2004-03-13
424
06:37 -!- SuperQ [ben@trogdor.likes.to.burninate.net] has joined #debian-boot
425
06:38 < SuperQ> anyone done much with d-i on pxe boot?
426
06:39 < SuperQ> I got it all setup, daily build from sjogren's files
427
06:39 < joshk> yes, it works
428
06:39 < SuperQ> "Warning: unable to open an initial console."
429
06:39 < SuperQ> Kernel panic: Attempted to kill init!
430
06:39 < joshk> pass devfs=mount to the kernel
431
06:40 < joshk> in pxelinux.cfg/whatever
432
06:40 < SuperQ> oh.. that's changed since the bug tracking post
433
06:40 < SuperQ> http://lists.debian.org/debian-testing/2003/debian-testing-200311/msg00098.html
434
06:40 < SuperQ> that says to devfs=nomount
435
06:41 < SuperQ> should probably copy the bulk of that message into
436
debian/dists/sarge/main/installer-i386/current/doc/INSTALLATION-HOWTO
438
06:41 < joshk> that's from months ago
440
06:41 < SuperQ> I know
441
06:42 < SuperQ> but it's still referanced in the howto
442
06:42 < SuperQ> yay! it works now
443
06:42 * SuperQ gives his new ThinkPad X31 some sarge love
444
06:42 < SuperQ> I'll have to write up a page on Sarge/D-I and things for
446
06:45 < SuperQ> thanks joshk
452
<sect2 arch="i386"><title>i386 Boot Parameters</title>
455
If you are booting from the boot floppy or from CD-ROM you will be
456
presented with the boot prompt, <prompt>boot:</prompt>. Details
457
about how to use boot parameters with the boot floppy can be found
458
in <xref linkend="floppy-boot"/>. If you are booting from an
459
existing operating system, you'll have to use other means to set boot
460
parameters. For instance, if you are installing from DOS, you can
461
edit the <filename>install.bat</filename> file with any text editor.
465
Some systems have floppies with ``inverted DCLs''. If you receive
466
errors reading from the floppy, even when you know the floppy is good,
467
try the parameter <userinput>floppy=thinkpad</userinput>.
471
On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506
472
disk drivers), the IDE drive may not be properly recognized. Again,
473
try it first without the parameters and see if the IDE drive is
474
recognized properly. If not, determine your drive geometry
475
(cylinders, heads, and sectors), and use the parameter
476
<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>.
480
If you have a very old machine, and the kernel hangs after saying
481
<computeroutput>Checking 'hlt' instruction...</computeroutput>, then
482
you should try the <userinput>no-hlt</userinput> boot argument, which
487
If your screen begins to show a weird picture while the kernel boots,
488
eg. pure white, pure black or colored pixel garbage, your system may
489
contain a problematic video card which does not switch to the
490
framebuffer mode properly. Then you can use the boot parameter
491
<userinput>debian-installer/framebuffer=false</userinput> or
492
<userinput>video=vga16:off</userinput> to disable the framebuffer
493
console. The language chooser will not appear; only the english
494
language will be available during the installation due to limited
495
console features. See <xref linkend="boot-parms"/> for details.
502
<title>System freeze during the PCMCIA configuration phase</title>
506
Some laptop models produced by Dell are known to crash when PCMCIA device
507
detection tries to access some hardware addresses. Other laptops may display
508
similar problems. If you experience such a problem and you don't need PCMCIA
509
support during the installation, you can disable PCMCIA using the
510
<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can
511
then configure PCMCIA after the installation is completed and exclude the
512
resource range causing the problems.
516
Alternatively, you can boot the installer in expert mode. You will
517
then be asked to enter the resource range options your hardware
518
needs. For example, if you have one of the Dell laptops mentioned
519
above, you should enter <userinput>exclude port
520
0x800-0x8ff</userinput> here. There is also a list of some common
521
resource range options in the <ulink
522
url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-2.html#ss2.5">System
523
resource settings section of the PCMCIA HOWTO</ulink>. Note that you
524
have to omit the commas, if any, when you enter this value in the
531
<title>System freeze while loading the USB modules</title>
534
The kernel normally tries to install USB modules and the USB keyboard driver
535
in order to support some non-standard USB keyboards. However, there are some
536
broken USB systems where the driver hangs on loading. A possible workaround
537
may be disabling the USB controller in your mainboard BIOS setup. Another option
538
is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter
539
at the boot prompt, which will prevent the modules from being loaded.