diff options
| author | Frans Pop <elendil@planet.nl> | 2006-08-16 18:28:05 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-08-16 18:28:05 +0000 |
| commit | d7333d682363ac9bf3e739282ccfb174646d35a3 (patch) | |
| tree | 0008878b695d3500e28b53fe6e7db0ba73d4c4b2 /po/pot | |
| parent | 26f4fd170823498f310cfba4b90c89970ef02d66 (diff) | |
| download | installation-guide-d7333d682363ac9bf3e739282ccfb174646d35a3.zip | |
Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/hardware.pot | 844 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 4 | ||||
| -rw-r--r-- | po/pot/installation-howto.pot | 4 | ||||
| -rw-r--r-- | po/pot/post-install.pot | 4 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 194 |
5 files changed, 531 insertions, 519 deletions
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 9c131ec60..cdfc71440 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: 2006-07-25 21:39+0000\n" +"POT-Creation-Date: 2006-08-16 18:10+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" @@ -33,499 +33,493 @@ msgid "Supported Hardware" msgstr "" #. Tag: para -#: hardware.xml:22 +#: hardware.xml:21 #, no-c-format msgid "Debian does not impose hardware requirements beyond the requirements of the Linux kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux kernel, libc, <command>gcc</command>, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with Debian." msgstr "" #. Tag: para -#: hardware.xml:33 +#: hardware.xml:32 #, no-c-format msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found." msgstr "" #. Tag: title -#: hardware.xml:42 +#: hardware.xml:41 #, no-c-format msgid "Supported Architectures" msgstr "" #. Tag: para -#: hardware.xml:44 +#: hardware.xml:42 #, no-c-format msgid "Debian &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>." msgstr "" #. Tag: entry -#: hardware.xml:55 +#: hardware.xml:53 #, no-c-format msgid "Architecture" msgstr "" #. Tag: entry -#: hardware.xml:55 +#: hardware.xml:53 #, no-c-format msgid "Debian Designation" msgstr "" #. Tag: entry -#: hardware.xml:56 +#: hardware.xml:54 #, no-c-format msgid "Subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:56 +#: hardware.xml:54 #, no-c-format msgid "Flavor" msgstr "" #. Tag: entry -#: hardware.xml:62 +#: hardware.xml:60 #, no-c-format msgid "Intel x86-based" msgstr "" #. Tag: entry -#: hardware.xml:63 +#: hardware.xml:61 #, no-c-format msgid "i386" msgstr "" #. Tag: entry -#: hardware.xml:65 -#, no-c-format -msgid "vanilla" -msgstr "" - -#. Tag: entry #: hardware.xml:67 #, no-c-format -msgid "speakup" +msgid "AMD64 & Intel EM64t" msgstr "" #. Tag: entry -#: hardware.xml:69 +#: hardware.xml:68 #, no-c-format -msgid "linux26" -msgstr "" - -#. Tag: entry -#: hardware.xml:73 -#, no-c-format -msgid "Motorola 680x0" +msgid "amd64" msgstr "" #. Tag: entry #: hardware.xml:74 #, no-c-format -msgid "m68k" +msgid "DEC Alpha" msgstr "" #. Tag: entry #: hardware.xml:75 #, no-c-format -msgid "Atari" -msgstr "" - -#. Tag: entry -#: hardware.xml:76 -#, no-c-format -msgid "atari" -msgstr "" - -#. Tag: entry -#: hardware.xml:78 -#, no-c-format -msgid "Amiga" +msgid "alpha" msgstr "" #. Tag: entry -#: hardware.xml:79 +#: hardware.xml:81 #, no-c-format -msgid "amiga" +msgid "ARM and StrongARM" msgstr "" #. Tag: entry -#: hardware.xml:81 +#: hardware.xml:82 #, no-c-format -msgid "68k Macintosh" +msgid "<entry>arm</entry>" msgstr "" #. Tag: entry -#: hardware.xml:82 +#: hardware.xml:83 #, no-c-format -msgid "<entry>mac</entry>" +msgid "Netwinder and CATS" msgstr "" #. Tag: entry #: hardware.xml:84 #, no-c-format -msgid "<entry>VME</entry>" +msgid "netwinder" msgstr "" #. Tag: entry -#: hardware.xml:85 +#: hardware.xml:86 #, no-c-format -msgid "bvme6000" +msgid "Linksys NSLU2" msgstr "" #. Tag: entry #: hardware.xml:87 #, no-c-format -msgid "mvme147" +msgid "nslu2" msgstr "" #. Tag: entry #: hardware.xml:89 #, no-c-format -msgid "mvme16x" +msgid "<entry>RiscPC</entry>" msgstr "" #. Tag: entry -#: hardware.xml:93 +#: hardware.xml:90 #, no-c-format -msgid "DEC Alpha" +msgid "<entry>rpc</entry>" msgstr "" #. Tag: entry #: hardware.xml:94 #, no-c-format -msgid "alpha" +msgid "HP PA-RISC" msgstr "" #. Tag: entry -#: hardware.xml:100 +#: hardware.xml:95 #, no-c-format -msgid "Sun SPARC" +msgid "hppa" msgstr "" #. Tag: entry -#: hardware.xml:101 +#: hardware.xml:96 #, no-c-format -msgid "sparc" +msgid "PA-RISC 1.1" msgstr "" #. Tag: entry -#: hardware.xml:103 +#: hardware.xml:97 #, no-c-format -msgid "sun4cdm" +msgid "<entry>32</entry>" msgstr "" #. Tag: entry -#: hardware.xml:105 +#: hardware.xml:99 #, no-c-format -msgid "sun4u" +msgid "PA-RISC 2.0" msgstr "" #. Tag: entry -#: hardware.xml:109 +#: hardware.xml:100 #, no-c-format -msgid "ARM and StrongARM" +msgid "<entry>64</entry>" msgstr "" #. Tag: entry -#: hardware.xml:110 +#: hardware.xml:104 #, no-c-format -msgid "<entry>arm</entry>" +msgid "Intel ia64-based" +msgstr "" + +#. Tag: entry +#: hardware.xml:105 +#, no-c-format +msgid "ia64" msgstr "" #. Tag: entry #: hardware.xml:111 #, no-c-format -msgid "Netwinder and CATS" +msgid "MIPS (big endian)" msgstr "" #. Tag: entry #: hardware.xml:112 #, no-c-format -msgid "netwinder" +msgid "mips" msgstr "" #. Tag: entry -#: hardware.xml:114 +#: hardware.xml:113 #, no-c-format -msgid "Linksys NSLU2" +msgid "SGI IP22 (Indy/Indigo 2)" msgstr "" #. Tag: entry -#: hardware.xml:115 +#: hardware.xml:114 #, no-c-format -msgid "nslu2" +msgid "r4k-ip22" msgstr "" #. Tag: entry -#: hardware.xml:117 +#: hardware.xml:116 #, no-c-format -msgid "<entry>RiscPC</entry>" +msgid "SGI IP32 (O2)" msgstr "" #. Tag: entry -#: hardware.xml:118 +#: hardware.xml:117 #, no-c-format -msgid "<entry>rpc</entry>" +msgid "r5k-ip32" msgstr "" #. Tag: entry -#: hardware.xml:122 +#: hardware.xml:119 hardware.xml:137 #, no-c-format -msgid "IBM/Motorola PowerPC" +msgid "Broadcom BCM91250A (SWARM)" msgstr "" #. Tag: entry -#: hardware.xml:123 +#: hardware.xml:120 hardware.xml:138 #, no-c-format -msgid "<entry>powerpc</entry>" +msgid "sb1-bcm91250a" msgstr "" #. Tag: entry -#: hardware.xml:124 +#: hardware.xml:122 hardware.xml:140 #, no-c-format -msgid "CHRP" +msgid "Broadcom BCM91480B (BigSur)" msgstr "" #. Tag: entry -#: hardware.xml:125 +#: hardware.xml:123 hardware.xml:141 #, no-c-format -msgid "chrp" +msgid "sb1a-bcm91480b" msgstr "" #. Tag: entry #: hardware.xml:127 #, no-c-format -msgid "PowerMac" +msgid "MIPS (little endian)" msgstr "" #. Tag: entry #: hardware.xml:128 #, no-c-format -msgid "pmac" +msgid "mipsel" msgstr "" #. Tag: entry -#: hardware.xml:130 +#: hardware.xml:129 #, no-c-format -msgid "PReP" +msgid "Cobalt" msgstr "" #. Tag: entry -#: hardware.xml:131 +#: hardware.xml:130 #, no-c-format -msgid "<entry>prep</entry>" +msgid "cobalt" msgstr "" #. Tag: entry -#: hardware.xml:133 +#: hardware.xml:132 #, no-c-format -msgid "APUS" +msgid "DECstation" msgstr "" #. Tag: entry -#: hardware.xml:134 +#: hardware.xml:133 hardware.xml:1044 hardware.xml:1059 hardware.xml:1069 #, no-c-format -msgid "<entry>apus</entry>" +msgid "r4k-kn04" msgstr "" #. Tag: entry -#: hardware.xml:138 +#: hardware.xml:135 hardware.xml:1039 hardware.xml:1049 hardware.xml:1054 hardware.xml:1064 #, no-c-format -msgid "HP PA-RISC" +msgid "r3k-kn02" msgstr "" #. Tag: entry -#: hardware.xml:139 +#: hardware.xml:145 #, no-c-format -msgid "hppa" +msgid "Motorola 680x0" msgstr "" #. Tag: entry -#: hardware.xml:140 +#: hardware.xml:146 #, no-c-format -msgid "PA-RISC 1.1" +msgid "m68k" msgstr "" #. Tag: entry -#: hardware.xml:141 +#: hardware.xml:147 #, no-c-format -msgid "<entry>32</entry>" +msgid "Atari" msgstr "" #. Tag: entry -#: hardware.xml:143 +#: hardware.xml:148 #, no-c-format -msgid "PA-RISC 2.0" +msgid "atari" msgstr "" #. Tag: entry -#: hardware.xml:144 +#: hardware.xml:150 #, no-c-format -msgid "<entry>64</entry>" +msgid "Amiga" msgstr "" #. Tag: entry -#: hardware.xml:148 +#: hardware.xml:151 #, no-c-format -msgid "Intel ia64-based" +msgid "amiga" msgstr "" #. Tag: entry -#: hardware.xml:149 +#: hardware.xml:153 #, no-c-format -msgid "ia64" +msgid "68k Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:155 +#: hardware.xml:154 #, no-c-format -msgid "MIPS (big endian)" +msgid "<entry>mac</entry>" msgstr "" #. Tag: entry #: hardware.xml:156 #, no-c-format -msgid "mips" +msgid "<entry>VME</entry>" msgstr "" #. Tag: entry #: hardware.xml:157 #, no-c-format -msgid "SGI IP22 (Indy/Indigo 2)" +msgid "bvme6000" msgstr "" #. Tag: entry -#: hardware.xml:158 +#: hardware.xml:159 #, no-c-format -msgid "r4k-ip22" +msgid "mvme147" msgstr "" #. Tag: entry -#: hardware.xml:160 +#: hardware.xml:161 #, no-c-format -msgid "SGI IP32 (O2)" +msgid "mvme16x" msgstr "" #. Tag: entry -#: hardware.xml:161 +#: hardware.xml:165 #, no-c-format -msgid "r5k-ip32" +msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry -#: hardware.xml:163 hardware.xml:181 +#: hardware.xml:166 #, no-c-format -msgid "Broadcom BCM91250A (SWARM)" +msgid "<entry>powerpc</entry>" msgstr "" #. Tag: entry -#: hardware.xml:164 hardware.xml:182 +#: hardware.xml:167 #, no-c-format -msgid "sb1-bcm91250a" +msgid "CHRP" msgstr "" #. Tag: entry -#: hardware.xml:166 hardware.xml:184 +#: hardware.xml:168 #, no-c-format -msgid "Broadcom BCM91480B (BigSur)" +msgid "chrp" msgstr "" #. Tag: entry -#: hardware.xml:167 hardware.xml:185 +#: hardware.xml:170 #, no-c-format -msgid "sb1a-bcm91480b" +msgid "PowerMac" msgstr "" #. Tag: entry #: hardware.xml:171 #, no-c-format -msgid "MIPS (little endian)" +msgid "pmac" msgstr "" #. Tag: entry -#: hardware.xml:172 +#: hardware.xml:173 #, no-c-format -msgid "mipsel" +msgid "PReP" msgstr "" #. Tag: entry -#: hardware.xml:173 +#: hardware.xml:174 #, no-c-format -msgid "Cobalt" +msgid "<entry>prep</entry>" msgstr "" #. Tag: entry -#: hardware.xml:174 +#: hardware.xml:176 #, no-c-format -msgid "cobalt" +msgid "APUS" msgstr "" #. Tag: entry -#: hardware.xml:176 +#: hardware.xml:177 #, no-c-format -msgid "DECstation" +msgid "<entry>apus</entry>" msgstr "" #. Tag: entry -#: hardware.xml:177 hardware.xml:1008 hardware.xml:1023 hardware.xml:1033 +#: hardware.xml:181 #, no-c-format -msgid "r4k-kn04" +msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:179 hardware.xml:1003 hardware.xml:1013 hardware.xml:1018 hardware.xml:1028 +#: hardware.xml:182 #, no-c-format -msgid "r3k-kn02" +msgid "sparc" msgstr "" #. Tag: entry -#: hardware.xml:189 +#: hardware.xml:184 #, no-c-format -msgid "IBM S/390" +msgid "sun4cdm" +msgstr "" + +#. Tag: entry +#: hardware.xml:186 +#, no-c-format +msgid "sun4u" msgstr "" #. Tag: entry #: hardware.xml:190 #, no-c-format -msgid "s390" +msgid "IBM S/390" msgstr "" #. Tag: entry #: hardware.xml:191 #, no-c-format -msgid "IPL from VM-reader and DASD" +msgid "s390" msgstr "" #. Tag: entry #: hardware.xml:192 #, no-c-format +msgid "IPL from VM-reader and DASD" +msgstr "" + +#. Tag: entry +#: hardware.xml:193 +#, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:194 +#: hardware.xml:195 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:195 +#: hardware.xml:196 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:200 +#: hardware.xml:201 #, 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:208 +#: hardware.xml:209 #, 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:231 hardware.xml:690 hardware.xml:766 hardware.xml:785 hardware.xml:828 hardware.xml:870 hardware.xml:938 hardware.xml:1097 hardware.xml:1543 +#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:802 hardware.xml:821 hardware.xml:864 hardware.xml:906 hardware.xml:974 hardware.xml:1133 hardware.xml:1579 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" @@ -1641,283 +1635,289 @@ msgid "It is believed that Debian &releasename; supports installing on all alpha msgstr "" #. Tag: para -#: hardware.xml:692 +#: hardware.xml:691 hardware.xml:822 #, 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 systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale." +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:699 hardware.xml:830 hardware.xml:947 +#, no-c-format +msgid "<title>CPU</title>" msgstr "" #. Tag: para #: hardware.xml:700 #, no-c-format +msgid "Both AMD64 and Intel EM64t processors are supported." +msgstr "" + +#. Tag: para +#: hardware.xml:728 +#, 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 systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale." +msgstr "" + +#. Tag: para +#: hardware.xml:736 +#, 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:708 +#: hardware.xml:744 #, no-c-format msgid "The supported systems are:" msgstr "" #. Tag: term -#: hardware.xml:715 +#: hardware.xml:751 #, no-c-format msgid "Netwinder" msgstr "" #. Tag: para -#: hardware.xml:716 +#: hardware.xml:752 #, 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)." msgstr "" #. Tag: term -#: hardware.xml:729 +#: hardware.xml:765 #, no-c-format msgid "NSLU2" msgstr "" #. Tag: para -#: hardware.xml:730 +#: hardware.xml:766 #, no-c-format msgid "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." msgstr "" #. Tag: term -#: hardware.xml:741 +#: hardware.xml:777 #, no-c-format msgid "<term>RiscPC</term>" msgstr "" #. Tag: para -#: hardware.xml:742 +#: hardware.xml:778 #, no-c-format msgid "This machine is the oldest supported hardware: it was released in 1994. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." msgstr "" #. Tag: para -#: hardware.xml:767 +#: hardware.xml:803 #, no-c-format msgid "The 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:786 -#, 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:794 hardware.xml:911 -#, no-c-format -msgid "<title>CPU</title>" -msgstr "" - -#. Tag: para -#: hardware.xml:795 +#: hardware.xml:831 #, no-c-format msgid "Nearly all x86-based processors are supported; this includes AMD and VIA (former Cyrix) processors as well. Also the new processors like Athlon XP and Intel P4 Xeon are supported. However, Linux will <emphasis>not</emphasis> run on 286 or earlier processors." msgstr "" #. Tag: title -#: hardware.xml:805 +#: hardware.xml:841 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:806 +#: hardware.xml:842 #, 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, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus)." msgstr "" #. Tag: para -#: hardware.xml:829 +#: hardware.xml:865 #, 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:836 +#: hardware.xml:872 #, 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:844 +#: hardware.xml:880 #, 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:871 +#: hardware.xml:907 #, 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> 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:912 +#: hardware.xml:948 #, 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:922 +#: hardware.xml:958 #, 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:939 +#: hardware.xml:975 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <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> 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:979 +#: hardware.xml:1015 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:981 +#: hardware.xml:1017 #, no-c-format msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" #. Tag: entry -#: hardware.xml:993 +#: hardware.xml:1029 #, no-c-format msgid "System Type" msgstr "" #. Tag: entry -#: hardware.xml:993 +#: hardware.xml:1029 #, no-c-format msgid "<entry>CPU</entry>" msgstr "" #. Tag: entry -#: hardware.xml:993 +#: hardware.xml:1029 #, no-c-format msgid "Code-name" msgstr "" #. Tag: entry -#: hardware.xml:994 +#: hardware.xml:1030 #, no-c-format msgid "Debian subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1000 +#: hardware.xml:1036 #, no-c-format msgid "DECstation 5000/1xx" msgstr "" #. Tag: entry -#: hardware.xml:1001 hardware.xml:1011 hardware.xml:1016 hardware.xml:1026 +#: hardware.xml:1037 hardware.xml:1047 hardware.xml:1052 hardware.xml:1062 #, no-c-format msgid "R3000" msgstr "" #. Tag: entry -#: hardware.xml:1002 hardware.xml:1007 +#: hardware.xml:1038 hardware.xml:1043 #, no-c-format msgid "3MIN" msgstr "" #. Tag: entry -#: hardware.xml:1005 +#: hardware.xml:1041 #, no-c-format msgid "DECstation 5000/150" msgstr "" #. Tag: entry -#: hardware.xml:1006 hardware.xml:1031 +#: hardware.xml:1042 hardware.xml:1067 #, no-c-format msgid "R4000" msgstr "" #. Tag: entry -#: hardware.xml:1010 +#: hardware.xml:1046 #, no-c-format msgid "DECstation 5000/200" msgstr "" #. Tag: entry -#: hardware.xml:1012 +#: hardware.xml:1048 #, no-c-format msgid "3MAX" msgstr "" #. Tag: entry -#: hardware.xml:1015 +#: hardware.xml:1051 #, no-c-format msgid "DECstation 5000/240" msgstr "" #. Tag: entry -#: hardware.xml:1017 hardware.xml:1022 +#: hardware.xml:1053 hardware.xml:1058 #, no-c-format msgid "3MAX+" msgstr "" #. Tag: entry -#: hardware.xml:1020 +#: hardware.xml:1056 #, no-c-format msgid "DECstation 5000/260" msgstr "" #. Tag: entry -#: hardware.xml:1021 +#: hardware.xml:1057 #, no-c-format msgid "R4400" msgstr "" #. Tag: entry -#: hardware.xml:1025 +#: hardware.xml:1061 #, no-c-format msgid "Personal DECstation 5000/xx" msgstr "" #. Tag: entry -#: hardware.xml:1027 hardware.xml:1032 +#: hardware.xml:1063 hardware.xml:1068 #, no-c-format msgid "Maxine" msgstr "" #. Tag: entry -#: hardware.xml:1030 +#: hardware.xml:1066 #, no-c-format msgid "Personal DECstation 5000/50" msgstr "" #. Tag: para -#: hardware.xml:1037 +#: hardware.xml:1073 #, no-c-format msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" #. Tag: para -#: hardware.xml:1044 +#: hardware.xml:1080 #, 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:1054 +#: hardware.xml:1090 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1055 +#: hardware.xml:1091 #, no-c-format msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para -#: hardware.xml:1066 +#: hardware.xml:1102 #, no-c-format msgid "" "If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" @@ -1926,1255 +1926,1267 @@ msgid "" msgstr "" #. Tag: para -#: hardware.xml:1084 +#: hardware.xml:1120 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1098 +#: hardware.xml:1134 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants." msgstr "" #. Tag: para -#: hardware.xml:1106 +#: hardware.xml:1142 #, no-c-format msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future." msgstr "" #. Tag: title -#: hardware.xml:1114 +#: hardware.xml:1150 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1116 +#: hardware.xml:1152 #, no-c-format msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1123 +#: hardware.xml:1159 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1124 +#: hardware.xml:1160 #, 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:1134 +#: hardware.xml:1170 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1135 +#: hardware.xml:1171 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1139 +#: hardware.xml:1175 #, 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:1145 +#: hardware.xml:1181 #, 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:1150 +#: hardware.xml:1186 #, 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: term -#: hardware.xml:1159 +#: hardware.xml:1195 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1160 +#: hardware.xml:1196 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1168 +#: hardware.xml:1204 #, no-c-format msgid "<term>apus</term>" msgstr "" #. Tag: para -#: hardware.xml:1169 +#: hardware.xml:1205 #, no-c-format msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title -#: hardware.xml:1182 +#: hardware.xml:1218 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1184 +#: 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:1191 +#: 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:1199 +#: 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:1207 +#: 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:1223 hardware.xml:1358 hardware.xml:1402 hardware.xml:1431 +#: hardware.xml:1259 hardware.xml:1394 hardware.xml:1438 hardware.xml:1467 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1224 +#: hardware.xml:1260 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1230 +#: hardware.xml:1266 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1231 +#: hardware.xml:1267 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1232 hardware.xml:1235 hardware.xml:1238 hardware.xml:1241 hardware.xml:1244 hardware.xml:1247 hardware.xml:1250 hardware.xml:1253 hardware.xml:1256 hardware.xml:1259 hardware.xml:1262 hardware.xml:1265 hardware.xml:1268 hardware.xml:1271 hardware.xml:1274 hardware.xml:1277 +#: 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:1234 +#: hardware.xml:1270 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1237 +#: hardware.xml:1273 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1240 +#: hardware.xml:1276 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1243 +#: hardware.xml:1279 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1246 +#: hardware.xml:1282 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1249 +#: hardware.xml:1285 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1252 +#: hardware.xml:1288 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1255 +#: hardware.xml:1291 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1258 +#: hardware.xml:1294 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1261 +#: hardware.xml:1297 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1264 +#: hardware.xml:1300 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1267 +#: hardware.xml:1303 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1270 +#: hardware.xml:1306 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1273 +#: hardware.xml:1309 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1276 +#: hardware.xml:1312 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1279 +#: hardware.xml:1315 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: 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 hardware.xml:1319 hardware.xml:1322 hardware.xml:1328 hardware.xml:1334 hardware.xml:1340 +#: 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:1282 +#: hardware.xml:1318 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1285 +#: hardware.xml:1321 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1288 +#: hardware.xml:1324 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1291 +#: hardware.xml:1327 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1294 +#: hardware.xml:1330 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1297 +#: hardware.xml:1333 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1300 +#: hardware.xml:1336 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1303 +#: hardware.xml:1339 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1306 +#: hardware.xml:1342 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1309 +#: hardware.xml:1345 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1312 +#: hardware.xml:1348 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1317 +#: hardware.xml:1353 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1318 +#: hardware.xml:1354 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1321 +#: hardware.xml:1357 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1326 +#: hardware.xml:1362 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1327 +#: hardware.xml:1363 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1332 +#: hardware.xml:1368 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1333 +#: hardware.xml:1369 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1338 hardware.xml:1364 +#: hardware.xml:1374 hardware.xml:1400 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1339 +#: hardware.xml:1375 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1348 +#: hardware.xml:1384 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1365 +#: hardware.xml:1401 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1367 +#: hardware.xml:1403 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1369 +#: hardware.xml:1405 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1371 +#: hardware.xml:1407 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1373 +#: hardware.xml:1409 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1377 hardware.xml:1408 +#: hardware.xml:1413 hardware.xml:1444 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1378 +#: hardware.xml:1414 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1380 +#: hardware.xml:1416 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1382 +#: hardware.xml:1418 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1384 +#: hardware.xml:1420 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1392 +#: hardware.xml:1428 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1409 +#: hardware.xml:1445 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1412 +#: hardware.xml:1448 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1413 +#: hardware.xml:1449 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1421 +#: hardware.xml:1457 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1437 +#: hardware.xml:1473 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1438 +#: hardware.xml:1474 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1446 +#: hardware.xml:1482 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1448 +#: 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:1485 +#: hardware.xml:1521 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1487 +#: 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:1496 +#: 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:1504 +#: 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:1520 +#: hardware.xml:1556 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1521 +#: 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://oss.software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml\">technical details web page</ulink> at <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml\">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: para -#: hardware.xml:1544 +#: hardware.xml:1580 #, no-c-format msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." msgstr "" #. Tag: title -#: hardware.xml:1564 +#: hardware.xml:1600 #, no-c-format msgid "Memory Configuration" msgstr "" #. Tag: para -#: hardware.xml:1565 +#: hardware.xml:1601 #, no-c-format msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result." msgstr "" #. Tag: para -#: hardware.xml:1574 +#: hardware.xml:1610 #, no-c-format msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient." msgstr "" #. Tag: para -#: hardware.xml:1582 +#: hardware.xml:1618 #, no-c-format msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2." msgstr "" #. Tag: title -#: hardware.xml:1593 +#: hardware.xml:1629 #, no-c-format msgid "Graphics Configuration" msgstr "" #. Tag: para -#: hardware.xml:1594 +#: hardware.xml:1630 #, no-c-format msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized." msgstr "" #. Tag: para -#: hardware.xml:1603 +#: hardware.xml:1639 #, no-c-format msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk." msgstr "" #. Tag: para -#: hardware.xml:1611 +#: hardware.xml:1647 #, no-c-format msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console." msgstr "" #. Tag: title -#: hardware.xml:1623 +#: hardware.xml:1659 #, no-c-format msgid "Graphics Card" msgstr "" #. Tag: para -#: hardware.xml:1625 +#: hardware.xml:1660 #, 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:1633 +#: hardware.xml:1668 #, 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:1642 +#: hardware.xml:1677 #, no-c-format msgid "The X.Org X11 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:1651 +#: hardware.xml:1686 #, no-c-format msgid "The X.Org X11 window system is supported on some DECstation models. 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: title -#: hardware.xml:1663 +#: hardware.xml:1697 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1664 +#: hardware.xml:1698 #, no-c-format msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" msgstr "" #. Tag: title -#: hardware.xml:1676 hardware.xml:1701 hardware.xml:1724 +#: hardware.xml:1709 hardware.xml:1731 hardware.xml:1751 hardware.xml:1774 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1678 +#: hardware.xml:1710 #, no-c-format msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." msgstr "" #. Tag: para -#: hardware.xml:1686 +#: hardware.xml:1718 #, 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:1702 +#: hardware.xml:1733 +#, no-c-format +msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was 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:1742 +#, 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:1752 #, no-c-format msgid "Multi-processor support — also called <quote>symmetric multi-processing</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:1711 +#: hardware.xml:1761 #, 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:1725 +#: hardware.xml:1775 #, no-c-format msgid "Multi-processor support — also called <quote>symmetric multi-processing</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:1735 +#: hardware.xml:1785 #, 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. 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:1806 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1758 +#: hardware.xml:1808 #, 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 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:1769 +#: hardware.xml:1819 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1770 +#: hardware.xml:1820 #, 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:1776 +#: hardware.xml:1826 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1783 +#: hardware.xml:1833 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1785 +#: hardware.xml:1835 #, 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:1792 +#: hardware.xml:1842 #, 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:1804 +#: hardware.xml:1854 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. 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:1814 +#: hardware.xml:1864 #, 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:1819 +#: hardware.xml:1869 #, 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:1828 +#: hardware.xml:1878 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." msgstr "" #. Tag: para -#: hardware.xml:1833 +#: hardware.xml:1883 #, 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: para -#: hardware.xml:1848 +#: hardware.xml:1898 #, no-c-format msgid "On DECstations, 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." msgstr "" #. Tag: para -#: hardware.xml:1857 +#: hardware.xml:1907 #, no-c-format msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" #. Tag: para -#: hardware.xml:1866 +#: hardware.xml:1916 #, no-c-format msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: hardware.xml:1878 +#: hardware.xml:1928 #, no-c-format msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" #. Tag: title -#: hardware.xml:1885 +#: hardware.xml:1935 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1887 +#: hardware.xml:1937 #, 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:1893 +#: hardware.xml:1943 #, 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:1898 +#: hardware.xml:1948 #, 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:1906 +#: hardware.xml:1956 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1908 +#: hardware.xml:1958 #, 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:1920 +#: hardware.xml:1970 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1922 +#: hardware.xml:1972 #, no-c-format msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1928 +#: hardware.xml:1978 #, 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: para -#: hardware.xml:1933 +#: hardware.xml:1983 #, no-c-format msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." msgstr "" #. Tag: title -#: hardware.xml:1942 +#: hardware.xml:1992 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1944 +#: hardware.xml:1994 #, 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 the 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:1956 +#: hardware.xml:2006 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:1958 +#: hardware.xml:2008 #, 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:1968 +#: hardware.xml:2018 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, 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:1975 +#: hardware.xml:2025 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. 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:1985 +#: hardware.xml:2035 #, 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:1995 +#: hardware.xml:2045 #, 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:2028 +#: hardware.xml:2078 #, 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:2037 +#: hardware.xml:2087 #, 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:2043 +#: hardware.xml:2093 #, 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:2049 +#: hardware.xml:2099 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2054 +#: hardware.xml:2104 #, 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:2071 +#: hardware.xml:2121 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2072 +#: hardware.xml:2122 #, 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:2078 +#: hardware.xml:2128 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2084 +#: hardware.xml:2134 #, 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:2090 +#: hardware.xml:2140 #, 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:2096 +#: hardware.xml:2146 #, 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:2102 +#: hardware.xml:2152 #, 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:2112 +#: hardware.xml:2162 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2114 +#: hardware.xml:2164 #, 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:2122 +#: hardware.xml:2172 #, 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:2127 +#: hardware.xml:2177 #, 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:2135 +#: hardware.xml:2185 #, 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:2146 +#: hardware.xml:2196 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2147 +#: hardware.xml:2197 #, 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:2154 +#: hardware.xml:2204 #, 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:2165 +#: hardware.xml:2215 #, 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:2177 +#: hardware.xml:2227 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2178 +#: hardware.xml:2228 #, 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:2191 +#: hardware.xml:2241 #, 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 its 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:2212 +#: hardware.xml:2262 #, 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:2225 +#: hardware.xml:2275 #, no-c-format msgid "Fake or <quote>Virtual</quote> Parity RAM" msgstr "" #. Tag: para -#: hardware.xml:2226 +#: hardware.xml:2276 #, no-c-format msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits." msgstr "" #. Tag: para -#: hardware.xml:2241 +#: hardware.xml:2291 #, no-c-format msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>." msgstr "" #. Tag: para -#: hardware.xml:2247 +#: hardware.xml:2297 #, no-c-format msgid "Most, if not all, Alpha systems require true-parity RAM." msgstr "" #. Tag: title -#: hardware.xml:2262 +#: hardware.xml:2312 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2264 +#: hardware.xml:2314 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." msgstr "" #. Tag: para -#: hardware.xml:2273 +#: hardware.xml:2323 #, 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:2282 +#: hardware.xml:2332 #, 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:2290 +#: hardware.xml:2340 #, 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:2300 +#: hardware.xml:2350 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2311 +#: hardware.xml:2361 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2313 +#: hardware.xml:2363 #, no-c-format msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." msgstr "" #. Tag: para -#: hardware.xml:2332 +#: hardware.xml:2382 #, no-c-format msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." msgstr "" #. Tag: para -#: hardware.xml:2340 +#: hardware.xml:2390 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:2349 +#: hardware.xml:2399 #, no-c-format msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" msgstr "" #. Tag: para -#: hardware.xml:2355 +#: hardware.xml:2405 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2361 +#: hardware.xml:2411 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2369 +#: hardware.xml:2419 #, no-c-format msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" msgstr "" #. Tag: para -#: hardware.xml:2377 +#: hardware.xml:2427 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2383 +#: hardware.xml:2433 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2388 +#: hardware.xml:2438 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2395 hardware.xml:2401 hardware.xml:2407 hardware.xml:2413 hardware.xml:2419 +#: hardware.xml:2445 hardware.xml:2451 hardware.xml:2457 hardware.xml:2463 hardware.xml:2469 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." msgstr "" #. Tag: para -#: hardware.xml:2425 +#: hardware.xml:2475 #, no-c-format msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" #. Tag: para -#: hardware.xml:2431 +#: hardware.xml:2481 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2439 +#: hardware.xml:2489 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2444 +#: hardware.xml:2494 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2449 +#: hardware.xml:2499 #, no-c-format msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" msgstr "" #. Tag: para -#: hardware.xml:2454 +#: hardware.xml:2504 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2463 +#: hardware.xml:2513 #, no-c-format msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" msgstr "" #. Tag: para -#: hardware.xml:2469 +#: hardware.xml:2519 #, no-c-format msgid "PCI-based NE2000" msgstr "" #. Tag: para -#: hardware.xml:2475 +#: hardware.xml:2525 #, no-c-format msgid "DECchip Tulip" msgstr "" #. Tag: para -#: hardware.xml:2482 +#: hardware.xml:2532 #, no-c-format msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" msgstr "" #. Tag: para -#: hardware.xml:2488 +#: hardware.xml:2538 #, no-c-format msgid "Ether1" msgstr "" #. Tag: para -#: hardware.xml:2493 +#: hardware.xml:2543 #, no-c-format msgid "Ether3" msgstr "" #. Tag: para -#: hardware.xml:2498 +#: hardware.xml:2548 #, no-c-format msgid "EtherH" msgstr "" #. Tag: para -#: hardware.xml:2505 +#: hardware.xml:2555 #, no-c-format msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." msgstr "" #. Tag: para -#: hardware.xml:2511 +#: hardware.xml:2561 #, no-c-format msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 8b31ac59e..091205a38 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: 2006-08-07 22:39+0000\n" +"POT-Creation-Date: 2006-08-16 18:10+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" @@ -260,7 +260,7 @@ msgstr "" #. Tag: para #: install-methods.xml:394 #, no-c-format -msgid "If you have access to an i386 machine, you can use one of the following programs to copy images to floppies." +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 diff --git a/po/pot/installation-howto.pot b/po/pot/installation-howto.pot index db4d4b247..2d41378fa 100644 --- a/po/pot/installation-howto.pot +++ b/po/pot/installation-howto.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: 2006-08-07 22:39+0000\n" +"POT-Creation-Date: 2006-08-16 18:10+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" @@ -191,7 +191,7 @@ msgstr "" #. Tag: para #: installation-howto.xml:211 #, no-c-format -msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>). <phrase arch=\"x86\"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. <footnote><para> The 2.6 kernel is the default for most boot methods, but is not available when booting from a floppy. </para></footnote> </phrase>" +msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>). <phrase arch=\"i386\"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. <footnote><para> The 2.6 kernel is the default for most boot methods, but is not available when booting from a floppy. </para></footnote> </phrase>" msgstr "" #. Tag: para diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index 2dc1bcc82..120fa6b0e 100644 --- a/po/pot/post-install.pot +++ b/po/pot/post-install.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: 2006-08-07 22:39+0000\n" +"POT-Creation-Date: 2006-08-16 18:10+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" @@ -284,7 +284,7 @@ msgstr "" #. Tag: para #: post-install.xml:419 #, no-c-format -msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <phrase condition=\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"x86\"> such as <quote>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, <phrase condition=\"classic-kpkg\">e.g., if you have PCMCIA,</phrase> you'll need to install that package as well." +msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <phrase condition=\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, <phrase condition=\"classic-kpkg\">e.g., if you have PCMCIA,</phrase> you'll need to install that package as well." msgstr "" #. Tag: para diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index e5288c2dc..66d64f370 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.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: 2006-08-07 22:39+0000\n" +"POT-Creation-Date: 2006-08-16 18:10+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" @@ -1329,325 +1329,325 @@ msgid "This section will walk you through pre-installation hardware setup, if an msgstr "" #. Tag: title -#: preparing.xml:1429 +#: preparing.xml:1434 #, no-c-format msgid "Invoking the BIOS Set-Up Menu" msgstr "" #. Tag: para -#: preparing.xml:1431 +#: preparing.xml:1436 #, no-c-format msgid "BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS set-up menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not doing so can lead to intermittent crashes or an inability to install Debian." msgstr "" #. Tag: para -#: preparing.xml:1440 +#: preparing.xml:1445 #, no-c-format msgid "The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></ulink>, answering the question, <quote>How do I enter the CMOS configuration menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) configuration menu depends on who wrote your BIOS software:" msgstr "" #. Tag: term -#: preparing.xml:1454 +#: preparing.xml:1459 #, no-c-format msgid "AMI BIOS" msgstr "" #. Tag: para -#: preparing.xml:1455 +#: preparing.xml:1460 #, no-c-format msgid "<keycap>Delete</keycap> key during the POST (power on self test)" msgstr "" #. Tag: term -#: preparing.xml:1463 +#: preparing.xml:1468 #, no-c-format msgid "Award BIOS" msgstr "" #. Tag: para -#: preparing.xml:1464 +#: preparing.xml:1469 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST" msgstr "" #. Tag: term -#: preparing.xml:1473 +#: preparing.xml:1478 #, no-c-format msgid "DTK BIOS" msgstr "" #. Tag: para -#: preparing.xml:1474 +#: preparing.xml:1479 #, no-c-format msgid "<keycap>Esc</keycap> key during the POST" msgstr "" #. Tag: term -#: preparing.xml:1481 +#: preparing.xml:1486 #, no-c-format msgid "IBM PS/2 BIOS" msgstr "" #. Tag: para -#: preparing.xml:1482 +#: preparing.xml:1487 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> </keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo>" msgstr "" #. Tag: term -#: preparing.xml:1496 +#: preparing.xml:1501 #, no-c-format msgid "Phoenix BIOS" msgstr "" #. Tag: para -#: preparing.xml:1497 +#: preparing.xml:1502 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> </keycombo> or <keycap>F1</keycap>" msgstr "" #. Tag: para -#: preparing.xml:1513 +#: preparing.xml:1518 #, no-c-format msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>." msgstr "" #. Tag: para -#: preparing.xml:1518 +#: preparing.xml:1523 #, no-c-format msgid "Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></ulink>." msgstr "" #. Tag: title -#: preparing.xml:1529 preparing.xml:1873 +#: preparing.xml:1534 preparing.xml:1878 #, no-c-format msgid "Boot Device Selection" msgstr "" #. Tag: para -#: preparing.xml:1531 +#: preparing.xml:1536 #, no-c-format msgid "Many BIOS set-up menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian." msgstr "" #. Tag: para -#: preparing.xml:1542 +#: preparing.xml:1547 #, no-c-format msgid "If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller." msgstr "" #. Tag: para -#: preparing.xml:1549 +#: preparing.xml:1554 #, no-c-format msgid "Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device." msgstr "" #. Tag: para -#: preparing.xml:1557 +#: preparing.xml:1562 #, no-c-format msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive." msgstr "" #. Tag: title -#: preparing.xml:1566 +#: preparing.xml:1571 #, no-c-format msgid "Changing the Boot Order on IDE Computers" msgstr "" #. Tag: para -#: preparing.xml:1569 +#: preparing.xml:1574 #, no-c-format msgid "As your computer starts, press the keys to enter the BIOS utility. Often, it is the <keycap>Delete</keycap> key. However, consult the hardware documentation for the exact keystrokes." msgstr "" #. Tag: para -#: preparing.xml:1576 +#: preparing.xml:1581 #, no-c-format msgid "Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives." msgstr "" #. Tag: para -#: preparing.xml:1581 +#: preparing.xml:1586 #, no-c-format msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." msgstr "" #. Tag: para -#: preparing.xml:1586 +#: preparing.xml:1591 #, no-c-format msgid "C is the hard drive, and A is the floppy drive." msgstr "" #. Tag: para -#: preparing.xml:1592 +#: preparing.xml:1597 #, no-c-format msgid "Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys cycle through the possible choices." msgstr "" #. Tag: para -#: preparing.xml:1600 +#: preparing.xml:1605 #, no-c-format msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer." msgstr "" #. Tag: title -#: preparing.xml:1610 +#: preparing.xml:1615 #, no-c-format msgid "Changing the Boot Order on SCSI Computers" msgstr "" #. Tag: para -#: preparing.xml:1614 +#: preparing.xml:1619 #, no-c-format msgid "As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" #. Tag: para -#: preparing.xml:1619 +#: preparing.xml:1624 #, no-c-format msgid "You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer." msgstr "" #. Tag: para -#: preparing.xml:1625 +#: preparing.xml:1630 #, no-c-format msgid "The keystrokes you need depend on the utility. Often, it is <keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, consult your hardware documentation for the exact keystrokes." msgstr "" #. Tag: para -#: preparing.xml:1633 +#: preparing.xml:1638 #, no-c-format msgid "Find the utility for changing the boot order." msgstr "" #. Tag: para -#: preparing.xml:1638 +#: preparing.xml:1643 #, no-c-format msgid "Set the utility so that the SCSI ID of the CD drive is first on the list." msgstr "" #. Tag: para -#: preparing.xml:1644 +#: preparing.xml:1649 #, no-c-format msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press <keycap>F10</keycap>." msgstr "" #. Tag: title -#: preparing.xml:1658 +#: preparing.xml:1663 #, no-c-format msgid "Miscellaneous BIOS Settings" msgstr "" #. Tag: title -#: preparing.xml:1660 +#: preparing.xml:1665 #, no-c-format msgid "CD-ROM Settings" msgstr "" #. Tag: para -#: preparing.xml:1661 +#: preparing.xml:1666 #, no-c-format msgid "Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get <userinput>seek failed</userinput> error messages, this may be your problem." msgstr "" #. Tag: title -#: preparing.xml:1671 +#: preparing.xml:1676 #, no-c-format msgid "Extended vs. Expanded Memory" msgstr "" #. Tag: para -#: preparing.xml:1672 +#: preparing.xml:1677 #, no-c-format msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory." msgstr "" #. Tag: title -#: preparing.xml:1682 +#: preparing.xml:1687 #, no-c-format msgid "Virus Protection" msgstr "" #. Tag: para -#: preparing.xml:1683 +#: preparing.xml:1688 #, no-c-format msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>." msgstr "" #. Tag: title -#: preparing.xml:1704 +#: preparing.xml:1709 #, no-c-format msgid "Shadow RAM" msgstr "" #. Tag: para -#: preparing.xml:1705 +#: preparing.xml:1710 #, no-c-format msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices." msgstr "" #. Tag: title -#: preparing.xml:1722 +#: preparing.xml:1727 #, no-c-format msgid "Memory Hole" msgstr "" #. Tag: para -#: preparing.xml:1723 +#: preparing.xml:1728 #, no-c-format msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM." msgstr "" #. Tag: para -#: preparing.xml:1729 +#: preparing.xml:1734 #, no-c-format msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device — it just worked with that setting and not without it." msgstr "" #. Tag: title -#: preparing.xml:1745 +#: preparing.xml:1750 #, no-c-format msgid "Advanced Power Management" msgstr "" #. Tag: para -#: preparing.xml:1746 +#: preparing.xml:1751 #, no-c-format msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS." msgstr "" #. Tag: title -#: preparing.xml:1764 +#: preparing.xml:1769 #, no-c-format msgid "Firmware Revisions and Existing OS Setup" msgstr "" #. Tag: para -#: preparing.xml:1766 +#: preparing.xml:1771 #, no-c-format msgid "&arch-title; machines are generally self-configuring and do not require firmware configuration. However, you should make sure that you have the appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 is recommended because version 7.0.1 contains a bug in the video drivers preventing the boot loader from deactivating the video interrupts, resulting in a boot hang. On the BVM VMEbus systems you should make sure you are using BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as standard on the BVM systems but are available from BVM on request free of charge." msgstr "" #. Tag: title -#: preparing.xml:1789 +#: preparing.xml:1794 #, no-c-format msgid "Invoking OpenFirmware" msgstr "" #. Tag: para -#: preparing.xml:1790 +#: preparing.xml:1795 #, no-c-format msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine." msgstr "" #. Tag: para -#: preparing.xml:1798 +#: preparing.xml:1803 #, no-c-format msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command</keycap> <keycap>option</keycap> <keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints." msgstr "" #. Tag: para -#: preparing.xml:1807 +#: preparing.xml:1812 #, no-c-format msgid "" "The OpenFirmware prompt looks like this: <informalexample><screen>\n" @@ -1657,43 +1657,43 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1820 +#: preparing.xml:1825 #, no-c-format msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, is broken. These machines will most likely not be able to boot from the hard drive unless the firmware is patched. A firmware patch is included in the <application>System Disk 2.3.1</application> utility, available from Apple at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, and launching it, select the <guibutton>Save button</guibutton> to have the firmware patches installed to nvram." msgstr "" #. Tag: title -#: preparing.xml:1840 +#: preparing.xml:1845 #, no-c-format msgid "Invoking OpenBoot" msgstr "" #. Tag: para -#: preparing.xml:1842 +#: preparing.xml:1847 #, no-c-format msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts." msgstr "" #. Tag: para -#: preparing.xml:1850 +#: preparing.xml:1855 #, no-c-format msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>></userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt." msgstr "" #. Tag: para -#: preparing.xml:1862 +#: preparing.xml:1867 #, no-c-format msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program." msgstr "" #. Tag: para -#: preparing.xml:1875 +#: preparing.xml:1880 #, no-c-format msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." msgstr "" #. Tag: para -#: preparing.xml:1885 +#: preparing.xml:1890 #, no-c-format msgid "" "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form <informalexample> <screen>\n" @@ -1704,7 +1704,7 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1908 +#: preparing.xml:1913 #, no-c-format msgid "" "To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen>\n" @@ -1713,205 +1713,205 @@ msgid "" msgstr "" #. Tag: screen -#: preparing.xml:1927 +#: preparing.xml:1932 #, no-c-format msgid "eeprom boot-device=disk1:1" msgstr "" #. Tag: title -#: preparing.xml:1937 +#: preparing.xml:1942 #, no-c-format msgid "BIOS Setup" msgstr "" #. Tag: para -#: preparing.xml:1938 +#: preparing.xml:1943 #, no-c-format msgid "In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based." msgstr "" #. Tag: para -#: preparing.xml:1950 +#: preparing.xml:1955 #, no-c-format msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you." msgstr "" #. Tag: para -#: preparing.xml:1960 +#: preparing.xml:1965 #, no-c-format msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where do you find them. Based on both sources of information you have to prepare your machine and the installation medium and to perform a boot from it. When you see the welcome message in your client session join this document again for the Debian-specific installation steps." msgstr "" #. Tag: title -#: preparing.xml:1977 +#: preparing.xml:1982 #, no-c-format msgid "Native and LPAR installations" msgstr "" #. Tag: para -#: preparing.xml:1978 +#: preparing.xml:1983 #, no-c-format msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux." msgstr "" #. Tag: title -#: preparing.xml:1992 +#: preparing.xml:1997 #, no-c-format msgid "Installation as a VM guest" msgstr "" #. Tag: para -#: preparing.xml:1994 +#: preparing.xml:1999 #, no-c-format msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux." msgstr "" #. Tag: para -#: preparing.xml:2004 +#: preparing.xml:2009 #, no-c-format msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters." msgstr "" #. Tag: title -#: preparing.xml:2016 +#: preparing.xml:2021 #, no-c-format msgid "Setting up an installation server" msgstr "" #. Tag: para -#: preparing.xml:2018 +#: preparing.xml:2023 #, no-c-format msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: preparing.xml:2026 +#: preparing.xml:2031 #, no-c-format msgid "The installation server needs to copy the exact directory structure from any &debian; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree." msgstr "" #. Tag: emphasis -#: preparing.xml:2035 +#: preparing.xml:2040 #, no-c-format msgid "FIXME: more information needed — from a Redbook?" msgstr "" #. Tag: title -#: preparing.xml:2041 +#: preparing.xml:2046 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "" #. Tag: para -#: preparing.xml:2042 +#: preparing.xml:2047 #, no-c-format msgid "Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It sometimes works, but is sensitive to temperature and other factors and can actually damage your system. One of the authors of this document over-clocked his own system for a year, and then the system started aborting the <command>gcc</command> program with an unexpected signal while it was compiling the operating system kernel. Turning the CPU speed back down to its rated value solved the problem." msgstr "" #. Tag: para -#: preparing.xml:2052 +#: preparing.xml:2057 #, no-c-format msgid "The <command>gcc</command> compiler is often the first thing to die from bad memory modules (or other hardware problems that change data unpredictably) because it builds huge data structures that it traverses repeatedly. An error in these data structures will cause it to execute an illegal instruction or access a non-existent address. The symptom of this will be <command>gcc</command> dying from an unexpected signal." msgstr "" #. Tag: para -#: preparing.xml:2062 +#: preparing.xml:2067 #, no-c-format msgid "Atari TT RAM boards are notorious for RAM problems under Linux; if you encounter any strange problems, try running at least the kernel in ST-RAM. Amiga users may need to exclude RAM using a booter memfile. <phrase condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </emphasis></phrase>" msgstr "" #. Tag: para -#: preparing.xml:2074 +#: preparing.xml:2079 #, no-c-format msgid "The very best motherboards support parity RAM and will actually tell you if your system has a single-bit error in RAM. Unfortunately, they don't have a way to fix the error, thus they generally crash immediately after they tell you about the bad RAM. Still, it's better to be told you have bad memory than to have it silently insert errors in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend=\"Parity-RAM\"/>." msgstr "" #. Tag: para -#: preparing.xml:2085 +#: preparing.xml:2090 #, no-c-format msgid "If you do have true-parity RAM and your motherboard can handle it, be sure to enable any BIOS settings that cause the motherboard to interrupt on memory parity errors." msgstr "" #. Tag: title -#: preparing.xml:2093 +#: preparing.xml:2098 #, no-c-format msgid "The Turbo Switch" msgstr "" #. Tag: para -#: preparing.xml:2094 +#: preparing.xml:2099 #, no-c-format msgid "Many systems have a <emphasis>turbo</emphasis> switch that controls the speed of the CPU. Select the high-speed setting. If your BIOS allows you to disable software control of the turbo switch (or software control of CPU speed), do so and lock the system in high-speed mode. We have one report that on a particular system, while Linux is auto-probing (looking for hardware devices) it can accidentally touch the software control for the turbo switch." msgstr "" #. Tag: title -#: preparing.xml:2107 +#: preparing.xml:2112 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "" #. Tag: para -#: preparing.xml:2108 +#: preparing.xml:2113 #, no-c-format msgid "Many users of Cyrix CPUs have had to disable the cache in their systems during installation, because the floppy disk has errors if they do not. If you have to do this, be sure to re-enable your cache when you are finished with installation, as the system runs <emphasis>much</emphasis> slower with the cache disabled." msgstr "" #. Tag: para -#: preparing.xml:2116 +#: preparing.xml:2121 #, no-c-format msgid "We don't think this is necessarily the fault of the Cyrix CPU. It may be something that Linux can work around. We'll continue to look into the problem. For the technically curious, we suspect a problem with the cache being invalid after a switch from 16-bit to 32-bit code." msgstr "" #. Tag: title -#: preparing.xml:2126 +#: preparing.xml:2131 #, no-c-format msgid "Peripheral Hardware Settings" msgstr "" #. Tag: para -#: preparing.xml:2127 +#: preparing.xml:2132 #, no-c-format msgid "You may have to change some settings or jumpers on your computer's peripheral cards. Some cards have setup menus, while others rely on jumpers. This document cannot hope to provide complete information on every hardware device; what it hopes to provide is useful tips." msgstr "" #. Tag: para -#: preparing.xml:2134 +#: preparing.xml:2139 #, no-c-format msgid "If any cards provide <quote>mapped memory</quote>, the memory should be mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 megabyte) or at an address at least 1 megabyte greater than the total amount of RAM in your system." msgstr "" #. Tag: title -#: preparing.xml:2145 +#: preparing.xml:2150 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "" #. Tag: para -#: preparing.xml:2146 +#: preparing.xml:2151 #, no-c-format msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options." msgstr "" #. Tag: title -#: preparing.xml:2159 +#: preparing.xml:2164 #, no-c-format msgid "More than 64 MB RAM" msgstr "" #. Tag: para -#: preparing.xml:2160 +#: preparing.xml:2165 #, no-c-format msgid "The Linux Kernel cannot always detect what amount of RAM you have. If this is the case please look at <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: title -#: preparing.xml:2169 +#: preparing.xml:2174 #, no-c-format msgid "Display visibility on OldWorld Powermacs" msgstr "" #. Tag: para -#: preparing.xml:2170 +#: preparing.xml:2175 #, no-c-format msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver but possibly others as well, may not produce a colormap with reliably results in visible output under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>." msgstr "" |