1763
#: boot-installer.xml:2580
1751
#: boot-installer.xml:2576
1765
1753
msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
1769
#: boot-installer.xml:2586
1757
#: boot-installer.xml:2582
1771
1759
msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
1763
#: boot-installer.xml:2615
1765
msgid "Currently, PReP and New World PowerMac systems support netbooting."
1775
1769
#: boot-installer.xml:2619
1777
msgid "Currently, PReP and New World PowerMac systems support netbooting."
1781
#: boot-installer.xml:2623
1783
msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <command>boot enet:0</command>. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <userinput>boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>. On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options."
1787
#: boot-installer.xml:2641
1772
"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n"
1773
"0 > boot enet:0\n"
1774
"</screen></informalexample> If this doesn't work, you might have to add the filename like this: <informalexample><screen>\n"
1775
"0 > boot enet:0,yaboot\n"
1776
"</screen></informalexample> PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <informalexample><screen>\n"
1777
"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable>\n"
1778
"</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options."
1782
#: boot-installer.xml:2647
1789
1784
msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
1793
#: boot-installer.xml:2653
1788
#: boot-installer.xml:2659
1795
1790
msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
1799
#: boot-installer.xml:2659
1794
#: boot-installer.xml:2665
1801
1796
msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
1805
#: boot-installer.xml:2666
1800
#: boot-installer.xml:2672
1807
1802
msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
1811
#: boot-installer.xml:2677
1806
#: boot-installer.xml:2683
1813
1808
msgid "PowerPC Boot Parameters"
1817
#: boot-installer.xml:2678
1812
#: boot-installer.xml:2684
1819
1814
msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
1823
#: boot-installer.xml:2718
1818
#: boot-installer.xml:2724
1825
1820
msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server."
1829
#: boot-installer.xml:2772
1824
#: boot-installer.xml:2778
1831
1826
msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
1835
#: boot-installer.xml:2781
1830
#: boot-installer.xml:2787
1837
1832
msgid "IDPROM Messages"
1841
#: boot-installer.xml:2782
1836
#: boot-installer.xml:2788
1843
1838
msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
1847
#: boot-installer.xml:2801
1842
#: boot-installer.xml:2807
1849
1844
msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
1853
#: boot-installer.xml:2808
1848
#: boot-installer.xml:2814
1855
1850
msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
1859
#: boot-installer.xml:2815
1854
#: boot-installer.xml:2821
1861
1856
msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
1865
#: boot-installer.xml:2824
1860
#: boot-installer.xml:2830
1868
1863
"When the kernel boots, a message <informalexample><screen>\n"
1874
#: boot-installer.xml:2840
1869
#: boot-installer.xml:2846
1876
msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
1871
msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
1880
#: boot-installer.xml:2853
1875
#: boot-installer.xml:2858
1882
1877
msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
1886
#: boot-installer.xml:2864
1881
#: boot-installer.xml:2869
1888
1883
msgid "Debian Installer Parameters"
1892
#: boot-installer.xml:2865
1887
#: boot-installer.xml:2870
1894
1889
msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
1898
#: boot-installer.xml:2878
1893
#: boot-installer.xml:2883
1900
1895
msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
1904
#: boot-installer.xml:2890
1899
#: boot-installer.xml:2895
1906
1901
msgid "debconf/priority (priority)"
1910
#: boot-installer.xml:2891
1905
#: boot-installer.xml:2896
1912
1907
msgid "This parameter sets the lowest priority of messages to be displayed."
1916
#: boot-installer.xml:2895
1911
#: boot-installer.xml:2900
1918
1913
msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
1922
#: boot-installer.xml:2902
1917
#: boot-installer.xml:2907
1924
1919
msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
1928
#: boot-installer.xml:2916
1923
#: boot-installer.xml:2921
1930
1925
msgid "DEBIAN_FRONTEND"
1934
#: boot-installer.xml:2917
1929
#: boot-installer.xml:2922
1936
1931
msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
1940
#: boot-installer.xml:2946
1935
#: boot-installer.xml:2951
1942
1937
msgid "BOOT_DEBUG"
1946
#: boot-installer.xml:2947
1941
#: boot-installer.xml:2952
1948
1943
msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
1951
1946
#. Tag: userinput
1952
#: boot-installer.xml:2956
1947
#: boot-installer.xml:2961
1954
1949
msgid "BOOT_DEBUG=0"
1958
#: boot-installer.xml:2957
1953
#: boot-installer.xml:2962
1960
1955
msgid "This is the default."
1963
1958
#. Tag: userinput
1964
#: boot-installer.xml:2961
1959
#: boot-installer.xml:2966
1966
1961
msgid "BOOT_DEBUG=1"
1970
#: boot-installer.xml:2962
1965
#: boot-installer.xml:2967
1972
1967
msgid "More verbose than usual."
1975
1970
#. Tag: userinput
1976
#: boot-installer.xml:2966
1971
#: boot-installer.xml:2971
1978
1973
msgid "BOOT_DEBUG=2"
1982
#: boot-installer.xml:2967
1977
#: boot-installer.xml:2972
1984
1979
msgid "Lots of debugging information."
1987
1982
#. Tag: userinput
1988
#: boot-installer.xml:2971
1983
#: boot-installer.xml:2976
1990
1985
msgid "BOOT_DEBUG=3"
1994
#: boot-installer.xml:2972
1989
#: boot-installer.xml:2977
1996
1991
msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
2000
#: boot-installer.xml:2986
1995
#: boot-installer.xml:2991
2002
1997
msgid "INSTALL_MEDIA_DEV"
2006
#: boot-installer.xml:2987
2001
#: boot-installer.xml:2992
2008
2003
msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
2012
#: boot-installer.xml:2993
2007
#: boot-installer.xml:2998
2014
2009
msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
2018
#: boot-installer.xml:3003
2013
#: boot-installer.xml:3008
2024
#: boot-installer.xml:3004
2019
#: boot-installer.xml:3009
2026
2021
msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
2030
#: boot-installer.xml:3014
2025
#: boot-installer.xml:3019
2032
2027
msgid "debian-installer/framebuffer (fb)"
2036
#: boot-installer.xml:3015
2031
#: boot-installer.xml:3020
2038
2033
msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
2042
#: boot-installer.xml:3024
2037
#: boot-installer.xml:3029
2044
2039
msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card."
2048
#: boot-installer.xml:3030
2043
#: boot-installer.xml:3035
2050
2045
msgid "Such problems have been reported on the Amiga 1200 and SE/30."
2054
#: boot-installer.xml:3034
2049
#: boot-installer.xml:3039
2056
2051
msgid "Such problems have been reported on hppa."
2060
#: boot-installer.xml:3038
2055
#: boot-installer.xml:3043
2062
2057
msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
2066
#: boot-installer.xml:3052
2061
#: boot-installer.xml:3057
2068
2063
msgid "debian-installer/theme (theme)"
2072
#: boot-installer.xml:3053
2067
#: boot-installer.xml:3058
2074
2069
msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
2078
#: boot-installer.xml:3065 boot-installer.xml:3315
2073
#: boot-installer.xml:3070 boot-installer.xml:3320
2080
2075
msgid "netcfg/disable_dhcp"
2084
#: boot-installer.xml:3066
2079
#: boot-installer.xml:3071
2086
2081
msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
2090
#: boot-installer.xml:3073
2085
#: boot-installer.xml:3078
2092
2087
msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
2096
#: boot-installer.xml:3084
2091
#: boot-installer.xml:3089
2098
2093
msgid "hw-detect/start_pcmcia"
2102
#: boot-installer.xml:3085
2097
#: boot-installer.xml:3090
2104
2099
msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
2108
#: boot-installer.xml:3095
2103
#: boot-installer.xml:3100
2110
2105
msgid "disk-detect/dmraid/enable (dmraid)"
2114
#: boot-installer.xml:3096
2109
#: boot-installer.xml:3101
2116
2111
msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">Debian Installer Wiki</ulink>."
2120
#: boot-installer.xml:3107
2115
#: boot-installer.xml:3112
2122
2117
msgid "preseed/url (url)"
2126
#: boot-installer.xml:3108
2121
#: boot-installer.xml:3113
2128
2123
msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
2132
#: boot-installer.xml:3117
2127
#: boot-installer.xml:3122
2134
2129
msgid "preseed/file (file)"
2138
#: boot-installer.xml:3118
2133
#: boot-installer.xml:3123
2140
2135
msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
2144
#: boot-installer.xml:3127
2139
#: boot-installer.xml:3132
2146
2141
msgid "preseed/interactive"
2150
#: boot-installer.xml:3128
2145
#: boot-installer.xml:3133
2152
2147
msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
2156
#: boot-installer.xml:3140
2151
#: boot-installer.xml:3145
2158
2153
msgid "auto-install/enable (auto)"
2162
#: boot-installer.xml:3141
2157
#: boot-installer.xml:3146
2164
2159
msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
2168
#: boot-installer.xml:3152
2163
#: boot-installer.xml:3157
2170
2165
msgid "finish-install/keep-consoles"
2174
#: boot-installer.xml:3153
2169
#: boot-installer.xml:3158
2176
2171
msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
2180
#: boot-installer.xml:3164
2175
#: boot-installer.xml:3169
2182
2177
msgid "cdrom-detect/eject"
2186
#: boot-installer.xml:3165
2181
#: boot-installer.xml:3170
2188
2183
msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
2192
#: boot-installer.xml:3174
2187
#: boot-installer.xml:3179
2194
2189
msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
2198
#: boot-installer.xml:3185
2193
#: boot-installer.xml:3190
2200
2195
msgid "debian-installer/allow_unauthenticated"
2204
#: boot-installer.xml:3186
2199
#: boot-installer.xml:3191
2206
2201
msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
2210
#: boot-installer.xml:3197
2205
#: boot-installer.xml:3202
2212
2207
msgid "ramdisk_size"
2216
#: boot-installer.xml:3198
2211
#: boot-installer.xml:3203
2218
2213
msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
2222
#: boot-installer.xml:3208
2217
#: boot-installer.xml:3213
2224
2219
msgid "mouse/protocol"
2228
#: boot-installer.xml:3209
2223
#: boot-installer.xml:3214
2230
2225
msgid "For the gtk frontend (graphical installer), users can set the mouse protocol to be used by setting this parameter. Supported values are<footnote> <para> See the man page for <citerefentry><refentrytitle>directfbrc</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for additional information. </para> </footnote>: <userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, <userinput>MS</userinput>, <userinput>MS3</userinput>, <userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>. In most cases the default protocol should work correctly."
2234
#: boot-installer.xml:3231
2229
#: boot-installer.xml:3236
2236
2231
msgid "mouse/device"
2240
#: boot-installer.xml:3232
2235
#: boot-installer.xml:3237
2242
2237
msgid "For the gtk frontend (graphical installer), users can specify the mouse device to be used by setting this parameter. This is mostly useful if the mouse is connected to a serial port (serial mouse). Example: <userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>."
2246
#: boot-installer.xml:3243
2241
#: boot-installer.xml:3248
2248
2243
msgid "mouse/left"
2252
#: boot-installer.xml:3244
2247
#: boot-installer.xml:3249
2254
2249
msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>."
2258
#: boot-installer.xml:3253
2253
#: boot-installer.xml:3258
2260
2255
msgid "directfb/hw-accel"
2264
#: boot-installer.xml:3254
2259
#: boot-installer.xml:3259
2266
2261
msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. Set this parameter to <userinput>true</userinput> to enable it."
2270
#: boot-installer.xml:3264
2265
#: boot-installer.xml:3269
2272
2267
msgid "rescue/enable"
2276
#: boot-installer.xml:3265
2271
#: boot-installer.xml:3270
2278
2273
msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
2282
#: boot-installer.xml:3276
2277
#: boot-installer.xml:3281
2284
2279
msgid "Using boot parameters to answer questions"
2288
#: boot-installer.xml:3277
2283
#: boot-installer.xml:3282
2290
2285
msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
2294
#: boot-installer.xml:3289
2289
#: boot-installer.xml:3294
2296
2291
msgid "debian-installer/locale (locale)"
2300
#: boot-installer.xml:3290
2295
#: boot-installer.xml:3295
2302
2297
msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country."
2306
#: boot-installer.xml:3301
2301
#: boot-installer.xml:3306
2308
2303
msgid "anna/choose_modules (modules)"
2312
#: boot-installer.xml:3302
2307
#: boot-installer.xml:3307
2314
2309
msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
2318
#: boot-installer.xml:3316
2313
#: boot-installer.xml:3321
2320
2315
msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
2324
#: boot-installer.xml:3325
2319
#: boot-installer.xml:3330
2326
2321
msgid "mirror/protocol (protocol)"
2330
#: boot-installer.xml:3326
2325
#: boot-installer.xml:3331
2332
2327
msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
2336
#: boot-installer.xml:3339
2331
#: boot-installer.xml:3344
2338
2333
msgid "tasksel:tasksel/first (tasks)"
2342
#: boot-installer.xml:3340
2337
#: boot-installer.xml:3345
2344
2339
msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
2348
#: boot-installer.xml:3354
2343
#: boot-installer.xml:3359
2350
2345
msgid "Passing parameters to kernel modules"
2354
#: boot-installer.xml:3355
2349
#: boot-installer.xml:3360
2356
2351
msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
2360
#: boot-installer.xml:3368
2355
#: boot-installer.xml:3373
2362
2357
msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
2366
#: boot-installer.xml:3375
2361
#: boot-installer.xml:3380
2369
2364
"The syntax to use to set parameters for modules is: <informalexample><screen>\n"
2375
#: boot-installer.xml:3385
2370
#: boot-installer.xml:3390
2377
2372
msgid "3c509.xcvr=3 3c509.irq=10"
2381
#: boot-installer.xml:3391
2376
#: boot-installer.xml:3396
2383
2378
msgid "Blacklisting kernel modules"
2387
#: boot-installer.xml:3392
2382
#: boot-installer.xml:3397
2389
2384
msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
2393
#: boot-installer.xml:3401
2388
#: boot-installer.xml:3406
2395
2390
msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
2399
#: boot-installer.xml:3409
2394
#: boot-installer.xml:3414
2401
2396
msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
2405
#: boot-installer.xml:3426
2400
#: boot-installer.xml:3431
2407
2402
msgid "Troubleshooting the Installation Process"
2411
#: boot-installer.xml:3431
2406
#: boot-installer.xml:3436
2413
2408
msgid "CD-ROM Reliability"
2417
#: boot-installer.xml:3432
2412
#: boot-installer.xml:3437
2419
2414
msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation."
2423
#: boot-installer.xml:3439
2418
#: boot-installer.xml:3444
2425
msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
2420
msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
2429
#: boot-installer.xml:3445
2424
#: boot-installer.xml:3450
2431
2426
msgid "There are two very simple things that you should try first."
2435
#: boot-installer.xml:3450
2430
#: boot-installer.xml:3455
2437
2432
msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
2441
#: boot-installer.xml:3456
2436
#: boot-installer.xml:3461
2443
2438
msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way."
2447
#: boot-installer.xml:3466
2442
#: boot-installer.xml:3471
2449
2444
msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
2453
#: boot-installer.xml:3472
2448
#: boot-installer.xml:3477
2455
2450
msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
2459
#: boot-installer.xml:3480
2454
#: boot-installer.xml:3485
2461
2456
msgid "Common issues"
2465
#: boot-installer.xml:3483
2460
#: boot-installer.xml:3488
2467
2462
msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
2471
#: boot-installer.xml:3489
2466
#: boot-installer.xml:3494
2473
2468
msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)."
2477
#: boot-installer.xml:3496
2472
#: boot-installer.xml:3501
2479
2474
msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled."
2483
#: boot-installer.xml:3507
2478
#: boot-installer.xml:3512
2485
2480
msgid "How to investigate and maybe solve issues"
2489
#: boot-installer.xml:3508
2484
#: boot-installer.xml:3513
2491
2486
msgid "If the CD-ROM fails to boot, try the suggestions listed below."
2495
#: boot-installer.xml:3513
2490
#: boot-installer.xml:3518
2497
2492
msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using."
2501
#: boot-installer.xml:3519
2496
#: boot-installer.xml:3524
2504
2499
"If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
2577
#: boot-installer.xml:3603
2572
#: boot-installer.xml:3608
2579
2574
msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
2583
#: boot-installer.xml:3618
2578
#: boot-installer.xml:3623
2585
2580
msgid "Floppy Disk Reliability"
2589
#: boot-installer.xml:3620
2584
#: boot-installer.xml:3625
2591
2586
msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability."
2595
#: boot-installer.xml:3625
2590
#: boot-installer.xml:3630
2597
2592
msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
2601
#: boot-installer.xml:3634
2596
#: boot-installer.xml:3639
2603
2598
msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
2607
#: boot-installer.xml:3643
2602
#: boot-installer.xml:3648
2609
2604
msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
2613
#: boot-installer.xml:3649
2608
#: boot-installer.xml:3654
2615
2610
msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
2619
#: boot-installer.xml:3655
2614
#: boot-installer.xml:3660
2621
2616
msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
2625
#: boot-installer.xml:3664
2620
#: boot-installer.xml:3669
2627
2622
msgid "Boot Configuration"
2631
#: boot-installer.xml:3666
2626
#: boot-installer.xml:3671
2633
2628
msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
2637
#: boot-installer.xml:3673
2632
#: boot-installer.xml:3678
2639
2634
msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
2643
#: boot-installer.xml:3679
2638
#: boot-installer.xml:3684
2645
2640
msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>."
2649
#: boot-installer.xml:3690 boot-installer.xml:3774
2644
#: boot-installer.xml:3695 boot-installer.xml:3797
2651
2646
msgid "Common &arch-title; Installation Problems"
2655
#: boot-installer.xml:3691
2650
#: boot-installer.xml:3696
2657
2652
msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
2661
#: boot-installer.xml:3696
2656
#: boot-installer.xml:3701
2663
2658
msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>."
2667
#: boot-installer.xml:3702
2662
#: boot-installer.xml:3707
2669
2664
msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>."
2673
#: boot-installer.xml:3711
2668
#: boot-installer.xml:3716
2675
2670
msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test."
2679
#: boot-installer.xml:3718
2681
msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
2674
#: boot-installer.xml:3723
2676
msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resulutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>."
2680
#: boot-installer.xml:3741
2682
msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
2685
#: boot-installer.xml:3732
2686
#: boot-installer.xml:3755
2687
2688
msgid "System Freeze During the PCMCIA Configuration Phase"
2691
#: boot-installer.xml:3733
2692
#: boot-installer.xml:3756
2693
2694
msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
2697
#: boot-installer.xml:3743
2698
#: boot-installer.xml:3766
2699
2700
msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
2703
#: boot-installer.xml:3760
2704
#: boot-installer.xml:3783
2705
2706
msgid "System Freeze while Loading USB Modules"
2709
#: boot-installer.xml:3761
2710
#: boot-installer.xml:3784
2711
2712
msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>nousb</userinput> parameter at the boot prompt."
2715
#: boot-installer.xml:3775
2716
#: boot-installer.xml:3798
2717
2718
msgid "There are some common installation problems that are worth mentioning."
2721
#: boot-installer.xml:3781
2722
#: boot-installer.xml:3804
2723
2724
msgid "Misdirected video output"
2727
#: boot-installer.xml:3782
2728
#: boot-installer.xml:3805
2730
2731
"It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
2737
#: boot-installer.xml:3796
2738
#: boot-installer.xml:3819
2739
2740
msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
2743
#: boot-installer.xml:3807
2744
#: boot-installer.xml:3830
2745
2746
msgid "Failure to Boot or Install from CD-ROM"
2749
#: boot-installer.xml:3808
2750
#: boot-installer.xml:3831
2751
2752
msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
2755
#: boot-installer.xml:3814
2756
#: boot-installer.xml:3837
2757
2758
msgid "We recommend to install such systems by netbooting the installer."
2761
#: boot-installer.xml:3823
2762
#: boot-installer.xml:3846
2763
2764
msgid "Interpreting the Kernel Startup Messages"
2767
#: boot-installer.xml:3825
2768
#: boot-installer.xml:3848
2769
2770
msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)."
2773
#: boot-installer.xml:3850
2774
#: boot-installer.xml:3873
2775
2776
msgid "Reporting Installation Problems"
2779
#: boot-installer.xml:3851
2780
#: boot-installer.xml:3874
2781
2782
msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
2785
#: boot-installer.xml:3862
2786
#: boot-installer.xml:3885
2787
2788
msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
2791
#: boot-installer.xml:3873
2792
#: boot-installer.xml:3896
2793
2794
msgid "Submitting Installation Reports"
2797
#: boot-installer.xml:3874
2798
#: boot-installer.xml:3897
2799
2800
msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
2803
#: boot-installer.xml:3881
2804
#: boot-installer.xml:3904
2805
2806
msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
2809
#: boot-installer.xml:3887
2810
#: boot-installer.xml:3910
2811
2812
msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
2815
#: boot-installer.xml:3897
2816
#: boot-installer.xml:3920
2818
2819
"Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
added
removed
po/pot/boot-installer.pot
