/[d-i]/trunk/manual/en/boot-installer/parameters.xml
ViewVC logotype

Diff of /trunk/manual/en/boot-installer/parameters.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

trunk/doc/manual/en/boot-installer/parameters.xml revision 5338 by toff, Fri Oct 24 01:03:02 2003 UTC trunk/manual/en/boot-installer/parameters.xml revision 33725 by fjp, Tue Jan 3 19:39:07 2006 UTC
# Line 1  Line 1 
1  <!-- retain these comments for translator revision tracking -->  <!-- retain these comments for translator revision tracking -->
2  <!-- $Id: parameters.xml,v 1.2 2003/10/24 01:03:02 toff Exp $ -->  <!-- $Id$ -->
3    
4   <sect1 id="boot-parms"><title>Boot Parameters</title>   <sect1 id="boot-parms"><title>Boot Parameters</title>
5  <para>  <para>
# Line 12  However, in some cases you'll have to he Line 12  However, in some cases you'll have to he
12  </para><para>  </para><para>
13    
14  If this is the first time you're booting the system, try the default  If this is the first time you're booting the system, try the default
15  boot parameters (i.e., don't try setting arguments) and see if it works  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  correctly. It probably will.  If not, you can reboot later and look for
17  any special parameters that inform the system about your hardware.  any special parameters that inform the system about your hardware.
18    
19  </para><para>  </para><para>
20    
21  Full information on boot parameters can be found in the <ulink  Information on many boot parameters can be found in the
22  url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html"> Linux  <ulink url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html"> Linux
23  BootPrompt HOWTO</ulink>, including tips for obscure hardware.  This  BootPrompt HOWTO</ulink>, including tips for obscure hardware.  This
24  section contains only a sketch of the most salient parameters.  Some  section contains only a sketch of the most salient parameters.  Some
25  common gotchas are included below in  common gotchas are included below in
26  <xref linkend="boot-troubleshooting"/>.  <xref linkend="boot-troubleshooting"/>.
27    
28  </para><para>  </para><para>
29    
30  When the kernel boots, a message  When the kernel boots, a message
31    
32  <informalexample><screen>  <informalexample><screen>
33    Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available
 Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available  
   
34  </screen></informalexample>  </screen></informalexample>
35    
36  should be emitted early in the process.  should be emitted early in the process.
# Line 41  in kilobytes.  If this doesn't match the Line 39  in kilobytes.  If this doesn't match the
39  installed, you need to use the  installed, you need to use the
40  <userinput>mem=<replaceable>ram</replaceable></userinput> parameter,  <userinput>mem=<replaceable>ram</replaceable></userinput> parameter,
41  where <replaceable>ram</replaceable> is set to the amount of memory,  where <replaceable>ram</replaceable> is set to the amount of memory,
42  suffixed with ``k'' for kilobytes, or ``m'' for megabytes.  For  suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for
43  example, both <userinput>mem=65536k</userinput> and  megabytes.  For example, both <userinput>mem=65536k</userinput> and
44  <userinput>mem=64m</userinput> mean 64MB of RAM.  <userinput>mem=64m</userinput> mean 64MB of RAM.
45    
 </para><para>  
   
 If your monitor is only capable of black-and-white, use the  
 <userinput>mono</userinput> boot argument.  Otherwise, your  
 installation will use color, which is the default.  
   
46  </para><para condition="supports-serial-console">  </para><para condition="supports-serial-console">
47    
48  If you are booting with a serial console, generally the kernel will  If you are booting with a serial console, generally the kernel will
49  autodetect this  autodetect
50  <phrase arch="mipsel">(although not on DECstations)</phrase>  this<phrase arch="mipsel"> (although not on DECstations)</phrase>.
51  If you have a videocard (framebuffer) and a keyboard also attached to  If you have a videocard (framebuffer) and a keyboard also attached to
52  the computer which you wish to boot via serial console, you may have  the computer which you wish to boot via serial console, you may have
53  to pass the  to pass the
54  <userinput>console=<replaceable>device</replaceable></userinput>  <userinput>console=<replaceable>device</replaceable></userinput>
55  argument to the kernel, where <replaceable>device</replaceable> is  argument to the kernel, where <replaceable>device</replaceable> is
56  your serial device, which is usually something like ``ttyS0''.  your serial device, which is usually something like
57    <filename>ttyS0</filename>.
58    
59  </para><para arch="sparc">  </para><para arch="sparc">
60    
61  for &arch-title; the serial devices are ``ttya'' or ``ttyb''.  For &arch-title; the serial devices are <filename>ttya</filename> or
62  Alternatively, set the <replaceable>input-device</replaceable> and  <filename>ttyb</filename>.
63  <replaceable>output-device</replaceable> OpenPROM variables to  Alternatively, set the <envar>input-device</envar> and
64  ``ttya''.  <envar>output-device</envar> OpenPROM variables to
65    <filename>ttya</filename>.
66    
67  </para>  </para>
68    
69    
70    <sect2 id="installer-args"><title>Debian Installer Arguments</title>    <sect2 id="installer-args"><title>Debian Installer Parameters</title>
71    <para>
72    
73    The installation system recognizes a few additional boot parameters<footnote>
74    
75  <para>  <para>
76    
77  The installation system recognizes a few boot arguments which may be  Note that the kernel accepts a maximum of 8 command line options and
78  useful.  8 environment options (including any options added by default for the
79    installer). If these numbers are exceeded, 2.4 kernels will drop any
80    excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer,
81    you can use 32 command line options and 32 environment options.
82    
83    </para>
84    
85    </footnote> which may be useful.
86    
87  </para>  </para>
88    
89  <variablelist>  <variablelist>
90  <varlistentry>  <varlistentry>
91  <term>DEBCONF_PRIORITY=CRITICAL</term>  <term>debconf/priority</term>
92  <listitem><para>  <listitem><para>
93    
94  This will cause the installation system to  This parameter sets the lowest priority of messages to be displayed.
95  display only critical messages and try to do the right thing without  
96  fuss.  If problems are encountered, the installer adjusts the priority  </para><para>
97  as needed.  
98    The default installation uses <userinput>debconf/priority=high</userinput>.
99    This means that both high and critical priority messages are shown, but medium
100    and low priority messages are skipped.
101    If problems are encountered, the installer adjusts the priority as needed.
102    
103    </para><para>
104    
105    If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you
106    will be shown the installation menu and gain more control over the installation.
107    When <userinput>debconf/priority=low</userinput> is used, all messages are shown
108    (this is equivalent to the <emphasis>expert</emphasis> boot method).
109    With <userinput>debconf/priority=critical</userinput>, the installation system
110    will display only critical messages and try to do the right thing without fuss.
111    
112  </para></listitem>  </para></listitem>
113  </varlistentry>  </varlistentry>
114    
115    
116  <varlistentry>  <varlistentry>
117  <term>DEBCONF_PRIORITY=HIGH</term>  <term>DEBIAN_FRONTEND</term>
118  <term>DEBCONF_PRIORITY=MEDIUM</term>  <listitem><para>
119  <term>DEBCONF_PRIORITY=LOW</term>  
120    This boot parameter controls the type of user interface used for the
121    installer. The current possible parameter settings are:
122    
123    <itemizedlist>
124    <listitem>
125    <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para>
126    </listitem><listitem>
127    <para><userinput>DEBIAN_FRONTEND=text</userinput></para>
128    </listitem><listitem>
129    <para><userinput>DEBIAN_FRONTEND=newt</userinput></para>
130    </listitem><listitem>
131    <para><userinput>DEBIAN_FRONTEND=slang</userinput></para>
132    </listitem><listitem>
133    <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para>
134    </listitem><listitem>
135    <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para>
136    </listitem><listitem>
137    <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para>
138    </listitem><listitem>
139    <para><userinput>DEBIAN_FRONTEND=corba</userinput></para>
140    </listitem>
141    </itemizedlist>
142    
143    The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>.
144    <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for
145    serial console installs. Generally only the
146    <userinput>newt</userinput> frontend is available on default install
147    media, so this is not very useful right now.
148    
149    </para></listitem>
150    </varlistentry>
151    
152    
153    <varlistentry>
154    <term>BOOT_DEBUG</term>
155  <listitem><para>  <listitem><para>
156    
157  These parameter settings will similarly set the highest priority of  Setting this boot parameter to 2 will cause the installer's boot process
158  messages to be displayed. For example, with the priority set to HIGH,  to be verbosely logged. Setting it to 3 makes debug shells
159  both high and critical priority messages are shown, but medium and  available at strategic points in the boot process. (Exit the shells to
160  low priority messages are skipped.  continue the boot process.)
161    
162    <variablelist>
163    <varlistentry>
164    <term><userinput>BOOT_DEBUG=0</userinput></term>
165    <listitem><para>This is the default.</para></listitem>
166    </varlistentry>
167    
168    <varlistentry>
169    <term><userinput>BOOT_DEBUG=1</userinput></term>
170    <listitem><para>More verbose than usual.</para></listitem>
171    </varlistentry>
172    
173    <varlistentry>
174    <term><userinput>BOOT_DEBUG=2</userinput></term>
175    <listitem><para>Lots of debugging information.</para></listitem>
176    </varlistentry>
177    
178    <varlistentry>
179    <term><userinput>BOOT_DEBUG=3</userinput></term>
180    <listitem><para>
181    
182    Shells are run at various points in the boot process to allow detailed
183    debugging. Exit the shell to continue the boot.
184    
185  </para></listitem>  </para></listitem>
186  </varlistentry>  </varlistentry>
187    </variablelist>
188    
189    </para></listitem>
190    </varlistentry>
191    
192    
193  <varlistentry>  <varlistentry>
194  <term>debug</term>  <term>INSTALL_MEDIA_DEV</term>
195  <listitem><para>  <listitem><para>
196    
197  Emit additional debug messages to the installation system log (see  The value of the parameter is the path to the device to load the
198  <xref linkend="dbootstrap-shell-log"/>), including every command run.  Debian installer from. For example,
199    <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>
200    
201    </para><para>
202    
203    The boot floppy, which normally scans all floppies and USB storage
204    devices it can to find the root floppy, can be overridden by this
205    parameter to only look at the one device.
206    
207  </para></listitem>  </para></listitem>
208  </varlistentry>  </varlistentry>
209    
210  <varlistentry>  <varlistentry>
211  <term>nofb</term>  <term>debian-installer/framebuffer</term>
212  <listitem><para>  <listitem><para>
213    
214  Some architectures use the kernel framebuffer to offer installation in  Some architectures use the kernel framebuffer to offer installation in
215  a number of languages. If framebuffer causes a problem on your system  a number of languages. If framebuffer causes a problem on your system
216  you can use this option to disable the feature. Problem symptoms are  you can disable the feature by the parameter
217  error messages about bterm or bogl, a blank screen, or a freeze within  <userinput>debian-installer/framebuffer=false</userinput>. Problem
218  a few minutes after starting the install.  symptoms are error messages about bterm or bogl, a blank screen, or
219    a freeze within a few minutes after starting the install.
220    
221  </para><para arch="i386">  </para><para arch="i386">
222    
223  The <userinput>video=vga16:off</userinput> argument may also be used  The <userinput>video=vga16:off</userinput> argument may also be used
224  to disable  to disable the framebuffer. Such problems have been reported on a Dell
225  the framebuffer. Such problems have been reported on a Dell Inspiron with  Inspiron with Mobile Radeon card.
 Mobile Radeon card.  
226    
227  </para><para arch="m68k">  </para><para arch="m68k">
228    
# Line 144  Such problems have been reported on the Line 232  Such problems have been reported on the
232    
233  Such problems have been reported on hppa.  Such problems have been reported on hppa.
234    
235    </para><note arch="sparc"><para>
236    
237    Because of display problems on some systems, framebuffer support is
238    <emphasis>disabled by default</emphasis> for &arch-title;. This can result
239    in ugly display on systems that do properly support the framebuffer, like
240    those with ATI graphical cards.
241    If you see display problems in the installer, you can try booting with
242    parameter <userinput>debian-installer/framebuffer=true</userinput>.
243    
244    </para></note></listitem>
245    </varlistentry>
246    
247    <varlistentry>
248    <term>debian-installer/probe/usb</term>
249    <listitem><para>
250    
251    Set to <userinput>false</userinput> to prevent probing for USB on
252    boot, if that causes problems.
253    
254    </para></listitem>
255    </varlistentry>
256    
257    <varlistentry>
258    <term>netcfg/disable_dhcp</term>
259    <listitem><para>
260    
261    By default, the &d-i; automatically probes for network configuration
262    via DHCP. If the probe succeeds, you won't have a chance to review and
263    change the obtained settings. You can get to the manual network setup
264    only in case the DHCP probe fails.
265    
266    </para><para>
267    
268    If you have a DHCP server on your local network, but want to avoid it
269    because e.g. it gives wrong answers, you can use the parameter
270    <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring
271    the network with DHCP and to enter the information manually.
272    
273    </para></listitem>
274    </varlistentry>
275    
276    <varlistentry>
277    <term>hw-detect/start_pcmcia</term>
278    <listitem><para>
279    
280    Set to <userinput>false</userinput> to prevent starting PCMCIA
281    services, if that causes problems. Some laptops are well known for
282    this misbehavior.
283    
284    </para></listitem>
285    </varlistentry>
286    
287    <varlistentry>
288    <term>preseed/url</term>
289    <listitem><para>
290    
291    Specify the url to a preconfiguration file to download and use in
292    automating the install. See <xref linkend="automatic-install"/>.
293    
294    </para></listitem>
295    </varlistentry>
296    
297    <varlistentry>
298    <term>preseed/file</term>
299    <listitem><para>
300    
301    Specify the path to a preconfiguration file to load to
302    automating the install. See <xref linkend="automatic-install"/>.
303    
304    </para></listitem>
305    </varlistentry>
306    
307    <varlistentry>
308    <term>cdrom-detect/eject</term>
309    <listitem><para>
310    
311    By default, before rebooting, &d-i; automatically ejects the optical
312    media used during the installation. This can be unnecessary if the system
313    does not automatically boot off the CD. In some cases it may even be
314    undesirable, for example if the optical drive cannot reinsert the media
315    itself and the user is not there to do it manually. Many slot loading,
316    slim-line, and caddy style drives cannot reload media automatically.
317    
318    </para><para>
319    
320    Set to <userinput>false</userinput> to disable automatic ejection, and
321    be aware that you may need to ensure that the system does not
322    automatically boot from the optical drive after the initial
323    installation.
324    
325    </para></listitem>
326    </varlistentry>
327    
328    <varlistentry>
329    <term>ramdisk_size</term>
330    <listitem><para>
331    
332    If you are using a 2.2.x kernel, you may need to set &ramdisksize;.
333    
334    </para></listitem>
335    </varlistentry>
336    
337    <varlistentry>
338    <term>rescue/enable</term>
339    <listitem><para>
340    
341    Set to <userinput>true</userinput> to enter rescue mode rather than
342    performing a normal installation. See <xref linkend="rescue"/>.
343    
344  </para></listitem>  </para></listitem>
345  </varlistentry>  </varlistentry>
346    
Legend:
Removed from v.5338  
changed lines
  Added in v.33725
  ViewVC Help
Powered by ViewVC 1.1.5