diff options
Diffstat (limited to 'po/pot/boot-installer.pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 174 |
1 files changed, 87 insertions, 87 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 547679f53..5636e2d0c 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-04-28 19:33+0000\n" +"POT-Creation-Date: 2006-06-21 12:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -854,13 +854,13 @@ msgstr "" #: boot-installer.xml:1077 #, no-c-format #. Tag: para -msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux debconf/priority=medium</userinput>)." +msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux fb=false</userinput>)." msgstr "" #: boot-installer.xml:1086 #, no-c-format #. Tag: para -msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>debian-installer/framebuffer=false</userinput> to the boot prompt, as described in the help text." +msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>fb=false</userinput> to the boot prompt, as described in the help text." msgstr "" #: boot-installer.xml:1161 @@ -1203,7 +1203,7 @@ msgstr "" #: boot-installer.xml:1673 #, no-c-format #. Tag: para -msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." +msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #: boot-installer.xml:1682 @@ -1221,7 +1221,7 @@ msgstr "" #: boot-installer.xml:1690 #, no-c-format #. Tag: para -msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." +msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #: boot-installer.xml:1699 @@ -1840,7 +1840,7 @@ msgstr "" #: boot-installer.xml:2805 #, no-c-format #. Tag: para -msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." +msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." msgstr "" #: boot-installer.xml:2825 @@ -1852,442 +1852,442 @@ msgstr "" #: boot-installer.xml:2826 #, no-c-format #. Tag: para -msgid "This parameter sets the lowest priority of messages to be displayed." +msgid "This parameter sets the lowest priority of messages to be displayed. Short form: <userinput>priority</userinput>" msgstr "" -#: boot-installer.xml:2830 +#: boot-installer.xml:2831 #, no-c-format #. Tag: para -msgid "The default installation uses <userinput>debconf/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." +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." msgstr "" -#: boot-installer.xml:2837 +#: boot-installer.xml:2838 #, no-c-format #. Tag: para -msgid "If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>debconf/priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>debconf/priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." +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." msgstr "" -#: boot-installer.xml:2851 +#: boot-installer.xml:2852 #, no-c-format #. Tag: term msgid "DEBIAN_FRONTEND" msgstr "" -#: boot-installer.xml:2852 +#: boot-installer.xml:2853 #, no-c-format #. Tag: para 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=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end 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, so this is not very useful right now." msgstr "" -#: boot-installer.xml:2888 +#: boot-installer.xml:2889 #, no-c-format #. Tag: term msgid "BOOT_DEBUG" msgstr "" -#: boot-installer.xml:2889 +#: boot-installer.xml:2890 #, no-c-format #. Tag: para 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.)" msgstr "" -#: boot-installer.xml:2898 +#: boot-installer.xml:2899 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=0" msgstr "" -#: boot-installer.xml:2899 +#: boot-installer.xml:2900 #, no-c-format #. Tag: para msgid "This is the default." msgstr "" -#: boot-installer.xml:2903 +#: boot-installer.xml:2904 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=1" msgstr "" -#: boot-installer.xml:2904 +#: boot-installer.xml:2905 #, no-c-format #. Tag: para msgid "More verbose than usual." msgstr "" -#: boot-installer.xml:2908 +#: boot-installer.xml:2909 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=2" msgstr "" -#: boot-installer.xml:2909 +#: boot-installer.xml:2910 #, no-c-format #. Tag: para msgid "Lots of debugging information." msgstr "" -#: boot-installer.xml:2913 +#: boot-installer.xml:2914 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=3" msgstr "" -#: boot-installer.xml:2914 +#: boot-installer.xml:2915 #, no-c-format #. Tag: para msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" -#: boot-installer.xml:2928 +#: boot-installer.xml:2929 #, no-c-format #. Tag: term msgid "INSTALL_MEDIA_DEV" msgstr "" -#: boot-installer.xml:2929 +#: boot-installer.xml:2930 #, no-c-format #. Tag: para 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>" msgstr "" -#: boot-installer.xml:2935 +#: boot-installer.xml:2936 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:2945 +#: boot-installer.xml:2946 #, no-c-format #. Tag: term msgid "debian-installer/framebuffer" msgstr "" -#: boot-installer.xml:2946 +#: boot-installer.xml:2947 #, no-c-format #. Tag: para -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>debian-installer/framebuffer=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." +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>debian-installer/framebuffer=false</userinput>, or <userinput>fb=false</userinput> for short. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." msgstr "" -#: boot-installer.xml:2955 +#: boot-installer.xml:2957 #, no-c-format #. Tag: para -msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." +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." msgstr "" -#: boot-installer.xml:2961 +#: boot-installer.xml:2963 #, no-c-format #. Tag: para msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" -#: boot-installer.xml:2965 +#: boot-installer.xml:2967 #, no-c-format #. Tag: para msgid "Such problems have been reported on hppa." msgstr "" -#: boot-installer.xml:2969 +#: boot-installer.xml:2971 #, no-c-format #. Tag: para 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>." msgstr "" -#: boot-installer.xml:2982 +#: boot-installer.xml:2984 #, no-c-format #. Tag: term msgid "debian-installer/probe/usb" msgstr "" -#: boot-installer.xml:2983 +#: boot-installer.xml:2985 #, no-c-format #. Tag: para msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." msgstr "" -#: boot-installer.xml:2992 +#: boot-installer.xml:2994 #, no-c-format #. Tag: term msgid "netcfg/disable_dhcp" msgstr "" -#: boot-installer.xml:2993 +#: boot-installer.xml:2995 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3000 +#: boot-installer.xml:3002 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3011 +#: boot-installer.xml:3013 #, no-c-format #. Tag: term msgid "hw-detect/start_pcmcia" msgstr "" -#: boot-installer.xml:3012 +#: boot-installer.xml:3014 #, no-c-format #. Tag: para msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" -#: boot-installer.xml:3022 +#: boot-installer.xml:3024 #, no-c-format #. Tag: term msgid "preseed/url" msgstr "" -#: boot-installer.xml:3023 +#: boot-installer.xml:3025 #, no-c-format #. Tag: para -msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>." +msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>url</userinput>" msgstr "" -#: boot-installer.xml:3032 +#: boot-installer.xml:3035 #, no-c-format #. Tag: term msgid "preseed/file" msgstr "" -#: boot-installer.xml:3033 +#: boot-installer.xml:3036 #, no-c-format #. Tag: para -msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>." +msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>file</userinput>" msgstr "" -#: boot-installer.xml:3042 +#: boot-installer.xml:3046 #, no-c-format #. Tag: term msgid "cdrom-detect/eject" msgstr "" -#: boot-installer.xml:3043 +#: boot-installer.xml:3047 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3052 +#: boot-installer.xml:3056 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3063 +#: boot-installer.xml:3067 #, no-c-format #. Tag: term msgid "ramdisk_size" msgstr "" -#: boot-installer.xml:3064 +#: boot-installer.xml:3068 #, no-c-format #. Tag: para msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr "" -#: boot-installer.xml:3072 +#: boot-installer.xml:3076 #, no-c-format #. Tag: term msgid "rescue/enable" msgstr "" -#: boot-installer.xml:3073 +#: boot-installer.xml:3077 #, no-c-format #. Tag: para msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" -#: boot-installer.xml:3091 +#: boot-installer.xml:3095 #, no-c-format #. Tag: title msgid "Troubleshooting the Installation Process" msgstr "" -#: boot-installer.xml:3096 +#: boot-installer.xml:3100 #, no-c-format #. Tag: title msgid "Floppy Disk Reliability" msgstr "" -#: boot-installer.xml:3098 +#: boot-installer.xml:3102 #, no-c-format #. Tag: para msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" -#: boot-installer.xml:3103 +#: boot-installer.xml:3107 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3112 +#: boot-installer.xml:3116 #, no-c-format #. Tag: para msgid "If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a <emphasis>different</emphasis> floppy. 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." msgstr "" -#: boot-installer.xml:3122 +#: boot-installer.xml:3126 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3128 +#: boot-installer.xml:3132 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3137 +#: boot-installer.xml:3141 #, no-c-format #. Tag: title msgid "Boot Configuration" msgstr "" -#: boot-installer.xml:3139 +#: boot-installer.xml:3143 #, no-c-format #. Tag: para 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\"/>." msgstr "" -#: boot-installer.xml:3146 +#: boot-installer.xml:3150 #, no-c-format #. Tag: para msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." msgstr "" -#: boot-installer.xml:3153 +#: boot-installer.xml:3157 #, no-c-format #. Tag: para msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" -#: boot-installer.xml:3159 +#: boot-installer.xml:3163 #, no-c-format #. Tag: para 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>." msgstr "" -#: boot-installer.xml:3170 +#: boot-installer.xml:3174 #, no-c-format #. Tag: title msgid "Common &arch-title; Installation Problems" msgstr "" -#: boot-installer.xml:3171 +#: boot-installer.xml:3175 #, no-c-format #. Tag: para msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" -#: boot-installer.xml:3176 +#: boot-installer.xml:3180 #, no-c-format #. Tag: para 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>." msgstr "" -#: boot-installer.xml:3182 +#: boot-installer.xml:3186 #, no-c-format #. Tag: para 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>." msgstr "" -#: boot-installer.xml:3191 +#: boot-installer.xml:3195 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3198 +#: boot-installer.xml:3202 #, no-c-format #. Tag: para -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>debian-installer/framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." +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 the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" -#: boot-installer.xml:3213 +#: boot-installer.xml:3216 #, no-c-format #. Tag: title msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" -#: boot-installer.xml:3214 +#: boot-installer.xml:3217 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3224 +#: boot-installer.xml:3227 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3241 +#: boot-installer.xml:3244 #, no-c-format #. Tag: title msgid "System Freeze while Loading the USB Modules" msgstr "" -#: boot-installer.xml:3242 +#: boot-installer.xml:3245 #, no-c-format #. Tag: para 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>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" -#: boot-installer.xml:3256 +#: boot-installer.xml:3259 #, no-c-format #. Tag: title msgid "Interpreting the Kernel Startup Messages" msgstr "" -#: boot-installer.xml:3258 +#: boot-installer.xml:3261 #, no-c-format #. Tag: para 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\"/>)." msgstr "" -#: boot-installer.xml:3283 +#: boot-installer.xml:3286 #, no-c-format #. Tag: title msgid "Bug Reporter" msgstr "" -#: boot-installer.xml:3284 +#: boot-installer.xml:3287 #, no-c-format #. Tag: para msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in 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." msgstr "" -#: boot-installer.xml:3295 +#: boot-installer.xml:3298 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3306 +#: boot-installer.xml:3309 #, no-c-format #. Tag: title msgid "Submitting Installation Reports" msgstr "" -#: boot-installer.xml:3307 +#: boot-installer.xml:3310 #, no-c-format #. Tag: para 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." msgstr "" -#: boot-installer.xml:3314 +#: boot-installer.xml:3317 #, no-c-format #. Tag: para msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." msgstr "" -#: boot-installer.xml:3321 +#: boot-installer.xml:3324 #, no-c-format #. Tag: para msgid "" |