path: root/po/tl/hardware.po

# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: d-i-manual_hardware\n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
"POT-Creation-Date: 2012-11-01 19:41+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#: hardware.xml:5
#, no-c-format
msgid "System Requirements"
msgstr ""

#. Tag: para
#: hardware.xml:7
#, no-c-format
msgid ""
"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 &arch-kernel;."
msgstr ""

#. Tag: title
#: hardware.xml:20
#, no-c-format
msgid "Supported Hardware"
msgstr ""

#. Tag: para
#: hardware.xml:21
#, no-c-format
msgid ""
"&debian; does not impose hardware requirements beyond the requirements of "
"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any "
"architecture or platform to which the Linux or kFreeBSD 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-gnu;."
msgstr ""

#. Tag: para
#: hardware.xml:32
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: hardware.xml:41
#, no-c-format
msgid "Supported Architectures"
msgstr ""

#. Tag: para
#: hardware.xml:42
#, no-c-format
msgid ""
"&debian; GNU/Linux &release; supports eleven major architectures and several "
"variations of each architecture known as <quote>flavors</quote>."
msgstr ""

#. Tag: entry
#: hardware.xml:53 hardware.xml:186
#, no-c-format
msgid "Architecture"
msgstr ""

#. Tag: entry
#: hardware.xml:53 hardware.xml:186
#, no-c-format
msgid "&debian; Designation"
msgstr ""

#. Tag: entry
#: hardware.xml:54
#, no-c-format
msgid "Subarchitecture"
msgstr ""

#. Tag: entry
#: hardware.xml:54
#, no-c-format
msgid "Flavor"
msgstr ""

#. Tag: entry
#: hardware.xml:60 hardware.xml:192
#, no-c-format
msgid "Intel x86-based"
msgstr ""

#. Tag: entry
#: hardware.xml:61
#, no-c-format
msgid "i386"
msgstr ""

#. Tag: entry
#: hardware.xml:67 hardware.xml:197
#, no-c-format
msgid "AMD64 &amp; Intel 64"
msgstr ""

#. Tag: entry
#: hardware.xml:68
#, no-c-format
msgid "amd64"
msgstr ""

#. Tag: entry
#: hardware.xml:74
#, no-c-format
msgid "<entry>ARM</entry>"
msgstr ""

#. Tag: entry
#: hardware.xml:75
#, no-c-format
msgid "armel"
msgstr ""

#. Tag: entry
#: hardware.xml:76
#, no-c-format
msgid "Intel IOP32x"
msgstr ""

#. Tag: entry
#: hardware.xml:77
#, no-c-format
msgid "iop32x"
msgstr ""

#. Tag: entry
#: hardware.xml:79
#, no-c-format
msgid "Intel IXP4xx"
msgstr ""

#. Tag: entry
#: hardware.xml:80
#, no-c-format
msgid "ixp4xx"
msgstr ""

#. Tag: entry
#: hardware.xml:82
#, no-c-format
msgid "Marvell Kirkwood"
msgstr ""

#. Tag: entry
#: hardware.xml:83
#, no-c-format
msgid "kirkwood"
msgstr ""

#. Tag: entry
#: hardware.xml:85
#, no-c-format
msgid "Marvell Orion"
msgstr ""

#. Tag: entry
#: hardware.xml:86
#, no-c-format
msgid "orion5x"
msgstr ""

#. Tag: entry
#: hardware.xml:88
#, no-c-format
msgid "<entry>Versatile</entry>"
msgstr ""

#. Tag: entry
#: hardware.xml:89
#, no-c-format
msgid "versatile"
msgstr ""

#. Tag: entry
#: hardware.xml:93
#, no-c-format
msgid "ARM with hardware FPU"
msgstr ""

#. Tag: entry
#: hardware.xml:94
#, no-c-format
msgid "armhf"
msgstr ""

#. Tag: entry
#: hardware.xml:95
#, no-c-format
msgid "Freescale"
msgstr ""

#. Tag: entry
#: hardware.xml:96
#, no-c-format
msgid "<entry>mx5</entry>"
msgstr ""

#. Tag: entry
#: hardware.xml:100
#, no-c-format
msgid "Intel IA-64"
msgstr ""

#. Tag: entry
#: hardware.xml:101
#, no-c-format
msgid "ia64"
msgstr ""

#. Tag: entry
#: hardware.xml:107
#, no-c-format
msgid "MIPS (big endian)"
msgstr ""

#. Tag: entry
#: hardware.xml:108
#, no-c-format
msgid "mips"
msgstr ""

#. Tag: entry
#: hardware.xml:109
#, no-c-format
msgid "SGI IP22 (Indy/Indigo 2)"
msgstr ""

#. Tag: entry
#: hardware.xml:110
#, no-c-format
msgid "r4k-ip22"
msgstr ""

#. Tag: entry
#: hardware.xml:112
#, no-c-format
msgid "SGI IP32 (O2)"
msgstr ""

#. Tag: entry
#: hardware.xml:113
#, no-c-format
msgid "r5k-ip32"
msgstr ""

#. Tag: entry
#: hardware.xml:115 hardware.xml:128
#, no-c-format
msgid "MIPS Malta (32 bit)"
msgstr ""

#. Tag: entry
#: hardware.xml:116 hardware.xml:129
#, no-c-format
msgid "4kc-malta"
msgstr ""

#. Tag: entry
#: hardware.xml:118 hardware.xml:131
#, no-c-format
msgid "MIPS Malta (64 bit)"
msgstr ""

#. Tag: entry
#: hardware.xml:119 hardware.xml:132
#, no-c-format
msgid "5kc-malta"
msgstr ""

