# SOME DESCRIPTIVE TITLE. # FIRST AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: d-i-manual_hardware\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2014-10-05 18:15+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \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, " "gcc, etc. have been ported, and for which a &debian; port " "exists, can run &debian;. Please refer to the Ports pages at 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 eight major architectures and several " "variations of each architecture known as flavors." msgstr "" #. Tag: entry #: hardware.xml:53 hardware.xml:197 #, no-c-format msgid "Architecture" msgstr "" #. Tag: entry #: hardware.xml:53 hardware.xml:197 #, 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:203 #, 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:208 #, no-c-format msgid "AMD64 & Intel 64" msgstr "" #. Tag: entry #: hardware.xml:68 #, no-c-format msgid "amd64" msgstr "" #. Tag: entry #: hardware.xml:74 #, no-c-format msgid "ARM" msgstr "" #. Tag: entry #: hardware.xml:75 #, no-c-format msgid "armel" msgstr "" #. Tag: entry #: hardware.xml:76 #, no-c-format msgid "Intel IXP4xx" msgstr "" #. Tag: entry #: hardware.xml:77 #, no-c-format msgid "ixp4xx" msgstr "" #. Tag: entry #: hardware.xml:79 #, no-c-format msgid "Marvell Kirkwood" msgstr "" #. Tag: entry #: hardware.xml:80 #, no-c-format msgid "kirkwood" msgstr "" #. Tag: entry #: hardware.xml:82 #, no-c-format msgid "Marvell Orion" msgstr "" #. Tag: entry #: hardware.xml:83 #, no-c-format msgid "orion5x" msgstr "" #. Tag: entry #: hardware.xml:90 #, no-c-format msgid "Versatile" msgstr "" #. Tag: entry #: hardware.xml:91 #, no-c-format msgid "versatile" msgstr "" #. Tag: entry #: hardware.xml:95 #, no-c-format msgid "ARM with hardware FPU" msgstr "" #. Tag: entry #: hardware.xml:96 #, no-c-format msgid "armhf" msgstr "" #. Tag: entry #: hardware.xml:101 #, no-c-format msgid "multiplatform" msgstr "" #. Tag: entry #: hardware.xml:102 #, no-c-format msgid "armmp" msgstr "" #. Tag: entry #: hardware.xml:104 #, no-c-format msgid "multiplatform for LPAE-capable systems" msgstr "" #. Tag: entry #: hardware.xml:105 #, no-c-format msgid "armmp-lpae" msgstr "" #. Tag: entry #: hardware.xml:109 #, no-c-format msgid "64bit ARM" msgstr "" #. Tag: entry #: hardware.xml:110 #, no-c-format msgid "arm64" msgstr "" #. Tag: entry #: hardware.xml:116 #, no-c-format msgid "MIPS (big endian)" msgstr "" #. Tag: entry #: hardware.xml:117 #, no-c-format msgid "mips" msgstr "" #. Tag: entry #: hardware.xml:118 #, no-c-format msgid "SGI IP22 (Indy/Indigo 2)" msgstr "" #. Tag: entry #: hardware.xml:119 #, no-c-format msgid "r4k-ip22" msgstr "" #. Tag: entry #: hardware.xml:121 #, no-c-format msgid "SGI IP32 (O2)" msgstr "" #. Tag: entry #: hardware.xml:122 #, no-c-format msgid "r5k-ip32" msgstr "" #. Tag: entry #: hardware.xml:124 hardware.xml:134 #, no-c-format msgid "MIPS Malta (32 bit)" msgstr "" #. Tag: entry #: hardware.xml:125 hardware.xml:135 #, no-c-format msgid "4kc-malta" msgstr "" #. Tag: entry #: hardware.xml:127 hardware.xml:137 #, no-c-format msgid "MIPS Malta (64 bit)" msgstr "" #. Tag: entry #: hardware.xml:128 hardware.xml:138 #, no-c-format msgid "5kc-malta" msgstr "" #. Tag: entry #: hardware.xml:132 #, no-c-format msgid "MIPS (little endian)" msgstr "" #. Tag: entry #: hardware.xml:133 #, no-c-format msgid "mipsel" msgstr "" #. Tag: entry #: hardware.xml:142 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry #: hardware.xml:143 #, no-c-format msgid "powerpc" msgstr "" #. Tag: entry #: hardware.xml:144 #, no-c-format msgid "PowerMac" msgstr "" #. Tag: entry #: hardware.xml:145 #, no-c-format msgid "pmac" msgstr "" #. Tag: entry #: hardware.xml:147 #, no-c-format msgid "PReP" msgstr "" #. Tag: entry #: hardware.xml:148 #, no-c-format msgid "prep" msgstr "" #. Tag: entry #: hardware.xml:152 #, no-c-format msgid "IBM PowerPC (little endian)" msgstr "" #. Tag: entry #: hardware.xml:153 #, no-c-format msgid "ppc64el" msgstr "" #. Tag: entry #: hardware.xml:179 #, no-c-format msgid "64bit IBM S/390" msgstr "" #. Tag: entry #: hardware.xml:180 #, no-c-format msgid "s390x" msgstr "" #. Tag: entry #: hardware.xml:181 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry #: hardware.xml:182 #, no-c-format msgid "generic" msgstr "" #. Tag: para #: hardware.xml:187 #, no-c-format msgid "&debian; GNU/kFreeBSD &release; supports two architectures." msgstr "" #. Tag: entry #: hardware.xml:204 #, no-c-format msgid "kfreebsd-i386" msgstr "" #. Tag: entry #: hardware.xml:209 #, no-c-format msgid "kfreebsd-amd64" msgstr "" #. Tag: para #: hardware.xml:214 #, no-c-format msgid "" "This document covers installation for the &arch-title; " "architecture using the &arch-kernel; kernel. If you are " "looking for information on any of the other &debian;-supported architectures " "take a look at the &debian;-" "Ports pages." msgstr "" #. Tag: para #: hardware.xml:224 #, 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 D and the Core2 Duo). Those systems are supported " "by the amd64 architecture or, if you prefer a 32-bit " "userland, the i386 architecture." msgstr "" #. Tag: para #: hardware.xml:234 #, 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 Bug Tracking System to report any " "problems; make sure to mention the fact that the bug is on the &arch-title; " "platform using the &arch-kernel; kernel. It can be " "necessary to use the debian-&arch-" "listname; mailing list as well." msgstr "" #. Tag: title #: hardware.xml:256 #, no-c-format msgid "CPU Support" msgstr "" #. Tag: para #: hardware.xml:257 #, no-c-format msgid "Both AMD64 and Intel 64 processors are supported." msgstr "" #. Tag: title #: hardware.xml:282 hardware.xml:603 hardware.xml:622 hardware.xml:701 #: hardware.xml:759 hardware.xml:789 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para #: hardware.xml:284 #, no-c-format msgid "" "ARM systems are a lot more heterogenous than the i386/amd64-based PC " "architecture, where all systems share a common system firmware (BIOS or/and " "UEFI) which handles the board-specific basic hardware initialization in a " "standardized way. The ARM architecture is used mainly in so-called " "systems-on-chip (SOCs). These SOCs are designed by many " "different companies with vastly varying hardware components even for the " "very basic functionality required to bring the system up. Systems using them " "usually lack a common system firmware interface and as a result, on ARM " "systems the Linux kernel has to take care of many system-specific low-level " "issues which are handled by the mainboard's BIOS in the PC world." msgstr "" #. Tag: para #: hardware.xml:301 #, no-c-format msgid "" "At the beginning of the ARM support in the Linux kernel, this resulted in " "the requirement of having a seperate kernel for each ARM system in contrast " "to the one-fits-all kernel for PC systems. As this approach " "does not scale to a large number of different systems, work has started to " "be able to provide a single ARM kernel that can run on different ARM " "systems. Support for newer ARM systems gets implemented in a way that allows " "the use of such a multiplatform kernel, but for several older systems a " "seperate specific kernel is still required. Because of this, the standard " "&debian; distribution only supports installation on a selected number of " "older ARM systems in addition to the newer systems which are supported by " "the ARM multiplatform (armmp) kernel." msgstr "" #. Tag: para #: hardware.xml:318 #, no-c-format msgid "" "The ARM architecture has evolved over time and modern ARM processors provide " "features which are not available in older models. &debian; therefore " "provides two ARM ports, the &debian;/armel and the &debian;/armhf port. " "&debian;/armel targets older ARM processors without support for a hardware " "floating point unit (FPU), while &debian;/armhf works only on newer ARM " "processors which implement at least the ARMv7 architecture with version 3 of " "the ARM vector floating point specification (VFPv3). &debian;/armhf makes " "use of the extended features and performance enhancements available on these " "models." msgstr "" #. Tag: para #: hardware.xml:346 #, no-c-format msgid "" "Technically, several ARM CPUs can be run in either endian mode (big or " "little), but in practice the vast majority of currently available systems " "uses little-endian mode. Both &debian;/armhf and &debian;/armel support only " "little-endian systems." msgstr "" #. Tag: title #: hardware.xml:354 #, no-c-format msgid "Platforms supported by Debian/armel" msgstr "" #. Tag: para #: hardware.xml:356 #, no-c-format msgid "" "The following platforms are supported by &debian;/armel; they require " "platform-specific kernels." msgstr "" #. Tag: term #: hardware.xml:364 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para #: hardware.xml:365 #, no-c-format msgid "" "The Intel IXP4xx processor series is used in network attached storage " "devices like the Linksys NSLU2." msgstr "" #. Tag: term #: hardware.xml:374 #, no-c-format msgid "Kirkwood" msgstr "" #. Tag: para #: hardware.xml:375 #, 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), plug " "computers (SheevaPlug, GuruPlug and DreamPlug), QNAP Turbo Station (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:391 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para #: hardware.xml:392 #, 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: Buffalo Kurobox, D-Link DNS-323 and HP mv2120." msgstr "" #. Tag: term #: hardware.xml:406 #, no-c-format msgid "Versatile" msgstr "" #. Tag: para #: hardware.xml:407 #, 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: title #: hardware.xml:420 #, no-c-format msgid "Platforms no longer supported by Debian/armel" msgstr "" #. Tag: term #: hardware.xml:424 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para #: hardware.xml:425 #, no-c-format msgid "" "Intel's I/O Processor (IOP) line is found in a number of products related to " "data storage and processing, such as the GLAN Tank from IO-Data and the Thecus N2100. &debian; has supported the IOP32x " "platform in &debian; 7, but does not support it anymore from version 8 on " "due to hardware constraints of the platform which make it unsuitable for the " "installation of newer &debian; releases." msgstr "" #. Tag: term #: hardware.xml:439 #, no-c-format msgid "MV78xx0" msgstr "" #. Tag: para #: hardware.xml:440 #, no-c-format msgid "" "The MV78xx0 platform has been used on the Marvell DB-78xx0-BP development " "board. It was supported in Debian 7 with a platform-specific kernel (based " "on the Linux kernel version 3.2), but is not supported anymore from Debian 8 " "onwards." msgstr "" #. Tag: title #: hardware.xml:455 #, no-c-format msgid "Platforms supported by Debian/armhf" msgstr "" #. Tag: para #: hardware.xml:457 #, no-c-format msgid "" "The following systems are known to work with &debian;/armhf using the " "multiplatform (armmp) kernel:" msgstr "" #. Tag: term #: hardware.xml:464 #, no-c-format msgid "Freescale MX53 Quick Start Board" msgstr "" #. Tag: para #: hardware.xml:466 #, no-c-format msgid "The IMX53QSB is a development board based on the i.MX53 SOC." msgstr "" #. Tag: term #: hardware.xml:473 #, no-c-format msgid "Versatile Express" msgstr "" #. Tag: para #: hardware.xml:475 #, no-c-format msgid "" "The Versatile Express is a development board series from ARM consisting of a " "baseboard which can be equipped with various CPU daughterboards." msgstr "" #. Tag: term #: hardware.xml:484 #, no-c-format msgid "Certain Allwinner sunXi-based development boards and embedded systems" msgstr "" #. Tag: para #: hardware.xml:487 #, no-c-format msgid "" "The armmp kernel supports several development boards and embedded systems " "based on the Allwinner A10 (architecture codename sun4i) and " "A20 (architecture codename sun7i) SOCs. Full installer " "support is currently available for the following sunXi-based systems:" msgstr "" #. Tag: para #: hardware.xml:494 #, no-c-format msgid "Cubietech Cubieboard 1 + 2 / Cubietruck" msgstr "" #. Tag: para #: hardware.xml:497 #, no-c-format msgid "LinkSprite pcDuino" msgstr "" #. Tag: para #: hardware.xml:500 #, no-c-format msgid "Mele A1000" msgstr "" #. Tag: para #: hardware.xml:503 #, no-c-format msgid "Miniand Hackberry" msgstr "" #. Tag: para #: hardware.xml:506 #, no-c-format msgid "" "Olimex A10-Olinuxino-LIME / A10s-Olinuxino Micro / A13-Olinuxino / A13-" "Olinuxino Micro / A20-Olinuxino Micro" msgstr "" #. Tag: para #: hardware.xml:510 #, no-c-format msgid "PineRiver Mini X-Plus" msgstr "" #. Tag: para #: hardware.xml:516 #, no-c-format msgid "" "System support for Allwinner sunXi-based devices is limited to drivers and " "device-tree information available in the mainline Linux kernel. The android-" "derived linux-sunxi.org 3.4 kernel series is not supported by Debian." msgstr "" #. Tag: para #: hardware.xml:522 #, no-c-format msgid "" "The mainline Linux kernel generally supports serial console, ethernet, SATA, " "USB and MMC/SD-cards on Allwinner A10 and A20 SOCs, but it does not have " "local display (HDMI/VGA/LVDS) and audio support. The NAND flash memory that " "is built into some sunXi-based systems is not supported." msgstr "" #. Tag: term #: hardware.xml:533 #, no-c-format msgid "SolidRun Cubox-i2eX / Cubox-i4Pro" msgstr "" #. Tag: para #: hardware.xml:535 #, no-c-format msgid "" "The Cubox-i series is a set of small, cubical-shaped systems based on the " "Freescale i.MX6 SOC family. System support for the Cubox-i series is limited " "to drivers and device-tree information available in the mainline Linux " "kernel; the Freescale 3.0 kernel series for the Cubox-i is not supported by " "Debian. Available drivers in the mainline kernel include serial console, " "ethernet, USB, MMC/SD-card and basic local display support over HDMI." msgstr "" #. Tag: para #: hardware.xml:550 #, no-c-format msgid "" "Generally, the ARM multiplatform support in the Linux kernel allows running " "&d-i; on armhf systems not explicitly listed above, as long as the kernel " "used by &d-i; has support for the target system's components and a device-" "tree file for the target is available. In these cases, the installer can " "usually provide a working userland installation, but it probably cannot " "automatically make the system bootable, as doing that in many cases requires " "device-specific information." msgstr "" #. Tag: para #: hardware.xml:561 #, no-c-format msgid "" "When using &d-i; on such systems, you have to manually make the system " "bootable at the end of the installation, e.g. by running the required " "commands in a shell started from within &d-i;." msgstr "" #. Tag: title #: hardware.xml:570 #, no-c-format msgid "Platforms no longer supported by Debian/armhf" msgstr "" #. Tag: term #: hardware.xml:574 #, no-c-format msgid "EfikaMX" msgstr "" #. Tag: para #: hardware.xml:575 #, no-c-format msgid "" "The EfikaMX platform (Genesi Efika Smartbook and Genesi EfikaMX nettop) has " "been supported in &debian; 7 with a platform-specific kernel, but is not " "supported anymore from &debian; 8 onwards. The code required to build the " "formerly used platform-specific kernel has been removed from the upstream " "Linux kernel source in 2012, so Debian cannot provide newer builds." msgstr "" #. Tag: para #: hardware.xml:583 #, no-c-format msgid "" "Using the armmp multiplatform kernel on the EfikaMX platform would require " "device-tree support for it, which is currently not available." msgstr "" #. Tag: para #: hardware.xml:604 #, no-c-format msgid "" "There are two major support &architecture; 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:623 #, no-c-format msgid "" "Complete information concerning supported peripherals can be found at Linux Hardware Compatibility HOWTO. " "This section merely outlines the basics." msgstr "" #. Tag: title #: hardware.xml:631 hardware.xml:736 #, no-c-format msgid "CPU" msgstr "" #. Tag: para #: hardware.xml:632 #, 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:639 #, no-c-format msgid "" "However, &debian; GNU/Linux &releasename; will not 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; 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. . (No version of Linux has ever supported the 286 or earlier chips " "in the series.) All i486 and later processors are still supported " " 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. ." msgstr "" #. Tag: para #: hardware.xml:672 #, 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:681 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para #: hardware.xml:682 #, 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:702 #, no-c-format msgid "" "&debian; on &arch-title; supports the following platforms: " " 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. SGI IP32: this platform is " "generally known as SGI O2. 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. Complete information regarding supported mips/mipsel machines " "can be found at the Linux-MIPS homepage. 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 " "debian-&arch-listname; mailing list." msgstr "" #. Tag: para #: hardware.xml:737 #, 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:743 #, 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:760 #, no-c-format msgid "" "&debian; on &arch-title; supports the following platforms: " " 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. Complete information regarding " "supported mips/mipsel machines can be found at the Linux-MIPS homepage. 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 debian-&arch-listname; mailing list." msgstr "" #. Tag: para #: hardware.xml:790 #, 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:811 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para #: hardware.xml:813 #, no-c-format msgid "" "There are two flavours of the powerpc kernel in &debian;, based on the CPU " "type:" msgstr "" #. Tag: term #: hardware.xml:820 #, no-c-format msgid "powerpc" msgstr "" #. Tag: para #: hardware.xml:821 #, no-c-format msgid "" "This kernel flavour 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:831 #, no-c-format msgid "powerpc-smp" msgstr "" #. Tag: para #: hardware.xml:832 #, no-c-format msgid "All Apple PowerMac G4 SMP machines." msgstr "" #. Tag: term #: hardware.xml:840 #, no-c-format msgid "power64" msgstr "" #. Tag: para #: hardware.xml:841 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para #: hardware.xml:845 #, 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:851 #, 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:856 #, no-c-format msgid "" "Systems using the PPC970 processor (Apple G5, YDL PowerStation, IBM " "Intellistation POWER 185) are also based on the POWER4 architecture, and use " "this kernel flavour." msgstr "" #. Tag: para #: hardware.xml:862 #, no-c-format msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors." msgstr "" #. Tag: title #: hardware.xml:895 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para #: hardware.xml:897 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: hardware.xml:904 #, 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:912 #, 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 ROM in RAM system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para #: hardware.xml:920 #, no-c-format msgid "" "Specifications for Apple hardware are available at AppleSpec, and, for older " "hardware, AppleSpec Legacy." msgstr "" #. Tag: entry #: hardware.xml:936 hardware.xml:1071 hardware.xml:1115 hardware.xml:1148 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry #: hardware.xml:937 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry #: hardware.xml:943 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry #: hardware.xml:944 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry #: hardware.xml:945 hardware.xml:948 hardware.xml:951 hardware.xml:954 #: hardware.xml:957 hardware.xml:960 hardware.xml:963 hardware.xml:966 #: hardware.xml:969 hardware.xml:972 hardware.xml:975 hardware.xml:978 #: hardware.xml:981 hardware.xml:984 hardware.xml:987 hardware.xml:990 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry #: hardware.xml:947 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry #: hardware.xml:950 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry #: hardware.xml:953 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry #: hardware.xml:956 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry #: hardware.xml:959 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry #: hardware.xml:962 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry #: hardware.xml:965 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry #: hardware.xml:968 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry #: hardware.xml:971 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry #: hardware.xml:974 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry #: hardware.xml:977 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry #: hardware.xml:980 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry #: hardware.xml:983 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry #: hardware.xml:986 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry #: hardware.xml:989 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry #: hardware.xml:992 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry #: hardware.xml:993 hardware.xml:996 hardware.xml:999 hardware.xml:1002 #: hardware.xml:1005 hardware.xml:1008 hardware.xml:1011 hardware.xml:1014 #: hardware.xml:1017 hardware.xml:1020 hardware.xml:1023 hardware.xml:1026 #: hardware.xml:1032 hardware.xml:1035 hardware.xml:1041 hardware.xml:1047 #: hardware.xml:1053 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry #: hardware.xml:995 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry #: hardware.xml:998 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry #: hardware.xml:1001 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry #: hardware.xml:1004 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry #: hardware.xml:1007 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry #: hardware.xml:1010 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry #: hardware.xml:1013 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry #: hardware.xml:1016 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry #: hardware.xml:1019 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry #: hardware.xml:1022 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry #: hardware.xml:1025 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry #: hardware.xml:1030 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry #: hardware.xml:1031 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry #: hardware.xml:1034 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry #: hardware.xml:1039 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry #: hardware.xml:1040 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry #: hardware.xml:1045 #, no-c-format msgid "APS" msgstr "" #. Tag: entry #: hardware.xml:1046 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry #: hardware.xml:1051 hardware.xml:1077 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry #: hardware.xml:1052 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title #: hardware.xml:1061 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry #: hardware.xml:1078 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry #: hardware.xml:1080 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry #: hardware.xml:1082 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry #: hardware.xml:1084 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry #: hardware.xml:1086 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry #: hardware.xml:1090 hardware.xml:1121 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry #: hardware.xml:1091 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry #: hardware.xml:1093 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry #: hardware.xml:1095 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry #: hardware.xml:1097 #, no-c-format msgid "p640" msgstr "" #. Tag: title #: hardware.xml:1105 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry #: hardware.xml:1122 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry #: hardware.xml:1125 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry #: hardware.xml:1126 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: entry #: hardware.xml:1129 #, no-c-format msgid "Fixstars" msgstr "" #. Tag: entry #: hardware.xml:1130 #, no-c-format msgid "YDL PowerStation" msgstr "" #. Tag: title #: hardware.xml:1138 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry #: hardware.xml:1154 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry #: hardware.xml:1155 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title #: hardware.xml:1163 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para #: hardware.xml:1165 #, 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: " " Power Macintosh 6100, 7100, 8100 " " Performa 5200, 6200, 6300 " " Powerbook 1400, 2300, and 5300 " " Workgroup Server 6150, 8150, 9150 A linux kernel for these machines and limited support is " "available at ." msgstr "" #. Tag: title #: hardware.xml:1202 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para #: hardware.xml:1204 #, no-c-format msgid "" "Macintosh computers using the 680x0 series of processors are not in the PowerPC family but are instead m68k machines. Those models " "start with Mac II series, go on to the LC " "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:1213 #, 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:1221 #, 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:1237 #, no-c-format msgid "zSeries and System z machine types" msgstr "" #. Tag: para #: hardware.xml:1238 #, 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 " " Linux on System z page on developerWorks." msgstr "" #. Tag: title #: hardware.xml:1255 #, no-c-format msgid "PAV and HyperPAV" msgstr "" #. Tag: para #: hardware.xml:1256 #, 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:1272 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para #: hardware.xml:1273 #, 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:1284 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para #: hardware.xml:1286 #, 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 Wikipedia SPARCstation page." msgstr "" #. Tag: para #: hardware.xml:1293 #, 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:1303 #, no-c-format msgid "sun4u" msgstr "" #. Tag: para #: hardware.xml:1305 #, 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:1318 #, no-c-format msgid "sun4v" msgstr "" #. Tag: para #: hardware.xml:1320 #, 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:1331 #, 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:1340 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para #: hardware.xml:1341 #, 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 (airplane mode). " "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 " "Linux Laptop pages." msgstr "" #. Tag: title #: hardware.xml:1358 hardware.xml:1378 hardware.xml:1405 hardware.xml:1428 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para #: hardware.xml:1359 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. Having multiple " "processors in a computer was originally only an issue for high-end server " "systems but has become common in recent years nearly everywhere with the " "introduction of so called multi-core processors. These " "contain two or more processor units, called cores, in one " "physical chip." msgstr "" #. Tag: para #: hardware.xml:1369 #, 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:1380 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. The standard " "&debian; &release; kernel image has been compiled with SMP-" "alternatives 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:1389 #, no-c-format msgid "" "Having multiple processors in a computer was originally only an issue for " "high-end server systems but has become common in recent years nearly " "everywhere with the introduction of so called multi-core " "processors. These contain two or more processor units, called cores, in one physical chip." msgstr "" #. Tag: para #: hardware.xml:1396 #, 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:1406 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing 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 only the first CPU." msgstr "" #. Tag: para #: hardware.xml:1415 #, no-c-format msgid "" "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 . At this " "time (kernel version &kernelversion;) the way you enable SMP is to select " "&smp-config-option; in the &smp-config-section; section of the kernel config." msgstr "" #. Tag: para #: hardware.xml:1429 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing 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." msgstr "" #. Tag: para #: hardware.xml:1439 #, 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:1445 #, no-c-format msgid "" "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in . At this time (kernel version &kernelversion;) the way " "you enable SMP is to select &smp-config-option; in the " "&smp-config-section; section of the kernel config." msgstr "" #. Tag: title #: hardware.xml:1456 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para #: hardware.xml:1457 #, 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 firmware images " "(see ). 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:1470 #, no-c-format msgid "" "Details on supported graphics cards and pointing devices can be found at " ". &debian; &release; ships with X.Org " "version &x11ver;." msgstr "" #. Tag: para #: hardware.xml:1475 #, 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:1480 #, 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 afbinit package, and read the " "documentation included with it on how to activate the card." msgstr "" #. Tag: para #: hardware.xml:1490 #, 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:1512 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para #: hardware.xml:1513 #, 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. This includes most " "PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops. " "Many older ISA cards are supported as well." msgstr "" #. Tag: para #: hardware.xml:1523 #, 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:1529 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para #: hardware.xml:1534 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para #: hardware.xml:1539 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para #: hardware.xml:1544 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para #: hardware.xml:1549 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para #: hardware.xml:1556 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para #: hardware.xml:1561 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para #: hardware.xml:1566 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para #: hardware.xml:1571 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para #: hardware.xml:1580 #, 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:1585 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title #: hardware.xml:1592 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para #: hardware.xml:1593 #, 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:1600 #, no-c-format msgid "" "If firmware is needed, the installer will prompt you to load firmware. See " " for detailed information on how to load " "firmware during the installation." msgstr "" #. Tag: para #: hardware.xml:1605 #, 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:1610 #, 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:1620 #, 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. If no Linux driver is available, " "your last resort is to use the ndiswrapper package, " "which allows you to use a Windows driver." msgstr "" #. Tag: title #: hardware.xml:1634 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para #: hardware.xml:1635 #, no-c-format msgid "" "There are a couple of issues with specific network cards that are worth " "mentioning here." msgstr "" #. Tag: title #: hardware.xml:1642 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para #: hardware.xml:1644 #, 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 tulip driver, others with the dfme " "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:1654 #, no-c-format msgid "" "This is a common problem on Netra systems with a Davicom (DEC-Tulip " "compatible) NIC. In that case the tulip driver is " "probably the correct one. You can prevent this issue by blacklisting the " "wrong driver module as described in ." msgstr "" #. Tag: para #: hardware.xml:1662 #, no-c-format msgid "" "An alternative solution during the installation is to switch to a shell and " "unload the wrong driver module using modprobe -r " "module (or both, if they are both " "loaded). After that you can load the correct module using " "modprobe module. Note that " "the wrong module may then still be loaded when the system is rebooted." msgstr "" #. Tag: title #: hardware.xml:1675 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para #: hardware.xml:1677 #, no-c-format msgid "" "The cassini network driver does not work with Sun B100 " "blade systems." msgstr "" #. Tag: title #: hardware.xml:1692 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para #: hardware.xml:1693 #, no-c-format msgid "" "Support for braille displays is determined by the underlying support found " "in brltty. Most displays work under " "brltty, connected via either a serial port, USB or " "bluetooth. Details on supported braille devices can be found on the brltty website. &debian-" "gnu; &release; ships with brltty version &brlttyver;." msgstr "" #. Tag: title #: hardware.xml:1707 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para #: hardware.xml:1708 #, no-c-format msgid "" "Support for hardware speech synthesis devices is determined by the " "underlying support found in speakup. " "speakup 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 speakup " "website. &debian-gnu; &release; ships with speakup version &speakupver;." msgstr "" #. Tag: title #: hardware.xml:1728 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para #: hardware.xml:1729 #, no-c-format msgid "" "&arch-kernel; supports a large variety of hardware devices such as mice, " "printers, scanners, PCMCIA/CardBus/ExpressCard and USB devices. However, " "most of these devices are not required while installing the system." msgstr "" #. Tag: para #: hardware.xml:1735 #, no-c-format msgid "" "USB hardware generally works fine. On some very old PC systems some USB " "keyboards may require additional configuration (see ). On modern PCs, USB keyboards and mice work without requiring " "any specific configuration." msgstr "" #. Tag: para #: hardware.xml:1744 #, 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: title #: hardware.xml:1757 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para #: hardware.xml:1758 #, no-c-format msgid "" "Besides the availability of a device driver, some hardware also requires so-" "called firmware or microcode " "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:1769 #, 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:1777 #, 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:1786 #, 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 for detailed " "information on how to load firmware files or packages during the " "installation." msgstr "" #. Tag: para #: hardware.xml:1795 #, 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:1812 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "" #. Tag: para #: hardware.xml:1814 #, no-c-format msgid "" "There are several vendors, who ship systems with &debian; or other " "distributions of GNU/Linux pre-installed. 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:1822 #, 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 " "windows refund may get you some useful information to help " "with that." msgstr "" #. Tag: para #: hardware.xml:1830 #, 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:1841 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para #: hardware.xml:1842 #, 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:1852 #, 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 " "Human Interface Devices, 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:1864 #, 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:1875 #, 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:1888 #, 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:1903 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para #: hardware.xml:1905 #, 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, , 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:1915 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para #: hardware.xml:1916 #, 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:1922 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title #: hardware.xml:1929 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para #: hardware.xml:1931 #, no-c-format msgid "" "Whenever you see CD-ROM 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:1937 #, no-c-format msgid "CD-ROM based installation is supported for most architectures." msgstr "" #. Tag: para #: hardware.xml:1941 #, no-c-format msgid "On PCs SATA, IDE/ATAPI and SCSI CD-ROMs are supported." msgstr "" #. Tag: para #: hardware.xml:1945 #, 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:1950 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para #: hardware.xml:1954 #, 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 Unix/PC or 512/2048, place it in the Unix or 512 position. " "To start the install, simply choose the System installation " "entry in the firmware." msgstr "" #. Tag: title #: hardware.xml:1968 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para #: hardware.xml:1970 #, 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:1982 #, no-c-format msgid "Network" msgstr "" #. Tag: para #: hardware.xml:1984 #, 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:1994 #, no-c-format msgid "" "You can also boot 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. This is the " "preferred installation technique for &arch-title;." msgstr "" #. Tag: para #: hardware.xml:2007 #, 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:2016 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para #: hardware.xml:2018 #, 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:2025 #, 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:2034 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para #: hardware.xml:2036 #, 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 . This " "installation method is only recommended for advanced users when no other " "installation method is available." msgstr "" #. Tag: title #: hardware.xml:2049 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para #: hardware.xml:2051 #, 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:2055 #, 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:2072 #, 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: " " Sparc ESP " " PTI Qlogic,ISP Adaptec " "AIC7xxx NCR and Symbios 53C8XX IDE systems (such as the UltraSPARC 5) are also " "supported. See Linux for SPARC " "Processors FAQ for more information on SPARC hardware supported by " "the Linux kernel." msgstr "" #. Tag: para #: hardware.xml:2105 #, 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:2111 #, 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:2117 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system." msgstr "" #. Tag: para #: hardware.xml:2122 #, 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:2139 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para #: hardware.xml:2141 #, 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 ." msgstr "" #. Tag: para #: hardware.xml:2148 #, no-c-format msgid "" "Installation on systems with less memory " "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 text-based and the graphical installer, the former " "should be selected. or disk space available may be " "possible but is only advised for experienced users." msgstr ""