diff options
| author | Felipe Augusto van de Wiel <faw@debian.org> | 2009-05-03 00:15:49 +0000 |
|---|---|---|
| committer | Felipe Augusto van de Wiel <faw@debian.org> | 2009-05-03 00:15:49 +0000 |
| commit | 211e43ba7b2efc6db4193ad56241b234148b4e41 (patch) | |
| tree | 4e6b7d25e03be958b792af1535222ca6ac59c259 /po/pot | |
| parent | eca5acbffa5d8cc001073fa70483cbeab7e4d28e (diff) | |
| download | installation-guide-211e43ba7b2efc6db4193ad56241b234148b4e41.zip | |
[SILENT_COMMIT] Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 817 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 1026 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 362 |
3 files changed, 1053 insertions, 1152 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 05ec6f00e..e792af08b 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: 2009-04-29 00:14+0000\n" +"POT-Creation-Date: 2009-05-03 00:14+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" @@ -350,7 +350,7 @@ msgid "As on other architectures, you should install the newest available revisi msgstr "" #. Tag: title -#: boot-installer.xml:301 boot-installer.xml:1047 boot-installer.xml:1574 boot-installer.xml:2071 boot-installer.xml:2153 boot-installer.xml:2242 boot-installer.xml:2588 boot-installer.xml:2697 +#: boot-installer.xml:301 boot-installer.xml:963 boot-installer.xml:1490 boot-installer.xml:1987 boot-installer.xml:2069 boot-installer.xml:2158 boot-installer.xml:2504 boot-installer.xml:2613 #, no-c-format msgid "Booting with TFTP" msgstr "" @@ -499,166 +499,103 @@ msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:468 boot-installer.xml:1053 boot-installer.xml:1592 boot-installer.xml:2077 boot-installer.xml:2594 boot-installer.xml:2703 +#: boot-installer.xml:468 boot-installer.xml:969 boot-installer.xml:1508 boot-installer.xml:1993 boot-installer.xml:2510 boot-installer.xml:2619 #, no-c-format msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" #. Tag: para -#: boot-installer.xml:473 boot-installer.xml:1058 boot-installer.xml:1597 boot-installer.xml:2082 boot-installer.xml:2599 boot-installer.xml:2708 +#: boot-installer.xml:473 boot-installer.xml:974 boot-installer.xml:1513 boot-installer.xml:1998 boot-installer.xml:2515 boot-installer.xml:2624 #, 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:478 boot-installer.xml:1063 boot-installer.xml:1602 boot-installer.xml:2087 boot-installer.xml:2604 boot-installer.xml:2713 +#: boot-installer.xml:478 boot-installer.xml:979 boot-installer.xml:1518 boot-installer.xml:2003 boot-installer.xml:2520 boot-installer.xml:2629 #, no-c-format msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:486 -#, no-c-format -msgid "Booting from TFTP on Netwinder" -msgstr "" - -#. Tag: para -#: boot-installer.xml:487 -#, no-c-format -msgid "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card (which is generally referred to as <literal>eth0</literal>) and a 100Mbps Tulip card. There may be problems loading the image via TFTP using the 100Mbps card so it is recommended that you use the 10Mbps interface (the one labeled with <literal>10 Base-T</literal>)." -msgstr "" - -#. Tag: para -#: boot-installer.xml:496 -#, no-c-format -msgid "You need NeTTrom 2.2.1 or later to boot the installation system, and version 2.3.3 is recommended. Unfortunately, firmware files are currently not available for download because of license issues. If this situation changes, you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:504 -#, no-c-format -msgid "" - "When you boot your Netwinder you have to interrupt the boot process during the countdown. This allows you to set a number of firmware settings needed in order to boot the installer. First of all, start by loading the default settings: <informalexample><screen>\n" - " NeTTrom command-> load-defaults\n" - "</screen></informalexample> Furthermore, you must configure the network, either with a static address: <informalexample><screen>\n" - " NeTTrom command-> setenv netconfig_eth0 flash\n" - " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" - "</screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen>\n" - " NeTTrom command-> setenv netconfig_eth0 dhcp\n" - "</screen></informalexample> You may also need to configure the <userinput>route1</userinput> settings if the TFTP server is not on the local subnet. Following these settings, you have to specify the TFTP server and the location of the image. You can then store your settings to flash. <informalexample><screen>\n" - " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" - " NeTTrom command-> setenv kerntftpfile boot.img\n" - " NeTTrom command-> save-all\n" - "</screen></informalexample> Now you have to tell the firmware that the TFTP image should be booted: <informalexample><screen>\n" - " NeTTrom command-> setenv kernconfig tftp\n" - " NeTTrom command-> setenv rootdev /dev/ram\n" - "</screen></informalexample> If you use a serial console to install your Netwinder, you need to add the following setting: <informalexample><screen>\n" - " NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n" - "</screen></informalexample> Alternatively, for installations using a keyboard and monitor you have to set: <informalexample><screen>\n" - " NeTTrom command-> setenv cmdappend root=/dev/ram\n" - "</screen></informalexample> You can use the <command>printenv</command> command to review your environment settings. After you have verified that the settings are correct, you can load the image: <informalexample><screen>\n" - " NeTTrom command-> boot\n" - "</screen></informalexample> In case you run into any problems, a <ulink url=\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</ulink> is available." -msgstr "" - -#. Tag: title -#: boot-installer.xml:556 -#, no-c-format -msgid "Booting from TFTP on CATS" -msgstr "" - -#. Tag: para -#: boot-installer.xml:557 -#, no-c-format -msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt." -msgstr "" - -#. Tag: title -#: boot-installer.xml:567 +#: boot-installer.xml:489 #, no-c-format msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1211 boot-installer.xml:2034 boot-installer.xml:2380 boot-installer.xml:2742 +#: boot-installer.xml:495 boot-installer.xml:659 boot-installer.xml:1127 boot-installer.xml:1950 boot-installer.xml:2296 boot-installer.xml:2658 #, no-c-format msgid "The easiest route for most people will be to use a set of Debian CDs. 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:584 boot-installer.xml:754 boot-installer.xml:1222 boot-installer.xml:2045 boot-installer.xml:2391 boot-installer.xml:2753 +#: boot-installer.xml:506 boot-installer.xml:670 boot-installer.xml:1138 boot-installer.xml:1961 boot-installer.xml:2307 boot-installer.xml:2669 #, 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:592 boot-installer.xml:762 boot-installer.xml:1230 boot-installer.xml:2053 boot-installer.xml:2399 boot-installer.xml:2761 +#: boot-installer.xml:514 boot-installer.xml:678 boot-installer.xml:1146 boot-installer.xml:1969 boot-installer.xml:2315 boot-installer.xml:2677 #, 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 media, such as floppies. 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:600 boot-installer.xml:770 boot-installer.xml:1238 boot-installer.xml:2061 boot-installer.xml:2407 boot-installer.xml:2769 +#: boot-installer.xml:522 boot-installer.xml:686 boot-installer.xml:1154 boot-installer.xml:1977 boot-installer.xml:2323 boot-installer.xml:2685 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" -#. Tag: para -#: boot-installer.xml:607 -#, no-c-format -msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>" -msgstr "" - #. Tag: title -#: boot-installer.xml:616 +#: boot-installer.xml:532 #, no-c-format msgid "Booting from Firmware" msgstr "" #. Tag: para -#: boot-installer.xml:622 +#: boot-installer.xml:538 #, no-c-format msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines." msgstr "" #. Tag: para -#: boot-installer.xml:628 +#: boot-installer.xml:544 #, no-c-format msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely." msgstr "" #. Tag: title -#: boot-installer.xml:639 +#: boot-installer.xml:555 #, no-c-format msgid "Booting the NSLU2" msgstr "" #. Tag: para -#: boot-installer.xml:640 +#: boot-installer.xml:556 #, no-c-format msgid "There are three ways how to put the installer firmware into flash:" msgstr "" #. Tag: title -#: boot-installer.xml:646 +#: boot-installer.xml:562 #, no-c-format msgid "Using the NSLU2 web interface" msgstr "" #. Tag: para -#: boot-installer.xml:647 +#: boot-installer.xml:563 #, no-c-format msgid "Go to the administration section and choose the menu item <literal>Upgrade</literal>. You can then browse your disk for the installer image you have previously downloaded. Then press the <literal>Start Upgrade</literal> button, confirm, wait for a few minutes and confirm again. The system will then boot straight into the installer." msgstr "" #. Tag: title -#: boot-installer.xml:658 +#: boot-installer.xml:574 #, no-c-format msgid "Via the network using Linux/Unix" msgstr "" #. Tag: para -#: boot-installer.xml:659 +#: boot-installer.xml:575 #, no-c-format msgid "" "You can use <command>upslug2</command> from any Linux or Unix machine to upgrade the machine via the network. This software is packaged for Debian. First, you have to put your NSLU2 in upgrade mode: <orderedlist> <listitem><para> Disconnect any disks and/or devices from the USB ports. </para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> <listitem><para> Press and hold the reset button (accessible through the small hole on the back just above the power input). </para></listitem> <listitem><para> Press and release the power button to power on the NSLU2. </para></listitem> <listitem><para> Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button. </para></listitem> <listitem><para> The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. </para></listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image: <informalexample><screen>\n" @@ -667,79 +604,79 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:720 +#: boot-installer.xml:636 #, no-c-format msgid "Via the network using Windows" msgstr "" #. Tag: para -#: boot-installer.xml:721 +#: boot-installer.xml:637 #, no-c-format msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware via the network." msgstr "" #. Tag: title -#: boot-installer.xml:737 boot-installer.xml:1205 boot-installer.xml:2022 boot-installer.xml:2374 boot-installer.xml:2736 +#: boot-installer.xml:653 boot-installer.xml:1121 boot-installer.xml:1938 boot-installer.xml:2290 boot-installer.xml:2652 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" #. Tag: title -#: boot-installer.xml:844 +#: boot-installer.xml:760 #, no-c-format msgid "Booting from Windows" msgstr "" #. Tag: para -#: boot-installer.xml:845 +#: boot-installer.xml:761 #, no-c-format msgid "To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:851 +#: boot-installer.xml:767 #, 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:859 +#: boot-installer.xml:775 #, no-c-format msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to start the &debian; installer." msgstr "" #. Tag: title -#: boot-installer.xml:899 +#: boot-installer.xml:815 #, no-c-format msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: boot-installer.xml:902 +#: boot-installer.xml:818 #, 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:907 +#: boot-installer.xml:823 #, 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:917 +#: boot-installer.xml:833 #, 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:926 +#: boot-installer.xml:842 #, 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:947 +#: boot-installer.xml:863 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -748,19 +685,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:947 +#: boot-installer.xml:863 #, 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:956 +#: boot-installer.xml:872 #, no-c-format msgid "The procedure for <command>GRUB</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:964 +#: boot-installer.xml:880 #, no-c-format msgid "" "title New Install\n" @@ -770,127 +707,127 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:966 +#: boot-installer.xml:882 #, 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:975 +#: boot-installer.xml:891 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" #. Tag: para -#: boot-installer.xml:976 +#: boot-installer.xml:892 #, no-c-format msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should 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: title -#: boot-installer.xml:989 boot-installer.xml:2134 boot-installer.xml:2643 +#: boot-installer.xml:905 boot-installer.xml:2050 boot-installer.xml:2559 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:990 boot-installer.xml:2651 +#: boot-installer.xml:906 boot-installer.xml:2567 #, 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:997 +#: boot-installer.xml:913 #, 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:1003 +#: boot-installer.xml:919 #, 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:1013 +#: boot-installer.xml:929 #, 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:1022 +#: boot-installer.xml:938 #, 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:1028 +#: boot-installer.xml:944 #, 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:1037 +#: boot-installer.xml:953 #, 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: para -#: boot-installer.xml:1071 +#: boot-installer.xml:987 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:1077 +#: boot-installer.xml:993 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:1078 +#: boot-installer.xml:994 #, 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:1089 +#: boot-installer.xml:1005 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:1090 +#: boot-installer.xml:1006 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:1095 +#: boot-installer.xml:1011 #, 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:1103 +#: boot-installer.xml:1019 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:1104 +#: boot-installer.xml:1020 #, 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:1114 +#: boot-installer.xml:1030 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:1115 +#: boot-installer.xml:1031 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and a menu: <informalexample><screen>\n" @@ -906,25 +843,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1125 +#: boot-installer.xml:1041 #, no-c-format msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical 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." msgstr "" #. Tag: para -#: boot-installer.xml:1132 +#: boot-installer.xml:1048 #, 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:1138 +#: boot-installer.xml:1054 #, no-c-format msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; 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:1147 +#: boot-installer.xml:1063 #, 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. Note that it is not possible to return to the boot menu after the help screens have been displayed. However, the F3 and F4 help screens list commands that are equivalent to the boot methods listed in the menu. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n" @@ -933,259 +870,259 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1166 +#: boot-installer.xml:1082 #, 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:1176 +#: boot-installer.xml:1092 #, 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:1186 +#: boot-installer.xml:1102 #, 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>fb=false</userinput> to the boot prompt, as described in the help text." msgstr "" #. Tag: title -#: boot-installer.xml:1246 +#: boot-installer.xml:1162 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:1248 +#: boot-installer.xml:1164 #, 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:1264 +#: boot-installer.xml:1180 #, 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:1280 +#: boot-installer.xml:1196 #, 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:1289 +#: boot-installer.xml:1205 #, 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:1301 +#: boot-installer.xml:1217 #, 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:1320 +#: boot-installer.xml:1236 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:1321 +#: boot-installer.xml:1237 #, 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:1333 +#: boot-installer.xml:1249 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:1340 +#: boot-installer.xml:1256 #, 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:1346 +#: boot-installer.xml:1262 #, 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:1352 +#: boot-installer.xml:1268 #, 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:1363 +#: boot-installer.xml:1279 #, 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:1374 +#: boot-installer.xml:1290 #, 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:1386 +#: boot-installer.xml:1302 #, 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:1396 +#: boot-installer.xml:1312 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:1397 +#: boot-installer.xml:1313 #, 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:1408 +#: boot-installer.xml:1324 #, 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:1414 +#: boot-installer.xml:1330 #, 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:1428 +#: boot-installer.xml:1344 #, 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:1435 +#: boot-installer.xml:1351 #, 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:1442 +#: boot-installer.xml:1358 #, 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:1449 +#: boot-installer.xml:1365 #, 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:1463 +#: boot-installer.xml:1379 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1465 +#: boot-installer.xml:1381 #, 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:1476 +#: boot-installer.xml:1392 #, 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:1483 +#: boot-installer.xml:1399 #, 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:1494 +#: boot-installer.xml:1410 #, 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:1503 +#: boot-installer.xml:1419 #, 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:1512 +#: boot-installer.xml:1428 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1514 +#: boot-installer.xml:1430 #, 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:1526 +#: boot-installer.xml:1442 #, 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:1544 +#: boot-installer.xml:1460 #, 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:1549 +#: boot-installer.xml:1465 #, 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:1556 +#: boot-installer.xml:1472 #, 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:1565 boot-installer.xml:1701 +#: boot-installer.xml:1481 boot-installer.xml:1617 #, 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:1576 +#: boot-installer.xml:1492 #, 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:1610 +#: boot-installer.xml:1526 #, 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:1621 +#: boot-installer.xml:1537 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1622 +#: boot-installer.xml:1538 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" @@ -1198,13 +1135,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1632 +#: boot-installer.xml:1548 #, 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:1642 +#: boot-installer.xml:1558 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -1216,331 +1153,331 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1642 +#: boot-installer.xml:1558 #, 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:1659 +#: boot-installer.xml:1575 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1660 +#: boot-installer.xml:1576 #, 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:1692 +#: boot-installer.xml:1608 #, 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:1714 +#: boot-installer.xml:1630 #, no-c-format msgid "Choosing an Installation Method" msgstr "" #. Tag: para -#: boot-installer.xml:1716 +#: boot-installer.xml:1632 #, no-c-format msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs." msgstr "" #. Tag: para -#: boot-installer.xml:1724 +#: boot-installer.xml:1640 #, no-c-format msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." msgstr "" #. Tag: para -#: boot-installer.xml:1729 +#: boot-installer.xml:1645 #, no-c-format msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters." msgstr "" #. Tag: para -#: boot-installer.xml:1734 +#: boot-installer.xml:1650 #, no-c-format msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:1751 +#: boot-installer.xml:1667 #, no-c-format msgid "Amiga" msgstr "" #. Tag: para -#: boot-installer.xml:1752 +#: boot-installer.xml:1668 #, no-c-format msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: para -#: boot-installer.xml:1758 +#: boot-installer.xml:1674 #, no-c-format msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:1767 +#: boot-installer.xml:1683 #, no-c-format msgid "Atari" msgstr "" #. Tag: para -#: boot-installer.xml:1768 +#: boot-installer.xml:1684 #, no-c-format msgid "The installer for atari may be started from either the hard drive (see <xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: para -#: boot-installer.xml:1775 +#: boot-installer.xml:1691 #, no-c-format msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:1784 +#: boot-installer.xml:1700 #, no-c-format msgid "BVME6000" msgstr "" #. Tag: para -#: boot-installer.xml:1785 +#: boot-installer.xml:1701 #, no-c-format msgid "The installer for BVME6000 may be started from a cdrom (see <xref linkend=\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:1795 +#: boot-installer.xml:1711 #, no-c-format msgid "Macintosh" msgstr "" #. Tag: para -#: boot-installer.xml:1796 +#: boot-installer.xml:1712 #, no-c-format msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1803 +#: boot-installer.xml:1719 #, no-c-format msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but which will disable SCSI disconnects. Note that specifying this parameter is only necessary if you have more than one hard disk; otherwise, the system will run faster if you do not specify it." msgstr "" #. Tag: title -#: boot-installer.xml:1818 +#: boot-installer.xml:1734 #, no-c-format msgid "MVME147 and MVME16x" msgstr "" #. Tag: para -#: boot-installer.xml:1819 +#: boot-installer.xml:1735 #, no-c-format msgid "The installer for MVME147 and MVME16x may be started from either floppies (see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: title -#: boot-installer.xml:1829 +#: boot-installer.xml:1745 #, no-c-format msgid "Q40/Q60" msgstr "" #. Tag: para -#: boot-installer.xml:1830 +#: boot-installer.xml:1746 #, no-c-format msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: title -#: boot-installer.xml:1841 +#: boot-installer.xml:1757 #, no-c-format msgid "Booting from a Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1847 boot-installer.xml:2453 +#: boot-installer.xml:1763 boot-installer.xml:2369 #, 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:1853 boot-installer.xml:2459 +#: boot-installer.xml:1769 boot-installer.xml:2375 #, no-c-format msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1862 +#: boot-installer.xml:1778 #, no-c-format msgid "At least six different ramdisks may be used to boot from the hard drive, three different types each with and without support for a 2.2.x linux kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> for details)." msgstr "" #. Tag: para -#: boot-installer.xml:1870 +#: boot-installer.xml:1786 #, no-c-format msgid "The three different types of ramdisks are <filename>cdrom</filename>, <filename>hd-media</filename>, and <filename>nativehd</filename>. These ramdisks differ only in their source for installation packages. The <filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer packages. The <filename>hd-media</filename> ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the <filename>nativehd</filename> ramdisk uses the net to install packages." msgstr "" #. Tag: title -#: boot-installer.xml:1891 +#: boot-installer.xml:1807 #, no-c-format msgid "Booting from AmigaOS" msgstr "" #. Tag: para -#: boot-installer.xml:1892 +#: boot-installer.xml:1808 #, no-c-format msgid "In the <command>Workbench</command>, start the Linux installation process by double-clicking on the <guiicon>StartInstall</guiicon> icon in the <filename>debian</filename> directory." msgstr "" #. Tag: para -#: boot-installer.xml:1898 +#: boot-installer.xml:1814 #, no-c-format msgid "You may have to press the &enterkey; key twice after the Amiga installer program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue down at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1913 +#: boot-installer.xml:1829 #, no-c-format msgid "Booting from Atari TOS" msgstr "" #. Tag: para -#: boot-installer.xml:1914 +#: boot-installer.xml:1830 #, no-c-format msgid "At the GEM desktop, start the Linux installation process by double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</filename> directory and clicking <guibutton>Ok</guibutton> at the program options dialog box." msgstr "" #. Tag: para -#: boot-installer.xml:1921 +#: boot-installer.xml:1837 #, no-c-format msgid "You may have to press the &enterkey; key after the Atari bootstrap program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1936 +#: boot-installer.xml:1852 #, no-c-format msgid "Booting from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1937 +#: boot-installer.xml:1853 #, no-c-format msgid "You must retain the original Mac system and boot from it. It is <emphasis>essential</emphasis> that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the <keycap>shift</keycap> key down to prevent extensions from loading. If you don't use MacOS except for loading linux, you can accomplish the same thing by removing all extensions and control panels from the Mac's System Folder. Otherwise extensions may be left running and cause random problems with the running linux kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1948 +#: boot-installer.xml:1864 #, no-c-format msgid "Macs require the <command>Penguin</command> bootloader, which can be downloaded from <ulink url=\"&url-m68k-mac;\">the Linux/mac68k sourceforge.net project</ulink>. If you do not have the tools to handle a <command>Stuffit</command> archive, you can put it on a MacOS-formatted floppy using a second GNU/Linux machine of any architecture and the <command>hmount</command>, <command>hcopy</command>, and <command>humount</command> tools from the <classname>hfsutils</classname> suite." msgstr "" #. Tag: para -#: boot-installer.xml:1959 +#: boot-installer.xml:1875 #, no-c-format msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in the <filename>Penguin</filename> directory. The <command>Penguin</command> booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</filename> directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files." msgstr "" #. Tag: para -#: boot-installer.xml:1974 +#: boot-installer.xml:1890 #, no-c-format msgid "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> <guimenuitem>Settings...</guimenuitem>, then switch to the <guilabel>Options</guilabel> tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</guimenuitem>." msgstr "" #. Tag: para -#: boot-installer.xml:1983 +#: boot-installer.xml:1899 #, no-c-format msgid "Close the <guilabel>Settings</guilabel> dialog, save the settings and start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the <guimenu>File</guimenu> menu." msgstr "" #. Tag: para -#: boot-installer.xml:1990 +#: boot-installer.xml:1906 #, no-c-format msgid "The <command>Penguin</command> booter will output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2005 +#: boot-installer.xml:1921 #, no-c-format msgid "Booting from Q40/Q60" msgstr "" #. Tag: para -#: boot-installer.xml:2007 +#: boot-installer.xml:1923 #, no-c-format msgid "FIXME" msgstr "" #. Tag: para -#: boot-installer.xml:2011 +#: boot-installer.xml:1927 #, no-c-format msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2023 +#: boot-installer.xml:1939 #, no-c-format msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." msgstr "" #. Tag: para -#: boot-installer.xml:2095 +#: boot-installer.xml:2011 #, no-c-format msgid "After booting the VMEbus systems you will be presented with the LILO <prompt>Boot:</prompt> prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:" msgstr "" #. Tag: para -#: boot-installer.xml:2106 +#: boot-installer.xml:2022 #, no-c-format msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000" msgstr "" #. Tag: para -#: boot-installer.xml:2111 +#: boot-installer.xml:2027 #, no-c-format msgid "type <screen>i162 &enterkey;</screen> to install an MVME162" msgstr "" #. Tag: para -#: boot-installer.xml:2116 +#: boot-installer.xml:2032 #, no-c-format msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167" msgstr "" #. Tag: para -#: boot-installer.xml:2123 +#: boot-installer.xml:2039 #, no-c-format msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." msgstr "" #. Tag: para -#: boot-installer.xml:2135 +#: boot-installer.xml:2051 #, no-c-format msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method." msgstr "" #. Tag: para -#: boot-installer.xml:2140 +#: boot-installer.xml:2056 #, no-c-format msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." msgstr "" #. Tag: title -#: boot-installer.xml:2156 boot-installer.xml:2203 +#: boot-installer.xml:2072 boot-installer.xml:2119 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2157 +#: boot-installer.xml:2073 #, no-c-format msgid "" "After entering the command monitor use <informalexample><screen>\n" @@ -1551,13 +1488,13 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2176 boot-installer.xml:2225 boot-installer.xml:2280 boot-installer.xml:2319 +#: boot-installer.xml:2092 boot-installer.xml:2141 boot-installer.xml:2196 boot-installer.xml:2235 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2177 boot-installer.xml:2281 +#: boot-installer.xml:2093 boot-installer.xml:2197 #, no-c-format msgid "" "On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: <informalexample><screen>\n" @@ -1568,19 +1505,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2200 boot-installer.xml:2304 boot-installer.xml:2907 +#: boot-installer.xml:2116 boot-installer.xml:2220 boot-installer.xml:2823 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2204 +#: boot-installer.xml:2120 #, 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:2209 +#: boot-installer.xml:2125 #, 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" @@ -1589,127 +1526,127 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2219 +#: boot-installer.xml:2135 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: para -#: boot-installer.xml:2226 boot-installer.xml:2320 +#: boot-installer.xml:2142 boot-installer.xml:2236 #, no-c-format msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP server and add your parameters to the <replaceable>extra_args</replaceable> variable." msgstr "" #. Tag: title -#: boot-installer.xml:2245 boot-installer.xml:2307 +#: boot-installer.xml:2161 boot-installer.xml:2223 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2246 +#: boot-installer.xml:2162 #, no-c-format msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:" msgstr "" #. Tag: para -#: boot-installer.xml:2256 +#: boot-installer.xml:2172 #, no-c-format msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation." msgstr "" #. Tag: para -#: boot-installer.xml:2265 +#: boot-installer.xml:2181 #, no-c-format msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port." msgstr "" #. Tag: para -#: boot-installer.xml:2308 +#: boot-installer.xml:2224 #, no-c-format msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable." msgstr "" #. Tag: title -#: boot-installer.xml:2336 +#: boot-installer.xml:2252 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:2337 +#: boot-installer.xml:2253 #, 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:2342 +#: boot-installer.xml:2258 #, 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:2353 +#: boot-installer.xml:2269 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2354 +#: boot-installer.xml:2270 #, 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. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images." msgstr "" #. Tag: para -#: boot-installer.xml:2414 +#: boot-installer.xml:2330 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (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 CD-ROM." msgstr "" #. Tag: para -#: boot-installer.xml:2423 +#: boot-installer.xml:2339 #, 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:2432 +#: boot-installer.xml:2348 #, no-c-format msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as" msgstr "" #. Tag: screen -#: boot-installer.xml:2441 +#: boot-installer.xml:2357 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: title -#: boot-installer.xml:2447 +#: boot-installer.xml:2363 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: title -#: boot-installer.xml:2479 +#: boot-installer.xml:2395 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:2480 +#: boot-installer.xml:2396 #, 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:2498 +#: boot-installer.xml:2414 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:2499 +#: boot-installer.xml:2415 #, 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" @@ -1720,31 +1657,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2531 +#: boot-installer.xml:2447 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:2532 +#: boot-installer.xml:2448 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:2538 +#: boot-installer.xml:2454 #, 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:2547 +#: boot-installer.xml:2463 #, 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:2559 +#: boot-installer.xml:2475 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1753,25 +1690,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2573 +#: boot-installer.xml:2489 #, 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:2579 +#: boot-installer.xml:2495 #, 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:2612 +#: boot-installer.xml:2528 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:2616 +#: boot-installer.xml:2532 #, 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" @@ -1784,163 +1721,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2644 +#: boot-installer.xml:2560 #, 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:2656 +#: boot-installer.xml:2572 #, 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:2662 +#: boot-installer.xml:2578 #, 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:2669 +#: boot-installer.xml:2585 #, 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:2680 +#: boot-installer.xml:2596 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2681 +#: boot-installer.xml:2597 #, 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: para -#: boot-installer.xml:2721 +#: boot-installer.xml:2637 #, 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:2776 +#: boot-installer.xml:2692 #, 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:2785 +#: boot-installer.xml:2701 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:2786 +#: boot-installer.xml:2702 #, 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:2805 +#: boot-installer.xml:2721 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:2806 +#: boot-installer.xml:2722 #, no-c-format msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"alpha;ia64;powerpc;x86\">USB braille displays are detected automatically, but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;m68k;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. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." msgstr "" #. Tag: title -#: boot-installer.xml:2823 +#: boot-installer.xml:2739 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2824 +#: boot-installer.xml:2740 #, 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." msgstr "" #. Tag: title -#: boot-installer.xml:2837 +#: boot-installer.xml:2753 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2838 +#: boot-installer.xml:2754 #, 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-driver-codes;\">driver code list</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. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-table-codes;\">table code list</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu." msgstr "" #. Tag: title -#: boot-installer.xml:2858 +#: boot-installer.xml:2774 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:2859 +#: boot-installer.xml:2775 #, no-c-format msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select the <quote>Graphical install</quote> entry in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:2865 +#: boot-installer.xml:2781 #, 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-driver-codes;\">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:2880 +#: boot-installer.xml:2796 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:2881 +#: boot-installer.xml:2797 #, 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>fb=false</userinput> boot parameter. This will however reduce the number of available languages." msgstr "" #. Tag: title -#: boot-installer.xml:2892 +#: boot-installer.xml:2808 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:2893 +#: boot-installer.xml:2809 #, no-c-format msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter." msgstr "" #. Tag: para -#: boot-installer.xml:2908 +#: boot-installer.xml:2824 #, 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:2915 +#: boot-installer.xml:2831 #, 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:2922 +#: boot-installer.xml:2838 #, 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: para -#: boot-installer.xml:2931 +#: boot-installer.xml:2847 #, no-c-format msgid "" "When the kernel boots, a message <informalexample><screen>\n" @@ -1949,511 +1886,511 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2947 +#: boot-installer.xml:2863 #, 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><footnote> <para> 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>. </para> </footnote>." msgstr "" #. Tag: para -#: boot-installer.xml:2971 +#: boot-installer.xml:2887 #, 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:2982 +#: boot-installer.xml:2898 #, no-c-format msgid "Debian Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2983 +#: boot-installer.xml:2899 #, 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:2996 +#: boot-installer.xml:2912 #, 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:3008 +#: boot-installer.xml:2924 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:3009 +#: boot-installer.xml:2925 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:3013 +#: boot-installer.xml:2929 #, 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:3020 +#: boot-installer.xml:2936 #, 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:3034 +#: boot-installer.xml:2950 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:3035 +#: boot-installer.xml:2951 #, 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. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:3064 +#: boot-installer.xml:2980 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:3065 +#: boot-installer.xml:2981 #, 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:3074 +#: boot-installer.xml:2990 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:3075 +#: boot-installer.xml:2991 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:3079 +#: boot-installer.xml:2995 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:3080 +#: boot-installer.xml:2996 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:3084 +#: boot-installer.xml:3000 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:3085 +#: boot-installer.xml:3001 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:3089 +#: boot-installer.xml:3005 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:3090 +#: boot-installer.xml:3006 #, 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:3104 +#: boot-installer.xml:3020 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:3105 +#: boot-installer.xml:3021 #, 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:3111 +#: boot-installer.xml:3027 #, 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:3121 +#: boot-installer.xml:3037 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:3122 +#: boot-installer.xml:3038 #, 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:3132 +#: boot-installer.xml:3048 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:3133 +#: boot-installer.xml:3049 #, 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:3142 +#: boot-installer.xml:3058 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:3143 +#: boot-installer.xml:3059 #, 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 by the parameter <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:3152 +#: boot-installer.xml:3068 #, no-c-format msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." msgstr "" #. Tag: para -#: boot-installer.xml:3158 +#: boot-installer.xml:3074 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para -#: boot-installer.xml:3162 +#: boot-installer.xml:3078 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:3166 +#: boot-installer.xml:3082 #, 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:3180 +#: boot-installer.xml:3096 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:3181 +#: boot-installer.xml:3097 #, 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:3193 boot-installer.xml:3443 +#: boot-installer.xml:3109 boot-installer.xml:3359 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:3194 +#: boot-installer.xml:3110 #, no-c-format msgid "By default, the &d-i; automatically probes for network configuration via 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 DHCP probe fails." msgstr "" #. Tag: para -#: boot-installer.xml:3201 +#: boot-installer.xml:3117 #, no-c-format msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:3212 +#: boot-installer.xml:3128 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:3213 +#: boot-installer.xml:3129 #, 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:3223 +#: boot-installer.xml:3139 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:3224 +#: boot-installer.xml:3140 #, 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:3235 +#: boot-installer.xml:3151 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:3236 +#: boot-installer.xml:3152 #, 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:3245 +#: boot-installer.xml:3161 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:3246 +#: boot-installer.xml:3162 #, 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:3255 +#: boot-installer.xml:3171 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:3256 +#: boot-installer.xml:3172 #, 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:3268 +#: boot-installer.xml:3184 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:3269 +#: boot-installer.xml:3185 #, 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:3280 +#: boot-installer.xml:3196 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:3281 +#: boot-installer.xml:3197 #, 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:3292 +#: boot-installer.xml:3208 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:3293 +#: boot-installer.xml:3209 #, 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:3302 +#: boot-installer.xml:3218 #, 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:3313 +#: boot-installer.xml:3229 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:3314 +#: boot-installer.xml:3230 #, 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:3325 +#: boot-installer.xml:3241 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:3326 +#: boot-installer.xml:3242 #, 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:3336 +#: boot-installer.xml:3252 #, no-c-format msgid "mouse/protocol" msgstr "" #. Tag: para -#: boot-installer.xml:3337 +#: boot-installer.xml:3253 #, no-c-format msgid "For the gtk frontend (graphical installer), users can set the mouse protocol to be used by setting this parameter. Supported values are<footnote> <para> See the man page for <citerefentry><refentrytitle>directfbrc</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for additional information. </para> </footnote>: <userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, <userinput>MS</userinput>, <userinput>MS3</userinput>, <userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>. In most cases the default protocol should work correctly." msgstr "" #. Tag: term -#: boot-installer.xml:3359 +#: boot-installer.xml:3275 #, no-c-format msgid "mouse/device" msgstr "" #. Tag: para -#: boot-installer.xml:3360 +#: boot-installer.xml:3276 #, no-c-format msgid "For the gtk frontend (graphical installer), users can specify the mouse device to be used by setting this parameter. This is mostly useful if the mouse is connected to a serial port (serial mouse). Example: <userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3371 +#: boot-installer.xml:3287 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:3372 +#: boot-installer.xml:3288 #, no-c-format msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3381 +#: boot-installer.xml:3297 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3382 +#: boot-installer.xml:3298 #, no-c-format msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. Set this parameter to <userinput>true</userinput> to enable it." msgstr "" #. Tag: term -#: boot-installer.xml:3392 +#: boot-installer.xml:3308 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3393 +#: boot-installer.xml:3309 #, 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:3404 +#: boot-installer.xml:3320 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:3405 +#: boot-installer.xml:3321 #, 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:3417 +#: boot-installer.xml:3333 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:3418 +#: boot-installer.xml:3334 #, no-c-format msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." msgstr "" #. Tag: term -#: boot-installer.xml:3429 +#: boot-installer.xml:3345 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:3430 +#: boot-installer.xml:3346 #, 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:3444 +#: boot-installer.xml:3360 #, no-c-format msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:3453 +#: boot-installer.xml:3369 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:3454 +#: boot-installer.xml:3370 #, 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:3467 +#: boot-installer.xml:3383 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:3468 +#: boot-installer.xml:3384 #, 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:3482 +#: boot-installer.xml:3398 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3483 +#: boot-installer.xml:3399 #, 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:3496 +#: boot-installer.xml:3412 #, 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:3503 +#: boot-installer.xml:3419 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2462,133 +2399,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3513 +#: boot-installer.xml:3429 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3519 +#: boot-installer.xml:3435 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3520 +#: boot-installer.xml:3436 #, 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:3529 +#: boot-installer.xml:3445 #, 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:3537 +#: boot-installer.xml:3453 #, 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:3554 +#: boot-installer.xml:3470 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3559 +#: boot-installer.xml:3475 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3560 +#: boot-installer.xml:3476 #, 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:3567 +#: boot-installer.xml:3483 #, 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:3573 +#: boot-installer.xml:3489 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3578 +#: boot-installer.xml:3494 #, 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:3584 +#: boot-installer.xml:3500 #, 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 older CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:3594 +#: boot-installer.xml:3510 #, 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:3600 +#: boot-installer.xml:3516 #, 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:3608 +#: boot-installer.xml:3524 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3611 +#: boot-installer.xml:3527 #, 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:3617 +#: boot-installer.xml:3533 #, no-c-format msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:3624 +#: boot-installer.xml:3540 #, no-c-format msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled." msgstr "" #. Tag: title -#: boot-installer.xml:3635 +#: boot-installer.xml:3551 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3636 +#: boot-installer.xml:3552 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3641 +#: boot-installer.xml:3557 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" #. Tag: para -#: boot-installer.xml:3647 +#: boot-installer.xml:3563 #, 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" @@ -2598,7 +2535,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3660 +#: boot-installer.xml:3576 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2611,19 +2548,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3665 +#: boot-installer.xml:3581 #, 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 Linux 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:3677 +#: boot-installer.xml:3593 #, 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:3684 +#: boot-installer.xml:3600 #, 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" @@ -2636,13 +2573,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3698 +#: boot-installer.xml:3614 #, 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:3706 +#: boot-installer.xml:3622 #, 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" @@ -2651,7 +2588,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3716 +#: boot-installer.xml:3632 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2664,163 +2601,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3731 +#: boot-installer.xml:3647 #, 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:3746 +#: boot-installer.xml:3662 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3748 +#: boot-installer.xml:3664 #, 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:3753 +#: boot-installer.xml:3669 #, 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:3762 +#: boot-installer.xml:3678 #, 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:3771 +#: boot-installer.xml:3687 #, 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:3777 +#: boot-installer.xml:3693 #, 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:3783 +#: boot-installer.xml:3699 #, 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:3792 +#: boot-installer.xml:3708 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3794 +#: boot-installer.xml:3710 #, 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:3801 +#: boot-installer.xml:3717 #, no-c-format msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para -#: boot-installer.xml:3807 +#: boot-installer.xml:3723 #, no-c-format msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:3818 boot-installer.xml:3920 +#: boot-installer.xml:3734 boot-installer.xml:3836 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3819 +#: boot-installer.xml:3735 #, 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:3824 +#: boot-installer.xml:3740 #, no-c-format msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3830 +#: boot-installer.xml:3746 #, no-c-format msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3839 +#: boot-installer.xml:3755 #, no-c-format msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para -#: boot-installer.xml:3846 +#: boot-installer.xml:3762 #, no-c-format msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3864 +#: boot-installer.xml:3780 #, 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:3878 +#: boot-installer.xml:3794 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3879 +#: boot-installer.xml:3795 #, no-c-format msgid "Some 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:3889 +#: boot-installer.xml:3805 #, 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: title -#: boot-installer.xml:3906 +#: boot-installer.xml:3822 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3907 +#: boot-installer.xml:3823 #, no-c-format msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>nousb</userinput> parameter at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:3921 +#: boot-installer.xml:3837 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3927 +#: boot-installer.xml:3843 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3928 +#: boot-installer.xml:3844 #, 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" @@ -2830,85 +2767,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3942 +#: boot-installer.xml:3858 #, 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:3953 +#: boot-installer.xml:3869 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3954 +#: boot-installer.xml:3870 #, 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:3960 +#: boot-installer.xml:3876 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3969 +#: boot-installer.xml:3885 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3971 +#: boot-installer.xml:3887 #, 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 (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:3996 +#: boot-installer.xml:3912 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3997 +#: boot-installer.xml:3913 #, 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:4008 +#: boot-installer.xml:3924 #, 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:4019 +#: boot-installer.xml:3935 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:4020 +#: boot-installer.xml:3936 #, 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:4027 +#: boot-installer.xml:3943 #, 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:4033 +#: boot-installer.xml:3949 #, 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:4043 +#: boot-installer.xml:3959 #, 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 e59edf476..429d7436c 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: 2009-04-08 00:13+0000\n" +"POT-Creation-Date: 2009-05-03 00:14+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" @@ -125,2993 +125,2981 @@ msgstr "" #. Tag: entry #: hardware.xml:82 #, no-c-format -msgid "<entry>arm</entry>" +msgid "armel" msgstr "" #. Tag: entry #: hardware.xml:83 #, no-c-format -msgid "Netwinder and CATS" +msgid "Intel IOP32x" msgstr "" #. Tag: entry #: hardware.xml:84 #, no-c-format -msgid "netwinder" +msgid "iop32x" msgstr "" #. Tag: entry #: hardware.xml:86 #, no-c-format -msgid "armel" +msgid "Intel IXP4xx" msgstr "" #. Tag: entry #: hardware.xml:87 #, no-c-format -msgid "<entry>Versatile</entry>" +msgid "ixp4xx" msgstr "" #. Tag: entry -#: hardware.xml:88 +#: hardware.xml:89 #, no-c-format -msgid "versatile" +msgid "Marvell Kirkwood" msgstr "" #. Tag: entry #: hardware.xml:90 #, no-c-format -msgid "arm and armel" -msgstr "" - -#. Tag: entry -#: hardware.xml:91 -#, no-c-format -msgid "Intel IOP32x" +msgid "kirkwood" msgstr "" #. Tag: entry #: hardware.xml:92 #, no-c-format -msgid "iop32x" +msgid "Marvell Orion" msgstr "" #. Tag: entry -#: hardware.xml:94 +#: hardware.xml:93 #, no-c-format -msgid "Intel IXP4xx" +msgid "orion5x" msgstr "" #. Tag: entry #: hardware.xml:95 #, no-c-format -msgid "ixp4xx" -msgstr "" - -#. Tag: entry -#: hardware.xml:97 -#, no-c-format -msgid "Marvell Orion" +msgid "<entry>Versatile</entry>" msgstr "" #. Tag: entry -#: hardware.xml:98 +#: hardware.xml:96 #, no-c-format -msgid "orion5x" +msgid "versatile" msgstr "" #. Tag: entry -#: hardware.xml:102 +#: hardware.xml:100 #, no-c-format msgid "HP PA-RISC" msgstr "" #. Tag: entry -#: hardware.xml:103 +#: hardware.xml:101 #, no-c-format msgid "hppa" msgstr "" #. Tag: entry -#: hardware.xml:104 +#: hardware.xml:102 #, no-c-format msgid "PA-RISC 1.1" msgstr "" #. Tag: entry -#: hardware.xml:105 +#: hardware.xml:103 #, no-c-format msgid "<entry>32</entry>" msgstr "" #. Tag: entry -#: hardware.xml:107 +#: hardware.xml:105 #, no-c-format msgid "PA-RISC 2.0" msgstr "" #. Tag: entry -#: hardware.xml:108 +#: hardware.xml:106 #, no-c-format msgid "<entry>64</entry>" msgstr "" #. Tag: entry -#: hardware.xml:112 +#: hardware.xml:110 #, no-c-format msgid "Intel IA-64" msgstr "" #. Tag: entry -#: hardware.xml:113 +#: hardware.xml:111 #, no-c-format msgid "ia64" msgstr "" #. Tag: entry -#: hardware.xml:119 +#: hardware.xml:117 #, no-c-format msgid "MIPS (big endian)" msgstr "" #. Tag: entry -#: hardware.xml:120 +#: hardware.xml:118 #, no-c-format msgid "mips" msgstr "" #. Tag: entry -#: hardware.xml:121 +#: hardware.xml:119 #, no-c-format msgid "SGI IP22 (Indy/Indigo 2)" msgstr "" #. Tag: entry -#: hardware.xml:122 +#: hardware.xml:120 #, no-c-format msgid "r4k-ip22" msgstr "" #. Tag: entry -#: hardware.xml:124 +#: hardware.xml:122 #, no-c-format msgid "SGI IP32 (O2)" msgstr "" #. Tag: entry -#: hardware.xml:125 +#: hardware.xml:123 #, no-c-format msgid "r5k-ip32" msgstr "" #. Tag: entry -#: hardware.xml:127 hardware.xml:146 +#: hardware.xml:125 hardware.xml:144 #, no-c-format msgid "MIPS Malta (32 bit)" msgstr "" #. Tag: entry -#: hardware.xml:128 hardware.xml:147 +#: hardware.xml:126 hardware.xml:145 #, no-c-format msgid "4kc-malta" msgstr "" #. Tag: entry -#: hardware.xml:130 hardware.xml:149 +#: hardware.xml:128 hardware.xml:147 #, no-c-format msgid "MIPS Malta (64 bit)" msgstr "" #. Tag: entry -#: hardware.xml:131 hardware.xml:150 +#: hardware.xml:129 hardware.xml:148 #, no-c-format msgid "5kc-malta" msgstr "" #. Tag: entry -#: hardware.xml:133 hardware.xml:152 +#: hardware.xml:131 hardware.xml:150 #, no-c-format msgid "Broadcom BCM91250A (SWARM)" msgstr "" #. Tag: entry -#: hardware.xml:134 hardware.xml:153 +#: hardware.xml:132 hardware.xml:151 #, no-c-format msgid "sb1-bcm91250a" msgstr "" #. Tag: entry -#: hardware.xml:136 hardware.xml:155 +#: hardware.xml:134 hardware.xml:153 #, no-c-format msgid "Broadcom BCM91480B (BigSur)" msgstr "" #. Tag: entry -#: hardware.xml:137 hardware.xml:156 +#: hardware.xml:135 hardware.xml:154 #, no-c-format msgid "sb1a-bcm91480b" msgstr "" #. Tag: entry -#: hardware.xml:141 +#: hardware.xml:139 #, no-c-format msgid "MIPS (little endian)" msgstr "" #. Tag: entry -#: hardware.xml:142 +#: hardware.xml:140 #, no-c-format msgid "mipsel" msgstr "" #. Tag: entry -#: hardware.xml:143 +#: hardware.xml:141 #, no-c-format msgid "Cobalt" msgstr "" #. Tag: entry -#: hardware.xml:144 +#: hardware.xml:142 #, no-c-format msgid "cobalt" msgstr "" #. Tag: entry -#: hardware.xml:160 +#: hardware.xml:158 #, no-c-format msgid "Motorola 680x0" msgstr "" #. Tag: entry -#: hardware.xml:161 +#: hardware.xml:159 #, no-c-format msgid "m68k" msgstr "" #. Tag: entry -#: hardware.xml:162 +#: hardware.xml:160 #, no-c-format msgid "Atari" msgstr "" #. Tag: entry -#: hardware.xml:163 +#: hardware.xml:161 #, no-c-format msgid "atari" msgstr "" #. Tag: entry -#: hardware.xml:165 +#: hardware.xml:163 #, no-c-format msgid "Amiga" msgstr "" #. Tag: entry -#: hardware.xml:166 +#: hardware.xml:164 #, no-c-format msgid "amiga" msgstr "" #. Tag: entry -#: hardware.xml:168 +#: hardware.xml:166 #, no-c-format msgid "68k Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:169 +#: hardware.xml:167 #, no-c-format msgid "<entry>mac</entry>" msgstr "" #. Tag: entry -#: hardware.xml:171 +#: hardware.xml:169 #, no-c-format msgid "<entry>VME</entry>" msgstr "" #. Tag: entry -#: hardware.xml:172 +#: hardware.xml:170 #, no-c-format msgid "bvme6000" msgstr "" #. Tag: entry -#: hardware.xml:174 +#: hardware.xml:172 #, no-c-format msgid "mvme147" msgstr "" #. Tag: entry -#: hardware.xml:176 +#: hardware.xml:174 #, no-c-format msgid "mvme16x" msgstr "" #. Tag: entry -#: hardware.xml:180 +#: hardware.xml:178 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry -#: hardware.xml:181 +#: hardware.xml:179 #, no-c-format msgid "<entry>powerpc</entry>" msgstr "" #. Tag: entry -#: hardware.xml:182 +#: hardware.xml:180 #, no-c-format msgid "PowerMac" msgstr "" #. Tag: entry -#: hardware.xml:183 +#: hardware.xml:181 #, no-c-format msgid "pmac" msgstr "" #. Tag: entry -#: hardware.xml:185 +#: hardware.xml:183 #, no-c-format msgid "PReP" msgstr "" #. Tag: entry -#: hardware.xml:186 +#: hardware.xml:184 #, no-c-format msgid "prep" msgstr "" #. Tag: entry -#: hardware.xml:190 +#: hardware.xml:188 #, no-c-format msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:191 +#: hardware.xml:189 #, no-c-format msgid "sparc" msgstr "" #. Tag: entry -#: hardware.xml:192 +#: hardware.xml:190 #, no-c-format msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:193 +#: hardware.xml:191 #, no-c-format msgid "sparc64" msgstr "" #. Tag: entry -#: hardware.xml:195 +#: hardware.xml:193 #, no-c-format msgid "<entry>sun4v</entry>" msgstr "" #. Tag: entry -#: hardware.xml:199 +#: hardware.xml:197 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:200 +#: hardware.xml:198 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:201 +#: hardware.xml:199 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:202 +#: hardware.xml:200 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:204 +#: hardware.xml:202 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:205 +#: hardware.xml:203 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:210 +#: hardware.xml:208 #, no-c-format msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." msgstr "" #. Tag: para -#: hardware.xml:218 +#: hardware.xml:216 #, no-c-format msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." msgstr "" #. Tag: title -#: hardware.xml:240 hardware.xml:699 hardware.xml:735 hardware.xml:839 hardware.xml:858 hardware.xml:940 hardware.xml:982 hardware.xml:1056 hardware.xml:1128 +#: hardware.xml:238 hardware.xml:697 hardware.xml:733 hardware.xml:837 hardware.xml:856 hardware.xml:938 hardware.xml:980 hardware.xml:1054 hardware.xml:1126 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:241 +#: hardware.xml:239 #, no-c-format msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks." msgstr "" #. Tag: para -#: hardware.xml:248 +#: hardware.xml:246 #, no-c-format msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system." msgstr "" #. Tag: para -#: hardware.xml:256 +#: hardware.xml:254 #, no-c-format msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:" msgstr "" #. Tag: entry -#: hardware.xml:273 +#: hardware.xml:271 #, no-c-format msgid "Hardware Type" msgstr "" #. Tag: entry -#: hardware.xml:274 +#: hardware.xml:272 #, no-c-format msgid "Aliases" msgstr "" #. Tag: entry -#: hardware.xml:274 +#: hardware.xml:272 #, no-c-format msgid "MILO image" msgstr "" #. Tag: entry -#: hardware.xml:280 +#: hardware.xml:278 #, no-c-format msgid "ALCOR" msgstr "" #. Tag: entry -#: hardware.xml:281 +#: hardware.xml:279 #, no-c-format msgid "AlphaStation 500 5/266.300" msgstr "" #. Tag: entry -#: hardware.xml:282 +#: hardware.xml:280 #, no-c-format msgid "Maverick" msgstr "" #. Tag: entry -#: hardware.xml:283 hardware.xml:287 hardware.xml:291 +#: hardware.xml:281 hardware.xml:285 hardware.xml:289 #, no-c-format msgid "alcor" msgstr "" #. Tag: entry -#: hardware.xml:285 +#: hardware.xml:283 #, no-c-format msgid "AlphaStation 500 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:286 +#: hardware.xml:284 #, no-c-format msgid "Bret" msgstr "" #. Tag: entry -#: hardware.xml:289 +#: hardware.xml:287 #, no-c-format msgid "AlphaStation 600/266...300" msgstr "" #. Tag: entry -#: hardware.xml:290 +#: hardware.xml:288 #, no-c-format msgid "Alcor" msgstr "" #. Tag: entry -#: hardware.xml:293 +#: hardware.xml:291 #, no-c-format msgid "AlphaStation 600/300...433" msgstr "" #. Tag: entry -#: hardware.xml:294 +#: hardware.xml:292 #, no-c-format msgid "<entry>XLT</entry>" msgstr "" #. Tag: entry -#: hardware.xml:295 +#: hardware.xml:293 #, no-c-format msgid "<entry>xlt</entry>" msgstr "" #. Tag: entry -#: hardware.xml:299 +#: hardware.xml:297 #, no-c-format msgid "BOOK1" msgstr "" #. Tag: entry -#: hardware.xml:300 +#: hardware.xml:298 #, no-c-format msgid "AlphaBook1 (laptop)" msgstr "" #. Tag: entry -#: hardware.xml:301 +#: hardware.xml:299 #, no-c-format msgid "Alphabook1/Burns" msgstr "" #. Tag: entry -#: hardware.xml:302 +#: hardware.xml:300 #, no-c-format msgid "book1" msgstr "" #. Tag: entry -#: hardware.xml:306 +#: hardware.xml:304 #, no-c-format msgid "AVANTI" msgstr "" #. Tag: entry -#: hardware.xml:307 +#: hardware.xml:305 #, no-c-format msgid "AlphaStation 200 4/100...166" msgstr "" #. Tag: entry -#: hardware.xml:308 +#: hardware.xml:306 #, no-c-format msgid "Mustang" msgstr "" #. Tag: entry -#: hardware.xml:309 hardware.xml:313 hardware.xml:317 hardware.xml:321 hardware.xml:325 hardware.xml:329 hardware.xml:333 hardware.xml:337 +#: hardware.xml:307 hardware.xml:311 hardware.xml:315 hardware.xml:319 hardware.xml:323 hardware.xml:327 hardware.xml:331 hardware.xml:335 #, no-c-format msgid "avanti" msgstr "" #. Tag: entry -#: hardware.xml:311 +#: hardware.xml:309 #, no-c-format msgid "AlphaStation 200 4/233" msgstr "" #. Tag: entry -#: hardware.xml:312 +#: hardware.xml:310 #, no-c-format msgid "Mustang+" msgstr "" #. Tag: entry -#: hardware.xml:315 +#: hardware.xml:313 #, no-c-format msgid "AlphaStation 205 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:316 +#: hardware.xml:314 #, no-c-format msgid "<entry>LX3</entry>" msgstr "" #. Tag: entry -#: hardware.xml:319 +#: hardware.xml:317 #, no-c-format msgid "AlphaStation 250 4/300" msgstr "" #. Tag: entry -#: hardware.xml:320 +#: hardware.xml:318 #, no-c-format msgid "<entry>M3+</entry>" msgstr "" #. Tag: entry -#: hardware.xml:323 +#: hardware.xml:321 #, no-c-format msgid "AlphaStation 255 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:324 +#: hardware.xml:322 #, no-c-format msgid "LX3+" msgstr "" #. Tag: entry -#: hardware.xml:327 +#: hardware.xml:325 #, no-c-format msgid "AlphaStation 300 4/266" msgstr "" #. Tag: entry -#: hardware.xml:328 +#: hardware.xml:326 #, no-c-format msgid "Melmac" msgstr "" #. Tag: entry -#: hardware.xml:331 +#: hardware.xml:329 #, no-c-format msgid "AlphaStation 400 4/166" msgstr "" #. Tag: entry -#: hardware.xml:332 +#: hardware.xml:330 #, no-c-format msgid "Chinet" msgstr "" #. Tag: entry -#: hardware.xml:335 +#: hardware.xml:333 #, no-c-format msgid "AlphaStation 400 4/233...300" msgstr "" #. Tag: entry -#: hardware.xml:336 +#: hardware.xml:334 #, no-c-format msgid "Avanti" msgstr "" #. Tag: entry -#: hardware.xml:341 hardware.xml:354 hardware.xml:355 +#: hardware.xml:339 hardware.xml:352 hardware.xml:353 #, no-c-format msgid "EB164" msgstr "" #. Tag: entry -#: hardware.xml:342 +#: hardware.xml:340 #, no-c-format msgid "AlphaPC164" msgstr "" #. Tag: entry -#: hardware.xml:343 +#: hardware.xml:341 #, no-c-format msgid "PC164" msgstr "" #. Tag: entry -#: hardware.xml:344 +#: hardware.xml:342 #, no-c-format msgid "pc164" msgstr "" #. Tag: entry -#: hardware.xml:346 +#: hardware.xml:344 #, no-c-format msgid "AlphaPC164-LX" msgstr "" #. Tag: entry -#: hardware.xml:347 +#: hardware.xml:345 #, no-c-format msgid "LX164" msgstr "" #. Tag: entry -#: hardware.xml:348 +#: hardware.xml:346 #, no-c-format msgid "lx164" msgstr "" #. Tag: entry -#: hardware.xml:350 +#: hardware.xml:348 #, no-c-format msgid "AlphaPC164-SX" msgstr "" #. Tag: entry -#: hardware.xml:351 +#: hardware.xml:349 #, no-c-format msgid "SX164" msgstr "" #. Tag: entry -#: hardware.xml:352 +#: hardware.xml:350 #, no-c-format msgid "sx164" msgstr "" #. Tag: entry -#: hardware.xml:356 +#: hardware.xml:354 #, no-c-format msgid "eb164" msgstr "" #. Tag: entry -#: hardware.xml:360 hardware.xml:369 hardware.xml:370 +#: hardware.xml:358 hardware.xml:367 hardware.xml:368 #, no-c-format msgid "EB64+" msgstr "" #. Tag: entry -#: hardware.xml:361 +#: hardware.xml:359 #, no-c-format msgid "AlphaPC64" msgstr "" #. Tag: entry -#: hardware.xml:362 hardware.xml:366 +#: hardware.xml:360 hardware.xml:364 #, no-c-format msgid "Cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:363 hardware.xml:367 +#: hardware.xml:361 hardware.xml:365 #, no-c-format msgid "cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:365 +#: hardware.xml:363 #, no-c-format msgid "AlphaPCI64" msgstr "" #. Tag: entry -#: hardware.xml:371 +#: hardware.xml:369 #, no-c-format msgid "eb64p" msgstr "" #. Tag: entry -#: hardware.xml:375 hardware.xml:376 hardware.xml:377 +#: hardware.xml:373 hardware.xml:374 hardware.xml:375 #, no-c-format msgid "EB66" msgstr "" #. Tag: entry -#: hardware.xml:378 +#: hardware.xml:376 #, no-c-format msgid "eb66" msgstr "" #. Tag: entry -#: hardware.xml:380 hardware.xml:381 +#: hardware.xml:378 hardware.xml:379 #, no-c-format msgid "EB66+" msgstr "" #. Tag: entry -#: hardware.xml:382 +#: hardware.xml:380 #, no-c-format msgid "eb66p" msgstr "" #. Tag: entry -#: hardware.xml:386 +#: hardware.xml:384 #, no-c-format msgid "JENSEN" msgstr "" #. Tag: entry -#: hardware.xml:387 +#: hardware.xml:385 #, no-c-format msgid "DEC 2000 Model 300(S)" msgstr "" #. Tag: entry -#: hardware.xml:388 hardware.xml:396 +#: hardware.xml:386 hardware.xml:394 #, no-c-format msgid "Jensen" msgstr "" #. Tag: entry -#: hardware.xml:389 hardware.xml:393 hardware.xml:397 hardware.xml:458 hardware.xml:462 hardware.xml:480 hardware.xml:484 hardware.xml:488 hardware.xml:492 hardware.xml:496 hardware.xml:500 hardware.xml:504 hardware.xml:518 hardware.xml:522 hardware.xml:526 hardware.xml:530 hardware.xml:534 hardware.xml:568 hardware.xml:572 hardware.xml:576 hardware.xml:580 hardware.xml:594 hardware.xml:598 hardware.xml:602 hardware.xml:606 hardware.xml:613 hardware.xml:617 hardware.xml:621 hardware.xml:625 hardware.xml:629 hardware.xml:633 hardware.xml:637 hardware.xml:641 hardware.xml:645 hardware.xml:649 hardware.xml:653 hardware.xml:657 hardware.xml:661 hardware.xml:668 hardware.xml:672 +#: hardware.xml:387 hardware.xml:391 hardware.xml:395 hardware.xml:456 hardware.xml:460 hardware.xml:478 hardware.xml:482 hardware.xml:486 hardware.xml:490 hardware.xml:494 hardware.xml:498 hardware.xml:502 hardware.xml:516 hardware.xml:520 hardware.xml:524 hardware.xml:528 hardware.xml:532 hardware.xml:566 hardware.xml:570 hardware.xml:574 hardware.xml:578 hardware.xml:592 hardware.xml:596 hardware.xml:600 hardware.xml:604 hardware.xml:611 hardware.xml:615 hardware.xml:619 hardware.xml:623 hardware.xml:627 hardware.xml:631 hardware.xml:635 hardware.xml:639 hardware.xml:643 hardware.xml:647 hardware.xml:651 hardware.xml:655 hardware.xml:659 hardware.xml:666 hardware.xml:670 #, no-c-format msgid "<entry>N/A</entry>" msgstr "" #. Tag: entry -#: hardware.xml:391 +#: hardware.xml:389 #, no-c-format msgid "DEC 2000 Model 500" msgstr "" #. Tag: entry -#: hardware.xml:392 +#: hardware.xml:390 #, no-c-format msgid "Culzen" msgstr "" #. Tag: entry -#: hardware.xml:395 +#: hardware.xml:393 #, no-c-format msgid "DECpc 150" msgstr "" #. Tag: entry -#: hardware.xml:401 +#: hardware.xml:399 #, no-c-format msgid "MIATA" msgstr "" #. Tag: entry -#: hardware.xml:402 +#: hardware.xml:400 #, no-c-format msgid "Personal WorkStation 433a" msgstr "" #. Tag: entry -#: hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 hardware.xml:427 hardware.xml:431 +#: hardware.xml:401 hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 hardware.xml:429 #, no-c-format msgid "Miata" msgstr "" #. Tag: entry -#: hardware.xml:404 hardware.xml:408 hardware.xml:412 hardware.xml:416 hardware.xml:420 hardware.xml:424 hardware.xml:428 hardware.xml:432 +#: hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 hardware.xml:426 hardware.xml:430 #, no-c-format msgid "miata" msgstr "" #. Tag: entry -#: hardware.xml:406 +#: hardware.xml:404 #, no-c-format msgid "Personal WorkStation 433au" msgstr "" #. Tag: entry -#: hardware.xml:410 +#: hardware.xml:408 #, no-c-format msgid "Personal WorkStation 466au" msgstr "" #. Tag: entry -#: hardware.xml:414 +#: hardware.xml:412 #, no-c-format msgid "Personal WorkStation 500a" msgstr "" #. Tag: entry -#: hardware.xml:418 +#: hardware.xml:416 #, no-c-format msgid "Personal WorkStation 500au" msgstr "" #. Tag: entry -#: hardware.xml:422 +#: hardware.xml:420 #, no-c-format msgid "Personal WorkStation 550au" msgstr "" #. Tag: entry -#: hardware.xml:426 +#: hardware.xml:424 #, no-c-format msgid "Personal WorkStation 600a" msgstr "" #. Tag: entry -#: hardware.xml:430 +#: hardware.xml:428 #, no-c-format msgid "Personal WorkStation 600au" msgstr "" #. Tag: entry -#: hardware.xml:436 +#: hardware.xml:434 #, no-c-format msgid "MIKASA" msgstr "" #. Tag: entry -#: hardware.xml:437 +#: hardware.xml:435 #, no-c-format msgid "AlphaServer 1000 4/200" msgstr "" #. Tag: entry -#: hardware.xml:438 +#: hardware.xml:436 #, no-c-format msgid "Mikasa" msgstr "" #. Tag: entry -#: hardware.xml:439 hardware.xml:443 hardware.xml:447 hardware.xml:451 +#: hardware.xml:437 hardware.xml:441 hardware.xml:445 hardware.xml:449 #, no-c-format msgid "mikasa" msgstr "" #. Tag: entry -#: hardware.xml:441 +#: hardware.xml:439 #, no-c-format msgid "AlphaServer 1000 4/233..266" msgstr "" #. Tag: entry -#: hardware.xml:442 +#: hardware.xml:440 #, no-c-format msgid "Mikasa+" msgstr "" #. Tag: entry -#: hardware.xml:445 hardware.xml:449 +#: hardware.xml:443 hardware.xml:447 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "" #. Tag: entry -#: hardware.xml:446 +#: hardware.xml:444 #, no-c-format msgid "Mikasa-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:450 +#: hardware.xml:448 #, no-c-format msgid "Mikasa-Primo" msgstr "" #. Tag: entry -#: hardware.xml:455 +#: hardware.xml:453 #, no-c-format msgid "NAUTILUS" msgstr "" #. Tag: entry -#: hardware.xml:456 +#: hardware.xml:454 #, no-c-format msgid "UP1000" msgstr "" #. Tag: entry -#: hardware.xml:457 +#: hardware.xml:455 #, no-c-format msgid "Nautilus" msgstr "" #. Tag: entry -#: hardware.xml:460 +#: hardware.xml:458 #, no-c-format msgid "UP1100" msgstr "" #. Tag: entry -#: hardware.xml:461 +#: hardware.xml:459 #, no-c-format msgid "Galaxy-Train/Nautilus Jr." msgstr "" #. Tag: entry -#: hardware.xml:466 +#: hardware.xml:464 #, no-c-format msgid "NONAME" msgstr "" #. Tag: entry -#: hardware.xml:467 +#: hardware.xml:465 #, no-c-format msgid "AXPpci33" msgstr "" #. Tag: entry -#: hardware.xml:468 +#: hardware.xml:466 #, no-c-format msgid "Noname" msgstr "" #. Tag: entry -#: hardware.xml:469 hardware.xml:473 +#: hardware.xml:467 hardware.xml:471 #, no-c-format msgid "noname" msgstr "" #. Tag: entry -#: hardware.xml:471 +#: hardware.xml:469 #, no-c-format msgid "<entry>UDB</entry>" msgstr "" #. Tag: entry -#: hardware.xml:472 +#: hardware.xml:470 #, no-c-format msgid "Multia" msgstr "" #. Tag: entry -#: hardware.xml:477 +#: hardware.xml:475 #, no-c-format msgid "NORITAKE" msgstr "" #. Tag: entry -#: hardware.xml:478 +#: hardware.xml:476 #, no-c-format msgid "AlphaServer 1000A 4/233...266" msgstr "" #. Tag: entry -#: hardware.xml:479 +#: hardware.xml:477 #, no-c-format msgid "Noritake" msgstr "" #. Tag: entry -#: hardware.xml:482 +#: hardware.xml:480 #, no-c-format msgid "AlphaServer 1000A 5/300" msgstr "" #. Tag: entry -#: hardware.xml:483 +#: hardware.xml:481 #, no-c-format msgid "Noritake-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:486 +#: hardware.xml:484 #, no-c-format msgid "AlphaServer 1000A 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:487 +#: hardware.xml:485 #, no-c-format msgid "Noritake-Primo" msgstr "" #. Tag: entry -#: hardware.xml:490 +#: hardware.xml:488 #, no-c-format msgid "AlphaServer 800 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:491 hardware.xml:499 hardware.xml:503 +#: hardware.xml:489 hardware.xml:497 hardware.xml:501 #, no-c-format msgid "Corelle" msgstr "" #. Tag: entry -#: hardware.xml:494 +#: hardware.xml:492 #, no-c-format msgid "AlphaStation 600 A" msgstr "" #. Tag: entry -#: hardware.xml:495 +#: hardware.xml:493 #, no-c-format msgid "Alcor-Primo" msgstr "" #. Tag: entry -#: hardware.xml:498 +#: hardware.xml:496 #, no-c-format msgid "Digital Server 3300" msgstr "" #. Tag: entry -#: hardware.xml:502 +#: hardware.xml:500 #, no-c-format msgid "Digital Server 3300R" msgstr "" #. Tag: entry -#: hardware.xml:508 +#: hardware.xml:506 #, no-c-format msgid "PLATFORM 2000" msgstr "" #. Tag: entry -#: hardware.xml:509 hardware.xml:510 +#: hardware.xml:507 hardware.xml:508 #, no-c-format msgid "<entry>P2K</entry>" msgstr "" #. Tag: entry -#: hardware.xml:511 +#: hardware.xml:509 #, no-c-format msgid "<entry>p2k</entry>" msgstr "" #. Tag: entry -#: hardware.xml:515 +#: hardware.xml:513 #, no-c-format msgid "RAWHIDE" msgstr "" #. Tag: entry -#: hardware.xml:516 +#: hardware.xml:514 #, no-c-format msgid "AlphaServer 1200 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:517 hardware.xml:529 +#: hardware.xml:515 hardware.xml:527 #, no-c-format msgid "Tincup/DaVinci" msgstr "" #. Tag: entry -#: hardware.xml:520 +#: hardware.xml:518 #, no-c-format msgid "AlphaServer 4000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:521 +#: hardware.xml:519 #, no-c-format msgid "Wrangler/Durango" msgstr "" #. Tag: entry -#: hardware.xml:524 +#: hardware.xml:522 #, no-c-format msgid "AlphaServer 4100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:525 hardware.xml:533 +#: hardware.xml:523 hardware.xml:531 #, no-c-format msgid "Dodge" msgstr "" #. Tag: entry -#: hardware.xml:528 +#: hardware.xml:526 #, no-c-format msgid "Digital Server 5300" msgstr "" #. Tag: entry -#: hardware.xml:532 +#: hardware.xml:530 #, no-c-format msgid "Digital Server 7300" msgstr "" #. Tag: entry -#: hardware.xml:538 +#: hardware.xml:536 #, no-c-format msgid "RUFFIAN" msgstr "" #. Tag: entry -#: hardware.xml:539 +#: hardware.xml:537 #, no-c-format msgid "DeskStation AlphaPC164-UX" msgstr "" #. Tag: entry -#: hardware.xml:540 hardware.xml:544 hardware.xml:548 hardware.xml:552 hardware.xml:556 hardware.xml:560 +#: hardware.xml:538 hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 hardware.xml:558 #, no-c-format msgid "Ruffian" msgstr "" #. Tag: entry -#: hardware.xml:541 hardware.xml:545 hardware.xml:549 hardware.xml:553 hardware.xml:557 hardware.xml:561 +#: hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 hardware.xml:555 hardware.xml:559 #, no-c-format msgid "ruffian" msgstr "" #. Tag: entry -#: hardware.xml:543 +#: hardware.xml:541 #, no-c-format msgid "DeskStation RPL164-2" msgstr "" #. Tag: entry -#: hardware.xml:547 +#: hardware.xml:545 #, no-c-format msgid "DeskStation RPL164-4" msgstr "" #. Tag: entry -#: hardware.xml:551 +#: hardware.xml:549 #, no-c-format msgid "DeskStation RPX164-2" msgstr "" #. Tag: entry -#: hardware.xml:555 +#: hardware.xml:553 #, no-c-format msgid "DeskStation RPX164-4" msgstr "" #. Tag: entry -#: hardware.xml:559 +#: hardware.xml:557 #, no-c-format msgid "Samsung AlphaPC164-BX" msgstr "" #. Tag: entry -#: hardware.xml:565 +#: hardware.xml:563 #, no-c-format msgid "SABLE" msgstr "" #. Tag: entry -#: hardware.xml:566 +#: hardware.xml:564 #, no-c-format msgid "AlphaServer 2000 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:567 +#: hardware.xml:565 #, no-c-format msgid "Demi-Sable" msgstr "" #. Tag: entry -#: hardware.xml:570 +#: hardware.xml:568 #, no-c-format msgid "AlphaServer 2000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:571 +#: hardware.xml:569 #, no-c-format msgid "Demi-Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:574 +#: hardware.xml:572 #, no-c-format msgid "AlphaServer 2100 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:575 +#: hardware.xml:573 #, no-c-format msgid "Sable" msgstr "" #. Tag: entry -#: hardware.xml:578 +#: hardware.xml:576 #, no-c-format msgid "AlphaServer 2100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:579 +#: hardware.xml:577 #, no-c-format msgid "Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:584 +#: hardware.xml:582 #, no-c-format msgid "TAKARA" msgstr "" #. Tag: entry -#: hardware.xml:585 +#: hardware.xml:583 #, no-c-format msgid "21164 PICMG SBC" msgstr "" #. Tag: entry -#: hardware.xml:586 +#: hardware.xml:584 #, no-c-format msgid "Takara" msgstr "" #. Tag: entry -#: hardware.xml:587 +#: hardware.xml:585 #, no-c-format msgid "takara" msgstr "" #. Tag: entry -#: hardware.xml:591 +#: hardware.xml:589 #, no-c-format msgid "TITAN" msgstr "" #. Tag: entry -#: hardware.xml:592 +#: hardware.xml:590 #, no-c-format msgid "AlphaServer DS15" msgstr "" #. Tag: entry -#: hardware.xml:593 +#: hardware.xml:591 #, no-c-format msgid "HyperBrick2" msgstr "" #. Tag: entry -#: hardware.xml:596 +#: hardware.xml:594 #, no-c-format msgid "AlphaServer DS25" msgstr "" #. Tag: entry -#: hardware.xml:597 +#: hardware.xml:595 #, no-c-format msgid "Granite" msgstr "" #. Tag: entry -#: hardware.xml:600 +#: hardware.xml:598 #, no-c-format msgid "AlphaServer ES45" msgstr "" #. Tag: entry -#: hardware.xml:601 +#: hardware.xml:599 #, no-c-format msgid "Privateer" msgstr "" #. Tag: entry -#: hardware.xml:604 hardware.xml:643 hardware.xml:647 +#: hardware.xml:602 hardware.xml:641 hardware.xml:645 #, no-c-format msgid "UNKNOWN" msgstr "" #. Tag: entry -#: hardware.xml:605 +#: hardware.xml:603 #, no-c-format msgid "Yukon" msgstr "" #. Tag: entry -#: hardware.xml:610 +#: hardware.xml:608 #, no-c-format msgid "TSUNAMI" msgstr "" #. Tag: entry -#: hardware.xml:611 +#: hardware.xml:609 #, no-c-format msgid "AlphaServer DS10" msgstr "" #. Tag: entry -#: hardware.xml:612 hardware.xml:660 +#: hardware.xml:610 hardware.xml:658 #, no-c-format msgid "Webbrick" msgstr "" #. Tag: entry -#: hardware.xml:615 +#: hardware.xml:613 #, no-c-format msgid "AlphaServer DS10L" msgstr "" #. Tag: entry -#: hardware.xml:616 +#: hardware.xml:614 #, no-c-format msgid "Slate" msgstr "" #. Tag: entry -#: hardware.xml:619 +#: hardware.xml:617 #, no-c-format msgid "AlphaServer DS20" msgstr "" #. Tag: entry -#: hardware.xml:620 +#: hardware.xml:618 #, no-c-format msgid "Catamaran/Goldrush" msgstr "" #. Tag: entry -#: hardware.xml:623 +#: hardware.xml:621 #, no-c-format msgid "AlphaServer DS20E" msgstr "" #. Tag: entry -#: hardware.xml:624 +#: hardware.xml:622 #, no-c-format msgid "Goldrack" msgstr "" #. Tag: entry -#: hardware.xml:627 +#: hardware.xml:625 #, no-c-format msgid "AlphaServer DS20L" msgstr "" #. Tag: entry -#: hardware.xml:628 +#: hardware.xml:626 #, no-c-format msgid "Shark" msgstr "" #. Tag: entry -#: hardware.xml:631 +#: hardware.xml:629 #, no-c-format msgid "AlphaServer ES40" msgstr "" #. Tag: entry -#: hardware.xml:632 +#: hardware.xml:630 #, no-c-format msgid "Clipper" msgstr "" #. Tag: entry -#: hardware.xml:635 hardware.xml:636 +#: hardware.xml:633 hardware.xml:634 #, no-c-format msgid "DP264" msgstr "" #. Tag: entry -#: hardware.xml:639 +#: hardware.xml:637 #, no-c-format msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "" #. Tag: entry -#: hardware.xml:640 +#: hardware.xml:638 #, no-c-format msgid "Eiger" msgstr "" #. Tag: entry -#: hardware.xml:644 +#: hardware.xml:642 #, no-c-format msgid "Warhol" msgstr "" #. Tag: entry -#: hardware.xml:648 +#: hardware.xml:646 #, no-c-format msgid "Windjammer" msgstr "" #. Tag: entry -#: hardware.xml:651 +#: hardware.xml:649 #, no-c-format msgid "UP2000" msgstr "" #. Tag: entry -#: hardware.xml:652 +#: hardware.xml:650 #, no-c-format msgid "Swordfish" msgstr "" #. Tag: entry -#: hardware.xml:655 +#: hardware.xml:653 #, no-c-format msgid "XP1000" msgstr "" #. Tag: entry -#: hardware.xml:656 +#: hardware.xml:654 #, no-c-format msgid "Monet/Brisbane" msgstr "" #. Tag: entry -#: hardware.xml:659 +#: hardware.xml:657 #, no-c-format msgid "XP900" msgstr "" #. Tag: entry -#: hardware.xml:665 +#: hardware.xml:663 #, no-c-format msgid "WILDFIRE" msgstr "" #. Tag: entry -#: hardware.xml:666 +#: hardware.xml:664 #, no-c-format msgid "AlphaServer GS160" msgstr "" #. Tag: entry -#: hardware.xml:667 hardware.xml:671 +#: hardware.xml:665 hardware.xml:669 #, no-c-format msgid "Wildfire" msgstr "" #. Tag: entry -#: hardware.xml:670 +#: hardware.xml:668 #, no-c-format msgid "AlphaServer GS320" msgstr "" #. Tag: entry -#: hardware.xml:676 hardware.xml:678 +#: hardware.xml:674 hardware.xml:676 #, no-c-format msgid "<entry>XL</entry>" msgstr "" #. Tag: entry -#: hardware.xml:677 +#: hardware.xml:675 #, no-c-format msgid "XL-233...266" msgstr "" #. Tag: entry -#: hardware.xml:679 +#: hardware.xml:677 #, no-c-format msgid "<entry>xl</entry>" msgstr "" #. Tag: para -#: hardware.xml:684 +#: hardware.xml:682 #, no-c-format msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options." msgstr "" #. Tag: para -#: hardware.xml:700 hardware.xml:859 +#: hardware.xml:698 hardware.xml:857 #, 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:708 hardware.xml:867 hardware.xml:1029 +#: hardware.xml:706 hardware.xml:865 hardware.xml:1027 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:709 +#: hardware.xml:707 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:737 +#: hardware.xml:735 #, no-c-format msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU." msgstr "" #. Tag: para -#: hardware.xml:746 +#: hardware.xml:744 #, no-c-format msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." msgstr "" #. Tag: para -#: hardware.xml:754 +#: hardware.xml:752 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:761 +#: hardware.xml:759 #, no-c-format -msgid "Netwinder" +msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:762 +#: hardware.xml:760 #, no-c-format -msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." +msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." msgstr "" #. Tag: term -#: hardware.xml:775 +#: hardware.xml:773 #, no-c-format -msgid "IOP32x" +msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:776 +#: hardware.xml:774 #, no-c-format -msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." +msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>." msgstr "" #. Tag: term -#: hardware.xml:789 +#: hardware.xml:788 #, no-c-format -msgid "IXP4xx" +msgid "Kirkwood" msgstr "" #. Tag: para -#: hardware.xml:790 +#: hardware.xml:789 #, no-c-format -msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>." +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: <ulink url=\"&url-arm-cyrius-sheevaplug;\">SheevaPlug</ulink> and <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-119 and TS-219)." msgstr "" #. Tag: term -#: hardware.xml:804 +#: hardware.xml:802 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para -#: hardware.xml:805 +#: hardware.xml:803 #, 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-mv2120;\">HP mv2120</ulink>, <ulink url=\"&url-arm-cyrius-qnap;\">QNAP Turbo Station</ulink> (TS-109, TS-209 and TS-409)." msgstr "" #. Tag: term -#: hardware.xml:820 +#: hardware.xml:818 #, no-c-format msgid "<term>Versatile</term>" msgstr "" #. Tag: para -#: hardware.xml:821 +#: hardware.xml:819 #, no-c-format msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run Debian on ARM if you don't have the hardware." msgstr "" #. Tag: para -#: hardware.xml:840 +#: hardware.xml:838 #, no-c-format msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para -#: hardware.xml:868 +#: hardware.xml:866 #, 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:875 +#: hardware.xml:873 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: para -#: hardware.xml:908 +#: hardware.xml:906 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T 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:917 +#: hardware.xml:915 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:918 +#: hardware.xml:916 #, 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, 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:941 +#: hardware.xml:939 #, no-c-format msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." msgstr "" #. Tag: para -#: hardware.xml:948 +#: hardware.xml:946 #, no-c-format msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:956 +#: hardware.xml:954 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." msgstr "" #. Tag: para -#: hardware.xml:983 +#: hardware.xml:981 #, 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> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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:1030 +#: hardware.xml:1028 #, 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. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: para -#: hardware.xml:1040 +#: hardware.xml:1038 #, 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:1057 +#: hardware.xml:1055 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1098 +#: hardware.xml:1096 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1100 +#: hardware.xml:1098 #, no-c-format msgid "All MIPS based Cobalt machines are supported." msgstr "" #. Tag: para -#: hardware.xml:1104 +#: hardware.xml:1102 #, no-c-format msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: title -#: hardware.xml:1114 +#: hardware.xml:1112 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1115 +#: hardware.xml:1113 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1129 +#: hardware.xml:1127 #, no-c-format msgid "For &debian; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." msgstr "" #. Tag: title -#: hardware.xml:1150 +#: hardware.xml:1148 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1152 +#: hardware.xml:1150 #, no-c-format msgid "There are two flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1159 +#: hardware.xml:1157 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1160 +#: hardware.xml:1158 #, no-c-format msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term -#: hardware.xml:1170 +#: hardware.xml:1168 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1171 +#: hardware.xml:1169 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1175 +#: hardware.xml:1173 #, 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:1181 +#: hardware.xml:1179 #, 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:1186 +#: hardware.xml:1184 #, no-c-format msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: title -#: hardware.xml:1220 +#: hardware.xml:1218 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1222 +#: hardware.xml:1220 #, 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:1229 +#: hardware.xml:1227 #, 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:1237 +#: hardware.xml:1235 #, 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:1245 +#: hardware.xml:1243 #, 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:1261 hardware.xml:1396 hardware.xml:1440 hardware.xml:1469 +#: hardware.xml:1259 hardware.xml:1394 hardware.xml:1438 hardware.xml:1467 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1262 +#: hardware.xml:1260 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1268 +#: hardware.xml:1266 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1269 +#: hardware.xml:1267 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1270 hardware.xml:1273 hardware.xml:1276 hardware.xml:1279 hardware.xml:1282 hardware.xml:1285 hardware.xml:1288 hardware.xml:1291 hardware.xml:1294 hardware.xml:1297 hardware.xml:1300 hardware.xml:1303 hardware.xml:1306 hardware.xml:1309 hardware.xml:1312 hardware.xml:1315 +#: hardware.xml:1268 hardware.xml:1271 hardware.xml:1274 hardware.xml:1277 hardware.xml:1280 hardware.xml:1283 hardware.xml:1286 hardware.xml:1289 hardware.xml:1292 hardware.xml:1295 hardware.xml:1298 hardware.xml:1301 hardware.xml:1304 hardware.xml:1307 hardware.xml:1310 hardware.xml:1313 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1272 +#: hardware.xml:1270 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1275 +#: hardware.xml:1273 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1278 +#: hardware.xml:1276 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1281 +#: hardware.xml:1279 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1284 +#: hardware.xml:1282 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1287 +#: hardware.xml:1285 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1290 +#: hardware.xml:1288 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1293 +#: hardware.xml:1291 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1296 +#: hardware.xml:1294 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1299 +#: hardware.xml:1297 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1302 +#: hardware.xml:1300 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1305 +#: hardware.xml:1303 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1308 +#: hardware.xml:1306 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1311 +#: hardware.xml:1309 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1314 +#: hardware.xml:1312 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1317 +#: hardware.xml:1315 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1318 hardware.xml:1321 hardware.xml:1324 hardware.xml:1327 hardware.xml:1330 hardware.xml:1333 hardware.xml:1336 hardware.xml:1339 hardware.xml:1342 hardware.xml:1345 hardware.xml:1348 hardware.xml:1351 hardware.xml:1357 hardware.xml:1360 hardware.xml:1366 hardware.xml:1372 hardware.xml:1378 +#: hardware.xml:1316 hardware.xml:1319 hardware.xml:1322 hardware.xml:1325 hardware.xml:1328 hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1355 hardware.xml:1358 hardware.xml:1364 hardware.xml:1370 hardware.xml:1376 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1320 +#: hardware.xml:1318 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1323 +#: hardware.xml:1321 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1326 +#: hardware.xml:1324 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1329 +#: hardware.xml:1327 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1332 +#: hardware.xml:1330 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1335 +#: hardware.xml:1333 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1338 +#: hardware.xml:1336 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1341 +#: hardware.xml:1339 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1344 +#: hardware.xml:1342 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1347 +#: hardware.xml:1345 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1350 +#: hardware.xml:1348 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1355 +#: hardware.xml:1353 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1356 +#: hardware.xml:1354 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1359 +#: hardware.xml:1357 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1364 +#: hardware.xml:1362 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1365 +#: hardware.xml:1363 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1370 +#: hardware.xml:1368 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1371 +#: hardware.xml:1369 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1376 hardware.xml:1402 +#: hardware.xml:1374 hardware.xml:1400 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1377 +#: hardware.xml:1375 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1386 +#: hardware.xml:1384 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1403 +#: hardware.xml:1401 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1405 +#: hardware.xml:1403 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1407 +#: hardware.xml:1405 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1409 +#: hardware.xml:1407 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1411 +#: hardware.xml:1409 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1415 hardware.xml:1446 +#: hardware.xml:1413 hardware.xml:1444 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1416 +#: hardware.xml:1414 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1418 +#: hardware.xml:1416 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1420 +#: hardware.xml:1418 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1422 +#: hardware.xml:1420 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1430 +#: hardware.xml:1428 #, no-c-format msgid "CHRP subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:1447 +#: hardware.xml:1445 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1450 +#: hardware.xml:1448 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1451 +#: hardware.xml:1449 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1459 +#: hardware.xml:1457 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:1475 +#: hardware.xml:1473 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1476 +#: hardware.xml:1474 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1484 +#: hardware.xml:1482 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1486 +#: hardware.xml:1484 #, 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:1523 +#: hardware.xml:1521 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1525 +#: hardware.xml:1523 #, 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:1534 +#: hardware.xml:1532 #, 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:1542 +#: hardware.xml:1540 #, 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:1558 +#: hardware.xml:1556 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1559 +#: hardware.xml:1557 #, no-c-format msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" #. Tag: title -#: hardware.xml:1581 +#: hardware.xml:1579 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1582 +#: hardware.xml:1580 #, 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:1593 +#: hardware.xml:1591 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1595 +#: hardware.xml:1593 #, 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:1602 +#: hardware.xml:1600 #, 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:1612 +#: hardware.xml:1610 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1614 +#: hardware.xml:1612 #, 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:1627 +#: hardware.xml:1625 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1629 +#: hardware.xml:1627 #, 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:1640 +#: hardware.xml:1638 #, 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:1649 +#: hardware.xml:1647 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1650 +#: hardware.xml:1648 #, no-c-format msgid "Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may 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:1662 hardware.xml:1685 hardware.xml:1705 hardware.xml:1728 +#: hardware.xml:1660 hardware.xml:1683 hardware.xml:1703 hardware.xml:1726 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1663 +#: hardware.xml:1661 #, 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 SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable." msgstr "" #. Tag: para -#: hardware.xml:1672 +#: hardware.xml:1670 #, no-c-format msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1687 +#: hardware.xml:1685 #, 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:1696 +#: hardware.xml:1694 #, no-c-format msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1706 +#: hardware.xml:1704 #, 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 the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1715 +#: hardware.xml:1713 #, no-c-format msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <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." msgstr "" #. Tag: para -#: hardware.xml:1729 +#: hardware.xml:1727 #, 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:1739 +#: hardware.xml:1737 #, 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:1745 +#: hardware.xml:1743 #, no-c-format msgid "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <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." msgstr "" #. Tag: title -#: hardware.xml:1756 +#: hardware.xml:1754 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1757 +#: hardware.xml:1755 #, no-c-format msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" #. Tag: para -#: hardware.xml:1765 +#: hardware.xml:1763 #, no-c-format msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, 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:1774 +#: hardware.xml:1772 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1783 +#: hardware.xml:1781 #, no-c-format msgid "The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1790 +#: hardware.xml:1788 #, 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:1800 +#: hardware.xml:1798 #, 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:1822 +#: hardware.xml:1820 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1823 +#: hardware.xml:1821 #, no-c-format msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1835 +#: hardware.xml:1833 #, 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:1841 +#: hardware.xml:1839 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1846 +#: hardware.xml:1844 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1851 +#: hardware.xml:1849 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1856 +#: hardware.xml:1854 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1861 +#: hardware.xml:1859 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1868 +#: hardware.xml:1866 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1873 +#: hardware.xml:1871 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1878 +#: hardware.xml:1876 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1883 +#: hardware.xml:1881 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1892 +#: hardware.xml:1890 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1902 +#: hardware.xml:1900 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1909 +#: hardware.xml:1907 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1910 +#: hardware.xml:1908 #, no-c-format msgid "Wireless networking is in general supported as well and a growing number of wireless adapters is supported by the official Linux kernel, although many of them do require firmware to be loaded. Wireless NICs that are not supported by the official Linux kernel can generally be made to work under &debian;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:1918 +#: hardware.xml:1916 #, no-c-format msgid "The use of wireless networking during installation is still under development and whether it will work depends on the type of adaptor and the configuration of your wireless access point. If there is no other NIC you can use during the installation, it is still possible to install &debian; 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:1930 +#: hardware.xml:1928 #, 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:1944 +#: hardware.xml:1942 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1945 +#: hardware.xml:1943 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1952 +#: hardware.xml:1950 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1954 +#: hardware.xml:1952 #, 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:1964 +#: hardware.xml:1962 #, 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:1972 +#: hardware.xml:1970 #, 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:1985 +#: hardware.xml:1983 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1987 +#: hardware.xml:1985 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:2002 +#: hardware.xml:2000 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:2003 +#: hardware.xml:2001 #, 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; &release; ships with <classname>brltty</classname> version &brlttyver;." msgstr "" #. Tag: title -#: hardware.xml:2017 +#: hardware.xml:2015 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:2018 +#: hardware.xml:2016 #, 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 or serial-to-USB 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; &release; ships with <classname>speakup</classname> version &speakupver;." msgstr "" #. Tag: title -#: hardware.xml:2038 +#: hardware.xml:2036 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2039 +#: hardware.xml:2037 #, no-c-format msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:2045 +#: hardware.xml:2043 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2051 +#: hardware.xml:2049 #, no-c-format msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:2057 +#: hardware.xml:2055 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:2063 +#: hardware.xml:2061 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." msgstr "" #. Tag: para -#: hardware.xml:2069 +#: hardware.xml:2067 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:2083 +#: hardware.xml:2081 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2084 +#: hardware.xml:2082 #, 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." msgstr "" #. Tag: para -#: hardware.xml:2092 +#: hardware.xml:2090 #, no-c-format msgid "In most cases firmware is non-free according to the criteria used by the &debian; 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; 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:2101 +#: hardware.xml:2099 #, no-c-format msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." msgstr "" #. Tag: title -#: hardware.xml:2117 +#: hardware.xml:2115 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2119 +#: hardware.xml:2117 #, 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:2127 +#: hardware.xml:2125 #, no-c-format msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" #. Tag: para -#: hardware.xml:2132 +#: hardware.xml:2130 #, 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:2140 +#: hardware.xml:2138 #, no-c-format msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:2151 +#: hardware.xml:2149 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2152 +#: hardware.xml:2150 #, 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 Linux source code." msgstr "" #. Tag: para -#: hardware.xml:2159 +#: hardware.xml:2157 #, no-c-format msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" #. Tag: para -#: hardware.xml:2170 +#: hardware.xml:2168 #, no-c-format msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:2182 +#: hardware.xml:2180 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2183 +#: hardware.xml:2181 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:2196 +#: hardware.xml:2194 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2217 +#: hardware.xml:2215 #, no-c-format msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title -#: hardware.xml:2234 +#: hardware.xml:2232 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:2236 +#: hardware.xml:2234 #, no-c-format msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used 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:2247 +#: hardware.xml:2245 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:2248 +#: hardware.xml:2246 #, 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:2254 +#: hardware.xml:2252 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:2261 +#: hardware.xml:2259 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:2263 +#: hardware.xml:2261 #, no-c-format msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" #. Tag: para -#: hardware.xml:2270 +#: hardware.xml:2268 #, no-c-format msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." msgstr "" #. Tag: para -#: hardware.xml:2282 +#: hardware.xml:2280 #, no-c-format msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:2288 +#: hardware.xml:2286 #, no-c-format msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:2293 +#: hardware.xml:2291 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." msgstr "" #. Tag: para -#: hardware.xml:2302 +#: hardware.xml:2300 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:2306 +#: hardware.xml:2304 #, 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. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: title -#: hardware.xml:2324 +#: hardware.xml:2322 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2326 +#: hardware.xml:2324 #, 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." msgstr "" #. Tag: para -#: hardware.xml:2332 +#: hardware.xml:2330 #, no-c-format msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" #. Tag: para -#: hardware.xml:2337 +#: hardware.xml:2335 #, 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:2345 +#: hardware.xml:2343 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:2347 +#: hardware.xml:2345 #, no-c-format msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" #. Tag: title -#: hardware.xml:2359 +#: hardware.xml:2357 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:2361 +#: hardware.xml:2359 #, 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:2371 +#: hardware.xml:2369 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2377 +#: hardware.xml:2375 #, 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:2385 +#: hardware.xml:2383 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2387 +#: hardware.xml:2385 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian; 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\"/>." msgstr "" #. Tag: title -#: hardware.xml:2399 +#: hardware.xml:2397 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2401 +#: hardware.xml:2399 #, no-c-format msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:2411 +#: hardware.xml:2409 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, 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:2418 +#: hardware.xml:2416 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2426 +#: hardware.xml:2424 #, no-c-format msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." msgstr "" #. Tag: para -#: hardware.xml:2436 +#: hardware.xml:2434 #, 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:2469 +#: hardware.xml:2467 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" msgstr "" #. Tag: para -#: hardware.xml:2478 +#: hardware.xml:2476 #, 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:2484 +#: hardware.xml:2482 #, 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:2490 +#: hardware.xml:2488 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2495 +#: hardware.xml:2493 #, 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:2512 +#: hardware.xml:2510 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2514 +#: hardware.xml:2512 #, 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:2521 +#: hardware.xml:2519 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" #. Tag: para -#: hardware.xml:2538 +#: hardware.xml:2536 #, no-c-format msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" #. Tag: para -#: hardware.xml:2547 +#: hardware.xml:2545 #, no-c-format msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" #. Tag: para -#: hardware.xml:2555 +#: hardware.xml:2553 #, no-c-format msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" #. Tag: emphasis -#: hardware.xml:2565 +#: hardware.xml:2563 #, no-c-format msgid "FIXME: is this still true?" msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 507a95355..072d95889 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.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: 2009-02-18 01:09+0000\n" +"POT-Creation-Date: 2009-05-03 00:14+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" @@ -107,185 +107,161 @@ msgstr "" #. Tag: title #: install-methods.xml:151 #, no-c-format -msgid "Netwinder Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:152 -#, no-c-format -msgid "The easiest way to boot a Netwinder is over the network, using the supplied TFTP image &netwinder-boot-img;." -msgstr "" - -#. Tag: title -#: install-methods.xml:161 -#, no-c-format -msgid "CATS Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:162 -#, no-c-format -msgid "CATS can be booted either via the network or from CD-ROM. The kernel and initrd can be obtained from &cats-boot-img;." -msgstr "" - -#. Tag: title -#: install-methods.xml:171 -#, no-c-format msgid "NSLU2 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:172 +#: install-methods.xml:152 #, no-c-format msgid "A firmware image is provided for the Linksys NSLU2 which will automatically boot <classname>debian-installer</classname>. This image can be uploaded via the Linksys web frontend or with upslug2. This firmware image can be obtained from &nslu2-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:184 +#: install-methods.xml:164 #, no-c-format msgid "Thecus N2100 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:185 +#: install-methods.xml:165 #, no-c-format msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:196 +#: install-methods.xml:176 #, no-c-format msgid "GLAN Tank Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:197 +#: install-methods.xml:177 #, no-c-format msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install Debian. These images can be obtained from &glantank-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:207 +#: install-methods.xml:187 #, no-c-format msgid "Kurobox Pro Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:208 +#: install-methods.xml:188 #, no-c-format msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install Debian. These images can be obtained from &kuroboxpro-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:218 +#: install-methods.xml:198 #, no-c-format msgid "HP mv2120 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:219 +#: install-methods.xml:199 #, no-c-format msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:231 +#: install-methods.xml:211 #, no-c-format msgid "QNAP Turbo Station Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:232 +#: install-methods.xml:212 #, no-c-format msgid "The QNAP Turbo Station (TS-109, TS-209 and TS-409) requires a kernel and ramdisk which can be obtained from &qnap-firmware-img;. A script is provided to write these images to flash." msgstr "" #. Tag: title -#: install-methods.xml:278 +#: install-methods.xml:258 #, no-c-format msgid "Choosing a Kernel" msgstr "" #. Tag: para -#: install-methods.xml:280 +#: install-methods.xml:260 #, no-c-format msgid "Some m68k subarchs have a choice of kernels to install. In general we recommend trying the most recent version first. If your subarch or machine needs to use a 2.2.x kernel, make sure you choose one of the images that supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)." msgstr "" #. Tag: para -#: install-methods.xml:289 +#: install-methods.xml:269 #, no-c-format msgid "All of the m68k images for use with 2.2.x kernels, require the kernel parameter &ramdisksize;." msgstr "" #. Tag: title -#: install-methods.xml:307 +#: install-methods.xml:287 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para -#: install-methods.xml:309 +#: install-methods.xml:289 #, no-c-format msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>." msgstr "" #. Tag: title -#: install-methods.xml:333 +#: install-methods.xml:313 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:334 +#: install-methods.xml:314 #, no-c-format msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." msgstr "" #. Tag: para -#: install-methods.xml:339 +#: install-methods.xml:319 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:344 +#: install-methods.xml:324 #, no-c-format msgid "Booting the installer from floppy disk is not supported on Amigas or 68k Macs." msgstr "" #. Tag: para -#: install-methods.xml:349 +#: install-methods.xml:329 #, no-c-format msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." msgstr "" #. Tag: para -#: install-methods.xml:360 +#: install-methods.xml:340 #, no-c-format msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms." msgstr "" #. Tag: para -#: install-methods.xml:366 +#: install-methods.xml:346 #, no-c-format msgid "Before you can create the floppies, you will first need to download them from one of the Debian mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:374 +#: install-methods.xml:354 #, no-c-format msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." msgstr "" #. Tag: title -#: install-methods.xml:382 +#: install-methods.xml:362 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:383 +#: install-methods.xml:363 #, no-c-format msgid "" "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n" @@ -294,283 +270,283 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:404 +#: install-methods.xml:384 #, no-c-format msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" msgstr "" #. Tag: para -#: install-methods.xml:425 +#: install-methods.xml:405 #, no-c-format msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." msgstr "" #. Tag: title -#: install-methods.xml:443 +#: install-methods.xml:423 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:445 +#: install-methods.xml:425 #, no-c-format msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies." msgstr "" #. Tag: para -#: install-methods.xml:450 +#: install-methods.xml:430 #, no-c-format msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." msgstr "" #. Tag: para -#: install-methods.xml:458 +#: install-methods.xml:438 #, no-c-format msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." msgstr "" #. Tag: para -#: install-methods.xml:464 +#: install-methods.xml:444 #, no-c-format msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory." msgstr "" #. Tag: title -#: install-methods.xml:477 +#: install-methods.xml:457 #, no-c-format msgid "Writing Disk Images on Atari Systems" msgstr "" #. Tag: para -#: install-methods.xml:478 +#: install-methods.xml:458 #, no-c-format msgid "You'll find the &rawwrite.ttp; program in the same directory as the floppy disk images. Start the program by double clicking on the program icon, and type in the name of the floppy image file you want written to the floppy at the TOS program command line dialog box." msgstr "" #. Tag: title -#: install-methods.xml:489 +#: install-methods.xml:469 #, no-c-format msgid "Writing Disk Images on Macintosh Systems" msgstr "" #. Tag: para -#: install-methods.xml:490 +#: install-methods.xml:470 #, no-c-format msgid "Since the current release does not yet support booting from floppies to start the installation, there would be no point in doing this on Macintosh Systems. However, these files are needed for the installation of the operating system and modules, later in the process." msgstr "" #. Tag: title -#: install-methods.xml:506 +#: install-methods.xml:486 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:507 +#: install-methods.xml:487 #, no-c-format msgid "An AppleScript, <application>Make Debian Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." msgstr "" #. Tag: para -#: install-methods.xml:518 +#: install-methods.xml:498 #, no-c-format msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." msgstr "" #. Tag: title -#: install-methods.xml:529 +#: install-methods.xml:509 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:530 +#: install-methods.xml:510 #, no-c-format msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror." msgstr "" #. Tag: para -#: install-methods.xml:539 +#: install-methods.xml:519 #, no-c-format msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." msgstr "" #. Tag: para -#: install-methods.xml:546 +#: install-methods.xml:526 #, no-c-format msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." msgstr "" #. Tag: para -#: install-methods.xml:553 +#: install-methods.xml:533 #, no-c-format msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." msgstr "" #. Tag: para -#: install-methods.xml:562 +#: install-methods.xml:542 #, no-c-format msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." msgstr "" #. Tag: para -#: install-methods.xml:569 +#: install-methods.xml:549 #, no-c-format msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." msgstr "" #. Tag: title -#: install-methods.xml:584 +#: install-methods.xml:564 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:588 +#: install-methods.xml:568 #, no-c-format msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." msgstr "" #. Tag: para -#: install-methods.xml:596 +#: install-methods.xml:576 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:602 +#: install-methods.xml:582 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:607 +#: install-methods.xml:587 #, no-c-format msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." msgstr "" #. Tag: para -#: install-methods.xml:615 +#: install-methods.xml:595 #, no-c-format msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." msgstr "" #. Tag: title -#: install-methods.xml:634 +#: install-methods.xml:614 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:636 +#: install-methods.xml:616 #, no-c-format msgid "There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common." msgstr "" #. Tag: para -#: install-methods.xml:644 +#: install-methods.xml:624 #, no-c-format msgid "For the first installation method you'll need to download an installer image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>) and use the <quote>flexible way</quote> explained below to copy the files to the USB stick." msgstr "" #. Tag: para -#: install-methods.xml:652 +#: install-methods.xml:632 #, no-c-format msgid "Installation images for the second installation method can be found in the <filename>hd-media</filename> directory and either the <quote>easy way</quote> or the <quote>flexible way</quote> can be used to copy the image to the USB stick. For this installation method you will also need to download a CD image. The installation image and the CD image must be based on the same release of &d-i;. If they do not match you are likely to get errors<footnote> <para> The error message that is most likely to be displayed is that no kernel modules can be found. This means that the version of the kernel module udebs included on the CD image is different from the version of the running kernel. </para> </footnote> during the installation." msgstr "" #. Tag: para -#: install-methods.xml:671 +#: install-methods.xml:651 #, no-c-format msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch." msgstr "" #. Tag: para -#: install-methods.xml:685 +#: install-methods.xml:665 #, no-c-format msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." msgstr "" #. Tag: para -#: install-methods.xml:693 +#: install-methods.xml:673 #, no-c-format msgid "Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: title -#: install-methods.xml:701 +#: install-methods.xml:681 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para -#: install-methods.xml:702 +#: install-methods.xml:682 #, no-c-format msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file.</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:711 +#: install-methods.xml:691 #, no-c-format msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 256 MB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose. A second disadvantage is that you cannot copy a full CD image onto the USB stick, but only the smaller businesscard or netinst CD images." msgstr "" #. Tag: para -#: install-methods.xml:721 +#: install-methods.xml:701 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:725 +#: install-methods.xml:705 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:727 +#: install-methods.xml:707 #, no-c-format msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:" msgstr "" #. Tag: screen -#: install-methods.xml:733 +#: install-methods.xml:713 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:735 +#: install-methods.xml:715 #, no-c-format msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:752 +#: install-methods.xml:732 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:753 +#: install-methods.xml:733 #, no-c-format msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that — if the capacity of your USB stick is large enough — you have the option of copying a full CD ISO image to it." msgstr "" #. Tag: title -#: install-methods.xml:768 install-methods.xml:865 +#: install-methods.xml:748 install-methods.xml:845 #, no-c-format msgid "Partitioning the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:769 +#: install-methods.xml:749 #, no-c-format msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device." msgstr "" #. Tag: para -#: install-methods.xml:774 +#: install-methods.xml:754 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition, and then create the filesystem using: <informalexample><screen>\n" @@ -579,13 +555,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:788 +#: install-methods.xml:768 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:798 +#: install-methods.xml:778 #, no-c-format msgid "" "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n" @@ -594,19 +570,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:815 install-methods.xml:912 +#: install-methods.xml:795 install-methods.xml:892 #, no-c-format msgid "Adding the installer image" msgstr "" #. Tag: para -#: install-methods.xml:816 +#: install-methods.xml:796 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names." msgstr "" #. Tag: para -#: install-methods.xml:840 +#: install-methods.xml:820 #, no-c-format msgid "" "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines: <informalexample><screen>\n" @@ -616,13 +592,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:850 install-methods.xml:952 +#: install-methods.xml:830 install-methods.xml:932 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy a Debian ISO image (businesscard, netinst or full CD image; be sure to select one that fits) onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)." msgstr "" #. Tag: para -#: install-methods.xml:866 +#: install-methods.xml:846 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n" @@ -631,13 +607,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:883 +#: install-methods.xml:863 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:892 +#: install-methods.xml:872 #, no-c-format msgid "" "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n" @@ -650,37 +626,37 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:913 +#: install-methods.xml:893 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:" msgstr "" #. Tag: para -#: install-methods.xml:920 +#: install-methods.xml:900 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:925 +#: install-methods.xml:905 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:930 +#: install-methods.xml:910 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:935 +#: install-methods.xml:915 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:942 +#: install-methods.xml:922 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -698,259 +674,259 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:967 +#: install-methods.xml:947 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:968 +#: install-methods.xml:948 #, no-c-format msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" msgstr "" #. Tag: screen -#: install-methods.xml:975 +#: install-methods.xml:955 #, no-c-format msgid "# install-mbr /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:986 +#: install-methods.xml:966 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:987 +#: install-methods.xml:967 #, no-c-format msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para -#: install-methods.xml:993 +#: install-methods.xml:973 #, no-c-format msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" #. Tag: para -#: install-methods.xml:1000 +#: install-methods.xml:980 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para -#: install-methods.xml:1004 +#: install-methods.xml:984 #, no-c-format msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" #. Tag: para -#: install-methods.xml:1015 +#: install-methods.xml:995 #, no-c-format msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." msgstr "" #. Tag: title -#: install-methods.xml:1024 +#: install-methods.xml:1004 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:1026 +#: install-methods.xml:1006 #, no-c-format msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" #. Tag: para -#: install-methods.xml:1032 +#: install-methods.xml:1012 #, no-c-format msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" #. Tag: para -#: install-methods.xml:1038 +#: install-methods.xml:1018 #, no-c-format msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1045 +#: install-methods.xml:1025 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:1050 +#: install-methods.xml:1030 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:1057 +#: install-methods.xml:1037 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1067 +#: install-methods.xml:1047 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1068 +#: install-methods.xml:1048 #, no-c-format msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." msgstr "" #. Tag: para -#: install-methods.xml:1081 +#: install-methods.xml:1061 #, no-c-format msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." msgstr "" #. Tag: title -#: install-methods.xml:1101 +#: install-methods.xml:1081 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1102 +#: install-methods.xml:1082 #, no-c-format msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para -#: install-methods.xml:1113 +#: install-methods.xml:1093 #, no-c-format msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." msgstr "" #. Tag: filename -#: install-methods.xml:1123 install-methods.xml:1480 +#: install-methods.xml:1103 install-methods.xml:1460 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1128 install-methods.xml:1485 +#: install-methods.xml:1108 install-methods.xml:1465 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1133 install-methods.xml:1490 +#: install-methods.xml:1113 install-methods.xml:1470 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1138 install-methods.xml:1495 +#: install-methods.xml:1118 install-methods.xml:1475 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1143 +#: install-methods.xml:1123 #, no-c-format msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" #. Tag: para -#: install-methods.xml:1151 +#: install-methods.xml:1131 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1164 +#: install-methods.xml:1144 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1165 +#: install-methods.xml:1145 #, no-c-format msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" #. Tag: para -#: install-methods.xml:1173 +#: install-methods.xml:1153 #, no-c-format msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:1180 +#: install-methods.xml:1160 #, no-c-format msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> <phrase arch=\"m68k\">Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1197 +#: install-methods.xml:1177 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1203 +#: install-methods.xml:1183 #, no-c-format msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console." msgstr "" #. Tag: para -#: install-methods.xml:1220 +#: install-methods.xml:1200 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." msgstr "" #. Tag: para -#: install-methods.xml:1225 +#: install-methods.xml:1205 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1233 +#: install-methods.xml:1213 #, no-c-format msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." msgstr "" #. Tag: title -#: install-methods.xml:1251 +#: install-methods.xml:1231 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1252 +#: install-methods.xml:1232 #, no-c-format msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1264 +#: install-methods.xml:1244 #, no-c-format msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1286 +#: install-methods.xml:1266 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1287 +#: install-methods.xml:1267 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1295 +#: install-methods.xml:1275 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" @@ -967,25 +943,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1328 +#: install-methods.xml:1308 #, no-c-format msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. In that case, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1349 +#: install-methods.xml:1329 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1350 +#: install-methods.xml:1330 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1357 +#: install-methods.xml:1337 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -1010,25 +986,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1359 +#: install-methods.xml:1339 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1369 +#: install-methods.xml:1349 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1377 +#: install-methods.xml:1357 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1378 +#: install-methods.xml:1358 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -1063,13 +1039,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1394 +#: install-methods.xml:1374 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1395 +#: install-methods.xml:1375 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" @@ -1078,19 +1054,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1407 +#: install-methods.xml:1387 #, no-c-format msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1417 +#: install-methods.xml:1397 #, no-c-format msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> All <command>in.tftpd</command> alternatives available in Debian should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. </para> </footnote>; you'll need that below. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1437 +#: install-methods.xml:1417 #, no-c-format msgid "" "If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1101,61 +1077,61 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1459 +#: install-methods.xml:1439 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1460 +#: install-methods.xml:1440 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1469 +#: install-methods.xml:1449 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1500 +#: install-methods.xml:1480 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1505 +#: install-methods.xml:1485 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1513 +#: install-methods.xml:1493 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1525 +#: install-methods.xml:1505 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1526 +#: install-methods.xml:1506 #, no-c-format msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." msgstr "" #. Tag: title -#: install-methods.xml:1541 +#: install-methods.xml:1521 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1542 +#: install-methods.xml:1522 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1164,85 +1140,85 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1558 +#: install-methods.xml:1538 #, no-c-format msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1565 +#: install-methods.xml:1545 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1576 +#: install-methods.xml:1556 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1577 +#: install-methods.xml:1557 #, no-c-format msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1582 +#: install-methods.xml:1562 #, no-c-format msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information." msgstr "" #. Tag: title -#: install-methods.xml:1594 +#: install-methods.xml:1574 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1595 +#: install-methods.xml:1575 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1607 +#: install-methods.xml:1587 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1608 +#: install-methods.xml:1588 #, no-c-format msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to be loaded to CFE." msgstr "" #. Tag: title -#: install-methods.xml:1713 +#: install-methods.xml:1693 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1714 +#: install-methods.xml:1694 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" #. Tag: title -#: install-methods.xml:1727 +#: install-methods.xml:1707 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1728 +#: install-methods.xml:1708 #, no-c-format msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1735 +#: install-methods.xml:1715 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" |