#. Tag: entry
#: hardware.xml:123
#, no-c-format
msgid "MIPS (little endian)"
msgstr ""

#. Tag: entry
#: hardware.xml:124
#, no-c-format
msgid "mipsel"
msgstr ""

#. Tag: entry
#: hardware.xml:125
#, no-c-format
msgid "Cobalt"
msgstr ""

#. Tag: entry
#: hardware.xml:126
#, no-c-format
msgid "cobalt"
msgstr ""

#. Tag: entry
#: hardware.xml:136
#, no-c-format
msgid "IBM/Motorola PowerPC"
msgstr ""

#. Tag: entry
#: hardware.xml:137
#, no-c-format
msgid "<entry>powerpc</entry>"
msgstr ""

#. Tag: entry
#: hardware.xml:138
#, no-c-format
msgid "PowerMac"
msgstr ""

#. Tag: entry
#: hardware.xml:139
#, no-c-format
msgid "pmac"
msgstr ""

#. Tag: entry
#: hardware.xml:141
#, no-c-format
msgid "PReP"
msgstr ""

#. Tag: entry
#: hardware.xml:142
#, no-c-format
msgid "prep"
msgstr ""

#. Tag: entry
#: hardware.xml:146
#, no-c-format
msgid "Sun SPARC"
msgstr ""

#. Tag: entry
#: hardware.xml:147
#, no-c-format
msgid "sparc"
msgstr ""

#. Tag: entry
#: hardware.xml:148
#, no-c-format
msgid "<entry>sun4u</entry>"
msgstr ""

#. Tag: entry
#: hardware.xml:149
#, no-c-format
msgid "sparc64"
msgstr ""

#. Tag: entry
#: hardware.xml:151
#, no-c-format
msgid "<entry>sun4v</entry>"
msgstr ""

#. Tag: entry
#: hardware.xml:155
#, no-c-format
msgid "IBM S/390"
msgstr ""

#. Tag: entry
#: hardware.xml:156
#, no-c-format
msgid "s390"
msgstr ""

#. Tag: entry
#: hardware.xml:157 hardware.xml:167
#, no-c-format
msgid "IPL from VM-reader and DASD"
msgstr ""

#. Tag: entry
#: hardware.xml:158 hardware.xml:168
#, no-c-format
msgid "generic"
msgstr ""

#. Tag: entry
#: hardware.xml:160 hardware.xml:170
#, no-c-format
msgid "IPL from tape"
msgstr ""

#. Tag: entry
#: hardware.xml:161 hardware.xml:171
#, no-c-format
msgid "tape"
msgstr ""

#. Tag: entry
#: hardware.xml:165
#, no-c-format
msgid "64bit IBM S/390"
msgstr ""

#. Tag: entry
#: hardware.xml:166
#, no-c-format
msgid "s390x"
msgstr ""

#. Tag: para
#: hardware.xml:176
#, no-c-format
msgid "&debian; GNU/kFreeBSD &release; supports two architectures."
msgstr ""

#. Tag: entry
#: hardware.xml:193
#, no-c-format
msgid "kfreebsd-i386"
msgstr ""

#. Tag: entry
#: hardware.xml:198
#, no-c-format
msgid "kfreebsd-amd64"
msgstr ""

#. Tag: para
#: hardware.xml:203
#, no-c-format
msgid ""
"This document covers installation for the <emphasis>&arch-title;</emphasis> "
"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. 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."
msgstr ""

#. Tag: para
#: hardware.xml:213
#, no-c-format
msgid ""
"The &arch-title; architecture only supports Intel Itanium processors and not "
"the much more common 64-bit processors from the Intel 64 family (including e."
"g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported "
"by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit "
"userland, the <emphasis>i386</emphasis> architecture."
msgstr ""

#. Tag: para
#: hardware.xml:223
#, no-c-format
msgid ""
"This is the first official release of &debian-gnu; 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 using the <emphasis>&arch-kernel;</emphasis> kernel. It can be "
"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-"
"listname; mailing list</ulink> as well."
msgstr ""

#. Tag: title
#: hardware.xml:245
#, no-c-format
msgid "CPU Support"
msgstr ""

#. Tag: para
#: hardware.xml:246
#, no-c-format
msgid "Both AMD64 and Intel 64 processors are supported."
msgstr ""

#. Tag: title
#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464
#: hardware.xml:522 hardware.xml:575
#, no-c-format
msgid "CPU, Main Boards, and Video Support"
msgstr ""

#. Tag: para
#: hardware.xml:273
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:282
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:290
#, no-c-format
msgid "The supported platforms are:"
msgstr ""

#. Tag: term
#: hardware.xml:297
#, no-c-format
msgid "IOP32x"
msgstr ""

#. Tag: para
#: hardware.xml:298
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: term
#: hardware.xml:311
#, no-c-format
msgid "Kirkwood"
msgstr ""

#. Tag: para
#: hardware.xml:312
#, no-c-format
msgid ""
"Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM "
"CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently "
"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-"
"Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug "
"computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-"
"arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x "
"and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, "
"Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
msgstr ""

#. Tag: term
#: hardware.xml:328
#, no-c-format
msgid "Orion5x"
msgstr ""

#. Tag: para
#: hardware.xml:329
#, no-c-format
msgid ""
"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-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-"
"cyrius-mv2120;\">HP mv2120</ulink>."
msgstr ""

#. Tag: term
#: hardware.xml:343
#, no-c-format
msgid "<term>Versatile</term>"
msgstr ""

#. Tag: para
#: hardware.xml:344
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:363
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:382
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: hardware.xml:390 hardware.xml:499
#, no-c-format
msgid "<title>CPU</title>"
msgstr ""

