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

17 files changed, 2454 insertions, 0 deletions

diff --git a/fi/hardware/hardware-supported.xml b/fi/hardware/hardware-supported.xml
new file mode 100644
index 000000000..43bae3a81
--- /dev/null
+++ b/fi/hardware/hardware-supported.xml
@@ -0,0 +1,341 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+ <sect1 id="hardware-supported">
+ <title>Supported Hardware</title>
+
+<para>
+
+Debian does not impose hardware requirements beyond the requirements
+of the Linux kernel and the GNU tool-sets.  Therefore, any
+architecture or platform to which the Linux kernel, libc,
+<command>gcc</command>, etc. have been ported, and for which a Debian
+port exists, can run Debian. Please refer to the Ports pages at
+<ulink url="&url-ports;"></ulink> for
+more details on &arch-title; architecture systems which have been
+tested with Debian.
+
+</para><para>
+
+Rather than attempting to describe all the different hardware
+configurations which are supported for &arch-title;, this section
+contains general information and pointers to where additional
+information can be found.
+
+</para>
+
+  <sect2><title>Supported Architectures</title>
+
+<para>
+
+Debian &release; supports eleven major architectures and several
+variations of each architecture known as <quote>flavors</quote>.
+
+</para><para>
+
+<informaltable>
+<tgroup cols="4">
+<thead>
+<row>
+  <entry>Architecture</entry><entry>Debian Designation</entry>
+  <entry>Subarchitecture</entry><entry>Flavor</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry morerows="2">Intel x86-based</entry>
+  <entry morerows="2">i386</entry>
+  <entry morerows="2"></entry>
+  <entry>vanilla</entry>
+</row><row>
+  <entry>speakup</entry>
+</row><row>
+  <entry>linux26</entry>
+</row>
+
+<row>
+  <entry morerows="5">Motorola 680x0</entry>
+  <entry morerows="5">m68k</entry>
+  <entry>Atari</entry>
+  <entry>atari</entry>
+</row><row>
+  <entry>Amiga</entry>
+  <entry>amiga</entry>
+</row><row>
+  <entry>68k Macintosh</entry>
+  <entry>mac</entry>
+</row><row>
+  <entry morerows="2">VME</entry>
+  <entry>bvme6000</entry>
+</row><row>
+  <entry>mvme147</entry>
+</row><row>
+  <entry>mvme16x</entry>
+</row>
+
+<row>
+  <entry>DEC Alpha</entry>
+  <entry>alpha</entry>
+  <entry></entry>
+  <entry></entry>
+</row>
+
+<row>
+  <entry morerows="1">Sun SPARC</entry>
+  <entry morerows="1">sparc</entry>
+  <entry morerows="1"></entry>
+  <entry>sun4cdm</entry>
+</row><row>
+  <entry>sun4u</entry>
+</row>
+
+<row>
+  <entry morerows="3">ARM and StrongARM</entry>
+  <entry morerows="3">arm</entry>
+  <entry morerows="3"></entry>
+  <entry>netwinder</entry>
+</row><row>
+  <entry>riscpc</entry>
+</row><row>
+  <entry>shark</entry>
+</row><row>
+  <entry>lart</entry>
+</row>
+
+<row>
+  <entry morerows="3">IBM/Motorola PowerPC</entry>
+  <entry morerows="3">powerpc</entry>
+  <entry>CHRP</entry>
+  <entry>chrp</entry>
+</row><row>
+  <entry>PowerMac</entry>
+  <entry>pmac</entry>
+</row><row>
+  <entry>PReP</entry>
+  <entry>prep</entry>
+</row><row>
+  <entry>APUS</entry>
+  <entry>apus</entry>
+</row>
+
+<row>
+  <entry morerows="1">HP PA-RISC</entry>
+  <entry morerows="1">hppa</entry>
+  <entry>PA-RISC 1.1</entry>
+  <entry>32</entry>
+</row><row>
+  <entry>PA-RISC 2.0</entry>
+  <entry>64</entry>
+</row>
+
+<row>
+  <entry>Intel ia64-based</entry>
+  <entry>ia64</entry>
+  <entry></entry>
+  <entry></entry>
+</row>
+
+<row>
+  <entry morerows="2">MIPS (big endian)</entry>
+  <entry morerows="2">mips</entry>
+  <entry morerows="1">SGI Indy/Indigo 2</entry>
+  <entry>r4k-ip22</entry>
+</row><row>
+  <entry>r5k-ip22</entry>
+</row><row>
+  <entry>Broadcom BCM91250A (SWARM)</entry>
+  <entry>sb1-swarm-bn</entry>
+</row>
+
+<row>
+  <entry morerows="3">MIPS (little endian)</entry>
+  <entry morerows="3">mipsel</entry>
+  <entry>Cobalt</entry>
+  <entry>cobalt</entry>
+</row><row>
+  <entry morerows="1">DECstation</entry>
+  <entry>r4k-kn04</entry>
+</row><row>
+  <entry>r3k-kn02</entry>
+</row><row>
+  <entry>Broadcom BCM91250A (SWARM)</entry>
+  <entry>sb1-swarm-bn</entry>
+</row>
+
+<row>
+  <entry morerows="1">IBM S/390</entry>
+  <entry morerows="1">s390</entry>
+  <entry>IPL from VM-reader and DASD</entry>
+  <entry>generic</entry>
+</row><row>
+  <entry>IPL from tape</entry>
+  <entry>tape</entry>
+</row>
+
+</tbody></tgroup></informaltable>
+
+</para><para>
+
+This document covers installation for the
+<emphasis>&arch-title;</emphasis> architecture.  If you are looking
+for information on any of the other Debian-supported architectures
+take a look at the
+<ulink url="http://www.debian.org/ports/">Debian-Ports</ulink> pages.
+
+</para><para condition="new-arch">
+
+This is the first official release of &debian; for the &arch-title;
+architecture.  We feel that it has proven itself sufficiently to be
+released. However, because it has not had the exposure (and hence
+testing by users) that some other architectures have had, you may
+encounter a few bugs. Use our
+<ulink url="&url-bts;">Bug Tracking System</ulink> to report any
+problems; make sure to mention the fact that the bug is on the
+&arch-title; platform. It can be necessary to use the
+<ulink url="&url-list-subscribe;">debian-&architecture; mailing list</ulink>
+as well.
+
+</para>
+
+  </sect2>
+
+<!-- supported cpu docs -->
+&supported-alpha.xml;
+&supported-arm.xml;
+&supported-hppa.xml;
+&supported-i386.xml;
+&supported-ia64.xml;  <!-- FIXME: currently missing -->
+&supported-m68k.xml;
+&supported-mips.xml;
+&supported-mipsel.xml;
+&supported-powerpc.xml;
+&supported-s390.xml;
+&supported-sparc.xml;
+
+  <sect2 id="gfx" arch="not-s390"><title>Graphics Card</title>
+
+<para arch="i386">
+
+You should be using a VGA-compatible display interface for the console
+terminal. Nearly every modern display card is compatible with
+VGA. Ancient standards such CGA, MDA, or HGA should also work,
+assuming you do not require X11 support.  Note that X11 is not used
+during the installation process described in this document.
+
+</para><para>
+
+Debian's support for graphical interfaces is determined by the
+underlying support found in XFree86's X11 system.  Most AGP, PCI and
+PCIe video cards work under XFree86.  Details on supported graphics
+buses, cards, monitors, and pointing devices can be found at
+<ulink url="&url-xfree86;"></ulink>.  Debian &release; ships
+with XFree86 version &x11ver;.
+
+</para><para arch="mips">
+
+The XFree86 X11 window system is only supported on the SGI Indy.  The
+Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports
+VGA emulation or Linux framebuffer on a selected range of graphics cards.
+A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for
+the BCM91250A is available.
+
+</para><para arch="mipsel">
+
+The XFree86 X11 window system is supported on some DECstation models.  The
+Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports
+VGA emulation or Linux framebuffer on a selected range of graphics cards.
+A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for
+the BCM91250A is available.
+
+</para>
+
+  </sect2>
+
+  <sect2 arch="i386" id="laptops"><title>Laptops</title>
+<para>
+
+Laptops are also supported.  Laptops are often specialized or contain
+proprietary hardware.  To see if your particular laptop works well
+with GNU/Linux, see the
+<ulink url="&url-x86-laptop;">Linux Laptop pages</ulink>
+
+</para>
+   </sect2>
+
+
+  <sect2 condition="defaults-smp">
+<title>Multiple Processors</title>
+
+<para>
+
+Multi-processor support &mdash; also called <quote>symmetric multi-processing</quote>
+or SMP &mdash; is supported for this architecture.  The standard Debian
+&release; kernel image was compiled with SMP support.  This should not
+prevent installation, since the SMP kernel should boot on non-SMP systems;
+the kernel will simply cause a bit more overhead.
+
+</para><para>
+
+In order to optimize the kernel for single CPU systems, you'll have to
+replace the standard Debian kernel.  You can find a discussion of how
+to do this in <xref linkend="kernel-baking"/>.  At this time
+(kernel version &kernelversion;) the way you disable SMP is to deselect
+<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote>
+section of the kernel config.
+
+</para>
+
+  </sect2>
+
+
+  <sect2 condition="supports-smp">
+ <title>Multiple Processors</title>
+<para>
+
+Multi-processor support &mdash; also called <quote>symmetric
+multi-processing</quote> or SMP &mdash; is supported for this architecture.
+However, the standard Debian &release; kernel image does not support
+SMP.  This should not prevent installation, since the standard,
+non-SMP kernel should boot on SMP systems; the kernel will simply use
+the first CPU.
+
+</para><para>
+
+In order to take advantage of multiple processors, you'll have to
+replace the standard Debian kernel.  You can find a discussion of how
+to do this in <xref linkend="kernel-baking"/>.  At this time
+(kernel version &kernelversion;) the way you enable SMP is to select
+<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote>
+section of the kernel config.
+
+</para>
+  </sect2>
+
+  <sect2 condition="supports-smp-sometimes">
+ <title>Multiple Processors</title>
+<para>
+
+Multi-processor support &mdash; also called <quote>symmetric
+multi-processing</quote> or SMP &mdash; is supported for this architecture,
+and is supported by a precompiled Debian kernel image. Depending on your
+install media, this SMP-capable kernel may or may not be installed by
+default. This should not prevent installation, since the standard,
+non-SMP kernel should boot on SMP systems; the kernel will simply use
+the first CPU.
+
+</para><para>
+
+In order to take advantage of multiple processors, you should check to see
+if a kernel package that supports SMP is installed, and if not, choose an
+appropriate kernel package.
+
+You can also build your own customized kernel to support SMP. You can find
+a discussion of how to do this in <xref linkend="kernel-baking"/>.  At this
+time (kernel version &kernelversion;) the way you enable SMP is to select
+<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote>
+section of the kernel config.
+
+</para>
+  </sect2>
+ </sect1>
diff --git a/fi/hardware/hardware.xml b/fi/hardware/hardware.xml
new file mode 100644
index 000000000..166cb9ab1
--- /dev/null
+++ b/fi/hardware/hardware.xml
@@ -0,0 +1,21 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+<chapter id="hardware-req">
+ <title>System Requirements</title>
+
+<para>
+
+This section contains information about what hardware you need to get
+started with Debian.  You will also find links to further information
+about hardware supported by GNU and Linux.
+
+</para>
+
+&hardware-supported.xml;
+&installation-media.xml;
+&supported-peripherals.xml;
+&memory-disk-requirements.xml;
+&network-cards.xml;
+
+</chapter>
diff --git a/fi/hardware/installation-media.xml b/fi/hardware/installation-media.xml
new file mode 100644
index 000000000..d9b182897
--- /dev/null
+++ b/fi/hardware/installation-media.xml
@@ -0,0 +1,311 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+ <sect1 id="installation-media">
+ <title>Installation Media</title>
+
+<para>
+
+This section will help you determine which different media types you can use to
+install Debian. For example, if you have a floppy disk drive on your machine,
+it can be used to install Debian. There is a whole chapter devoted media,
+<xref linkend="install-methods"/>, which lists the advantages and
+disadvantages of each media type. You may want to refer back to this page once
+you reach that section.
+
+</para>
+
+  <sect2 condition="supports-floppy-boot"><title>Floppies</title>
+<para>
+
+In some cases, you'll have to do your first boot from floppy disks.
+Generally, all you will need is a
+high-density (1440 kilobytes) 3.5 inch floppy drive.
+
+</para><para arch="powerpc">
+
+For CHRP, floppy support is currently broken.
+
+</para>
+  </sect2>
+
+  <sect2><title>CD-ROM/DVD-ROM</title>
+
+<note><para>
+
+Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both
+CD-ROMs and DVD-ROMs, because both technologies are really
+the same from the operating system's point of view, except for some very
+old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI.
+
+</para></note><para>
+
+CD-ROM based installation is supported for some architectures.
+On machines which support bootable CD-ROMs, you should be able to do a
+completely
+<phrase arch="not-s390">floppy-less</phrase>
+<phrase arch="s390">tape-less</phrase>
+installation.  Even if your system doesn't
+support booting from a CD-ROM, you can use the CD-ROM in conjunction
+with the other techniques to install your system, once you've booted
+up by other means; see <xref linkend="boot-installer"/>.
+
+</para><para arch="i386">
+
+Both SCSI and IDE/ATAPI CD-ROMs are supported.  In addition, all
+non-standard CD interfaces supported by Linux are supported by the
+boot disks (such as Mitsumi and Matsushita drives).  However, these
+models might require special boot parameters or other massaging to get
+them to work, and booting off these non-standard interfaces is
+unlikely.  The <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink>
+contains in-depth information on using CD-ROMs with Linux.
+
+</para><para arch="i386">
+
+USB CD-ROM drives are also supported, as are FireWire devices that
+are supported by the ohci1394 and sbp2 drivers.
+
+</para><para arch="alpha">
+
+Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long
+as the controller is supported by the SRM console.  This rules out many
+add-on controller cards, but most integrated IDE and SCSI chips and
+controller cards that were provided by the manufacturer can be expected
+to work.  To find out whether your device is supported from the SRM
+console, see the <ulink url="&url-srm-howto;">SRM HOWTO</ulink>.
+
+</para><para arch="arm">
+
+IDE/ATAPI CD-ROMs are supported on all ARM machines.
+On RiscPCs, SCSI CD-ROMs are also supported.
+
+</para><para arch="mips">
+
+On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive
+capable of working with a logical blocksize of 512 bytes. Many of the
+SCSI CD-DROM drives sold for the PC market do not have this
+capability. If your CD-ROM drive has a jumper labeled
+<quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the
+<quote>Unix</quote> or <quote>512</quote> position.
+To start the install, simply choose the <quote>System installation</quote>
+entry in the firmware.  The Broadcom BCM91250A supports standard IDE devices,
+including CD-ROM drives, but CD images for this platform are currently not
+provided because the firmware doesn't recognize CD drives.
+
+</para><para arch="mipsel">
+
+On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive
+capable of working with a logical blocksize of 512 bytes. Many of the
+SCSI CD-DROM drives sold for the PC market do not have this capability.
+If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or
+<quote>512/2048</quote>, place it in the <quote>Unix</quote> or
+<quote>512</quote> position.
+
+</para><para arch="mipsel">
+
+CD 1 contains the installer for the r3k-kn02 subarchitecture
+(the R3000-based DECstations 5000/1xx and 5000/240 as well as
+the R3000-based Personal DECstation models), CD 2 the
+installer for the r4k-kn04 subarchitecture (the R4x00-based
+DECstations 5000/150 and 5000/260 as well as the Personal DECstation
+5000/50).
+
+</para><para arch="mipsel">
+
+To boot from CD, issue the command <userinput>boot
+<replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput>
+on the firmware prompt, where <replaceable>#</replaceable> is the
+number of the TurboChannel device from which to boot (3 on most
+DECstations) and <replaceable>id</replaceable> is the SCSI ID of the
+CD-ROM drive.  If you need to pass additional parameters, they can
+optionally be appended with the following syntax:
+
+</para><para arch="mipsel">
+
+<userinput>boot
+<replaceable>#</replaceable>/rz<replaceable>id</replaceable>
+param1=value1 param2=value2 ...</userinput>
+
+</para>
+  </sect2>
+
+  <sect2><title>Hard Disk</title>
+
+<para>
+
+Booting the installation system directly from a hard disk is another option
+for many architectures. This will require some other operating system
+to load the installer onto the hard disk.
+
+</para><para arch="m68k">
+
+In fact, installation from your local disk is the preferred
+installation technique for most &architecture; machines.
+
+</para><para arch="sparc">
+
+Although the &arch-title; does not allow booting from SunOS
+(Solaris), you can install from a SunOS partition (UFS slices).
+
+</para>
+  </sect2>
+
+  <sect2 condition="bootable-usb"><title>USB Memory Stick</title>
+
+<para>
+
+Many Debian boxes need their floppy and/or CD-ROM drives only for
+setting up the system and for rescue purposes. If you operate some
+servers, you will probably already have thought about omitting those
+drives and using an USB memory stick for installing and (when
+necessary) for recovering the system. This is also useful for small
+systems which have no room for unnecessary drives.
+
+</para>
+  </sect2>
+
+  <sect2><title>Network</title>
+
+<para condition="supports-tftp">
+
+You can also <emphasis>boot</emphasis> your system over the network.
+<phrase arch="mips">This is the preferred installation technique for
+Mips.</phrase>
+
+</para><para condition="supports-nfsroot">
+
+Diskless installation, using network booting from a local area network
+and NFS-mounting of all local filesystems, is another option.
+
+</para><para>
+
+After the operating system kernel is installed, you can install the
+rest of your system via any sort of network connection (including
+PPP after installation of the base system), via FTP or HTTP.
+
+</para>
+  </sect2>
+
+  <sect2><title>Un*x or GNU system</title>
+
+<para>
+
+If you are running another Unix-like system, you could use it to install
+&debian; without using the &d-i; described in the rest of the
+manual. This kind of install may be useful for users with otherwise
+unsupported hardware or on hosts which can't afford downtime.  If you
+are interested in this technique, skip to the <xref
+linkend="linux-upgrade"/>.
+
+</para>
+  </sect2>
+
+  <sect2><title>Supported Storage Systems</title>
+
+<para>
+
+The Debian boot disks contain a kernel which is built to maximize the
+number of systems it runs on.  Unfortunately, this makes for a larger
+kernel, which includes many drivers that won't be used for your
+machine (see <xref linkend="kernel-baking"/> to learn how to
+build your own kernel).  Support for the widest possible range of
+devices is desirable in general, to ensure that Debian can be
+installed on the widest array of hardware.
+
+</para><para arch="i386">
+
+Generally, the Debian installation system includes support for floppies,
+IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and
+drives, USB, and FireWire.  The file systems supported include FAT,
+Win-32 FAT extensions (VFAT), and NTFS, among others.
+
+</para><para arch="i386">
+
+The disk interfaces that emulate the <quote>AT</quote> hard disk interface
+which are often called MFM, RLL, IDE, or ATA are supported.  Very old 8 bit
+hard disk controllers used in the IBM XT computer are supported only
+as a module. SCSI disk controllers from many different manufacturers
+are supported. See the
+<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>
+for more details.
+
+</para><para arch="m68k">
+
+Pretty much all storage systems supported by the Linux kernel are
+supported by the Debian installation system.  Note that the current
+Linux kernel does not support floppies on the Macintosh at all, and
+the Debian installation system doesn't support floppies for Amigas.
+Also supported on the Atari is the Macintosh HFS system, and AFFS as a
+module.  Macs support the Atari (FAT) file system.  Amigas support the
+FAT file system, and HFS as a module.
+
+</para><para arch="sparc">
+
+Any storage system supported by the Linux kernel is also supported by
+the boot system. The following SCSI drivers are supported in the default
+kernel:
+
+<itemizedlist>
+<listitem><para>
+
+Sparc ESP
+
+</para></listitem>
+<listitem><para>
+
+PTI Qlogic,ISP
+
+</para></listitem>
+<listitem><para>
+
+Adaptec AIC7xxx
+
+</para></listitem>
+<listitem><para>
+
+NCR and Symbios 53C8XX
+
+</para></listitem>
+</itemizedlist>
+
+IDE systems (such as the UltraSPARC 5) are also supported. See
+<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink>
+for more information on SPARC hardware supported by the Linux kernel.
+
+</para><para arch="alpha">
+
+Any storage system supported by the Linux kernel is also supported by
+the boot system.  This includes both SCSI and IDE disks.  Note, however,
+that on many systems, the SRM console is unable to boot from IDE drives,
+and the Jensen is unable to boot from floppies.  (see
+<ulink url="&url-jensen-howto;"></ulink>
+for more information on booting the Jensen)
+
+</para><para arch="powerpc">
+
+Any storage system supported by the Linux kernel is also supported by
+the boot system.  Note that the current Linux kernel does not support
+floppies on CHRP systems at all.
+
+</para><para arch="hppa">
+
+Any storage system supported by the Linux kernel is also supported by
+the boot system.  Note that the current Linux kernel does not support
+the floppy drive.
+
+</para><para arch="mips">
+
+Any storage system supported by the Linux kernel is also supported by
+the boot system.
+
+</para><para arch="s390">
+
+Any storage system supported by the Linux kernel is also supported by
+the boot system.  This means that FBA and ECKD DASDs are supported with
+the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl).
+
+</para>
+
+  </sect2>
+
+ </sect1>
diff --git a/fi/hardware/memory-disk-requirements.xml b/fi/hardware/memory-disk-requirements.xml
new file mode 100644
index 000000000..e048007b8
--- /dev/null
+++ b/fi/hardware/memory-disk-requirements.xml
@@ -0,0 +1,47 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28672 untranslated -->
+
+ <sect1 id="memory-disk-requirements">
+ <title>Memory and Disk Space Requirements</title>
+
+<para>
+
+You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk
+space. For a minimal console-based system (all standard packages),
+250MB is required. If you want to install a reasonable amount of
+software, including the X Window System, and some development programs
+and libraries, you'll need at least 400MB. For a more or less complete
+desktop system, you'll need a few gigabytes.
+
+</para><para arch="m68k">
+
+On the Amiga the size of FastRAM is relevant towards the total memory
+requirements.  Also, using Zorro cards with 16-bit RAM is not
+supported; you'll need 32-bit RAM.  The <command>amiboot</command>
+program can be used to disable 16-bit RAM; see the
+<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink>.  Recent kernels should
+disable 16-bit RAM automatically.
+
+</para><para arch="m68k">
+
+On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux.
+Many users have reported problems running the kernel itself in Fast
+RAM, so the Atari bootstrap will place the kernel in ST-RAM. The
+minimum requirement for ST-RAM is 2 MB. You will need an additional
+12 MB or more of TT-RAM.
+
+</para><para arch="m68k">
+
+On the Macintosh, care should be taken on machines with RAM-based
+video (RBV). The RAM segment at physical address 0 is used as screen
+memory, making the default load position for the kernel unavailable.
+The alternate RAM segment used for kernel and RAMdisk must be at least
+4 MB.
+
+</para><para arch="m68k">
+
+<emphasis condition="FIXME">FIXME: is this still true?</emphasis>
+
+</para>
+
+ </sect1>
diff --git a/fi/hardware/network-cards.xml b/fi/hardware/network-cards.xml
new file mode 100644
index 000000000..d296a821e
--- /dev/null
+++ b/fi/hardware/network-cards.xml
@@ -0,0 +1,214 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28672 untranslated -->
+
+ <sect1 id="network-cards">
+ <title>Network Connectivity Hardware</title>
+
+<para arch="i386">
+
+<!-- last updated for kernel-image_2.0.36-2 -->
+
+Most PCI and many older ISA network cards are supported.
+Some network interface cards are not supported by most Debian
+installation disks, such as AX.25 cards and protocols;
+NI16510 EtherBlaster cards; Schneider &amp; Koch G16 cards;
+and the Zenith Z-Note built-in network card. Microchannel (MCA) network
+cards are not supported by the standard installation system, but see
+<ulink url="&url-linux-mca;">Linux on MCA</ulink> for some (old)
+instructions.
+FDDI networks are also not supported by the installation disks, both
+cards and protocols.
+
+<!-- missing-doc FIXME You can create a custom kernel which supports an
+otherwise unsupported card and then substitute in the installer (see
+<xref linkend="rescue-replace-kernel"/>). -->
+
+</para><para arch="i386">
+
+As for ISDN, the D-channel protocol for the (old) German 1TR6 is not
+supported; Spellcaster BRI ISDN boards are also not supported by the
+&d-i;.
+
+</para>
+
+<para arch="m68k">
+
+Any network interface card (NIC) supported by the Linux kernel should
+also be supported by the boot disks.  You may need to load your
+network driver as a module.  Again, see
+<ulink url="&url-m68k-faq;"></ulink> for complete details.
+
+</para>
+
+<para arch="sparc">
+
+The following network interface cards (NICs) are supported from the bootable
+kernel directly:
+
+<itemizedlist>
+ <listitem><para>
+
+Sun LANCE
+
+
+</para></listitem>
+ <listitem><para>
+
+Sun Happy Meal
+
+
+</para></listitem>
+</itemizedlist>
+
+</para><para arch="sparc">
+
+The following network interface cards are supported as modules.  They
+can be enabled once the drivers are installed during the setup.
+However, due to the magic of OpenPROM, you still should be able to
+boot from these devices:
+
+<itemizedlist>
+ <listitem><para>
+
+Sun BigMAC
+
+
+</para></listitem>
+ <listitem><para>
+
+Sun QuadEthernet
+
+</para></listitem>
+ <listitem><para>
+
+MyriCOM Gigabit Ethernet
+
+</para></listitem>
+</itemizedlist>
+
+</para><para arch="alpha">
+
+Any network interface card (NIC) supported by the Linux kernel should
+also be supported by the boot disks.  You may need to load your
+network driver as a module.
+
+</para><para arch="powerpc">
+
+Any network interface card (NIC) supported by the Linux kernel should
+also be supported by the boot disks.  You may need to load your
+network driver as a module.
+
+</para><para arch="hppa">
+
+Any network interface card (NIC) supported by the Linux kernel should
+also be supported by the boot disks.  You may need to load your
+network driver as a module.
+
+</para><para arch="ia64">
+
+Any network interface card (NIC) supported by the Linux kernel should
+also be supported by the boot disks.  You may need to load your
+network driver as a module.
+
+</para><para arch="mips">
+
+Any network interface card (NIC) supported by the Linux kernel should
+also be supported by the boot disks.  You may need to load your
+network driver as a module.
+
+</para><para arch="mipsel">
+
+Due to kernel limitations only the onboard network interfaces on
+DECstations are supported, TurboChannel option network cards currently
+do not work.
+
+</para><para arch="s390">
+
+Any network interface card (NIC) supported by the Linux kernel are
+also be supported by the boot disks.  All network drivers are compiled
+as modules so you need to load one first during the initial network
+setup. The list of supported network devices is:
+
+<itemizedlist>
+ <listitem><para>
+
+Channel to Channel (CTC) and ESCON connection (real or emulated)
+
+</para></listitem>
+ <listitem><para>
+
+OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)
+
+</para></listitem>
+<listitem><para>
+
+Inter-User Communication Vehicle (IUCV) &mdash; available for VM guests only
+
+</para></listitem>
+<listitem><para>
+
+OSA-Express in QDIO mode, HiperSockets and Guest-LANs
+
+</para></listitem>
+</itemizedlist>
+
+</para>
+
+<para arch="arm">
+
+The following network interface cards are supported directly by the
+boot disks on NetWinder and CATS machines:
+
+<itemizedlist>
+ <listitem><para>
+
+    PCI-based NE2000
+
+
+</para></listitem>
+ <listitem><para>
+
+    DECchip Tulip
+
+</para></listitem>
+</itemizedlist>
+
+</para><para arch="arm">
+
+The following network interface cards are supported directly by the
+boot disks on RiscPCs:
+
+<itemizedlist>
+ <listitem><para>
+
+    Ether1
+
+</para></listitem>
+ <listitem><para>
+
+    Ether3
+
+</para></listitem>
+ <listitem><para>
+
+    EtherH
+
+</para></listitem>
+</itemizedlist>
+
+</para><para arch="arm">
+
+If your card is mentioned in the lists above, the complete installation
+can be carried out from the network with no need for CD-ROMs or floppy
+disks.
+
+</para><para arch="arm">
+
+Any other network interface card (NIC) supported by the Linux kernel
+should also be supported by the boot disks.  You may need to load your
+network driver as a module; this means that you will have to install
+the operating system kernel and modules using some other media.
+
+</para>
+
+ </sect1>
diff --git a/fi/hardware/supported-peripherals.xml b/fi/hardware/supported-peripherals.xml
new file mode 100644
index 000000000..f3ab5db99
--- /dev/null
+++ b/fi/hardware/supported-peripherals.xml
@@ -0,0 +1,187 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 29467 untranslated -->
+
+ <sect1 id="supported-peripherals">
+ <title>Peripherals and Other Hardware</title>
+<para arch="not-s390">
+
+Linux supports a large variety of hardware devices such as mice,
+printers, scanners, PCMCIA and USB devices.  However, most of these
+devices are not required while installing the system.
+
+</para><para arch="i386">
+
+USB hardware generally works fine, only some
+USB keyboards may require additional configuration
+(see <xref linkend="usb-keyboard-config"/>).
+
+</para><para arch="i386">
+
+Again, see the
+<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>
+to determine whether your specific hardware is supported by Linux.
+
+</para><para arch="s390">
+
+Package installations from XPRAM and tape are not supported by this
+system.  All packages that you want to install need to be available on a
+DASD or over the network using NFS, HTTP or FTP.
+
+</para><para arch="mips">
+
+The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64
+bit PCI slots as well as USB connectors.
+
+</para><para arch="mipsel">
+
+The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64
+bit PCI slots as well as USB connectors.  The Cobalt RaQ has no support for
+additional devices but the Qube has one PCI slot.
+
+</para>
+</sect1>
+
+ <sect1 arch="not-s390"><title>Purchasing Hardware Specifically for GNU/Linux</title>
+
+<para>
+
+There are several vendors, who ship systems with Debian or other
+distributions of GNU/Linux
+<ulink url="&url-pre-installed;">pre-installed</ulink>. You might pay more
+for the privilege, but it does buy a level of peace of mind, since you can
+be sure that the hardware is well-supported by GNU/Linux.
+
+</para><para arch="m68k">
+
+Unfortunately, it's quite rare to find any vendor shipping
+new &arch-title; machines at all.
+
+</para><para arch="i386">
+
+If you do have to buy a machine with Windows bundled, carefully read
+the software license that comes with Windows; you may be able to
+reject the license and obtain a rebate from your vendor.  Searching
+the Internet for <quote>windows refund</quote> may get you some useful
+information to help with that.
+
+</para><para>
+
+Whether or not you are purchasing a system with Linux bundled, or even
+a used system, it is still important to check that your hardware is
+supported by the Linux kernel.  Check if your hardware is listed in
+the references found above.  Let your salesperson (if any) know that
+you're shopping for a Linux system.  Support Linux-friendly hardware
+vendors.
+
+</para>
+
+  <sect2><title>Avoid Proprietary or Closed Hardware</title>
+<para>
+
+Some hardware manufacturers simply won't tell us how to write drivers
+for their hardware. Others won't allow us access to the documentation
+without a non-disclosure agreement that would prevent us from
+releasing the Linux source code.
+
+</para><para arch="m68k">
+
+Another example is the proprietary hardware in the older
+Macintosh line. In fact, no specifications or documentation have ever
+been released for any Macintosh hardware, most notably the ADB
+controller (used by the mouse and keyboard), the floppy controller,
+and all acceleration and CLUT manipulation of the video hardware
+(though we do now support CLUT manipulation on nearly all internal
+video chips).  In a nutshell, this explains why the Macintosh Linux
+port lags behind other Linux ports.
+
+</para><para>
+
+Since we haven't been granted access to the documentation on these
+devices, they simply won't work under Linux. You can help by asking
+the manufacturers of such hardware to release the documentation. If
+enough people ask, they will realize that the free software community
+is an important market.
+
+</para>
+</sect2>
+
+
+  <sect2 arch="i386"><title>Windows-specific Hardware</title>
+<para>
+
+A disturbing trend is the proliferation of Windows-specific modems and
+printers. In some cases these are specially designed to be operated by
+the Microsoft Windows operating system and bear the legend <quote>WinModem</quote>
+or <quote>Made especially for Windows-based computers</quote>. This
+is generally done by removing the embedded processors of the hardware
+and shifting the work they do over to a Windows driver that is run by
+your computer's main CPU. This strategy makes the hardware less
+expensive, but the savings are often <emphasis>not</emphasis> passed on to the
+user and this hardware may even be more expensive than equivalent
+devices that retain their embedded intelligence.
+
+</para><para>
+
+You should avoid Windows-specific hardware for two reasons. The first
+is that the manufacturers do not generally make the resources
+available to write a Linux driver. Generally, the hardware and
+software interface to the device is proprietary, and documentation is
+not available without a non-disclosure agreement, if it is available
+at all. This precludes its being used for free software, since free
+software writers disclose the source code of their programs. The
+second reason is that when devices like these have had their embedded
+processors removed, the operating system must perform the work of the
+embedded processors, often at <emphasis>real-time</emphasis> priority,
+and thus the CPU is not available to run your programs while it is
+driving these devices. Since the typical Windows user does not
+multi-process as intensively as a Linux user, the manufacturers hope
+that the Windows user simply won't notice the burden this hardware
+places on their CPU.  However, any multi-processing operating system,
+even Windows 2000 or XP, suffers from degraded performance when
+peripheral manufacturers skimp on the embedded processing power of
+their hardware.
+
+</para><para>
+
+You can help this situation by encouraging these manufacturers to
+release the documentation and other resources necessary for us to
+program their hardware, but the best strategy is simply to avoid this
+sort of hardware until it is listed as working in the
+<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>.
+
+</para>
+</sect2>
+
+
+  <sect2 id="Parity-RAM">
+  <title>Fake or <quote>Virtual</quote> Parity RAM</title>
+<para>
+
+If you ask for Parity RAM in a computer store, you'll probably get
+<emphasis>virtual parity</emphasis> memory modules instead of
+<emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often
+(but not always) be distinguished because they only have one more chip
+than an equivalent non-parity SIMM, and that one extra chip is smaller
+than all the others. Virtual-parity SIMMs work exactly like non-parity
+memory.  They can't tell you when you have a single-bit RAM error the
+way true-parity SIMMs do in a motherboard that implements
+parity. Don't ever pay more for a virtual-parity SIMM than a
+non-parity one. Do expect to pay a little more for true-parity SIMMs,
+because you are actually buying one extra bit of memory for every 8
+bits.
+
+</para><para>
+
+If you want complete information on &arch-title; RAM issues, and what
+is the best RAM to buy, see the
+<ulink url="&url-pc-hw-faq;">PC Hardware FAQ</ulink>.
+
+</para><para arch="alpha">
+
+Most, if not all, Alpha systems require true-parity RAM.
+
+</para>
+
+  </sect2>
+
+ </sect1>
diff --git a/fi/hardware/supported/alpha.xml b/fi/hardware/supported/alpha.xml
new file mode 100644
index 000000000..02e0ad4be
--- /dev/null
+++ b/fi/hardware/supported/alpha.xml
@@ -0,0 +1,457 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="alpha" id="alpha-cpus"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+Complete information regarding supported DEC Alphas can be found at
+<ulink url="&url-alpha-howto;">Linux Alpha HOWTO</ulink>.  The
+purpose of this section is to describe the systems supported
+by the boot disks.
+
+</para><para>
+
+Alpha machines are subdivided into different system types because there
+are a number of generations of motherboard and supporting chipsets.
+Different systems (<quote>sub-architectures</quote>) often have radically
+different engineering and capabilities.  Therefore, the process of
+installing and, more to the point, booting, can vary from system to system.
+
+</para><para>
+
+The following table lists the system types supported by the Debian
+installation system.  The table also indicates the <emphasis>code
+name</emphasis> for these system types.  You'll need to know this code
+name when you actually begin the installation process:
+
+</para>
+
+<informaltable>
+<tgroup cols="4">
+<colspec colname="c1"/>
+<colspec colname="c2"/>
+<colspec colname="c3"/>
+<colspec colname="c4"/>
+<thead>
+<row>
+  <entry namest="c1" nameend="c2">Hardware Type</entry>
+  <entry>Aliases</entry><entry>MILO image</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry morerows="3">ALCOR</entry>
+  <entry>AlphaStation 500 5/266.300</entry>
+  <entry>Maverick</entry>
+  <entry>alcor</entry>
+</row><row>
+  <entry>AlphaStation 500 5/333...500</entry>
+  <entry>Bret</entry>
+  <entry>alcor</entry>
+</row><row>
+  <entry>AlphaStation 600/266...300</entry>
+  <entry>Alcor</entry>
+  <entry>alcor</entry>
+</row><row>
+  <entry>AlphaStation 600/300...433</entry>
+  <entry>XLT</entry>
+  <entry>xlt</entry>
+</row>
+
+<row>
+  <entry>BOOK1</entry>
+  <entry>AlphaBook1 (laptop)</entry>
+  <entry>Alphabook1/Burns</entry>
+  <entry>book1</entry>
+</row>
+
+<row>
+  <entry morerows="7">AVANTI</entry>
+  <entry>AlphaStation 200 4/100...166</entry>
+  <entry>Mustang</entry>
+  <entry>avanti</entry>
+</row><row>
+  <entry>AlphaStation 200 4/233</entry>
+  <entry>Mustang+</entry>
+  <entry>avanti</entry>
+</row><row>
+  <entry>AlphaStation 205 4/133...333</entry>
+  <entry>LX3</entry>
+  <entry>avanti</entry>
+</row><row>
+  <entry>AlphaStation 250 4/300</entry>
+  <entry>M3+</entry>
+  <entry>avanti</entry>
+</row><row>
+  <entry>AlphaStation 255 4/133...333</entry>
+  <entry>LX3+</entry>
+  <entry>avanti</entry>
+</row><row>
+  <entry>AlphaStation 300 4/266</entry>
+  <entry>Melmac</entry>
+  <entry>avanti</entry>
+</row><row>
+  <entry>AlphaStation 400 4/166</entry>
+  <entry>Chinet</entry>
+  <entry>avanti</entry>
+</row><row>
+  <entry>AlphaStation 400 4/233...300</entry>
+  <entry>Avanti</entry>
+  <entry>avanti</entry>
+</row>
+
+<row>
+  <entry morerows="3">EB164</entry>
+  <entry>AlphaPC164</entry>
+  <entry>PC164</entry>
+  <entry>pc164</entry>
+</row><row>
+  <entry>AlphaPC164-LX</entry>
+  <entry>LX164</entry>
+  <entry>lx164</entry>
+</row><row>
+  <entry>AlphaPC164-SX</entry>
+  <entry>SX164</entry>
+  <entry>sx164</entry>
+</row><row>
+  <entry>EB164</entry>
+  <entry>EB164</entry>
+  <entry>eb164</entry>
+</row>
+
+<row>
+  <entry morerows="2">EB64+</entry>
+  <entry>AlphaPC64</entry>
+  <entry>Cabriolet</entry>
+  <entry>cabriolet</entry>
+</row><row>
+  <entry>AlphaPCI64</entry>
+  <entry>Cabriolet</entry>
+  <entry>cabriolet</entry>
+</row><row>
+  <entry>EB64+</entry>
+  <entry>EB64+</entry>
+  <entry>eb64p</entry>
+</row>
+
+<row>
+  <entry morerows="1">EB66</entry>
+  <entry>EB66</entry>
+  <entry>EB66</entry>
+  <entry>eb66</entry>
+</row><row>
+  <entry>EB66+</entry>
+  <entry>EB66+</entry>
+  <entry>eb66p</entry>
+</row>
+
+<row>
+  <entry morerows="2">JENSEN</entry>
+  <entry>DEC 2000 Model 300(S)</entry>
+  <entry>Jensen</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>DEC 2000 Model 500</entry>
+  <entry>Culzen</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>DECpc 150</entry>
+  <entry>Jensen</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry morerows="7">MIATA</entry>
+  <entry>Personal WorkStation 433a</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row><row>
+  <entry>Personal WorkStation 433au</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row><row>
+  <entry>Personal WorkStation 466au</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row><row>
+  <entry>Personal WorkStation 500a</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row><row>
+  <entry>Personal WorkStation 500au</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row><row>
+  <entry>Personal WorkStation 550au</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row><row>
+  <entry>Personal WorkStation 600a</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row><row>
+  <entry>Personal WorkStation 600au</entry>
+  <entry>Miata</entry>
+  <entry>miata</entry>
+</row>
+
+<row>
+  <entry morerows="3">MIKASA</entry>
+  <entry>AlphaServer 1000 4/200</entry>
+  <entry>Mikasa</entry>
+  <entry>mikasa</entry>
+</row><row>
+  <entry>AlphaServer 1000 4/233..266</entry>
+  <entry>Mikasa+</entry>
+  <entry>mikasa</entry>
+</row><row>
+  <entry>AlphaServer 1000 5/300</entry>
+  <entry>Mikasa-Pinnacle</entry>
+  <entry>mikasa</entry>
+</row><row>
+  <entry>AlphaServer 1000 5/300</entry>
+  <entry>Mikasa-Primo</entry>
+  <entry>mikasa</entry>
+</row>
+
+<row>
+  <entry morerows="1">NAUTILUS</entry>
+  <entry>UP1000</entry>
+  <entry>Nautilus</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>UP1100</entry>
+  <entry>Galaxy-Train/Nautilus Jr.</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry morerows="1">NONAME</entry>
+  <entry>AXPpci33</entry>
+  <entry>Noname</entry>
+  <entry>noname</entry>
+</row><row>
+  <entry>UDB</entry>
+  <entry>Multia</entry>
+  <entry>noname</entry>
+</row>
+
+<row>
+  <entry morerows="6">NORITAKE</entry>
+  <entry>AlphaServer 1000A 4/233...266</entry>
+  <entry>Noritake</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 1000A 5/300</entry>
+  <entry>Noritake-Pinnacle</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 1000A 5/333...500</entry>
+  <entry>Noritake-Primo</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 800 5/333...500</entry>
+  <entry>Corelle</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaStation 600 A</entry>
+  <entry>Alcor-Primo</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>Digital Server 3300</entry>
+  <entry>Corelle</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>Digital Server 3300R</entry>
+  <entry>Corelle</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry>PLATFORM 2000</entry>
+  <entry>P2K</entry>
+  <entry>P2K</entry>
+  <entry>p2k</entry>
+</row>
+
+<row>
+  <entry morerows="4">RAWHIDE</entry>
+  <entry>AlphaServer 1200 5/xxx</entry>
+  <entry>Tincup/DaVinci</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 4000 5/xxx</entry>
+  <entry>Wrangler/Durango</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 4100 5/xxx</entry>
+  <entry>Dodge</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>Digital Server 5300</entry>
+  <entry>Tincup/DaVinci</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>Digital Server 7300</entry>
+  <entry>Dodge</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry morerows="5">RUFFIAN</entry>
+  <entry>DeskStation AlphaPC164-UX</entry>
+  <entry>Ruffian</entry>
+  <entry>ruffian</entry>
+</row><row>
+  <entry>DeskStation RPL164-2</entry>
+  <entry>Ruffian</entry>
+  <entry>ruffian</entry>
+</row><row>
+  <entry>DeskStation RPL164-4</entry>
+  <entry>Ruffian</entry>
+  <entry>ruffian</entry>
+</row><row>
+  <entry>DeskStation RPX164-2</entry>
+  <entry>Ruffian</entry>
+  <entry>ruffian</entry>
+</row><row>
+  <entry>DeskStation RPX164-4</entry>
+  <entry>Ruffian</entry>
+  <entry>ruffian</entry>
+</row><row>
+  <entry>Samsung AlphaPC164-BX</entry>
+  <entry>Ruffian</entry>
+  <entry>ruffian</entry>
+</row>
+
+<row>
+  <entry morerows="3">SABLE</entry>
+  <entry>AlphaServer 2000 4/xxx</entry>
+  <entry>Demi-Sable</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 2000 5/xxx</entry>
+  <entry>Demi-Gamma-Sable</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 2100 4/xxx</entry>
+  <entry>Sable</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer 2100 5/xxx</entry>
+  <entry>Gamma-Sable</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry>TAKARA</entry>
+  <entry>21164 PICMG SBC</entry>
+  <entry>Takara</entry>
+  <entry>takara</entry>
+</row>
+
+<row>
+  <entry morerows="3">TITAN</entry>
+  <entry>AlphaServer DS15</entry>
+  <entry>HyperBrick2</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer DS25</entry>
+  <entry>Granite</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer ES45</entry>
+  <entry>Privateer</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>UNKNOWN</entry>
+  <entry>Yukon</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry morerows="12">TSUNAMI</entry>
+  <entry>AlphaServer DS10</entry>
+  <entry>Webbrick</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer DS10L</entry>
+  <entry>Slate</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer DS20</entry>
+  <entry>Catamaran/Goldrush</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer DS20E</entry>
+  <entry>Goldrack</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer DS20L</entry>
+  <entry>Shark</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer ES40</entry>
+  <entry>Clipper</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>DP264</entry>
+  <entry>DP264</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>SMARTengine 21264 PCI/ISA SBC</entry>
+  <entry>Eiger</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>UNKNOWN</entry>
+  <entry>Warhol</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>UNKNOWN</entry>
+  <entry>Windjammer</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>UP2000</entry>
+  <entry>Swordfish</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>XP1000</entry>
+  <entry>Monet/Brisbane</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>XP900</entry>
+  <entry>Webbrick</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry morerows="1">WILDFIRE</entry>
+  <entry>AlphaServer GS160</entry>
+  <entry>Wildfire</entry>
+  <entry>N/A</entry>
+</row><row>
+  <entry>AlphaServer GS320</entry>
+  <entry>Wildfire</entry>
+  <entry>N/A</entry>
+</row>
+
+<row>
+  <entry>XL</entry>
+  <entry>XL-233...266</entry>
+  <entry>XL</entry>
+  <entry>xl</entry>
+</row>
+
+</tbody></tgroup></informaltable>
+
+<para>
+
+It is believed that Debian &releasename; supports installing on all
+alpha sub-architectures with the exception of the ARC-only Ruffian and
+XL sub-architectures and the Titan subarchitecture, which requires a
+change to the kernel compile options.
+
+</para>
+  </sect2>
diff --git a/fi/hardware/supported/arm.xml b/fi/hardware/supported/arm.xml
new file mode 100644
index 000000000..9ae4bef4e
--- /dev/null
+++ b/fi/hardware/supported/arm.xml
@@ -0,0 +1,95 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 25809 untranslated -->
+
+
+  <sect2 arch="arm"><title>CPU, Main Boards, and Video Support</title>
+
+<para>
+
+Each distinct ARM architecture requires its own kernel. Because of
+this the standard Debian distribution only supports installation on
+a number of the most common systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale.
+
+</para>
+
+<para>
+
+Most ARM CPUs may be run in either endian mode (big or little). However,
+almost every current system implementation uses little-endian mode.
+Debian currently only supports little-endian ARM systems.
+
+</para>
+
+<para>
+
+The commonly supported systems are
+
+<variablelist>
+<varlistentry>
+<term>Netwinder</term>
+<listitem><para>
+
+This is actually the name for the group of machines
+based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It
+comprises of machines like: Netwinder (possibly one of the most common ARM
+boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq
+personal server (cps, aka skiff).
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Bast</term>
+<listitem><para>
+
+This is a modern ARM 920 board with a 266MHz Samsung
+processor. It has integrated IDE, USB, Serial, Parallel, audio, video,
+flash and two ethernet ports. This system has a good bootloader which
+is also found on the CATS and Riscstation systems.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>RiscPC</term>
+<listitem><para>
+
+This machine is the oldest supported hardware: it was released
+in 1994. It has RISC OS in ROM, Linux can be booted from that OS using
+linloader. The RiscPC has a modular CPU card and typically has a 30MHz
+610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has
+integrated IDE, SVGA video, parallel port, single serial port, PS/2
+keyboard and proprietary mouse port. The proprietary module expansion
+bus allows for up to eight expansion cards to be fitted depending on
+configuration, several of these modules have Linux drivers.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Riscstation</term>
+<listitem><para>
+
+This is an inexpensive 56MHz 7500FE based machine with
+integrated video, IDE, PS/2 keyboard and mouse and two serial
+ports. Its lack of processing power was made up for by its price. It
+may be found in two configurations one with RISC OS and one with a
+simple bootloader.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>LART</term>
+<listitem><para>
+
+This is a modular open hardware platform intended to be built
+by enthusiasts. To be useful to install Debian it requires its KSB
+expansion board.
+
+</para></listitem>
+</varlistentry>
+</variablelist>
+
+</para>
+  </sect2>
diff --git a/fi/hardware/supported/hppa.xml b/fi/hardware/supported/hppa.xml
new file mode 100644
index 000000000..6f3c8c8ee
--- /dev/null
+++ b/fi/hardware/supported/hppa.xml
@@ -0,0 +1,17 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+  <sect2 arch="hppa"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+The are two major support <emphasis>&architecture;</emphasis> flavors:
+PA-RISC 1.1 and PA-RISC 2.0.  The PA-RISC 1.1 architecture is targeted
+at 32-bit processors whereas the 2.0 architecture is targeted to
+the 64-bit processors.  Some systems are able to run either kernel.
+In both cases, the userland is 32-bit.  There is the possibility of
+a 64-bit userland in the future.
+
+</para>
+  </sect2>
+
diff --git a/fi/hardware/supported/i386.xml b/fi/hardware/supported/i386.xml
new file mode 100644
index 000000000..725a5169b
--- /dev/null
+++ b/fi/hardware/supported/i386.xml
@@ -0,0 +1,37 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+  <sect2 arch="i386"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+Complete information concerning supported peripherals can be found at
+<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>.
+This section merely outlines the basics.
+
+</para>
+
+   <sect3><title>CPU</title>
+<para>
+
+Nearly all x86-based processors are supported; this includes AMD and
+VIA (former Cyrix) processors as well.  Also the new processors like
+Athlon XP and Intel P4 Xeon are supported.  However, Linux will
+<emphasis>not</emphasis> run on 286 or earlier processors.
+
+</para>
+   </sect3>
+
+   <sect3 id="bus"><title>I/O Bus</title>
+<para>
+
+The system bus is the part of the motherboard which allows the CPU to
+communicate with peripherals such as storage devices.  Your computer
+must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used
+in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL
+bus).
+
+</para>
+   </sect3>
+  </sect2>
+
diff --git a/fi/hardware/supported/ia64.xml b/fi/hardware/supported/ia64.xml
new file mode 100644
index 000000000..0dabd4a41
--- /dev/null
+++ b/fi/hardware/supported/ia64.xml
@@ -0,0 +1,3 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
diff --git a/fi/hardware/supported/m68k.xml b/fi/hardware/supported/m68k.xml
new file mode 100644
index 000000000..4de0bc0f8
--- /dev/null
+++ b/fi/hardware/supported/m68k.xml
@@ -0,0 +1,39 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+  <sect2 arch="m68k"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+Complete information concerning supported M68000 based
+(<emphasis>&architecture;</emphasis>) systems can be found at the
+<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink>.  This section merely
+outlines the basics.
+
+</para><para>
+
+The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged
+Memory Management Unit) and a FPU (floating-point unit).  This
+includes the 68020 with an external 68851 PMMU, the 68030, and better,
+and excludes the <quote>EC</quote> line of 680x0 processors.  See the
+<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink> for complete details.
+
+</para><para>
+
+There are four major flavors of supported
+<emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh
+and VME machines.  Amiga and Atari were the first two systems to which
+Linux was ported; in keeping, they are also the two most
+well-supported Debian ports.  The Macintosh line is supported
+incompletely, both by Debian and by the Linux kernel; see
+<ulink url="&url-m68k-mac;">Linux m68k for Macintosh</ulink> for project
+status and supported hardware.  The BVM and Motorola single board
+VMEbus computers are the most recent addition to the list of machines
+supported by Debian.  Ports to other &architecture; architectures,
+such as the Sun3 architecture and NeXT black box, are underway but not
+yet supported by Debian.
+
+</para>
+  </sect2>
+
+
+
diff --git a/fi/hardware/supported/mips.xml b/fi/hardware/supported/mips.xml
new file mode 100644
index 000000000..7ea1a2bf7
--- /dev/null
+++ b/fi/hardware/supported/mips.xml
@@ -0,0 +1,52 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 22939 untranslated -->
+
+
+  <sect2 arch="mips"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+Debian on &arch-title; currently supports two subarchitectures:
+
+<itemizedlist>
+<listitem><para>
+
+SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and
+Challenge S.  Since these machines are very similar, whenever this document
+refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well.
+
+</para></listitem>
+<listitem><para>
+
+Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from
+Broadcom based on their SiByte processor family.
+
+</para></listitem>
+</itemizedlist>
+
+Complete information regarding supported mips/mipsel machines can be found
+at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>.  In the
+following, only the systems supported by the Debian installer will be
+covered.  If you are looking for support for other subarchitectures, please
+contact the <ulink url="&url-list-subscribe;">
+debian-&architecture; mailing list</ulink>.
+
+</para>
+
+   <sect3><title>CPU</title>
+<para>
+
+On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000
+processors are supported by the Debian installation system on big endian
+MIPS.  The Broadcom BCM91250A evaluation board comes with an SB1250 chip with
+two SB-1 cores which are supported in SMP mode by this installer.
+
+</para><para>
+
+Some MIPS machines can be operated in both big and little endian mode.  For
+little endian MIPS, please read the documentation for the mipsel
+architecture.
+
+</para>
+   </sect3>
+  </sect2>
+
diff --git a/fi/hardware/supported/mipsel.xml b/fi/hardware/supported/mipsel.xml
new file mode 100644
index 000000000..63d5a5bc1
--- /dev/null
+++ b/fi/hardware/supported/mipsel.xml
@@ -0,0 +1,149 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="mipsel"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+Debian on &arch-title; currently supports three subarchitectures:
+
+<itemizedlist>
+<listitem><para>
+
+DECstation: various models of the DECstation are supported.
+
+</para></listitem>
+<listitem><para>
+
+Cobalt Microserver: only MIPS based Cobalt machines are covered here.
+This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway
+Microserver.
+
+</para></listitem>
+<listitem><para>
+
+Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from
+Broadcom based on their SiByte processor family.
+
+</para></listitem>
+</itemizedlist>
+
+Complete information regarding supported mips/mipsel machines can be found
+at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>.  In the
+following, only the systems supported by the Debian installer will be
+covered.  If you are looking for support for other subarchitectures, please
+contact the <ulink url="&url-list-subscribe;">
+debian-&architecture; mailing list</ulink>.
+
+</para>
+
+   <sect3><title>CPU/Machine types</title>
+
+<para>
+
+Currently only DECstations with R3000 and R4000/R4400 CPUs are
+supported by the Debian installation system on little endian MIPS.
+The Debian installation system works on the following machines:
+
+</para><para>
+
+<informaltable>
+<tgroup cols="4">
+<thead>
+<row>
+  <entry>System Type</entry><entry>CPU</entry><entry>Code-name</entry>
+  <entry>Debian subarchitecture</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry>DECstation 5000/1xx</entry>
+  <entry>R3000</entry>
+  <entry>3MIN</entry>
+  <entry>r3k-kn02</entry>
+</row><row>
+  <entry>DECstation 5000/150</entry>
+  <entry>R4000</entry>
+  <entry>3MIN</entry>
+  <entry>r4k-kn04</entry>
+</row><row>
+  <entry>DECstation 5000/200</entry>
+  <entry>R3000</entry>
+  <entry>3MAX</entry>
+  <entry>r3k-kn02</entry>
+</row><row>
+  <entry>DECstation 5000/240</entry>
+  <entry>R3000</entry>
+  <entry>3MAX+</entry>
+  <entry>r3k-kn02</entry>
+</row><row>
+  <entry>DECstation 5000/260</entry>
+  <entry>R4400</entry>
+  <entry>3MAX+</entry>
+  <entry>r4k-kn04</entry>
+</row><row>
+  <entry>Personal DECstation 5000/xx</entry>
+  <entry>R3000</entry>
+  <entry>Maxine</entry>
+  <entry>r3k-kn02</entry>
+</row><row>
+  <entry>Personal DECstation 5000/50</entry>
+  <entry>R4000</entry>
+  <entry>Maxine</entry>
+  <entry>r4k-kn04</entry>
+</row>
+</tbody></tgroup></informaltable>
+
+</para><para>
+
+All Cobalt machines are supported which have a serial console (which is
+needed for the installation).
+
+</para><para>
+
+The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two
+SB-1 cores which are supported in SMP mode by this installer.
+
+</para>
+   </sect3>
+
+   <sect3><title>Supported console options</title>
+<para>
+
+Serial console is available on all supported DECstations (9600 bps,
+8N1). For using serial console, you have to boot the installer image
+with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel
+parameter (with <replaceable>x</replaceable> being the number
+of the serial port you have your terminal connected to &mdash; usually
+<literal>2</literal>, but <literal>0</literal> for the Personal DECstations).
+On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) local console
+is available with the PMAG-BA and the PMAGB-B graphics options.
+
+</para><para>
+
+If you have a Linux system to use as serial terminal, an easy way
+is to run <command>cu</command><footnote>
+
+<para>
+In Woody this command was part of the <classname>uucp</classname> package,
+but in later releases it is available as a separate package.
+</para>
+
+</footnote> on it. Example:
+
+<informalexample><screen>
+$ cu -l /dev/ttyS1 -s 9600
+</screen></informalexample>
+
+where the option <literal>-l</literal> (line) sets the serial port to use
+and <literal>-s</literal> (speed) sets the speed for the connection (9600
+bits per second).
+
+</para><para>
+
+Both Cobalt and Broadcom BCM91250A use 115200 bps.
+
+</para>
+   </sect3>
+  </sect2>
diff --git a/fi/hardware/supported/powerpc.xml b/fi/hardware/supported/powerpc.xml
new file mode 100644
index 000000000..fbc4b2f8b
--- /dev/null
+++ b/fi/hardware/supported/powerpc.xml
@@ -0,0 +1,381 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 30269 untranslated -->
+
+
+  <sect2 arch="powerpc"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+There are four major supported <emphasis>&architecture;</emphasis>
+subarchitectures: PMac (Power-Macintosh), PReP, APUS (Amiga Power-UP
+System), and CHRP machines. Each subarchitecture has its own boot
+methods. In addition, there are four different kernel flavours,
+supporting different CPU variants.
+
+</para><para>
+
+Ports to other <emphasis>&architecture;</emphasis> architectures, such
+as the Be-Box and MBX architecture, are underway but not yet supported
+by Debian. We may have a 64-bit port in the future.
+
+</para>
+
+   <sect3><title>Kernel Flavours</title>
+
+<para>
+
+There are four flavours of the powerpc kernel in Debian, based on the
+CPU type:
+
+<variablelist>
+<varlistentry>
+<term>powerpc</term>
+<listitem><para>
+
+Most systems use this kernel flavour, which supports the PowerPC 601,
+603, 604, 740, 750, and 7400 processors. All Apple Power Macintosh
+systems up to and including the G4 use one of these processors.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>power3</term>
+<listitem><para>
+
+The POWER3 processor is used in older IBM 64-bit server systems: known
+models include the IntelliStation POWER Model 265, the pSeries 610 and
+640, and the RS/6000 7044-170, 7043-260, and 7044-270.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>power4</term>
+<listitem><para>
+
+The POWER4 processor is used in more recent IBM 64-bit server systems:
+known models include the pSeries 615, 630, 650, 655, 670, and 690.
+
+</para><para>
+
+The Apple G5 is also based on the POWER4 architecture, and uses this
+kernel flavour.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>apus</term>
+<listitem><para>
+
+This kernel flavour supports the Amiga Power-UP System.
+
+</para></listitem>
+</varlistentry>
+</variablelist>
+
+</para>
+
+   </sect3>
+
+   <sect3><title>Power Macintosh (pmac) subarchitecture</title>
+
+<para>
+
+Apple (and briefly a few other manufacturers &mdash; Power Computing, for
+example) makes a series of Macintosh computers based on the PowerPC
+processor. For purposes of architecture support, they are categorized
+as NuBus, OldWorld PCI, and NewWorld.
+
+</para><para>
+
+Macintosh computers using the 680x0 series of processors are not in
+the PowerPC family but are instead m68k machines. Those models start
+with <quote>Mac II</quote> or have a 3-digit model number such as Centris 650
+or Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits.
+
+</para><para>
+
+NuBus systems are not currently supported by debian/powerpc. The
+monolithic Linux/PPC kernel architecture does not have support for
+these machines; instead, one must use the MkLinux Mach microkernel,
+which Debian does not yet support. These include the following:
+
+<itemizedlist>
+<listitem><para>
+
+Power Macintosh 6100, 7100, 8100
+
+</para></listitem>
+<listitem><para>
+
+Performa 5200, 6200, 6300
+
+</para></listitem>
+<listitem><para>
+
+Powerbook 1400, 2300, and 5300
+
+</para></listitem>
+<listitem><para>
+
+Workgroup Server 6150, 8150, 9150
+
+</para></listitem>
+</itemizedlist>
+
+A linux kernel for these machines and limited support is available at
+<ulink url="http://nubus-pmac.sourceforge.net/"></ulink>
+
+</para><para>
+
+OldWorld systems are most Power Macintoshes with a floppy drive and a
+PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are
+OldWorld machines. The beige colored G3 systems are also OldWorld.
+
+</para><para>
+
+The so called NewWorld PowerMacs are any PowerMacs in translucent
+colored plastic cases. That includes all iMacs, iBooks, G4 systems,
+blue colored G3 systems, and most PowerBooks manufactured in and after
+1999. The NewWorld PowerMacs are also known for using the <quote>ROM in
+RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards.
+
+</para><para>
+
+Specifications for Apple hardware are available at
+<ulink url="http://www.info.apple.com/support/applespec.html">AppleSpec</ulink>,
+and, for older hardware,
+<ulink url="http://www.info.apple.com/support/applespec.legacy/index.html">AppleSpec Legacy</ulink>.
+
+</para><para>
+
+<informaltable>
+<tgroup cols="3">
+<colspec colname="c1"/>
+<colspec colname="c2"/>
+<colspec colname="c3"/>
+<thead>
+<row>
+  <entry namest="c1" nameend="c2">Model Name/Number</entry>
+  <entry>Generation</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry morerows="22">Apple</entry>
+  <entry>iMac Bondi Blue, 5 Flavors, Slot Loading</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>iMac Summer 2000, Early 2001</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>iMac G5</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>iBook, iBook SE, iBook Dual USB</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>iBook2</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>iBook G4</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>Power Macintosh Blue and White (B&amp;W) G3</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>Power Macintosh G4 PCI, AGP, Cube</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>Power Macintosh G4 Gigabit Ethernet</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>Power Macintosh G4 Digital Audio, Quicksilver</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>Power Macintosh G5</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>PowerBook G3 FireWire Pismo (2000)</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>PowerBook G3 Lombard (1999)</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>PowerBook G4 Titanium</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>PowerBook G4 Aluminum</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>Xserve G5</entry>
+  <entry>NewWorld</entry>
+</row><row>
+  <entry>Performa 4400, 54xx, 5500</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Performa 6360, 6400, 6500</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Power Macintosh 4400, 5400</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Power Macintosh 7200, 7300, 7500, 7600</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Power Macintosh 8200, 8500, 8600</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Power Macintosh 9500, 9600</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Power Macintosh (Beige) G3 Minitower</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Power Macintosh (Beige) Desktop, All-in-One</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>PowerBook 2400, 3400, 3500</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>PowerBook G3 Wallstreet (1998)</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Twentieth Anniversary Macintosh</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>Workgroup Server 7250, 7350, 8550, 9650, G3</entry>
+  <entry>OldWorld</entry>
+</row>
+
+<row>
+  <entry morerows="1">Power Computing</entry>
+  <entry>PowerBase, PowerTower / Pro, PowerWave</entry>
+  <entry>OldWorld</entry>
+</row><row>
+  <entry>PowerCenter / Pro, PowerCurve</entry>
+  <entry>OldWorld</entry>
+</row>
+
+<row>
+  <entry>UMAX</entry>
+  <entry>C500, C600, J700, S900</entry>
+  <entry>OldWorld</entry>
+</row>
+
+<row>
+  <entry>APS</entry>
+  <entry>APS Tech M*Power 604e/2000</entry>
+  <entry>OldWorld</entry>
+</row>
+
+<row>
+  <entry>Motorola</entry>
+  <entry>Starmax 3000, 4000, 5000, 5500</entry>
+  <entry>OldWorld</entry>
+</row>
+</tbody></tgroup></informaltable>
+
+</para>
+
+   </sect3>
+
+   <sect3><title>PReP subarchitecture</title>
+
+<para>
+
+<informaltable>
+<tgroup cols="2">
+<colspec colname="c1"/>
+<colspec colname="c2"/>
+<thead>
+<row>
+  <entry namest="c1" nameend="c2">Model Name/Number</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry morerows="4">Motorola</entry>
+  <entry>Firepower, PowerStack Series E, PowerStack II</entry>
+</row><row>
+  <entry>MPC 7xx, 8xx</entry>
+</row><row>
+  <entry>MTX, MTX+</entry>
+</row><row>
+  <entry>MVME2300(SC)/24xx/26xx/27xx/36xx/46xx</entry>
+</row><row>
+  <entry>MCP(N)750</entry>
+</row>
+
+<row>
+  <entry morerows="3">IBM RS/6000</entry>
+  <entry>40P, 43P</entry>
+</row><row>
+  <entry>Power 830/850/860 (6070, 6050)</entry>
+</row><row>
+  <entry>6030, 7025, 7043</entry>
+</row><row>
+  <entry>p640</entry>
+</row>
+</tbody></tgroup></informaltable>
+
+</para>
+
+   </sect3>
+
+   <sect3><title>CHRP subarchitecture</title>
+
+<para>
+
+<informaltable>
+<tgroup cols="2">
+<colspec colname="c1"/>
+<colspec colname="c2"/>
+<thead>
+<row>
+  <entry namest="c1" nameend="c2">Model Name/Number</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry>IBM RS/6000</entry>
+  <entry>B50, 43P-150, 44P</entry>
+</row>
+<row>
+  <entry>Genesi</entry>
+  <entry>Pegasos I, Pegasos II</entry>
+</row>
+</tbody></tgroup></informaltable>
+
+</para>
+
+   </sect3>
+
+   <sect3><title>APUS subarchitecture</title>
+
+<para>
+
+<informaltable>
+<tgroup cols="2">
+<colspec colname="c1"/>
+<colspec colname="c2"/>
+<thead>
+<row>
+  <entry namest="c1" nameend="c2">Model Name/Number</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry>Amiga Power-UP Systems (APUS)</entry>
+  <entry>A1200, A3000, A4000</entry>
+</row>
+</tbody></tgroup></informaltable>
+
+</para>
+   </sect3>
+  </sect2>
diff --git a/fi/hardware/supported/s390.xml b/fi/hardware/supported/s390.xml
new file mode 100644
index 000000000..edda7217d
--- /dev/null
+++ b/fi/hardware/supported/s390.xml
@@ -0,0 +1,21 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28672 untranslated -->
+
+
+  <sect2 arch="s390"><title>S/390 and zSeries machine types</title>
+<para>
+
+Complete information regarding supported S/390 and zSeries machines can
+be found in IBM's Redbook
+<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf">
+Linux for IBM eServer zSeries and S/390: Distributions</ulink> in
+chapter 2.1 or at the
+<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml">technical details web page</ulink> at
+<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml">developerWorks</ulink>.
+In short, G5, Multiprise 3000, G6 and all zSeries are fully supported;
+Multiprise 2000, G3 and G4 machines are supported with IEEE floating
+point emulation and thus degraded performance.
+
+</para>
+  </sect2>
+
diff --git a/fi/hardware/supported/sparc.xml b/fi/hardware/supported/sparc.xml
new file mode 100644
index 000000000..d00c6b252
--- /dev/null
+++ b/fi/hardware/supported/sparc.xml
@@ -0,0 +1,82 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="sparc" id="sparc-cpus"><title>CPU, Main Boards, and Video Support</title>
+<para>
+
+Currently the <emphasis>&architecture;</emphasis> port supports
+several types of Sparc systems. The most common identifiers for Sparc
+systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not
+support very old sun4 hardware. However, the other systems are
+supported. Sun4d has been tested the least of these, so expect
+possible problems with regard to the kernel stability. Sun4c and
+Sun4m, the most common of the older Sparc hardware, includes such
+systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5,
+10, and 20, respectively. The UltraSPARC class systems fall under the
+sun4u identifier, and are supported using the sun4u set of install
+images. Some systems that fall under these supported identifiers are
+known to not be supported. Known unsupported systems are the AP1000
+multicomputer and the Tadpole Sparcbook 1. See the
+<ulink url="&url-sparc-linux-faq;">Linux for SPARCProcessors FAQ</ulink>
+for complete information.
+
+</para>
+
+   <sect3><title>Memory Configuration</title>
+<para>
+
+Some older Sun workstations, notably the Sun IPX and Sun IPC have
+memory banks located at fixed locations in physical memory.  Thus if
+the banks are not filled gaps will exist in the physical memory space.
+The Linux installation requires a contiguous memory block into which
+to load the kernel and the initial RAMdisk.  If this is not available a
+<quote>Data Access Exception</quote> will result.
+
+</para><para>
+
+Thus you must configure the memory so that the lowest memory block is
+contiguous for at least 8Mb.  In the IPX and IPC cited above, memory banks
+are mapped in at 16Mb boundaries.  In effect this means that you must have
+a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk.
+In this case 4Mb is <emphasis>not</emphasis> sufficient.
+
+</para><para>
+
+Example:
+In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM.  There are four
+SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS
+connectors]. You must therefore install the 16Mb SIMM in bank 0; it is
+then recommended to install the 4Mb SIMM in bank 2.
+
+</para>
+   </sect3>
+
+   <sect3><title>Graphics Configuration</title>
+<para>
+
+Especially in the case of older Sun workstations, it is very common
+for there to be an onboard framebuffer which has been superseded (for
+example the bwtwo on a sun IPC), and an SBUS card containing a later
+probably accelerated buffer is then plugged in to an SBUS slot.
+Under Solaris/SunOS this causes no problems because both cards are
+initialized.
+
+</para><para>
+
+However with Linux this can cause a problem, in that the boot PROM
+monitor may display its output on this additional card; however the
+linux kernel boot messages may then be directed to the original on
+board framebuffer, leaving <emphasis>no</emphasis> error messages on
+the screen, with the machine apparently stuck loading the RAMdisk.
+
+</para><para>
+
+To avoid this problem, connect the monitor (if required) to the video
+card in the lowest numbered SBUS slot (on motherboard card counts
+as below external slots).  Alternatively it is possible to use a serial
+console.
+
+</para>
+   </sect3>
+  </sect2>