| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- original version: 24663 untranslated -->
|
| 3 |
|
| 4 |
<sect2 arch="i386"><title>Booting from a CD-ROM</title>
|
| 5 |
|
| 6 |
&boot-installer-intro-cd.xml;
|
| 7 |
|
| 8 |
<!-- We'll comment the following section until we know exact layout -->
|
| 9 |
<!--
|
| 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;.
|
| 16 |
|
| 17 |
</para><para>
|
| 18 |
|
| 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),
|
| 23 |
or CD5 (bf2.4).
|
| 24 |
|
| 25 |
</para><para>
|
| 26 |
|
| 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
|
| 31 |
different CD-ROMs:
|
| 32 |
|
| 33 |
<variablelist>
|
| 34 |
<varlistentry>
|
| 35 |
<term>CD 1</term><listitem><para>
|
| 36 |
|
| 37 |
Allows a selection of kernel images to boot from (the idepci flavor is
|
| 38 |
the default if no selection is made).
|
| 39 |
|
| 40 |
</para></listitem></varlistentry>
|
| 41 |
<varlistentry>
|
| 42 |
<term>CD 2</term><listitem><para>
|
| 43 |
|
| 44 |
Boots the `vanilla' flavor.
|
| 45 |
|
| 46 |
</para></listitem></varlistentry>
|
| 47 |
<varlistentry>
|
| 48 |
<term>CD 3</term><listitem><para>
|
| 49 |
|
| 50 |
Boots the `compact' flavor.
|
| 51 |
|
| 52 |
</para></listitem></varlistentry>
|
| 53 |
<varlistentry>
|
| 54 |
<term>CD 4</term><listitem><para>
|
| 55 |
|
| 56 |
Boots the `idepci' flavor.
|
| 57 |
|
| 58 |
</para></listitem></varlistentry>
|
| 59 |
<varlistentry>
|
| 60 |
<term>CD 5</term><listitem><para>
|
| 61 |
|
| 62 |
Boots the `bf2.4' flavor.
|
| 63 |
|
| 64 |
</para></listitem></varlistentry>
|
| 65 |
|
| 66 |
</variablelist>
|
| 67 |
|
| 68 |
</para><para>
|
| 69 |
|
| 70 |
-->
|
| 71 |
|
| 72 |
</sect2>
|
| 73 |
|
| 74 |
<!-- FIXME the documented procedure does not exactly work, commented out
|
| 75 |
until fixes
|
| 76 |
|
| 77 |
<sect2 arch="i386" id="install-from-dos">
|
| 78 |
<title>Booting from a DOS partition</title>
|
| 79 |
|
| 80 |
&boot-installer-intro-hd.xml;
|
| 81 |
|
| 82 |
<para>
|
| 83 |
|
| 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 `safe mode command prompt only'
|
| 87 |
option). Enter the subdirectory for the flavor you chose, e.g.,
|
| 88 |
|
| 89 |
<informalexample><screen>
|
| 90 |
cd c:\install
|
| 91 |
</screen></informalexample>.
|
| 92 |
|
| 93 |
Next, execute <command>install.bat</command>.
|
| 94 |
The kernel will load and launch the installer system.
|
| 95 |
|
| 96 |
</para><para>
|
| 97 |
|
| 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.
|
| 102 |
|
| 103 |
</para>
|
| 104 |
</sect2>
|
| 105 |
|
| 106 |
END FIXME -->
|
| 107 |
|
| 108 |
<sect2 arch="i386" id="boot-initrd">
|
| 109 |
<title>Booting from linux using <command>LILO</command> or
|
| 110 |
<command>GRUB</command></title>
|
| 111 |
|
| 112 |
<para>
|
| 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"/>.
|
| 115 |
</para>
|
| 116 |
|
| 117 |
<para>
|
| 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 corresponding kernel.
|
| 121 |
This will allow you
|
| 122 |
to repartition the hard disk from which you boot the installer, although
|
| 123 |
you should do so with care.
|
| 124 |
</para>
|
| 125 |
|
| 126 |
<para>
|
| 127 |
Alternatively, if you intend to keep an existing partition on the hard
|
| 128 |
drive unchanged during the install, you can download the
|
| 129 |
<filename>hd-media/initrd.gz</filename>
|
| 130 |
file and its kernel, as well as copy a CD iso to the drive (make sure the
|
| 131 |
file is named ending in ".iso". The installer can then boot from the drive
|
| 132 |
and install from the CD image, without needing the network.
|
| 133 |
</para>
|
| 134 |
|
| 135 |
<para>
|
| 136 |
For <command>LILO</command>, you will need to configure two
|
| 137 |
essential things in <filename>/etc/lilo.conf</filename>:
|
| 138 |
<itemizedlist>
|
| 139 |
<listitem><para>
|
| 140 |
|
| 141 |
to load the <filename>initrd.gz</filename> installer at boot time;
|
| 142 |
|
| 143 |
</para></listitem>
|
| 144 |
<listitem><para>
|
| 145 |
|
| 146 |
have the <filename>vmlinuz</filename> kernel use a RAM disk as
|
| 147 |
its root partition.
|
| 148 |
|
| 149 |
</para></listitem>
|
| 150 |
</itemizedlist>
|
| 151 |
|
| 152 |
Here is a <filename>/etc/lilo.conf</filename> example:
|
| 153 |
|
| 154 |
</para><para>
|
| 155 |
|
| 156 |
<informalexample><screen>
|
| 157 |
image=/boot/newinstall/vmlinuz
|
| 158 |
label=newinstall
|
| 159 |
initrd=/boot/newinstall/initrd.gz
|
| 160 |
root=/dev/ram0
|
| 161 |
append="devfs=mount,dall ramdisk_size=12000"
|
| 162 |
</screen></informalexample>
|
| 163 |
|
| 164 |
For more details, refer to the
|
| 165 |
<citerefentry><refentrytitle>initrd</refentrytitle>
|
| 166 |
<manvolnum>4</manvolnum></citerefentry> and
|
| 167 |
<citerefentry><refentrytitle>lilo.conf</refentrytitle>
|
| 168 |
<manvolnum>5</manvolnum></citerefentry> man pages. Now run
|
| 169 |
<userinput>lilo</userinput> and reboot.
|
| 170 |
|
| 171 |
</para><para>
|
| 172 |
|
| 173 |
The procedure for <command>GRUB</command> is quite similar. Locate your
|
| 174 |
<filename>menu.lst</filename> in the <filename>/boot/grub/</filename>
|
| 175 |
directory (sometimes in the <filename>/boot/boot/grub/</filename>),
|
| 176 |
add the following lines:
|
| 177 |
|
| 178 |
<informalexample><screen>
|
| 179 |
title New Install
|
| 180 |
kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000
|
| 181 |
initrd (hd0,0)/boot/newinstall/initrd.gz
|
| 182 |
</screen></informalexample>
|
| 183 |
|
| 184 |
and reboot. If the boot fails, you can try adding
|
| 185 |
<userinput>devfs=mount,dall</userinput> to the <quote>kernel</quote> line.
|
| 186 |
|
| 187 |
</para><para>
|
| 188 |
|
| 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>.
|
| 193 |
|
| 194 |
</para>
|
| 195 |
</sect2>
|
| 196 |
|
| 197 |
<sect2 arch="i386" id="usb-boot">
|
| 198 |
<title>Booting from USB memory stick</title>
|
| 199 |
<para>
|
| 200 |
|
| 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;.
|
| 207 |
|
| 208 |
</para><para>
|
| 209 |
|
| 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
|
| 215 |
&d-i; starting.
|
| 216 |
|
| 217 |
</para>
|
| 218 |
</sect2>
|
| 219 |
|
| 220 |
<sect2 arch="i386" id="floppy-boot">
|
| 221 |
<title>Booting from Floppies</title>
|
| 222 |
<para>
|
| 223 |
|
| 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"/>. -->
|
| 228 |
|
| 229 |
</para><para>
|
| 230 |
|
| 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
|
| 233 |
on.
|
| 234 |
|
| 235 |
</para><para>
|
| 236 |
|
| 237 |
For installing from a 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.
|
| 245 |
|
| 246 |
</para><para>
|
| 247 |
|
| 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 ``hard'' 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
|
| 253 |
booting.
|
| 254 |
|
| 255 |
</para><para>
|
| 256 |
|
| 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>
|
| 259 |
prompt.
|
| 260 |
|
| 261 |
</para><para>
|
| 262 |
|
| 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"/>.
|
| 269 |
|
| 270 |
</para><para>
|
| 271 |
|
| 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.
|
| 276 |
|
| 277 |
</para>
|
| 278 |
</sect2>
|
| 279 |
|
| 280 |
<sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title>
|
| 281 |
|
| 282 |
&boot-installer-intro-net.xml;
|
| 283 |
|
| 284 |
<para>
|
| 285 |
|
| 286 |
There are various ways to do a TFTP boot on i386.
|
| 287 |
|
| 288 |
</para>
|
| 289 |
|
| 290 |
<sect3><title>NIC or Motherboard that support PXE</title>
|
| 291 |
<para>
|
| 292 |
|
| 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-implemention
|
| 296 |
of TFTP boot. If so you may be able to configure your BIOS to boot from the
|
| 297 |
network.
|
| 298 |
|
| 299 |
</para>
|
| 300 |
</sect3>
|
| 301 |
|
| 302 |
<sect3><title>NIC with network bootROM</title>
|
| 303 |
<para>
|
| 304 |
|
| 305 |
It could be that your Network Interface Card provides
|
| 306 |
TFTP boot functionality.
|
| 307 |
|
| 308 |
</para><para condition="FIXME">
|
| 309 |
|
| 310 |
Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
|
| 311 |
Please refer to this document.
|
| 312 |
|
| 313 |
</para>
|
| 314 |
</sect3>
|
| 315 |
|
| 316 |
<sect3><title>Etherboot</title>
|
| 317 |
<para>
|
| 318 |
|
| 319 |
The <ulink url="http://www.etherboot.org">etherboot project</ulink>
|
| 320 |
provides bootdiskettes and even bootroms that do a TFTPboot.
|
| 321 |
|
| 322 |
</para>
|
| 323 |
</sect3>
|
| 324 |
</sect2>
|
| 325 |
|
| 326 |
<sect2 arch="i386"><title>i386 Boot Parameters</title>
|
| 327 |
<para>
|
| 328 |
|
| 329 |
When the installer boots, you will be presented with the boot prompt,
|
| 330 |
<prompt>boot:</prompt>. You can do two things at the <prompt>boot:</prompt>
|
| 331 |
prompt. You can press the function keys <keycap>F1</keycap> through
|
| 332 |
<keycap>F10</keycap> to view a few pages of helpful information, or
|
| 333 |
you can press <keycap>Enter</keycap> to boot the system.
|
| 334 |
|
| 335 |
</para><para>
|
| 336 |
|
| 337 |
Information on boot parameters which might be useful can be found by
|
| 338 |
pressing <keycap>F3</keycap> through <keycap>F7</keycap>. If you add any
|
| 339 |
parameters to
|
| 340 |
the boot command line, be sure to type the boot method (the default is
|
| 341 |
<userinput>linux</userinput>) and a space before the first parameter (e.g.,
|
| 342 |
<userinput>linux floppy=thinkpad</userinput>). If you simply press &enterkey;,
|
| 343 |
that's the same as typing <userinput>linux</userinput> without any special
|
| 344 |
parameters.
|
| 345 |
|
| 346 |
</para><para>
|
| 347 |
|
| 348 |
Some systems have floppies with ``inverted DCLs''. If you receive
|
| 349 |
errors reading from the floppy, even when you know the floppy is good,
|
| 350 |
try the parameter <userinput>floppy=thinkpad</userinput>.
|
| 351 |
|
| 352 |
</para><para>
|
| 353 |
|
| 354 |
On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506
|
| 355 |
disk drivers), the IDE drive may not be properly recognized. Again,
|
| 356 |
try it first without the parameters and see if the IDE drive is
|
| 357 |
recognized properly. If not, determine your drive geometry
|
| 358 |
(cylinders, heads, and sectors), and use the parameter
|
| 359 |
<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>.
|
| 360 |
|
| 361 |
</para><para>
|
| 362 |
|
| 363 |
If you have a very old machine, and the kernel hangs after saying
|
| 364 |
<computeroutput>Checking 'hlt' instruction...</computeroutput>, then
|
| 365 |
you should try the <userinput>no-hlt</userinput> boot argument, which
|
| 366 |
disables this test.
|
| 367 |
|
| 368 |
</para><para>
|
| 369 |
|
| 370 |
If your screen begins to show a weird picture while the kernel boots,
|
| 371 |
eg. pure white, pure black or colored pixel garbage, your system may
|
| 372 |
contain a problematic video card which does not switch to the
|
| 373 |
framebuffer mode properly. Then you can use the boot parameter
|
| 374 |
<userinput>debian-installer/framebuffer=false</userinput> or
|
| 375 |
<userinput>video=vga16:off</userinput> to disable the framebuffer
|
| 376 |
console. Only the English
|
| 377 |
language will be available during the installation due to limited
|
| 378 |
console features. See <xref linkend="boot-parms"/> for details.
|
| 379 |
|
| 380 |
</para>
|
| 381 |
</sect2>
|
| 382 |
|
| 383 |
|
| 384 |
<sect2 arch="i386">
|
| 385 |
<title>System freeze during the PCMCIA configuration phase</title>
|
| 386 |
|
| 387 |
<para>
|
| 388 |
|
| 389 |
Some laptop models produced by Dell are known to crash when PCMCIA device
|
| 390 |
detection tries to access some hardware addresses. Other laptops may display
|
| 391 |
similar problems. If you experience such a problem and you don't need PCMCIA
|
| 392 |
support during the installation, you can disable PCMCIA using the
|
| 393 |
<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can
|
| 394 |
then configure PCMCIA after the installation is completed and exclude the
|
| 395 |
resource range causing the problems.
|
| 396 |
|
| 397 |
</para><para>
|
| 398 |
|
| 399 |
Alternatively, you can boot the installer in expert mode. You will
|
| 400 |
then be asked to enter the resource range options your hardware
|
| 401 |
needs. For example, if you have one of the Dell laptops mentioned
|
| 402 |
above, you should enter <userinput>exclude port
|
| 403 |
0x800-0x8ff</userinput> here. There is also a list of some common
|
| 404 |
resource range options in the <ulink
|
| 405 |
url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System
|
| 406 |
resource settings section of the PCMCIA HOWTO</ulink>. Note that you
|
| 407 |
have to omit the commas, if any, when you enter this value in the
|
| 408 |
installer.
|
| 409 |
|
| 410 |
</para>
|
| 411 |
</sect2>
|
| 412 |
|
| 413 |
<sect2 arch="i386">
|
| 414 |
<title>System freeze while loading the USB modules</title>
|
| 415 |
<para>
|
| 416 |
|
| 417 |
The kernel normally tries to install USB modules and the USB keyboard driver
|
| 418 |
in order to support some non-standard USB keyboards. However, there are some
|
| 419 |
broken USB systems where the driver hangs on loading. A possible workaround
|
| 420 |
may be disabling the USB controller in your mainboard BIOS setup. Another option
|
| 421 |
is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter
|
| 422 |
at the boot prompt, which will prevent the modules from being loaded.
|
| 423 |
|
| 424 |
</para>
|
| 425 |
</sect2>
|
Parent Directory
| 
Revision Log