#. Tag: para
#: hardware.xml:391
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:398
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: para
#: hardware.xml:431
#, no-c-format
msgid ""
"If your system has a 64-bit processor from the AMD64 or Intel 64 families, "
"you will probably want to use the installer for the amd64 architecture "
"instead of the installer for the (32-bit) i386 architecture."
msgstr ""

#. Tag: title
#: hardware.xml:440
#, no-c-format
msgid "I/O Bus"
msgstr ""

#. Tag: para
#: hardware.xml:441
#, no-c-format
msgid ""
"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, PCI-X, or VESA Local Bus (VLB, sometimes called "
"the VL bus). Essentially all personal computers sold in recent years use one "
"of these."
msgstr ""

#. Tag: para
#: hardware.xml:465
#, no-c-format
msgid ""
"&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> </"
"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>."
msgstr ""

#. Tag: para
#: hardware.xml:500
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:506
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:523
#, no-c-format
msgid ""
"&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 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> </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>."
msgstr ""

#. Tag: title
#: hardware.xml:551
#, no-c-format
msgid "CPU/Machine types"
msgstr ""

#. Tag: para
#: hardware.xml:553
#, no-c-format
msgid ""
"All MIPS based Cobalt machines are supported with the exception of the Qube "
"2700 (Qube 1)."
msgstr ""

#. Tag: title
#: hardware.xml:561
#, no-c-format
msgid "Supported console options"
msgstr ""

#. Tag: para
#: hardware.xml:562
#, no-c-format
msgid "Cobalt machines use 115200 bps."
msgstr ""

#. Tag: para
#: hardware.xml:576
#, no-c-format
msgid ""
"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and "
"PreP subarchitectures are supported."
msgstr ""

#. Tag: title
#: hardware.xml:597
#, no-c-format
msgid "Kernel Flavours"
msgstr ""

#. Tag: para
#: hardware.xml:599
#, no-c-format
msgid ""
"There are two flavours of the powerpc kernel in &debian;, based on the CPU "
"type:"
msgstr ""

#. Tag: term
#: hardware.xml:606
#, no-c-format
msgid "<term>powerpc</term>"
msgstr ""

#. Tag: para
#: hardware.xml:607
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: term
#: hardware.xml:617
#, no-c-format
msgid "power64"
msgstr ""

#. Tag: para
#: hardware.xml:618
#, no-c-format
msgid "The power64 kernel flavour supports the following CPUs:"
msgstr ""

#. Tag: para
#: hardware.xml:622
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:628
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:633
#, no-c-format
msgid ""
"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 "
"architecture, and use this kernel flavour."
msgstr ""

#. Tag: title
#: hardware.xml:667
#, no-c-format
msgid "Power Macintosh (pmac) subarchitecture"
msgstr ""

#. Tag: para
#: hardware.xml:669
#, no-c-format
msgid ""
"Apple (and briefly a few other manufacturers &mdash; 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."
msgstr ""

#. Tag: para
#: hardware.xml:676
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:684
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:692
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: entry
#: hardware.xml:708 hardware.xml:843 hardware.xml:887 hardware.xml:916
#, no-c-format
msgid "Model Name/Number"
msgstr ""

#. Tag: entry
#: hardware.xml:709
#, no-c-format
msgid "Generation"
msgstr ""

#. Tag: entry
#: hardware.xml:715
#, no-c-format
msgid "Apple"
msgstr ""

#. Tag: entry
#: hardware.xml:716
#, no-c-format
msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
msgstr ""

#. Tag: entry
#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726
#: hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738
#: hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750
#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
#, no-c-format
msgid "NewWorld"
msgstr ""

#. Tag: entry
#: hardware.xml:719
#, no-c-format
msgid "iMac Summer 2000, Early 2001"
msgstr ""

#. Tag: entry
#: hardware.xml:722
#, no-c-format
msgid "iMac G5"
msgstr ""

#. Tag: entry
#: hardware.xml:725
#, no-c-format
msgid "iBook, iBook SE, iBook Dual USB"
msgstr ""

#. Tag: entry
#: hardware.xml:728
#, no-c-format
msgid "iBook2"
msgstr ""

#. Tag: entry
#: hardware.xml:731
#, no-c-format
msgid "iBook G4"
msgstr ""

#. Tag: entry
#: hardware.xml:734
#, no-c-format
msgid "Power Macintosh Blue and White (B&amp;W) G3"
msgstr ""

#. Tag: entry
#: hardware.xml:737
#, no-c-format
msgid "Power Macintosh G4 PCI, AGP, Cube"
msgstr ""

#. Tag: entry
#: hardware.xml:740
#, no-c-format
msgid "Power Macintosh G4 Gigabit Ethernet"
msgstr ""

#. Tag: entry
#: hardware.xml:743
#, no-c-format
msgid "Power Macintosh G4 Digital Audio, Quicksilver"
msgstr ""

#. Tag: entry
#: hardware.xml:746
#, no-c-format
msgid "Power Macintosh G5"
msgstr ""

#. Tag: entry
#: hardware.xml:749
#, no-c-format
msgid "PowerBook G3 FireWire Pismo (2000)"
msgstr ""

#. Tag: entry
#: hardware.xml:752
#, no-c-format
msgid "PowerBook G3 Lombard (1999)"
msgstr ""

#. Tag: entry
#: hardware.xml:755
#, no-c-format
msgid "PowerBook G4 Titanium"
msgstr ""

#. Tag: entry
#: hardware.xml:758
#, no-c-format
msgid "PowerBook G4 Aluminum"
msgstr ""

