diff options
Diffstat (limited to 'en/hardware')
| -rw-r--r-- | en/hardware/accessibility.xml | 2 | ||||
| -rw-r--r-- | en/hardware/hardware-supported.xml | 58 | ||||
| -rw-r--r-- | en/hardware/installation-media.xml | 49 | ||||
| -rw-r--r-- | en/hardware/network-cards.xml | 87 | ||||
| -rw-r--r-- | en/hardware/supported/hppa.xml | 17 | ||||
| -rw-r--r-- | en/hardware/supported/ia64.xml | 3 | ||||
| -rw-r--r-- | en/hardware/supported/mips.xml | 116 | ||||
| -rw-r--r-- | en/hardware/supported/powerpc.xml | 8 | ||||
| -rw-r--r-- | en/hardware/supported/sparc.xml | 70 |
9 files changed, 12 insertions, 398 deletions
diff --git a/en/hardware/accessibility.xml b/en/hardware/accessibility.xml index 428be96b2..0600e7481 100644 --- a/en/hardware/accessibility.xml +++ b/en/hardware/accessibility.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect2 id="braille-displays" arch="ia64;powerpc;ppc64el;x86"> + <sect2 id="braille-displays" arch="ppc64el;x86"> <title>Braille Displays</title> <para> diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml index 3db1387e4..f1dddcc5e 100644 --- a/en/hardware/hardware-supported.xml +++ b/en/hardware/hardware-supported.xml @@ -79,18 +79,6 @@ variations of each architecture known as <quote>flavors</quote>. <entry></entry> </row> -<!-- -<row> - <entry morerows="1">32bit MIPS (big-endian)</entry> - <entry morerows="1">mips</entry> - <entry>MIPS Malta</entry> - <entry>4kc-malta</entry> -</row><row> - <entry>Cavium Octeon</entry> - <entry>octeon</entry> -</row> ---> - <row> <entry morerows="2">64bit MIPS (little-endian)</entry> <entry morerows="2">mips64el</entry> @@ -138,26 +126,6 @@ variations of each architecture known as <quote>flavors</quote>. <entry></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>IBM S/390</entry> - <entry>s390</entry> - <entry>IPL from VM-reader and DASD</entry> - <entry>generic</entry> -</row> ---> - <row> <entry>64bit IBM S/390</entry> <entry>s390x</entry> @@ -200,10 +168,8 @@ as well. &supported-amd64.xml; &supported-arm.xml; &supported-i386.xml; -&supported-mips.xml; &supported-powerpc.xml; &supported-s390.xml; -&supported-sparc.xml; <sect2 arch="x86" id="laptops"><title>Laptops</title> <para> @@ -358,30 +324,6 @@ Details on supported graphics hardware and pointing devices can be found at <ulink url="&url-xorg;"></ulink>. &debian; &release; ships with X.Org version &x11ver;. -</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> diff --git a/en/hardware/installation-media.xml b/en/hardware/installation-media.xml index 742a09e09..00eba6c8a 100644 --- a/en/hardware/installation-media.xml +++ b/en/hardware/installation-media.xml @@ -73,7 +73,7 @@ deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. -<phrase arch="mips;mipsel;mips64el">This is the preferred installation technique +<phrase arch="mipsel;mips64el">This is the preferred installation technique for &arch-title;.</phrase> </para><para condition="supports-nfsroot"> @@ -94,12 +94,8 @@ for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available. -</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> @@ -141,38 +137,9 @@ SCSI disk controllers from many different manufacturers are supported. See the for more details. --> -</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><para> -</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. +IDE systems are also supported. <!-- </para><para arch="powerpc"> @@ -180,13 +147,7 @@ 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;mipsel;mips64el"> +</para><para arch="mipsel;mips64el"> Any storage system supported by the Linux kernel is also supported by the boot system. diff --git a/en/hardware/network-cards.xml b/en/hardware/network-cards.xml index cd1b059ce..692d38202 100644 --- a/en/hardware/network-cards.xml +++ b/en/hardware/network-cards.xml @@ -13,40 +13,9 @@ should normally be loaded automatically. PCMCIA/Express Cards on laptops.</phrase> <phrase arch="i386">Many older ISA cards are supported as well.</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><para arch="s390"> +<para arch="s390"> The list of supported network devices is: @@ -123,56 +92,4 @@ 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> - -<!-- BTS: #334104; may also affect other arches, but most common on sparc --> -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> diff --git a/en/hardware/supported/hppa.xml b/en/hardware/supported/hppa.xml deleted file mode 100644 index b2fdad4d1..000000000 --- a/en/hardware/supported/hppa.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <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> - diff --git a/en/hardware/supported/ia64.xml b/en/hardware/supported/ia64.xml deleted file mode 100644 index 53394db87..000000000 --- a/en/hardware/supported/ia64.xml +++ /dev/null @@ -1,3 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - diff --git a/en/hardware/supported/mips.xml b/en/hardware/supported/mips.xml deleted file mode 100644 index f8fd19a54..000000000 --- a/en/hardware/supported/mips.xml +++ /dev/null @@ -1,116 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="mips;mips64el;mipsel"><title>Platforms supported by the - &debian; &architecture; port</title> -<para> - -&debian; on &arch-title; supports the following platforms: - - <variablelist> - <varlistentry> - <term>Cavium Octeon</term> - <listitem> - <para> - Cavium designs a range of 64-bit MIPS Octeon processors which are - mainly used in networking devices. Devices with these processors - include the Ubiquiti EdgeRouter and the Rhino Labs UTM8. - </para> - </listitem> - </varlistentry> - - <varlistentry arch="mips64el;mipsel"> - <term>Loongson 3</term> - <listitem> - <para> - Devices based on the Loongson 3A and 3B processors are supported. - <!-- TODO list some actual devices here --> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MIPS Malta</term> - <listitem> - <para> - 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> - <para> - There are two Malta kernel flavours: 4kc-malta is built for 32-bit - processors, and 5kc-malta is built for 64-bit processors. - </para> - </listitem> - </varlistentry> - </variablelist> -</para> -<para> - - In addition, other boards which contain <phrase arch="mips;mipsel">MIPS32r2 - or</phrase> MIPS64r2 based processors should also be able to run &debian;, - however kernels for these processors are not built and the &debian; - installer does not directly support them. - -</para> -<para> - -Complete information regarding supported mips/mipsel/mips64el 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> - - Some MIPS machines can be operated in both big and little endian mode. - <phrase arch="mips64el;mipsel"> - For little endian MIPS, please read the documentation for the mipsel and - mips64el architectures. - </phrase> - <phrase arch="mips"> - For big endian MIPS, please read the documentation for the mips architecture. - </phrase> - -</para> - </sect3> - </sect2> - - <sect2 arch="mips;mipsel"><title>Platforms no longer supported by the &debian; &architecture; port</title> -<para> - Since &debian; Stretch, support for all MIPS processors which do not - implement MIPS32 Release 2 have been dropped. Therefore the following - platforms supported in Jessie are no longer supported: - - <variablelist> - <varlistentry> - <term>Loongson 2E and 2F</term> - <listitem> - These are the older Loongson processors. Devices based on them - include the Fuloong Mini-PC and the Lemote Yeeloong laptop. - </listitem> - </varlistentry> - <varlistentry> - <term>SGI IP22</term> - <listitem> - This platform includes the SGI machines Indy, Indigo 2 and Challenge S. - </listitem> - </varlistentry> - <varlistentry> - <term>SGI IP32</term> - <listitem>This platform is generally known as SGI O2.</listitem> - </varlistentry> - <varlistentry> - <term>Broadcom BCM91250</term> - <listitem> - Development board for Broadcom's SiByte core. Also known by its - codename SWARM. - </listitem> - </varlistentry> - </variablelist> -</para> - </sect2> diff --git a/en/hardware/supported/powerpc.xml b/en/hardware/supported/powerpc.xml index 4b9ab56ad..414f82eb5 100644 --- a/en/hardware/supported/powerpc.xml +++ b/en/hardware/supported/powerpc.xml @@ -2,13 +2,13 @@ <!-- $Id$ --> +<!-- <sect2 arch="powerpc"><title>CPU, Main Boards, and Video Support</title> <para> For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported. -<!-- There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot @@ -20,7 +20,6 @@ supporting different CPU variants. 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> @@ -82,7 +81,7 @@ Newer IBM systems using POWER5, POWER6, and POWER7 processors. </para></listitem> </varlistentry> -<!-- + <varlistentry> <term>prep</term> <listitem><para> @@ -101,7 +100,7 @@ currently disabled. </para></listitem> </varlistentry> ---> + </variablelist> </para> @@ -444,6 +443,7 @@ which is Nubus, please see the section above). </sect3> </sect2> +--> <sect2 arch="ppc64el"><title>CPU, Main Boards, and Video Support</title> <!-- Section for ppc64el --> diff --git a/en/hardware/supported/sparc.xml b/en/hardware/supported/sparc.xml deleted file mode 100644 index a8261e45f..000000000 --- a/en/hardware/supported/sparc.xml +++ /dev/null @@ -1,70 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <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> |