diff options
Diffstat (limited to 'nb/hardware/hardware.xml')
| -rw-r--r-- | nb/hardware/hardware.xml | 2534 |
1 files changed, 2534 insertions, 0 deletions
diff --git a/nb/hardware/hardware.xml b/nb/hardware/hardware.xml new file mode 100644 index 000000000..2b6525e19 --- /dev/null +++ b/nb/hardware/hardware.xml @@ -0,0 +1,2534 @@ +<!-- Start of file hardware/hardware.xml --> +<!-- $Id: hardware.xml 56244 2008-10-03 16:05:55Z fjp $ --> + +<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> + + +<!-- Start of file hardware/hardware-supported.xml --> +<!-- $Id: hardware-supported.xml 56439 2008-10-15 17:45:28Z fjp $ --> + + <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 +>Intel x86-based</entry> + <entry +>i386</entry> + <entry +></entry> + <entry +></entry> +</row> + +<row> + <entry +>AMD64 & Intel EM64T</entry> + <entry +>amd64</entry> + <entry +></entry> + <entry +></entry> +</row> + +<row> + <entry +>DEC Alpha</entry> + <entry +>alpha</entry> + <entry +></entry> + <entry +></entry> +</row> + +<row> + <entry morerows="4" +>ARM</entry> + <entry +>arm</entry> + <entry +>Netwinder and CATS</entry> + <entry +>netwinder</entry> +</row +><row> + <entry +>armel</entry> + <entry +>Versatile</entry> + <entry +>versatile</entry> +</row +><row> + <entry morerows="2" +>arm and armel</entry> + <entry +>Intel IOP32x</entry> + <entry +>iop32x</entry> +</row +><row> + <entry +>Intel IXP4xx</entry> + <entry +>ixp4xx</entry> +</row +><row> + <entry +>Marvell Orion</entry> + <entry +>orion5x</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 IA-64</entry> + <entry +>ia64</entry> + <entry +></entry> + <entry +></entry> +</row> + +<row> + <entry morerows="5" +>MIPS (big endian)</entry> + <entry morerows="5" +>mips</entry> + <entry +>SGI IP22 (Indy/Indigo 2)</entry> + <entry +>r4k-ip22</entry> +</row +><row> + <entry +>SGI IP32 (O2)</entry> + <entry +>r5k-ip32</entry> +</row +><row> + <entry +>MIPS Malta (32 bit)</entry> + <entry +>4kc-malta</entry> +</row +><row> + <entry +>MIPS Malta (64 bit)</entry> + <entry +>5kc-malta</entry> +</row +><row> + <entry +>Broadcom BCM91250A (SWARM)</entry> + <entry +>sb1-bcm91250a</entry> +</row +><row> + <entry +>Broadcom BCM91480B (BigSur)</entry> + <entry +>sb1a-bcm91480b</entry> +</row> + +<row> + <entry morerows="4" +>MIPS (little endian)</entry> + <entry morerows="4" +>mipsel</entry> + <entry +>Cobalt</entry> + <entry +>cobalt</entry> +</row +><row> + <entry +>MIPS Malta (32 bit)</entry> + <entry +>4kc-malta</entry> +</row +><row> + <entry +>MIPS Malta (64 bit)</entry> + <entry +>5kc-malta</entry> +</row +><row> + <entry +>Broadcom BCM91250A (SWARM)</entry> + <entry +>sb1-bcm91250a</entry> +</row +><row> + <entry +>Broadcom BCM91480B (BigSur)</entry> + <entry +>sb1a-bcm91480b</entry> +</row> + +<row arch="m68k"> + <entry morerows="5" +>Motorola 680x0</entry> + <entry morerows="5" +>m68k</entry> + <entry +>Atari</entry> + <entry +>atari</entry> +</row +><row arch="m68k"> + <entry +>Amiga</entry> + <entry +>amiga</entry> +</row +><row arch="m68k"> + <entry +>68k Macintosh</entry> + <entry +>mac</entry> +</row +><row arch="m68k"> + <entry morerows="2" +>VME</entry> + <entry +>bvme6000</entry> +</row +><row arch="m68k"> + <entry +>mvme147</entry> +</row +><row arch="m68k"> + <entry +>mvme16x</entry> +</row> + +<row> + <entry morerows="1" +>IBM/Motorola PowerPC</entry> + <entry morerows="1" +>powerpc</entry> + <entry +>PowerMac</entry> + <entry +>pmac</entry> +</row +><row> + <entry +>PReP</entry> + <entry +>prep</entry> +</row> + +<row> + <entry morerows="1" +>Sun SPARC</entry> + <entry morerows="1" +>sparc</entry> + <entry +>sun4u</entry> + <entry morerows="1" +>sparc64</entry> +</row +><row> + <entry +>sun4v</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-&arch-listname; mailing list</ulink +> as well. </para> + </sect2> + +<!-- supported cpu docs --> + +<!-- Start of file hardware/supported/alpha.xml --> +<!-- $Id: alpha.xml 28997 2005-07-07 21:09:22Z fjp $ --> + + + <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> +<!-- End of file hardware/supported/alpha.xml --> + +<!-- Start of file hardware/supported/amd64.xml --> +<!-- $Id: i386.xml 39614 2006-08-07 15:50:11Z fjp $ --> + + + <sect2 arch="amd64" +><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 +>Both AMD64 and Intel EM64T processors are supported. </para> + </sect3> + +<!-- Not sure if this is relevant for AMD64; AFAIK only PCI supported + <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 PCI bus. + +</para> + </sect3> +--> + </sect2> + +<!-- End of file hardware/supported/amd64.xml --> + +<!-- Start of file hardware/supported/arm.xml --> +<!-- $Id: arm.xml 55470 2008-08-31 16:25:05Z tbm $ --> + + + <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 platforms. The Debian userland however may be used by <emphasis +>any</emphasis +> ARM CPU. </para> + +<para +>Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems. </para> + +<para +>The supported platforms 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 (also known as Footbridge). 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 +>IOP32x</term> +<listitem +><para +>Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url="&url-arm-cyrius-glantank;" +>GLAN Tank</ulink +> from IO-Data and the <ulink url="&url-arm-cyrius-n2100;" +>Thecus N2100</ulink +>. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>IXP4xx</term> +<listitem +><para +>The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url="&url-arm-cyrius-nslu2;" +>installation instructions</ulink +>. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>Orion5x</term> +<listitem +><para +>Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url="&url-arm-cyrius-kuroboxpro;" +>Buffalo Kurobox</ulink +>, <ulink url="&url-arm-cyrius-mv2120;" +>HP mv2120</ulink +>, <ulink url="&url-arm-cyrius-qnap;" +>QNAP Turbo Station</ulink +> (TS-109, TS-209 and TS-409). </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>Versatile</term> +<listitem +><para +>The Versatile platform is emulated by QEMU and is therefore a nice way to test and run Debian on ARM if you don't have the hardware. </para +></listitem> +</varlistentry> + +</variablelist> + +</para> + </sect2> +<!-- End of file hardware/supported/arm.xml --> + +<!-- Start of file hardware/supported/hppa.xml --> +<!-- $Id: hppa.xml 41452 2006-10-09 13:21:56Z cjwatson $ --> + + + <sect2 arch="hppa" +><title +>CPU, Main Boards, and Video Support</title> +<para +>There 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> + +<!-- End of file hardware/supported/hppa.xml --> + +<!-- Start of file hardware/supported/i386.xml --> +<!-- $Id: i386.xml 56248 2008-10-03 17:07:28Z fjp $ --> + + + <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 (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's "Pentium" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon. </para +><para +>However, Debian GNU/Linux &releasename; will <emphasis +>not</emphasis +> run on 386 or earlier processors. Despite the architecture name "i386", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote +> <para +> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para +> </footnote +>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote +> <para +> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para +> </footnote +>. </para> +<note +><para +>If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture. </para +></note> + </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, PCIe, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these. </para> + </sect3> + </sect2> + +<!-- End of file hardware/supported/i386.xml --> + +<!-- Start of file hardware/supported/ia64.xml --> +<!-- $Id: ia64.xml 11648 2004-03-22 00:37:46Z joeyh $ --> + +<!-- End of file hardware/supported/ia64.xml --> + +<!-- Start of file hardware/supported/m68k.xml --> +<!-- $Id: m68k.xml 36732 2006-04-27 09:33:13Z fjp $ --> + + <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 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> + + + +<!-- End of file hardware/supported/m68k.xml --> + +<!-- Start of file hardware/supported/mips.xml --> +<!-- $Id: mips.xml 55471 2008-08-31 16:30:54Z tbm $ --> + + + <sect2 arch="mips" +><title +>CPU, Main Boards, and Video Support</title> +<para +>Debian on &arch-title; supports the following platforms: <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 +> SGI IP32: this platform is generally known as SGI O2. </para +></listitem +> <listitem +><para +> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para +></listitem +> <listitem +><para +> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para +></listitem +> <listitem +><para +> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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-&arch-listname; 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. On SGI IP32, currently only systems based on the R5000 are supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode. </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> + +<!-- End of file hardware/supported/mips.xml --> + +<!-- Start of file hardware/supported/mipsel.xml --> +<!-- $Id: mipsel.xml 55471 2008-08-31 16:30:54Z tbm $ --> + + + <sect2 arch="mipsel" +><title +>CPU, Main Boards, and Video Support</title> +<para +>Debian on &arch-title; supports the following platforms: <itemizedlist +> <listitem +><para +> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para +></listitem +> <listitem +><para +> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para +></listitem +> <listitem +><para +> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para +></listitem +> <listitem +><para +> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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-&arch-listname; mailing list</ulink +>. </para> + + <sect3 +><title +>CPU/Machine types</title> + +<para +>All MIPS based Cobalt machines are supported. </para +><para +>The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode. </para> + </sect3> + + <sect3 +><title +>Supported console options</title> +<para +>Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps. </para> + </sect3> + </sect2> +<!-- End of file hardware/supported/mipsel.xml --> + +<!-- Start of file hardware/supported/powerpc.xml --> +<!-- $Id: powerpc.xml 56248 2008-10-03 17:07:28Z fjp $ --> + + + <sect2 arch="powerpc" +><title +>CPU, Main Boards, and Video Support</title> +<para +>For &debian; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported. </para> + + <sect3 +><title +>Kernel Flavours</title> + +<para +>There are two 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 PowerMac machines up to and including the one marketed as G4 use one of these processors. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>power64</term> +<listitem +><para +>The power64 kernel flavour supports the following CPUs: </para +><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 +><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 +>Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour. </para +></listitem> +</varlistentry> + +<!-- +<varlistentry> +<term +>prep</term> +<listitem +><para> + +This kernel flavour supports the PReP subarchitecture. + +</para +></listitem> +</varlistentry> + +<varlistentry> +<term +>apus</term> +<listitem +><para> + +This kernel flavour supports the Amiga Power-UP System, though it is +currently disabled. + +</para +></listitem> +</varlistentry> +--> +</variablelist> + +</para> + + </sect3> + + <sect3 +><title +>Power Macintosh (pmac) subarchitecture</title> + +<para +>Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by Debian), OldWorld, and NewWorld. </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. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld. </para +><para +>The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. 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="27" +>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&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 (unsupported)</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 (unsupported)</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> + + <sect3 +><title +>Nubus PowerMac subarchitecture (unsupported)</title> + +<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> + + </sect3> + + <sect3 +><title +>Non-PowerPC Macs</title> + +<para +>Macintosh computers using the 680x0 series of processors are <emphasis +>not</emphasis +> in the PowerPC family but are instead m68k machines. Those models start with <quote +>Mac II</quote +> series, go on to the <quote +>LC</quote +> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950. </para +><para +>This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD. </para +><para +>In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above). </para> + + </sect3> + </sect2> +<!-- End of file hardware/supported/powerpc.xml --> + +<!-- Start of file hardware/supported/s390.xml --> +<!-- $Id: s390.xml 39895 2006-08-16 20:28:37Z fjp $ --> + + + <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://www-128.ibm.com/developerworks/linux/linux390/index.html" +>zSeries page at the 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> + +<!-- End of file hardware/supported/s390.xml --> + +<!-- Start of file hardware/supported/sparc.xml --> +<!-- $Id: sparc.xml 49849 2007-10-21 12:12:33Z fjp $ --> + + <sect2 arch="sparc" id="sparc-cpus"> + <title +>CPU and Main Boards Support</title> +<para +>Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them. </para> + +<variablelist> +<varlistentry> +<term +>sun4, sun4c, sun4d, sun4m</term> + +<listitem +><para +>None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url="http://en.wikipedia.org/wiki/SPARCstation" +>Wikipedia SPARCstation page</ulink +>. </para +><para +>The last Debian release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>sun4u</term> + +<listitem +><para +>This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>sun4v</term> + +<listitem +><para +>This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel. </para +></listitem> +</varlistentry> +</variablelist> + +<para +>Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel. </para> + </sect2> +<!-- End of file hardware/supported/sparc.xml --> + + <sect2 arch="x86" id="laptops" +><title +>Laptops</title> +<para +>Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url="&url-x86-laptop;" +>Linux Laptop pages</ulink +>. </para> + </sect2> + + <sect2 condition="defaults-smp"> + <title +>Multiple Processors</title> +<para +>Multiprocessor support — also called <quote +>symmetric multiprocessing</quote +> or SMP — is available for this architecture. The standard Debian &release; kernel image has been compiled with SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable. </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="smp-alternatives"> +<title +>Multiple Processors</title> + +<para +>Multiprocessor support — also called <quote +>symmetric multiprocessing</quote +> or SMP — is available for this architecture. The standard Debian &release; kernel image has been compiled with <firstterm +>SMP-alternatives</firstterm +> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems. </para +><para arch="i386" +>The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support. </para> + </sect2> + + <sect2 condition="supports-smp"> + <title +>Multiple Processors</title> +<para +>Multiprocessor support — also called <quote +>symmetric multiprocessing</quote +> or SMP — is available 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 +>Multiprocessor support — also called <quote +>symmetric multiprocessing</quote +> or SMP — is available 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. </para +><para +>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> + + <sect2 id="gfx" arch="not-s390" +><title +>Graphics Card Support</title> +<para arch="x86" +>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 X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url="&url-xorg;" +></ulink +>. Debian &release; ships with X.Org version &x11ver;. </para +><para arch="mips" +>The X.Org X Window System is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url="&url-bcm91250a-hardware;" +>compatibility listing</ulink +> for Broadcom evaluation boards is available. </para +><para arch="mipsel" +>The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url="&url-bcm91250a-hardware;" +>compatibility listing</ulink +> for Broadcom evaluation boards is available. </para +><para arch="sparc" +>Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname +>afbinit</classname +> package, and read the documentation included with it on how to activate the card. </para +><para arch="sparc" +>It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system. </para> + </sect2> + + +<!-- Start of file hardware/network-cards.xml --> +<!-- $Id: network-cards.xml 56450 2008-10-17 09:58:39Z fjp $ --> + + <sect2 id="network-cards"> + <title +>Network Connectivity Hardware</title> +<para +>Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch="x86" +>This includes most PCI and PCMCIA cards.</phrase +> <phrase arch="i386" +>Many older ISA cards are supported as well.</phrase +> <phrase arch="m68k" +>Again, see <ulink url="&url-m68k-faq;" +></ulink +> for complete details.</phrase +> </para +><para arch="sparc" +>This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun: <itemizedlist> +<listitem +><para +>Sun LANCE </para +></listitem> +<listitem +><para +>Sun Happy Meal </para +></listitem> +<listitem +><para +>Sun BigMAC </para +></listitem> +<listitem +><para +>Sun QuadEthernet </para +></listitem> +<listitem +><para +>MyriCOM Gigabit Ethernet </para +></listitem> +</itemizedlist> + +</para +><para arch="s390" +>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 +>OSA-Express in QDIO mode, HiperSockets and Guest-LANs </para +></listitem> +</itemizedlist> + +</para> + +<para arch="arm" +>On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url="&url-slug-firmware;" +>Slug-Firmware site</ulink +>. </para +><para arch="x86" +>ISDN is supported, but not during the installation. </para> + + <sect3 condition="supports-wireless" id="nics-wireless"> + <title +>Wireless Network Cards</title> +<para +>Wireless networking is in general supported as well and a growing number of wireless adapters is supported by the official Linux kernel, although many of them do require firmware to be loaded. Wireless NICs that are not supported by the official Linux kernel can generally be made to work under &debian;, but are not supported during the installation. </para +><para +>The use of wireless networking during installation is still under development and whether it will work depends on the type of adaptor and the configuration of your wireless access point. If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually. </para +><para +>In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch="x86" +>If no Linux driver is available, your last resort is to use the <classname +>ndiswrapper</classname +> package, which allows you to use a Windows driver.</phrase +> </para> + </sect3> + + <sect3 arch="sparc" id="nics-sparc-trouble"> + <title +>Known Issues for &arch-title;</title> +<para +>There are a couple of issues with specific network cards that are worth mentioning here. </para> + + <sect4 +><title +>Conflict between tulip and dfme drivers</title> +<!-- BTS: #334104; may also affect other arches, but most common on sparc --> +<para +>There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal +>tulip</literal +> driver, others with the <literal +>dfme</literal +> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly. </para +><para +>This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal +>tulip</literal +> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend="module-blacklist"/>. </para +><para +>An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput +>modprobe -r <replaceable +>module</replaceable +></userinput +> (or both, if they are both loaded). After that you can load the correct module using <userinput +>modprobe <replaceable +>module</replaceable +></userinput +>. Note that the wrong module may then still be loaded when the system is rebooted. </para> + </sect4> + + <sect4 +><title +>Sun B100 blade</title> +<!-- BTS: #384549; should be checked for kernels +>2.6.18 --> +<para +>The <literal +>cassini</literal +> network driver does not work with Sun B100 blade systems. </para> + </sect4> + </sect3> + </sect2> +<!-- End of file hardware/network-cards.xml --> + +<!-- Start of file hardware/supported-peripherals.xml --> +<!-- $Id: supported-peripherals.xml 56244 2008-10-03 16:05:55Z fjp $ --> + + <sect2 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="x86" +>USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend="hardware-issues"/>). </para +><para arch="x86" +>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. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. </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 Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot. </para> + </sect2> +<!-- End of file hardware/supported-peripherals.xml --> + + </sect1> + + <sect1 arch="not-s390" id="hardware-firmware"> + <title +>Devices Requiring Firmware</title> +<para +>Besides the availability of a device driver, some hardware also requires so-called <firstterm +>firmware</firstterm +> or <firstterm +>microcode</firstterm +> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. </para +><para +>In most cases firmware is non-free according to the criteria used by the &debian; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive. </para +><para +>However, this does not mean that such hardware cannot be used during an installation. Starting with &debian; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend="loading-firmware"/> for detailed information on how to load firmware files or packages during the installation. </para> + </sect1> +<!-- End of file hardware/hardware-supported.xml --> + +<!-- Start of file hardware/buying-hardware.xml --> +<!-- $Id: buying-hardware.xml 56244 2008-10-03 16:05:55Z fjp $ --> + + <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="x86" +>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="x86" +><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 it 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 improve 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> + </sect1> +<!-- End of file hardware/buying-hardware.xml --> + +<!-- Start of file hardware/installation-media.xml --> +<!-- $Id: installation-media.xml 56150 2008-09-26 10:48:26Z lunar $ --> + + <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 to 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="x86" +>SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url="&url-cd-howto;" +>Linux CD-ROM HOWTO</ulink +> contains in-depth information on using CD-ROMs with Linux. </para +><para arch="x86" +>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. </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-ROM drives sold on 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. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card. </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 +>The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP. </para +><para condition="supports-tftp" +>You can also <emphasis +>boot</emphasis +> the installation system over the network. <phrase arch="mips" +>This is the preferred installation technique for &arch-title;.</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> + </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 this 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="x86" +>Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS. </para +><para arch="i386" +>Disk interfaces that emulate the <quote +>AT</quote +> hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and 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> +<!-- End of file hardware/installation-media.xml --> + +<!-- Start of file hardware/memory-disk-requirements.xml --> +<!-- $Id: memory-disk-requirements.xml 52960 2008-04-30 06:22:01Z fjp $ --> + + <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 to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend="minimum-hardware-reqts"/>. </para +><para +>Installation on systems with less memory<footnote condition="gtk" +> <para +> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para +> </footnote +> or disk space available may be possible but is only advised for experienced users. </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> +<!-- End of file hardware/memory-disk-requirements.xml --> + +</chapter> +<!-- End of file hardware/hardware.xml --> |