diff options
| author | Holger Wansing <linux@wansing-online.de> | 2015-05-04 18:32:24 +0000 |
|---|---|---|
| committer | Holger Wansing <linux@wansing-online.de> | 2015-05-04 18:32:24 +0000 |
| commit | 2c3e77286f206ba02897e9b1706ec40e2272d6af (patch) | |
| tree | 71ce09d21ca8e97e8b91a3eb06bdf2c0066253f9 /po/pot | |
| parent | 7c988d32d2c0f7cfd59d1eebb67f7f8ca202cd41 (diff) | |
| download | installation-guide-2c3e77286f206ba02897e9b1706ec40e2272d6af.zip | |
Refresh pot and po files after changings in en
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 858 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 612 | ||||
| -rw-r--r-- | po/pot/partitioning.pot | 4 |
3 files changed, 791 insertions, 683 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 80fdbd9e9..c151c57e2 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2015-04-15 20:29+0000\n" +"POT-Creation-Date: 2015-05-04 18:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -39,85 +39,145 @@ msgid "For information on how to boot the graphical installer, see <xref linkend msgstr "" #. Tag: title -#: boot-installer.xml:38 +#: boot-installer.xml:39 #, no-c-format msgid "Boot image formats" msgstr "" #. Tag: para -#: boot-installer.xml:39 +#: boot-installer.xml:40 #, no-c-format msgid "On ARM-based systems in most cases one of two formats for boot images is used: a) standard Linux zImage-format kernels (<quote>vmlinuz</quote>) in conjunction with standard Linux initial ramdisks (<quote>initrd.gz</quote>) or b) uImage-format kernels (<quote>uImage</quote>) in conjunction with corresponding initial ramdisks (<quote>uInitrd</quote>)." msgstr "" #. Tag: para -#: boot-installer.xml:47 +#: boot-installer.xml:48 #, no-c-format -msgid "uImage/uInitrd are image formats designed for the U-Boot firmware that is used on many ARM-based systems. Older U-Boot versions can only boot files in uImage/uInitrd format, so these are often used on older armel systems. Newer U-Boot versions can - besides booting uImages/uInitrds - also boot standard Linux kernels and ramdisk images, but the command syntax to do that is slightly different from that for booting uImages." +msgid "uImage/uInitrd are image formats designed for the U-Boot firmware that is used on many ARM-based systems (mostly 32-bit ones). Older U-Boot versions can only boot files in uImage/uInitrd format, so these are often used on older armel systems. Newer U-Boot versions can - besides booting uImages/uInitrds - also boot standard Linux kernels and ramdisk images, but the command syntax to do that is slightly different from that for booting uImages." msgstr "" #. Tag: para -#: boot-installer.xml:56 +#: boot-installer.xml:57 #, no-c-format -msgid "For systems using a multiplatform kernel, besides kernel and initial ramdisk a so-called device-tree file (or device-tree blob, <quote>dtb</quote>) is needed. It is specific to each supported system and contains a description of the particular hardware." +msgid "For systems using a multiplatform kernel, besides kernel and initial ramdisk a so-called device-tree file (or device-tree blob, <quote>dtb</quote>) is needed. It is specific to each supported system and contains a description of the particular hardware. The dtb should be supplied on the device by the firmware, but in practice a newer one often needs to be loaded." msgstr "" #. Tag: title -#: boot-installer.xml:65 +#: boot-installer.xml:68 boot-installer.xml:86 #, no-c-format msgid "Console configuration" msgstr "" #. Tag: para -#: boot-installer.xml:66 +#: boot-installer.xml:69 #, no-c-format -msgid "The netboot tarball (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), the hd-media tarball (<xref linkend=\"boot-hd-media\"/>) and the installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) use the (platform-specific) default console that is defined by U-Boot in the <quote>console</quote> variable. In most cases that is a serial console, so on those platforms you by default need a serial console cable to use the installer." +msgid "The netboot tarball (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), and the installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) use the (platform-specific) default console that is defined by U-Boot in the <quote>console</quote> variable. In most cases that is a serial console, so on those platforms you by default need a serial console cable to use the installer." msgstr "" #. Tag: para -#: boot-installer.xml:75 +#: boot-installer.xml:78 #, no-c-format msgid "On platforms which also support a video console, you can modify the U-Boot <quote>console</quote> variable accordingly if you would like the installer to start on the video console." msgstr "" +#. Tag: para +#: boot-installer.xml:87 +#, no-c-format +msgid "The graphical installer is not enabled on the arm64 &d-i; images for jessie so the serial console is used. The console device should be detected automatically from the firmware, but if it is not then after you boot linux from the GRUB menu you will see a 'Booting Linux' message then nothing more." +msgstr "" + +#. Tag: para +#: boot-installer.xml:94 +#, no-c-format +msgid "If you hit this issue you will need to set a specific console config on the kernel command line. Hit <userinput>e</userinput> for 'Edit Kernel command-line' at the GRUB menu, and change <informalexample><screen>--- quiet</screen></informalexample> to <informalexample><screen>console=<device>,<speed></screen></informalexample> e.g. <informalexample><screen>console=ttyAMA0,115200n8</screen></informalexample> When finished hit <keycombo><keycap>Control</keycap> <keycap>x</keycap></keycombo> to continue booting with new setting." +msgstr "" + +#. Tag: title +#: boot-installer.xml:108 +#, no-c-format +msgid "Juno Installation" +msgstr "" + +#. Tag: para +#: boot-installer.xml:109 +#, no-c-format +msgid "Juno has UEFI so the install is straightforward. The most practical method is installing from USB stick. You need up to date firmware for USB-booting to work. Builds from <ulink url=\"&url-juno-firmware;\">&url-juno-firmware;</ulink> after March 2015 tested OK. Consult Juno documentation on firmware updating." +msgstr "" + +#. Tag: para +#: boot-installer.xml:116 +#, no-c-format +msgid "Prepare a standard arm64 CD image on a USB stick. Insert it in one of the USB ports on the back. Plug a serial cable into the upper 9-pin serial port on the back. If you need networking (netboot image) plug the ethernet cable into the socket on the front of the machine." +msgstr "" + +#. Tag: para +#: boot-installer.xml:123 +#, no-c-format +msgid "Run a serial console at 115200, 8bit no parity, and boot the Juno. It should boot from the USB stick to a GRUB menu. The console config is not correctly detected on Juno so just hitting return will show no kernel output. Set the console to <informalexample><screen>console=ttyAMA0,115200n8</screen></informalexample> as described in (<xref linkend=\"arm64-console-setup\"/>). <keycombo><keycap>Control</keycap> <keycap>x</keycap></keycombo> to boot should show you the &d-i; screens, and allow you to proceed with a standard installation." +msgstr "" + +#. Tag: title +#: boot-installer.xml:136 +#, no-c-format +msgid "Applied Micro Mustang Installation" +msgstr "" + +#. Tag: para +#: boot-installer.xml:137 +#, no-c-format +msgid "UEFI is available for this machine but it is normally shipped with U-Boot so you will need to either install UEFI firmware first then use standard boot/install methods, or use U-Boot boot methods. Also USB is not supported in the jessie kernel so installing from a USB stick does not work. You must use a serial console to control the installation because the graphical installer is not enabled on the arm64 architecture." +msgstr "" + +#. Tag: para +#: boot-installer.xml:146 +#, no-c-format +msgid "The recommended install method is to copy the &d-i; kernel and initrd onto the hard drive, using the openembedded system supplied with the machine, then boot from that to run the installer. Alternatively use TFTP to get the kernel/dtb/initrd copied over and booted (<xref linkend=\"boot-tftp-uboot\"/>). After installation, manual changes to boot from the installed image are needed." +msgstr "" + +#. Tag: para +#: boot-installer.xml:155 +#, no-c-format +msgid "Run a serial console at 115200, 8bit no parity, and boot the machine. Reboot the machine and when you see \"Hit any key to stop autoboot:\" hit a key to get a Mustang# prompt. Then use U-Boot commands to load and boot the kernel, dtb and initrd." +msgstr "" + #. Tag: title -#: boot-installer.xml:82 +#: boot-installer.xml:164 #, no-c-format msgid "Booting by TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:88 boot-installer.xml:727 boot-installer.xml:1362 boot-installer.xml:1546 boot-installer.xml:1868 boot-installer.xml:2016 +#: boot-installer.xml:170 boot-installer.xml:832 boot-installer.xml:1467 boot-installer.xml:1651 boot-installer.xml:1973 boot-installer.xml:2121 #, no-c-format msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server for automatic network configuration)." msgstr "" #. Tag: para -#: boot-installer.xml:94 boot-installer.xml:733 boot-installer.xml:1368 boot-installer.xml:1552 boot-installer.xml:1874 boot-installer.xml:2022 +#: boot-installer.xml:176 boot-installer.xml:838 boot-installer.xml:1473 boot-installer.xml:1657 boot-installer.xml:1979 boot-installer.xml:2127 #, no-c-format msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." msgstr "" #. Tag: para -#: boot-installer.xml:99 boot-installer.xml:738 boot-installer.xml:1373 boot-installer.xml:1557 boot-installer.xml:1879 boot-installer.xml:2027 +#: boot-installer.xml:181 boot-installer.xml:843 boot-installer.xml:1478 boot-installer.xml:1662 boot-installer.xml:1984 boot-installer.xml:2132 #, no-c-format msgid "The server-side setup to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:108 +#: boot-installer.xml:190 #, no-c-format msgid "TFTP-booting in U-Boot" msgstr "" #. Tag: para -#: boot-installer.xml:109 +#: boot-installer.xml:191 #, no-c-format msgid "Network booting on systems using the U-Boot firmware consists of three steps: a) configuring the network, b) loading the images (kernel/initial ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" #. Tag: para -#: boot-installer.xml:115 +#: boot-installer.xml:197 #, no-c-format msgid "" "First you have to configure the network, either automatically via DHCP by running <informalexample><screen>\n" @@ -133,19 +193,19 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:122 +#: boot-installer.xml:204 #, no-c-format msgid "saveenv" msgstr "" #. Tag: para -#: boot-installer.xml:124 +#: boot-installer.xml:206 #, no-c-format msgid "Afterwards you need to load the images (kernel/initial ramdisk/dtb) into memory. This is done with the tftpboot command, which has to be provided with the address at which the image shall be stored in memory. Unfortunately the memory map can vary from system to system, so there is no general rule which addresses can be used for this." msgstr "" #. Tag: para -#: boot-installer.xml:132 +#: boot-installer.xml:214 #, no-c-format msgid "" "On some systems, U-Boot predefines a set of environment variables with suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You can check whether they are defined by running <informalexample><screen>\n" @@ -154,7 +214,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:143 +#: boot-installer.xml:225 #, no-c-format msgid "" "setenv kernel_addr_r 0x46000000\n" @@ -163,13 +223,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:145 +#: boot-installer.xml:227 #, no-c-format msgid "When the load addresses are defined, you can load the images into memory from the previously defined tftp server with" msgstr "" #. Tag: screen -#: boot-installer.xml:148 +#: boot-installer.xml:230 #, no-c-format msgid "" "tftpboot ${kernel_addr_r} <filename of the kernel image>\n" @@ -178,7 +238,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:150 +#: boot-installer.xml:232 #, no-c-format msgid "" "The third part is setting the kernel commandline and actually executing the loaded code. U-Boot passes the content of the <quote>bootargs</quote> environment variable as commandline to the kernel, so any parameters for the kernel and the installer - such as the console device (see <xref linkend=\"boot-console\"/>) or preseeding options (see <xref linkend=\"installer-args\"/> and <xref linkend=\"appendix-preseed\"/>) - can be set with a command like <informalexample><screen>\n" @@ -189,49 +249,49 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:163 +#: boot-installer.xml:245 #, no-c-format msgid "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" msgstr "" #. Tag: para -#: boot-installer.xml:165 +#: boot-installer.xml:247 #, no-c-format msgid "Note: When booting standard linux images, it is important to load the initial ramdisk image after the kernel and the dtb as U-Boot sets the filesize variable to the size of the last file loaded and the bootz command requires the size of the ramdisk image to work correctly. In case of booting a platform-specific kernel, i.e. a kernel without device-tree, simply omit the ${fdt_addr_r} parameter." msgstr "" #. Tag: title -#: boot-installer.xml:176 +#: boot-installer.xml:258 #, no-c-format msgid "Pre-built netboot tarball" msgstr "" #. Tag: para -#: boot-installer.xml:177 +#: boot-installer.xml:259 #, no-c-format msgid "&debian; provides a pre-built tarball (&armmp-netboot-tarball;) that can simply be unpacked on your tftp server and contains all files necessary for netbooting. It also includes a boot script that automates all steps to load the installer. Modern U-Boot versions contain a tftp autoboot feature that becomes active if there is no bootable local storage device (MMC/SD, USB, IDE/SATA/SCSI) and then loads this boot script from the tftp server. Prerequisite for using this feature is that you have a dhcp server in your network which provides the client with the address of the tftp server." msgstr "" #. Tag: para -#: boot-installer.xml:189 +#: boot-installer.xml:271 #, no-c-format msgid "If you would like to trigger the tftp autoboot feature from the U-Boot commandline, you can use the follwing command:" msgstr "" #. Tag: screen -#: boot-installer.xml:192 +#: boot-installer.xml:274 #, no-c-format msgid "run bootcmd_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:194 +#: boot-installer.xml:276 #, no-c-format msgid "To manually load the bootscript provided by the tarball, you can alternatively issue the following commands at the U-Boot prompt:" msgstr "" #. Tag: screen -#: boot-installer.xml:198 +#: boot-installer.xml:280 #, no-c-format msgid "" "setenv autoload no\n" @@ -241,163 +301,169 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:206 +#: boot-installer.xml:288 +#, no-c-format +msgid "Booting from USB Memory Stick with UEFI" +msgstr "" + +#. Tag: para +#: boot-installer.xml:294 boot-installer.xml:553 +#, no-c-format +msgid "If your computer will boot from USB, this will probably be the easiest route for installation. Assuming you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>, just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with a graphical boot menu (on hardware that supports it). Here you can select various installer options, or just hit &enterkey;." +msgstr "" + +#. Tag: title +#: boot-installer.xml:310 #, no-c-format msgid "Booting from a USB stick in U-Boot" msgstr "" #. Tag: para -#: boot-installer.xml:207 +#: boot-installer.xml:311 #, no-c-format msgid "Many modern U-Boot versions have USB support and allow booting from USB mass storage devices such as USB sticks. Unfortunately the exact steps required to do that can vary quite a bit from device to device." msgstr "" #. Tag: para -#: boot-installer.xml:214 +#: boot-installer.xml:318 #, no-c-format msgid "U-Boot v2014.10 has introduced a common commandline handling and autoboot framework. This allows building generic boot images that work on any system implementing this framework. The &d-i; supports installation from a USB stick on such systems, but unfortunately not all platforms have adopted this new framework yet." msgstr "" #. Tag: para -#: boot-installer.xml:223 +#: boot-installer.xml:327 #, no-c-format msgid "To build a bootable USB stick for installing &debian;, unpack the hd-media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick formatted with a filesystem supported by the U-Boot version on your device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. Then copy the ISO image file of the first &debian; installation CD or DVD onto the stick." msgstr "" #. Tag: para -#: boot-installer.xml:233 +#: boot-installer.xml:337 #, no-c-format msgid "The autoboot framework in modern U-Boot versions works similar to the boot ordering options in a PC BIOS, i.e. it checks a list of possible boot devices for a valid boot image and starts the first one it finds. If there is no operating system installed, plugging in the USB stick and powering up the system should result in starting the installer. You can also initiate the USB-boot process any time from the U-Boot prompt by entering the <quote>run bootcmd_usb0</quote> command." msgstr "" #. Tag: para -#: boot-installer.xml:243 +#: boot-installer.xml:347 #, no-c-format msgid "One problem that can come up when booting from a USB stick while using a serial console can be a console baudrate mismatch. If a console variable is defined in U-Boot, the &d-i; boot script automatically passes it to the kernel to set the primary console device and, if applicable, the console baudrate. Unfortunately the handling of the console variable varies from platform to platform - on some platforms, the console variable includes the baudrate (as in <quote>console=ttyS0,115200</quote>), while on other platforms the console variable contains only the device (as in <quote>console=ttyS0</quote>). The latter case leads to a garbled console output when the default baudrate differs between U-Boot and the kernel. Modern U-Boot versions often use 115200 baud while the kernel still defaults to the traditional 9600 baud. If this happens, you should manually set the console variable to contain the correct baudrate for your system and then start the installer with the <quote>run bootcmd_usb0</quote> command." msgstr "" #. Tag: title -#: boot-installer.xml:264 +#: boot-installer.xml:368 #, no-c-format msgid "Using pre-built SD-card images with the installer" msgstr "" #. Tag: para -#: boot-installer.xml:265 +#: boot-installer.xml:369 #, no-c-format msgid "For a number of systems, Debian provides SD card images that contain both U-Boot and the &d-i;. These images are provided in two variants - one for downloading the software packages over the network (available at &armmp-netboot-sd-img;) and one for offline installations using a Debian CD/DVD (available at &armmp-hd-media-sd-img;). To save space and network bandwidth, the images consist of two parts - a system-dependent part named <quote>firmware.<system-type>.img.gz</quote>, and a system-independent part named <quote>partition.img.gz</quote>." msgstr "" #. Tag: para -#: boot-installer.xml:276 +#: boot-installer.xml:380 #, no-c-format msgid "To create a complete image from the two parts on Linux systems, you can use zcat as follows: <informalexample><screen>zcat firmware.<system-type>.img.gz partition.img.gz > complete_image.img</screen></informalexample> On Windows systems, you have to first decompress the two parts separately, which can be done e.g. by using 7-Zip, and then concatenate the decompressed parts together by running the command <informalexample><screen>copy /b firmware.<system-type>.img + partition.img complete_image.img</screen></informalexample> in a Windows CMD.exe window." msgstr "" #. Tag: para -#: boot-installer.xml:290 +#: boot-installer.xml:394 #, no-c-format msgid "Write the resulting image onto an SD card, e.g. by running the following command on a Linux system: <informalexample><screen>cat complete_image.img > /dev/SD_CARD_DEVICE</screen></informalexample> After plugging the SD card into the target system and powering the system up, the installer is loaded from the SD card. If you use the hd-media variant for offline installations, you must provide the installer with access to the first &debian; CD/DVD on a separate medium, which can e.g. be a CD/DVD ISO image on a USB stick." msgstr "" #. Tag: para -#: boot-installer.xml:302 +#: boot-installer.xml:406 #, no-c-format msgid "When you come to the partitioning step in the installer (see <xref linkend=\"di-partition\"/>), you can delete or replace any previous partitions on the card. Once the installer is started, it runs completely in the system's main memory and does not need to access the SD card anymore, so you can use the full card for installing &debian;. The easiest way to create a proper partition layout on the SD card is to let the installer automatically create one for you (see <xref linkend=\"partman-auto\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:443 +#: boot-installer.xml:547 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" -#. Tag: para -#: boot-installer.xml:449 -#, no-c-format -msgid "If your computer will boot from USB, this will probably be the easiest route for installation. Assuming you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>, just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with a graphical boot menu. Here you can select various installer options, or just hit &enterkey;." -msgstr "" - #. Tag: title -#: boot-installer.xml:463 boot-installer.xml:976 boot-installer.xml:1632 boot-installer.xml:2050 +#: boot-installer.xml:568 boot-installer.xml:1081 boot-installer.xml:1737 boot-installer.xml:2155 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:469 boot-installer.xml:982 boot-installer.xml:1638 boot-installer.xml:2056 +#: boot-installer.xml:574 boot-installer.xml:1087 boot-installer.xml:1743 boot-installer.xml:2161 #, no-c-format msgid "If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter." msgstr "" #. Tag: para -#: boot-installer.xml:479 boot-installer.xml:992 boot-installer.xml:1648 boot-installer.xml:2066 +#: boot-installer.xml:584 boot-installer.xml:1097 boot-installer.xml:1753 boot-installer.xml:2171 #, no-c-format msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you." msgstr "" #. Tag: para -#: boot-installer.xml:487 boot-installer.xml:1000 boot-installer.xml:1656 boot-installer.xml:2074 +#: boot-installer.xml:592 boot-installer.xml:1105 boot-installer.xml:1761 boot-installer.xml:2179 #, no-c-format msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different medium and when it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive." msgstr "" #. Tag: para -#: boot-installer.xml:495 boot-installer.xml:1008 boot-installer.xml:1664 boot-installer.xml:2082 +#: boot-installer.xml:600 boot-installer.xml:1113 boot-installer.xml:1769 boot-installer.xml:2187 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:505 +#: boot-installer.xml:610 #, no-c-format msgid "Booting from Windows" msgstr "" #. Tag: para -#: boot-installer.xml:506 +#: boot-installer.xml:611 #, no-c-format msgid "To start the installer from Windows, you can either" msgstr "" #. Tag: para -#: boot-installer.xml:511 +#: boot-installer.xml:616 #, no-c-format msgid "obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory stick</phrase> installation media as described in <xref linkend=\"official-cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-usb-files\"/></phrase> or" msgstr "" #. Tag: para -#: boot-installer.xml:519 +#: boot-installer.xml:624 #, no-c-format msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors." msgstr "" #. Tag: para -#: boot-installer.xml:527 +#: boot-installer.xml:632 #, no-c-format msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>." msgstr "" #. Tag: para -#: boot-installer.xml:535 +#: boot-installer.xml:640 #, no-c-format msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer." msgstr "" #. Tag: title -#: boot-installer.xml:545 +#: boot-installer.xml:650 #, no-c-format msgid "Booting from DOS using loadlin" msgstr "" #. Tag: para -#: boot-installer.xml:546 +#: boot-installer.xml:651 #, no-c-format msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk." msgstr "" #. Tag: para -#: boot-installer.xml:551 +#: boot-installer.xml:656 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n" @@ -406,7 +472,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:561 +#: boot-installer.xml:666 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n" @@ -417,37 +483,37 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:579 +#: boot-installer.xml:684 #, no-c-format msgid "Booting from Linux using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: boot-installer.xml:582 +#: boot-installer.xml:687 #, no-c-format msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:587 +#: boot-installer.xml:692 #, no-c-format msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." msgstr "" #. Tag: para -#: boot-installer.xml:597 +#: boot-installer.xml:702 #, no-c-format msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network." msgstr "" #. Tag: para -#: boot-installer.xml:606 +#: boot-installer.xml:711 #, no-c-format msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:" msgstr "" #. Tag: screen -#: boot-installer.xml:627 +#: boot-installer.xml:732 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -456,19 +522,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:627 +#: boot-installer.xml:732 #, no-c-format msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot." msgstr "" #. Tag: para -#: boot-installer.xml:636 +#: boot-installer.xml:741 #, no-c-format msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):" msgstr "" #. Tag: screen -#: boot-installer.xml:644 +#: boot-installer.xml:749 #, no-c-format msgid "" "title New Install\n" @@ -478,13 +544,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:646 +#: boot-installer.xml:751 #, no-c-format msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:" msgstr "" #. Tag: screen -#: boot-installer.xml:652 +#: boot-installer.xml:757 #, no-c-format msgid "" "menuentry 'New Install' {\n" @@ -497,127 +563,127 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:654 +#: boot-installer.xml:759 #, no-c-format msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>." msgstr "" #. Tag: title -#: boot-installer.xml:663 boot-installer.xml:1918 +#: boot-installer.xml:768 boot-installer.xml:2023 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:664 boot-installer.xml:1926 +#: boot-installer.xml:769 boot-installer.xml:2031 #, no-c-format msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:671 +#: boot-installer.xml:776 #, no-c-format msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on." msgstr "" #. Tag: para -#: boot-installer.xml:677 +#: boot-installer.xml:782 #, no-c-format msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:687 +#: boot-installer.xml:792 #, no-c-format msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting." msgstr "" #. Tag: para -#: boot-installer.xml:696 +#: boot-installer.xml:801 #, no-c-format msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." msgstr "" #. Tag: para -#: boot-installer.xml:702 +#: boot-installer.xml:807 #, no-c-format msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:711 +#: boot-installer.xml:816 #, no-c-format msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched." msgstr "" #. Tag: title -#: boot-installer.xml:721 boot-installer.xml:1344 boot-installer.xml:1486 boot-installer.xml:1540 boot-installer.xml:1862 boot-installer.xml:2010 +#: boot-installer.xml:826 boot-installer.xml:1449 boot-installer.xml:1591 boot-installer.xml:1645 boot-installer.xml:1967 boot-installer.xml:2115 #, no-c-format msgid "Booting with TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:746 +#: boot-installer.xml:851 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:752 +#: boot-installer.xml:857 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:753 +#: boot-installer.xml:858 #, no-c-format msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network." msgstr "" #. Tag: title -#: boot-installer.xml:764 +#: boot-installer.xml:869 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:765 +#: boot-installer.xml:870 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:770 +#: boot-installer.xml:875 #, no-c-format msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." msgstr "" #. Tag: title -#: boot-installer.xml:778 +#: boot-installer.xml:883 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:779 +#: boot-installer.xml:884 #, no-c-format msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title -#: boot-installer.xml:789 +#: boot-installer.xml:894 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:790 +#: boot-installer.xml:895 #, no-c-format msgid "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu:" msgstr "" #. Tag: screen -#: boot-installer.xml:795 +#: boot-installer.xml:900 #, no-c-format msgid "" "Installer boot menu\n" @@ -630,37 +696,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:799 +#: boot-installer.xml:904 #, no-c-format msgid "This graphical screen will look very slightly different depending on how your computer has booted (BIOS or UEFI), but the same options will be shown." msgstr "" #. Tag: para -#: boot-installer.xml:807 +#: boot-installer.xml:912 #, no-c-format msgid "Depending on the installation method you are using, the <quote>Graphical install</quote> option may not be available. Bi-arch images additionally have a 64 bit variant for each install option, right below it, thus almost doubling the number of options." msgstr "" #. Tag: para -#: boot-installer.xml:814 +#: boot-installer.xml:919 #, no-c-format -msgid "For a normal installation, select either the <quote>Graphical install</quote> or the <quote>Install</quote> entry — using either the arrow keys on your keyboard or by typing the first (highlighted) letter — and press &enterkey; to boot the installer. The <quote>Graphical install</quote> entry is already selected by default." +msgid "For a normal installation, select either the <quote>Graphical install</quote> or the <quote>Install</quote> entry — using either the arrow keys on your keyboard or by typing the first (highlighted) letter — and press &enterkey; to boot the installer. The <quote>Install</quote> entry is already selected by default." msgstr "" #. Tag: para -#: boot-installer.xml:822 +#: boot-installer.xml:927 #, no-c-format msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs." msgstr "" #. Tag: para -#: boot-installer.xml:828 +#: boot-installer.xml:933 #, no-c-format msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey; (BIOS boot) or &ekey; (UEFI boot). This will display the boot command for the selected menu entry and allow you to edit it to suit your needs. The help screens (see below) list some common possible options. Press &enterkey; (BIOS boot) or &f10key; (UEFI boot) to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made." msgstr "" #. Tag: para -#: boot-installer.xml:839 +#: boot-installer.xml:944 #, no-c-format msgid "" "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n" @@ -669,313 +735,313 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:857 +#: boot-installer.xml:962 #, no-c-format msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use." msgstr "" #. Tag: para -#: boot-installer.xml:867 +#: boot-installer.xml:972 #, no-c-format msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)." msgstr "" #. Tag: para -#: boot-installer.xml:877 +#: boot-installer.xml:982 #, no-c-format msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text." msgstr "" #. Tag: title -#: boot-installer.xml:893 +#: boot-installer.xml:998 #, no-c-format msgid "The Graphical Installer" msgstr "" #. Tag: para -#: boot-installer.xml:894 +#: boot-installer.xml:999 #, no-c-format msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the text-based installer as it basically uses the same programs, but with a different frontend." msgstr "" #. Tag: para -#: boot-installer.xml:902 +#: boot-installer.xml:1007 #, no-c-format msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the text-based <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen." msgstr "" #. Tag: para -#: boot-installer.xml:911 +#: boot-installer.xml:1016 #, no-c-format msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:922 +#: boot-installer.xml:1027 #, no-c-format msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing." msgstr "" #. Tag: para -#: boot-installer.xml:935 +#: boot-installer.xml:1040 #, no-c-format msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems." msgstr "" #. Tag: para -#: boot-installer.xml:949 +#: boot-installer.xml:1054 #, no-c-format msgid "Just as with the text-based installer it is possible to add boot parameters when starting the graphical installer." msgstr "" #. Tag: para -#: boot-installer.xml:955 +#: boot-installer.xml:1060 #, no-c-format msgid "The graphical installer requires significantly more memory to run than the text-based installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the text-based <quote>newt</quote> frontend." msgstr "" #. Tag: para -#: boot-installer.xml:962 +#: boot-installer.xml:1067 #, no-c-format msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the text-based installer would still work. Using the text-based installer is recommended for systems with little available memory." msgstr "" #. Tag: title -#: boot-installer.xml:1016 +#: boot-installer.xml:1121 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:1018 +#: boot-installer.xml:1123 #, no-c-format msgid "There are three basic variations of &debian; Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a &debian; mirror site in order to install the extra packages one would want for a complete system . The set of &debian; CDs can install a complete system from the wide range of packages without needing access to the network." msgstr "" #. Tag: para -#: boot-installer.xml:1034 +#: boot-installer.xml:1139 #, no-c-format msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems." msgstr "" #. Tag: para -#: boot-installer.xml:1050 +#: boot-installer.xml:1155 #, no-c-format msgid "The &debian; Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below." msgstr "" #. Tag: para -#: boot-installer.xml:1059 +#: boot-installer.xml:1164 #, no-c-format msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed." msgstr "" #. Tag: para -#: boot-installer.xml:1071 +#: boot-installer.xml:1176 #, no-c-format msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option." msgstr "" #. Tag: title -#: boot-installer.xml:1090 +#: boot-installer.xml:1195 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:1091 +#: boot-installer.xml:1196 #, no-c-format msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt." msgstr "" #. Tag: title -#: boot-installer.xml:1103 +#: boot-installer.xml:1208 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:1110 +#: boot-installer.xml:1215 #, no-c-format msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization." msgstr "" #. Tag: para -#: boot-installer.xml:1116 +#: boot-installer.xml:1221 #, no-c-format msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu." msgstr "" #. Tag: para -#: boot-installer.xml:1122 +#: boot-installer.xml:1227 #, no-c-format msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same." msgstr "" #. Tag: para -#: boot-installer.xml:1133 +#: boot-installer.xml:1238 #, no-c-format msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step." msgstr "" #. Tag: para -#: boot-installer.xml:1144 +#: boot-installer.xml:1249 #, no-c-format msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" #. Tag: para -#: boot-installer.xml:1156 +#: boot-installer.xml:1261 #, no-c-format msgid "These steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options." msgstr "" #. Tag: title -#: boot-installer.xml:1166 +#: boot-installer.xml:1271 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:1167 +#: boot-installer.xml:1272 #, no-c-format msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with the following steps:" msgstr "" #. Tag: para -#: boot-installer.xml:1178 +#: boot-installer.xml:1283 #, no-c-format msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization." msgstr "" #. Tag: para -#: boot-installer.xml:1184 +#: boot-installer.xml:1289 #, no-c-format msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1198 +#: boot-installer.xml:1303 #, no-c-format msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>." msgstr "" #. Tag: para -#: boot-installer.xml:1205 +#: boot-installer.xml:1310 #, no-c-format msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt." msgstr "" #. Tag: para -#: boot-installer.xml:1212 +#: boot-installer.xml:1317 #, no-c-format msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" #. Tag: para -#: boot-installer.xml:1219 +#: boot-installer.xml:1324 #, no-c-format msgid "As with option 1, these steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options." msgstr "" #. Tag: title -#: boot-installer.xml:1233 +#: boot-installer.xml:1338 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1235 +#: boot-installer.xml:1340 #, no-c-format msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured." msgstr "" #. Tag: para -#: boot-installer.xml:1246 +#: boot-installer.xml:1351 #, no-c-format msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell." msgstr "" #. Tag: para -#: boot-installer.xml:1253 +#: boot-installer.xml:1358 #, no-c-format msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window." msgstr "" #. Tag: para -#: boot-installer.xml:1264 +#: boot-installer.xml:1369 #, no-c-format msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode." msgstr "" #. Tag: para -#: boot-installer.xml:1273 +#: boot-installer.xml:1378 #, no-c-format msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation." msgstr "" #. Tag: title -#: boot-installer.xml:1282 +#: boot-installer.xml:1387 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1284 +#: boot-installer.xml:1389 #, no-c-format msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options." msgstr "" #. Tag: para -#: boot-installer.xml:1296 +#: boot-installer.xml:1401 #, no-c-format msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:" msgstr "" #. Tag: para -#: boot-installer.xml:1314 +#: boot-installer.xml:1419 #, no-c-format msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys." msgstr "" #. Tag: para -#: boot-installer.xml:1319 +#: boot-installer.xml:1424 #, no-c-format msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified." msgstr "" #. Tag: para -#: boot-installer.xml:1326 +#: boot-installer.xml:1431 #, no-c-format msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the &debian; Installer." msgstr "" #. Tag: para -#: boot-installer.xml:1335 boot-installer.xml:1472 +#: boot-installer.xml:1440 boot-installer.xml:1577 #, no-c-format msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions." msgstr "" #. Tag: para -#: boot-installer.xml:1346 +#: boot-installer.xml:1451 #, no-c-format msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1381 +#: boot-installer.xml:1486 #, no-c-format msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network." msgstr "" #. Tag: title -#: boot-installer.xml:1392 +#: boot-installer.xml:1497 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1393 +#: boot-installer.xml:1498 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" @@ -988,13 +1054,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1403 +#: boot-installer.xml:1508 #, no-c-format msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system." msgstr "" #. Tag: screen -#: boot-installer.xml:1413 +#: boot-installer.xml:1518 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -1006,37 +1072,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1413 +#: boot-installer.xml:1518 #, no-c-format msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details." msgstr "" #. Tag: title -#: boot-installer.xml:1430 +#: boot-installer.xml:1535 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1431 +#: boot-installer.xml:1536 #, no-c-format msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server." msgstr "" #. Tag: para -#: boot-installer.xml:1463 +#: boot-installer.xml:1568 #, no-c-format msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the &debian; Installer." msgstr "" #. Tag: title -#: boot-installer.xml:1489 boot-installer.xml:1513 +#: boot-installer.xml:1594 boot-installer.xml:1618 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1490 +#: boot-installer.xml:1595 #, no-c-format msgid "" "After entering the command monitor use <informalexample><screen>\n" @@ -1047,19 +1113,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1510 boot-installer.xml:2301 +#: boot-installer.xml:1615 boot-installer.xml:2406 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1514 +#: boot-installer.xml:1619 #, no-c-format msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor." msgstr "" #. Tag: para -#: boot-installer.xml:1519 +#: boot-installer.xml:1624 #, no-c-format msgid "" "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n" @@ -1068,43 +1134,43 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1529 +#: boot-installer.xml:1634 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title -#: boot-installer.xml:1572 +#: boot-installer.xml:1677 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:1573 +#: boot-installer.xml:1678 #, no-c-format msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." msgstr "" #. Tag: para -#: boot-installer.xml:1578 +#: boot-installer.xml:1683 #, no-c-format msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system." msgstr "" #. Tag: title -#: boot-installer.xml:1589 +#: boot-installer.xml:1694 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1590 +#: boot-installer.xml:1695 #, no-c-format msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. It needs to be fixed-width with 80 characters per line. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images. If a parameter is too long to fit into the 80 characters limit it can simply be continued in the first column of the next line. All the lines are concatenated without spaces when being passed to the kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1607 +#: boot-installer.xml:1712 #, no-c-format msgid "" "If you boot the installer in a logical partition (LPAR) or virtual machine (VM) where a lot of devices are visible, you can instruct the kernel to restrict the list to a fixed set of devices. This is advised for the installer's boot process if a lot of disks are visible, most likely in LPAR mode. The <quote>cio_ignore</quote> option supports both a blacklist (to only disallow a few devices) and a whitelist (to only allow specific devices): <informalexample role=\"example\"><screen>\n" @@ -1116,13 +1182,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1671 +#: boot-installer.xml:1776 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1680 +#: boot-installer.xml:1785 #, no-c-format msgid "" "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n" @@ -1131,79 +1197,79 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1691 +#: boot-installer.xml:1796 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: para -#: boot-installer.xml:1693 +#: boot-installer.xml:1798 #, no-c-format msgid "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files." msgstr "" #. Tag: para -#: boot-installer.xml:1702 +#: boot-installer.xml:1807 #, no-c-format msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type" msgstr "" #. Tag: screen -#: boot-installer.xml:1708 +#: boot-installer.xml:1813 #, no-c-format msgid "boot cd install/pegasos" msgstr "" #. Tag: para -#: boot-installer.xml:1710 +#: boot-installer.xml:1815 #, no-c-format msgid "On YDL Powerstation machine, pres <keycap>s</keycap> immediately after <quote>Press 's' to enter Open Firmware</quote> message, when SLOF prompt appears type" msgstr "" #. Tag: screen -#: boot-installer.xml:1715 +#: boot-installer.xml:1820 #, no-c-format msgid "0 > boot cdrom" msgstr "" #. Tag: title -#: boot-installer.xml:1721 +#: boot-installer.xml:1826 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1727 +#: boot-installer.xml:1832 #, no-c-format msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." msgstr "" #. Tag: para -#: boot-installer.xml:1733 +#: boot-installer.xml:1838 #, no-c-format msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1753 +#: boot-installer.xml:1858 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1754 +#: boot-installer.xml:1859 #, no-c-format msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer." msgstr "" #. Tag: title -#: boot-installer.xml:1772 +#: boot-installer.xml:1877 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:1773 +#: boot-installer.xml:1878 #, no-c-format msgid "" "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n" @@ -1214,31 +1280,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1805 +#: boot-installer.xml:1910 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:1806 +#: boot-installer.xml:1911 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:1812 +#: boot-installer.xml:1917 #, no-c-format msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1821 +#: boot-installer.xml:1926 #, no-c-format msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work." msgstr "" #. Tag: para -#: boot-installer.xml:1833 +#: boot-installer.xml:1938 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1247,25 +1313,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1847 +#: boot-installer.xml:1952 #, no-c-format msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: para -#: boot-installer.xml:1853 +#: boot-installer.xml:1958 #, no-c-format msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1887 +#: boot-installer.xml:1992 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:1891 +#: boot-installer.xml:1996 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n" @@ -1278,781 +1344,781 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1919 +#: boot-installer.xml:2024 #, no-c-format msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting." msgstr "" #. Tag: para -#: boot-installer.xml:1931 +#: boot-installer.xml:2036 #, no-c-format msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button." msgstr "" #. Tag: para -#: boot-installer.xml:1937 +#: boot-installer.xml:2042 #, no-c-format msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions." msgstr "" #. Tag: para -#: boot-installer.xml:1944 +#: boot-installer.xml:2049 #, no-c-format msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory." msgstr "" #. Tag: title -#: boot-installer.xml:1955 +#: boot-installer.xml:2060 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1956 +#: boot-installer.xml:2061 #, no-c-format msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ." msgstr "" #. Tag: title -#: boot-installer.xml:1968 +#: boot-installer.xml:2073 #, no-c-format msgid "Booting a ppc64el machine" msgstr "" #. Tag: para -#: boot-installer.xml:1969 +#: boot-installer.xml:2074 #, no-c-format msgid "How to boot a ppc64el machine:" msgstr "" #. Tag: title -#: boot-installer.xml:1975 +#: boot-installer.xml:2080 #, no-c-format msgid "Petitboot" msgstr "" #. Tag: para -#: boot-installer.xml:1976 +#: boot-installer.xml:2081 #, no-c-format msgid "Petitboot is a platform independent bootloader based on the Linux kexec. Petitboot supports loading kernel, initrd and device tree files from any Linux mountable filesystem, plus can load files from the network using the FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can boot any operating system that includes kexec boot support." msgstr "" #. Tag: para -#: boot-installer.xml:1984 +#: boot-installer.xml:2089 #, no-c-format msgid "Petitboot looks for bootloader configuration files on mountable devices in the system, and can also be configured to use boot information from a DHCP server." msgstr "" #. Tag: para -#: boot-installer.xml:2035 +#: boot-installer.xml:2140 #, no-c-format msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command." msgstr "" #. Tag: para -#: boot-installer.xml:2089 +#: boot-installer.xml:2194 #, no-c-format msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)." msgstr "" #. Tag: title -#: boot-installer.xml:2098 +#: boot-installer.xml:2203 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:2099 +#: boot-installer.xml:2204 #, no-c-format msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information." msgstr "" #. Tag: title -#: boot-installer.xml:2118 +#: boot-installer.xml:2223 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:2119 +#: boot-installer.xml:2224 #, no-c-format msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;ppc64el;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." msgstr "" #. Tag: title -#: boot-installer.xml:2139 +#: boot-installer.xml:2244 #, no-c-format msgid "Installer front-end" msgstr "" #. Tag: para -#: boot-installer.xml:2140 +#: boot-installer.xml:2245 #, no-c-format msgid "The &debian; installer supports several front-ends for asking questions, with varying convenience for accessibility: notably, <userinput>text</userinput> uses plain text while <userinput>newt</userinput> uses text-based dialog boxes. The choice can be made at the boot prompt, see the documentation for <userinput>DEBIAN_FRONTEND</userinput> in <xref linkend=\"installer-args\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2152 +#: boot-installer.xml:2257 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2153 +#: boot-installer.xml:2258 #, no-c-format msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:2168 +#: boot-installer.xml:2273 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2169 +#: boot-installer.xml:2274 #, no-c-format msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:2192 boot-installer.xml:3201 +#: boot-installer.xml:2297 boot-installer.xml:3306 #, no-c-format msgid "Software Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:2193 +#: boot-installer.xml:2298 #, no-c-format msgid "Support for software speech synthesis is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. It can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The textual version of the installer will then be automatically selected, and support for software speech synthesis will be automatically installed on the target system." msgstr "" #. Tag: para -#: boot-installer.xml:2202 +#: boot-installer.xml:2307 #, no-c-format msgid "The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)." msgstr "" #. Tag: para -#: boot-installer.xml:2208 +#: boot-installer.xml:2313 #, no-c-format msgid "The default speech rate is quite slow. To make it faster, press <keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. To make it slower, press <keycombo><keycap>CapsLock</keycap><keycap>5</keycap></keycombo>. The default volume should be medium. To make it louder, press <keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. To make it quieter, press <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></keycombo>. To get more details on the browsing shortcuts, see the <ulink url=\"&url-speakup-guide;\">Speakup guide</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:2227 +#: boot-installer.xml:2332 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:2228 +#: boot-installer.xml:2333 #, no-c-format msgid "Support for hardware speech synthesis devices is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. You thus need to select a <quote>Graphical install</quote> entry in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:2235 +#: boot-installer.xml:2340 #, no-c-format msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-guide;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system." msgstr "" #. Tag: title -#: boot-installer.xml:2250 +#: boot-installer.xml:2355 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:2251 +#: boot-installer.xml:2356 #, no-c-format msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages." msgstr "" #. Tag: para -#: boot-installer.xml:2259 +#: boot-installer.xml:2364 #, no-c-format msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;." msgstr "" #. Tag: title -#: boot-installer.xml:2267 +#: boot-installer.xml:2372 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:2268 +#: boot-installer.xml:2373 #, no-c-format msgid "For users with low vision, the installer can use a high-contrast color theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter." msgstr "" #. Tag: title -#: boot-installer.xml:2277 +#: boot-installer.xml:2382 #, no-c-format msgid "Preseeding" msgstr "" #. Tag: para -#: boot-installer.xml:2278 +#: boot-installer.xml:2383 #, no-c-format msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2286 +#: boot-installer.xml:2391 #, no-c-format msgid "Accessibility of the installed system" msgstr "" #. Tag: para -#: boot-installer.xml:2287 +#: boot-installer.xml:2392 #, no-c-format msgid "Documentation on accessibility of the installed system is available on the <ulink url=\"&url-debian-wiki-accessibility;\">Debian Accessibility wiki page</ulink>." msgstr "" #. Tag: para -#: boot-installer.xml:2302 +#: boot-installer.xml:2407 #, no-c-format msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit." msgstr "" #. Tag: para -#: boot-installer.xml:2309 +#: boot-installer.xml:2414 #, no-c-format msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware." msgstr "" #. Tag: para -#: boot-installer.xml:2316 +#: boot-installer.xml:2421 #, no-c-format msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2328 +#: boot-installer.xml:2433 #, no-c-format msgid "Boot console" msgstr "" #. Tag: para -#: boot-installer.xml:2330 +#: boot-installer.xml:2435 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:2342 +#: boot-installer.xml:2447 #, no-c-format msgid "You may need to specify parameters for the serial port, such as speed and parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other typical speeds may be 57600 or 115200. Be sure to specify this option after <quote>---</quote>, so that it is copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader)." msgstr "" #. Tag: para -#: boot-installer.xml:2350 +#: boot-installer.xml:2455 #, no-c-format msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>." msgstr "" #. Tag: para -#: boot-installer.xml:2366 +#: boot-installer.xml:2471 #, no-c-format msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:2378 +#: boot-installer.xml:2483 #, no-c-format msgid "&debian; Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2379 +#: boot-installer.xml:2484 #, no-c-format msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful." msgstr "" #. Tag: para -#: boot-installer.xml:2392 +#: boot-installer.xml:2497 #, no-c-format msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too." msgstr "" #. Tag: term -#: boot-installer.xml:2404 +#: boot-installer.xml:2509 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2405 +#: boot-installer.xml:2510 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2409 +#: boot-installer.xml:2514 #, no-c-format msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed." msgstr "" #. Tag: para -#: boot-installer.xml:2416 +#: boot-installer.xml:2521 #, no-c-format msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." msgstr "" #. Tag: term -#: boot-installer.xml:2430 +#: boot-installer.xml:2535 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2431 +#: boot-installer.xml:2536 #, no-c-format msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2462 +#: boot-installer.xml:2567 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2463 +#: boot-installer.xml:2568 #, no-c-format msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" msgstr "" #. Tag: userinput -#: boot-installer.xml:2472 +#: boot-installer.xml:2577 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2473 +#: boot-installer.xml:2578 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2477 +#: boot-installer.xml:2582 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2478 +#: boot-installer.xml:2583 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2482 +#: boot-installer.xml:2587 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2483 +#: boot-installer.xml:2588 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2487 +#: boot-installer.xml:2592 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2488 +#: boot-installer.xml:2593 #, no-c-format msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term -#: boot-installer.xml:2502 +#: boot-installer.xml:2607 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2503 +#: boot-installer.xml:2608 #, no-c-format msgid "The value of the parameter is the path to the device to load the &debian; installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>" msgstr "" #. Tag: para -#: boot-installer.xml:2509 +#: boot-installer.xml:2614 #, no-c-format msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term -#: boot-installer.xml:2520 +#: boot-installer.xml:2625 #, no-c-format msgid "log_host" msgstr "" #. Tag: term -#: boot-installer.xml:2521 +#: boot-installer.xml:2626 #, no-c-format msgid "log_port" msgstr "" #. Tag: para -#: boot-installer.xml:2522 +#: boot-installer.xml:2627 #, no-c-format msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514." msgstr "" #. Tag: term -#: boot-installer.xml:2533 +#: boot-installer.xml:2638 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2534 +#: boot-installer.xml:2639 #, no-c-format msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2544 +#: boot-installer.xml:2649 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:2545 +#: boot-installer.xml:2650 #, no-c-format msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited." msgstr "" #. Tag: term -#: boot-installer.xml:2554 +#: boot-installer.xml:2659 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2555 +#: boot-installer.xml:2660 #, no-c-format msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." msgstr "" #. Tag: para -#: boot-installer.xml:2564 +#: boot-installer.xml:2669 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2568 +#: boot-installer.xml:2673 #, no-c-format msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." msgstr "" #. Tag: term -#: boot-installer.xml:2582 +#: boot-installer.xml:2687 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2583 +#: boot-installer.xml:2688 #, no-c-format msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2595 boot-installer.xml:2828 +#: boot-installer.xml:2700 boot-installer.xml:2933 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "" #. Tag: para -#: boot-installer.xml:2596 +#: boot-installer.xml:2701 #, no-c-format msgid "By default, the &d-i; automatically probes for network configuration via IPv6 autoconfiguration and DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the automatic configuration fails." msgstr "" #. Tag: para -#: boot-installer.xml:2603 +#: boot-installer.xml:2708 #, no-c-format msgid "If you have an IPv6 router or a DHCP server on your local network, but want to avoid them because e.g. they give wrong answers, you can use the parameter <userinput>netcfg/disable_autoconfig=true</userinput> to prevent any automatic configuration of the network (neither v4 nor v6) and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:2614 +#: boot-installer.xml:2719 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:2615 +#: boot-installer.xml:2720 #, no-c-format msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" #. Tag: term -#: boot-installer.xml:2625 +#: boot-installer.xml:2730 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:2626 +#: boot-installer.xml:2731 #, no-c-format msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>." msgstr "" #. Tag: term -#: boot-installer.xml:2637 +#: boot-installer.xml:2742 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:2638 +#: boot-installer.xml:2743 #, no-c-format msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2647 +#: boot-installer.xml:2752 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:2648 +#: boot-installer.xml:2753 #, no-c-format msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2657 +#: boot-installer.xml:2762 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:2658 +#: boot-installer.xml:2763 #, no-c-format msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details." msgstr "" #. Tag: term -#: boot-installer.xml:2670 +#: boot-installer.xml:2775 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:2671 +#: boot-installer.xml:2776 #, no-c-format msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs." msgstr "" #. Tag: term -#: boot-installer.xml:2682 +#: boot-installer.xml:2787 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:2683 +#: boot-installer.xml:2788 #, no-c-format msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this." msgstr "" #. Tag: term -#: boot-installer.xml:2694 +#: boot-installer.xml:2799 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:2695 +#: boot-installer.xml:2800 #, no-c-format msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically." msgstr "" #. Tag: para -#: boot-installer.xml:2704 +#: boot-installer.xml:2809 #, no-c-format msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." msgstr "" #. Tag: term -#: boot-installer.xml:2715 +#: boot-installer.xml:2820 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "" #. Tag: para -#: boot-installer.xml:2716 +#: boot-installer.xml:2821 #, no-c-format msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2723 +#: boot-installer.xml:2828 #, no-c-format msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users." msgstr "" #. Tag: term -#: boot-installer.xml:2735 +#: boot-installer.xml:2840 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:2736 +#: boot-installer.xml:2841 #, no-c-format msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>" msgstr "" #. Tag: term -#: boot-installer.xml:2747 +#: boot-installer.xml:2852 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:2748 +#: boot-installer.xml:2853 #, no-c-format msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB." msgstr "" #. Tag: term -#: boot-installer.xml:2758 +#: boot-installer.xml:2863 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:2759 +#: boot-installer.xml:2864 #, no-c-format msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2772 +#: boot-installer.xml:2877 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:2773 +#: boot-installer.xml:2878 #, no-c-format msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below." msgstr "" #. Tag: term -#: boot-installer.xml:2785 +#: boot-installer.xml:2890 #, no-c-format msgid "debian-installer/language (language)" msgstr "" #. Tag: term -#: boot-installer.xml:2786 +#: boot-installer.xml:2891 #, no-c-format msgid "debian-installer/country (country)" msgstr "" #. Tag: term -#: boot-installer.xml:2787 +#: boot-installer.xml:2892 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2788 +#: boot-installer.xml:2893 #, no-c-format msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2793 +#: boot-installer.xml:2898 #, no-c-format msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way." msgstr "" #. Tag: para -#: boot-installer.xml:2802 +#: boot-installer.xml:2907 #, no-c-format msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2814 +#: boot-installer.xml:2919 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2815 +#: boot-installer.xml:2920 #, no-c-format msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." msgstr "" #. Tag: para -#: boot-installer.xml:2829 +#: boot-installer.xml:2934 #, no-c-format msgid "Set to <userinput>true</userinput> if you want to disable IPv6 autoconfiguration and DHCP and instead force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:2838 +#: boot-installer.xml:2943 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2839 +#: boot-installer.xml:2944 #, no-c-format msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." msgstr "" #. Tag: term -#: boot-installer.xml:2852 +#: boot-installer.xml:2957 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2853 +#: boot-installer.xml:2958 #, no-c-format msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information." msgstr "" #. Tag: title -#: boot-installer.xml:2867 +#: boot-installer.xml:2972 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2868 +#: boot-installer.xml:2973 #, no-c-format msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2881 +#: boot-installer.xml:2986 #, no-c-format msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." msgstr "" #. Tag: para -#: boot-installer.xml:2888 +#: boot-installer.xml:2993 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2061,127 +2127,127 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2898 +#: boot-installer.xml:3003 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:2904 +#: boot-installer.xml:3009 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2905 +#: boot-installer.xml:3010 #, no-c-format msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first." msgstr "" #. Tag: para -#: boot-installer.xml:2914 +#: boot-installer.xml:3019 #, no-c-format msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2922 +#: boot-installer.xml:3027 #, no-c-format msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases." msgstr "" #. Tag: title -#: boot-installer.xml:2938 +#: boot-installer.xml:3043 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:2943 +#: boot-installer.xml:3048 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2944 +#: boot-installer.xml:3049 #, no-c-format msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." msgstr "" #. Tag: para -#: boot-installer.xml:2951 +#: boot-installer.xml:3056 #, no-c-format msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." msgstr "" #. Tag: para -#: boot-installer.xml:2957 +#: boot-installer.xml:3062 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:2962 +#: boot-installer.xml:3067 #, no-c-format msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." msgstr "" #. Tag: para -#: boot-installer.xml:2968 +#: boot-installer.xml:3073 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:2978 +#: boot-installer.xml:3083 #, no-c-format msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." msgstr "" #. Tag: para -#: boot-installer.xml:2984 +#: boot-installer.xml:3089 #, no-c-format msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." msgstr "" #. Tag: title -#: boot-installer.xml:2992 +#: boot-installer.xml:3097 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:2995 +#: boot-installer.xml:3100 #, no-c-format msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." msgstr "" #. Tag: para -#: boot-installer.xml:3012 +#: boot-installer.xml:3117 #, no-c-format msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them." msgstr "" #. Tag: title -#: boot-installer.xml:3023 +#: boot-installer.xml:3128 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3024 +#: boot-installer.xml:3129 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3029 +#: boot-installer.xml:3134 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS." msgstr "" #. Tag: para -#: boot-installer.xml:3036 +#: boot-installer.xml:3141 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n" @@ -2191,7 +2257,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3049 +#: boot-installer.xml:3154 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2204,19 +2270,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3054 +#: boot-installer.xml:3159 #, no-c-format msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." msgstr "" #. Tag: para -#: boot-installer.xml:3066 +#: boot-installer.xml:3171 #, no-c-format msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3073 +#: boot-installer.xml:3178 #, no-c-format msgid "" "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n" @@ -2229,13 +2295,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3087 +#: boot-installer.xml:3192 #, no-c-format msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:3095 +#: boot-installer.xml:3200 #, no-c-format msgid "" "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n" @@ -2244,7 +2310,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3105 +#: boot-installer.xml:3210 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2257,151 +2323,151 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3120 +#: boot-installer.xml:3225 #, no-c-format msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." msgstr "" #. Tag: title -#: boot-installer.xml:3135 +#: boot-installer.xml:3240 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3137 +#: boot-installer.xml:3242 #, no-c-format msgid "The biggest problem for people using floppy disks to install &debian; seems to be floppy disk reliability." msgstr "" #. Tag: para -#: boot-installer.xml:3142 +#: boot-installer.xml:3247 #, no-c-format msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors." msgstr "" #. Tag: para -#: boot-installer.xml:3151 +#: boot-installer.xml:3256 #, no-c-format msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para -#: boot-installer.xml:3160 +#: boot-installer.xml:3265 #, no-c-format msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." msgstr "" #. Tag: para -#: boot-installer.xml:3166 +#: boot-installer.xml:3271 #, no-c-format msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." msgstr "" #. Tag: para -#: boot-installer.xml:3172 +#: boot-installer.xml:3277 #, no-c-format msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." msgstr "" #. Tag: title -#: boot-installer.xml:3181 +#: boot-installer.xml:3286 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3183 +#: boot-installer.xml:3288 #, no-c-format msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:3192 +#: boot-installer.xml:3297 #, no-c-format msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)." msgstr "" #. Tag: para -#: boot-installer.xml:3203 +#: boot-installer.xml:3308 #, no-c-format msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)." msgstr "" #. Tag: userinput -#: boot-installer.xml:3214 +#: boot-installer.xml:3319 #, no-c-format msgid "dmesg" msgstr "" #. Tag: userinput -#: boot-installer.xml:3216 +#: boot-installer.xml:3321 #, no-c-format msgid "lspci" msgstr "" #. Tag: userinput -#: boot-installer.xml:3218 +#: boot-installer.xml:3323 #, no-c-format msgid "lsmod" msgstr "" #. Tag: userinput -#: boot-installer.xml:3220 +#: boot-installer.xml:3325 #, no-c-format msgid "amixer" msgstr "" #. Tag: title -#: boot-installer.xml:3228 boot-installer.xml:3339 +#: boot-installer.xml:3333 boot-installer.xml:3444 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3229 +#: boot-installer.xml:3334 #, no-c-format msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" #. Tag: para -#: boot-installer.xml:3280 +#: boot-installer.xml:3385 #, no-c-format msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:3294 +#: boot-installer.xml:3399 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3295 +#: boot-installer.xml:3400 #, no-c-format msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:3305 +#: boot-installer.xml:3410 #, no-c-format msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: para -#: boot-installer.xml:3340 +#: boot-installer.xml:3445 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3346 +#: boot-installer.xml:3451 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3347 +#: boot-installer.xml:3452 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n" @@ -2411,85 +2477,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3361 +#: boot-installer.xml:3466 #, no-c-format msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:3372 +#: boot-installer.xml:3477 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3373 +#: boot-installer.xml:3478 #, no-c-format msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems." msgstr "" #. Tag: para -#: boot-installer.xml:3379 +#: boot-installer.xml:3484 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3388 +#: boot-installer.xml:3493 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3390 +#: boot-installer.xml:3495 #, no-c-format msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>." msgstr "" #. Tag: title -#: boot-installer.xml:3415 +#: boot-installer.xml:3520 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3416 +#: boot-installer.xml:3521 #, no-c-format msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3427 +#: boot-installer.xml:3532 #, no-c-format msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title -#: boot-installer.xml:3438 +#: boot-installer.xml:3543 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3439 +#: boot-installer.xml:3544 #, no-c-format msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." msgstr "" #. Tag: para -#: boot-installer.xml:3446 +#: boot-installer.xml:3551 #, no-c-format msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public." msgstr "" #. Tag: para -#: boot-installer.xml:3452 +#: boot-installer.xml:3557 #, no-c-format msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3462 +#: boot-installer.xml:3567 #, no-c-format msgid "" "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 342231f03..08bbce5e0 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2015-04-15 20:29+0000\n" +"POT-Creation-Date: 2015-05-04 18:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -405,102 +405,132 @@ msgid "Both AMD64 and Intel 64 processors are supported." msgstr "" #. Tag: title -#: hardware.xml:268 hardware.xml:723 hardware.xml:780 hardware.xml:838 hardware.xml:868 hardware.xml:1311 +#: hardware.xml:267 #, no-c-format -msgid "CPU, Main Boards, and Video Support" +msgid "Three different ARM ports" +msgstr "" + +#. Tag: para +#: hardware.xml:269 +#, 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:270 +#: hardware.xml:275 #, no-c-format -msgid "ARM systems are much more heterogeneous than the i386/amd64-based PC architecture, so whilst 64-bit ARM machines should boot in a standardised way, like PCs, the situation is more complicated for 32-bit ARM machines." +msgid "&debian;/armel targets older 32-bit ARM processors without support for a hardware floating point unit (FPU)," msgstr "" #. Tag: para #: hardware.xml:279 #, no-c-format -msgid "The ARM architecture is used mainly in so-called <quote>systems-on-chip</quote> (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. 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 are handled by the mainboard's BIOS in the PC world." +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:292 +#: hardware.xml:286 #, 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 <quote>one-fits-all</quote> 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 gets 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." +msgid "&debian;/arm64 works on 64-bit ARM processors which implement at least the ARMv8 architecture." msgstr "" #. Tag: para -#: hardware.xml:304 +#: hardware.xml:293 #, no-c-format -msgid "Because of this, the standard &debian; distribution only supports installation on a selected number of older 32-bit ARM systems in addition to the newer (32 and 64-bit) systems which are supported by the ARM multiplatform kernels (called 'armmp' on 32-bit armhf, no flavour name on 64-bit arm64)." +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:302 +#, no-c-format +msgid "Variations in ARM CPU designs and support complexity" msgstr "" #. Tag: para -#: hardware.xml:313 +#: hardware.xml:304 #, 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: the &debian;/arm64 port for all 64-bit machines, and the &debian;/armel and the &debian;/armhf ports for 32-bit machines. &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. &debian;/arm64 works on processors which implement at least the ARMv8 architecture (which is 64bit)." +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:350 +#: hardware.xml:310 #, 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." +msgid "The ARM architecture is used mainly in so-called <quote>system-on-chip</quote> (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 in the PC world." msgstr "" -#. Tag: title -#: hardware.xml:357 +#. Tag: para +#: hardware.xml:322 #, no-c-format -msgid "Platforms supported by Debian/arm64" +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 <quote>one-fits-all</quote> 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:359 +#: 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 have had support merged in the mainline kernel version in this release, which is the main requirement to have &d-i; working on them." +msgid "The ARM architecture is used mainly in so-called <quote>system-on-chip</quote> (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:368 +#: hardware.xml:349 +#, 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:359 #, no-c-format -msgid "The tested platforms are listed below, but in general, the multiplatform support in the arm64 Linux kernel also allows running &d-i; on arm64 systems not explicitly listed below, so 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, and so long as UEFI is in use, it should be able to make the system bootable as well. If UEFI is not used (some 64-bit machines have been shipped with U-Boot) you will probably also need some manual steps to make the system bootable." +msgid "Platforms supported by Debian/arm64" msgstr "" #. Tag: para -#: hardware.xml:382 +#: hardware.xml:361 #, no-c-format -msgid "The following platforms are known to be supported by &debian;/arm64 in this release. There is only one kernel, which supports all the listed platforms." +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:389 +#: hardware.xml:373 #, no-c-format msgid "Applied Micro (APM) Mustang/X-Gene" msgstr "" #. Tag: para -#: hardware.xml:391 +#: hardware.xml:375 #, no-c-format -msgid "The APM Mustang was the first Linux-capable ARMv8 system available. It uses the X-gene SoC, since also used in other machines, which is an 8-core CPU, with ethernet, USB, serial. A common form-factor looks just like a desktop PC box, but many versions are expected. Most of the hardware is supported in the mainline kernel, but USB support is lacking in the &releasename-cap; kernel." +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:404 +#: hardware.xml:389 #, no-c-format msgid "ARM Juno Development Platform" msgstr "" #. Tag: para -#: hardware.xml:406 +#: hardware.xml:391 #, 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 hardware is supported in the mainline kernel and in &releasename-cap;." +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:420 +#: hardware.xml:405 #, 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:413 +#, no-c-format +msgid "Other platforms" +msgstr "" + +#. Tag: para +#: hardware.xml:414 +#, 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:430 #, no-c-format msgid "Platforms supported by Debian/armhf" @@ -593,7 +623,7 @@ msgstr "" #. Tag: para #: hardware.xml:496 #, 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." +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 @@ -617,7 +647,7 @@ msgstr "" #. Tag: para #: hardware.xml:524 #, 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." +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 @@ -629,43 +659,37 @@ msgstr "" #. Tag: para #: hardware.xml:541 #, no-c-format -msgid "The Wandboard Quad is a development board based on the Freescale i.MX6 Quad SoC. System support for it 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 and SATA. Support for the onboard audio options (analog, S/PDIF, HDMI-Audio) and for the onboard WLAN/Bluetooth module is not available in &debian; 8." +msgid "The Wandboard Quad is a development board based on the Freescale i.MX6 Quad SoC. System support for it 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 and SATA. Support for the onboard audio options (analog, S/PDIF, HDMI-Audio) and for the onboard WLAN/Bluetooth module is not available in &debian; 8." msgstr "" #. Tag: para #: hardware.xml:559 #, 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." +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:570 +#: hardware.xml:571 #, 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:579 +#: hardware.xml:580 #, no-c-format msgid "Platforms no longer supported by Debian/armhf" msgstr "" #. Tag: term -#: hardware.xml:583 -#, no-c-format -msgid "EfikaMX" -msgstr "" - -#. Tag: para #: hardware.xml:584 #, 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 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." +msgid "EfikaMX" msgstr "" #. Tag: para -#: hardware.xml:591 +#: hardware.xml:585 #, 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." +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 @@ -689,1397 +713,1415 @@ msgstr "" #. Tag: para #: hardware.xml:614 #, no-c-format -msgid "The Intel IXP4xx processor series is used in network attached storage devices like the Linksys NSLU2." +msgid "The Intel IXP4xx processor series is used in commonly used network attached storage (NAS) devices like the Linksys NSLU2." msgstr "" #. Tag: para #: hardware.xml:619 #, no-c-format -msgid "While there is kernel support for this platform in &debian; 8, it is not supported by the &d-i;. It is possible to do a <quote>dist-upgrade</quote> from Debian 7 to Debian 8 for existing installations, though. Due to the low amount of RAM that systems based on the IXP4xx usually have, this requires that swap space is enabled prior to upgrading. Support for the IXP4xx platform will be dropped completely in &debian; 9." +msgid "While there is kernel support for this platform in &debian; 8, it is not supported by the &d-i;. It is possible to do a <quote>dist-upgrade</quote> from &debian; 7 to &debian; 8 for existing installations, though. Due to the small amount of RAM that systems based on the IXP4xx typically have, this requires that swap space is enabled prior to upgrading. Support for the IXP4xx platform will be dropped completely in &debian; 9." msgstr "" #. Tag: term -#: hardware.xml:632 +#: hardware.xml:633 #, no-c-format msgid "Kirkwood" msgstr "" #. Tag: para -#: hardware.xml:633 +#: hardware.xml:634 #, no-c-format -msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)." +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: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)." msgstr "" #. Tag: term -#: hardware.xml:649 +#: hardware.xml:651 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para -#: hardware.xml:650 +#: hardware.xml:652 #, no-c-format -msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>." +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: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>." msgstr "" #. Tag: term -#: hardware.xml:664 +#: hardware.xml:667 #, no-c-format msgid "<term>Versatile</term>" msgstr "" #. Tag: para -#: hardware.xml:665 +#: hardware.xml:668 #, 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." +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:678 +#: hardware.xml:681 #, no-c-format msgid "Platforms no longer supported by Debian/armel" msgstr "" #. Tag: term -#: hardware.xml:682 +#: hardware.xml:685 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:683 +#: hardware.xml:686 #, 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 <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>. &debian; has supported the IOP32x platform in &debian; 7, but does not support it any longer 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:698 +#: hardware.xml:701 #, no-c-format msgid "MV78xx0" msgstr "" #. Tag: para -#: hardware.xml:699 +#: hardware.xml:702 #, 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 any more from Debian 8 onwards." +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 any more from &debian; 8 onwards." +msgstr "" + +#. Tag: title +#: hardware.xml:721 hardware.xml:778 hardware.xml:836 hardware.xml:866 hardware.xml:1309 +#, no-c-format +msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:724 +#: hardware.xml:722 #, no-c-format msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." msgstr "" #. Tag: title -#: hardware.xml:732 hardware.xml:815 +#: hardware.xml:730 hardware.xml:813 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:733 +#: hardware.xml:731 #, 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:740 +#: hardware.xml:738 #, no-c-format msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 486 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 and 80486 processors (and their clones) was dropped with the Sarge (r3.1) and Squeeze (r6.0) releases of &debian;, respectively. The Intel Pentium and clones, including those without an FPU (Floating-Point Unit or math coprocessor), are supported. The Intel Quark is <emphasis>not</emphasis> supported, due to hardware errata." msgstr "" #. Tag: para -#: hardware.xml:752 +#: hardware.xml:750 #, 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:761 +#: hardware.xml:759 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:762 +#: hardware.xml:760 #, 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:781 +#: hardware.xml:779 #, no-c-format msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para -#: hardware.xml:816 +#: hardware.xml:814 #, 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:822 +#: hardware.xml:820 #, 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:839 +#: hardware.xml:837 #, no-c-format msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para -#: hardware.xml:869 +#: hardware.xml:867 #, 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:890 +#: hardware.xml:888 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:892 +#: hardware.xml:890 #, no-c-format msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:899 +#: hardware.xml:897 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:900 +#: hardware.xml:898 #, 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:910 +#: hardware.xml:908 #, no-c-format msgid "powerpc-smp" msgstr "" #. Tag: para -#: hardware.xml:911 +#: hardware.xml:909 #, no-c-format msgid "All Apple PowerMac G4 SMP machines." msgstr "" #. Tag: term -#: hardware.xml:919 +#: hardware.xml:917 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:920 +#: hardware.xml:918 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:924 +#: hardware.xml:922 #, 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:930 +#: hardware.xml:928 #, 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:935 +#: hardware.xml:933 #, 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:941 +#: hardware.xml:939 #, no-c-format msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors." msgstr "" #. Tag: title -#: hardware.xml:974 +#: hardware.xml:972 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:976 +#: hardware.xml:974 #, 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:983 +#: hardware.xml:981 #, 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:991 +#: hardware.xml:989 #, no-c-format msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para -#: hardware.xml:999 +#: hardware.xml:997 #, no-c-format msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>." msgstr "" #. Tag: entry -#: hardware.xml:1015 hardware.xml:1150 hardware.xml:1194 hardware.xml:1227 +#: hardware.xml:1013 hardware.xml:1148 hardware.xml:1192 hardware.xml:1225 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1016 +#: hardware.xml:1014 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1022 +#: hardware.xml:1020 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1023 +#: hardware.xml:1021 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1024 hardware.xml:1027 hardware.xml:1030 hardware.xml:1033 hardware.xml:1036 hardware.xml:1039 hardware.xml:1042 hardware.xml:1045 hardware.xml:1048 hardware.xml:1051 hardware.xml:1054 hardware.xml:1057 hardware.xml:1060 hardware.xml:1063 hardware.xml:1066 hardware.xml:1069 +#: hardware.xml:1022 hardware.xml:1025 hardware.xml:1028 hardware.xml:1031 hardware.xml:1034 hardware.xml:1037 hardware.xml:1040 hardware.xml:1043 hardware.xml:1046 hardware.xml:1049 hardware.xml:1052 hardware.xml:1055 hardware.xml:1058 hardware.xml:1061 hardware.xml:1064 hardware.xml:1067 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1026 +#: hardware.xml:1024 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1029 +#: hardware.xml:1027 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1032 +#: hardware.xml:1030 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1035 +#: hardware.xml:1033 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1038 +#: hardware.xml:1036 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1041 +#: hardware.xml:1039 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1044 +#: hardware.xml:1042 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1047 +#: hardware.xml:1045 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1050 +#: hardware.xml:1048 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1053 +#: hardware.xml:1051 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1056 +#: hardware.xml:1054 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1059 +#: hardware.xml:1057 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1062 +#: hardware.xml:1060 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1065 +#: hardware.xml:1063 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1068 +#: hardware.xml:1066 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1071 +#: hardware.xml:1069 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1072 hardware.xml:1075 hardware.xml:1078 hardware.xml:1081 hardware.xml:1084 hardware.xml:1087 hardware.xml:1090 hardware.xml:1093 hardware.xml:1096 hardware.xml:1099 hardware.xml:1102 hardware.xml:1105 hardware.xml:1111 hardware.xml:1114 hardware.xml:1120 hardware.xml:1126 hardware.xml:1132 +#: hardware.xml:1070 hardware.xml:1073 hardware.xml:1076 hardware.xml:1079 hardware.xml:1082 hardware.xml:1085 hardware.xml:1088 hardware.xml:1091 hardware.xml:1094 hardware.xml:1097 hardware.xml:1100 hardware.xml:1103 hardware.xml:1109 hardware.xml:1112 hardware.xml:1118 hardware.xml:1124 hardware.xml:1130 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1074 +#: hardware.xml:1072 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1077 +#: hardware.xml:1075 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1080 +#: hardware.xml:1078 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1083 +#: hardware.xml:1081 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1086 +#: hardware.xml:1084 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1089 +#: hardware.xml:1087 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1092 +#: hardware.xml:1090 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1095 +#: hardware.xml:1093 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1098 +#: hardware.xml:1096 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1101 +#: hardware.xml:1099 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1104 +#: hardware.xml:1102 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1109 +#: hardware.xml:1107 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1110 +#: hardware.xml:1108 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1113 +#: hardware.xml:1111 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1118 +#: hardware.xml:1116 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1119 +#: hardware.xml:1117 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1124 +#: hardware.xml:1122 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1125 +#: hardware.xml:1123 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1130 hardware.xml:1156 +#: hardware.xml:1128 hardware.xml:1154 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1131 +#: hardware.xml:1129 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1140 +#: hardware.xml:1138 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1157 +#: hardware.xml:1155 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1159 +#: hardware.xml:1157 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1161 +#: hardware.xml:1159 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1163 +#: hardware.xml:1161 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1165 +#: hardware.xml:1163 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1169 hardware.xml:1200 +#: hardware.xml:1167 hardware.xml:1198 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1170 +#: hardware.xml:1168 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1172 +#: hardware.xml:1170 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1174 +#: hardware.xml:1172 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1176 +#: hardware.xml:1174 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1184 +#: hardware.xml:1182 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1201 +#: hardware.xml:1199 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1204 +#: hardware.xml:1202 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1205 +#: hardware.xml:1203 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: entry -#: hardware.xml:1208 +#: hardware.xml:1206 #, no-c-format msgid "Fixstars" msgstr "" #. Tag: entry -#: hardware.xml:1209 +#: hardware.xml:1207 #, no-c-format msgid "YDL PowerStation" msgstr "" #. Tag: title -#: hardware.xml:1217 +#: hardware.xml:1215 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:1233 +#: hardware.xml:1231 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1234 +#: hardware.xml:1232 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1242 +#: hardware.xml:1240 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1244 +#: hardware.xml:1242 #, no-c-format msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." msgstr "" #. Tag: title -#: hardware.xml:1281 +#: hardware.xml:1279 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1283 +#: hardware.xml:1281 #, no-c-format msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para -#: hardware.xml:1292 +#: hardware.xml:1290 #, 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:1300 +#: hardware.xml:1298 #, 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:1314 +#: hardware.xml:1312 #, no-c-format msgid "Machines" msgstr "" #. Tag: para -#: hardware.xml:1317 +#: hardware.xml:1315 #, no-c-format msgid "S822L" msgstr "" #. Tag: para -#: hardware.xml:1322 +#: hardware.xml:1320 #, no-c-format msgid "S821L" msgstr "" #. Tag: para -#: hardware.xml:1327 +#: hardware.xml:1325 #, no-c-format msgid "S822" msgstr "" #. Tag: para -#: hardware.xml:1332 +#: hardware.xml:1330 #, no-c-format msgid "S821" msgstr "" #. Tag: para -#: hardware.xml:1337 +#: hardware.xml:1335 #, no-c-format msgid "TYAN GN70-BP010" msgstr "" #. Tag: title -#: hardware.xml:1352 +#: hardware.xml:1350 #, no-c-format msgid "zSeries and System z machine types" msgstr "" #. Tag: para -#: hardware.xml:1353 +#: hardware.xml:1351 #, no-c-format msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1370 +#: hardware.xml:1368 #, no-c-format msgid "PAV and HyperPAV" msgstr "" #. Tag: para -#: hardware.xml:1371 +#: hardware.xml:1369 #, 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:1387 +#: hardware.xml:1385 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1388 +#: hardware.xml:1386 #, 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:1399 +#: hardware.xml:1397 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1401 +#: hardware.xml:1399 #, no-c-format msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1408 +#: hardware.xml:1406 #, 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:1418 +#: hardware.xml:1416 #, no-c-format msgid "sun4u" msgstr "" #. Tag: para -#: hardware.xml:1420 +#: hardware.xml:1418 #, 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:1433 +#: hardware.xml:1431 #, no-c-format msgid "sun4v" msgstr "" #. Tag: para -#: hardware.xml:1435 +#: hardware.xml:1433 #, 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:1446 +#: hardware.xml:1444 #, 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:1455 +#: hardware.xml:1453 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1456 +#: hardware.xml:1454 #, no-c-format msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1473 hardware.xml:1493 hardware.xml:1520 hardware.xml:1543 +#: hardware.xml:1471 hardware.xml:1491 hardware.xml:1518 hardware.xml:1541 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1474 +#: hardware.xml:1472 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> 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 <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip." msgstr "" #. Tag: para -#: hardware.xml:1484 +#: hardware.xml:1482 #, 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:1495 +#: hardware.xml:1493 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." msgstr "" #. Tag: para -#: hardware.xml:1504 +#: hardware.xml:1502 #, 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 <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip." msgstr "" #. Tag: para -#: hardware.xml:1511 +#: hardware.xml:1509 #, no-c-format msgid "The 586 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1521 +#: hardware.xml:1519 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use only the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1530 +#: hardware.xml:1528 #, no-c-format msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1544 +#: hardware.xml:1542 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1554 +#: hardware.xml:1552 #, 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:1560 +#: hardware.xml:1558 #, no-c-format msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:1571 +#: hardware.xml:1569 +#, no-c-format +msgid "Graphics Hardware Support" +msgstr "" + +#. Tag: para +#: hardware.xml:1570 #, no-c-format -msgid "Graphics Card Support" +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 <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>)." msgstr "" #. Tag: para -#: hardware.xml:1572 +#: hardware.xml:1582 #, no-c-format -msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions." +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:1585 +#: hardware.xml:1593 #, no-c-format -msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;." +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:1590 +#: hardware.xml:1607 +#, no-c-format +msgid "Details on supported graphics hardware and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;." +msgstr "" + +#. Tag: para +#: hardware.xml:1612 #, 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:1595 +#: hardware.xml:1617 #, no-c-format msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card." msgstr "" #. Tag: para -#: hardware.xml:1605 +#: hardware.xml:1627 #, 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:1627 +#: hardware.xml:1649 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1628 +#: hardware.xml:1650 #, no-c-format msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1638 +#: hardware.xml:1660 #, 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:1644 +#: hardware.xml:1666 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1649 +#: hardware.xml:1671 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1654 +#: hardware.xml:1676 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1659 +#: hardware.xml:1681 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1664 +#: hardware.xml:1686 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1671 +#: hardware.xml:1693 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1676 +#: hardware.xml:1698 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1681 +#: hardware.xml:1703 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1686 +#: hardware.xml:1708 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1695 +#: hardware.xml:1717 #, 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:1700 +#: hardware.xml:1722 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1707 +#: hardware.xml:1729 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1708 +#: hardware.xml:1730 #, 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:1715 +#: hardware.xml:1737 #, no-c-format msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation." msgstr "" #. Tag: para -#: hardware.xml:1720 +#: hardware.xml:1742 #, 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:1725 +#: hardware.xml:1747 #, 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:1735 +#: hardware.xml:1757 #, no-c-format msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:1749 +#: hardware.xml:1771 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1750 +#: hardware.xml:1772 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1757 +#: hardware.xml:1779 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1759 +#: hardware.xml:1781 #, no-c-format msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" #. Tag: para -#: hardware.xml:1769 +#: hardware.xml:1791 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>." msgstr "" #. Tag: para -#: hardware.xml:1777 +#: hardware.xml:1799 #, no-c-format msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted." msgstr "" #. Tag: title -#: hardware.xml:1790 +#: hardware.xml:1812 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1792 +#: hardware.xml:1814 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:1807 +#: hardware.xml:1829 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:1808 +#: hardware.xml:1830 #, no-c-format msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;." msgstr "" #. Tag: title -#: hardware.xml:1822 +#: hardware.xml:1844 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:1823 +#: hardware.xml:1845 #, no-c-format msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;." msgstr "" #. Tag: title -#: hardware.xml:1843 +#: hardware.xml:1865 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:1844 +#: hardware.xml:1866 #, 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:1850 +#: hardware.xml:1872 #, no-c-format msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration." msgstr "" #. Tag: para -#: hardware.xml:1859 +#: hardware.xml:1881 #, 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:1872 +#: hardware.xml:1894 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:1873 +#: hardware.xml:1895 #, no-c-format msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system." msgstr "" #. Tag: para -#: hardware.xml:1884 +#: hardware.xml:1906 #, 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:1892 +#: hardware.xml:1914 #, 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:1901 +#: hardware.xml:1923 #, no-c-format msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." msgstr "" #. Tag: para -#: hardware.xml:1910 +#: hardware.xml:1932 #, 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:1927 +#: hardware.xml:1949 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "" #. Tag: para -#: hardware.xml:1929 +#: hardware.xml:1951 #, no-c-format msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:1937 +#: hardware.xml:1959 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:1945 +#: hardware.xml:1967 #, 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:1956 +#: hardware.xml:1978 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:1957 +#: hardware.xml:1979 #, 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:1967 +#: hardware.xml:1989 #, no-c-format msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant." msgstr "" #. Tag: para -#: hardware.xml:1979 +#: hardware.xml:2001 #, 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:1990 +#: hardware.xml:2012 #, 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:2003 +#: hardware.xml:2025 #, 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:2018 +#: hardware.xml:2040 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:2020 +#: hardware.xml:2042 #, no-c-format msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:2030 +#: hardware.xml:2052 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:2031 +#: hardware.xml:2053 #, 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:2037 +#: hardware.xml:2059 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:2044 +#: hardware.xml:2066 #, no-c-format msgid "CD-ROM/DVD-ROM/BD-ROM" msgstr "" #. Tag: para -#: hardware.xml:2046 +#: hardware.xml:2068 #, no-c-format msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to all of CD-ROMs, DVD-ROMs and BD-ROMs, because all these technologies are really the same from the operating system's point of view." msgstr "" #. Tag: para -#: hardware.xml:2052 +#: hardware.xml:2074 #, no-c-format msgid "CD-ROM based installation is supported for most architectures." msgstr "" #. Tag: para -#: hardware.xml:2056 +#: hardware.xml:2078 #, no-c-format msgid "On PCs SATA, IDE/ATAPI, USB and SCSI CD-ROMs are supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:2071 +#: hardware.xml:2093 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware." msgstr "" #. Tag: title -#: hardware.xml:2085 +#: hardware.xml:2107 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:2087 +#: hardware.xml:2109 #, 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 is the standard way of installing a new operating system on them." msgstr "" #. Tag: title -#: hardware.xml:2099 +#: hardware.xml:2121 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:2101 +#: hardware.xml:2123 #, 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:2111 +#: hardware.xml:2133 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2124 +#: hardware.xml:2146 #, 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:2133 +#: hardware.xml:2155 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2135 +#: hardware.xml:2157 #, 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:2142 +#: hardware.xml:2164 #, 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:2151 +#: hardware.xml:2173 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2153 +#: hardware.xml:2175 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This installation method is only recommended for advanced users when no other installation method is available." msgstr "" #. Tag: title -#: hardware.xml:2166 +#: hardware.xml:2188 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2168 +#: hardware.xml:2190 #, 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:2172 +#: hardware.xml:2194 #, 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:2189 +#: hardware.xml:2211 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." msgstr "" #. Tag: para -#: hardware.xml:2222 +#: hardware.xml:2244 #, 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:2228 +#: hardware.xml:2250 #, 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:2234 +#: hardware.xml:2256 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2239 +#: hardware.xml:2261 #, 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:2256 +#: hardware.xml:2278 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2258 +#: hardware.xml:2280 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:2265 +#: hardware.xml:2287 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the text-based and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot index dc43fc047..20daf54e3 100644 --- a/po/pot/partitioning.pot +++ b/po/pot/partitioning.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2015-04-15 20:29+0000\n" +"POT-Creation-Date: 2015-05-04 18:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -293,7 +293,7 @@ msgstr "" #. Tag: para #: partitioning.xml:155 #, no-c-format -msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150–250MB is needed for the root partition." +msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically &root-system-size-min;–&root-system-size-max;MB is needed for the root partition." msgstr "" #. Tag: para |