3 files changed, 127 insertions, 31 deletions
diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml
index caf304e2b..8d9e43cd6 100644
--- a/nl/boot-installer/parameters.xml
+++ b/nl/boot-installer/parameters.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 42367 untranslated -->
+<!-- original version: 42982 untranslated -->
 
  <sect1 id="boot-parms"><title>Boot Parameters</title>
 <para>
@@ -126,23 +126,16 @@ installer. The current possible parameter settings are:
 </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>.
+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, so this is not very useful right now.
+media. On architectures which support it, the graphical installer uses
+the <userinput>gtk</userinput> frontend.
 
 </para></listitem>
 </varlistentry>
@@ -304,7 +297,7 @@ this misbehavior.
 
 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>
+Short form: <userinput>url</userinput>.
 
 </para></listitem>
 </varlistentry>
@@ -315,7 +308,7 @@ Short form: <userinput>url</userinput>
 
 Specify the path to a preconfiguration file to load to
 automating the install. See <xref linkend="automatic-install"/>.
-Short form: <userinput>file</userinput>
+Short form: <userinput>file</userinput>.
 
 </para></listitem>
 </varlistentry>
@@ -362,7 +355,17 @@ If you are using a 2.2.x kernel, you may need to set &ramdisksize;.
 </para></listitem>
 </varlistentry>
 
-<varlistentry>
+<varlistentry condition="g-i">
+<term>mouse/left</term>
+<listitem><para>
+
+For the gtk frontend (graphical installer), users can switch the mouse to
+left-handed operation by setting this parameter to <userinput>true</userinput>.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry condition="g-i">
 <term>directfb/hw-accel</term>
 <listitem><para>
 
@@ -384,6 +387,97 @@ performing a normal installation. See <xref linkend="rescue"/>.
 </varlistentry>
 
 </variablelist>
+
+   <sect3 id="preseed-args">
+   <title>Using boot parameters to answer questions</title>
+<para>
+
+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.
+
+</para>
+
+<variablelist>
+
+<varlistentry>
+<term>debian-installer/locale</term>
+<listitem><para>
+
+Can be used to set both the language and country for the installation.
+This will only work if the locale is supported in Debian.
+Short form: <userinput>locale</userinput>.
+For example, use <userinput>locale=de_CH</userinput> to select German as
+language and Switserland as country.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>netcfg/disable_dhcp</term>
+<listitem><para>
+
+Set to <userinput>true</userinput> if you want to disable DHCP and instead
+force static network configuration.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>tasksel:tasksel/first</term>
+<listitem><para>
+
+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.
+Short form: <userinput>tasks</userinput>.
+
+</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+   </sect3>
+
+   <sect3 id="module-parms"><title>Passing parameters to kernel modules</title>
+<para>
+
+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.
+
+</para><para>
+
+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.
+
+</para><para>
+
+The syntax to use to set parameters for modules is:
+
+<informalexample><screen>
+<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>
+</screen></informalexample>
+
+If you need to pass multiple parameters to the same or different modules,
+just repeat this. For example, to set an old 3Com network interface card
+to use the BNC (coax) connector and IRQ 10, you would pass:
+
+<informalexample><screen>
+3c509.xcvr=3 3c509.irq=10
+</screen></informalexample>
+
+</para>
+   </sect3>
   </sect2>
  </sect1>
-
diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml
index d5cf3b1cc..312c6132b 100644
--- a/nl/boot-installer/trouble.xml
+++ b/nl/boot-installer/trouble.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 42461 untranslated -->
+<!-- original version: 42532 untranslated -->
 
  <sect1 id="boot-troubleshooting">
  <title>Troubleshooting the Installation Process</title>
@@ -35,8 +35,8 @@ it is not dirty.
 <listitem><para>
 
 If the installer fails to recognize a CD-ROM, try just running the option
-<guimenu> <guimenuitem>Detect and mount CD-ROM</guimenuitem></guimenu> a
-second time. Some DMA related isses with older CD-ROM drives are known to
+<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice>
+a second time. Some DMA related isses with older CD-ROM drives are known to
 be resolved in this way.
 
 </para></listitem>
@@ -231,32 +231,32 @@ 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
+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.
 
 </para><para>
 
-If you are having the installation stall at a particular floppy, the
-first thing you should write it to a <emphasis>different</emphasis>
-floppy. Simply reformatting the old
+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.
 
 </para><para>
 
-Normally you should not have 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.
-
-</para><para>
-
 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.
 
 </para><para>
 
+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.
+
+</para><para>
+
 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.
diff --git a/nl/boot-installer/x86.xml b/nl/boot-installer/x86.xml
index 3caa968b2..8472097bb 100644
--- a/nl/boot-installer/x86.xml
+++ b/nl/boot-installer/x86.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 41808 untranslated -->
+<!-- original version: 42929 untranslated -->
 
   <sect2 arch="x86"><title>Booting from a CD-ROM</title>
 
@@ -118,8 +118,10 @@ and place the needed files as described in <xref linkend="boot-drive-files"/>.
 If you intend to use the hard drive only for booting and then
 download everything over the network, you should download the
 <filename>netboot/debian-installer/i386/initrd.gz</filename> file and its
-corresponding kernel. This will allow you to repartition the hard disk
-from which you boot the installer, although you should do so with care.
+corresponding kernel
+<filename>netboot/debian-installer/i386/linux</filename>. This will allow you
+to repartition the hard disk from which you boot the installer, although you
+should do so with care.
 </para>
 
 <para>