#. Tag: entry
#: hardware.xml:761
#, no-c-format
msgid "Xserve G5"
msgstr ""

#. Tag: entry
#: hardware.xml:764
#, no-c-format
msgid "Performa 4400, 54xx, 5500"
msgstr ""

#. Tag: entry
#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774
#: hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786
#: hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798
#: hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819
#: hardware.xml:825
#, no-c-format
msgid "OldWorld"
msgstr ""

#. Tag: entry
#: hardware.xml:767
#, no-c-format
msgid "Performa 6360, 6400, 6500"
msgstr ""

#. Tag: entry
#: hardware.xml:770
#, no-c-format
msgid "Power Macintosh 4400, 5400"
msgstr ""

#. Tag: entry
#: hardware.xml:773
#, no-c-format
msgid "Power Macintosh 7200, 7300, 7500, 7600"
msgstr ""

#. Tag: entry
#: hardware.xml:776
#, no-c-format
msgid "Power Macintosh 8200, 8500, 8600"
msgstr ""

#. Tag: entry
#: hardware.xml:779
#, no-c-format
msgid "Power Macintosh 9500, 9600"
msgstr ""

#. Tag: entry
#: hardware.xml:782
#, no-c-format
msgid "Power Macintosh (Beige) G3 Minitower"
msgstr ""

#. Tag: entry
#: hardware.xml:785
#, no-c-format
msgid "Power Macintosh (Beige) Desktop, All-in-One"
msgstr ""

#. Tag: entry
#: hardware.xml:788
#, no-c-format
msgid "PowerBook 2400, 3400, 3500"
msgstr ""

#. Tag: entry
#: hardware.xml:791
#, no-c-format
msgid "PowerBook G3 Wallstreet (1998)"
msgstr ""

#. Tag: entry
#: hardware.xml:794
#, no-c-format
msgid "Twentieth Anniversary Macintosh"
msgstr ""

#. Tag: entry
#: hardware.xml:797
#, no-c-format
msgid "Workgroup Server 7250, 7350, 8550, 9650, G3"
msgstr ""

#. Tag: entry
#: hardware.xml:802
#, no-c-format
msgid "Power Computing"
msgstr ""

#. Tag: entry
#: hardware.xml:803
#, no-c-format
msgid "PowerBase, PowerTower / Pro, PowerWave"
msgstr ""

#. Tag: entry
#: hardware.xml:806
#, no-c-format
msgid "PowerCenter / Pro, PowerCurve"
msgstr ""

#. Tag: entry
#: hardware.xml:811
#, no-c-format
msgid "UMAX"
msgstr ""

#. Tag: entry
#: hardware.xml:812
#, no-c-format
msgid "C500, C600, J700, S900"
msgstr ""

#. Tag: entry
#: hardware.xml:817
#, no-c-format
msgid "<entry>APS</entry>"
msgstr ""

#. Tag: entry
#: hardware.xml:818
#, no-c-format
msgid "APS Tech M*Power 604e/2000"
msgstr ""

#. Tag: entry
#: hardware.xml:823 hardware.xml:849
#, no-c-format
msgid "Motorola"
msgstr ""

#. Tag: entry
#: hardware.xml:824
#, no-c-format
msgid "Starmax 3000, 4000, 5000, 5500"
msgstr ""

#. Tag: title
#: hardware.xml:833
#, no-c-format
msgid "PReP subarchitecture"
msgstr ""

#. Tag: entry
#: hardware.xml:850
#, no-c-format
msgid "Firepower, PowerStack Series E, PowerStack II"
msgstr ""

#. Tag: entry
#: hardware.xml:852
#, no-c-format
msgid "MPC 7xx, 8xx"
msgstr ""

#. Tag: entry
#: hardware.xml:854
#, no-c-format
msgid "MTX, MTX+"
msgstr ""

#. Tag: entry
#: hardware.xml:856
#, no-c-format
msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx"
msgstr ""

#. Tag: entry
#: hardware.xml:858
#, no-c-format
msgid "MCP(N)750"
msgstr ""

#. Tag: entry
#: hardware.xml:862 hardware.xml:893
#, no-c-format
msgid "IBM RS/6000"
msgstr ""

#. Tag: entry
#: hardware.xml:863
#, no-c-format
msgid "40P, 43P"
msgstr ""

#. Tag: entry
#: hardware.xml:865
#, no-c-format
msgid "Power 830/850/860 (6070, 6050)"
msgstr ""

#. Tag: entry
#: hardware.xml:867
#, no-c-format
msgid "6030, 7025, 7043"
msgstr ""

#. Tag: entry
#: hardware.xml:869
#, no-c-format
msgid "p640"
msgstr ""

#. Tag: title
#: hardware.xml:877
#, no-c-format
msgid "CHRP subarchitecture (unsupported)"
msgstr ""

#. Tag: entry
#: hardware.xml:894
#, no-c-format
msgid "B50, 43P-150, 44P"
msgstr ""

#. Tag: entry
#: hardware.xml:897
#, no-c-format
msgid "Genesi"
msgstr ""

#. Tag: entry
#: hardware.xml:898
#, no-c-format
msgid "Pegasos I, Pegasos II"
msgstr ""

#. Tag: title
#: hardware.xml:906
#, no-c-format
msgid "APUS subarchitecture (unsupported)"
msgstr ""

#. Tag: entry
#: hardware.xml:922
#, no-c-format
msgid "Amiga Power-UP Systems (APUS)"
msgstr ""

#. Tag: entry
#: hardware.xml:923
#, no-c-format
msgid "A1200, A3000, A4000"
msgstr ""

#. Tag: title
#: hardware.xml:931
#, no-c-format
msgid "Nubus PowerMac subarchitecture (unsupported)"
msgstr ""

