move manual to top-level directory, split out of debian-installer package

15 files changed, 2348 insertions, 0 deletions

diff --git a/eu/boot-installer/alpha.xml b/eu/boot-installer/alpha.xml
new file mode 100644
index 000000000..0613ddda4
--- /dev/null
+++ b/eu/boot-installer/alpha.xml
@@ -0,0 +1,451 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+ <sect2 arch="alpha" id="alpha-firmware">
+ <title>Alpha Console Firmware</title>
+<para>
+
+Console firmware is stored in a flash ROM and started when an Alpha
+system is powered up or reset.  There are two different console
+specifications used on Alpha systems, and hence two classes of console
+firmware available:
+
+</para>
+
+<itemizedlist>
+<listitem><para>
+
+  <emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem
+  specification, which provides an operating environment for OpenVMS, Tru64
+  UNIX, and Linux operating systems.
+
+</para></listitem>
+<listitem><para>
+
+  <emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the
+  Advanced RISC Computing (ARC) specification, which provides an operating
+  environment for Windows NT.
+
+</para></listitem>
+</itemizedlist>
+
+<para>
+
+From the user's perspective, the most important difference between SRM
+and ARC is that the choice of console constrains the possible
+disk-partitioning scheme for the hard disk which you wish to boot off
+of.
+
+</para><para>
+
+ARC requires that you use an MS-DOS partition table (as created by
+<command>cfdisk</command>) for the boot disk.  Therefore MS-DOS partition
+tables are the ``native'' partition format when booting from ARC.  In
+fact, since AlphaBIOS contains a disk partitioning utility, you may
+prefer to partition your disks from the firmware menus before
+installing Linux.
+
+</para><para>
+
+Conversely, SRM is <emphasis>incompatible</emphasis> with MS-DOS partition tables.
+<footnote><para>Specifically, the bootsector format required by the Console
+Subsystem Specification conflicts with the placement of the DOS
+partition table.</para></footnote> Since Tru64 Unix uses the BSD disklabel format,
+this is the ``native'' partition format for SRM installations.
+
+</para><para>
+
+Because GNU/Linux is the only operating system on Alpha that can be
+booted from both console types, the choice will also depend on what
+other operating systems you wish to run on the same machine.  All
+other Unix-like operating systems (Tru64 Unix, FreeBSD, OpenBSD, and
+NetBSD) and OpenVMS can only boot from SRM, whereas Windows NT can
+only boot from ARC.
+
+</para><para>
+
+The following table summarizes available and supported system
+type/console combinations (see <xref linkend="alpha-cpus"/> for the
+system type names).  The word `ARC' below denotes any of the
+ARC-compliant consoles.
+
+</para><para>
+
+<informaltable><tgroup cols="2">
+<thead>
+<row>
+  <entry>System Type</entry>
+  <entry>Console Type Supported</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry>alcor</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>avanti</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>book1</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>cabriolet</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>dp264</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>eb164</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>eb64p</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>eb66</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>eb66p</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>jensen</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>lx164</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>miata</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>mikasa</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>mikasa-p</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>nautilus</entry>
+  <entry>ARC only (see motherboard manual)</entry>
+</row><row>
+  <entry>noname</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>noritake</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>noritake-p</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>pc164</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>rawhide</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>ruffian</entry>
+  <entry>ARC only</entry>
+</row><row>
+  <entry>sable</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>sable-g</entry>
+  <entry>SRM only</entry>
+</row><row>
+  <entry>sx164</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>takara</entry>
+  <entry>ARC or SRM</entry>
+</row><row>
+  <entry>xl</entry>
+  <entry>ARC only</entry>
+</row><row>
+  <entry>xlt</entry>
+  <entry>ARC or SRM</entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+</para><para>
+
+Generally, none of these consoles can boot Linux directly, so the
+assistance of an intermediary bootloader is required.  There are two
+mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>.
+
+</para><para>
+
+<command>MILO</command> is itself a console, which replaces ARC or SRM in
+memory.  <command>MILO</command> can be booted from both ARC and SRM and is
+the only way to bootstrap Linux from the ARC console.
+<command>MILO</command> is platform-specific (a different <command>MILO</command>
+is needed for each system type) and exist only for those systems, for
+which ARC support is shown in the table above.  See also the
+(unfortunately outdated) 
+<ulink url="&url-milo-howto;">MILO HOWTO</ulink>.
+
+</para><para>
+
+<command>aboot</command> is a small, platform-independent bootloader, which
+runs from SRM only.  See the (also unfortunately outdated) <ulink
+url="&url-srm-howto;">SRM HOWTO</ulink> for more information on
+<command>aboot</command>.
+
+</para><para>
+
+Thus, three scenarios are generally possible, depending on the
+system's console firmware and whether or not <command>MILO</command> is
+available:
+
+<informalexample><screen>
+
+SRM -> aboot
+SRM -> MILO
+ARC -> MILO
+
+</screen></informalexample>
+
+</para><para>
+
+The UP1000 motherboard (subarchitecture name `nautilus') from Alpha
+Processor, Inc. is different from all the others, in that it uses an
+API-specific bootloader that runs under AlphaBIOS firmware.
+
+</para><para>
+
+Because <command>MILO</command> is not available for any of the Alpha
+systems currently in production (as of February 2000), and because it
+is no longer necessary to buy an OpenVMS or Tru64 Unix license to have
+SRM firmware on your older Alpha, it is recommended that you use SRM and
+<command>aboot</command> on new installations of GNU/Linux, unless you wish
+to dual-boot with Windows NT.
+
+</para><para>
+
+The majority of AlphaServers and all current server and workstation
+products contain both SRM and AlphaBIOS in their firmware.  For
+"half-flash" machines such as the various evaluation boards, it is
+possible to switch from one version to another by reflashing the
+firmware.  Also, once SRM is installed, it is possible to run
+ARC/AlphaBIOS from a floppy disk (using the <command>arc</command>
+command).  For the
+reasons mentioned above, we recommend switching to SRM before
+installing &debian;.
+
+</para><para>
+
+As on other architectures, you should install the newest available
+revision of the firmware <footnote><para>Except on Jensen, where
+Linux is not supported on firmware versions newer than 1.7 - see
+<ulink url="&url-jensen-howto;"></ulink> for more
+information</para></footnote> before installing &debian;.  For
+Alpha, firmware updates can be obtained from 
+<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>.
+
+</para>
+ </sect2>
+
+
+  <sect2 arch="alpha"><title>Booting with TFTP</title>
+<para>
+
+In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput>
+prefix, and will be listed in the output of the <userinput>show dev</userinput> command,
+like this (edited slightly):
+
+<informalexample><screen>
+
+>>> show dev
+ewa0.0.0.9.0               EWA0              08-00-2B-86-98-65
+ewb0.0.0.11.0              EWB0              08-00-2B-86-98-54
+ewc0.0.0.2002.0            EWC0              00-06-2B-01-32-B0
+
+</screen></informalexample>
+
+You first need to set the boot protocol:
+<informalexample><screen>
+
+>>> set ewa0_protocol bootp
+
+</screen></informalexample>
+
+Then check the medium type is correct:
+
+<informalexample><screen>
+
+>>> set ewa0_mode <replaceable>mode</replaceable>
+
+</screen></informalexample>
+
+You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>.
+
+</para><para>
+
+Then, to boot from the first Ethernet interface, you would type:
+
+<informalexample><screen>
+
+>>> boot ewa0
+
+</screen></informalexample>
+
+</para><para>
+
+If you wish to use a serial console, you <emphasis>must</emphasis>
+pass the <userinput>console=</userinput> parameter to the kernel.
+This can be done using the <userinput>-flags</userinput> argument to
+the SRM <userinput>boot</userinput> command.  The serial ports are
+named the same as their corresponding files in
+<userinput>/dev</userinput>.  For example, to boot from
+<userinput>ewa0</userinput> and use a console on the first serial
+port, you would type: 
+
+<informalexample><screen>
+
+>>> boot ewa0 -flags console=ttyS0
+
+</screen></informalexample>
+
+</para>
+  </sect2>
+
+  <sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title>
+<para>
+
+Type
+
+<informalexample><screen>
+
+&gt;&gt;&gt; boot xxxx -flags 0
+
+</screen></informalexample>
+
+where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation.
+
+</para>
+  </sect2>
+
+  <sect2 arch="alpha">
+  <title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title>
+<para>
+
+To boot a CD-ROM from the ARC console, find your sub-architecture code
+name (see <xref linkend="alpha-cpus"/>), then enter
+<filename>\milo\linload.exe</filename> as the boot loader and
+<filename>\milo\<replaceable>subarch</replaceable></filename> (where
+<replaceable>subarch</replaceable> is the proper subarchitecture name)
+as the OS Path in the `OS Selection Setup' menu. Ruffians make an
+exception: You need to use <filename>\milo\ldmilo.exe</filename> as
+boot loader.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="alpha">
+  <title>Booting from Floppies with the SRM Console</title>
+<para>
+
+At the SRM prompt (<prompt>&gt;&gt;&gt;</prompt>), issue the following
+command:
+
+<informalexample><screen>
+
+&gt;&gt;&gt; boot dva0 -flags 0
+        
+</screen></informalexample>
+
+possibly replacing <filename>dva0</filename> with the actual device
+name.  Usually, <filename>dva0</filename> is the floppy; type
+
+<informalexample><screen>
+
+&gt;&gt;&gt; show dev
+        
+</screen></informalexample>
+
+to see the list of devices (e.g., if you want to boot from a CD).
+Note that if you are booting via MILO, <command>-flags</command> argument
+is ignored, so you can just type <command>boot dva0</command>.
+If everything works OK, you will eventually see the Linux kernel boot.
+
+</para><para>
+
+If you want to specify kernel parameters when booting via
+<command>aboot</command>, use the following command:
+<informalexample><screen>
+
+&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments"
+        
+</screen></informalexample>
+(typed on one line), substituting, if necessary, the actual SRM boot
+device name for <filename>dva0</filename>, the Linux boot device name for
+<filename>fd0</filename>, and the desired kernel parameters for
+<filename>arguments</filename>.
+
+</para><para>
+
+If you want to specify kernel parameters when booting via
+<command>MILO</command>, you will have to interrupt bootstrap once you get
+into MILO.  See <xref linkend="booting-from-milo"/>.
+</para>
+  </sect2>
+
+
+  <sect2 arch="alpha">
+  <title>Booting from Floppies with the ARC or AlphaBIOS Console</title>
+
+<para>
+
+In the OS Selection menu, set <command>linload.exe</command> as the boot
+loader, and <command>milo</command> as the OS Path.  Bootstrap using the
+newly created entry.
+
+</para>
+  </sect2>
+
+  <sect2 arch="alpha">
+  <title>Booting from Floppies with the APB Boot Loader (UP1000)</title>
+
+<para>
+
+To boot on this platform, run <command>\apb\apb.exe</command> from the
+`Utility/Run Maintenance Program' menu, and type
+      <informalexample><screen>
+
+boot debian_install
+      
+</screen></informalexample>
+ at the APB prompt.
+
+</para>
+  </sect2>
+
+ <sect2 arch="alpha" id="booting-from-milo"><title>Booting with MILO</title>
+<para>
+
+MILO contained on the bootstrap media is configured to proceed straight
+to Linux automatically.  Should you wish to intervene, all you need is to
+press space during MILO countdown.
+
+</para><para>
+
+If you want to specify all the bits explicitly (for example, to supply
+additional parameters), you can use a command like this:
+
+<informalexample><screen>
+
+MILO&gt; boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->
+        
+</screen></informalexample>
+
+</para><para>
+
+If you are booting from something other than a floppy, substitute
+<filename>fd0</filename> in the above example with the appropriate device name
+in Linux notation.  The <command>help</command> command would give you a brief
+MILO command reference.
+
+</para>
+ </sect2>
+
diff --git a/eu/boot-installer/arm.xml b/eu/boot-installer/arm.xml
new file mode 100644
index 000000000..fadc600e3
--- /dev/null
+++ b/eu/boot-installer/arm.xml
@@ -0,0 +1,109 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+  <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title>
+
+&boot-installer-intro-net.xml;
+
+  <sect3 arch="arm"><title>Booting from TFTP on NetWinder</title>
+
+<para>
+
+NetWinders have two network interfaces: The 10Mbps NE2000-compatible
+card is <filename>eth0</filename> and the 100Mbps Tulip card is
+<filename>eth1</filename>.
+
+</para><note><para>
+
+You need NeTTrom 2.2.1 or later to boot the
+installation system. NeTTrom 2.3.3 is recommended: get these files
+from 
+<ulink url="ftp://ftp.netwinder.org/pub/netwinder/firmware/"></ulink>:
+<itemizedlist>
+<listitem><para>
+
+<filename>nettrom-2.3-3.armv4l.rpm</filename>
+
+</para></listitem>
+<listitem><para>
+
+<filename>nettrom-2.3.3.bin</filename>
+
+</para></listitem>
+<listitem><para>
+
+<filename>nettrom-2.3.3.bin.md5sum</filename>
+
+</para></listitem>
+</itemizedlist>
+
+</para></note><para>
+
+After rebooting and interrupting the boot process during the countdown, you 
+must first configure the network either with a static address:
+<informalexample><screen>
+
+    NeTTrom command-> setenv eth0_ip 192.168.0.10/24
+
+</screen></informalexample>
+where 24 is the number of set bits in the netmask, or a dynamic address:
+<informalexample><screen>
+
+    NeTTrom command-> boot diskless
+
+</screen></informalexample>
+
+</para><para>
+
+You may also need to configure the <userinput>route1</userinput>
+settings if the TFTP
+server is not on the local subnet.  The rest of the config is pretty 
+standard (the save-all step is optional):
+<informalexample><screen>
+
+    NeTTrom command-> setenv kerntftpserver 192.168.0.1
+    NeTTrom command-> setenv kerntftpfile tftpboot.img
+    NeTTrom command-> save-all
+    NeTTrom command-> setenv netconfig_eth0 flash
+    NeTTrom command-> setenv kernconfig tftp
+
+</screen></informalexample>
+
+</para><para>
+
+Only the last two of these interfere with normal disk booting, so it is 
+safe to <command>save-all</command> right before it, which will
+store the network settings in case you need to boot from the network
+again. Use the <command>printenv</command> command to review your
+environment settings. Finally, if your <envar>cmdappend</envar>
+NeTTrom variable has the <option>noinitrd</option> option (which is  
+necessary to boot 2.4 kernels), you must remove it so the downloaded 
+kernel can boot with its attached ramdisk.
+
+</para>
+  </sect3>
+
+  <sect3 arch="arm"><title>Booting from TFTP on CATS</title>
+
+<para>
+
+On CATS machines, use <command>boot de0:</command> or similar at the
+Cyclone prompt.
+
+</para>
+   </sect3>
+  </sect2>
+
+
+
+  <sect2 arch="arm"><title>Booting from CD-ROM</title>
+
+&boot-installer-intro-cd.xml;
+
+<para>
+
+To boot a CD-ROM from the Cyclone console prompt, use the command
+<command>boot cd0:cats.bin</command>
+
+</para>
+  </sect2>
diff --git a/eu/boot-installer/boot-installer.xml b/eu/boot-installer/boot-installer.xml
new file mode 100644
index 000000000..9bf77d2b2
--- /dev/null
+++ b/eu/boot-installer/boot-installer.xml
@@ -0,0 +1,28 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 13948 untranslated -->
+
+<chapter id="boot-installer"><title>Booting the Installation System</title>
+
+ <sect1><title>Booting the Installer on &arch-title;</title>
+<para> </para>
+<!-- This info is so architecture dependent, that I have turned the   -->
+<!-- structure inside out for this chapter. Each arch has a document. -->
+
+&boot-installer-alpha.xml;
+&boot-installer-arm.xml;
+&boot-installer-i386.xml;
+&boot-installer-ia64.xml;
+&boot-installer-m68k.xml;
+&boot-installer-mips.xml;
+&boot-installer-s390.xml;
+&boot-installer-powerpc.xml;
+&boot-installer-sparc.xml;
+
+ </sect1>
+
+&boot-installer-parameters.xml;
+&boot-installer-trouble.xml;
+
+</chapter>
+
+
diff --git a/eu/boot-installer/i386.xml b/eu/boot-installer/i386.xml
new file mode 100644
index 000000000..0867c918a
--- /dev/null
+++ b/eu/boot-installer/i386.xml
@@ -0,0 +1,542 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 16879 untranslated -->
+
+  <sect2 arch="i386"><title>Booting from a CD-ROM</title>
+
+&boot-installer-intro-cd.xml;
+
+<para>
+
+You may need to configure your hardware as indicated in 
+<xref linkend="boot-dev-select"/>. Then put the CD-ROM into the drive,
+and reboot.  The system should boot up, and you should be presented
+with the <prompt>boot:</prompt> prompt.  Here you can enter your
+boot arguments, or just hit &enterkey;.
+
+</para><para>
+
+<!-- We'll comment the following section until we know exact layout -->
+<!-- 
+CD #1 of official Debian CD-ROM sets for &arch-title; will present a
+<prompt>boot:</prompt> prompt on most hardware. Press
+<keycap>F3</keycap> to see the list of kernel options available
+from which to boot. Just type your chosen flavor name (idepci,
+vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt
+followed by &enterkey;.
+
+</para><para>
+
+If your hardware doesn't support booting of multiple images, put one
+of the other CDs in the drive. It appears that most SCSI CD-ROM drives 
+do not support <command>isolinux</command> multiple image booting, so users
+with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact), 
+or CD5 (bf2.4). 
+
+</para><para>
+
+CD's 2 through 5 will each boot a 
+different ``flavor'' depending on which CD-ROM is
+inserted. See <xref linkend="kernel-choice"/> for a discussion of the
+different flavors.  Here's how the flavors are laid out on the
+different CD-ROMs:
+
+<variablelist>
+<varlistentry>
+<term>CD 1</term><listitem><para>
+
+Allows a selection of kernel images to boot from (the idepci flavor is
+the default if no selection is made). 
+
+</para></listitem></varlistentry>
+<varlistentry>
+<term>CD 2</term><listitem><para>
+
+Boots the `vanilla' flavor.
+
+</para></listitem></varlistentry>
+<varlistentry>
+<term>CD 3</term><listitem><para>
+
+Boots the `compact' flavor.
+
+</para></listitem></varlistentry>
+<varlistentry>
+<term>CD 4</term><listitem><para>
+
+Boots the `idepci' flavor.
+
+</para></listitem></varlistentry>
+<varlistentry>
+<term>CD 5</term><listitem><para>
+
+Boots the `bf2.4' flavor.
+
+</para></listitem></varlistentry>
+
+ </variablelist>
+
+</para><para>
+
+-->
+
+If your system can't boot directly from CD-ROM, or you simply can't
+seem to get it to work, don't despair; you can simply run
+<command>E:\install\boot.bat</command> under DOS (replace
+<userinput>E:</userinput> with whatever drive letter DOS assigns to
+your CD-ROM drive) to start the installation process. Then, skip down
+to <xref linkend="init-config"/>.
+
+</para><para>
+
+Also, if you're going to be installing from a FAT (DOS) partition, you
+have the option of booting the installer from the hard disk. See 
+<xref linkend="install-from-dos"/> for more information on 
+installing via this method.
+
+</para>
+  </sect2>
+
+
+
+  <sect2 arch="i386" id="install-from-dos">
+  <title>Booting from a DOS partition</title>
+
+&boot-installer-intro-hd.xml;
+
+<para>
+
+Boot into DOS (not Windows) without any drivers being loaded.  To do
+this, you have to press <keycap>F8</keycap> at exactly the right
+moment (and optionally select the `safe mode command prompt only'
+option).  Enter the subdirectory for the flavor you chose, e.g.,
+
+<informalexample><screen>
+
+cd c:\current\compact
+
+</screen></informalexample>.  
+
+Next, execute <command>install.bat</command>.
+The kernel will load and launch the installer system. 
+
+</para><para>
+
+Please note, there is currently a loadlin problem (#142421) which
+precludes <filename>install.bat</filename> from being used with the
+bf2.4 flavor. The symptom of the problem is an
+<computeroutput>invalid compressed format</computeroutput> error.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="i386" id="boot-initrd">
+  <title>Booting from linux using <command>LILO</command> or
+  <command>GRUB</command></title>
+<para>
+
+For <command>LILO</command>, you will need to configure two
+essentials things in <filename>/etc/lilo.conf</filename>:
+<itemizedlist>
+<listitem><para>
+
+to load the <filename>initrd.gz</filename> installer at boot time;
+
+</para></listitem>
+<listitem><para>
+
+have the <filename>vmlinuz</filename> kernel use a RAM disk as
+its root partition.
+
+</para></listitem>
+</itemizedlist>
+
+Here is a <filename>/etc/lilo.conf</filename> example:
+
+</para><para>
+
+<informalexample><screen>
+
+image=/boot/newinstall/vmlinuz
+       label=newinstall
+       initrd=/boot/newinstall/initrd.gz
+       root=/dev/ram
+       append="devfs=mount,dall"
+
+</screen></informalexample>
+
+For more details, refer to the
+<citerefentry><refentrytitle>initrd</refentrytitle>
+<manvolnum>4</manvolnum></citerefentry> and
+<citerefentry><refentrytitle>lilo.conf</refentrytitle>
+<manvolnum>5</manvolnum></citerefentry> man pages. Now run
+<userinput>lilo</userinput> and reboot.
+
+</para><para>
+
+The procedure for <command>GRUB</command> is quite similar. Locate your
+<filename>menu.lst</filename> in the <filename>/boot/grub/</filename>
+directory (sometimes in the <filename>/boot/boot/grub/</filename>),
+add the following lines:
+
+<informalexample><screen>
+
+title  New Install
+kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram devfs=mount,dall
+initrd (hd0,0)/boot/newinstall/initrd.gz
+
+</screen></informalexample>
+
+and reboot. Please note, that you may need an additional parameter
+<userinput>ramdisk_size=<replaceable>size in KB</replaceable></userinput>,
+depending on the image you are booting. From now on, there should be
+no difference between <command>GRUB</command> or <command>LILO</command>.
+
+</para><para>
+
+You can trace the <filename>initrd</filename> magic at work several
+times during the boot.
+
+<itemizedlist>
+<listitem><para>
+
+before the kernel has even been loaded, <command>LILO</command>
+displays a much longer <computeroutput>Loading
+<replaceable>imagelabel</replaceable>......</computeroutput> line with
+more dots than usual, showing the progression of the RAM disk image
+loading.
+
+</para></listitem>
+<listitem><para>
+
+You should see the <computeroutput>RAM disk driver
+initialized</computeroutput>
+notice, near the real time clock initialization, proving that your
+kernel supports the RAM disk feature.
+
+</para></listitem>
+<listitem><para>
+
+Finally, if you don't see <computeroutput>RAMDISK: ext2 filesystem
+found at block 0</computeroutput> immediately after the partition
+checks, it's probably because
+your kernel miss the <filename>initrd</filename> feature.
+
+</para></listitem>
+</itemizedlist>
+
+</para><para condition="FIXME">
+
+You should now see the debian installer running. If you do not use any
+removable medium, you want to check very early that your network
+connection is working and <emphasis>before</emphasis> irreversibly
+partitioning your hard disk. So you maybe need to
+<userinput>insmod</userinput> some additional kernel modules for this,
+for instance for your network interface. It's time
+<emphasis>not</emphasis> to follow the order of steps suggested by
+<command>debian-installer</command>. Leap directly to <userinput>Mount a
+Previously-Initialized Partition</userinput>, and mount the partition
+where you stored the modules that you extracted from
+<filename>drivers.tgz</filename> (<xref linkend="files-lilo"></xref>).
+
+</para>
+
+<!-- Ideally, configure Device Driver Modules should support the
+following (insmod-ing from the hard-disk) and not only from a floppy.
+That would avoid the need to open a shell -->
+
+<para>
+
+Then switch to an other virtual terminal and use a shell (see 
+<xref linkend="shell"/>) to find drivers
+in the just mounted <filename>/target</filename>
+directory. <userinput>insmod</userinput> the ones you need.
+
+</para><para>
+
+Go to <xref linkend="netcfg"/> in the
+<command>debian-installer</command> installer menus, and
+<userinput>ping</userinput> your favorite debian mirror at last.
+Congratulations!
+
+</para><para>
+
+Use <userinput>Unmount a Partition</userinput> if you have mounted one
+in the previous
+paragraph, safely go back to the partitioning steps at the start of
+<command>debian-installer</command> and follow the regular procedure,
+with the network as a bonus. At this stage, it is even possible
+(only a bit risky) to completely wipe out all the previous partitions
+on your hard drive for a very clean installation. The only risk is that
+your hard drive will be un-bootable for a short period of time.
+
+</para>
+  </sect2>
+
+  <sect2 arch="i386" id="usb-boot">
+  <title>Booting from USB memory stick</title>
+<para>
+
+Lets assume you have prepared everything from <xref
+linkend="boot-dev-select"/> and <xref linkend="boot-usb-files"/>.  Now
+just plug your USB stick into some free USB connector and reboot the
+computer.  The system should boot up, and you should be presented with
+the <prompt>boot:</prompt> prompt.  Here you can enter optional boot
+arguments, or just hit &enterkey;.
+
+</para><para>
+
+In case your computer doesn't support booting from USB memory devices,
+you can still use a single floppy to do the initial boot and then
+switch to USB. Advance according to <xref linkend="floppy-boot"/>; the
+kernel on boot floppy should detect your USB stick automatically. When
+it asks for the root floppy, simply press &enterkey;. You should see
+&d-i; starting.
+
+</para>
+  </sect2>
+
+  <sect2 arch="i386" id="floppy-boot">
+  <title>Booting from Floppies</title>
+<para>
+
+You will have already downloaded the floppy images you needed and
+created floppies from the images in <xref linkend="create-floppy"/>.
+If you need to, you can also modify the boot floppy; see 
+<xref linkend="rescue-replace-kernel"/>.
+
+</para><para>
+
+To boot from the installer boot floppy, place it in the primary floppy
+drive, shut down the system as you normally would, then turn it back
+on.
+
+</para><para>
+
+For installing from a LS-120 drive (ATAPI version) with a set of
+floppies, you need to specify the virtual location for the floppy
+device.  This is done with the <emphasis>root=</emphasis> boot
+argument, giving the device that the ide-floppy driver maps the device
+to. For example, if your LS-120 drive is connected as the first IDE
+device (master) on the second cable, you enter
+<userinput>linux root=/dev/hdc</userinput> at the boot prompt.
+Installation from LS-120 is only supported by 2.4 and later kernels.
+
+</para><para>
+
+Note that on some machines, <keycombo><keycap>Control</keycap>
+<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not
+properly reset the machine, so a ``hard'' reboot is recommended.  If
+you are installing from an existing operating system (e.g., from a DOS
+box) you don't have a choice. Otherwise, please do a hard reboot when
+booting.
+
+</para><para>
+
+The floppy disk will be accessed, and you should then see a screen
+that introduces the boot floppy and ends with the <prompt>boot:</prompt>
+prompt.
+
+</para><para>
+
+You can do two things at the <prompt>boot:</prompt> prompt. You can
+press the function keys <keycap>F1</keycap> through
+<keycap>F10</keycap> to view a few pages of helpful information, or
+you can boot the system.
+
+</para><para>
+
+Information on boot parameters which might be useful can be found by
+pressing <keycap>F4</keycap> through <keycap>F7</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 floppy=thinkpad</userinput>). If you simply press &enterkey;,
+that's the same as typing <userinput>linux</userinput> without any special
+parameters.
+
+</para><para>
+
+Once you press &enterkey;, you should see the message
+<computeroutput>Loading...</computeroutput>, followed by
+<computeroutput>Uncompressing Linux...</computeroutput>, and
+then a screenful or so of information about the hardware in your
+system.  More information on this phase of the boot process can be
+found below in <xref linkend="kernel-msgs"/>.
+
+</para><para>
+
+After booting from the boot floppy, the root floppy is
+requested. Insert the root floppy and press &enterkey;, and the
+contents are loaded into memory. The installer program
+<command>debian-installer</command> is automatically launched.
+
+</para>
+  </sect2>
+  
+  <sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title>
+ 
+&boot-installer-intro-net.xml;
+ 
+<para>
+
+There are various ways to do a TFTP boot on i386.
+
+</para>
+
+   <sect3><title>Etherboot</title>
+<para>
+
+The <ulink url="http://www.etherboot.org">etherboot project</ulink>
+provides bootdiskettes and even bootroms that do a TFTPboot.
+
+</para>
+   </sect3>
+
+   <sect3><title>NIC with network bootROM</title>
+<para>
+
+It could be that your Network Interface Card provides
+TFTP boot functionality.
+
+</para><para condition="FIXME">
+
+Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
+Please refer to this document.
+
+</para>
+   </sect3>
+
+   <sect3><title>NIC or Motherboard that support PXE</title>
+<para>
+
+It could be that your Network Interface Card or Motherboard provides
+PXE boot functionality.
+Which is a <trademark class="trade">Intel</trademark> re-implemention
+of TFTP boot.
+
+</para><para condition="FIXME">
+
+Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
+Please refer to this document.
+
+<!-- from #debian-boot 2004-03-13
+06:37 -!- SuperQ [ben@trogdor.likes.to.burninate.net] has joined #debian-boot
+06:38 < SuperQ> anyone done much with d-i on pxe boot?
+06:39 < SuperQ> I got it all setup, daily build from sjogren's files
+06:39 < joshk> yes, it works
+06:39 < SuperQ> "Warning: unable to open an initial console."
+06:39 < SuperQ> Kernel panic: Attempted to kill init!
+06:39 < joshk> pass devfs=mount to the kernel
+06:40 < joshk> in pxelinux.cfg/whatever
+06:40 < SuperQ> oh.. that's changed since the bug tracking post
+06:40 < SuperQ> http://lists.debian.org/debian-testing/2003/debian-testing-200311/msg00098.html
+06:40 < SuperQ> that says to devfs=nomount
+06:41 < SuperQ> should probably copy the bulk of that message into
+debian/dists/sarge/main/installer-i386/current/doc/INSTALLATION-HOWTO
+06:41 < SuperQ> :) )
+06:41 < joshk> that's from months ago
+06:41 < joshk> :P
+06:41 < SuperQ> I know
+06:42 < SuperQ> but it's still referanced in the howto
+06:42 < SuperQ> yay! it works now
+06:42  * SuperQ gives his new ThinkPad X31 some sarge love
+06:42 < SuperQ> I'll have to write up a page on Sarge/D-I and things for
+                linux-laptops.net
+06:45 < SuperQ> thanks joshk
+-->
+</para>
+   </sect3>
+  </sect2>
+
+  <sect2 arch="i386"><title>i386 Boot Parameters</title>
+<para>
+
+If you are booting from the boot floppy or from CD-ROM you will be
+presented with the boot prompt, <prompt>boot:</prompt>.  Details
+about how to use boot parameters with the boot floppy can be found
+in <xref linkend="floppy-boot"/>.  If you are booting from an
+existing operating system, you'll have to use other means to set boot
+parameters.  For instance, if you are installing from DOS, you can
+edit the <filename>install.bat</filename> file with any text editor.
+
+</para><para>
+
+Some systems have floppies with ``inverted DCLs''. If you receive
+errors reading from the floppy, even when you know the floppy is good,
+try the parameter <userinput>floppy=thinkpad</userinput>.
+
+</para><para>
+
+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>.
+
+</para><para>
+
+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.
+
+</para><para>
+
+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. The language chooser will not appear; only the english
+language will be available during the installation due to limited
+console features. See <xref linkend="boot-parms"/> for details.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="i386">
+  <title>System freeze during the PCMCIA configuration phase</title>
+
+<para>
+
+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.
+
+</para><para>
+
+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-2.html#ss2.5">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.
+
+</para>
+  </sect2>
+
+  <sect2 arch="i386">
+  <title>System freeze while loading the USB modules</title>
+<para>
+
+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.
+
+</para>
+  </sect2>
diff --git a/eu/boot-installer/ia64.xml b/eu/boot-installer/ia64.xml
new file mode 100644
index 000000000..7c6459479
--- /dev/null
+++ b/eu/boot-installer/ia64.xml
@@ -0,0 +1,115 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 14350 untranslated -->
+
+  <sect2 arch="ia64"><title>Booting from a CD-ROM</title>
+
+&boot-installer-intro-cd.xml;
+
+  <emphasis condition="FIXME">Not yet written.</emphasis>
+
+  </sect2>
+
+  <sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>
+
+&boot-installer-intro-net.xml;
+
+<para>
+
+Network booting an ia64 system requires two architecture-specific actions.
+On the boot server, DHCP and TFTP must be configured to deliver
+<command>elilo</command>.
+On the client a new boot option must be defined in the EFI boot manager
+to enable loading over a network.
+
+</para>
+
+  <sect3 arch="ia64" id="boot-tftp-server">
+  <title>Configuring the Server</title>
+<para>
+
+A suitable TFTP entry for network booting an ia64 system looks something
+like this:
+
+<informalexample><screen>
+
+host mcmuffin {
+        hardware ethernet 00:30:6e:1e:0e:83;
+        fixed-address 10.0.0.21;
+        filename "elilo.efi";
+}
+
+</screen></informalexample>
+
+Note that the goal is to get <command>elilo.efi</command> running on
+the client.
+
+</para><para>
+
+Create an <filename>ia64/</filename> subdirectory in your tftpboot
+directory, and populate it with the <filename>vmlinuz</filename> and
+<filename>initrd.gz</filename> files from the Debian installer netboot
+directory.
+
+</para><para>
+
+Copy <filename>elilo.efi</filename> to your tftpboot directory and
+make it world readable.  This file can usually be found in the elilo
+package in IA64 distributions, or in
+<filename>/usr/lib/elilo</filename> or in a subdirectory of
+<filename>/boot/efi</filename>.  A suitable copy is provided in the
+Debian installer netboot directory.
+
+</para><para>
+
+Create an <filename>elilo.conf</filename> file in your tftpboot
+directory.  This will
+be loaded by <command>elilo.efi</command> once it is running on the
+client, and controls what
+happens next, including the choice of kernel, initrd image, etc.  An
+example file is provided in the Debian installer netboot directory, review
+the contents and update as needed for your choice of paths, etc.
+
+It is possible to have different config files for different clients by naming
+them using the client's IP address in hex with the suffix
+<filename>.conf</filename> instead of <filename>elilo.conf</filename>.
+See documentation provided in the <classname>elilo</classname> package
+for details.
+
+</para>
+  </sect3>
+
+  <sect3 arch="ia64" id="boot-tftp-client">
+  <title>Configuring the Client</title>
+<para>
+
+To configure the client to support TFTP booting, start by booting to
+EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>.
+
+<itemizedlist>
+<listitem><para>
+
+Add a boot option.
+
+</para></listitem>
+<listitem><para>
+
+Select the line saying <guimenuitem>Load File
+[Acpi()/.../Mac()]</guimenuitem> and press &enterkey;.
+
+</para></listitem>
+<listitem><para>
+
+Name the entry <userinput>Netboot</userinput> or something similar,
+save, and exit back to the boot options menu.  
+
+</para></listitem>
+</itemizedlist>
+
+You should see the new boot option you just created, and selecting it
+should initiate a DHCP query, leading to a TFTP load of
+<filename>elilo.efi</filename> from the server.
+
+</para>
+
+  </sect3>
+  </sect2>
diff --git a/eu/boot-installer/intro-cd.xml b/eu/boot-installer/intro-cd.xml
new file mode 100644
index 000000000..4959075fa
--- /dev/null
+++ b/eu/boot-installer/intro-cd.xml
@@ -0,0 +1,36 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+<para>
+
+The easiest route for most people will be to use a 
+<ulink url="http://www.debian.org/CD/vendors/">set of Debian CDs</ulink>. 
+If you have a CD set, and if your machine supports booting directly off
+the CD, great!  Simply 
+<phrase arch="i386">
+configure your system for booting off a CD as described in 
+<xref linkend="boot-dev-select"/>,
+</phrase> 
+insert your CD, reboot, and proceed to the next chapter.
+
+</para><para>
+
+Note that certain CD drives may require special drivers, and thus be
+inaccessible in the early installation stages. If it turns out the
+standard way of booting off a CD doesn't work for your hardware,
+revisit this chapter and read about alternate kernels and installation
+methods which may work for you.
+
+</para><para>
+
+Even if you cannot boot from CD-ROM, you can probably install the
+Debian system components and any packages you want from CD-ROM.
+Simply boot using a different media, such as floppies.  When it's
+time to install the operating system, base system, and any additional
+packages, point the installation system at the CD-ROM drive. 
+
+</para><para>
+
+If you have problems booting, see <xref linkend="boot-troubleshooting"/>.
+
+</para>
\ No newline at end of file
diff --git a/eu/boot-installer/intro-hd.xml b/eu/boot-installer/intro-hd.xml
new file mode 100644
index 000000000..be5f65be3
--- /dev/null
+++ b/eu/boot-installer/intro-hd.xml
@@ -0,0 +1,16 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+<para>
+
+Booting from an existing operating system is often a convenient
+option; for some systems it is the only supported method of
+installation. 
+
+</para><para>
+
+To boot the installer from hard disk, you will have already completed
+downloading and placing the needed files in 
+<xref linkend="boot-drive-files"/>.
+
+</para>
\ No newline at end of file
diff --git a/eu/boot-installer/intro-net.xml b/eu/boot-installer/intro-net.xml
new file mode 100644
index 000000000..79189195c
--- /dev/null
+++ b/eu/boot-installer/intro-net.xml
@@ -0,0 +1,19 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+<para>
+
+Booting from the network requires that you have a network
+connection and a TFTP network boot server (DHCP, RARP, or BOOTP).
+
+</para><para arch="hppa">
+
+Older systems such as the 715 might require the use of an RBOOT server
+instead of a BOOTP server.
+
+</para><para>
+
+The installation method to support network booting is described in <xref
+linkend="install-tftp"/>.
+
+</para>
\ No newline at end of file
diff --git a/eu/boot-installer/m68k.xml b/eu/boot-installer/m68k.xml
new file mode 100644
index 000000000..1d96afa9a
--- /dev/null
+++ b/eu/boot-installer/m68k.xml
@@ -0,0 +1,192 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+  <sect2 arch="m68k"><title>Booting from Hard Disk</title>
+
+&boot-installer-intro-hd.xml;
+
+  </sect2>
+
+  <sect2 arch="m68k"><title>Booting from AmigaOS</title>
+<para>
+
+In the <command>Workbench</command>, start the Linux installation
+process by double-clicking on the <guiicon>StartInstall</guiicon> icon
+in the <filename>debian</filename> directory.
+
+</para><para>
+
+You may have to press the &enterkey; key twice after the Amiga
+installer program has output some debugging information into a window.
+After this, the screen will go grey, there will be a few seconds'
+delay. Next, a black screen with white text should come up, displaying
+all kinds of kernel debugging information.  These messages may scroll
+by too fast for you to read, but that's OK.  After a couple of
+seconds, the installation program should start automatically, so you
+can continue down at <xref linkend="init-config"/>.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="m68k"><title>Booting from Atari TOS</title>
+<para>
+
+At the GEM desktop, start the Linux installation process by
+double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the
+<filename>debian</filename> directory and clicking
+<guibutton>Ok</guibutton> at the program options dialog box.
+
+</para><para>
+
+You may have to press the &enterkey; key after the Atari
+bootstrap program has output some debugging information into a
+window. After this, the screen will go grey, there will be a few
+seconds' delay.  Next, a black screen with white text should come up,
+displaying all kinds of kernel debugging information. These messages
+may scroll by too fast for you to read, but that's OK. After a couple
+of seconds, the installation program should start automatically, so
+you can continue below at <xref linkend="init-config"/>.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="m68k"><title>Booting from 68k MacOS</title>
+<para>
+
+At the MacOS desktop, start the Linux installation process by
+double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in
+the <filename>debian</filename> directory. The
+<command>Penguin</command> booter will start up. Go to the
+<guimenuitem>Settings</guimenuitem> item in the
+<guimenu>File</guimenu> menu, click the
+<guilabel>Kernel</guilabel> tab.  Select the kernel
+(<filename>linux.bin</filename>) and ramdisk
+(<filename>root.bin</filename>) images in the
+<filename>debian</filename> directory by clicking on the corresponding
+buttons in the upper right corner, and navigating the file select
+dialogs to locate the files. Close the <guilabel>Settings</guilabel>
+dialog, save the settings and start the bootstrap using the
+<guimenuitem>Boot Now</guimenuitem> item in the
+<guimenu>File</guimenu> menu.
+
+</para><para>
+
+The <command>Penguin</command> booter will output some debugging
+information into a window. After this, the screen will go grey, there
+will be a few seconds' delay. Next, a black screen with white text
+should come up, displaying all kinds of kernel debugging
+information. These messages may scroll by too fast for you to read,
+but that's OK. After a couple of seconds, the installation program
+should start automatically, so you can continue below at 
+<xref linkend="init-config"/>.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="m68k"><title>Booting from a CD-ROM</title>
+
+&boot-installer-intro-cd.xml;
+
+<para>
+
+Currently, the only &arch-title; subarchitecture that
+supports CD-ROM booting is the BVME6000. The easiest route In that
+case will be to use a 
+<ulink url="&url-debian-cd-vendors;">set of Debian CDs</ulink>. 
+Simply insert your CD, reboot, and proceed to the next chapter.  
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title>
+
+&boot-installer-intro-net.xml;
+
+<para>
+
+After booting the VMEbus systems you will be presented with the LILO
+<prompt>Boot:</prompt> prompt.  At that prompt enter one of the
+following to boot Linux and begin installation proper of the Debian
+software using vt102 terminal emulation:
+
+<!-- Because the &enterkey; definition uses <keycap>,    -->
+<!-- we use <screen> instead of <userinput> in this list -->
+
+<itemizedlist>
+<listitem><para>
+
+type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000
+
+</para></listitem>
+<listitem><para>
+
+type <screen>i162 &enterkey;</screen> to install an MVME162
+
+</para></listitem>
+<listitem><para>
+
+type <screen>i167 &enterkey;</screen> to install an MVME166/167
+
+</para></listitem>
+    </itemizedlist>
+
+</para><para>
+
+You may additionally append the string
+<screen>TERM=vt100</screen> to use vt100 terminal emulation,
+e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="m68k" id="boot-from-floppies">
+  <title>Booting from Floppies</title>
+<para>
+
+For most m68k architectures, booting from a local filesystem is the
+recommended method.
+
+</para><para>
+
+Booting from the boot floppy is supported only for Atari and VME
+(with a SCSI floppy drive on VME) at this time. 
+
+</para>
+ </sect2>
+
+
+  <sect2 arch="m68k"><title>Macintosh Limitations</title>
+<para>
+
+In the case of Macintosh, you must retain the original Mac system and
+boot from it. It is <emphasis>essential</emphasis> that, when booting
+MacOS in preparation for booting the Penguin linux loader, you must
+hold the <keycap>shift</keycap> key down to prevent extensions from
+loading. If you
+don't use MacOS except for loading linux, you can accomplish the same
+thing by removing all extensions and control panels from the Mac's
+System Folder. Otherwise extensions may be left running and cause
+random problems with the running linux kernel.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="m68k"><title>Penguin Boot Parameters</title>
+<para>
+
+In the Penguin boot program, choose <guimenu>File</guimenu> -&gt;
+<guimenuitem>Settings...</guimenuitem>, then switch to the
+<guilabel>Options</guilabel> tab.  Boot parameters may be typed in to
+the text entry area.  If you will always want to use these settings,
+select <guimenu>File</guimenu> -&gt; <guimenuitem>Save Settings as
+Default</guimenuitem>.
+
+</para>
+  </sect2>
diff --git a/eu/boot-installer/mips.xml b/eu/boot-installer/mips.xml
new file mode 100644
index 000000000..f1c27e517
--- /dev/null
+++ b/eu/boot-installer/mips.xml
@@ -0,0 +1,43 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+  <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title>
+<para>
+
+After entering the command monitor use
+<informalexample><screen>
+
+bootp(): root=/dev/ram0
+
+</screen></informalexample>
+on SGI Indys to boot linux and to begin installation of the Debian
+Software.  In order to make this
+work you may have to unset the <envar>netaddr</envar> environment
+variable. Type 
+<informalexample><screen>
+
+unsetenv netaddr
+
+</screen></informalexample>
+in the command monitor to do this. 
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="mips"><title>Boot Parameters</title>
+<para>
+
+On SGI Indys you can append boot parameters to the
+<command>bootp():</command> command in the command monitor.
+
+</para><para>
+
+Following the <command>bootp():</command> command you can give the
+path and name of the file to boot if you did not give an explicit name
+via your bootp/dhcp server - Example:
+<command>bootp():/boot/tftpboot.img</command>
+
+</para>
+  </sect2>
diff --git a/eu/boot-installer/parameters.xml b/eu/boot-installer/parameters.xml
new file mode 100644
index 000000000..b8a9c9784
--- /dev/null
+++ b/eu/boot-installer/parameters.xml
@@ -0,0 +1,277 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 14359 untranslated -->
+
+ <sect1 id="boot-parms"><title>Boot Parameters</title>
+<para>
+
+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.
+
+</para><para>
+
+If this is the first time you're booting the system, try the default
+boot parameters (i.e., don't try setting arguments) 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.
+
+</para><para>
+
+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"/>.
+
+</para><para>
+
+When the kernel boots, a message 
+
+<informalexample><screen>
+
+Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available 
+
+</screen></informalexample>
+
+should be emitted early in the process.
+<replaceable>total</replaceable> should match the total amount of RAM,
+in kilobytes.  If this doesn't match the actual amount of RAM you have
+installed, you need to use the
+<userinput>mem=<replaceable>ram</replaceable></userinput> parameter,
+where <replaceable>ram</replaceable> is set to the amount of memory,
+suffixed with ``k'' for kilobytes, or ``m'' for megabytes.  For
+example, both <userinput>mem=65536k</userinput> and
+<userinput>mem=64m</userinput> mean 64MB of RAM.
+
+</para><para>
+
+If your monitor is only capable of black-and-white, use the
+<userinput>mono</userinput> boot argument.  Otherwise, your
+installation will use color, which is the default.
+
+</para><para condition="supports-serial-console">
+
+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>.
+
+</para><para arch="sparc">
+
+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>.
+
+</para>
+
+
+  <sect2 id="installer-args"><title>Debian Installer Arguments</title>
+<para>
+
+The installation system recognizes a few boot arguments which may be
+useful. 
+
+</para>
+
+<variablelist>
+<varlistentry>
+<term>DEBCONF_PRIORITY</term>
+<listitem><para>
+
+This parameter settings will set the highest priority of messages
+to be displayed. 
+
+</para><para>
+
+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.
+
+</para><para>
+
+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.
+
+</para></listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>DEBCONF_FRONTEND</term>
+<listitem><para>
+
+This boot parameter controls the type of user interface used for the
+installer. The current possible parameter settings are:
+
+<itemizedlist>
+<listitem>
+<para><userinput>DEBCONF_FRONTEND=noninteractive</userinput></para>
+</listitem><listitem>
+<para><userinput>DEBCONF_FRONTEND=text</userinput></para>
+</listitem><listitem>
+<para><userinput>DEBCONF_FRONTEND=newt</userinput></para>
+</listitem><listitem>
+<para><userinput>DEBCONF_FRONTEND=slang</userinput></para>
+</listitem><listitem>
+<para><userinput>DEBCONF_FRONTEND=ncurses</userinput></para>
+</listitem><listitem>
+<para><userinput>DEBCONF_FRONTEND=bogl</userinput></para>
+</listitem><listitem>
+<para><userinput>DEBCONF_FRONTEND=gtk</userinput></para>
+</listitem><listitem>
+<para><userinput>DEBCONF_FRONTEND=corba</userinput></para>
+</listitem>
+</itemizedlist>
+
+The default front end is <userinput>DEBCONF_FRONTEND=newt</userinput>.
+<userinput>DEBCONF_FRONTEND=text</userinput> may be preferable for
+serial console installs. Other frontends but
+<userinput>newt</userinput> are not available on default install
+media, so this is not very useful right now.
+
+</para></listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>BOOT_DEBUG</term>
+<listitem><para>
+
+Passing this boot parameter will cause the boot to be more verbosely 
+logged.
+
+<variablelist>
+<varlistentry>
+<term><userinput>BOOT_DEBUG=0</userinput></term>
+<listitem><para>This is the default.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>BOOT_DEBUG=1</userinput></term>
+<listitem><para>More verbose than usual.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>BOOT_DEBUG=2</userinput></term>
+<listitem><para>Lots of debugging information.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>BOOT_DEBUG=3</userinput></term>
+<listitem><para>
+
+Shells are run at various points in the boot process to allow detailed
+debugging. Exit the shell to continue the boot.
+
+</para></listitem>
+</varlistentry>
+</variablelist>
+
+</para></listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>INSTALL_MEDIA_DEV</term>
+<listitem><para>
+
+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>
+
+</para><para>
+
+The boot floppy, which normally scans all floppys and USB storage
+devices it can to find the root floppy, can be overridden by this
+parameter to only look at the one device.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>debian-installer/framebuffer</term>
+<listitem><para>
+
+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.
+
+</para><para arch="i386">
+
+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.
+
+</para><para arch="m68k">
+
+Such problems have been reported on the Amiga 1200 and SE/30.
+
+</para><para arch="hppa">
+
+Such problems have been reported on hppa.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>debian-installer/probe/usb</term>
+<listitem><para>
+
+Set to <userinput>false</userinput> to prevent probing for USB on
+boot, if that causes problems.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>netcfg/disable_dhcp</term>
+<listitem><para>
+
+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
+chage the obtained settings. You can get to the manual network setup
+only in case the DHCP probe fails.
+
+</para><para>
+
+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.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>hw-detect/start_pcmcia</term>
+<listitem><para>
+
+Set to <userinput>false</userinput> to prevent starting PCMCIA
+services, if that causes problems. Some laptops are well known for
+this misbehaviour.
+
+</para></listitem>
+</varlistentry>
+
+</variablelist>
+  </sect2>
+ </sect1>
+
diff --git a/eu/boot-installer/powerpc.xml b/eu/boot-installer/powerpc.xml
new file mode 100644
index 000000000..6d001be6f
--- /dev/null
+++ b/eu/boot-installer/powerpc.xml
@@ -0,0 +1,188 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 15220 untranslated -->
+
+  <sect2 arch="powerpc"><title>Booting from a CD-ROM</title>
+
+&boot-installer-intro-cd.xml;
+
+<para>
+
+Currently, the only &arch-title; subarchitectures that support CD-ROM
+booting are PReP and New World PowerMacs. On PowerMacs, hold the
+<keycap>c</keycap> key, or else the combination of
+<keycap>Command</keycap>, <keycap>Option</keycap>,
+<keycap>Shift</keycap>, and <keycap>Delete</keycap>
+keys together while booting to boot from the CD-ROM.
+
+</para><para>
+
+OldWorld Powermacs will not boot a Debian CD, because OldWorld
+computers relied on a MacOSROM CD boot driver to be present on the CD,
+and a free-software version of this driver is not available. All
+OldWorld systems have floppy drives, so use the floppy drive to launch
+the installer, and then point the installer to the CD for the needed
+files.
+
+</para><para>
+
+If your system doesn't boot directly from CD-ROM, you can still use
+the CD-ROM to install the system. On NewWorlds, you can also use an
+OpenFirmware command to boot from the CD-ROM manually. Follow the
+instructions in <xref linkend="boot-newworld"/> for booting from
+the hard disk, except use the path to <command>yaboot</command> on the
+CD at the OF prompt, such as
+
+<informalexample><screen>
+
+0 > boot cd:,\install\yaboot
+
+</screen></informalexample>
+</para>
+  </sect2>
+
+  <sect2 arch="powerpc" id="install-drive">
+  <title>Booting from Hard Disk</title>
+
+&boot-installer-intro-hd.xml;
+
+  <sect3><title>Booting CHRP from OpenFirmware</title>
+
+<para>
+
+  <emphasis>Not yet written.</emphasis>
+
+</para>
+   </sect3>
+
+   <sect3><title>Booting OldWorld PowerMacs from MacOS</title>
+<para>
+
+If you set up BootX in <xref linkend="files-oldworld"/>, you can
+use it to boot into the installation system. Double click the
+<guiicon>BootX</guiicon> application icon. Click on the
+<guibutton>Options</guibutton> button and select <guilabel>Use
+Specified RAM Disk</guilabel>. This will give you the 
+chance to select the <filename>ramdisk.image.gz</filename> file. You
+may need to select the <guilabel>No Video Driver</guilabel> checkbox,
+depending on your hardware. Then click the
+<guibutton>Linux</guibutton> button to shut down MacOS and launch the
+installer.
+
+</para>
+   </sect3>
+
+
+  <sect3 id="boot-newworld">
+  <title>Booting NewWorld Macs from OpenFirmware</title>
+<para>
+
+You will have already placed the <filename>linux.bin, yaboot,
+yaboot.conf</filename>, and <filename>root.bin</filename> files at the
+root level of your HFS partition in <xref linkend="files-newworld"/>. 
+Restart the computer, and immediately (during the chime) hold down the
+<keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>,
+<keycap>o</keycap>, and <keycap>f</keycap> keys all together. After 
+a few seconds you will be presented with the Open Firmware prompt.
+At the prompt, type
+
+<informalexample><screen>
+
+0 > boot hd:<replaceable>x</replaceable>,yaboot
+
+</screen></informalexample>
+
+replacing <replaceable>x</replaceable> with the partition number of
+the HFS partition where the
+kernel and yaboot files were placed, followed by a &enterkey;. On some
+machines, you may need to use <userinput>ide0:</userinput> instead of
+<userinput>hd:</userinput>. In a few more seconds you will see a
+yaboot prompt
+
+<informalexample><screen>
+
+boot:
+
+</screen></informalexample>
+
+At yaboot's <prompt>boot:</prompt> prompt, type either
+<userinput>install</userinput> or <userinput>install-safe</userinput>
+followed by a &enterkey;.  The `safe' option uses the
+<userinput>video=ofonly</userinput> argument for maximum
+compatibility; you can try it if <userinput>install</userinput>
+doesn't work. The Debian installation program should start.
+
+</para>
+   </sect3>
+  </sect2>
+
+  <sect2 arch="powerpc" id="boot-tftp"><title>Booting with TFTP</title>
+
+&boot-installer-intro-net.xml;
+
+<para>
+
+Currently, PReP and New World PowerMac systems support netbooting. 
+
+</para><para>
+
+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 <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="powerpc">
+  <title>Booting from Floppies</title>
+<para>
+
+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.
+
+</para><para>
+
+You will have already downloaded the floppy images you needed and
+created floppies from the images in <xref linkend="create-floppy"/>.
+
+</para><para>
+
+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.
+
+</para><note><para>
+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.
+
+</para></note><para>
+
+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.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="powerpc"><title>PowerPC Boot Parameters</title>
+<para>
+
+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> .
+
+</para>
+  </sect2>
diff --git a/eu/boot-installer/s390.xml b/eu/boot-installer/s390.xml
new file mode 100644
index 000000000..1c4e3efec
--- /dev/null
+++ b/eu/boot-installer/s390.xml
@@ -0,0 +1,30 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+  <sect2 arch="s390"><title>s390 Limitations</title>
+<para>
+
+In order to run the installation system a working network setup and
+telnet session is needed on S/390.
+
+</para><para>
+
+The booting process starts with a network setup that prompts you for
+several network parameters. If the setup is successful, you will login
+to the system by starting a telnet session which will launch the
+standard installation system.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="s390"><title>s390 Boot Parameters</title>
+<para>
+
+On S/390 you can append boot parameters in the parm file.  This file can
+either be in ASCII or EBCDIC format.  Please read 
+<ulink url="&url-s390-devices;">Device Drivers and Installation Commands</ulink>
+for more information about S/390-specific boot parameters.
+
+</para>
+  </sect2>
diff --git a/eu/boot-installer/sparc.xml b/eu/boot-installer/sparc.xml
new file mode 100644
index 000000000..81549db6b
--- /dev/null
+++ b/eu/boot-installer/sparc.xml
@@ -0,0 +1,102 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+  <sect2 arch="sparc"><title>Booting from NFS</title>
+<para>
+
+To install the system via NFS, simply select
+<userinput>NFS</userinput> for the location of the images and files
+and follow the instructions provided.  You will be prompted for the
+<filename>server:/directory</filename> where the images are located.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title>
+
+&boot-installer-intro-net.xml;
+
+<para>
+
+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 <userinput>boot net:dhcp</userinput> to boot from
+a TFTP and DHCP server. Some older OpenBoot revisions require using
+the device name, such as <userinput>boot le()</userinput>; these
+probably don't support DHCP.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="sparc"><title>Booting from a CD-ROM</title>
+
+&boot-installer-intro-cd.xml;
+
+<para>
+
+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). You may have to use
+the actual device name for older OpenBoot versions that don't support
+this special command. Note that some problems have been reported on Sun4m
+(e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM.
+
+</para>
+  </sect2>
+
+
+  <sect2 arch="sparc">
+  <title>Booting from Floppies</title>
+<para>
+
+To boot from floppy on a Sparc, use 
+<informalexample><screen>
+
+Stop-A -> OpenBoot: "boot floppy"
+
+</screen></informalexample>
+</para><para>
+
+Be warned that the newer Sun4u (ultra) architecture does not support
+floppy booting. A typical error message is <computeroutput>Bad magic
+number in disk label - Can't open disk label package</computeroutput>.
+Furthermore, a number of Sun4c models (such as the IPX) do not support
+the compressed images found on the disks, so also are not supported.
+
+</para><para>
+
+Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from
+booting (instead of not supporting booting at all). The appropriate
+OBP update can be downloaded as product ID 106121 from
+<ulink url="http://sunsolve.sun.com"></ulink>.
+
+</para><para>
+
+If you are booting from the floppy, and you seem messages such as 
+<informalexample><screen>
+
+Fatal error: Cannot read partition
+Illegal or malformed device name
+
+</screen></informalexample>
+then it is possible that floppy booting is simply not supported on
+your machine.
+
+</para>
+  </sect2>
+
+  <sect2 arch="sparc"><title>IDPROM Messages</title>
+<para>
+
+If you cannot boot because you get messages about a problem with
+``IDPROM'', 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.
+
+</para>
+  </sect2>
diff --git a/eu/boot-installer/trouble.xml b/eu/boot-installer/trouble.xml
new file mode 100644
index 000000000..2db641c44
--- /dev/null
+++ b/eu/boot-installer/trouble.xml
@@ -0,0 +1,200 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 15221 untranslated -->
+
+ <sect1 id="boot-troubleshooting">
+ <title>Troubleshooting the Install Process</title>
+<para>
+</para>
+
+  <sect2 id="unreliable-floppies">
+  <title>Floppy Disk Reliability</title>
+
+<para>
+
+The biggest problem for people installing Debian for the first time
+seems to be floppy disk reliability.
+
+</para><para>
+
+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.
+
+</para><para>
+
+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.
+
+</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>
+
+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.
+
+</para>
+  </sect2>
+
+  <sect2><title>Boot Configuration</title>
+
+<para>
+
+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"/>.
+
+</para><para>
+
+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>.
+
+</para><para>
+
+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>
+
+</para><para>
+
+There are, however, some limitations in our boot floppy set with
+respect to supported hardware.  Some Linux-supported platforms might
+not be directly supported by our boot floppies.  If this is the case,
+you may have to create a custom boot disk (see
+<xref linkend="rescue-replace-kernel"/>), or investigate network
+installations.
+
+</para><para>
+
+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>.
+
+</para>
+  </sect2>
+
+  <sect2 id="kernel-msgs">
+  <title>Interpreting the Kernel Startup Messages</title>
+
+<para>
+
+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"/>).
+
+</para>
+  </sect2>
+
+
+  <sect2 id="problem-report">
+  <title>Bug Reporter</title>
+<para>
+
+If you get through the initial boot phase but cannot complete the
+install, the bug reporter menu choice may be helpful. It copies system
+error logs and configuration information to a user-supplied floppy.
+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.
+
+</para><para>
+
+Other pertinent installation messages may be found in
+<filename>/target/var/log/debian-installer/</filename> during the
+installation, and <filename>/var/log/debian-installer/</filename>
+after the computer has been booted into the installed system.
+
+</para>
+  </sect2>
+
+  <sect2 id="submit-bug">
+  <title>Submitting Bug Reports</title>
+<para>
+
+If you still have problems, please submit a bug report.  Send an email
+to <email>submit@bugs.debian.org</email>.  You
+<emphasis>must</emphasis> include the following as the first lines of
+the email:
+
+<informalexample><screen>
+
+Package: installation-reports
+Version: <replaceable>version</replaceable>
+
+</screen></informalexample>
+
+Be sure to fill in <replaceable>version</replaceable> with the
+version of the debian-installer that you used. The version number can
+be found if you press <keycap>F1</keycap> key on the
+<prompt>boot:</prompt> prompt of your installation media. You should
+also mention where did you download the installation media, or the
+source of a CD you bought.
+
+</para><para>
+
+You should also include the following information in your bug report.
+If you use the program <command>reportbug</command> to submit your 
+report, this information will be included automatically.
+
+<informalexample><screen>
+
+<phrase arch="i386">
+flavor:        <replaceable>flavor of image you are using</replaceable>
+</phrase>
+architecture:  &architecture; 
+model:         <replaceable>your general hardware vendor and model</replaceable>
+memory:        <replaceable>amount of RAM</replaceable>
+scsi:          <replaceable>SCSI host adapter, if any</replaceable>
+cd-rom:        <replaceable>CD-ROM model and interface type, e.g., ATAPI</replaceable>
+network card:  <replaceable>network interface card, if any</replaceable>
+pcmcia:        <replaceable>details of any PCMCIA devices</replaceable>
+
+</screen></informalexample>
+
+</para><para>
+
+Depending on the nature of the bug, it also might be useful to report
+whether you are installing to IDE or SCSI disks, other peripheral
+devices such as audio, disk capacity, and the model of video card.
+
+</para><para>
+
+In the bug report, describe what the problem is, including the last
+visible kernel messages in the event of a kernel hang.  Describe the
+steps that you did which brought the system into the problem state.
+
+</para>
+
+  </sect2>
+
+ </sect1>