| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- original version: 22935 untranslated -->
|
| 3 |
|
| 4 |
<sect1 id="boot-parms"><title>Boot Parameters</title>
|
| 5 |
<para>
|
| 6 |
|
| 7 |
Boot parameters are Linux kernel parameters which are generally used
|
| 8 |
to make sure that peripherals are dealt with properly. For the most
|
| 9 |
part, the kernel can auto-detect information about your peripherals.
|
| 10 |
However, in some cases you'll have to help the kernel a bit.
|
| 11 |
|
| 12 |
</para><para>
|
| 13 |
|
| 14 |
If this is the first time you're booting the system, try the default
|
| 15 |
boot parameters (i.e., don't try setting parameters) and see if it works
|
| 16 |
correctly. It probably will. If not, you can reboot later and look for
|
| 17 |
any special parameters that inform the system about your hardware.
|
| 18 |
|
| 19 |
</para><para>
|
| 20 |
|
| 21 |
Information on many boot parameters can be found in the
|
| 22 |
<ulink url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html"> Linux
|
| 23 |
BootPrompt HOWTO</ulink>, including tips for obscure hardware. This
|
| 24 |
section contains only a sketch of the most salient parameters. Some
|
| 25 |
common gotchas are included below in
|
| 26 |
<xref linkend="boot-troubleshooting"/>.
|
| 27 |
|
| 28 |
</para><para>
|
| 29 |
|
| 30 |
When the kernel boots, a message
|
| 31 |
|
| 32 |
<informalexample><screen>
|
| 33 |
|
| 34 |
Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available
|
| 35 |
|
| 36 |
</screen></informalexample>
|
| 37 |
|
| 38 |
should be emitted early in the process.
|
| 39 |
<replaceable>total</replaceable> should match the total amount of RAM,
|
| 40 |
in kilobytes. If this doesn't match the actual amount of RAM you have
|
| 41 |
installed, you need to use the
|
| 42 |
<userinput>mem=<replaceable>ram</replaceable></userinput> parameter,
|
| 43 |
where <replaceable>ram</replaceable> is set to the amount of memory,
|
| 44 |
suffixed with ``k'' for kilobytes, or ``m'' for megabytes. For
|
| 45 |
example, both <userinput>mem=65536k</userinput> and
|
| 46 |
<userinput>mem=64m</userinput> mean 64MB of RAM.
|
| 47 |
|
| 48 |
</para><para condition="supports-serial-console">
|
| 49 |
|
| 50 |
If you are booting with a serial console, generally the kernel will
|
| 51 |
autodetect this
|
| 52 |
<phrase arch="mipsel">(although not on DECstations)</phrase>
|
| 53 |
If you have a videocard (framebuffer) and a keyboard also attached to
|
| 54 |
the computer which you wish to boot via serial console, you may have
|
| 55 |
to pass the
|
| 56 |
<userinput>console=<replaceable>device</replaceable></userinput>
|
| 57 |
argument to the kernel, where <replaceable>device</replaceable> is
|
| 58 |
your serial device, which is usually something like
|
| 59 |
<filename>ttyS0</filename>.
|
| 60 |
|
| 61 |
</para><para arch="sparc">
|
| 62 |
|
| 63 |
For &arch-title; the serial devices are <filename>ttya</filename> or
|
| 64 |
<filename>ttyb</filename>.
|
| 65 |
Alternatively, set the <envar>input-device</envar> and
|
| 66 |
<envar>output-device</envar> OpenPROM variables to
|
| 67 |
<filename>ttya</filename>.
|
| 68 |
|
| 69 |
</para>
|
| 70 |
|
| 71 |
|
| 72 |
<sect2 id="installer-args"><title>Debian Installer Parameters</title>
|
| 73 |
<para>
|
| 74 |
|
| 75 |
The installation system recognizes a few additional boot parameters which may
|
| 76 |
be useful.
|
| 77 |
|
| 78 |
</para>
|
| 79 |
|
| 80 |
<variablelist>
|
| 81 |
<varlistentry>
|
| 82 |
<term>debconf/priority</term>
|
| 83 |
<listitem><para>
|
| 84 |
|
| 85 |
This parameter settings will set the highest priority of messages
|
| 86 |
to be displayed.
|
| 87 |
|
| 88 |
</para><para>
|
| 89 |
|
| 90 |
The default installation uses <userinput>debconf/priority=high</userinput>.
|
| 91 |
This means that both high and critical priority messages are shown, but medium
|
| 92 |
and low priority messages are skipped.
|
| 93 |
If problems are encountered, the installer adjusts the priority as needed.
|
| 94 |
|
| 95 |
</para><para>
|
| 96 |
|
| 97 |
If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you
|
| 98 |
will be shown the installation menu and gain more control over the installation.
|
| 99 |
When <userinput>debconf/priority=low</userinput> is used, all messages are shown
|
| 100 |
(this is equivalent to the <emphasis>expert</emphasis> boot method).
|
| 101 |
With <userinput>debconf/priority=critical</userinput>, the installation system
|
| 102 |
will display only critical messages and try to do the right thing without fuss.
|
| 103 |
|
| 104 |
</para></listitem>
|
| 105 |
</varlistentry>
|
| 106 |
|
| 107 |
|
| 108 |
<varlistentry>
|
| 109 |
<term>DEBIAN_FRONTEND</term>
|
| 110 |
<listitem><para>
|
| 111 |
|
| 112 |
This boot parameter controls the type of user interface used for the
|
| 113 |
installer. The current possible parameter settings are:
|
| 114 |
|
| 115 |
<itemizedlist>
|
| 116 |
<listitem>
|
| 117 |
<para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para>
|
| 118 |
</listitem><listitem>
|
| 119 |
<para><userinput>DEBIAN_FRONTEND=text</userinput></para>
|
| 120 |
</listitem><listitem>
|
| 121 |
<para><userinput>DEBIAN_FRONTEND=newt</userinput></para>
|
| 122 |
</listitem><listitem>
|
| 123 |
<para><userinput>DEBIAN_FRONTEND=slang</userinput></para>
|
| 124 |
</listitem><listitem>
|
| 125 |
<para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para>
|
| 126 |
</listitem><listitem>
|
| 127 |
<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para>
|
| 128 |
</listitem><listitem>
|
| 129 |
<para><userinput>DEBIAN_FRONTEND=gtk</userinput></para>
|
| 130 |
</listitem><listitem>
|
| 131 |
<para><userinput>DEBIAN_FRONTEND=corba</userinput></para>
|
| 132 |
</listitem>
|
| 133 |
</itemizedlist>
|
| 134 |
|
| 135 |
The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>.
|
| 136 |
<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for
|
| 137 |
serial console installs. Generally only the
|
| 138 |
<userinput>newt</userinput> frontend is available on default install
|
| 139 |
media, so this is not very useful right now.
|
| 140 |
|
| 141 |
</para></listitem>
|
| 142 |
</varlistentry>
|
| 143 |
|
| 144 |
|
| 145 |
<varlistentry>
|
| 146 |
<term>BOOT_DEBUG</term>
|
| 147 |
<listitem><para>
|
| 148 |
|
| 149 |
Passing this boot parameter will cause the boot to be more verbosely
|
| 150 |
logged.
|
| 151 |
|
| 152 |
<variablelist>
|
| 153 |
<varlistentry>
|
| 154 |
<term><userinput>BOOT_DEBUG=0</userinput></term>
|
| 155 |
<listitem><para>This is the default.</para></listitem>
|
| 156 |
</varlistentry>
|
| 157 |
|
| 158 |
<varlistentry>
|
| 159 |
<term><userinput>BOOT_DEBUG=1</userinput></term>
|
| 160 |
<listitem><para>More verbose than usual.</para></listitem>
|
| 161 |
</varlistentry>
|
| 162 |
|
| 163 |
<varlistentry>
|
| 164 |
<term><userinput>BOOT_DEBUG=2</userinput></term>
|
| 165 |
<listitem><para>Lots of debugging information.</para></listitem>
|
| 166 |
</varlistentry>
|
| 167 |
|
| 168 |
<varlistentry>
|
| 169 |
<term><userinput>BOOT_DEBUG=3</userinput></term>
|
| 170 |
<listitem><para>
|
| 171 |
|
| 172 |
Shells are run at various points in the boot process to allow detailed
|
| 173 |
debugging. Exit the shell to continue the boot.
|
| 174 |
|
| 175 |
</para></listitem>
|
| 176 |
</varlistentry>
|
| 177 |
</variablelist>
|
| 178 |
|
| 179 |
</para></listitem>
|
| 180 |
</varlistentry>
|
| 181 |
|
| 182 |
|
| 183 |
<varlistentry>
|
| 184 |
<term>INSTALL_MEDIA_DEV</term>
|
| 185 |
<listitem><para>
|
| 186 |
|
| 187 |
The value of the parameter is the path to the device to load the
|
| 188 |
Debian installer from. For example,
|
| 189 |
<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>
|
| 190 |
|
| 191 |
</para><para>
|
| 192 |
|
| 193 |
The boot floppy, which normally scans all floppies and USB storage
|
| 194 |
devices it can to find the root floppy, can be overridden by this
|
| 195 |
parameter to only look at the one device.
|
| 196 |
|
| 197 |
</para></listitem>
|
| 198 |
</varlistentry>
|
| 199 |
|
| 200 |
<varlistentry>
|
| 201 |
<term>debian-installer/framebuffer</term>
|
| 202 |
<listitem><para>
|
| 203 |
|
| 204 |
Some architectures use the kernel framebuffer to offer installation in
|
| 205 |
a number of languages. If framebuffer causes a problem on your system
|
| 206 |
you can disable the feature by the parameter
|
| 207 |
<userinput>debian-installer/framebuffer=false</userinput>. Problem
|
| 208 |
symptoms are error messages about bterm or bogl, a blank screen, or
|
| 209 |
a freeze within a few minutes after starting the install.
|
| 210 |
|
| 211 |
</para><para arch="i386">
|
| 212 |
|
| 213 |
The <userinput>video=vga16:off</userinput> argument may also be used
|
| 214 |
to disable the framebuffer. Such problems have been reported on a Dell
|
| 215 |
Inspiron with Mobile Radeon card.
|
| 216 |
|
| 217 |
</para><para arch="m68k">
|
| 218 |
|
| 219 |
Such problems have been reported on the Amiga 1200 and SE/30.
|
| 220 |
|
| 221 |
</para><para arch="hppa">
|
| 222 |
|
| 223 |
Such problems have been reported on hppa.
|
| 224 |
|
| 225 |
</para></listitem>
|
| 226 |
</varlistentry>
|
| 227 |
|
| 228 |
<varlistentry>
|
| 229 |
<term>debian-installer/probe/usb</term>
|
| 230 |
<listitem><para>
|
| 231 |
|
| 232 |
Set to <userinput>false</userinput> to prevent probing for USB on
|
| 233 |
boot, if that causes problems.
|
| 234 |
|
| 235 |
</para></listitem>
|
| 236 |
</varlistentry>
|
| 237 |
|
| 238 |
<varlistentry>
|
| 239 |
<term>netcfg/disable_dhcp</term>
|
| 240 |
<listitem><para>
|
| 241 |
|
| 242 |
By default, the &d-i; automatically probes for network configuration
|
| 243 |
via DHCP. If the probe succeeds, you won't have a chance to review and
|
| 244 |
change the obtained settings. You can get to the manual network setup
|
| 245 |
only in case the DHCP probe fails.
|
| 246 |
|
| 247 |
</para><para>
|
| 248 |
|
| 249 |
If you have a DHCP server on your local network, but want to avoid it
|
| 250 |
because e.g. it gives wrong answers, you can use the parameter
|
| 251 |
<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring
|
| 252 |
the network with DHCP and to enter the information manually.
|
| 253 |
|
| 254 |
</para></listitem>
|
| 255 |
</varlistentry>
|
| 256 |
|
| 257 |
<varlistentry>
|
| 258 |
<term>hw-detect/start_pcmcia</term>
|
| 259 |
<listitem><para>
|
| 260 |
|
| 261 |
Set to <userinput>false</userinput> to prevent starting PCMCIA
|
| 262 |
services, if that causes problems. Some laptops are well known for
|
| 263 |
this misbehavior.
|
| 264 |
|
| 265 |
</para></listitem>
|
| 266 |
</varlistentry>
|
| 267 |
|
| 268 |
<varlistentry>
|
| 269 |
<term>preseed/url</term>
|
| 270 |
<listitem><para>
|
| 271 |
|
| 272 |
Specify the url to a preconfiguration file to download and use in
|
| 273 |
automating the install. See <xref linkend="automatic-install"/>.
|
| 274 |
|
| 275 |
</para></listitem>
|
| 276 |
</varlistentry>
|
| 277 |
|
| 278 |
<varlistentry>
|
| 279 |
<term>preseed/file</term>
|
| 280 |
<listitem><para>
|
| 281 |
|
| 282 |
Specify the url to a preconfiguration file to load to
|
| 283 |
automating the install. See <xref linkend="automatic-install"/>.
|
| 284 |
|
| 285 |
</para></listitem>
|
| 286 |
</varlistentry>
|
| 287 |
|
| 288 |
<varlistentry>
|
| 289 |
<term>ramdisk_size</term>
|
| 290 |
<listitem><para>
|
| 291 |
|
| 292 |
If you are using a 2.2.x kernel, you may need to set &ramdisksize;.
|
| 293 |
|
| 294 |
</para></listitem>
|
| 295 |
</varlistentry>
|
| 296 |
|
| 297 |
</variablelist>
|
| 298 |
</sect2>
|
| 299 |
</sect1>
|
| 300 |
|
Parent Directory
| 
Revision Log