#. Tag: para
#: hardware.xml:933
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: title
#: hardware.xml:970
#, no-c-format
msgid "Non-PowerPC Macs"
msgstr ""

#. Tag: para
#: hardware.xml:972
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:981
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:989
#, no-c-format
msgid ""
"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)."
msgstr ""

#. Tag: title
#: hardware.xml:1005
#, no-c-format
msgid "zSeries and System z machine types"
msgstr ""

#. Tag: para
#: hardware.xml:1006
#, no-c-format
msgid ""
"Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. "
"Your machine needs to support the z/Architecture, 64-bit support is "
"mandatory. The userland of the s390 port is still compiled for ESA/390, "
"though. All zSeries and System z hardware is fully supported. &arch-title; "
"support software is included from the kernel 3.1 development stream. The "
"most current information about IBM's Linux support can be found at the "
"<ulink url=\"http://www.ibm.com/developerworks/linux/linux390/"
"development_technical.html\"> Linux on <trademark class=\"registered"
"\">System z</trademark> page on developerWorks</ulink>."
msgstr ""

#. Tag: title
#: hardware.xml:1023
#, no-c-format
msgid "PAV and HyperPAV"
msgstr ""

#. Tag: para
#: hardware.xml:1024
#, no-c-format
msgid ""
"PAV and HyperPAV are supported transparently, multipathing is not needed to "
"take advantage of these storage system features. Be sure to configure the "
"devices during DASD device selection. The alias devices will not be offered "
"neither for formatting, partitioning nor direct use."
msgstr ""

#. Tag: title
#: hardware.xml:1040
#, no-c-format
msgid "CPU and Main Boards Support"
msgstr ""

#. Tag: para
#: hardware.xml:1041
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: term
#: hardware.xml:1052
#, no-c-format
msgid "sun4, sun4c, sun4d, sun4m"
msgstr ""

#. Tag: para
#: hardware.xml:1054
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: para
#: hardware.xml:1061
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: term
#: hardware.xml:1071
#, no-c-format
msgid "<term>sun4u</term>"
msgstr ""

#. Tag: para
#: hardware.xml:1073
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: term
#: hardware.xml:1086
#, no-c-format
msgid "<term>sun4v</term>"
msgstr ""

#. Tag: para
#: hardware.xml:1088
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1099
#, no-c-format
msgid ""
"Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are "
"not supported due to lack of support in the Linux kernel."
msgstr ""

#. Tag: title
#: hardware.xml:1108
#, no-c-format
msgid "Laptops"
msgstr ""

#. Tag: para
#: hardware.xml:1109
#, no-c-format
msgid ""
"From a technical point of view, laptops are normal PCs, so all information "
"regarding PC systems applies to laptops as well. Installations on laptops "
"nowadays usually work out of the box, including things like automatically "
"suspending the system on closing the lid and laptop specfic hardware buttons "
"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). "
"Nonetheless sometimes the hardware vendors use specialized or proprietary "
"hardware for some laptop-specific functions which might 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>."
msgstr ""

#. Tag: title
#: hardware.xml:1126 hardware.xml:1146 hardware.xml:1174 hardware.xml:1197
#, no-c-format
msgid "Multiple Processors"
msgstr ""

#. Tag: para
#: hardware.xml:1127
#, no-c-format
msgid ""
"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
"quote> or SMP &mdash; is available for this architecture. Having multiple "
"processors in a computer was originally only an issue for high-end server "
"systems but has become quite common in recent years even for rather low-end "
"desktop computers and laptops with the introduction of so called "
"<quote>multi-core</quote> processors. These contain two or more processor "
"units, called <quote>cores</quote>, in one physical chip."
msgstr ""

#. Tag: para
#: hardware.xml:1137
#, no-c-format
msgid ""
"The standard &debian; &release; kernel image has been compiled with SMP "
"support. It is also usable on non-SMP systems without problems."
msgstr ""

#. Tag: para
#: hardware.xml:1148
#, no-c-format
msgid ""
"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
"quote> or SMP &mdash; 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."
msgstr ""

#. Tag: para
#: hardware.xml:1157
#, no-c-format
msgid ""
"Having multiple processors in a computer was originally only an issue for "
"high-end server systems but has become quite common in recent years even for "
"rather low-end desktop computers and laptops with the introduction of so "
"called <quote>multi-core</quote> processors. These contain two or more "
"processor units, called <quote>cores</quote>, in one physical chip."
msgstr ""

#. Tag: para
#: hardware.xml:1165
#, no-c-format
msgid ""
"The 486 flavour of the &debian; kernel image packages for &arch-title; is "
"not compiled with SMP support."
msgstr ""

#. Tag: para
#: hardware.xml:1175
#, no-c-format
msgid ""
"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
"quote> or SMP &mdash; 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 only the first CPU."
msgstr ""

#. Tag: para
#: hardware.xml:1184
#, no-c-format
msgid ""
"In order to take advantage of multiple processors, you'll have to replace "
"the standard &debian; kernel.<phrase arch=\"linux-any\"> 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.</phrase>"
msgstr ""

#. Tag: para
#: hardware.xml:1198
#, no-c-format
msgid ""
"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
"quote> or SMP &mdash; 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."
msgstr ""

#. Tag: para
#: hardware.xml:1208
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1214
#, no-c-format
msgid ""
"You can also build your own customized kernel to support SMP.<phrase arch="
"\"linux-any\"> 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.</phrase>"
msgstr ""

#. Tag: title
#: hardware.xml:1225
#, no-c-format
msgid "Graphics Card Support"
msgstr ""

