# Debian installation guide - translation into Ukranian # msgid "" msgstr "" "Project-Id-Version: hardware_uk\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2021-04-28 23:02+0000\n" "PO-Revision-Date: 2019-09-03 08:32+0100\n" "Last-Translator: \n" "Language-Team: Ukranian\n" "Language: uk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\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 9 major architectures and several " "variations of each architecture known as flavors." msgstr "" #. Tag: entry #: hardware.xml:53 #, no-c-format msgid "Architecture" msgstr "" #. Tag: entry #: hardware.xml:53 #, 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 #, no-c-format msgid "AMD64 & Intel 64" msgstr "" #. Tag: entry #: hardware.xml:61 #, no-c-format msgid "amd64" msgstr "" #. Tag: entry #: hardware.xml:67 #, no-c-format msgid "Intel x86-based" msgstr "" #. Tag: entry #: hardware.xml:68 #, no-c-format msgid "i386" msgstr "" #. Tag: entry #: hardware.xml:69 #, no-c-format msgid "default x86 machines" msgstr "" #. Tag: entry #: hardware.xml:70 #, no-c-format msgid "default" msgstr "" #. Tag: entry #: hardware.xml:72 #, no-c-format msgid "Xen PV domains only" msgstr "" #. Tag: entry #: hardware.xml:73 #, no-c-format msgid "xen" msgstr "" #. Tag: entry #: hardware.xml:77 #, no-c-format msgid "ARM" msgstr "" #. Tag: entry #: hardware.xml:78 #, no-c-format msgid "armel" msgstr "" #. Tag: entry #: hardware.xml:79 #, no-c-format msgid "Marvell Kirkwood and Orion" msgstr "" #. Tag: entry #: hardware.xml:80 #, no-c-format msgid "marvell" msgstr "" #. Tag: entry #: hardware.xml:84 #, no-c-format msgid "ARM with hardware FPU" msgstr "" #. Tag: entry #: hardware.xml:85 #, no-c-format msgid "armhf" msgstr "" #. Tag: entry #: hardware.xml:86 #, no-c-format msgid "multiplatform" msgstr "" #. Tag: entry #: hardware.xml:87 #, no-c-format msgid "armmp" msgstr "" #. Tag: entry #: hardware.xml:91 #, no-c-format msgid "64bit ARM" msgstr "" #. Tag: entry #: hardware.xml:92 #, no-c-format msgid "arm64" msgstr "" #. Tag: entry #: hardware.xml:110 #, no-c-format msgid "64bit MIPS (little-endian)" msgstr "" #. Tag: entry #: hardware.xml:111 #, no-c-format msgid "mips64el" msgstr "" #. Tag: entry #: hardware.xml:112 hardware.xml:125 #, no-c-format msgid "MIPS Malta" msgstr "" #. Tag: entry #: hardware.xml:113 #, no-c-format msgid "5kc-malta" msgstr "" #. Tag: entry #: hardware.xml:115 hardware.xml:128 #, no-c-format msgid "Cavium Octeon" msgstr "" #. Tag: entry #: hardware.xml:116 hardware.xml:129 #, no-c-format msgid "octeon" msgstr "" #. Tag: entry #: hardware.xml:118 hardware.xml:131 #, no-c-format msgid "Loongson 3" msgstr "" #. Tag: entry #: hardware.xml:119 hardware.xml:132 #, no-c-format msgid "loongson-3" msgstr "" #. Tag: entry #: hardware.xml:123 #, no-c-format msgid "32bit MIPS (little-endian)" msgstr "" #. Tag: entry #: hardware.xml:124 #, no-c-format msgid "mipsel" msgstr "" #. Tag: entry #: hardware.xml:126 #, no-c-format msgid "4kc-malta" msgstr "" #. Tag: entry #: hardware.xml:150 #, no-c-format msgid "Power Systems" msgstr "" #. Tag: entry #: hardware.xml:151 #, no-c-format msgid "ppc64el" msgstr "" #. Tag: entry #: hardware.xml:152 #, no-c-format msgid "IBM POWER8 or newer machines" msgstr "" #. Tag: entry #: hardware.xml:177 #, no-c-format msgid "64bit IBM S/390" msgstr "" #. Tag: entry #: hardware.xml:178 #, no-c-format msgid "s390x" msgstr "" #. Tag: entry #: hardware.xml:179 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry #: hardware.xml:180 #, no-c-format msgid "generic" msgstr "" #. Tag: para #: hardware.xml:187 #, 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:197 #, 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:219 #, no-c-format msgid "CPU Support" msgstr "" #. Tag: para #: hardware.xml:220 #, no-c-format msgid "Both AMD64 and Intel 64 processors are supported." msgstr "" #. Tag: title #: hardware.xml:244 #, no-c-format msgid "Three different ARM ports" msgstr "" #. Tag: para #: hardware.xml:246 #, 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 three ARM ports to give the best support for a very wide range of " "different machines:" msgstr "" #. Tag: para #: hardware.xml:252 #, no-c-format msgid "" "&debian;/armel targets older 32-bit ARM processors without support for a " "hardware floating point unit (FPU)," msgstr "" #. Tag: para #: hardware.xml:256 #, no-c-format msgid "" "&debian;/armhf works only on newer 32-bit ARM processors which implement at " "least the ARMv7 architecture with version 3 of the ARM vector floating point " "specification (VFPv3). It makes use of the extended features and performance " "enhancements available on these models." msgstr "" #. Tag: para #: hardware.xml:263 #, no-c-format msgid "" "&debian;/arm64 works on 64-bit ARM processors which implement at least the " "ARMv8 architecture." msgstr "" #. Tag: para #: hardware.xml:270 #, no-c-format msgid "" "Technically, all currently available ARM CPUs can be run in either endian " "mode (big or little), but in practice the vast majority use little-endian " "mode. All of &debian;/arm64, &debian;/armhf and &debian;/armel support only " "little-endian systems." msgstr "" #. Tag: title #: hardware.xml:279 #, no-c-format msgid "Variations in ARM CPU designs and support complexity" msgstr "" #. Tag: para #: hardware.xml:281 #, no-c-format msgid "" "ARM systems are much more heterogeneous than those based on the i386/amd64-" "based PC architecture, so the support situation can be much more complicated." msgstr "" #. Tag: para #: hardware.xml:287 #, no-c-format msgid "" "The ARM architecture is used mainly in so-called system-on-chip (SoC) designs. 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. System firmware interfaces " "have been increasingly standardised over time, but especially on older " "hardware firmware/boot interfaces vary a great deal, so on these systems the " "Linux kernel has to take care of many system-specific low-level issues which " "would be handled by the mainboard's BIOS/UEFI in the PC world." msgstr "" #. Tag: para #: hardware.xml:299 #, no-c-format msgid "" "At the beginning of the ARM support in the Linux kernel, the hardware " "variety resulted in the requirement of having a separate 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 " "was done to allow booting with a single ARM kernel that can run on different " "ARM systems. Support for newer ARM systems is now implemented in a way that " "allows the use of such a multiplatform kernel, but for several older systems " "a separate specific kernel is still required. Because of this, the standard " "&debian; distribution only supports installation on a selected number of " "such older ARM systems, alongside the newer systems which are supported by " "the ARM multiplatform kernels (called armmp) in &debian;/" "armhf." msgstr "" #. Tag: para #: hardware.xml:315 #, no-c-format msgid "" "The ARM architecture is used mainly in so-called system-on-chip (SoC) designs. These SoCs are designed by many different companies, " "often with vastly varying hardware components even for the very basic " "functionality required to bring the system up. Older versions of the ARM " "architecture have seen massive differences from one SoC to the next, but " "ARMv8 (arm64) is much more standardised and so is easier for the Linux " "kernel and other software to support." msgstr "" #. Tag: para #: hardware.xml:326 #, no-c-format msgid "" "Server versions of ARMv8 hardware are typically configured using the Unified " "Extensible Firmware Interface (UEFI) and Advanced Configuration and Power " "Interface (ACPI) standards. These two provide common, device-independent " "ways to boot and configure computer hardware. They are also common in the " "x86 PC world." msgstr "" #. Tag: title #: hardware.xml:336 #, no-c-format msgid "Platforms supported by Debian/arm64" msgstr "" #. Tag: para #: hardware.xml:338 #, no-c-format msgid "" "Arm64/AArch64/ARMv8 hardware became available quite late in the &debian; " "&releasename-cap; release cycle so not many platforms had support merged in " "the mainline kernel version by the time of this release; this is the main " "requirement to have &d-i; working on them. The following platforms are known " "to be supported by &debian;/arm64 in this release. There is only one kernel " "image, which supports all the listed platforms." msgstr "" #. Tag: term #: hardware.xml:350 #, no-c-format msgid "Applied Micro (APM) Mustang/X-Gene" msgstr "" #. Tag: para #: hardware.xml:352 #, no-c-format msgid "" "The APM Mustang was the first Linux-capable ARMv8 system available. It uses " "the X-gene SoC, which has since also been used in other machines. It is an 8-" "core CPU, with ethernet, USB and serial. A common form-factor looks just " "like a desktop PC box, but many other versions are expected in the future. " "Most of the hardware is supported in the mainline kernel, but at this point " "USB support is lacking in the &releasename-cap; kernel." msgstr "" #. Tag: term #: hardware.xml:366 #, no-c-format msgid "ARM Juno Development Platform" msgstr "" #. Tag: para #: hardware.xml:368 #, no-c-format msgid "" "Juno is a capable development board with a 6-core (2xA57, 4xA53) ARMv8-A " "800Mhz CPU, Mali (T624) graphics, 8GB DDR3 RAM, Ethernet, USB, Serial. It " "was designed for system bring-up and power testing so is neither small nor " "cheap, but was one of the first boards available. All the on-board hardware " "is supported in the mainline kernel and in &releasename-cap;." msgstr "" #. Tag: para #: hardware.xml:382 #, no-c-format msgid "" "When using &d-i; on non-UEFI systems, you may 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;. flash-kernel knows how to set " "up an X-Gene system booting with U-Boot." msgstr "" #. Tag: title #: hardware.xml:390 #, no-c-format msgid "Other platforms" msgstr "" #. Tag: para #: hardware.xml:391 #, no-c-format msgid "" "The multiplatform support in the arm64 Linux kernel may also allow running " "&d-i; on arm64 systems not explicitly listed above. So long as the kernel " "used by &d-i; has support for the target system's components, and a device-" "tree file for that target is available, a new target system may work just " "fine. In these cases, the installer can usually provide a working " "installation, and so long as UEFI is in use, it should be able to make the " "system bootable as well. If UEFI is not used you may also need to perform " "some manual configuration steps to make the system bootable." msgstr "" #. Tag: title #: hardware.xml:407 #, no-c-format msgid "Platforms supported by Debian/armhf" msgstr "" #. Tag: para #: hardware.xml:409 #, no-c-format msgid "" "The following systems are known to work with &debian;/armhf using the " "multiplatform (armmp) kernel:" msgstr "" #. Tag: term #: hardware.xml:416 #, no-c-format msgid "Freescale MX53 Quick Start Board (MX53 LOCO Board)" msgstr "" #. Tag: para #: hardware.xml:418 #, no-c-format msgid "The IMX53QSB is a development board based on the i.MX53 SoC." msgstr "" #. Tag: term #: hardware.xml:425 #, no-c-format msgid "Versatile Express" msgstr "" #. Tag: para #: hardware.xml:427 #, 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 daughter boards." msgstr "" #. Tag: term #: hardware.xml:436 #, no-c-format msgid "Certain Allwinner sunXi-based development boards and embedded systems" msgstr "" #. Tag: para #: hardware.xml:439 #, no-c-format msgid "" "The armmp kernel supports several development boards and embedded systems " "based on the Allwinner A10 (architecture codename sun4i), " "A10s/A13 (architecture codename sun5i), A20 (architecture " "codename sun7i), A31/A31s (architecture codename " "sun6i) and A23/A33 (part of the sun8i family) " "SoCs. Full installer support (including provision of ready-made SD card " "images with the installer) is currently available for the following sunXi-" "based systems:" msgstr "" #. Tag: para #: hardware.xml:453 #, no-c-format msgid "Cubietech Cubieboard 1 + 2 / Cubietruck" msgstr "" #. Tag: para #: hardware.xml:456 #, no-c-format msgid "LeMaker Banana Pi and Banana Pro" msgstr "" #. Tag: para #: hardware.xml:459 #, no-c-format msgid "LinkSprite pcDuino and pcDuino3" msgstr "" #. Tag: para #: hardware.xml:462 #, no-c-format msgid "" "Olimex A10-Olinuxino-LIME / A20-Olinuxino-LIME / A20-Olinuxino-LIME2 / A20-" "Olinuxino Micro / A20-SOM-EVB" msgstr "" #. Tag: para #: hardware.xml:466 #, no-c-format msgid "Xunlong OrangePi Plus" msgstr "" #. Tag: para #: hardware.xml:472 #, 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. Vendor-" "specific kernel trees (such as the Allwinner SDK kernels) and the android-" "derived linux-sunxi.org kernel 3.4 series are not supported by &debian;." msgstr "" #. Tag: para #: hardware.xml:480 #, no-c-format msgid "" "The mainline Linux kernel generally supports serial console, ethernet, SATA, " "USB and MMC/SD-cards on Allwinner A10, A10s/A13, A20, A23/A33 and A31/A31s " "SoCs. The level of support for local display (HDMI/VGA/LCD) and audio " "hardware varies between individual systems. For most systems, the kernel " "doesn't have native graphics drivers but instead uses the simplefb infrastructure in which the bootloader initializes the display and " "the kernel just re-uses the pre-initialized framebuffer. This generally " "works reasonably well, although it results in certain limitations (the " "display resolution cannot be changed on the fly and display powermanagement " "is not possible)." msgstr "" #. Tag: para #: hardware.xml:495 #, no-c-format msgid "" "Onboard flash memory intended to be used as a mass storage device generally " "exists in two basic variants on sunXi-based systems: raw NAND flash and eMMC " "flash. Most older sunXi-based boards with onboard flash storage use raw NAND " "flash for which support is not generally available in the mainline kernel " "and therefore also not in Debian. A number of newer systems use eMMC flash " "instead of raw NAND flash. An eMMC flash chip basically appears as a fast, " "non-removable SD card and is supported in the same way as a regular SD card." msgstr "" #. Tag: para #: hardware.xml:508 #, no-c-format msgid "" "The installer includes basic support for a number of sunXi-based systems not " "listed above, but it is largely untested on those systems as the &debian; " "project doesn't have access to the corresponding hardware. No pre-built SD " "card images with the installer are provided for those systems. Development " "boards with such limited support include:" msgstr "" #. Tag: para #: hardware.xml:517 #, no-c-format msgid "Olimex A10s-Olinuxino Micro / A13-Olinuxino / A13-Olinuxino Micro" msgstr "" #. Tag: para #: hardware.xml:521 #, no-c-format msgid "Sinovoip BPI-M2 (A31s-based)" msgstr "" #. Tag: para #: hardware.xml:524 #, no-c-format msgid "Xunlong Orange Pi (A20-based) / Orange Pi Mini (A20-based)" msgstr "" #. Tag: para #: hardware.xml:529 #, no-c-format msgid "" "In addition to the SoCs and systems listed above, the installer has very " "limited support for the Allwinner H3 SoC and a number of boards based on it. " "Mainline kernel support for the H3 is still largely work in progress at the " "time of the Debian 9 release freeze, so the installer only supports serial " "console, MMC/SD and the USB host controller on H3-based systems. There is no " "driver for the on-board ethernet port of the H3 yet, so networking is only " "possible with a USB ethernet adaptor or a USB wifi dongle. Systems based on " "the H3 for which such very basic installer support is available include:" msgstr "" #. Tag: para #: hardware.xml:542 #, no-c-format msgid "FriendlyARM NanoPi NEO" msgstr "" #. Tag: para #: hardware.xml:545 #, no-c-format msgid "" "Xunlong Orange Pi Lite / Orange Pi One / Orange Pi PC / Orange Pi PC Plus / " "Orange Pi Plus / Orange Pi Plus 2E / Orange Pi 2" msgstr "" #. Tag: term #: hardware.xml:556 #, no-c-format msgid "NVIDIA Jetson TK1" msgstr "" #. Tag: para #: hardware.xml:558 #, no-c-format msgid "" "The NVIDIA Jetson TK1 is a developer board based on the Tegra K1 chip (also " "known as Tegra 124). The Tegra K1 features a quad-core 32-bit ARM Cortex-A15 " "CPU and Kepler GPU (GK20A) with 192 CUDA cores. Other systems based on the " "Tegra 124 may work, too." msgstr "" #. Tag: term #: hardware.xml:569 #, no-c-format msgid "Seagate Personal Cloud and Seagate NAS" msgstr "" #. Tag: para #: hardware.xml:571 #, no-c-format msgid "" "The Seagate Personal Cloud and Seagate NAS are NAS devices based on " "Marvell's Armada 370 platform. Debian supports the Personal Cloud (SRN21C), " "Personal Cloud 2-Bay (SRN22C), Seagate NAS 2-Bay (SRPD20) and Seagate NAS 4-" "Bay (SRPD40)." msgstr "" #. Tag: term #: hardware.xml:581 #, no-c-format msgid "SolidRun Cubox-i2eX / Cubox-i4Pro" msgstr "" #. Tag: para #: hardware.xml:583 #, 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 display support over HDMI (console and X11). " "In addition to that, the eSATA port on the Cubox-i4Pro is supported." msgstr "" #. Tag: term #: hardware.xml:598 #, no-c-format msgid "Wandboard" msgstr "" #. Tag: para #: hardware.xml:600 #, no-c-format msgid "" "The Wandboard Quad, Dual and Solo are development boards based on the " "Freescale i.MX6 Quad SoC. System support is limited to drivers and device-" "tree information available in the mainline Linux kernel; the wandboard-" "specific 3.0 and 3.10 kernel series from wandboard.org are not supported by " "&debian;. The mainline kernel includes driver support for serial console, " "display via HDMI (console and X11), ethernet, USB, MMC/SD, SATA (Quad only) " "and analog audio. Support for the other audio options (S/PDIF, HDMI-Audio) " "and for the onboard WLAN/Bluetooth module is untested or not available in " "&debian; 9." msgstr "" #. Tag: para #: hardware.xml:618 #, 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 installation, but it may not be able to " "automatically make the system bootable. Doing that in many cases requires " "device-specific information." msgstr "" #. Tag: para #: hardware.xml:630 #, no-c-format msgid "" "When using &d-i; on such systems, you may 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:639 #, no-c-format msgid "Platforms no longer supported by Debian/armhf" msgstr "" #. Tag: term #: hardware.xml:643 #, no-c-format msgid "EfikaMX" msgstr "" #. Tag: para #: hardware.xml:644 #, no-c-format msgid "" "The EfikaMX platform (Genesi Efika Smartbook and Genesi EfikaMX nettop) was " "supported in &debian; 7 with a platform-specific kernel, but is no longer " "supported 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. Using the " "armmp multiplatform kernel on the EfikaMX platform would require device-tree " "support for it, which is currently not available." msgstr "" #. Tag: title #: hardware.xml:662 #, no-c-format msgid "Platforms supported by Debian/armel" msgstr "" #. Tag: para #: hardware.xml:664 #, no-c-format msgid "" "The following platforms are supported by &debian;/armel; they require " "platform-specific kernels." msgstr "" #. Tag: term #: hardware.xml:672 #, no-c-format msgid "Kirkwood" msgstr "" #. Tag: para #: hardware.xml:673 #, no-c-format msgid "" "Kirkwood is a system-on-chip (SoC) from Marvell that integrates an ARM CPU, " "Ethernet, SATA, USB, and other functionality in one chip. &debian; currently " "supports the following Kirkwood based devices:" msgstr "" #. Tag: ulink #: hardware.xml:681 #, no-c-format msgid "" "Plug computers (SheevaPlug, GuruPlug, DreamPlug and Seagate FreeAgent " "DockStar)" msgstr "" #. Tag: para #: hardware.xml:684 #, no-c-format msgid "" "QNAP Turbo Station " "(all TS-11x/TS-12x, HS-210, TS-21x/TS-22x and TS-41x/TS-42x models)" msgstr "" #. Tag: para #: hardware.xml:688 #, no-c-format msgid "" "LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 " "Network v2, 2Big Network v2 and 5Big Network v2)" msgstr "" #. Tag: para #: hardware.xml:692 #, no-c-format msgid "OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate)" msgstr "" #. Tag: term #: hardware.xml:701 hardware.xml:745 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para #: hardware.xml:702 #, no-c-format msgid "" "Orion is a system-on-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. &debian; currently supports the following Orion based devices: " "Buffalo Kurobox and " "HP mv2120." msgstr "" #. Tag: term #: hardware.xml:716 #, no-c-format msgid "Versatile" msgstr "" #. Tag: para #: hardware.xml:717 #, 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 real hardware." msgstr "" #. Tag: title #: hardware.xml:730 #, no-c-format msgid "Platforms and devices no longer supported by Debian/armel" msgstr "" #. Tag: term #: hardware.xml:734 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para #: hardware.xml:735 #, no-c-format msgid "" "Support for the Intel IXP4xx platform has been dropped in &debian; 9. The " "Linksys NSLU2 device is based on IXP4xx and is therefore no longer supported." msgstr "" #. Tag: para #: hardware.xml:746 #, no-c-format msgid "" "Support for the D-Link DNS-323 and Conceptronic CH3SNAS devices has been " "dropped from the Orion5x platform in &debian; 9. The Linux kernel no longer " "fits into the flash on these devices. Other Orion devices, such as Buffalo " "Kurobox and HP mv2120, are still supported." msgstr "" #. Tag: title #: hardware.xml:765 hardware.xml:933 hardware.xml:1376 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para #: hardware.xml:766 #, 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:774 hardware.xml:877 #, no-c-format msgid "CPU" msgstr "" #. Tag: para #: hardware.xml:775 #, no-c-format msgid "" "Nearly all x86-based (IA-32) processors still in use in personal computers " "are supported. 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:782 #, no-c-format msgid "" "However, &debian; GNU/Linux &releasename; will not run " "on 586 (Pentium) or earlier processors." msgstr "" #. Tag: para #: hardware.xml:788 #, 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:797 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para #: hardware.xml:798 #, 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 PCI, PCIe, or PCI-X bus. Essentially all personal computers sold in " "recent years use one of these." msgstr "" #. Tag: title #: hardware.xml:815 #, no-c-format msgid "Platforms supported by the &debian; &architecture; port" msgstr "" #. Tag: para #: hardware.xml:817 #, no-c-format msgid "&debian; on &arch-title; supports the following platforms:" msgstr "" #. Tag: term #: hardware.xml:823 #, no-c-format msgid "Cavium Octeon" msgstr "" #. Tag: para #: hardware.xml:825 #, no-c-format msgid "" "Cavium designs a range of 64-bit MIPS Octeon processors which are mainly " "used in networking devices. Devices with these processors include the " "Ubiquiti EdgeRouter and the Rhino Labs UTM8." msgstr "" #. Tag: term #: hardware.xml:834 #, no-c-format msgid "Loongson 3" msgstr "" #. Tag: para #: hardware.xml:836 #, no-c-format msgid "Devices based on the Loongson 3A and 3B processors are supported." msgstr "" #. Tag: term #: hardware.xml:844 #, no-c-format msgid "MIPS Malta" msgstr "" #. Tag: para #: hardware.xml:846 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: hardware.xml:850 #, no-c-format msgid "" "There are two Malta kernel flavours: 4kc-malta is built for 32-bit " "processors, and 5kc-malta is built for 64-bit processors." msgstr "" #. Tag: para #: hardware.xml:858 #, no-c-format msgid "" "In addition, other boards which contain MIPS32r2 or MIPS64r2 based processors should also be able to run " "&debian;, however kernels for these processors are not built and the " "&debian; installer does not directly support them." msgstr "" #. Tag: para #: hardware.xml:866 #, no-c-format msgid "" "Complete information regarding supported mips/mipsel/mips64el 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:878 #, 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 and mips64el architectures. For big endian MIPS, please read the documentation for the " "mips architecture. " msgstr "" #. Tag: title #: hardware.xml:893 #, no-c-format msgid "Platforms no longer supported by the &debian; &architecture; port" msgstr "" #. Tag: para #: hardware.xml:894 #, no-c-format msgid "" "Since &debian; Stretch, support for all MIPS processors which do not " "implement MIPS32 Release 2 have been dropped. Therefore the following " "platforms supported in Jessie are no longer supported:" msgstr "" #. Tag: term #: hardware.xml:901 #, no-c-format msgid "Loongson 2E and 2F" msgstr "" #. Tag: listitem #: hardware.xml:902 #, no-c-format msgid "" "These are the older Loongson processors. Devices based on them include the " "Fuloong Mini-PC and the Lemote Yeeloong laptop." msgstr "" #. Tag: term #: hardware.xml:908 #, no-c-format msgid "SGI IP22" msgstr "" #. Tag: listitem #: hardware.xml:909 #, no-c-format msgid "This platform includes the SGI machines Indy, Indigo 2 and Challenge S." msgstr "" #. Tag: term #: hardware.xml:914 #, no-c-format msgid "SGI IP32" msgstr "" #. Tag: listitem #: hardware.xml:915 #, no-c-format msgid "This platform is generally known as SGI O2." msgstr "" #. Tag: term #: hardware.xml:918 #, no-c-format msgid "Broadcom BCM91250" msgstr "" #. Tag: listitem #: hardware.xml:919 #, no-c-format msgid "" "Development board for Broadcom's SiByte core. Also known by its codename " "SWARM." msgstr "" #. Tag: para #: hardware.xml:934 #, 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:955 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para #: hardware.xml:957 #, no-c-format msgid "" "There are two flavours of the powerpc kernel in &debian;, based on the CPU " "type:" msgstr "" #. Tag: term #: hardware.xml:964 #, no-c-format msgid "powerpc" msgstr "" #. Tag: para #: hardware.xml:965 #, 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:975 #, no-c-format msgid "powerpc-smp" msgstr "" #. Tag: para #: hardware.xml:976 #, no-c-format msgid "All Apple PowerMac G4 SMP machines." msgstr "" #. Tag: term #: hardware.xml:984 #, no-c-format msgid "power64" msgstr "" #. Tag: para #: hardware.xml:985 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para #: hardware.xml:989 #, 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:995 #, 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:1000 #, 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:1006 #, no-c-format msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors." msgstr "" #. Tag: title #: hardware.xml:1039 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para #: hardware.xml:1041 #, 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:1048 #, 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:1056 #, 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:1064 #, no-c-format msgid "" "Specifications for Apple hardware are available at AppleSpec, and, for older " "hardware, AppleSpec Legacy." msgstr "" #. Tag: entry #: hardware.xml:1080 hardware.xml:1215 hardware.xml:1259 hardware.xml:1292 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry #: hardware.xml:1081 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry #: hardware.xml:1087 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry #: hardware.xml:1088 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry #: hardware.xml:1089 hardware.xml:1092 hardware.xml:1095 hardware.xml:1098 #: hardware.xml:1101 hardware.xml:1104 hardware.xml:1107 hardware.xml:1110 #: hardware.xml:1113 hardware.xml:1116 hardware.xml:1119 hardware.xml:1122 #: hardware.xml:1125 hardware.xml:1128 hardware.xml:1131 hardware.xml:1134 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry #: hardware.xml:1091 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry #: hardware.xml:1094 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry #: hardware.xml:1097 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry #: hardware.xml:1100 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry #: hardware.xml:1103 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry #: hardware.xml:1106 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry #: hardware.xml:1109 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry #: hardware.xml:1112 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry #: hardware.xml:1115 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry #: hardware.xml:1118 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry #: hardware.xml:1121 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry #: hardware.xml:1124 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry #: hardware.xml:1127 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry #: hardware.xml:1130 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry #: hardware.xml:1133 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry #: hardware.xml:1136 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry #: hardware.xml:1137 hardware.xml:1140 hardware.xml:1143 hardware.xml:1146 #: hardware.xml:1149 hardware.xml:1152 hardware.xml:1155 hardware.xml:1158 #: hardware.xml:1161 hardware.xml:1164 hardware.xml:1167 hardware.xml:1170 #: hardware.xml:1176 hardware.xml:1179 hardware.xml:1185 hardware.xml:1191 #: hardware.xml:1197 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry #: hardware.xml:1139 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry #: hardware.xml:1142 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry #: hardware.xml:1145 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry #: hardware.xml:1148 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry #: hardware.xml:1151 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry #: hardware.xml:1154 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry #: hardware.xml:1157 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry #: hardware.xml:1160 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry #: hardware.xml:1163 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry #: hardware.xml:1166 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry #: hardware.xml:1169 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry #: hardware.xml:1174 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry #: hardware.xml:1175 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry #: hardware.xml:1178 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry #: hardware.xml:1183 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry #: hardware.xml:1184 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry #: hardware.xml:1189 #, no-c-format msgid "APS" msgstr "" #. Tag: entry #: hardware.xml:1190 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry #: hardware.xml:1195 hardware.xml:1221 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry #: hardware.xml:1196 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title #: hardware.xml:1205 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry #: hardware.xml:1222 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry #: hardware.xml:1224 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry #: hardware.xml:1226 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry #: hardware.xml:1228 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry #: hardware.xml:1230 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry #: hardware.xml:1234 hardware.xml:1265 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry #: hardware.xml:1235 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry #: hardware.xml:1237 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry #: hardware.xml:1239 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry #: hardware.xml:1241 #, no-c-format msgid "p640" msgstr "" #. Tag: title #: hardware.xml:1249 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry #: hardware.xml:1266 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry #: hardware.xml:1269 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry #: hardware.xml:1270 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: entry #: hardware.xml:1273 #, no-c-format msgid "Fixstars" msgstr "" #. Tag: entry #: hardware.xml:1274 #, no-c-format msgid "YDL PowerStation" msgstr "" #. Tag: title #: hardware.xml:1282 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry #: hardware.xml:1298 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry #: hardware.xml:1299 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title #: hardware.xml:1307 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para #: hardware.xml:1309 #, 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:1346 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para #: hardware.xml:1348 #, 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:1357 #, 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:1365 #, 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:1379 #, no-c-format msgid "Machines" msgstr "" #. Tag: para #: hardware.xml:1382 #, no-c-format msgid "S822L" msgstr "" #. Tag: para #: hardware.xml:1387 #, no-c-format msgid "S821L" msgstr "" #. Tag: para #: hardware.xml:1392 #, no-c-format msgid "S822" msgstr "" #. Tag: para #: hardware.xml:1397 #, no-c-format msgid "S821" msgstr "" #. Tag: para #: hardware.xml:1402 #, no-c-format msgid "TYAN GN70-BP010" msgstr "" #. Tag: title #: hardware.xml:1417 #, no-c-format msgid "zSeries and System z machine types" msgstr "" #. Tag: para #: hardware.xml:1418 #, no-c-format msgid "" "The minimum required z/Architecture processor type is z196. 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:1431 #, no-c-format msgid "PAV and HyperPAV" msgstr "" #. Tag: para #: hardware.xml:1432 #, 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:1448 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para #: hardware.xml:1449 #, 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:1460 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para #: hardware.xml:1462 #, 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:1469 #, 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:1479 #, no-c-format msgid "sun4u" msgstr "" #. Tag: para #: hardware.xml:1481 #, 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:1494 #, no-c-format msgid "sun4v" msgstr "" #. Tag: para #: hardware.xml:1496 #, 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:1507 #, 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:1516 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para #: hardware.xml:1517 #, 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:1534 hardware.xml:1554 hardware.xml:1576 hardware.xml:1599 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para #: hardware.xml:1535 #, 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:1545 #, 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:1556 #, 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:1565 #, 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:1577 #, 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:1586 #, 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:1600 #, 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:1610 #, 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:1616 #, 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:1627 #, no-c-format msgid "Graphics Hardware Support" msgstr "" #. Tag: para #: hardware.xml:1628 #, no-c-format msgid "" "&debian;'s support for graphical interfaces is determined by the underlying " "support found in X.Org's X11 system, and the kernel. Basic framebuffer " "graphics is provided by the kernel, whilst desktop environments use X11. " "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 )." msgstr "" #. Tag: para #: hardware.xml:1640 #, no-c-format msgid "" "On modern PCs, having a graphical display usually works out of the box. 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. For quite a lot of hardware, " "3D acceleration also works well out of the box, but there is still some " "hardware that needs binary blobs to work well." msgstr "" #. Tag: para #: hardware.xml:1651 #, no-c-format msgid "" "Nearly all ARM machines have the graphics hardware built-in, rather than " "being on a plug-in card. Some machines do have expansion slots which will " "take graphics cards, but that is a rarity. Hardware designed to be headless " "with no graphics at all is quite common. Whilst basic framebuffer video " "provided by the kernel should work on all devices that have graphics, fast " "3D graphics invariably needs binary drivers to work. The situation is " "changing quickly but at the time of the &releasename; release free drivers " "for nouveau (Nvidia Tegra K1 SoC) and freedreno (Qualcomm Snapdragon SoCs) " "are available in the release. Other hardware needs non-free drivers from 3rd " "parties." msgstr "" #. Tag: para #: hardware.xml:1665 #, no-c-format msgid "" "Details on supported graphics hardware and pointing devices can be found at " ". &debian; &release; ships with X.Org " "version &x11ver;." msgstr "" #. Tag: para #: hardware.xml:1670 #, 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:1680 #, 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:1702 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para #: hardware.xml:1703 #, 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:1713 #, 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:1719 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para #: hardware.xml:1724 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para #: hardware.xml:1729 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para #: hardware.xml:1734 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para #: hardware.xml:1739 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para #: hardware.xml:1746 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para #: hardware.xml:1751 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para #: hardware.xml:1756 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para #: hardware.xml:1761 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para #: hardware.xml:1770 #, 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:1775 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title #: hardware.xml:1782 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para #: hardware.xml:1783 #, 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:1790 #, 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:1795 #, 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:1800 #, 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:1810 #, 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:1824 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para #: hardware.xml:1825 #, no-c-format msgid "" "There are a couple of issues with specific network cards that are worth " "mentioning here." msgstr "" #. Tag: title #: hardware.xml:1832 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para #: hardware.xml:1834 #, 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:1844 #, 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:1852 #, 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:1865 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para #: hardware.xml:1867 #, no-c-format msgid "" "The cassini network driver does not work with Sun B100 " "blade systems." msgstr "" #. Tag: title #: hardware.xml:1882 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para #: hardware.xml:1883 #, 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:1897 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para #: hardware.xml:1898 #, 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:1918 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para #: hardware.xml:1919 #, 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:1925 #, 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:1934 #, 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:1947 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para #: hardware.xml:1948 #, 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:1959 #, 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:1967 #, 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:1976 #, 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:1985 #, 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:2002 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "" #. Tag: para #: hardware.xml:2004 #, 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:2012 #, 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:2020 #, 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:2031 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para #: hardware.xml:2032 #, 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:2042 #, 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:2054 #, 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:2065 #, 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:2078 #, 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:2093 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para #: hardware.xml:2095 #, 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:2105 #, no-c-format msgid "CD-ROM/DVD-ROM/BD-ROM" msgstr "" #. Tag: para #: hardware.xml:2107 #, no-c-format msgid "Installation from optical disc is supported for most architectures." msgstr "" #. Tag: para #: hardware.xml:2111 #, no-c-format msgid "" "On PCs SATA, IDE/ATAPI, USB and SCSI optical drives are supported, as are " "FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: title #: hardware.xml:2128 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para #: hardware.xml:2130 #, 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 an optical drive anymore at all and booting " "from USB media is the standard way of installing a new operating system on " "them." msgstr "" #. Tag: title #: hardware.xml:2142 #, no-c-format msgid "Network" msgstr "" #. Tag: para #: hardware.xml:2144 #, 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:2154 #, 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:2167 #, 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:2176 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para #: hardware.xml:2178 #, 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:2185 #, 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:2194 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para #: hardware.xml:2196 #, 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:2209 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para #: hardware.xml:2211 #, 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:2215 #, 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:2232 #, 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:2277 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system." msgstr "" #. Tag: para #: hardware.xml:2282 #, 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:2299 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para #: hardware.xml:2301 #, 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:2308 #, no-c-format msgid "" "The installer normally automatically enables memory-saving tricks to be able " "to run on such low-memory system, but on architectures that are less tested " "it may miss doing so. It can however be enabled manually by appending the " "lowmem=1 or even lowmem=2 boot " "parameter (see also and )." msgstr "" #. Tag: para #: hardware.xml:2317 #, no-c-format msgid "" "On &architecture; the lowmem levels have not been tested, so automatic " "detection is probably outdated and you thus probably need to pass the boot parameter if your system has little memory." msgstr "" #. Tag: para #: hardware.xml:2323 #, 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 on such systems. or disk space " "available may be possible but is only advised for experienced users." msgstr ""