[SILENT_COMMIT] Update of POT and PO files for the manual

1 files changed, 115 insertions, 91 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index 959f9103e..c6571372d 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"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2008-03-07 01:09+0000\n"
+"POT-Creation-Date: 2008-04-20 00:10+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"
@@ -2035,7 +2035,7 @@ msgid "A theme determines how the user interface of the installer looks (colors,
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3029 boot-installer.xml:3232
+#: boot-installer.xml:3029 boot-installer.xml:3267
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
@@ -2169,125 +2169,149 @@ msgstr ""
 #. Tag: term
 #: boot-installer.xml:3160
 #, no-c-format
-msgid "mouse/left"
+msgid "mouse/protocol"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:3161
 #, no-c-format
+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."
+msgstr ""
+
+#. Tag: term
+#: boot-installer.xml:3183
+#, no-c-format
+msgid "mouse/device"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3184
+#, no-c-format
+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>."
+msgstr ""
+
+#. Tag: term
+#: boot-installer.xml:3195
+#, no-c-format
+msgid "mouse/left"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3196
+#, no-c-format
 msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3170
+#: boot-installer.xml:3205
 #, no-c-format
 msgid "directfb/hw-accel"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3171
+#: boot-installer.xml:3206
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3181
+#: boot-installer.xml:3216
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3182
+#: boot-installer.xml:3217
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3193
+#: boot-installer.xml:3228
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3194
+#: boot-installer.xml:3229
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3206
+#: boot-installer.xml:3241
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3207
+#: boot-installer.xml:3242
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3218
+#: boot-installer.xml:3253
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3219
+#: boot-installer.xml:3254
 #, no-c-format
 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>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3233
+#: boot-installer.xml:3268
 #, no-c-format
 msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3242
+#: boot-installer.xml:3277
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3243
+#: boot-installer.xml:3278
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3256
+#: boot-installer.xml:3291
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3257
+#: boot-installer.xml:3292
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3271
+#: boot-installer.xml:3306
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3272
+#: boot-installer.xml:3307
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3285
+#: boot-installer.xml:3320
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3292
+#: boot-installer.xml:3327
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -2296,133 +2320,133 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:3302
+#: boot-installer.xml:3337
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3308
+#: boot-installer.xml:3343
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3309
+#: boot-installer.xml:3344
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3318
+#: boot-installer.xml:3353
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3326
+#: boot-installer.xml:3361
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3343
+#: boot-installer.xml:3378
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3348
+#: boot-installer.xml:3383
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3349
+#: boot-installer.xml:3384
 #, no-c-format
 msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3356
+#: boot-installer.xml:3391
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3362
+#: boot-installer.xml:3397
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3367
+#: boot-installer.xml:3402
 #, no-c-format
 msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3373
+#: boot-installer.xml:3408
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3383
+#: boot-installer.xml:3418
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3389
+#: boot-installer.xml:3424
 #, no-c-format
 msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3397
+#: boot-installer.xml:3432
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3400
+#: boot-installer.xml:3435
 #, no-c-format
 msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3406
+#: boot-installer.xml:3441
 #, no-c-format
 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)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3413
+#: boot-installer.xml:3448
 #, no-c-format
 msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3424
+#: boot-installer.xml:3459
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3425
+#: boot-installer.xml:3460
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3430
+#: boot-installer.xml:3465
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3436
+#: boot-installer.xml:3471
 #, no-c-format
 msgid ""
       "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"
@@ -2432,7 +2456,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:3449
+#: boot-installer.xml:3484
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -2445,19 +2469,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3454
+#: boot-installer.xml:3489
 #, no-c-format
 msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3466
+#: boot-installer.xml:3501
 #, no-c-format
 msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3473
+#: boot-installer.xml:3508
 #, no-c-format
 msgid ""
       "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
@@ -2470,13 +2494,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3487
+#: boot-installer.xml:3522
 #, no-c-format
 msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3495
+#: boot-installer.xml:3530
 #, no-c-format
 msgid ""
       "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
@@ -2485,7 +2509,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3505
+#: boot-installer.xml:3540
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2498,157 +2522,157 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3520
+#: boot-installer.xml:3555
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3535
+#: boot-installer.xml:3570
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3537
+#: boot-installer.xml:3572
 #, no-c-format
 msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3542
+#: boot-installer.xml:3577
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3551
+#: boot-installer.xml:3586
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3560
+#: boot-installer.xml:3595
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3566
+#: boot-installer.xml:3601
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3572
+#: boot-installer.xml:3607
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: boot-installer.xml:3581
+#: boot-installer.xml:3616
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3583
+#: boot-installer.xml:3618
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3590
+#: boot-installer.xml:3625
 #, no-c-format
 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>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3596
+#: boot-installer.xml:3631
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: boot-installer.xml:3607 boot-installer.xml:3691
+#: boot-installer.xml:3642 boot-installer.xml:3726
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3608
+#: boot-installer.xml:3643
 #, no-c-format
 msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3613
+#: boot-installer.xml:3648
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3619
+#: boot-installer.xml:3654
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3628
+#: boot-installer.xml:3663
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3635
+#: boot-installer.xml:3670
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3649
+#: boot-installer.xml:3684
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3650
+#: boot-installer.xml:3685
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3660
+#: boot-installer.xml:3695
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: boot-installer.xml:3677
+#: boot-installer.xml:3712
 #, no-c-format
 msgid "System Freeze while Loading USB Modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3678
+#: boot-installer.xml:3713
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3692
+#: boot-installer.xml:3727
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3698
+#: boot-installer.xml:3733
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3699
+#: boot-installer.xml:3734
 #, no-c-format
 msgid ""
       "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"
@@ -2658,85 +2682,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3713
+#: boot-installer.xml:3748
 #, no-c-format
 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>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3724
+#: boot-installer.xml:3759
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3725
+#: boot-installer.xml:3760
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3731
+#: boot-installer.xml:3766
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3740
+#: boot-installer.xml:3775
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3742
+#: boot-installer.xml:3777
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: boot-installer.xml:3767
+#: boot-installer.xml:3802
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3768
+#: boot-installer.xml:3803
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3779
+#: boot-installer.xml:3814
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: boot-installer.xml:3790
+#: boot-installer.xml:3825
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3791
+#: boot-installer.xml:3826
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: boot-installer.xml:3798
+#: boot-installer.xml:3833
 #, no-c-format
 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3804
+#: boot-installer.xml:3839
 #, no-c-format
 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>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3814
+#: boot-installer.xml:3849
 #, no-c-format
 msgid ""
       "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"