#. Tag: para
#: hardware.xml:1226
#, no-c-format
msgid ""
"&debian;'s support for graphical interfaces is determined by the underlying "
"support found in X.Org's X11 system. On modern PCs, having a graphical "
"display usually works out of the box. Whether advanced graphics card "
"features such as 3D-hardware acceleration or hardware-accelerated video are "
"available, depends on the actual graphics hardware used in the system and in "
"some cases on the installation of additional <quote>firmware</quote> images "
"(see <xref linkend=\"hardware-firmware\"/>). In very few cases there have "
"been reports about hardware on which installation of additional graphics "
"card firmware was required even for basic graphics support, but these have "
"been rare exceptions."
msgstr ""

#. Tag: para
#: hardware.xml:1239
#, no-c-format
msgid ""
"Details on supported graphics cards and pointing devices can be found at "
"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org "
"version &x11ver;."
msgstr ""

#. Tag: para
#: hardware.xml:1244
#, no-c-format
msgid "The X.Org X Window System is only supported on the SGI Indy and the O2."
msgstr ""

#. Tag: para
#: hardware.xml:1249
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1259
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: hardware.xml:1281
#, no-c-format
msgid "Network Connectivity Hardware"
msgstr ""

#. Tag: para
#: hardware.xml:1282
#, no-c-format
msgid ""
"Almost any network interface card (NIC) supported by the &arch-kernel; "
"kernel should also be supported by the installation system; drivers should "
"normally be loaded automatically. <phrase arch=\"x86\">This includes most "
"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> "
"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
msgstr ""

#. Tag: para
#: hardware.xml:1292
#, no-c-format
msgid ""
"This includes a lot of generic PCI cards (for systems that have PCI) and the "
"following NICs from Sun:"
msgstr ""

#. Tag: para
#: hardware.xml:1298
#, no-c-format
msgid "Sun LANCE"
msgstr ""

#. Tag: para
#: hardware.xml:1303
#, no-c-format
msgid "Sun Happy Meal"
msgstr ""

#. Tag: para
#: hardware.xml:1308
#, no-c-format
msgid "Sun BigMAC"
msgstr ""

#. Tag: para
#: hardware.xml:1313
#, no-c-format
msgid "Sun QuadEthernet"
msgstr ""

#. Tag: para
#: hardware.xml:1318
#, no-c-format
msgid "MyriCOM Gigabit Ethernet"
msgstr ""

#. Tag: para
#: hardware.xml:1325
#, no-c-format
msgid "The list of supported network devices is:"
msgstr ""

#. Tag: para
#: hardware.xml:1330
#, no-c-format
msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
msgstr ""

#. Tag: para
#: hardware.xml:1335
#, no-c-format
msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
msgstr ""

#. Tag: para
#: hardware.xml:1340
#, no-c-format
msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
msgstr ""

#. Tag: para
#: hardware.xml:1349
#, no-c-format
msgid ""
"On &arch-title;, most built-in Ethernet devices are supported and modules "
"for additional PCI and USB devices are provided."
msgstr ""

#. Tag: para
#: hardware.xml:1354
#, no-c-format
msgid "ISDN is supported, but not during the installation."
msgstr ""

#. Tag: title
#: hardware.xml:1361
#, no-c-format
msgid "Wireless Network Cards"
msgstr ""

#. Tag: para
#: hardware.xml:1362
#, no-c-format
msgid ""
"Wireless networking is in general supported as well and a growing number of "
"wireless adapters are supported by the official &arch-kernel; kernel, "
"although many of them do require firmware to be loaded."
msgstr ""

#. Tag: para
#: hardware.xml:1369
#, no-c-format
msgid ""
"If firmware is needed, the installer will prompt you to load firmware. See "
"<xref linkend=\"loading-firmware\"/> for detailed information on how to load "
"firmware during the installation."
msgstr ""

#. Tag: para
#: hardware.xml:1374
#, no-c-format
msgid ""
"Wireless NICs that are not supported by the official &arch-kernel; kernel "
"can generally be made to work under &debian-gnu;, but are not supported "
"during the installation."
msgstr ""

#. Tag: para
#: hardware.xml:1379
#, no-c-format
msgid ""
"If there is a problem with wireless and there is no other NIC you can use "
"during the installation, it is still possible to install &debian-gnu; 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."
msgstr ""

#. Tag: para
#: hardware.xml:1389
#, no-c-format
msgid ""
"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>"
msgstr ""

#. Tag: title
#: hardware.xml:1403
#, no-c-format
msgid "Known Issues for &arch-title;"
msgstr ""

#. Tag: para
#: hardware.xml:1404
#, no-c-format
msgid ""
"There are a couple of issues with specific network cards that are worth "
"mentioning here."
msgstr ""

#. Tag: title
#: hardware.xml:1411
#, no-c-format
msgid "Conflict between tulip and dfme drivers"
msgstr ""

#. Tag: para
#: hardware.xml:1413
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1423
#, no-c-format
msgid ""
"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\"/>."
msgstr ""

#. Tag: para
#: hardware.xml:1431
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: hardware.xml:1444
#, no-c-format
msgid "Sun B100 blade"
msgstr ""

#. Tag: para
#: hardware.xml:1446
#, no-c-format
msgid ""
"The <literal>cassini</literal> network driver does not work with Sun B100 "
"blade systems."
msgstr ""

#. Tag: title
#: hardware.xml:1461
#, no-c-format
msgid "Braille Displays"
msgstr ""

#. Tag: para
#: hardware.xml:1462
#, no-c-format
msgid ""
"Support for braille displays is determined by the underlying support found "
"in <classname>brltty</classname>. Most displays work under "
"<classname>brltty</classname>, connected via either a serial port, USB or "
"bluetooth. Details on supported braille devices can be found on the <ulink "
"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-"
"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
msgstr ""

