diff options
Diffstat (limited to 'po/pot/hardware.pot')
| -rw-r--r-- | po/pot/hardware.pot | 552 |
1 files changed, 276 insertions, 276 deletions
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index d32be6b88..2b604463b 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-02-07 15:07+0000\n" +"POT-Creation-Date: 2006-03-07 20:14+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -230,6 +230,12 @@ msgstr "" msgid "<entry>arm</entry>" msgstr "" +#: hardware.xml:111 +#, no-c-format +#. Tag: entry +msgid "Netwinder and CATS" +msgstr "" + #: hardware.xml:112 #, no-c-format #. Tag: entry @@ -239,19 +245,25 @@ msgstr "" #: hardware.xml:114 #, no-c-format #. Tag: entry -msgid "riscpc" +msgid "Linksys NSLU2" +msgstr "" + +#: hardware.xml:115 +#, no-c-format +#. Tag: entry +msgid "nslu2" msgstr "" -#: hardware.xml:116 +#: hardware.xml:117 #, no-c-format #. Tag: entry -msgid "shark" +msgid "RiscPC and Riscstation" msgstr "" #: hardware.xml:118 #, no-c-format #. Tag: entry -msgid "lart" +msgid "riscpc" msgstr "" #: hardware.xml:122 @@ -434,13 +446,13 @@ msgstr "" msgid "DECstation" msgstr "" -#: hardware.xml:173 hardware.xml:1002 hardware.xml:1017 hardware.xml:1027 +#: hardware.xml:173 hardware.xml:994 hardware.xml:1009 hardware.xml:1019 #, no-c-format #. Tag: entry msgid "r4k-kn04" msgstr "" -#: hardware.xml:175 hardware.xml:997 hardware.xml:1007 hardware.xml:1012 hardware.xml:1022 +#: hardware.xml:175 hardware.xml:989 hardware.xml:999 hardware.xml:1004 hardware.xml:1014 #, no-c-format #. Tag: entry msgid "r3k-kn02" @@ -494,7 +506,7 @@ msgstr "" 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-&architecture; mailing list</ulink> as well." msgstr "" -#: hardware.xml:224 hardware.xml:683 hardware.xml:780 hardware.xml:799 hardware.xml:842 hardware.xml:884 hardware.xml:938 hardware.xml:1087 hardware.xml:1493 +#: hardware.xml:224 hardware.xml:683 hardware.xml:772 hardware.xml:791 hardware.xml:834 hardware.xml:876 hardware.xml:930 hardware.xml:1081 hardware.xml:1487 #, no-c-format #. Tag: title msgid "CPU, Main Boards, and Video Support" @@ -1619,7 +1631,7 @@ msgstr "" #: hardware.xml:693 #, no-c-format #. Tag: para -msgid "Most ARM CPUs may be run in either endian mode (big or little). However, almost every current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." +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 "" #: hardware.xml:701 @@ -1628,289 +1640,277 @@ msgstr "" msgid "The commonly supported systems are" msgstr "" -#: hardware.xml:707 +#: hardware.xml:708 #, no-c-format #. Tag: term msgid "Netwinder" msgstr "" -#: hardware.xml:708 +#: hardware.xml:709 #, no-c-format #. Tag: para -msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." +msgid "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 "" -#: hardware.xml:720 +#: hardware.xml:722 #, no-c-format #. Tag: term -msgid "Bast" +msgid "NSLU2" msgstr "" -#: hardware.xml:721 +#: hardware.xml:723 #, no-c-format #. Tag: para -msgid "This is a modern ARM 920 board with a 266MHz Samsung processor. It has integrated IDE, USB, Serial, Parallel, audio, video, flash and two ethernet ports. This system has a good bootloader which is also found on the CATS and Riscstation systems." +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 "" -#: hardware.xml:732 +#: hardware.xml:734 #, no-c-format #. Tag: term msgid "RiscPC" msgstr "" -#: hardware.xml:733 +#: hardware.xml:735 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:748 +#: hardware.xml:750 #, no-c-format #. Tag: term msgid "Riscstation" msgstr "" -#: hardware.xml:749 +#: hardware.xml:751 #, no-c-format #. Tag: para msgid "This is an inexpensive 56MHz 7500FE based machine with integrated video, IDE, PS/2 keyboard and mouse and two serial ports. Its lack of processing power was made up for by its price. It may be found in two configurations one with RISC OS and one with a simple bootloader." msgstr "" -#: hardware.xml:761 -#, no-c-format -#. Tag: term -msgid "LART" -msgstr "" - -#: hardware.xml:762 -#, no-c-format -#. Tag: para -msgid "This is a modular open hardware platform intended to be built by enthusiasts. To be useful to install Debian it requires its KSB expansion board." -msgstr "" - -#: hardware.xml:781 +#: hardware.xml:773 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:800 +#: hardware.xml:792 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:808 hardware.xml:914 +#: hardware.xml:800 hardware.xml:906 #, no-c-format #. Tag: title msgid "<title>CPU</title>" msgstr "" -#: hardware.xml:809 +#: hardware.xml:801 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:819 +#: hardware.xml:811 #, no-c-format #. Tag: title msgid "I/O Bus" msgstr "" -#: hardware.xml:820 +#: hardware.xml:812 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:843 +#: hardware.xml:835 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:850 +#: hardware.xml:842 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:858 +#: hardware.xml:850 #, no-c-format #. Tag: para msgid "There are four major flavors of 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 "" -#: hardware.xml:885 +#: hardware.xml:877 #, no-c-format #. Tag: para msgid "Debian on &arch-title; currently supports two subarchitectures: <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> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on their SiByte processor family. </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-&architecture; mailing list</ulink>." msgstr "" -#: hardware.xml:915 +#: hardware.xml:907 #, no-c-format #. Tag: para 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. The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two SB-1 cores which are supported in SMP mode by this installer." msgstr "" -#: hardware.xml:922 +#: hardware.xml:914 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:939 +#: hardware.xml:931 #, no-c-format #. Tag: para -msgid "Debian on &arch-title; currently supports three subarchitectures: <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 included the Cobalt Qube, 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 their SiByte processor family. </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-&architecture; mailing list</ulink>." +msgid "Debian on &arch-title; currently supports three subarchitectures: <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 included 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 their SiByte processor family. </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-&architecture; mailing list</ulink>." msgstr "" -#: hardware.xml:973 +#: hardware.xml:965 #, no-c-format #. Tag: title msgid "CPU/Machine types" msgstr "" -#: hardware.xml:975 +#: hardware.xml:967 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:987 +#: hardware.xml:979 #, no-c-format #. Tag: entry msgid "System Type" msgstr "" -#: hardware.xml:987 +#: hardware.xml:979 #, no-c-format #. Tag: entry msgid "<entry>CPU</entry>" msgstr "" -#: hardware.xml:987 +#: hardware.xml:979 #, no-c-format #. Tag: entry msgid "Code-name" msgstr "" -#: hardware.xml:988 +#: hardware.xml:980 #, no-c-format #. Tag: entry msgid "Debian subarchitecture" msgstr "" -#: hardware.xml:994 +#: hardware.xml:986 #, no-c-format #. Tag: entry msgid "DECstation 5000/1xx" msgstr "" -#: hardware.xml:995 hardware.xml:1005 hardware.xml:1010 hardware.xml:1020 +#: hardware.xml:987 hardware.xml:997 hardware.xml:1002 hardware.xml:1012 #, no-c-format #. Tag: entry msgid "R3000" msgstr "" -#: hardware.xml:996 hardware.xml:1001 +#: hardware.xml:988 hardware.xml:993 #, no-c-format #. Tag: entry msgid "3MIN" msgstr "" -#: hardware.xml:999 +#: hardware.xml:991 #, no-c-format #. Tag: entry msgid "DECstation 5000/150" msgstr "" -#: hardware.xml:1000 hardware.xml:1025 +#: hardware.xml:992 hardware.xml:1017 #, no-c-format #. Tag: entry msgid "R4000" msgstr "" -#: hardware.xml:1004 +#: hardware.xml:996 #, no-c-format #. Tag: entry msgid "DECstation 5000/200" msgstr "" -#: hardware.xml:1006 +#: hardware.xml:998 #, no-c-format #. Tag: entry msgid "3MAX" msgstr "" -#: hardware.xml:1009 +#: hardware.xml:1001 #, no-c-format #. Tag: entry msgid "DECstation 5000/240" msgstr "" -#: hardware.xml:1011 hardware.xml:1016 +#: hardware.xml:1003 hardware.xml:1008 #, no-c-format #. Tag: entry msgid "3MAX+" msgstr "" -#: hardware.xml:1014 +#: hardware.xml:1006 #, no-c-format #. Tag: entry msgid "DECstation 5000/260" msgstr "" -#: hardware.xml:1015 +#: hardware.xml:1007 #, no-c-format #. Tag: entry msgid "R4400" msgstr "" -#: hardware.xml:1019 +#: hardware.xml:1011 #, no-c-format #. Tag: entry msgid "Personal DECstation 5000/xx" msgstr "" -#: hardware.xml:1021 hardware.xml:1026 +#: hardware.xml:1013 hardware.xml:1018 #, no-c-format #. Tag: entry msgid "Maxine" msgstr "" -#: hardware.xml:1024 +#: hardware.xml:1016 #, no-c-format #. Tag: entry msgid "Personal DECstation 5000/50" msgstr "" -#: hardware.xml:1031 +#: hardware.xml:1023 #, no-c-format #. Tag: para -msgid "All Cobalt machines are supported which have a serial console (which is needed for the installation)." +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 "" -#: hardware.xml:1036 +#: hardware.xml:1030 #, no-c-format #. Tag: para msgid "The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two SB-1 cores which are supported in SMP mode by this installer." msgstr "" -#: hardware.xml:1044 +#: hardware.xml:1038 #, no-c-format #. Tag: title msgid "Supported console options" msgstr "" -#: hardware.xml:1045 +#: hardware.xml:1039 #, no-c-format #. Tag: para msgid "Serial console is available on all supported DECstations (9600 bps, 8N1). For using 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) local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" -#: hardware.xml:1056 +#: hardware.xml:1050 #, no-c-format #. Tag: para msgid "" @@ -1919,1219 +1919,1219 @@ msgid "" "</screen></informalexample> where the option <literal>-l</literal> (line) sets the serial port to use and <literal>-s</literal> (speed) sets the speed for the connection (9600 bits per second)." msgstr "" -#: hardware.xml:1074 +#: hardware.xml:1068 #, no-c-format #. Tag: para msgid "Both Cobalt and Broadcom BCM91250A use 115200 bps." msgstr "" -#: hardware.xml:1088 +#: hardware.xml:1082 #, no-c-format #. Tag: para msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh), 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 "" -#: hardware.xml:1096 +#: hardware.xml:1090 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1104 +#: hardware.xml:1098 #, no-c-format #. Tag: title msgid "Kernel Flavours" msgstr "" -#: hardware.xml:1106 +#: hardware.xml:1100 #, no-c-format #. Tag: para msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" -#: hardware.xml:1113 +#: hardware.xml:1107 #, no-c-format #. Tag: term msgid "<term>powerpc</term>" msgstr "" -#: hardware.xml:1114 +#: hardware.xml:1108 #, no-c-format #. Tag: para msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple Power Macintosh systems up to and including the G4 use one of these processors." msgstr "" -#: hardware.xml:1124 +#: hardware.xml:1118 #, no-c-format #. Tag: term msgid "power3" msgstr "" -#: hardware.xml:1125 +#: hardware.xml:1119 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1135 +#: hardware.xml:1129 #, no-c-format #. Tag: term msgid "power4" msgstr "" -#: hardware.xml:1136 +#: hardware.xml:1130 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1141 +#: hardware.xml:1135 #, no-c-format #. Tag: para msgid "The Apple G5 is also based on the POWER4 architecture, and uses this kernel flavour." msgstr "" -#: hardware.xml:1150 +#: hardware.xml:1144 #, no-c-format #. Tag: term msgid "<term>apus</term>" msgstr "" -#: hardware.xml:1151 +#: hardware.xml:1145 #, no-c-format #. Tag: para msgid "This kernel flavour supports the Amiga Power-UP System." msgstr "" -#: hardware.xml:1163 +#: hardware.xml:1157 #, no-c-format #. Tag: title msgid "Power Macintosh (pmac) subarchitecture" msgstr "" -#: hardware.xml:1165 +#: hardware.xml:1159 #, no-c-format #. Tag: para msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) makes a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus, OldWorld PCI, and NewWorld." msgstr "" -#: hardware.xml:1172 +#: hardware.xml:1166 #, no-c-format #. Tag: para msgid "Macintosh computers using the 680x0 series of processors are not in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> or have a 3-digit model number such as Centris 650 or Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits." msgstr "" -#: hardware.xml:1179 +#: hardware.xml:1173 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1212 +#: hardware.xml:1206 #, no-c-format #. Tag: para 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. The beige colored G3 systems are also OldWorld." msgstr "" -#: hardware.xml:1218 +#: hardware.xml:1212 #, no-c-format #. Tag: para msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases. 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 "" -#: hardware.xml:1226 +#: hardware.xml:1220 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1242 hardware.xml:1377 hardware.xml:1421 hardware.xml:1450 +#: hardware.xml:1236 hardware.xml:1371 hardware.xml:1415 hardware.xml:1444 #, no-c-format #. Tag: entry msgid "Model Name/Number" msgstr "" -#: hardware.xml:1243 +#: hardware.xml:1237 #, no-c-format #. Tag: entry msgid "Generation" msgstr "" -#: hardware.xml:1249 +#: hardware.xml:1243 #, no-c-format #. Tag: entry msgid "Apple" msgstr "" -#: hardware.xml:1250 +#: hardware.xml:1244 #, no-c-format #. Tag: entry msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" -#: hardware.xml:1251 hardware.xml:1254 hardware.xml:1257 hardware.xml:1260 hardware.xml:1263 hardware.xml:1266 hardware.xml:1269 hardware.xml:1272 hardware.xml:1275 hardware.xml:1278 hardware.xml:1281 hardware.xml:1284 hardware.xml:1287 hardware.xml:1290 hardware.xml:1293 hardware.xml:1296 +#: hardware.xml:1245 hardware.xml:1248 hardware.xml:1251 hardware.xml:1254 hardware.xml:1257 hardware.xml:1260 hardware.xml:1263 hardware.xml:1266 hardware.xml:1269 hardware.xml:1272 hardware.xml:1275 hardware.xml:1278 hardware.xml:1281 hardware.xml:1284 hardware.xml:1287 hardware.xml:1290 #, no-c-format #. Tag: entry msgid "NewWorld" msgstr "" -#: hardware.xml:1253 +#: hardware.xml:1247 #, no-c-format #. Tag: entry msgid "iMac Summer 2000, Early 2001" msgstr "" -#: hardware.xml:1256 +#: hardware.xml:1250 #, no-c-format #. Tag: entry msgid "iMac G5" msgstr "" -#: hardware.xml:1259 +#: hardware.xml:1253 #, no-c-format #. Tag: entry msgid "iBook, iBook SE, iBook Dual USB" msgstr "" -#: hardware.xml:1262 +#: hardware.xml:1256 #, no-c-format #. Tag: entry msgid "iBook2" msgstr "" -#: hardware.xml:1265 +#: hardware.xml:1259 #, no-c-format #. Tag: entry msgid "iBook G4" msgstr "" -#: hardware.xml:1268 +#: hardware.xml:1262 #, no-c-format #. Tag: entry msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" -#: hardware.xml:1271 +#: hardware.xml:1265 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" -#: hardware.xml:1274 +#: hardware.xml:1268 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" -#: hardware.xml:1277 +#: hardware.xml:1271 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" -#: hardware.xml:1280 +#: hardware.xml:1274 #, no-c-format #. Tag: entry msgid "Power Macintosh G5" msgstr "" -#: hardware.xml:1283 +#: hardware.xml:1277 #, no-c-format #. Tag: entry msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" -#: hardware.xml:1286 +#: hardware.xml:1280 #, no-c-format #. Tag: entry msgid "PowerBook G3 Lombard (1999)" msgstr "" -#: hardware.xml:1289 +#: hardware.xml:1283 #, no-c-format #. Tag: entry msgid "PowerBook G4 Titanium" msgstr "" -#: hardware.xml:1292 +#: hardware.xml:1286 #, no-c-format #. Tag: entry msgid "PowerBook G4 Aluminum" msgstr "" -#: hardware.xml:1295 +#: hardware.xml:1289 #, no-c-format #. Tag: entry msgid "Xserve G5" msgstr "" -#: hardware.xml:1298 +#: hardware.xml:1292 #, no-c-format #. Tag: entry msgid "Performa 4400, 54xx, 5500" msgstr "" -#: hardware.xml:1299 hardware.xml:1302 hardware.xml:1305 hardware.xml:1308 hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 hardware.xml:1338 hardware.xml:1341 hardware.xml:1347 hardware.xml:1353 hardware.xml:1359 +#: hardware.xml:1293 hardware.xml:1296 hardware.xml:1299 hardware.xml:1302 hardware.xml:1305 hardware.xml:1308 hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1332 hardware.xml:1335 hardware.xml:1341 hardware.xml:1347 hardware.xml:1353 #, no-c-format #. Tag: entry msgid "OldWorld" msgstr "" -#: hardware.xml:1301 +#: hardware.xml:1295 #, no-c-format #. Tag: entry msgid "Performa 6360, 6400, 6500" msgstr "" -#: hardware.xml:1304 +#: hardware.xml:1298 #, no-c-format #. Tag: entry msgid "Power Macintosh 4400, 5400" msgstr "" -#: hardware.xml:1307 +#: hardware.xml:1301 #, no-c-format #. Tag: entry msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" -#: hardware.xml:1310 +#: hardware.xml:1304 #, no-c-format #. Tag: entry msgid "Power Macintosh 8200, 8500, 8600" msgstr "" -#: hardware.xml:1313 +#: hardware.xml:1307 #, no-c-format #. Tag: entry msgid "Power Macintosh 9500, 9600" msgstr "" -#: hardware.xml:1316 +#: hardware.xml:1310 #, no-c-format #. Tag: entry msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" -#: hardware.xml:1319 +#: hardware.xml:1313 #, no-c-format #. Tag: entry msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" -#: hardware.xml:1322 +#: hardware.xml:1316 #, no-c-format #. Tag: entry msgid "PowerBook 2400, 3400, 3500" msgstr "" -#: hardware.xml:1325 +#: hardware.xml:1319 #, no-c-format #. Tag: entry msgid "PowerBook G3 Wallstreet (1998)" msgstr "" -#: hardware.xml:1328 +#: hardware.xml:1322 #, no-c-format #. Tag: entry msgid "Twentieth Anniversary Macintosh" msgstr "" -#: hardware.xml:1331 +#: hardware.xml:1325 #, no-c-format #. Tag: entry msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" -#: hardware.xml:1336 +#: hardware.xml:1330 #, no-c-format #. Tag: entry msgid "Power Computing" msgstr "" -#: hardware.xml:1337 +#: hardware.xml:1331 #, no-c-format #. Tag: entry msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" -#: hardware.xml:1340 +#: hardware.xml:1334 #, no-c-format #. Tag: entry msgid "PowerCenter / Pro, PowerCurve" msgstr "" -#: hardware.xml:1345 +#: hardware.xml:1339 #, no-c-format #. Tag: entry msgid "UMAX" msgstr "" -#: hardware.xml:1346 +#: hardware.xml:1340 #, no-c-format #. Tag: entry msgid "C500, C600, J700, S900" msgstr "" -#: hardware.xml:1351 +#: hardware.xml:1345 #, no-c-format #. Tag: entry msgid "<entry>APS</entry>" msgstr "" -#: hardware.xml:1352 +#: hardware.xml:1346 #, no-c-format #. Tag: entry msgid "APS Tech M*Power 604e/2000" msgstr "" -#: hardware.xml:1357 hardware.xml:1383 +#: hardware.xml:1351 hardware.xml:1377 #, no-c-format #. Tag: entry msgid "Motorola" msgstr "" -#: hardware.xml:1358 +#: hardware.xml:1352 #, no-c-format #. Tag: entry msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" -#: hardware.xml:1367 +#: hardware.xml:1361 #, no-c-format #. Tag: title msgid "PReP subarchitecture" msgstr "" -#: hardware.xml:1384 +#: hardware.xml:1378 #, no-c-format #. Tag: entry msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" -#: hardware.xml:1386 +#: hardware.xml:1380 #, no-c-format #. Tag: entry msgid "MPC 7xx, 8xx" msgstr "" -#: hardware.xml:1388 +#: hardware.xml:1382 #, no-c-format #. Tag: entry msgid "MTX, MTX+" msgstr "" -#: hardware.xml:1390 +#: hardware.xml:1384 #, no-c-format #. Tag: entry msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" -#: hardware.xml:1392 +#: hardware.xml:1386 #, no-c-format #. Tag: entry msgid "MCP(N)750" msgstr "" -#: hardware.xml:1396 hardware.xml:1427 +#: hardware.xml:1390 hardware.xml:1421 #, no-c-format #. Tag: entry msgid "IBM RS/6000" msgstr "" -#: hardware.xml:1397 +#: hardware.xml:1391 #, no-c-format #. Tag: entry msgid "40P, 43P" msgstr "" -#: hardware.xml:1399 +#: hardware.xml:1393 #, no-c-format #. Tag: entry msgid "Power 830/850/860 (6070, 6050)" msgstr "" -#: hardware.xml:1401 +#: hardware.xml:1395 #, no-c-format #. Tag: entry msgid "6030, 7025, 7043" msgstr "" -#: hardware.xml:1403 +#: hardware.xml:1397 #, no-c-format #. Tag: entry msgid "p640" msgstr "" -#: hardware.xml:1411 +#: hardware.xml:1405 #, no-c-format #. Tag: title msgid "CHRP subarchitecture" msgstr "" -#: hardware.xml:1428 +#: hardware.xml:1422 #, no-c-format #. Tag: entry msgid "B50, 43P-150, 44P" msgstr "" -#: hardware.xml:1431 +#: hardware.xml:1425 #, no-c-format #. Tag: entry msgid "Genesi" msgstr "" -#: hardware.xml:1432 +#: hardware.xml:1426 #, no-c-format #. Tag: entry msgid "Pegasos I, Pegasos II" msgstr "" -#: hardware.xml:1440 +#: hardware.xml:1434 #, no-c-format #. Tag: title msgid "APUS subarchitecture" msgstr "" -#: hardware.xml:1456 +#: hardware.xml:1450 #, no-c-format #. Tag: entry msgid "Amiga Power-UP Systems (APUS)" msgstr "" -#: hardware.xml:1457 +#: hardware.xml:1451 #, no-c-format #. Tag: entry msgid "A1200, A3000, A4000" msgstr "" -#: hardware.xml:1470 +#: hardware.xml:1464 #, no-c-format #. Tag: title msgid "S/390 and zSeries machine types" msgstr "" -#: hardware.xml:1471 +#: hardware.xml:1465 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1494 +#: hardware.xml:1488 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1514 +#: hardware.xml:1508 #, no-c-format #. Tag: title msgid "Memory Configuration" msgstr "" -#: hardware.xml:1515 +#: hardware.xml:1509 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1524 +#: hardware.xml:1518 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1532 +#: hardware.xml:1526 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1543 +#: hardware.xml:1537 #, no-c-format #. Tag: title msgid "Graphics Configuration" msgstr "" -#: hardware.xml:1544 +#: hardware.xml:1538 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1553 +#: hardware.xml:1547 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1561 +#: hardware.xml:1555 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1573 +#: hardware.xml:1567 #, no-c-format #. Tag: title msgid "Graphics Card" msgstr "" -#: hardware.xml:1575 +#: hardware.xml:1569 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1583 +#: hardware.xml:1577 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1592 +#: hardware.xml:1586 #, no-c-format #. Tag: para msgid "The X.Org X11 window system is only supported on the SGI Indy. The Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for the BCM91250A is available." msgstr "" -#: hardware.xml:1600 +#: hardware.xml:1594 #, no-c-format #. Tag: para msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for the BCM91250A is available." msgstr "" -#: hardware.xml:1612 +#: hardware.xml:1606 #, no-c-format #. Tag: title msgid "Laptops" msgstr "" -#: hardware.xml:1613 +#: hardware.xml:1607 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1625 hardware.xml:1650 hardware.xml:1673 +#: hardware.xml:1619 hardware.xml:1644 hardware.xml:1667 #, no-c-format #. Tag: title msgid "Multiple Processors" msgstr "" -#: hardware.xml:1627 +#: hardware.xml:1621 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is supported 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 "" -#: hardware.xml:1635 +#: hardware.xml:1629 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1651 +#: hardware.xml:1645 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is supported 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 "" -#: hardware.xml:1660 +#: hardware.xml:1654 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1674 +#: hardware.xml:1668 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is supported 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 "" -#: hardware.xml:1684 +#: hardware.xml:1678 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1705 +#: hardware.xml:1699 #, no-c-format #. Tag: title msgid "Installation Media" msgstr "" -#: hardware.xml:1707 +#: hardware.xml:1701 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1718 +#: hardware.xml:1712 #, no-c-format #. Tag: title msgid "Floppies" msgstr "" -#: hardware.xml:1719 +#: hardware.xml:1713 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1725 +#: hardware.xml:1719 #, no-c-format #. Tag: para msgid "For CHRP, floppy support is currently broken." msgstr "" -#: hardware.xml:1732 +#: hardware.xml:1726 #, no-c-format #. Tag: title msgid "CD-ROM/DVD-ROM" msgstr "" -#: hardware.xml:1734 +#: hardware.xml:1728 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1741 +#: hardware.xml:1735 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1753 +#: hardware.xml:1747 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1763 +#: hardware.xml:1757 #, no-c-format #. Tag: para msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" -#: hardware.xml:1768 +#: hardware.xml:1762 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1777 +#: hardware.xml:1771 #, no-c-format #. Tag: para msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." msgstr "" -#: hardware.xml:1782 +#: hardware.xml:1776 #, no-c-format #. Tag: para 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-DROM drives sold for 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." msgstr "" -#: hardware.xml:1795 +#: hardware.xml:1789 #, no-c-format #. Tag: para 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-DROM drives sold for 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 "" -#: hardware.xml:1804 +#: hardware.xml:1798 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1813 +#: hardware.xml:1807 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1825 +#: hardware.xml:1819 #, no-c-format #. Tag: userinput msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" -#: hardware.xml:1832 +#: hardware.xml:1826 #, no-c-format #. Tag: title msgid "Hard Disk" msgstr "" -#: hardware.xml:1834 +#: hardware.xml:1828 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1840 +#: hardware.xml:1834 #, no-c-format #. Tag: para msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" -#: hardware.xml:1845 +#: hardware.xml:1839 #, no-c-format #. Tag: para msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" -#: hardware.xml:1853 +#: hardware.xml:1847 #, no-c-format #. Tag: title msgid "USB Memory Stick" msgstr "" -#: hardware.xml:1855 +#: hardware.xml:1849 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1867 +#: hardware.xml:1861 #, no-c-format #. Tag: title msgid "Network" msgstr "" -#: hardware.xml:1869 +#: hardware.xml:1863 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1875 +#: hardware.xml:1869 #, no-c-format #. Tag: para msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" -#: hardware.xml:1880 +#: hardware.xml:1874 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1889 +#: hardware.xml:1883 #, no-c-format #. Tag: title msgid "Un*x or GNU system" msgstr "" -#: hardware.xml:1891 +#: hardware.xml:1885 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1903 +#: hardware.xml:1897 #, no-c-format #. Tag: title msgid "Supported Storage Systems" msgstr "" -#: hardware.xml:1905 +#: hardware.xml:1899 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1915 +#: hardware.xml:1909 #, no-c-format #. Tag: para 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 file systems supported include FAT, Win-32 FAT extensions (VFAT), and NTFS, among others." msgstr "" -#: hardware.xml:1922 +#: hardware.xml:1916 #, no-c-format #. Tag: para msgid "The disk interfaces that emulate the <quote>AT</quote> hard disk interface which are 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 "" -#: hardware.xml:1932 +#: hardware.xml:1926 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1942 +#: hardware.xml:1936 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1975 +#: hardware.xml:1969 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1984 +#: hardware.xml:1978 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1990 +#: hardware.xml:1984 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1996 +#: hardware.xml:1990 #, no-c-format #. Tag: para msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" -#: hardware.xml:2001 +#: hardware.xml:1995 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2018 +#: hardware.xml:2012 #, no-c-format #. Tag: title msgid "Peripherals and Other Hardware" msgstr "" -#: hardware.xml:2019 +#: hardware.xml:2013 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2025 +#: hardware.xml:2019 #, no-c-format #. Tag: para msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" -#: hardware.xml:2031 +#: hardware.xml:2025 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2037 +#: hardware.xml:2031 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2043 +#: hardware.xml:2037 #, no-c-format #. Tag: para msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors." msgstr "" -#: hardware.xml:2048 +#: hardware.xml:2042 #, no-c-format #. Tag: para msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" -#: hardware.xml:2057 +#: hardware.xml:2051 #, no-c-format #. Tag: title msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" -#: hardware.xml:2059 +#: hardware.xml:2053 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2067 +#: hardware.xml:2061 #, no-c-format #. Tag: para msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" -#: hardware.xml:2072 +#: hardware.xml:2066 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2080 +#: hardware.xml:2074 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2091 +#: hardware.xml:2085 #, no-c-format #. Tag: title msgid "Avoid Proprietary or Closed Hardware" msgstr "" -#: hardware.xml:2092 +#: hardware.xml:2086 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2099 +#: hardware.xml:2093 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2110 +#: hardware.xml:2104 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2122 +#: hardware.xml:2116 #, no-c-format #. Tag: title msgid "Windows-specific Hardware" msgstr "" -#: hardware.xml:2123 +#: hardware.xml:2117 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2136 +#: hardware.xml:2130 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2157 +#: hardware.xml:2151 #, no-c-format #. Tag: para msgid "You can help 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 "" -#: hardware.xml:2170 +#: hardware.xml:2164 #, no-c-format #. Tag: title msgid "Fake or <quote>Virtual</quote> Parity RAM" msgstr "" -#: hardware.xml:2171 +#: hardware.xml:2165 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2186 +#: hardware.xml:2180 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2192 +#: hardware.xml:2186 #, no-c-format #. Tag: para msgid "Most, if not all, Alpha systems require true-parity RAM." msgstr "" -#: hardware.xml:2207 +#: hardware.xml:2201 #, no-c-format #. Tag: title msgid "Memory and Disk Space Requirements" msgstr "" -#: hardware.xml:2209 +#: hardware.xml:2203 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2218 +#: hardware.xml:2212 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2227 +#: hardware.xml:2221 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2235 +#: hardware.xml:2229 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2245 +#: hardware.xml:2239 #, no-c-format #. Tag: emphasis msgid "FIXME: is this still true?" msgstr "" -#: hardware.xml:2256 +#: hardware.xml:2250 #, no-c-format #. Tag: title msgid "Network Connectivity Hardware" msgstr "" -#: hardware.xml:2258 +#: hardware.xml:2252 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2277 +#: hardware.xml:2271 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2285 +#: hardware.xml:2279 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2294 +#: hardware.xml:2288 #, no-c-format #. Tag: para msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" msgstr "" -#: hardware.xml:2300 +#: hardware.xml:2294 #, no-c-format #. Tag: para msgid "Sun LANCE" msgstr "" -#: hardware.xml:2306 +#: hardware.xml:2300 #, no-c-format #. Tag: para msgid "Sun Happy Meal" msgstr "" -#: hardware.xml:2314 +#: hardware.xml:2308 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2322 +#: hardware.xml:2316 #, no-c-format #. Tag: para msgid "Sun BigMAC" msgstr "" -#: hardware.xml:2328 +#: hardware.xml:2322 #, no-c-format #. Tag: para msgid "Sun QuadEthernet" msgstr "" -#: hardware.xml:2333 +#: hardware.xml:2327 #, no-c-format #. Tag: para msgid "MyriCOM Gigabit Ethernet" msgstr "" -#: hardware.xml:2340 hardware.xml:2346 hardware.xml:2352 hardware.xml:2358 hardware.xml:2364 +#: hardware.xml:2334 hardware.xml:2340 hardware.xml:2346 hardware.xml:2352 hardware.xml:2358 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2370 +#: hardware.xml:2364 #, no-c-format #. Tag: para msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" -#: hardware.xml:2376 +#: hardware.xml:2370 #, no-c-format #. Tag: para msgid "Any network interface card (NIC) supported by the Linux kernel are 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 "" -#: hardware.xml:2384 +#: hardware.xml:2378 #, no-c-format #. Tag: para msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" -#: hardware.xml:2389 +#: hardware.xml:2383 #, no-c-format #. Tag: para msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" -#: hardware.xml:2394 +#: hardware.xml:2388 #, no-c-format #. Tag: para msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" msgstr "" -#: hardware.xml:2399 +#: hardware.xml:2393 #, no-c-format #. Tag: para msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" -#: hardware.xml:2408 +#: hardware.xml:2402 #, no-c-format #. Tag: para -msgid "The following network interface cards are supported directly by the boot disks on NetWinder and CATS machines:" +msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" msgstr "" -#: hardware.xml:2414 +#: hardware.xml:2408 #, no-c-format #. Tag: para msgid "PCI-based NE2000" msgstr "" -#: hardware.xml:2420 +#: hardware.xml:2414 #, no-c-format #. Tag: para msgid "DECchip Tulip" msgstr "" -#: hardware.xml:2427 +#: hardware.xml:2421 #, no-c-format #. Tag: para msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" msgstr "" -#: hardware.xml:2433 +#: hardware.xml:2427 #, no-c-format #. Tag: para msgid "Ether1" msgstr "" -#: hardware.xml:2438 +#: hardware.xml:2432 #, no-c-format #. Tag: para msgid "Ether3" msgstr "" -#: hardware.xml:2443 +#: hardware.xml:2437 #, no-c-format #. Tag: para msgid "EtherH" msgstr "" -#: hardware.xml:2450 +#: hardware.xml:2444 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2456 +#: hardware.xml:2450 #, no-c-format #. Tag: para 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." |