#. Tag: title
#: hardware.xml:1476
#, no-c-format
msgid "Hardware Speech Synthesis"
msgstr ""

#. Tag: para
#: hardware.xml:1477
#, no-c-format
msgid ""
"Support for hardware speech synthesis devices is determined by the "
"underlying support found in <classname>speakup</classname>. "
"<classname>speakup</classname> only supports integrated boards and external "
"devices connected to a serial port (no USB, serial-to-USB or PCI adapters "
"are supported). Details on supported hardware speech synthesis devices can "
"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> "
"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</"
"classname> version &speakupver;."
msgstr ""

#. Tag: title
#: hardware.xml:1497
#, no-c-format
msgid "Peripherals and Other Hardware"
msgstr ""

#. Tag: para
#: hardware.xml:1498
#, no-c-format
msgid ""
"&arch-kernel; 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."
msgstr ""

#. Tag: para
#: hardware.xml:1504
#, no-c-format
msgid ""
"USB hardware generally works fine. On some very old PC systems some USB "
"keyboards may require additional configuration (see <xref linkend=\"hardware-"
"issues\"/>). On modern PCs, USB keyboards and mice work without requiring "
"any specific configuration."
msgstr ""

#. Tag: para
#: hardware.xml:1513
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1519
#, no-c-format
msgid ""
"The Cobalt RaQ has no support for additional devices but the Qube has one "
"PCI slot."
msgstr ""

#. Tag: title
#: hardware.xml:1531
#, no-c-format
msgid "Devices Requiring Firmware"
msgstr ""

#. Tag: para
#: hardware.xml:1532
#, no-c-format
msgid ""
"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. With many graphics cards, basic functionality is available without "
"additional firmware, but the use of advanced features requires an "
"appropriate firmware file to be installed in the system."
msgstr ""

#. Tag: para
#: hardware.xml:1543
#, no-c-format
msgid ""
"On many older devices which require firmware to work, the firmware file was "
"permanently placed in an EEPROM/Flash chip on the device itself by the "
"manufacturer. Nowadays most new devices do not have the firmware embedded "
"this way anymore, so the firmware file must be uploaded into the device by "
"the host operating system every time the system boots."
msgstr ""

#. Tag: para
#: hardware.xml:1551
#, no-c-format
msgid ""
"In most cases firmware is non-free according to the criteria used by the "
"&debian-gnu; 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-gnu; legally can distribute the firmware, it "
"will often be available as a separate package from the non-free section of "
"the archive."
msgstr ""

#. Tag: para
#: hardware.xml:1560
#, no-c-format
msgid ""
"However, this does not mean that such hardware cannot be used during an "
"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading "
"firmware files or packages containing firmware from a removable medium, such "
"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed "
"information on how to load firmware files or packages during the "
"installation."
msgstr ""

#. Tag: para
#: hardware.xml:1569
#, no-c-format
msgid ""
"If the &d-i; prompts for a firmware file and you do not have this firmware "
"file available or do not want to install a non-free firmware file on your "
"system, you can try to proceed without loading the firmware. There are "
"several cases where a driver prompts for additional firmware because it may "
"be needed under certain circumstances, but the device does work without it "
"on most systems (this e.g. happens with certain network cards using the tg3 "
"driver)."
msgstr ""

#. Tag: title
#: hardware.xml:1586
#, no-c-format
msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;"
msgstr ""

#. Tag: para
#: hardware.xml:1588
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1596
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1604
#, no-c-format
msgid ""
"Whether or not you are purchasing a system with &arch-kernel; bundled, or "
"even a used system, it is still important to check that your hardware is "
"supported by the &arch-kernel; kernel. Check if your hardware is listed in "
"the references found above. Let your salesperson (if any) know that you're "
"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware "
"vendors."
msgstr ""

#. Tag: title
#: hardware.xml:1615
#, no-c-format
msgid "Avoid Proprietary or Closed Hardware"
msgstr ""

#. Tag: para
#: hardware.xml:1616
#, no-c-format
msgid ""
"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 driver's "
"source code, which is one of the central elements of free software. Since we "
"haven't been granted access to usable documentation on these devices, they "
"simply won't work under &arch-kernel;."
msgstr ""

#. Tag: para
#: hardware.xml:1626
#, no-c-format
msgid ""
"In many cases there are standards (or at least some de-facto standards) "
"describing how an operating system and its device drivers communicate with a "
"certain class of devices. All devices which comply to such a (de-facto-)"
"standard can be used with a single generic device driver and no device-"
"specific drivers are required. With some kinds of hardware (e.g. USB "
"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB "
"mass storage devices like USB flash disks and memory card readers) this "
"works very well and practically every device sold in the market is standards-"
"compliant."
msgstr ""

#. Tag: para
#: hardware.xml:1638
#, no-c-format
msgid ""
"In other fields, among them e.g. printers, this is unfortunately not the "
"case. While there are many printers which can be addressed via a small set "
"of (de-facto-)standard control languages and therefore can be made to work "
"without problems in any operating system, there are quite a few models which "
"only understand proprietary control commands for which no usable "
"documentation is available and therefore either cannot be used at all on "
"free operating systems or can only be used with a vendor-supplied closed-"
"source driver."
msgstr ""

#. Tag: para
#: hardware.xml:1649
#, no-c-format
msgid ""
"Even if there is a vendor-provided closed-source driver for such hardware "
"when purchasing the device, the practical lifespan of the device is limited "
"by driver availability. Nowadays product cycles have become short and it is "
"not uncommon that a short time after a consumer device has ceased "
"production, no driver updates get made available any more by the "
"manufacturer. If the old closed-source driver does not work anymore after a "
"system update, an otherwise perfectly working device becomes unusable due to "
"lacking driver support and there is nothing that can be done in this case. "
"You should therefore avoid buying closed hardware in the first place, "
"regardless of the operating system you want to use it with."
msgstr ""

#. Tag: para
#: hardware.xml:1662
#, no-c-format
msgid ""
"You can help improve this situation by encouraging manufacturers of closed "
"hardware to release the documentation and other resources necessary for us "
"to provide free drivers for their hardware."
msgstr ""

#. Tag: title
#: hardware.xml:1677
#, no-c-format
msgid "Installation Media"
msgstr ""

#. Tag: para
#: hardware.xml:1679
#, no-c-format
msgid ""
"This section will help you determine which different media types you can use "
"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."
msgstr ""

#. Tag: title
#: hardware.xml:1689
#, no-c-format
msgid "Floppies"
msgstr ""

#. Tag: para
#: hardware.xml:1690
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1696
#, no-c-format
msgid "For CHRP, floppy support is currently broken."
msgstr ""

#. Tag: title
#: hardware.xml:1703
#, no-c-format
msgid "CD-ROM/DVD-ROM"
msgstr ""

#. Tag: para
#: hardware.xml:1705
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1711
#, no-c-format
msgid "CD-ROM based installation is supported for most architectures."
msgstr ""

#. Tag: para
#: hardware.xml:1715
#, no-c-format
msgid "On PCs SATA, IDE/ATAPI and SCSI CD-ROMs are supported."
msgstr ""

#. Tag: para
#: hardware.xml:1719
#, no-c-format
msgid ""
"USB CD-ROM drives are also supported, as are FireWire devices that are "
"supported by the ohci1394 and sbp2 drivers."
msgstr ""

#. Tag: para
#: hardware.xml:1724
#, no-c-format
msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
msgstr ""

#. Tag: para
#: hardware.xml:1728
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: hardware.xml:1742
#, no-c-format
msgid "USB Memory Stick"
msgstr ""

#. Tag: para
#: hardware.xml:1744
#, no-c-format
msgid ""
"USB flash disks a.k.a. USB memory sticks have become a commonly used and "
"cheap storage device. Most modern computer systems also allow booting the &d-"
"i; from such a stick. Many modern computer systems, in particular netbooks "
"and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting "
"from USB media ist the standard way of installing a new operating system on "
"them."
msgstr ""

#. Tag: title
#: hardware.xml:1756
#, no-c-format
msgid "Network"
msgstr ""

#. Tag: para
#: hardware.xml:1758
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1768
#, no-c-format
msgid ""
"You can also <emphasis>boot</emphasis> the installation system over the "
"network without needing any local media like CDs/DVDs or USB sticks. If you "
"already have a netboot-infrastructure available (i.e. you are already "
"running DHCP and TFTP services in your network), this allows an easy and "
"fast 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\">This is the "
"preferred installation technique for &arch-title;.</phrase>"
msgstr ""

#. Tag: para
#: hardware.xml:1781
#, no-c-format
msgid ""
"Diskless installation, using network booting from a local area network and "
"NFS-mounting of all local filesystems, is another option."
msgstr ""

#. Tag: title
#: hardware.xml:1790
#, no-c-format
msgid "Hard Disk"
msgstr ""

#. Tag: para
#: hardware.xml:1792
#, no-c-format
msgid ""
"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. This method is only recommended for "
"special cases when no other installation method is available."
msgstr ""

#. Tag: para
#: hardware.xml:1799
#, no-c-format
msgid ""
"Although the &arch-title; does not allow booting from SunOS (Solaris), you "
"can install from a SunOS partition (UFS slices)."
msgstr ""

#. Tag: title
#: hardware.xml:1808
#, no-c-format
msgid "Un*x or GNU system"
msgstr ""

#. Tag: para
#: hardware.xml:1810
#, no-c-format
msgid ""
"If you are running another Unix-like system, you could use it to install "
"&debian-gnu; 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\"/>. This "
"installation method is only recommended for advanced users when no other "
"installation method is available."
msgstr ""

#. Tag: title
#: hardware.xml:1823
#, no-c-format
msgid "Supported Storage Systems"
msgstr ""

#. Tag: para
#: hardware.xml:1825
#, no-c-format
msgid ""
"The &debian; installer contains a kernel which is built to maximize the "
"number of systems it runs on."
msgstr ""

#. Tag: para
#: hardware.xml:1829
#, no-c-format
msgid ""
"Generally, the &debian; installation system includes support for IDE (also "
"known as PATA) drives, SATA and SCSI controllers and drives, USB, and "
"FireWire. The supported file systems include FAT, Win-32 FAT extensions "
"(VFAT) and NTFS."
msgstr ""

#. Tag: para
#: hardware.xml:1846
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1879
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1885
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: hardware.xml:1891
#, no-c-format
msgid ""
"Any storage system supported by the Linux kernel is also supported by the "
"boot system."
msgstr ""

#. Tag: para
#: hardware.xml:1896
#, no-c-format
msgid ""
"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)."
msgstr ""

#. Tag: title
#: hardware.xml:1913
#, no-c-format
msgid "Memory and Disk Space Requirements"
msgstr ""

#. Tag: para
#: hardware.xml:1915
#, no-c-format
msgid ""
"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\"/>."
msgstr ""

#. Tag: para
#: hardware.xml:1922
#, no-c-format
msgid ""
"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."
msgstr ""