# Debian GNU/Linux Installation Guide msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2007-01-06 19:06+0000\n" "PO-Revision-Date: 2007-01-09 10:38+0800\n" "Last-Translator: Ji YongGang\n" "Language-Team: debian-chinese-gb \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #: hardware.xml:5 #, no-c-format msgid "System Requirements" msgstr "系统需求" #. Tag: para #: hardware.xml:7 #, no-c-format msgid "" "This section contains information about what hardware you need to get " "started with Debian. You will also find links to further information about " "hardware supported by GNU and Linux." msgstr "" "本章包括运行 Debian 所需硬件的信息。您还能找到更多有关 GNU 和 Linux 所支持硬" "件的信息的链接。" #. Tag: title #: hardware.xml:20 #, no-c-format msgid "Supported Hardware" msgstr "支持的硬件" #. Tag: para #: hardware.xml:21 #, no-c-format msgid "" "Debian does not impose hardware requirements beyond the requirements of the " "Linux kernel and the GNU tool-sets. Therefore, any architecture or platform " "to which the Linux kernel, libc, gcc, etc. have been " "ported, and for which a Debian port exists, can run Debian. Please refer to " "the Ports pages at for more details on " "&arch-title; architecture systems which have been tested with Debian." msgstr "" "Debian 不会超出 Linux 内核与 GNU 工具集所支持的硬件范围之外。因此,任何被移植" "了 Linux 内核,libc,gcc 等,并拥有对应的 Debian 移植版的" "硬件体系或平台都可以运行 Debian。请参考移植页面 以了解更多已被 Debian 测试过的 &arch-title; 体系。" #. Tag: para #: hardware.xml:32 #, no-c-format msgid "" "Rather than attempting to describe all the different hardware configurations " "which are supported for &arch-title;, this section contains general " "information and pointers to where additional information can be found." msgstr "" "本章仅包含一些通用的信息以及在何处可以获得更多信息的指导,而不是试图列出支持 " "&arch-title; 的所有不同硬件配置。" #. Tag: title #: hardware.xml:41 #, no-c-format msgid "Supported Architectures" msgstr "支持的体系" #. Tag: para #: hardware.xml:42 #, no-c-format msgid "" "Debian &release; supports twelve major architectures and several variations " "of each architecture known as flavors." msgstr "" "Debian &release; 支持十二种主要的体系和一些称为 flavors 的变" "种。" #. Tag: entry #: hardware.xml:53 #, no-c-format msgid "Architecture" msgstr "体系" #. Tag: entry #: hardware.xml:53 #, no-c-format msgid "Debian Designation" msgstr "Debian 命名" #. Tag: entry #: hardware.xml:54 #, no-c-format msgid "Subarchitecture" msgstr "子体系" #. Tag: entry #: hardware.xml:54 #, no-c-format msgid "Flavor" msgstr "Flavor" #. Tag: entry #: hardware.xml:60 #, no-c-format msgid "Intel x86-based" msgstr "Intel x86-based" #. Tag: entry #: hardware.xml:61 #, no-c-format msgid "i386" msgstr "i386" #. Tag: entry #: hardware.xml:67 #, no-c-format msgid "AMD64 & Intel EM64T" msgstr "AMD64 & Intel EM64T" #. Tag: entry #: hardware.xml:68 #, no-c-format msgid "amd64" msgstr "amd64" #. Tag: entry #: hardware.xml:74 #, no-c-format msgid "DEC Alpha" msgstr "DEC Alpha" #. Tag: entry #: hardware.xml:75 #, no-c-format msgid "alpha" msgstr "alpha" #. Tag: entry #: hardware.xml:81 #, no-c-format msgid "ARM and StrongARM" msgstr "ARM and StrongARM" #. Tag: entry #: hardware.xml:82 #, no-c-format msgid "arm" msgstr "arm" #. Tag: entry #: hardware.xml:83 #, no-c-format msgid "Netwinder and CATS" msgstr "Netwinder 与 CATS" #. Tag: entry #: hardware.xml:84 #, no-c-format msgid "netwinder" msgstr "netwinder" #. Tag: entry #: hardware.xml:86 #, no-c-format msgid "Intel IOP32x" msgstr "Intel IOP32x" #. Tag: entry #: hardware.xml:87 #, no-c-format msgid "iop32x" msgstr "iop32x" #. Tag: entry #: hardware.xml:89 #, no-c-format msgid "Intel IXP4xx" msgstr "Intel IXP4xx" #. Tag: entry #: hardware.xml:90 #, no-c-format msgid "ixp4xx" msgstr "ixp4xx" #. Tag: entry #: hardware.xml:92 #, no-c-format msgid "RiscPC" msgstr "RiscPC" #. Tag: entry #: hardware.xml:93 #, no-c-format msgid "rpc" msgstr "rpc" #. Tag: entry #: hardware.xml:97 #, no-c-format msgid "HP PA-RISC" msgstr "HP PA-RISC" #. Tag: entry #: hardware.xml:98 #, no-c-format msgid "hppa" msgstr "hppa" #. Tag: entry #: hardware.xml:99 #, no-c-format msgid "PA-RISC 1.1" msgstr "PA-RISC 1.1" #. Tag: entry #: hardware.xml:100 #, no-c-format msgid "32" msgstr "32" #. Tag: entry #: hardware.xml:102 #, no-c-format msgid "PA-RISC 2.0" msgstr "PA-RISC 2.0" #. Tag: entry #: hardware.xml:103 #, no-c-format msgid "64" msgstr "64" #. Tag: entry #: hardware.xml:107 #, no-c-format msgid "Intel IA-64" msgstr "Intel IA-64" #. Tag: entry #: hardware.xml:108 #, no-c-format msgid "ia64" msgstr "ia64" #. Tag: entry #: hardware.xml:114 #, no-c-format msgid "MIPS (big endian)" msgstr "MIPS (big endian)" #. Tag: entry #: hardware.xml:115 #, no-c-format msgid "mips" msgstr "mips" #. Tag: entry #: hardware.xml:116 #, no-c-format msgid "SGI IP22 (Indy/Indigo 2)" msgstr "SGI IP22 (Indy/Indigo 2)" #. Tag: entry #: hardware.xml:117 #, no-c-format msgid "r4k-ip22" msgstr "r4k-ip22" #. Tag: entry #: hardware.xml:119 #, no-c-format msgid "SGI IP32 (O2)" msgstr "SGI IP32 (O2)" #. Tag: entry #: hardware.xml:120 #, no-c-format msgid "r5k-ip32" msgstr "r5k-ip32" # index.docbook:162, index.docbook:177 #. Tag: entry #: hardware.xml:122 hardware.xml:140 #, no-c-format msgid "Broadcom BCM91250A (SWARM)" msgstr "Broadcom BCM91250A (SQARM)" # index.docbook:163, index.docbook:178 #. Tag: entry #: hardware.xml:123 hardware.xml:141 #, no-c-format msgid "sb1-bcm91250a" msgstr "sb1-bcm91250a" # index.docbook:162, index.docbook:177 #. Tag: entry #: hardware.xml:125 hardware.xml:143 #, no-c-format msgid "Broadcom BCM91480B (BigSur)" msgstr "Broadcom BCM91480B (BigSur)" # index.docbook:163, index.docbook:178 #. Tag: entry #: hardware.xml:126 hardware.xml:144 #, no-c-format msgid "sb1a-bcm91480b" msgstr "sb1a-bcm91480b" #. Tag: entry #: hardware.xml:130 #, no-c-format msgid "MIPS (little endian)" msgstr "MIPS (little endian)" #. Tag: entry #: hardware.xml:131 #, no-c-format msgid "mipsel" msgstr "mipsel" #. Tag: entry #: hardware.xml:132 #, no-c-format msgid "Cobalt" msgstr "Cobalt" #. Tag: entry #: hardware.xml:133 #, no-c-format msgid "cobalt" msgstr "cobalt" #. Tag: entry #: hardware.xml:135 #, no-c-format msgid "DECstation" msgstr "DECstation" # index.docbook:173, index.docbook:1002, index.docbook:1017, index.docbook:1027 #. Tag: entry #: hardware.xml:136 hardware.xml:1109 hardware.xml:1124 hardware.xml:1134 #, no-c-format msgid "r4k-kn04" msgstr "r4k-kn04" # index.docbook:175, index.docbook:997, index.docbook:1007, index.docbook:1012, index.docbook:1022 #. Tag: entry #: hardware.xml:138 hardware.xml:1104 hardware.xml:1114 hardware.xml:1119 #: hardware.xml:1129 #, no-c-format msgid "r3k-kn02" msgstr "r3k-kn02" #. Tag: entry #: hardware.xml:148 #, no-c-format msgid "Motorola 680x0" msgstr "Motorola 680x0" #. Tag: entry #: hardware.xml:149 #, no-c-format msgid "m68k" msgstr "m68k" #. Tag: entry #: hardware.xml:150 #, no-c-format msgid "Atari" msgstr "Atari" #. Tag: entry #: hardware.xml:151 #, no-c-format msgid "atari" msgstr "atari" #. Tag: entry #: hardware.xml:153 #, no-c-format msgid "Amiga" msgstr "Amiga" #. Tag: entry #: hardware.xml:154 #, no-c-format msgid "amiga" msgstr "amiga" #. Tag: entry #: hardware.xml:156 #, no-c-format msgid "68k Macintosh" msgstr "68k Macintosh" #. Tag: entry #: hardware.xml:157 #, no-c-format msgid "mac" msgstr "mac" #. Tag: entry #: hardware.xml:159 #, no-c-format msgid "VME" msgstr "VME" #. Tag: entry #: hardware.xml:160 #, no-c-format msgid "bvme6000" msgstr "bvme6000" #. Tag: entry #: hardware.xml:162 #, no-c-format msgid "mvme147" msgstr "mvme147" #. Tag: entry #: hardware.xml:164 #, no-c-format msgid "mvme16x" msgstr "mvme16x" #. Tag: entry #: hardware.xml:168 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "IBM/Motorola PowerPC" #. Tag: entry #: hardware.xml:169 #, no-c-format msgid "powerpc" msgstr "powerpc" #. Tag: entry #: hardware.xml:170 #, no-c-format msgid "CHRP" msgstr "CHRP" #. Tag: entry #: hardware.xml:171 #, no-c-format msgid "chrp" msgstr "chrp" #. Tag: entry #: hardware.xml:173 #, no-c-format msgid "PowerMac" msgstr "PowerMac" #. Tag: entry #: hardware.xml:174 #, no-c-format msgid "pmac" msgstr "pmac" #. Tag: entry #: hardware.xml:176 #, no-c-format msgid "PReP" msgstr "PReP" #. Tag: entry #: hardware.xml:177 #, no-c-format msgid "prep" msgstr "prep" #. Tag: entry #: hardware.xml:181 #, no-c-format msgid "Sun SPARC" msgstr "Sun SPARC" #. Tag: entry #: hardware.xml:182 #, no-c-format msgid "sparc" msgstr "sparc" #. Tag: entry #: hardware.xml:183 #, no-c-format msgid "sun4m" msgstr "sun4m" #. Tag: entry #: hardware.xml:184 #, no-c-format msgid "sparc32" msgstr "sparc32" #. Tag: entry #: hardware.xml:186 #, no-c-format msgid "sun4u" msgstr "sun4u" #. Tag: entry #: hardware.xml:187 #, no-c-format msgid "sparc64" msgstr "sparc64" #. Tag: entry #: hardware.xml:189 #, no-c-format msgid "sun4v" msgstr "sun4v" #. Tag: entry #: hardware.xml:193 #, no-c-format msgid "IBM S/390" msgstr "IBM S/390" #. Tag: entry #: hardware.xml:194 #, no-c-format msgid "s390" msgstr "s390" #. Tag: entry #: hardware.xml:195 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "IPL from VM-reader and DASD" #. Tag: entry #: hardware.xml:196 #, no-c-format msgid "generic" msgstr "generic" #. Tag: entry #: hardware.xml:198 #, no-c-format msgid "IPL from tape" msgstr "IPL from tape" #. Tag: entry #: hardware.xml:199 #, no-c-format msgid "tape" msgstr "type" #. Tag: para #: hardware.xml:204 #, no-c-format msgid "" "This document covers installation for the &arch-title; " "architecture. If you are looking for information on any of the other Debian-" "supported architectures take a look at the Debian-Ports pages." msgstr "" "本文档主要讲述的是 &arch-title; 体系下的安装。如果您在寻" "找其他 Debian 所支持的体系的信息,请浏览 Debian 移植 页面。" #. Tag: para #: hardware.xml:212 #, 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 Bug Tracking System 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 debian-&arch-listname; mailing list as well." msgstr "" "此为第一个 &arch-title; 体系的 &debian; 官方发布版。我们认为它已经达到了可发" "布的质量要求。但是,由于它没有像其他体系那样得到足够的曝光(经过用户测试),您" "可能会遇到一些 bug。请使用我们的 Bug 跟踪系统 来报告问题,并注明该 bug 是在 &arch-title; 平台上产生的。当然,您也可" "以使用 debian-&arch-listname; 邮件列表 来进行讨论。" # index.docbook:224, index.docbook:683, index.docbook:780, index.docbook:799, index.docbook:842, index.docbook:884, index.docbook:938, index.docbook:1085, index.docbook:1491 #. Tag: title #: hardware.xml:234 hardware.xml:693 hardware.xml:729 hardware.xml:824 #: hardware.xml:843 hardware.xml:929 hardware.xml:971 hardware.xml:1039 #: hardware.xml:1198 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "CPU,主板和视频支持" #. Tag: para #: hardware.xml:235 #, no-c-format msgid "" "Complete information regarding supported DEC Alphas can be found at Linux Alpha HOWTO. The purpose of this " "section is to describe the systems supported by the boot disks." msgstr "" "完整的 DEC Alphas 支持情况信息可以在 Linux " "Alpha HOWTO 中找到。本节是描述启动盘对系统支持的概况。" #. Tag: para #: hardware.xml:242 #, no-c-format msgid "" "Alpha machines are subdivided into different system types because there are " "a number of generations of motherboard and supporting chipsets. Different " "systems (sub-architectures) often have radically different " "engineering and capabilities. Therefore, the process of installing and, more " "to the point, booting, can vary from system to system." msgstr "" "由于有很多世代的主板和支持芯片,Alpha 机器可以细分成不同的系统。不同的系统" "(子体系(sub-architectures))通常具有完全不同的工程设计与运行效" "能。因此,安装过程,更准确地说是启动过程,会因系统不同而不同。" #. Tag: para #: hardware.xml:250 #, no-c-format msgid "" "The following table lists the system types supported by the Debian " "installation system. The table also indicates the code name for these system types. You'll need to know this code name when " "you actually begin the installation process:" msgstr "" "以下表格中列出 Debian 安装系统所支持的系统类型。表格中还指出这些系统类型的 " "代号(code name)。当开始安装时,您需要知道这些代号。" #. Tag: entry #: hardware.xml:267 #, no-c-format msgid "Hardware Type" msgstr "硬件类型" #. Tag: entry #: hardware.xml:268 #, no-c-format msgid "Aliases" msgstr "别名" #. Tag: entry #: hardware.xml:268 #, no-c-format msgid "MILO image" msgstr "MILO image" #. Tag: entry #: hardware.xml:274 #, no-c-format msgid "ALCOR" msgstr "ALCOR" #. Tag: entry #: hardware.xml:275 #, no-c-format msgid "AlphaStation 500 5/266.300" msgstr "AlphaStation 500 5/266.300" #. Tag: entry #: hardware.xml:276 #, no-c-format msgid "Maverick" msgstr "Maverick" # index.docbook:267, index.docbook:271, index.docbook:275 #. Tag: entry #: hardware.xml:277 hardware.xml:281 hardware.xml:285 #, no-c-format msgid "alcor" msgstr "alcor" #. Tag: entry #: hardware.xml:279 #, no-c-format msgid "AlphaStation 500 5/333...500" msgstr "AlphaStation 500 5/333...500" #. Tag: entry #: hardware.xml:280 #, no-c-format msgid "Bret" msgstr "Bret" #. Tag: entry #: hardware.xml:283 #, no-c-format msgid "AlphaStation 600/266...300" msgstr "AlphaStation 600/266...300" #. Tag: entry #: hardware.xml:284 #, no-c-format msgid "Alcor" msgstr "Alcor" #. Tag: entry #: hardware.xml:287 #, no-c-format msgid "AlphaStation 600/300...433" msgstr "AlphaStation 600/300...433" #. Tag: entry #: hardware.xml:288 #, no-c-format msgid "XLT" msgstr "XLT" #. Tag: entry #: hardware.xml:289 #, no-c-format msgid "xlt" msgstr "xlt" #. Tag: entry #: hardware.xml:293 #, no-c-format msgid "BOOK1" msgstr "BOOK1" #. Tag: entry #: hardware.xml:294 #, no-c-format msgid "AlphaBook1 (laptop)" msgstr "AlphaBook1 (laptop)" #. Tag: entry #: hardware.xml:295 #, no-c-format msgid "Alphabook1/Burns" msgstr "Alphabook1/Burns" #. Tag: entry #: hardware.xml:296 #, no-c-format msgid "book1" msgstr "book1" #. Tag: entry #: hardware.xml:300 #, no-c-format msgid "AVANTI" msgstr "AVANTI" #. Tag: entry #: hardware.xml:301 #, no-c-format msgid "AlphaStation 200 4/100...166" msgstr "AlphaStation 200 4/100...166" #. Tag: entry #: hardware.xml:302 #, no-c-format msgid "Mustang" msgstr "Mustang" # index.docbook:293, index.docbook:297, index.docbook:301, index.docbook:305, index.docbook:309, index.docbook:313, index.docbook:317, index.docbook:321 #. Tag: entry #: hardware.xml:303 hardware.xml:307 hardware.xml:311 hardware.xml:315 #: hardware.xml:319 hardware.xml:323 hardware.xml:327 hardware.xml:331 #, no-c-format msgid "avanti" msgstr "avanti" #. Tag: entry #: hardware.xml:305 #, no-c-format msgid "AlphaStation 200 4/233" msgstr "AlphaStation 200 4/233" #. Tag: entry #: hardware.xml:306 #, no-c-format msgid "Mustang+" msgstr "Mustang+" #. Tag: entry #: hardware.xml:309 #, no-c-format msgid "AlphaStation 205 4/133...333" msgstr "AlphaStation 205 4/133...333" #. Tag: entry #: hardware.xml:310 #, no-c-format msgid "LX3" msgstr "LX3" #. Tag: entry #: hardware.xml:313 #, no-c-format msgid "AlphaStation 250 4/300" msgstr "AlphaStation 250 4/300" #. Tag: entry #: hardware.xml:314 #, no-c-format msgid "M3+" msgstr "M3+" #. Tag: entry #: hardware.xml:317 #, no-c-format msgid "AlphaStation 255 4/133...333" msgstr "AlphaStation 255 4/133...333" #. Tag: entry #: hardware.xml:318 #, no-c-format msgid "LX3+" msgstr "LX3+" #. Tag: entry #: hardware.xml:321 #, no-c-format msgid "AlphaStation 300 4/266" msgstr "AlphaStation 300 4/266" #. Tag: entry #: hardware.xml:322 #, no-c-format msgid "Melmac" msgstr "Melmac" #. Tag: entry #: hardware.xml:325 #, no-c-format msgid "AlphaStation 400 4/166" msgstr "AlphaStation 400 4/166" #. Tag: entry #: hardware.xml:326 #, no-c-format msgid "Chinet" msgstr "Chinet" #. Tag: entry #: hardware.xml:329 #, no-c-format msgid "AlphaStation 400 4/233...300" msgstr "AlphaStation 400 4/233...300" #. Tag: entry #: hardware.xml:330 #, no-c-format msgid "Avanti" msgstr "Avanti" # index.docbook:325, index.docbook:338, index.docbook:339 #. Tag: entry #: hardware.xml:335 hardware.xml:348 hardware.xml:349 #, no-c-format msgid "EB164" msgstr "EB164" #. Tag: entry #: hardware.xml:336 #, no-c-format msgid "AlphaPC164" msgstr "AlphaPC164" #. Tag: entry #: hardware.xml:337 #, no-c-format msgid "PC164" msgstr "PC164" #. Tag: entry #: hardware.xml:338 #, no-c-format msgid "pc164" msgstr "pc164" #. Tag: entry #: hardware.xml:340 #, no-c-format msgid "AlphaPC164-LX" msgstr "AlphaPC164-LX" #. Tag: entry #: hardware.xml:341 #, no-c-format msgid "LX164" msgstr "LX164" #. Tag: entry #: hardware.xml:342 #, no-c-format msgid "lx164" msgstr "lx164" #. Tag: entry #: hardware.xml:344 #, no-c-format msgid "AlphaPC164-SX" msgstr "AlphaPC164-SX" #. Tag: entry #: hardware.xml:345 #, no-c-format msgid "SX164" msgstr "SX164" #. Tag: entry #: hardware.xml:346 #, no-c-format msgid "sx164" msgstr "sx164" #. Tag: entry #: hardware.xml:350 #, no-c-format msgid "eb164" msgstr "eb164" # index.docbook:344, index.docbook:353, index.docbook:354 #. Tag: entry #: hardware.xml:354 hardware.xml:363 hardware.xml:364 #, no-c-format msgid "EB64+" msgstr "EB64+" #. Tag: entry #: hardware.xml:355 #, no-c-format msgid "AlphaPC64" msgstr "AlphaPC64" # index.docbook:346, index.docbook:350 #. Tag: entry #: hardware.xml:356 hardware.xml:360 #, no-c-format msgid "Cabriolet" msgstr "Cabriolet" # index.docbook:347, index.docbook:351 #. Tag: entry #: hardware.xml:357 hardware.xml:361 #, no-c-format msgid "cabriolet" msgstr "cabriolet" #. Tag: entry #: hardware.xml:359 #, no-c-format msgid "AlphaPCI64" msgstr "AlphaPCI64" #. Tag: entry #: hardware.xml:365 #, no-c-format msgid "eb64p" msgstr "eb64p" # index.docbook:359, index.docbook:360, index.docbook:361 #. Tag: entry #: hardware.xml:369 hardware.xml:370 hardware.xml:371 #, no-c-format msgid "EB66" msgstr "EB66" #. Tag: entry #: hardware.xml:372 #, no-c-format msgid "eb66" msgstr "eb66" # index.docbook:364, index.docbook:365 #. Tag: entry #: hardware.xml:374 hardware.xml:375 #, no-c-format msgid "EB66+" msgstr "EB66+" #. Tag: entry #: hardware.xml:376 #, no-c-format msgid "eb66p" msgstr "eb66p" #. Tag: entry #: hardware.xml:380 #, no-c-format msgid "JENSEN" msgstr "JENSEN" #. Tag: entry #: hardware.xml:381 #, no-c-format msgid "DEC 2000 Model 300(S)" msgstr "DEC 2000 Model 300(S)" # index.docbook:372, index.docbook:380 #. Tag: entry #: hardware.xml:382 hardware.xml:390 #, no-c-format msgid "Jensen" msgstr "Jensen" # index.docbook:373, index.docbook:377, index.docbook:381, index.docbook:442, index.docbook:446, index.docbook:464, index.docbook:468, index.docbook:472, index.docbook:476, index.docbook:480, index.docbook:484, index.docbook:488, index.docbook:502, index.docbook:506, index.docbook:510, index.docbook:514, index.docbook:518, index.docbook:552, index.docbook:556, index.docbook:560, index.docbook:564, index.docbook:578, index.docbook:582, index.docbook:586, index.docbook:590, index.docbook:597, index.docbook:601, index.docbook:605, index.docbook:609, index.docbook:613, index.docbook:617, index.docbook:621, index.docbook:625, index.docbook:629, index.docbook:633, index.docbook:637, index.docbook:641, index.docbook:645, index.docbook:652, index.docbook:656 #. Tag: entry #: hardware.xml:383 hardware.xml:387 hardware.xml:391 hardware.xml:452 #: hardware.xml:456 hardware.xml:474 hardware.xml:478 hardware.xml:482 #: hardware.xml:486 hardware.xml:490 hardware.xml:494 hardware.xml:498 #: hardware.xml:512 hardware.xml:516 hardware.xml:520 hardware.xml:524 #: hardware.xml:528 hardware.xml:562 hardware.xml:566 hardware.xml:570 #: hardware.xml:574 hardware.xml:588 hardware.xml:592 hardware.xml:596 #: hardware.xml:600 hardware.xml:607 hardware.xml:611 hardware.xml:615 #: hardware.xml:619 hardware.xml:623 hardware.xml:627 hardware.xml:631 #: hardware.xml:635 hardware.xml:639 hardware.xml:643 hardware.xml:647 #: hardware.xml:651 hardware.xml:655 hardware.xml:662 hardware.xml:666 #, no-c-format msgid "N/A" msgstr "N/A" #. Tag: entry #: hardware.xml:385 #, no-c-format msgid "DEC 2000 Model 500" msgstr "DEC 2000 Model 500" #. Tag: entry #: hardware.xml:386 #, no-c-format msgid "Culzen" msgstr "Culzen" #. Tag: entry #: hardware.xml:389 #, no-c-format msgid "DECpc 150" msgstr "DECpc 150" #. Tag: entry #: hardware.xml:395 #, no-c-format msgid "MIATA" msgstr "MIATA" #. Tag: entry #: hardware.xml:396 #, no-c-format msgid "Personal WorkStation 433a" msgstr "Personal WorkStation 433a" # index.docbook:387, index.docbook:391, index.docbook:395, index.docbook:399, index.docbook:403, index.docbook:407, index.docbook:411, index.docbook:415 #. Tag: entry #: hardware.xml:397 hardware.xml:401 hardware.xml:405 hardware.xml:409 #: hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 #, no-c-format msgid "Miata" msgstr "Miata" # index.docbook:388, index.docbook:392, index.docbook:396, index.docbook:400, index.docbook:404, index.docbook:408, index.docbook:412, index.docbook:416 #. Tag: entry #: hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 #: hardware.xml:414 hardware.xml:418 hardware.xml:422 hardware.xml:426 #, no-c-format msgid "miata" msgstr "miata" #. Tag: entry #: hardware.xml:400 #, no-c-format msgid "Personal WorkStation 433au" msgstr "Personal WorkStation 433au" #. Tag: entry #: hardware.xml:404 #, no-c-format msgid "Personal WorkStation 466au" msgstr "Personal WorkStation 466au" #. Tag: entry #: hardware.xml:408 #, no-c-format msgid "Personal WorkStation 500a" msgstr "Personal WorkStation 500a" #. Tag: entry #: hardware.xml:412 #, no-c-format msgid "Personal WorkStation 500au" msgstr "Personal WorkStation 500au" #. Tag: entry #: hardware.xml:416 #, no-c-format msgid "Personal WorkStation 550au" msgstr "Personal WorkStation 550au" #. Tag: entry #: hardware.xml:420 #, no-c-format msgid "Personal WorkStation 600a" msgstr "Personal WorkStation 600a" #. Tag: entry #: hardware.xml:424 #, no-c-format msgid "Personal WorkStation 600au" msgstr "Personal WorkStation 600au" #. Tag: entry #: hardware.xml:430 #, no-c-format msgid "MIKASA" msgstr "MIKASA" #. Tag: entry #: hardware.xml:431 #, no-c-format msgid "AlphaServer 1000 4/200" msgstr "AlphaServer 1000 4/200" #. Tag: entry #: hardware.xml:432 #, no-c-format msgid "Mikasa" msgstr "Mikasa" # index.docbook:423, index.docbook:427, index.docbook:431, index.docbook:435 #. Tag: entry #: hardware.xml:433 hardware.xml:437 hardware.xml:441 hardware.xml:445 #, no-c-format msgid "mikasa" msgstr "mikasa" #. Tag: entry #: hardware.xml:435 #, no-c-format msgid "AlphaServer 1000 4/233..266" msgstr "AlphaServer 1000 4/233..266" #. Tag: entry #: hardware.xml:436 #, no-c-format msgid "Mikasa+" msgstr "Mikasa+" # index.docbook:429, index.docbook:433 #. Tag: entry #: hardware.xml:439 hardware.xml:443 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "AlphaServer 1000 5/300" #. Tag: entry #: hardware.xml:440 #, no-c-format msgid "Mikasa-Pinnacle" msgstr "Mikasa-Pinnacle" #. Tag: entry #: hardware.xml:444 #, no-c-format msgid "Mikasa-Primo" msgstr "Mikasa-Primo" #. Tag: entry #: hardware.xml:449 #, no-c-format msgid "NAUTILUS" msgstr "NAUTILUS" #. Tag: entry #: hardware.xml:450 #, no-c-format msgid "UP1000" msgstr "UP1000" #. Tag: entry #: hardware.xml:451 #, no-c-format msgid "Nautilus" msgstr "Nautilus" #. Tag: entry #: hardware.xml:454 #, no-c-format msgid "UP1100" msgstr "UP1100" #. Tag: entry #: hardware.xml:455 #, no-c-format msgid "Galaxy-Train/Nautilus Jr." msgstr "Galaxy-Train/Nautilus Jr." #. Tag: entry #: hardware.xml:460 #, no-c-format msgid "NONAME" msgstr "NONAME" #. Tag: entry #: hardware.xml:461 #, no-c-format msgid "AXPpci33" msgstr "AXPpci33" #. Tag: entry #: hardware.xml:462 #, no-c-format msgid "Noname" msgstr "Noname" # index.docbook:453, index.docbook:457 #. Tag: entry #: hardware.xml:463 hardware.xml:467 #, no-c-format msgid "noname" msgstr "noname" #. Tag: entry #: hardware.xml:465 #, no-c-format msgid "UDB" msgstr "UDB" #. Tag: entry #: hardware.xml:466 #, no-c-format msgid "Multia" msgstr "Multia" #. Tag: entry #: hardware.xml:471 #, no-c-format msgid "NORITAKE" msgstr "NORITAKE" #. Tag: entry #: hardware.xml:472 #, no-c-format msgid "AlphaServer 1000A 4/233...266" msgstr "AlphaServer 1000A 4/233...266" #. Tag: entry #: hardware.xml:473 #, no-c-format msgid "Noritake" msgstr "Noritake" #. Tag: entry #: hardware.xml:476 #, no-c-format msgid "AlphaServer 1000A 5/300" msgstr "AlphaServer 1000A 5/300" #. Tag: entry #: hardware.xml:477 #, no-c-format msgid "Noritake-Pinnacle" msgstr "Noritake-Pinnacle" #. Tag: entry #: hardware.xml:480 #, no-c-format msgid "AlphaServer 1000A 5/333...500" msgstr "AlphaServer 1000A 5/333...500" #. Tag: entry #: hardware.xml:481 #, no-c-format msgid "Noritake-Primo" msgstr "Noritake-Primo" #. Tag: entry #: hardware.xml:484 #, no-c-format msgid "AlphaServer 800 5/333...500" msgstr "AlphaServer 800 5/333...500" # index.docbook:475, index.docbook:483, index.docbook:487 #. Tag: entry #: hardware.xml:485 hardware.xml:493 hardware.xml:497 #, no-c-format msgid "Corelle" msgstr "Corelle" #. Tag: entry #: hardware.xml:488 #, no-c-format msgid "AlphaStation 600 A" msgstr "AlphaStation 600 A" #. Tag: entry #: hardware.xml:489 #, no-c-format msgid "Alcor-Primo" msgstr "Alcor-Primo" #. Tag: entry #: hardware.xml:492 #, no-c-format msgid "Digital Server 3300" msgstr "Digital Server 3300" #. Tag: entry #: hardware.xml:496 #, no-c-format msgid "Digital Server 3300R" msgstr "Digital Server 3300R" #. Tag: entry #: hardware.xml:502 #, no-c-format msgid "PLATFORM 2000" msgstr "PLATFORM 2000" # index.docbook:493, index.docbook:494 #. Tag: entry #: hardware.xml:503 hardware.xml:504 #, no-c-format msgid "P2K" msgstr "P2K" #. Tag: entry #: hardware.xml:505 #, no-c-format msgid "p2k" msgstr "p2k" #. Tag: entry #: hardware.xml:509 #, no-c-format msgid "RAWHIDE" msgstr "RAWHIDE" #. Tag: entry #: hardware.xml:510 #, no-c-format msgid "AlphaServer 1200 5/xxx" msgstr "AlphaServer 1200 5/xxx" # index.docbook:501, index.docbook:513 #. Tag: entry #: hardware.xml:511 hardware.xml:523 #, no-c-format msgid "Tincup/DaVinci" msgstr "Tincup/DaVinci" #. Tag: entry #: hardware.xml:514 #, no-c-format msgid "AlphaServer 4000 5/xxx" msgstr "AlphaServer 4000 5/xxx" #. Tag: entry #: hardware.xml:515 #, no-c-format msgid "Wrangler/Durango" msgstr "Wrangler/Durango" #. Tag: entry #: hardware.xml:518 #, no-c-format msgid "AlphaServer 4100 5/xxx" msgstr "AlphaServer 4100 5/xxx" # index.docbook:509, index.docbook:517 #. Tag: entry #: hardware.xml:519 hardware.xml:527 #, no-c-format msgid "Dodge" msgstr "Dodge" #. Tag: entry #: hardware.xml:522 #, no-c-format msgid "Digital Server 5300" msgstr "Digital Server 5300" #. Tag: entry #: hardware.xml:526 #, no-c-format msgid "Digital Server 7300" msgstr "Digital Server 7300" #. Tag: entry #: hardware.xml:532 #, no-c-format msgid "RUFFIAN" msgstr "RUFFIAN" #. Tag: entry #: hardware.xml:533 #, no-c-format msgid "DeskStation AlphaPC164-UX" msgstr "DeskStation AlphaPC164-UX" # index.docbook:524, index.docbook:528, index.docbook:532, index.docbook:536, index.docbook:540, index.docbook:544 #. Tag: entry #: hardware.xml:534 hardware.xml:538 hardware.xml:542 hardware.xml:546 #: hardware.xml:550 hardware.xml:554 #, no-c-format msgid "Ruffian" msgstr "Ruffian" # index.docbook:525, index.docbook:529, index.docbook:533, index.docbook:537, index.docbook:541, index.docbook:545 #. Tag: entry #: hardware.xml:535 hardware.xml:539 hardware.xml:543 hardware.xml:547 #: hardware.xml:551 hardware.xml:555 #, no-c-format msgid "ruffian" msgstr "ruffian" #. Tag: entry #: hardware.xml:537 #, no-c-format msgid "DeskStation RPL164-2" msgstr "DeskStation RPL164-2" #. Tag: entry #: hardware.xml:541 #, no-c-format msgid "DeskStation RPL164-4" msgstr "DeskStation RPL164-4" #. Tag: entry #: hardware.xml:545 #, no-c-format msgid "DeskStation RPX164-2" msgstr "DeskStation RPX164-2" #. Tag: entry #: hardware.xml:549 #, no-c-format msgid "DeskStation RPX164-4" msgstr "DeskStation RPX164-4" #. Tag: entry #: hardware.xml:553 #, no-c-format msgid "Samsung AlphaPC164-BX" msgstr "Samsung AlphaPC164-BX" #. Tag: entry #: hardware.xml:559 #, no-c-format msgid "SABLE" msgstr "SABLE" #. Tag: entry #: hardware.xml:560 #, no-c-format msgid "AlphaServer 2000 4/xxx" msgstr "AlphaServer 2000 4/xxx" #. Tag: entry #: hardware.xml:561 #, no-c-format msgid "Demi-Sable" msgstr "Demi-Sable" #. Tag: entry #: hardware.xml:564 #, no-c-format msgid "AlphaServer 2000 5/xxx" msgstr "AlphaServer 2000 5/xxx" #. Tag: entry #: hardware.xml:565 #, no-c-format msgid "Demi-Gamma-Sable" msgstr "Demi-Gamma-Sable" #. Tag: entry #: hardware.xml:568 #, no-c-format msgid "AlphaServer 2100 4/xxx" msgstr "AlphaServer 2100 4/xxx" #. Tag: entry #: hardware.xml:569 #, no-c-format msgid "Sable" msgstr "Sable" #. Tag: entry #: hardware.xml:572 #, no-c-format msgid "AlphaServer 2100 5/xxx" msgstr "AlphaServer 2100 5/xxx" #. Tag: entry #: hardware.xml:573 #, no-c-format msgid "Gamma-Sable" msgstr "Gamma-Sable" #. Tag: entry #: hardware.xml:578 #, no-c-format msgid "TAKARA" msgstr "TAKARA" #. Tag: entry #: hardware.xml:579 #, no-c-format msgid "21164 PICMG SBC" msgstr "21164 PICMG SBC" #. Tag: entry #: hardware.xml:580 #, no-c-format msgid "Takara" msgstr "Takara" #. Tag: entry #: hardware.xml:581 #, no-c-format msgid "takara" msgstr "takara" #. Tag: entry #: hardware.xml:585 #, no-c-format msgid "TITAN" msgstr "TITAN" #. Tag: entry #: hardware.xml:586 #, no-c-format msgid "AlphaServer DS15" msgstr "AlphaServer DS15" #. Tag: entry #: hardware.xml:587 #, no-c-format msgid "HyperBrick2" msgstr "HyperBrick2" #. Tag: entry #: hardware.xml:590 #, no-c-format msgid "AlphaServer DS25" msgstr "AlphaServer DS25" #. Tag: entry #: hardware.xml:591 #, no-c-format msgid "Granite" msgstr "Granite" #. Tag: entry #: hardware.xml:594 #, no-c-format msgid "AlphaServer ES45" msgstr "AlphaServer ES45" #. Tag: entry #: hardware.xml:595 #, no-c-format msgid "Privateer" msgstr "Privateer" # index.docbook:588, index.docbook:627, index.docbook:631 #. Tag: entry #: hardware.xml:598 hardware.xml:637 hardware.xml:641 #, no-c-format msgid "UNKNOWN" msgstr "UNKNOWN" #. Tag: entry #: hardware.xml:599 #, no-c-format msgid "Yukon" msgstr "Yukon" #. Tag: entry #: hardware.xml:604 #, no-c-format msgid "TSUNAMI" msgstr "TSUNAMI" #. Tag: entry #: hardware.xml:605 #, no-c-format msgid "AlphaServer DS10" msgstr "AlphaServer DS10" # index.docbook:596, index.docbook:644 #. Tag: entry #: hardware.xml:606 hardware.xml:654 #, no-c-format msgid "Webbrick" msgstr "Webbrick" #. Tag: entry #: hardware.xml:609 #, no-c-format msgid "AlphaServer DS10L" msgstr "AlphaServer DS10L" #. Tag: entry #: hardware.xml:610 #, no-c-format msgid "Slate" msgstr "Slate" #. Tag: entry #: hardware.xml:613 #, no-c-format msgid "AlphaServer DS20" msgstr "AlphaServer DS20" #. Tag: entry #: hardware.xml:614 #, no-c-format msgid "Catamaran/Goldrush" msgstr "Catamaran/Goldrush" #. Tag: entry #: hardware.xml:617 #, no-c-format msgid "AlphaServer DS20E" msgstr "AlphaServer DS20E" #. Tag: entry #: hardware.xml:618 #, no-c-format msgid "Goldrack" msgstr "Goldrack" #. Tag: entry #: hardware.xml:621 #, no-c-format msgid "AlphaServer DS20L" msgstr "AlphaServer DS20L" #. Tag: entry #: hardware.xml:622 #, no-c-format msgid "Shark" msgstr "Shark" #. Tag: entry #: hardware.xml:625 #, no-c-format msgid "AlphaServer ES40" msgstr "AlphaServer ES40" #. Tag: entry #: hardware.xml:626 #, no-c-format msgid "Clipper" msgstr "Clipper" # index.docbook:619, index.docbook:620 #. Tag: entry #: hardware.xml:629 hardware.xml:630 #, no-c-format msgid "DP264" msgstr "DP264" #. Tag: entry #: hardware.xml:633 #, no-c-format msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "SMARTengine 21264 PCI/ISA SBC" #. Tag: entry #: hardware.xml:634 #, no-c-format msgid "Eiger" msgstr "Eiger" #. Tag: entry #: hardware.xml:638 #, no-c-format msgid "Warhol" msgstr "Warhol" #. Tag: entry #: hardware.xml:642 #, no-c-format msgid "Windjammer" msgstr "Windjammer" #. Tag: entry #: hardware.xml:645 #, no-c-format msgid "UP2000" msgstr "UP2000" #. Tag: entry #: hardware.xml:646 #, no-c-format msgid "Swordfish" msgstr "Swordfish" #. Tag: entry #: hardware.xml:649 #, no-c-format msgid "XP1000" msgstr "XP1000" #. Tag: entry #: hardware.xml:650 #, no-c-format msgid "Monet/Brisbane" msgstr "Monet/Brisbane" #. Tag: entry #: hardware.xml:653 #, no-c-format msgid "XP900" msgstr "XP900" #. Tag: entry #: hardware.xml:659 #, no-c-format msgid "WILDFIRE" msgstr "WILDFIRE" #. Tag: entry #: hardware.xml:660 #, no-c-format msgid "AlphaServer GS160" msgstr "AlphaServer GS160" # index.docbook:651, index.docbook:655 #. Tag: entry #: hardware.xml:661 hardware.xml:665 #, no-c-format msgid "Wildfire" msgstr "Wildfire" #. Tag: entry #: hardware.xml:664 #, no-c-format msgid "AlphaServer GS320" msgstr "AlphaServer GS320" # index.docbook:660, index.docbook:662 #. Tag: entry #: hardware.xml:670 hardware.xml:672 #, no-c-format msgid "XL" msgstr "XL" #. Tag: entry #: hardware.xml:671 #, no-c-format msgid "XL-233...266" msgstr "XL-233...266" #. Tag: entry #: hardware.xml:673 #, no-c-format msgid "xl" msgstr "xl" #. Tag: para #: hardware.xml:678 #, no-c-format msgid "" "It is believed that Debian &releasename; supports installing on all alpha " "sub-architectures with the exception of the ARC-only Ruffian and XL sub-" "architectures and the Titan subarchitecture, which requires a change to the " "kernel compile options." msgstr "" "除了需要修改内核编译选项的 ARC-only Ruffian、XL sub-architectures,以及 " "Titan 子体系之外,Debian &releasename; 支持安装到所有的 alpha 子体系上。" #. Tag: para #: hardware.xml:694 hardware.xml:844 #, no-c-format msgid "" "Complete information concerning supported peripherals can be found at Linux Hardware Compatibility HOWTO. " "This section merely outlines the basics." msgstr "" "完整的周边设备支持情况信息可以在 Linux " "Hardware Compatibility HOWTO 中找到。本节只是基本的概况。" # index.docbook:808, index.docbook:914 #. Tag: title #: hardware.xml:702 hardware.xml:852 hardware.xml:1012 #, no-c-format msgid "CPU" msgstr "CPU" #. Tag: para #: hardware.xml:703 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "AMD64 和 Intel EM64T 处理器都获得支持。" #. Tag: para #: hardware.xml:731 #, no-c-format msgid "" "Each distinct ARM architecture requires its own kernel. Because of this the " "standard Debian distribution only supports installation on a number of the " "most common platforms. The Debian userland however may be used by " "any ARM CPU." msgstr "每种 ARM 体系要求使用各自的内核,正因为如此,Debian 标准发布版只支持安装到一些最常见的系统上。但 Debian userland 可以被 任何 ARM CPU 使用。" #. Tag: para #: hardware.xml:740 #, 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 "" "大多数的 ARM CPU 可以运行在(big 或 little)任一 endian 模式下。但是当前绝大多" "少系统的实现都是使用 little-endian 模式。Debian 现在也仅支持 little-endian " "ARM 系统。" #. Tag: para #: hardware.xml:748 #, no-c-format msgid "The supported platforms are:" msgstr "获得支持的平台有:" #. Tag: term #: hardware.xml:755 #, no-c-format msgid "Netwinder" msgstr "Netwinder" #. Tag: para #: hardware.xml:756 #, 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 "" "实际上这是一组机器的名称,它们基于 StrongARM 110 CPU 和 Intel 21285 北桥(也称" "作 Footbridge)。包括的机器有: Netwinder (也许是最常见的 ARM 机器)、CATS (也" "称为 EB110ATX)、EBSA 285 和 Compaq personal server (cps,也叫 skiff)。" #. Tag: term #: hardware.xml:769 #, no-c-format msgid "IOP32x" msgstr "IOP32x" #. Tag: para #: hardware.xml:770 #, no-c-format msgid "" "Intel's I/O Processor (IOP) line is found in a number of products related to " "data storage and processing. Debian currently supports the IOP32x platform, " "featuring the IOP 80219 and 32x chips commonly found in Network Attached " "Storage (NAS) devices. Debian explicitly supports two such devices: the " "GLAN Tank from IO-Data and " "the Thecus N2100." msgstr "Intel I/O Processor (IOP) 产品线可以在一些数据存储和处理的产品中找到。Debian 当前支持 IOP32x 平台,IOP 80219 和 32x 芯片通常在 Network Attached Storage (NAS) 设备上找到。Debian 明确支持两个设备:IO-Data 的 GLAN TankThecus N2100。" #. Tag: term #: hardware.xml:783 #, no-c-format msgid "IXP4xx" msgstr "IXP4xx" #. Tag: para #: hardware.xml:784 #, no-c-format msgid "" "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one " "IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 " "(Network Storage Link for USB 2.0 Disk Drives) is a small device which " "allows you to easily provide storage via the network. It comes with an " "Ethernet connection and two USB ports to which hard drives can be connected. " "There is an external site with installation instructions." msgstr "IXP4xx 平台基于 Intel XScale ARM 核心。当前,只有一个基于 IXP4xx 的系统被支持,Linksys NSLU2。Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) 是一个通过网络提供易用存储的小型设备。它提供了一个以太网接口和两个 USB 端口来连接硬盘。这里有一个外部网站 installation instructions。" #. Tag: term #: hardware.xml:798 #, no-c-format msgid "RiscPC" msgstr "RiscPC" #. Tag: para #: hardware.xml:799 #, no-c-format msgid "" "This machine is the oldest supported hardware but support for it in our new " "installer is incomplete. 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 "该机器是最早支持的硬件,但在我们新的安装程序里对它的支持还没有完成。它在 ROM 里面包含 RISC OS,Linux 可以使用 linloader 从该 OS 启动。RiscPC 有一种模块化的 CPU 卡,典型的安装有 30MHz 610、40MHz 710 或 233MHz Strongarm 110 CPU。主板集成了 IDE、SVGA 视频、并口、单串口、PS/2 键盘和专有的鼠标口。依据不同的配置,专有的模块扩充总线允许最多安装八块扩展卡,其中的一些模块有 Linux 驱动程序。" #. Tag: para #: hardware.xml:825 #, no-c-format msgid "" "There are two major support &architecture; 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 "" "有两个主要支持的 &architecture; 变种:PA-RISC 1.1 和 PA-" "RISC 2.0。PA-RISC 1.1 体系目标是 32 位处理器,而 2.0 体系目标是 64 位处理器。" "有一些系统可以运行任一种内核。两者的 userland 都是 32 位的。将来也许会有 64 " "位的 userland。" #. Tag: para #: hardware.xml:853 #, no-c-format msgid "" "Nearly all x86-based (IA-32) processors still in use in personal computers " "are supported, including all varieties of Intel's \"Pentium\" series. This " "also includes 32-bit AMD and VIA (former Cyrix) processors, and processors " "like the Athlon XP and Intel P4 Xeon." msgstr "几乎所有个人计算机中基于 x86 (IA-32) 的处理器都支持,包括所有的 Intel \"Pentium\" 系列变种。还包括 32 位 AMD 和 VIA (前身是 Cyrix) 处理器,以及像 Athlon XP 和 Intel P4 Xeon 这些处理器。" #. Tag: para #: hardware.xml:861 #, no-c-format msgid "" "If your system has a 64-bit processor from the AMD64 or Intel EM64T " "families, you will probably want to use the installer for the amd64 " "architecture instead of the installer for the (32-bit) i386 architecture." msgstr "假如您的系统中有 64 位 AMD64、Intel EM64T 家族的处理器,那么您该用 amd64 架构的安装程序替代 (32位) i386 架构的安装程序。" #. Tag: para #: hardware.xml:868 #, no-c-format msgid "" "However, Debian GNU/Linux &releasename; will not run on " "386 or earlier processors. Despite the architecture name \"i386\", support " "for actual 80386 processors (and their clones) was dropped with the Sarge " "(r3.1) release of Debian We have long tried to avoid this, " "but in the end it was necessary due a unfortunate series of issues with the " "compiler and the kernel, starting with an bug in the C++ ABI provided by " "GCC. You should still be able to run Debian GNU/Linux on actual 80386 " "processors if you compile your own kernel and compile all packages from " "source, but that is beyond the scope of this manual. . " "(No version of Linux has ever supported the 286 or earlier chips in the " "series.) All i486 and later processors are still supported " "Many Debian packages will actually run slightly faster on modern computers " "as a positive side effect of dropping support for these old chips. The i486, " "introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the " "i386, introduced in 1986, did not have. Previously, these could not be " "easily used by most Debian packages; now they can. ." msgstr "然而,Debian GNU/Linux &releasename; 将不能运行在 386 或更早的处理器上。尽管体系命名为 \"i386\",Debian 的 Sarge (r3.1) 版已经放弃对真正的 80386 处理器(以及它们的克隆)的支持,过去的版本曾经支持 我们已经尽力避免,但由于编译器和内核的一系列因素,起因是 GCC 提供的 C++ ABI 的 bug,最终只能如此。如果您自己动手从源码编译内核和所有的软件包,仍然可以将 Debian GNU/Linux 运行在真正的 80386 处理器上,这部分内容超出了本手册的范畴。 。(Linux 从来没有任何版本支持 286 或更早的芯片。) 所有的 i486 和后续的处理器仍然支持 许多 Debian 软件包在新的计算机上可以运行地稍微快一点,但另一方面却舍弃了对旧芯片的支持。1989 年发布的 i486 有三个 opcode (bswap、cmpxchg 和 xadd),然而 1986 年发布的 i386 却没有。以前,Debain 软件包不能使用它们,现在可以了。 。" #. Tag: title #: hardware.xml:905 #, no-c-format msgid "I/O Bus" msgstr "I/O 总线" #. Tag: para #: hardware.xml:906 #, 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). Essentially all " "personal computers sold in recent years use one of these." msgstr "" "系统总线作为主板的一部分用于 CPU 和诸如存储设备之类的周边设备通讯。您的计算机" "必须使用 ISA、EISA、PCI、微通道(MCA,用于 IBM's PS/2 系列)或者 VESA Local 总" "线(VLB, 有时称为 VL 总线)。近年来出售的个人电脑都会使用里面的一种。" #. Tag: para #: hardware.xml:930 #, no-c-format msgid "" "Complete information concerning supported M68000 based " "(&architecture;) systems can be found at the Linux/m68k FAQ. This section merely outlines the " "basics." msgstr "" "有关支持基于 M68000 (&architecture;完整的信息见 Linux/m68k FAQ。本节只是基本概况。" #. Tag: para #: hardware.xml:937 #, 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 " "EC line of 680x0 processors. See the Linux/m68k FAQ for complete details." msgstr "" "&architecture; 移植的 Linux 可以运行在具有 PMMU (Paged Memory Management " "Unit) 和 FPU (floating-point unit) 的任何 680x0 上面。这包括带有外部 68851 " "PMMU 的 68020、68030,以及其它更好的处理器,不包括 EC 系列的 " "680x0 处理器。请参考 Linux/m68k FAQ 以" "了解更多信息。" #. Tag: para #: hardware.xml:945 #, no-c-format msgid "" "There are four major supported &architecture; 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 Linux m68k for Macintosh 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 "" "一共有四个主要的 &architecture; 变种获得支持:Amiga、" "Atari、Macintosh 和 VME 机器。Amiga 与 Atari 是首批移植 Linux 的两个系统;并" "且,它们也是被 Debian 移植得最好的两个。Debian 与 Linux 内核对 Macintosh 系列" "的支持都是不完整的,请参考 Linux m68k for " "Macintosh 以了解项目的状态和支持的硬件。BVM 和 Motorola VMEbus 单板电" "脑最近才加入 Debian 支持行列。移植到其它的 &architecture; 体系的工作,比如 " "Sun3 体系与 NeXT black box,还在进行中,且没有被 Debian 支持。" #. Tag: para #: hardware.xml:972 #, no-c-format msgid "" "Debian on &arch-title; supports the following platforms: " " 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. SGI IP32: this platform is " "generally known as SGI O2. Broadcom " "BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom " "based on the dual-core SB1 1250 CPU. " "Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board " "from Broadcom based on the quad-core SB1A 1480 CPU. Complete information regarding supported mips/mipsel machines " "can be found at the Linux-MIPS homepage. In the following, only the systems supported by the Debian installer " "will be covered. If you are looking for support for other subarchitectures, " "please contact the debian-&arch-" "listname; mailing list." msgstr "" "&arch-title; 上的 Debian 支持以下平台: SGI " "IP22:该平台包括的 SGI 的 Indy、Indigo 2 和 Challenge S。由于这些机器非常接" "近,在本文档中所指的 SGI Indy 同样也代表 Indigo 2 与 Challenge S。 Broadcom BCM91250A (SWARM):此为 ATX 规格的开发" "板,基于 Broadcom 的 双核 SB1 1250 处理器。 " " Broadcom BCM91480B (BigSur):此为 ATX 规格的开发板,基于 " "Broadcom 的四核 SB1A 1480 CPU。 关于支持 " "mips/mipsel 机器的完整信息见 Linux-MIPS " "homepage。以下只涉及 Debian 安装程序所支持的系统。如果您在寻找其它子" "系统的支持,请联系 debian-&arch-" "listname; 邮件列表。" #. Tag: para #: hardware.xml:1013 #, 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 "" "Debian 安装系统支持 big endian MIPS 上的 SGI IP22、SGI Indy、Indigo 2 和具有 " "R4000、R4400、R4600 和 R5000 处理器的 Challenge S。对于 SGI IP32,当前只支持 " "R5000。带有 SB1 1250 双核芯片的 Broadcom BCM91250A 开发板,本安装程序在 SMP " "模式下提供支持。与此类似,BCM91480B 开发板包含一个四核的 SB1A 1480 芯片,也" "在 SMP 模式下获得支持。" #. Tag: para #: hardware.xml:1023 #, 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 "" "一些 MIPS 机器既可在 big 出可以在 little endian 模式下操作。对于 little " "endian MIPS,请阅读 mipsel 体系的相关文档。" #. Tag: para #: hardware.xml:1040 #, no-c-format msgid "" "Debian on &arch-title; supports the following platforms: " " DECstation: various models of the DECstation are supported. " " 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. Broadcom BCM91250A (SWARM): this is an ATX form " "factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. Broadcom BCM91480B (BigSur): this is an " "ATX form factor evaluation board from Broadcom based on the quad-core SB1A " "1480 CPU. Complete information regarding " "supported mips/mipsel machines can be found at the Linux-MIPS homepage. In the following, only the systems " "supported by the Debian installer will be covered. If you are looking for " "support for other subarchitectures, please contact the debian-&arch-listname; mailing list." msgstr "" "&arch-title; 上的 Debian 支持以下平台: " "DECstation:支持各种机型的 DECstation。 " "Cobalt Microserver:只适用基于 MIPS 的 Cobalt 机器。包括 Cobalt Qube 2700 " "(Qube1)、RaQ、Qube2 和 RaQ2,以及 Gateway Microserver。 " " Broadcom BCM91250A (SWARM):此为 ATX 规格的开发板,基于 " "Broadcom 的双核 SB1 1250 CPU。 Broadcom " "BCM91480B (BigSur): 此为 ATX 规格的开发板,基于 Broadcom 的四核 SB1A 1480 " "CPU。 关于支持 mips/mipsel 机器的完整信息" "见 Linux-MIPS homepage。以下只涉及 " "Debian 安装程序所支持的系统。如果您在寻找其它子系统的支持,请联系 debian-&arch-listname; 邮件列表。" #. Tag: title #: hardware.xml:1080 #, no-c-format msgid "CPU/Machine types" msgstr "CPU/机器类型" #. Tag: para #: hardware.xml:1082 #, 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 "" "当前 Debian 安装系统只支持 little endian MIPS 上 R3000 和 R4000/R4400 CPU 的 " "DECstation。Debian 安装系统可以在下列机器上工作:" #. Tag: entry #: hardware.xml:1094 #, no-c-format msgid "System Type" msgstr "系统类型" #. Tag: entry #: hardware.xml:1094 #, no-c-format msgid "CPU" msgstr "CPU" #. Tag: entry #: hardware.xml:1094 #, no-c-format msgid "Code-name" msgstr "代号(Code-name)" #. Tag: entry #: hardware.xml:1095 #, no-c-format msgid "Debian subarchitecture" msgstr "Debian 子系统" #. Tag: entry #: hardware.xml:1101 #, no-c-format msgid "DECstation 5000/1xx" msgstr "DECstation 5000/1xx" # index.docbook:995, index.docbook:1005, index.docbook:1010, index.docbook:1020 #. Tag: entry #: hardware.xml:1102 hardware.xml:1112 hardware.xml:1117 hardware.xml:1127 #, no-c-format msgid "R3000" msgstr "R3000" # index.docbook:996, index.docbook:1001 #. Tag: entry #: hardware.xml:1103 hardware.xml:1108 #, no-c-format msgid "3MIN" msgstr "3MIN" #. Tag: entry #: hardware.xml:1106 #, no-c-format msgid "DECstation 5000/150" msgstr "DECstation 5000/150" # index.docbook:1000, index.docbook:1025 #. Tag: entry #: hardware.xml:1107 hardware.xml:1132 #, no-c-format msgid "R4000" msgstr "R4000" #. Tag: entry #: hardware.xml:1111 #, no-c-format msgid "DECstation 5000/200" msgstr "DECstation 5000/200" #. Tag: entry #: hardware.xml:1113 #, no-c-format msgid "3MAX" msgstr "3MAX" #. Tag: entry #: hardware.xml:1116 #, no-c-format msgid "DECstation 5000/240" msgstr "DECstation 5000/240" # index.docbook:1011, index.docbook:1016 #. Tag: entry #: hardware.xml:1118 hardware.xml:1123 #, no-c-format msgid "3MAX+" msgstr "3MAX+" #. Tag: entry #: hardware.xml:1121 #, no-c-format msgid "DECstation 5000/260" msgstr "DECstation 5000/260" #. Tag: entry #: hardware.xml:1122 #, no-c-format msgid "R4400" msgstr "R4400" #. Tag: entry #: hardware.xml:1126 #, no-c-format msgid "Personal DECstation 5000/xx" msgstr "Personal DECstation 5000/xx" # index.docbook:1021, index.docbook:1026 #. Tag: entry #: hardware.xml:1128 hardware.xml:1133 #, no-c-format msgid "Maxine" msgstr "Maxine" #. Tag: entry #: hardware.xml:1131 #, no-c-format msgid "Personal DECstation 5000/50" msgstr "Personal DECstation 5000/50" #. Tag: para #: hardware.xml:1138 #, 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 "" "所有的 Cobalt 机器都支持。过去只有带有串口控制台的可以获得支持(也就是,除了 " "Qube 2700,即 Qube1 之外的机器)。但现在可以通过 SSH 进行安装。" #. Tag: para #: hardware.xml:1145 #, 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 "" "带有 SB1 1250 双核芯片的 Broadcom BCM91250A 开发板本,在本安装程序上以 SMP 模" "式获得支持。与此类似,BCM91480B 开发板,包含四核的 SB1A 1480 芯片,也以 SMP " "模式获得支持。" #. Tag: title #: hardware.xml:1155 #, no-c-format msgid "Supported console options" msgstr "支持的控制台选项" #. Tag: para #: hardware.xml:1156 #, 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 " "console=ttySx kernel parameter " "(with x being the number of the serial port you " "have your terminal connected to — usually 2, but " "0 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 "" "串行控制台可在所有支持的 DECstations (9600 bps, 8N1)上使用。为了使用串行控制" "台,您必须在启动安装程序映象时加上 console=ttySx 内核参数(x 是" "终端连接的串口号 — 通常为 2,但 Personal " "DECstations 是 0)。在 3MIN 和 3MAX+ (DECstation 5000/1xx, " "5000/240 和 5000/260) 上,本地控制台可使用 PMAG-BA 和 PMAGB-B 图形选项。" #. Tag: para #: hardware.xml:1167 #, no-c-format msgid "" "If you have a Linux system to use as serial terminal, an easy way is to run " "cu In Woody this command was part of the " "uucp package, but in later releases it is available " "as a separate package. on it. Example: " "\n" "$ cu -l /dev/ttyS1 -s 9600\n" " where the option -l (line) " "sets the serial port to use and -s (speed) sets the speed " "for the connection (9600 bits per second)." msgstr "" "如果您有一个用作串行终端的 Linux 系统,最简单的方法就是执行 cu 在 Woody 里该命令属于 uucp " "软件包,但在以后的发布中它属于其他的软件包。 。例如:" "\n" "$ cu -l /dev/ttyS1 -s 9600\n" " 其中 -l (line) 是设置使用的串" "口号,-s (speed) 是设置连接速度(9600 波特率)。" #. Tag: para #: hardware.xml:1185 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "Cobalt 和 Broadcom BCM91250A/BCM91480B 都使用 115200 bps。" #. Tag: para #: hardware.xml:1199 #, no-c-format msgid "" "There are four major supported &architecture; " "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 "" "有四个主要支持的 &architecture; 子体系:PMac (Power-" "Macintosh 或 PowerMac),PReP,APUS (Amiga Power-UP System) 和 CHRP 机器。每种" "子体系都有各自的启动方式。并且,还有四种不同的内核变种,以支持不同的 CPU。" #. Tag: para #: hardware.xml:1207 #, no-c-format msgid "" "Ports to other &architecture; 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 "" "移植到其它 &architecture; 体系的工作,比如 Be-Box 与 " "MBX 体系,仍在进行中,还不为 Debian 支持。将来我们也许会有 64 位的移植。" #. Tag: title #: hardware.xml:1215 #, no-c-format msgid "Kernel Flavours" msgstr "内核变种" #. Tag: para #: hardware.xml:1217 #, no-c-format msgid "" "There are four flavours of the powerpc kernel in Debian, based on the CPU " "type:" msgstr "在 Debian 中有四种基于 CPU 类型的 powerpc 内核:" #. Tag: term #: hardware.xml:1224 #, no-c-format msgid "powerpc" msgstr "powerpc" #. Tag: para #: hardware.xml:1225 #, 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 "" "绝大多数系统使用这种内核,它支持 PowerPC 601、603、604、740、750 与 7400 处理" "器。所有 Apple PowerMac 以后的系统包括 G4 都使用这其中的处理器。" #. Tag: term #: hardware.xml:1235 #, no-c-format msgid "power64" msgstr "power64" #. Tag: para #: hardware.xml:1236 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "power64 内核支持以下的 CPU:" #. Tag: para #: hardware.xml:1240 #, 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 "" "POWER3 处理器用于早期的 IBM 64 位服务器系统: 已知的型号包括 IntelliStation " "POWER Model 265、pSeries 610 与 640,以及 RS/6000 7044-170、7043-260 和 7044-" "270。" #. Tag: para #: hardware.xml:1246 #, 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 "" "POWER4 处理器用于最新的 IBM 64 位服务器系统: 已知的型号包括 pSeries 615、" "630、650、655、670 和 690。" #. Tag: para #: hardware.xml:1251 #, no-c-format msgid "" "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 " "architecture, and use this kernel flavour." msgstr "" "采用 Apple G5 (PPC970FX 处理器) 的系统也是基于 POWER4 体系,并使用这种内核。" #. Tag: term #: hardware.xml:1260 #, no-c-format msgid "prep" msgstr "prep" #. Tag: para #: hardware.xml:1261 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "这种内核支持 PReP 子系统。" #. Tag: term #: hardware.xml:1269 #, no-c-format msgid "apus" msgstr "apus" #. Tag: para #: hardware.xml:1270 #, no-c-format msgid "" "This kernel flavour supports the Amiga Power-UP System, though it is " "currently disabled." msgstr "这种内核支持 Amiga Power-UP 系统,当然已经禁用。" #. Tag: title #: hardware.xml:1283 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "Power Macintosh (pmac) 子体系" #. Tag: para #: hardware.xml:1285 #, 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 "" "Apple (以及其它一些制造商 — 比如 Power Computing) 生产了一系列基于 " "PowerPC 处理器 的 Macintosh 计算机。为体系支持的目的,它们被划分为 NuBus" "(Debian 没有支持)、OldWorld PCI 和 NewWorld。" #. Tag: para #: hardware.xml:1292 #, 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 "" "OldWorld 系统多数为带软驱和 PCI 总线的 Power Macintosh。大多数基于 603、" "603e、604 和 604e 的 Power Macintosh 是 OldWorld 机器。除了米色的 G3 系统,这" "些 Apple iMac PowerPC 前身使用 4 位数字命名方式,它们都是 OldWorld 的。" #. Tag: para #: hardware.xml:1300 #, no-c-format msgid "" "The so called NewWorld PowerMacs are any PowerMacs in translucent colored " "plastic cases and later models. That includes all iMacs, iBooks, G4 systems, " "blue colored G3 systems, and most PowerBooks manufactured in and after 1999. " "The NewWorld PowerMacs are also known for using the ROM in RAM system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" "被称做 NewWorld PowerMacs 是那些有半透明塑料外壳的机器。包括所有的 iMacs、" "iBook、G4 系统、蓝色的 G3 系统、和大多数 1999 年及以后生产的 PowerBook。" "NewWorld PowerMacs 也是 1998 下半年以后制造,使用 ROM in RAM " "MacOS 的系统。" #. Tag: para #: hardware.xml:1308 #, no-c-format msgid "" "Specifications for Apple hardware are available at AppleSpec, and, for older " "hardware, AppleSpec Legacy." msgstr "" "Apple 硬件的规格说明位于 AppleSpec,另外,对于旧硬件,参见 AppleSpec " "Legacy。" # index.docbook:1240, index.docbook:1375, index.docbook:1419, index.docbook:1448 #. Tag: entry #: hardware.xml:1324 hardware.xml:1459 hardware.xml:1503 hardware.xml:1532 #, no-c-format msgid "Model Name/Number" msgstr "型号名称/编号" #. Tag: entry #: hardware.xml:1325 #, no-c-format msgid "Generation" msgstr "世代" #. Tag: entry #: hardware.xml:1331 #, no-c-format msgid "Apple" msgstr "Apple" #. Tag: entry #: hardware.xml:1332 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "iMac Bondi Blue, 5 Flavors, Slot Loading" # index.docbook:1249, index.docbook:1252, index.docbook:1255, index.docbook:1258, index.docbook:1261, index.docbook:1264, index.docbook:1267, index.docbook:1270, index.docbook:1273, index.docbook:1276, index.docbook:1279, index.docbook:1282, index.docbook:1285, index.docbook:1288, index.docbook:1291, index.docbook:1294 #. Tag: entry #: hardware.xml:1333 hardware.xml:1336 hardware.xml:1339 hardware.xml:1342 #: hardware.xml:1345 hardware.xml:1348 hardware.xml:1351 hardware.xml:1354 #: hardware.xml:1357 hardware.xml:1360 hardware.xml:1363 hardware.xml:1366 #: hardware.xml:1369 hardware.xml:1372 hardware.xml:1375 hardware.xml:1378 #, no-c-format msgid "NewWorld" msgstr "NewWorld" #. Tag: entry #: hardware.xml:1335 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "iMac Summer 2000, Early 2001" #. Tag: entry #: hardware.xml:1338 #, no-c-format msgid "iMac G5" msgstr "iMac G5" #. Tag: entry #: hardware.xml:1341 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "iBook, iBook SE, iBook Dual USB" #. Tag: entry #: hardware.xml:1344 #, no-c-format msgid "iBook2" msgstr "iBook2" #. Tag: entry #: hardware.xml:1347 #, no-c-format msgid "iBook G4" msgstr "iBook G4" #. Tag: entry #: hardware.xml:1350 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "Power Macintosh Blue and White (B&W) G3" #. Tag: entry #: hardware.xml:1353 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "Power Macintosh G4 PCI, AGP, Cube" #. Tag: entry #: hardware.xml:1356 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "Power Macintosh G4 Gigabit Ethernet" #. Tag: entry #: hardware.xml:1359 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "Power Macintosh G4 Digital Audio, Quicksilver" #. Tag: entry #: hardware.xml:1362 #, no-c-format msgid "Power Macintosh G5" msgstr "Power Macintosh G5" #. Tag: entry #: hardware.xml:1365 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "PowerBook G3 FireWire Pismo (2000)" #. Tag: entry #: hardware.xml:1368 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "PowerBook G3 Lombard (1999)" #. Tag: entry #: hardware.xml:1371 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "PowerBook G4 Titanium" #. Tag: entry #: hardware.xml:1374 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "PowerBook G4 Aluminum" #. Tag: entry #: hardware.xml:1377 #, no-c-format msgid "Xserve G5" msgstr "Xserve G5" #. Tag: entry #: hardware.xml:1380 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "Performa 4400, 54xx, 5500" # index.docbook:1297, index.docbook:1300, index.docbook:1303, index.docbook:1306, index.docbook:1309, index.docbook:1312, index.docbook:1315, index.docbook:1318, index.docbook:1321, index.docbook:1324, index.docbook:1327, index.docbook:1330, index.docbook:1336, index.docbook:1339, index.docbook:1345, index.docbook:1351, index.docbook:1357 #. Tag: entry #: hardware.xml:1381 hardware.xml:1384 hardware.xml:1387 hardware.xml:1390 #: hardware.xml:1393 hardware.xml:1396 hardware.xml:1399 hardware.xml:1402 #: hardware.xml:1405 hardware.xml:1408 hardware.xml:1411 hardware.xml:1414 #: hardware.xml:1420 hardware.xml:1423 hardware.xml:1429 hardware.xml:1435 #: hardware.xml:1441 #, no-c-format msgid "OldWorld" msgstr "OldWorld" #. Tag: entry #: hardware.xml:1383 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "Performa 6360, 6400, 6500" #. Tag: entry #: hardware.xml:1386 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "Power Macintosh 4400, 5400" #. Tag: entry #: hardware.xml:1389 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "Power Macintosh 7200, 7300, 7500, 7600" #. Tag: entry #: hardware.xml:1392 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "Power Macintosh 8200, 8500, 8600" #. Tag: entry #: hardware.xml:1395 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "Power Macintosh 9500, 9600" #. Tag: entry #: hardware.xml:1398 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "Power Macintosh (Beige) G3 Minitower" #. Tag: entry #: hardware.xml:1401 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "Power Macintosh (Beige) Desktop, All-in-One" #. Tag: entry #: hardware.xml:1404 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "PowerBook 2400, 3400, 3500" #. Tag: entry #: hardware.xml:1407 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "PowerBook G3 Wallstreet (1998)" #. Tag: entry #: hardware.xml:1410 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "Twentieth Anniversary Macintosh" #. Tag: entry #: hardware.xml:1413 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "Workgroup Server 7250, 7350, 8550, 9650, G3" #. Tag: entry #: hardware.xml:1418 #, no-c-format msgid "Power Computing" msgstr "Power Computing" #. Tag: entry #: hardware.xml:1419 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "PowerBase, PowerTower / Pro, PowerWave" #. Tag: entry #: hardware.xml:1422 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "PowerCenter / Pro, PowerCurve" #. Tag: entry #: hardware.xml:1427 #, no-c-format msgid "UMAX" msgstr "UMAX" #. Tag: entry #: hardware.xml:1428 #, no-c-format msgid "C500, C600, J700, S900" msgstr "C500, C600, J700, S900" #. Tag: entry #: hardware.xml:1433 #, no-c-format msgid "APS" msgstr "APS" #. Tag: entry #: hardware.xml:1434 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "APS Tech M*Power 604e/2000" # index.docbook:1355, index.docbook:1381 #. Tag: entry #: hardware.xml:1439 hardware.xml:1465 #, no-c-format msgid "Motorola" msgstr "Motorola" #. Tag: entry #: hardware.xml:1440 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "Starmax 3000, 4000, 5000, 5500" #. Tag: title #: hardware.xml:1449 #, no-c-format msgid "PReP subarchitecture" msgstr "PReP 子体系" #. Tag: entry #: hardware.xml:1466 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "Firepower, PowerStack Series E, PowerStack II" #. Tag: entry #: hardware.xml:1468 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "MPC 7xx, 8xx" #. Tag: entry #: hardware.xml:1470 #, no-c-format msgid "MTX, MTX+" msgstr "MTX, MTX+" #. Tag: entry #: hardware.xml:1472 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" #. Tag: entry #: hardware.xml:1474 #, no-c-format msgid "MCP(N)750" msgstr "MCP(N)750" # index.docbook:1394, index.docbook:1425 #. Tag: entry #: hardware.xml:1478 hardware.xml:1509 #, no-c-format msgid "IBM RS/6000" msgstr "IBM RS/6000" #. Tag: entry #: hardware.xml:1479 #, no-c-format msgid "40P, 43P" msgstr "40P, 43P" #. Tag: entry #: hardware.xml:1481 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "Power 830/850/860 (6070, 6050)" #. Tag: entry #: hardware.xml:1483 #, no-c-format msgid "6030, 7025, 7043" msgstr "6030, 7025, 7043" #. Tag: entry #: hardware.xml:1485 #, no-c-format msgid "p640" msgstr "p640" #. Tag: title #: hardware.xml:1493 #, no-c-format msgid "CHRP subarchitecture" msgstr "CHRP 子体系" #. Tag: entry #: hardware.xml:1510 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "B50, 43P-150, 44P" #. Tag: entry #: hardware.xml:1513 #, no-c-format msgid "Genesi" msgstr "Genesi" #. Tag: entry #: hardware.xml:1514 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "Pegasos I, Pegasos II" #. Tag: title #: hardware.xml:1522 #, no-c-format msgid "APUS subarchitecture" msgstr "APUS 子体系" #. Tag: entry #: hardware.xml:1538 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "Amiga Power-UP Systems (APUS)" #. Tag: entry #: hardware.xml:1539 #, no-c-format msgid "A1200, A3000, A4000" msgstr "A1200, A3000, A4000" #. Tag: title #: hardware.xml:1547 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "Nubus PowerMac 自体系 (未支持)" #. Tag: para #: hardware.xml:1549 #, no-c-format msgid "" "NuBus systems are not currently supported by Debian/powerpc. The monolithic " "Linux/PPC kernel architecture does not have support for these machines; " "instead, one must use the MkLinux Mach microkernel, which Debian does not " "yet support. These include the following: " "Power Macintosh 6100, 7100, 8100 " "Performa 5200, 6200, 6300 Powerbook " "1400, 2300, and 5300 Workgroup Server " "6150, 8150, 9150 A linux kernel for these " "machines and limited support is available at ." msgstr "" "NuBus 系统现在还不被 Debian/powerpc 支持。单内核的 Linux/PPC 内核体系不支持这" "些机器;而必须使用 MkLinux Mach 微内核,而它未被 Debian 支持。它们包括: " " Power Macintosh 6100, 7100, 8100 Performa 5200, 6200, 6300 " " Powerbook 1400, 2300 和 5300 " " Workgroup Server 6150, 8150, 9150 对这些机器提供有限支持的 linux 内核位于 " #. Tag: title #: hardware.xml:1586 #, no-c-format msgid "Non-PowerPC Macs" msgstr "Non-PowerPC Macs" #. Tag: para #: hardware.xml:1588 #, no-c-format msgid "" "Macintosh computers using the 680x0 series of processors are not in the PowerPC family but are instead m68k machines. Those models " "start with Mac II series, go on to the LC " "family, then the Centris series, and culminate in the Quadras and Performas. " "These models usually have a Roman numeral or 3-digit model number such as " "Mac IIcx, LCIII or Quadra 950." msgstr "" "使用 680x0 系列的 Macintosh 计算机不属于 PowerPC 家族,而是 m68k 机器。这些机" "器型号自 Mac II 开始,经历 LC 家族,然后是 " "Centris 系列,至 Quadras 与 Performas 达到顶峰。这些型号使用罗马数字或 3 位数" "字,像 Mac IIcx、LCIII 或 Quadra 950。" #. Tag: para #: hardware.xml:1597 #, 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 "" "该型号范围始于 Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), 然后" "是 LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), 接着是 Mac TV, 还" "有 Centris (610, 650, 660AV), Quadra (605, 610, 630, 650, 660AV, 700, 800, " "840AV, 900, 950), 最后是 Performa 200-640CD。" #. Tag: para #: hardware.xml:1605 #, 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 "" "便携机方面,它起始于 Mac Portable,然后是 PowerBook 100-190cs 和 PowerBook " "Duo 210-550c (不包含带有 Nubus 的 PowerBook 500,见前面说明。)" #. Tag: title #: hardware.xml:1621 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "S/390 与 zSeries 机器类型" #. Tag: para #: hardware.xml:1622 #, no-c-format msgid "" "Complete information regarding supported S/390 and zSeries machines can be " "found in IBM's Redbook Linux for IBM eServer zSeries and S/390: " "Distributions in chapter 2.1 or at the zSeries page at the " "developerWorks. 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 "" "有关 S/390 和 zSeries 机器支持的完整信息参见 IBM 的 Redbook Linux for " "IBM eServer zSeries and S/390: Distributions 第 2.1 章节,或者 " "developerWorks 网站上的 zSeries 页面。简而言之,G5、Multiprise " "3000、G6 以及所有的 zSeries 都可以得到完整的支持;Multiprise 2000、G3 和 G4 " "机器使用 IEEE 浮点模拟来支持,因此会降低性能。" # index.docbook:224, index.docbook:683, index.docbook:780, index.docbook:799, index.docbook:842, index.docbook:884, index.docbook:938, index.docbook:1085, index.docbook:1491 #. Tag: title #: hardware.xml:1644 #, no-c-format msgid "CPU and Main Boards Support" msgstr "CPU 和主板支持" #. Tag: para #: hardware.xml:1645 #, no-c-format msgid "" "Sparc-based hardware is divided into a number of different subarchitectures, " "identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u " "or sun4v. The following list describes what machines they include and what " "level of support may be expected for each of them." msgstr "基于 sparc 的硬件分成不同的子体系,标识为下列名称:sun4、sun4c、sun4d、sun4m、sun4u 或 sun4v。下面说明包括哪些机器,以及每个获得支持的级别。" #. Tag: term #: hardware.xml:1656 #, no-c-format msgid "sun4, sun4c, sun4d" msgstr "sun4, sun4c, sun4d" #. Tag: para #: hardware.xml:1658 #, no-c-format msgid "" "These subarchitectures include some very old 32-bit machines, which are no " "longer supported. For a complete list please consult the Wikipedia SPARCstation page." msgstr "这些子体系包含一些非常老的 32 位机器,它们不再获得支持。完整的列表,请查阅 Wikipedia SPARCstation page。" #. Tag: term #: hardware.xml:1669 #, no-c-format msgid "sun4m" msgstr "sun4m" #. Tag: para #: hardware.xml:1671 #, no-c-format msgid "" "sun4m is the only 32-bit subarchitecture (sparc32) that is currently " "supported. The most popular machines belonging to this class are " "Sparcstation 4, 5, 10 and 20." msgstr "sun4m 是当前惟一被支持的 32 位子体系(sparc32)。属于此类的流行机器有 Sparcstation 4、5、10 和 20。" #. Tag: para #: hardware.xml:1677 #, no-c-format msgid "" "Note that symmetric multiprocessing (SMP) — the ability to run " "processes on multiple processors — is not supported on this hardware, " "due to stability problems with such configurations. The available " "uniprocessor (UP) sparc32 kernel will boot fine on multiprocessor machines, " "although it will activate and use only the first CPU." msgstr "注意,symmetric multiprocessing (SMP) — 进程运行在多处理器上的能力 — 因为该配置下稳定性的问题,在此硬件上不被支持。现有的 uniprocessor (UP) sparc32 内核可以在多处理器机器上引导,但只激活和使用第一个 CPU。" #. Tag: term #: hardware.xml:1689 #, no-c-format msgid "sun4u" msgstr "sun4u" #. Tag: para #: hardware.xml:1691 #, no-c-format msgid "" "This subarchitecture includes all 64-bit machines (sparc64) based on the " "UltraSparc processor and its clones. Most of the machines are well " "supported, even though for some you may experience problems booting from CD " "due to firmware or bootloader bugs (this problem may be worked around by " "using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP " "configurations respectively." msgstr "该子体系包括所有的基于 UltraSparc 处理器的 64 位机器(sparc64)及其克隆。大多数机器支持得很好,即使如此,您也可能会遇到因固件或 bootloader bug 引起的 CD 引导问题(该问题可通过使用网络引导避开)。分别地使用 sparc64 或 sparc64-smp 内核到 UP 和 SMP 配置中。" #. Tag: term #: hardware.xml:1704 #, no-c-format msgid "sun4v" msgstr "sun4v" #. Tag: para #: hardware.xml:1706 #, no-c-format msgid "" "This is the newest addition to the Sparc family, which includes machines " "based on the Niagara multi-core CPUs. At the moment such CPUs are only " "available in T1000 and T2000 servers by Sun, and are well supported. Use the " "sparc64-smp kernel." msgstr "这是 Sparc 家族中的最新成员,它们包括基于 Niagara 多核 CPU 的机器。当前该 CPU 只存在于 Sun 的 T1000 和 T2000 服务器上,并能很好地支持。使用 sparc64-smp 内核。" #. Tag: para #: hardware.xml:1717 #, no-c-format msgid "" "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are " "not supported due to lack of support in the Linux kernel." msgstr "注意,使用富士通 SPARC64 CPU 的 PRIMEPOWER 家族服务器因为缺乏 Linux 内核的支持而得不到支持。" #. Tag: title #: hardware.xml:1726 #, no-c-format msgid "Graphics Card Support" msgstr "图形卡支持" #. Tag: para #: hardware.xml:1727 #, 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 "" "您应该给终端控制台使用 VGA 兼容的显示接口。几乎所有的新显卡都兼容 VGA。在不使" "用 X11 支持的情况下,您也可以用古老的 CGA, MDA 或 HGA 工作。注意,在本文所述" "的安装过程中并不会使用 X11 图形界面。" #. Tag: para #: hardware.xml:1735 #, 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 . Debian " "&release; ships with X.Org version &x11ver;." msgstr "" "Debian 对显卡的支持决定于 X.Org 的 X11 系统。大多数 AGP、PCI 和 PCI 视频卡都" "能在 X.Org 下工作。更多的关于图形总线、显卡、显示器和指点设备的支持情况,见 " "。Debian &release; 包含 X.Org &x11ver; 版。" #. Tag: para #: hardware.xml:1744 #, no-c-format msgid "" "The X.Org X Window System is only supported on the SGI Indy and the O2. The " "Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI " "slots and support VGA emulation or Linux framebuffer on a selected range of " "graphics cards. A compatibility " "listing for Broadcom evaluation boards is available." msgstr "X.Org 的 X 窗口系统仅支持 SGI Indy 和 O2。Broadcom BCM91250A 和 BCM91480B 开发板具有标准的 3.3v PCI 插槽,并且可选配的显示卡支持 VGA 仿真或者 Linux framebuffer。这里有一份 Broadcom 开发板的 兼容列表。" #. Tag: para #: hardware.xml:1753 #, no-c-format msgid "" "The X.Org X 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 compatibility " "listing for Broadcom evaluation boards is available." msgstr "在某些 DEC 工作站机型上 X.Org 的 X 窗口系统获得支持。Broadcom BCM91250A 和 BCM91480B 开发板具有标准的 3.3v PCI 插槽,并且可选配的显示卡支持 VGA 仿真或者 Linux framebuffer。有一份 Broadcom 开发板的 兼容列表。" #. Tag: para #: hardware.xml:1761 #, no-c-format msgid "" "Most graphics options commonly found on Sparc-based machines are supported. " "X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, " "sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), " "PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards " "(glint driver). To use an Elite3D card with X.org you additionally need to " "install the afbinit package, and read the " "documentation included with it on how to activate the card." msgstr "多数基于 Sparc 机器的图形选项都能支持。X.org 图形驱动程序可用于 sunbw2、suncg14、suncg3、suncg6、sunleo 和 suntcx framebuffers、Creator3D 和 Elite3D 卡(sunffb 驱动程序), PGX24/PGX64 基于 ATI 的视频卡 (ati 驱动程序),和基于 PermediaII 的卡 (glint 驱动程序)。要在 X.org 中使用 Elite3D 卡,您需要额外安装 afbinit 软件包,并且阅读其中的文档了解如何激活该卡。" #. Tag: para #: hardware.xml:1771 #, no-c-format msgid "" "It is not uncommon for a Sparc machine to have two graphics cards in a " "default configuration. In such a case there is a possibility that the Linux " "kernel will not direct its output to the card initially used by the " "firmware. The lack of output on the graphical console may then be mistaken " "for a hang (usually the last message seen on console is 'Booting Linux...'). " "One possible solution is to physically remove one of the video cards; " "another option is to disable one of the cards using a kernel boot parameter. " "Also, if graphical output is not required or desired, serial console may be " "used as an alternative. On some systems use of serial console can be " "activated automatically by disconnecting the keyboard before booting the " "system." msgstr "对 Sparc 机器来说,默认配置中有两块图形卡并非不常见。这种情况下,Linux 内核可能不将输出指向固件初始化的那块卡。缺少输出的图形控制端会由于这种错误而挂起(一般在控制台上最后显示的信息是 'Booting Linux...')。一种解决方法是物理地取下一块视频卡;另外一种方法是用内核引导参数禁止其中一块。同样,如果图形输出并不是必须或想要的,可以通过串口控制台替代。在某些系统上,引导系统前断开键盘连接将自动激活串口控制台。" #. Tag: title #: hardware.xml:1788 #, no-c-format msgid "Laptops" msgstr "便携机" #. Tag: para #: hardware.xml:1789 #, 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 Linux Laptop pages" msgstr "" "便携机当然也受到支持。便携机通常使用特制或专有的硬件。要了解您的便携机是否能" "在 GNU/Linux 下正常工作,请参考 Linux 便携机" "页面" # index.docbook:1624, index.docbook:1649, index.docbook:1672 #. Tag: title #: hardware.xml:1800 hardware.xml:1822 hardware.xml:1842 hardware.xml:1865 #, no-c-format msgid "Multiple Processors" msgstr "多处理器" #. Tag: para #: hardware.xml:1801 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing 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 "多处理器支持 — 又称 symmetric multiprocessing 或 SMP — 在本体系架构下可以使用。标准的 Debian &release; 内核映像在编译时已经加入了 SMP 功能。这并不会影响安装,因为 SMP 的内核也能在非 SMP 的系统下启动,只不过多些系统开销。" #. Tag: para #: hardware.xml:1809 #, 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 . At this time (kernel version " "&kernelversion;) the way you disable SMP is to deselect &smp-config-" "option; in the &smp-config-section; section of the " "kernel config." msgstr "" "为了给单 CPU 系统优化内核,您需要替换标准的 Debian 内核。您可以在 找到相关的讨论。当前(内核版本 &kernelversion;)," "禁止 SMP 选项的方法是在内核配置的 &smp-config-section; 中取消" "选择 &smp-config-option;。" #. Tag: para #: hardware.xml:1824 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. The standard " "Debian &release; kernel image was compiled with SMP-alternatives support. This means that the kernel will detect the number of " "processors (or processor cores) and will automatically deactivate SMP on " "uniprocessor systems." msgstr "多处理器支持 — 又称 symmetric multiprocessing 或 SMP — 在本体系架构下可以使用。标准的 Debian &release; 内核映像在编译时已经加入了 SMP-alternatives 支持。也就是内核可以侦测处理器的数量(或者处理器核心数),并在单内核系统上自动关闭 SMP 的功能。" #. Tag: para #: hardware.xml:1833 #, no-c-format msgid "" "The 486 flavour of the Debian kernel image packages for &arch-title; is not " "compiled with SMP support." msgstr "&arch-title; 的 486 Debian 内核映像软件包没有支持 SMP 。" #. Tag: para #: hardware.xml:1843 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. However, the " "standard Debian &release; kernel image does not support SMP. This should not " "prevent installation, since the standard, non-SMP kernel should boot on SMP " "systems; the kernel will simply use the first CPU." msgstr "多处理器支持 — 又称 symmetric multiprocessing 或 SMP — 在本体系架构下可以使用。但是,标准的 Debian &release; 内核映像并不支持 SMP。这不会影响安装,因为非 SMP 的内核也能在 SMP 的系统下启动,只不过内核只使用第一个 CPU。" #. Tag: para #: hardware.xml:1852 #, no-c-format msgid "" "In order to take advantage of multiple processors, you'll have to replace " "the standard Debian kernel. You can find a discussion of how to do this in " ". At this time (kernel version " "&kernelversion;) the way you enable SMP is to select &smp-config-" "option; in the &smp-config-section; section of the " "kernel config." msgstr "" "为了使用多 CPU 的优势,您必须替换标准的 Debian 内核。您可以在 找到相关的讨论。当前(内核版本 &kernelversion;)启用 SMP 的" "方法是在内核配置的 &smp-config-section; 中选中 &smp-" "config-option;。" #. Tag: para #: hardware.xml:1866 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture, and is supported " "by a precompiled Debian kernel image. Depending on your install media, this " "SMP-capable kernel may or may not be installed by default. This should not " "prevent installation, since the standard, non-SMP kernel should boot on SMP " "systems; the kernel will simply use the first CPU." msgstr "多处理器支持 — 又称 symmetric multiprocessing 或 SMP — 在本体系架构下可以使用,并且有一个预编译的 Debian 内核映象已经开启这项功能。支持 SMP 的内核默认是否被安装,取决于您的安装介质。这并不会影响安装,因为非 SMP 的内核也能在 SMP 的系统下启动,只不过内核只使用第一个 CPU。" #. Tag: para #: hardware.xml:1876 #, no-c-format msgid "" "In order to take advantage of multiple processors, you should check to see " "if a kernel package that supports SMP is installed, and if not, choose an " "appropriate kernel package." msgstr "为了利用多处理器,您应该确认支持 SMP 的内核软件包是否被安装,如果没有,请选择一个合适的内核软件包。" #. Tag: para #: hardware.xml:1882 #, no-c-format msgid "" "You can also build your own customized kernel to support SMP. You can find a " "discussion of how to do this in . At this " "time (kernel version &kernelversion;) the way you enable SMP is to select " "&smp-config-option; in the &smp-config-section; section of the kernel config." msgstr "您可以自己定制内核来支持 SMP。可以在 找到相关的讨论。当前(内核版本 &kernelversion;)启用 SMP 的方法是在内核配置的 &smp-config-section; 中选中 &smp-config-option;。" #. Tag: title #: hardware.xml:1899 #, no-c-format msgid "Installation Media" msgstr "安装介质" #. Tag: para #: hardware.xml:1901 #, no-c-format msgid "" "This section will help you determine which different media types you can use " "to install Debian. For example, if you have a floppy disk drive on your " "machine, it can be used to install Debian. There is a whole chapter devoted " "to media, , 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 "" "本章将助您选则安装 Debian 所采用的介质。例如,您的电脑上有一个软驱,就可以用" "来安装 Debian。这里有一整章专门用于说明介质:,并列出了每种类型的优缺点。当您阅读那一章的时候,可能要返回来参考本页。" #. Tag: title #: hardware.xml:1912 #, no-c-format msgid "Floppies" msgstr "软盘" #. Tag: para #: hardware.xml:1913 #, 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 "" "在某些条件下,不得不从软盘做首次启动。通常,您所需的只是一个 3.5 英寸高密" "(1440kB)软驱。" #. Tag: para #: hardware.xml:1919 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "用于 CHRP 的软盘支持已经被停止。" #. Tag: title #: hardware.xml:1926 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "CD-ROM/DVD-ROM" #. Tag: para #: hardware.xml:1928 #, no-c-format msgid "" "Whenever you see CD-ROM 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 "" "每当在本手册中看到 CD-ROM,它泛指 CD-ROM 和 DVD-ROM。因为从操" "作系统的角度看,它们所用的技术是相同的。这里面除去那些既不属于 SCSI 也不属于 " "IDE/ATAPI 的老式的非标准 CD-ROM 驱动器。" #. Tag: para #: hardware.xml:1935 #, 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 " "floppy-less tape-" "less 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 ." msgstr "" "一些体系支持基于 CD-ROM 的安装。在支持 CD-ROM 启动的机器上,您可以完成 " "无软盘(floppy-less) " "无磁带(tape-less) 的安装。即使您的系统不支持从 CD-ROM 启动,您也可以" "结合其他技术在启动后,使用 CD-ROM 来安装系统,参阅 。" #. Tag: para #: hardware.xml:1947 #, 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 Linux CD-ROM HOWTO contains in-depth information on using CD-ROMs " "with Linux." msgstr "" "SCSI 和 IDE/ATAPI CD-ROM 的驱动器都是被支持的。另外,Linux 支持的所有非标准 " "CD 接口(比如美上美与松下的驱动器)也被启动盘支持。但是,这些机型需要特别指定 " "启动参数或者其他处理才能工作,并且从这些非标准的接口启动可能会失败。Linux CD-ROM HOWTO 包含一些关于在 Linux 下使" "用 CD-ROM 详尽的信息。" #. Tag: para #: hardware.xml:1957 #, 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 "" "USB CD-ROM 也是被支持的。而 FireWire 设备则是通过 ohci1394 和 sbp2 驱动程序来" "获得支持。" #. Tag: para #: hardware.xml:1962 #, 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 " "SRM HOWTO." msgstr "" "只要 SRM 控制台能支持相应的控制器,&arch-title; 上的 SCSI 和 IDE/ATAPI CD-" "ROM 就能获得支持。这将会把许多附加的控制卡排除在外,但是大多数由制造商提供的" "集成 IDE 和 SCSI 芯片以及控制卡都应该能够工作。要想知道您的设备是否被 SRM 控" "制台支持,请参阅 SRM HOWTO。" #. Tag: para #: hardware.xml:1971 #, no-c-format msgid "" "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-" "ROMs are also supported." msgstr "" "所有的 ARM 机器都支持 IDE/ATAPI CD-ROM。在 RiscPC 上,SCSI CD-ROM 也被支持。" #. Tag: para #: hardware.xml:1976 #, 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 Unix/PC or 512/2048, place it in the Unix or 512 position. " "To start the install, simply choose the System installation " "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 "" "在 SGI 的机器上,从 CD-ROM 启动需要一台能使用 512 字节逻辑块的 SCSI CD-ROM 驱" "动器。很多面向 PC 市场的 SCSI CD-ROM 驱动器并不具有这个能力。如果您的 CD-ROM " "驱动器上有标注为 Unix/PC512/2048 的跳线,请" "将其置于 Unix512 的位置上。要开始安装,请从" "固件上选择 System installation 项。Broadcom BCM91250A 支持标准" "的 IDE 设备,包括 CD-ROM 驱动器。但由于其固件不能识别 CD 驱动器,所以当前并不" "提供针对此平台的光盘映象。要将 Debian 安装到 Broadcom BCM91480B 开发板上,您" "需要一个 PCI IDE、SATA 或 SCSI 卡。" #. Tag: para #: hardware.xml:1991 #, 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 Unix/PC or 512/2048, place it in the Unix or 512 position." msgstr "" "在 DECstations 上,从 CD-ROM 启动需要一台能使用 512 字节逻辑块的 SCSI CD-ROM " "驱动器。很多面向 PC 市场的 SCSI CD-ROM 驱动器并不具有这个能力。如果您的 CD-" "ROM 驱动器上有标注为 Unix/PC512/2048 的跳" "线,请将其置于 Unix512 的位置上。" #. Tag: para #: hardware.xml:2000 #, 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 "" "CD 1 包含 r3k-kn02 子体系(基于 R3000 的 DEC 5000/1xx 和 5000/240 工作站以及 " "基于 R3000 DEC 的个人工作站型号)的安装程序,CD 2 的安装程序用于 r4k-kn04 子体" "系 (基于 R4x00 的DEC 5000/150 和 5000/260 工作站以及 DEC 5000/50 个人工作" "站)。" #. Tag: para #: hardware.xml:2009 #, no-c-format msgid "" "To boot from CD, issue the command boot #/rzid on the firmware " "prompt, where # is the number of the TurboChannel " "device from which to boot (3 on most DECstations) and id 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 "" "要从 CD 启动,在固件提示后使用命令boot #/rzid 其中# 是从哪个 TurboChannel 设备启动的编号 (DEC 工作站上大多数使用 " "3),id是 CD-ROM 驱动器 的 SCSI ID。如果您需要指定" "额外的参数,可以按照下面语法选择添加:" #. Tag: userinput #: hardware.xml:2021 #, no-c-format msgid "" "boot #/rzid " "param1=value1 param2=value2 ..." msgstr "" "boot #/rzid " "param1=value1 param2=value2 ..." #. Tag: title #: hardware.xml:2028 #, no-c-format msgid "Hard Disk" msgstr "硬盘" #. Tag: para #: hardware.xml:2030 #, 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:2036 #, no-c-format msgid "" "In fact, installation from your local disk is the preferred installation " "technique for most &architecture; machines." msgstr "事实上,从本地磁盘安装,对大多数 &architecture; 机器是推荐的做法。" #. Tag: para #: hardware.xml:2041 #, 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 "" "虽然 &arch-title; 不允许从 SunOS(Solaris) 启动,但您可以从一个 SunOS 的分区 " "(UFS slices)进行安装。" #. Tag: title #: hardware.xml:2049 #, no-c-format msgid "USB Memory Stick" msgstr "U 盘" #. Tag: para #: hardware.xml:2051 #, 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 "" "许多 Debian 机器只在设置系统和急救用途时才需要软盘和 CD-ROM 驱动器。如果使用" "过服务器,您也许已经想过怎么样省掉这些驱动器,而用 U 盘来安装和(在必需时)恢复" "系统。这对那些没有足够空间容纳不必要驱动器的小型系统非常有用。" #. Tag: title #: hardware.xml:2063 #, no-c-format msgid "Network" msgstr "网络" #. Tag: para #: hardware.xml:2065 #, no-c-format msgid "" "The network can be used during the installation to retrieve files needed for " "the installation. Whether the network is used or not depends on the " "installation method you choose and your answers to certain questions that " "will be asked during the installation. The installation system supports most " "types of network connections (including PPPoE, but not ISDN or PPP), via " "either HTTP or FTP. After the installation is completed, you can also " "configure your system to use ISDN and PPP." msgstr "安装过程中可以使用网络来获取安装所需要的文件。是否使用网络取决于您选择的安装方法和安装过程中回答的特定问题。安装系统支持大多数类型的网络连接(包括 PPPoE,但不含 ISDN 或 PPP),使用 HTTP 或 FTP。安装完成之后,您还可以配置您的系统使用 ISDN 和 PPP。" #. Tag: para #: hardware.xml:2075 #, no-c-format msgid "" "You can also boot the installation system over the " "network. This is the preferred installation technique " "for &arch-title;." msgstr "您还可以从网络 启动(boot) 系统。这是在 &arch-title; 下推荐的安装技术。" #. Tag: para #: hardware.xml:2081 #, 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 "" "无盘安装,使用网络从局域网启动,并用 NFS 挂载所有的本地文件系统,是另一种选" "择。" #. Tag: title #: hardware.xml:2089 #, no-c-format msgid "Un*x or GNU system" msgstr "Un*x 或 GNU 系统" #. Tag: para #: hardware.xml:2091 #, no-c-format msgid "" "If you are running another Unix-like system, you could use it to install " "&debian; without using the &d-i; described in the rest of this manual. This " "kind of install may be useful for users with otherwise unsupported hardware " "or on hosts which can't afford downtime. If you are interested in this " "technique, skip to the ." msgstr "如果您正在运行其它的类 Unix 系统,也可以用它来安装 &debian; 而无须本手册剩余部分讲述的 &d-i; 使用方法。这类安装方法可能对那些因为硬件不支持或机器停产的用户有用。如果您对此技术感兴趣,请直接跳到 。" #. Tag: title #: hardware.xml:2103 #, no-c-format msgid "Supported Storage Systems" msgstr "受支持的存储系统" #. Tag: para #: hardware.xml:2105 #, 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 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 "" "Debian 启动盘包括一个用于最大可能数量系统的内核。不幸的是,这将产生一个大内" "核,其中包括许多您的机器并不需要的驱动程序(参考学习如何创建自己的内核)。在通常情况下,支持最大范围内的设备是一种较合适的" "设计,这将使得 Debian 可以在尽可能多的硬件上安装。" #. Tag: para #: hardware.xml:2115 #, 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 "" "通常,Debian 安装系统支持软盘、IDE 驱动器、IDE 软盘、并口 IDE 驱动器、SCSI 控" "制器和驱动器、USB 和火线。文件系统支持 FAT、Win-32 FAT 扩展(VFAT)、NTFS。" #. Tag: para #: hardware.xml:2122 #, no-c-format msgid "" "Disk interfaces that emulate the AT 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 Linux Hardware " "Compatibility HOWTO for more details." msgstr "" "模拟 AT 硬盘接口的磁盘接口 — 称为 MFM、RLL、IDE 或 ATA " "— 是受支持的。用于 IBM XT 计算机的非常陈旧的 8 – 位硬盘控制器只在" "一个模块里来支持。大部分厂商生产的 SCSI 磁盘控制器都能获得支持。请参考 " "Linux Hardware Compatibility HOWTO 以获得更详细信息。" #. Tag: para #: hardware.xml:2132 #, 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 "" "基本上所有 Linux 内核支持的存储系统都被 Debian 安装系统所支持。注意,当前的 " "Linux 内核仍不支持 Macintosh 上的软盘,并且 Debian 安装系统也不支持 Amigas " "上 的软盘。支持 Atari 上的 Macintosh HFS 系统,并以模块形式支持 AFFS。Mac 机" "支持 Atari(FAT) 文件系统。Amigas 支持 FAT 文件系统,HFS 则是受模块支持。" #. Tag: para #: hardware.xml:2142 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system. The following SCSI drivers are supported in the default kernel: " " Sparc ESP " " PTI Qlogic,ISP Adaptec " "AIC7xxx NCR and Symbios 53C8XX IDE systems (such as the UltraSPARC 5) are also " "supported. See Linux for SPARC " "Processors FAQ for more information on SPARC hardware supported by " "the Linux kernel." msgstr "" "所有 Linux 内核支持的存储系统也都被启动系统所支持。下列 SCSI 驱动被默认内核支" "持: Sparc ESP " " PTI Qlogic,ISP Adaptec " "AIC7xxx NCR 与 Symbios 53C8XX IDE 系统(例如 UltraSPARC 5)是受支持的。请参考 " "Linux for SPARC Processors FAQ " "以了解更多关于 SPARC 硬件被 Linux 内核支持的情况。" #. Tag: para #: hardware.xml:2175 #, 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 for more information on booting the Jensen)" msgstr "" "所有 Linux 内核支持的存储系统也都被启动系统所支持。这包括 SCSI 和 IDE 磁盘。" "注意,在许多系统上,SRM 控制台不能从 IDE 驱动器上启动,并且 Jensen 不能从软盘" "上启动。(请参考 以了解更多关于从 " "Jensen 启动的信息)" #. Tag: para #: hardware.xml:2184 #, 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 "" "所有 Linux 内核支持的存储系统也都被启动系统所支持。注意当前的 Linux 内核还不" "支持 CHRP 系统上的软盘。" #. Tag: para #: hardware.xml:2190 #, 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 "" "所有 Linux 内核支持的存储系统也都被启动系统所支持。注意当前的 Linux 内核还不" "支持软驱。" #. Tag: para #: hardware.xml:2196 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system." msgstr "所有 Linux 内核支持的存储系统也都被启动系统所支持。" #. Tag: para #: hardware.xml:2201 #, 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 "" "所有 Linux 内核支持的存储系统也都被启动系统所支持。这意味着 FBA 和 ECKD DASD " "可以被 旧的 Linux disk layout (ldl) 和新的 common S/390 disk layout (cdl)支" "持。" #. Tag: title #: hardware.xml:2218 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "外围设备与其他硬件" #. Tag: para #: hardware.xml:2219 #, 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 "" "Linux 支持众多的硬件设备,比如:鼠标、打印机、扫描仪、PCMCIA 和 USB 设备。然" "而,在安装系统的时候,并不需要其中的大部分设备。" #. Tag: para #: hardware.xml:2225 #, no-c-format msgid "" "USB hardware generally works fine, only some USB keyboards may require " "additional configuration (see )." msgstr "USB 硬件通常工作得很好,只有一些 USB 键盘需要额外的配置(参阅 )。" #. Tag: para #: hardware.xml:2231 #, no-c-format msgid "" "Again, see the Linux Hardware " "Compatibility HOWTO to determine whether your specific hardware is " "supported by Linux." msgstr "" "另外,请查考 Linux Hardware " "Compatibility HOWTO 来判断您的硬件是否被 Linux 支持。" #. Tag: para #: hardware.xml:2237 #, 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 "" "从 XPRAM 和磁带安装的软件包不受本系统支持。所有要安装的包必须位于 DASD 上或者" "通过 NFS、HTTP、FTP 从网络上取得。" #. Tag: para #: hardware.xml:2243 #, 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 "" "Broadcom BCM91250A 开发板提供标准的 3.3v 32 位和 64 位 PCI 插槽,以及 USB 接" "口。Broadcom BCM91480B 开发板有四个 64 位 PCI 插槽。" #. Tag: para #: hardware.xml:2249 #, 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 "" "Broadcom BCM91250A 开发板提供标准的 3.3v 32 位和 64 位 PCI 插槽,以及 USB 接" "口。Broadcom BCM91480B 开发板有四个 64 位 PCI 插槽。Cobalt RaQ 不支持额外的设" "备,但 Qube 上有一个 PCI 插槽。" #. Tag: title #: hardware.xml:2259 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "特别为 GNU/Linux 采购硬件" #. Tag: para #: hardware.xml:2261 #, no-c-format msgid "" "There are several vendors, who ship systems with Debian or other " "distributions of GNU/Linux pre-installed. You might pay more for the privilege, but it does buy a level of " "peace of mind, since you can be sure that the hardware is well-supported by " "GNU/Linux." msgstr "" "现在有一些经销商,他们出售的系统是 预装 Debian 或者是其他的 GNU/Linux。您或许会多花一些钱,但是买来一份安心," "因为这些硬件都已经确保能被 GNU/Linux 很好地支持。" #. Tag: para #: hardware.xml:2269 #, no-c-format msgid "" "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; " "machines at all." msgstr "不幸的是,很少会有厂商出售新 &arch-title; 机器。" #. Tag: para #: hardware.xml:2274 #, no-c-format msgid "" "If you do have to buy a machine with Windows bundled, carefully read the " "software license that comes with Windows; you may be able to reject the " "license and obtain a rebate from your vendor. Searching the Internet for " "windows refund may get you some useful information to help " "with that." msgstr "" "如果您不得不购买一台捆绑 Windows 系统的机器,请仔细阅读 Windows 附带的软件许" "可证,您也许可以拒绝该许可证,并从经销商那里获得一定的折扣。在互联网上用 " "windows refund 搜索可以查到一些有益的信息。" #. Tag: para #: hardware.xml:2282 #, 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 "" "无论是购买一个捆绑 Linux 的系统,还是一个已经用过的系统,检查 Linux 内核是否" "支持您的硬件仍然很重要。检查您的硬件是否列在上面的参考资料中。让推销员(或者其" "他)知道您是在为一个 Linux 系统采购设备。请支持对 Linux 友好的硬件销售商。" #. Tag: title #: hardware.xml:2293 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "避免专有或封闭的硬件" #. Tag: para #: hardware.xml:2294 #, 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 "" "一些硬件制造商愚蠢地拒绝告诉我们如何给他们的硬件写驱动程序。其他的则要求签署" "不公开的契约才能接触文档,以阻止我们发布 Linux 驱动程序源代码。" #. Tag: para #: hardware.xml:2301 #, 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 "" "另一个例子是老式 Macintosh 产品系列的专有硬件。事实上,Macintosh 硬件没有公布" "任何规格书与文档,特别是 ADB 控制器(用于鼠标和键盘)、软盘控制器、所有的视频硬" "件加速和 CLUT 处理器(虽然我们不支持绝大多数内置显示芯片的 CLUT 处理器)。总" "之,这就是为什么向 Macintosh 移植 Linux 的进度总是滞后于其他移植版的原因。" #. Tag: para #: hardware.xml:2312 #, 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 "" "因为我们没有被授权查看这些设备的文档,它们自然不会在 Linux 下工作。您可以帮我" "们去告诉那些制造商,要求他们发布文档。如果有足够多的人要求,他们将认识到自由" "软件社区也是一个重要的市场。" #. Tag: title #: hardware.xml:2324 #, no-c-format msgid "Windows-specific Hardware" msgstr "Windows 专用硬件" #. Tag: para #: hardware.xml:2325 #, 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 WinModem or Made especially for Windows-based computers. 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 not passed on to the user and " "this hardware may even be more expensive than equivalent devices that retain " "their embedded intelligence." msgstr "" "一个令人不安的趋势是 Windows 规格的调制解调器和打印机的增长。在某些情况下它们" "专为微软的 Windows 操作系统设计并且标有 WinModem专" "为基于 Windows 的计算机制造 字样。这通常是省掉硬件的内嵌处理器,将它" "的工作交给 Windows 驱动程序并由您计算机中的 CPU 来完成。这样做是为了降低硬件" "成本,但是常常并不能为用户节省任何开销,并且可能还会比同" "等功能的保留内嵌处理器的设备昂贵。" #. Tag: para #: hardware.xml:2338 #, no-c-format msgid "" "You should avoid Windows-specific hardware for two reasons. The first is " "that the manufacturers do not generally make the resources available to " "write a Linux driver. Generally, the hardware and software interface to the " "device is proprietary, and documentation is not available without a non-" "disclosure agreement, if it is available at all. This precludes it being " "used for free software, since free software writers disclose the source code " "of their programs. The second reason is that when devices like these have " "had their embedded processors removed, the operating system must perform the " "work of the embedded processors, often at real-time " "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 "有两个原因让您应当避免使用 Windows 规格的硬件。首先,这些制造商一般不提供相应资料用于编写 Linux 驱动程序。通常,这些设备的软硬件接口是专有的,即使相关资料存在,但不签署封闭的契约也无法得到它们。这就排除了被自由软件使用的可能,因为自由软件的开发者不会将它们的软件源码封闭起来。其次,这些设备是没有内嵌处理器的,操作系统必须承担本该由这些处理器完成的工作,并且经常是在实时优先级下,因此 CPU 在驱动这些设备时就无法运行您的程序。因为典型的 Windows 用户并不像 Linux 用户那样对多任务有强烈要求,这些制造商希望 Windows 用户不会注意到 CPU 为他们硬件的开销。但是,任何多任务操作系统,甚至是 Windows 2000 或 XP,都要忍受这些制造商克扣内嵌处理器造成的性能下降。" #. Tag: para #: hardware.xml:2359 #, 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 Linux Hardware Compatibility HOWTO." msgstr "" "您可以帮助改变这种状况,要求制造商发布相应的文档和资料,让我们可以编写他们硬" "件的程序,但最好还是避免使用这些硬件,直到它们被列入 Linux Hardware Compatibility HOWTO。" #. Tag: title #: hardware.xml:2376 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "内存与磁盘空间的需求" #. Tag: para #: hardware.xml:2378 #, no-c-format msgid "" "You must have at least &minimum-memory; of memory and &minimum-fs-size; of " "hard disk space. Note that these are really bare-minimum numbers. For more " "realistic figures, see ." msgstr "您必须至少有 &minimum-memory; 的内存和 &minimum-fs-size; 的硬盘空间。注意这是最小的数字,要了解实际的情况,参阅 。" #. Tag: para #: hardware.xml:2384 #, 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 amiboot program can be used " "to disable 16-bit RAM; see the Linux/m68k FAQ. Recent kernels should disable 16-bit RAM automatically." msgstr "" "在 Amiga 上,FastRAM 的大小与总的内存需求相关联。而且,使用 16 位的 Zorro " "RAM 卡不 被支持,您要用32位的。amiboot 程序可以被用来禁止 " "16 位 RAM,请参考 Linux/m68k FAQ。最近" "的内核可以自动禁止 16 位的 RAM。" #. Tag: para #: hardware.xml:2393 #, 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 "" "在 Atari 上,ST-RAM 和 Fast RAM (TT-RAM) 都可以被 Linux 所使用。许多用户报告" "在 Fast RAM 上运行内核有问题,因此 Atari 启动将内核放在 ST-RAM。最小需要 2 " "MB 的 ST-RAM。您需要额外的 12 MB 或更多的 TT-RAM。" #. Tag: para #: hardware.xml:2401 #, 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 "" "在 Macintosh 上,需要注意 RAM-based video (RBV)。物理地址 0 的 RAM 段用于显示" "内存,使得默认的内核引导位置无效。替代的用于内核的 RAM 段与 RAMdisk 至少 需" "要 4 MB。" #. Tag: emphasis #: hardware.xml:2411 #, no-c-format msgid "FIXME: is this still true?" msgstr "FIXME: is this still true?" #. Tag: title #: hardware.xml:2422 #, no-c-format msgid "Network Connectivity Hardware" msgstr "网络连接硬件" #. Tag: para #: hardware.xml:2423 #, no-c-format msgid "" "Almost any network interface card (NIC) supported by the Linux kernel should " "also be supported by the installation system; modular drivers should " "normally be loaded automatically. This includes most " "PCI and PCMCIA cards. Many older ISA cards " "are supported as well. Again, see for complete details." msgstr "几乎所有被 Linux 内核支持的网络接口卡(NIC)也全都被安装系统所支持;驱动模块通常会自动加载。这包含大多数 PCI 和 PCMCIA 卡。 许多旧的 ISA 卡也能支持。 再次,参阅 获得完整的信息。" #. Tag: para #: hardware.xml:2435 #, no-c-format msgid "" "This includes a lot of generic PCI cards (for systems that have PCI) and the " "following NICs from Sun:" msgstr "这包括一些通用 PCI 卡(对于支持 PCI 的系统)和来自 Sun 的网卡:" #. Tag: para #: hardware.xml:2441 #, no-c-format msgid "Sun LANCE" msgstr "Sun LANCE" #. Tag: para #: hardware.xml:2446 #, no-c-format msgid "Sun Happy Meal" msgstr "Sun Happy Meal" #. Tag: para #: hardware.xml:2451 #, no-c-format msgid "Sun BigMAC" msgstr "Sun BigMAC" #. Tag: para #: hardware.xml:2456 #, no-c-format msgid "Sun QuadEthernet" msgstr "Sun QuadEthernet" #. Tag: para #: hardware.xml:2461 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "MyriCOM Gigabit Ethernet" #. Tag: para #: hardware.xml:2468 #, 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 "因为内核的限制,DECstation 上只有板载网络接口获得支持,TurboChannel 网卡现在还不能工作。" #. Tag: para #: hardware.xml:2474 #, no-c-format msgid "The list of supported network devices is:" msgstr "支持的网络设备有:" #. Tag: para #: hardware.xml:2479 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "Channel to Channel (CTC) 和 ESCON connection (实际或模拟)" #. Tag: para #: hardware.xml:2484 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "OSA-2 Token Ring/Ethernet 和 OSA-Express Fast Ethernet (non-QDIO)" #. Tag: para #: hardware.xml:2489 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "QDIO 模式的 OSA-Express,HiperSockets 和 Guest-LANs" #. Tag: para #: hardware.xml:2498 #, no-c-format msgid "" "On &arch-title;, most built-in Ethernet devices are supported and modules " "for additional PCI and USB devices are provided. The major exception is the " "IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a " "proprietary microcode for the operation of its built-in Ethernet device. " "Unofficial images for Linksys NSLU2 with this proprietary microcode can be " "obtained from the Slug-Firmware site." msgstr "在 &arch-title; 上,多数内建的以太网设备都支持,并提供额外的 PCI 和 USB 设备模块。主要的例外是 IXP4xx 平台(典型的设备是 Linksys NSLU2),它需要专用的 microcode 来操作内建的以太网设备。包含该专有 microcode 的 Linksys NSLU2 非正式映像可以从 Slug-Firmware site 地址获得。" #. Tag: para #: hardware.xml:2508 #, 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;. " "Using ISDN during the installation is not supported." msgstr "对于 ISDN,用于(老式)德国 1TR6 的 D-channel 协议不被支持,Spellcaster BRI ISDN 板也不被 &d-i; 支持。所以,安装过程中使用 ISDN 不被支持。" #. Tag: title #: hardware.xml:2517 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "需要固件的驱动程序" #. Tag: para #: hardware.xml:2518 #, no-c-format msgid "" "The installation system currently does not support retrieving firmware. This " "means that any network cards that use a driver that requires firmware to be " "loaded, is not supported by default." msgstr "安装系统当前不支持获取固件。也就是说,默认不支持那些需要驱动程序加载固件的网卡。" #. Tag: para #: hardware.xml:2524 #, no-c-format msgid "" "If there is no other NIC you can use during the installation, it is still " "possible to install &debian; using a full CD-ROM or DVD image. Select the " "option to not configure a network and install using only the packages " "available from the CD/DVD. You can then install the driver and firmware you " "need after the installation is completed (after the reboot) and configure " "your network manually. Note that the firmware may be packaged separately " "from the driver and may not be available in the main section " "of the &debian; archive." msgstr "如果您在安装时没有其他的网卡,使用完整的 CD-ROM 或 DVD 映像也可以安装 &debian;。选择不配置网络并且安装时只使用 CD/DVD 上有的软件包。完成安装之后,您再安装驱动程序和固件(重启之后)并且手动配置网络。注意,固件可能与驱动放在不同的软件包,并可能不在 &debian; archive 的 main 部分之中。" #. Tag: para #: hardware.xml:2535 #, no-c-format msgid "" "If the driver itself is supported, you may also be able " "to use the NIC during installation by copying the firmware from some medium " "to /usr/lib/hotplug/firmware. Don't forget to also copy " "the firmware to that location for the installed system before the reboot at " "the end of the installation." msgstr "如果驱动程序自己支持,您在安装过程中通过将固件复制到 /usr/lib/hotplug/firmware 也许可以使用网卡。完成安装之后别忘了将该固件复制到安装好的系统。" #. Tag: title #: hardware.xml:2547 #, no-c-format msgid "Wireless Network Cards" msgstr "无线网卡" #. Tag: para #: hardware.xml:2548 #, no-c-format msgid "" "Wireless NICs are in general supported as well, with one big proviso. A lot " "of wireless adapters require drivers that are either non-free or have not " "been accepted into the official Linux kernel. These NICs can generally be " "made to work under &debian;, but are not supported during the installation." msgstr "无线网卡通常也能支持得很好,但会附加限制性条款。很多无线网卡要求驱动程序是非自由的,或不能包含在正式的 Linux 内核之中。这些网卡一般可以在 &debian; 下工作,但不被安装系统支持。" #. Tag: para #: hardware.xml:2555 #, no-c-format msgid "" "If there is no other NIC you can use during the installation, it is still " "possible to install &debian; using a full CD-ROM or DVD image. Use the same " "procedure as described above for NICs that require firmware." msgstr "如果安装时您没有其他的网卡可用,可以使用完整的 CD-ROM 或 DVD 映像来安装 &debian;。与要求固件的网卡步骤相同。" #. Tag: para #: hardware.xml:2561 #, no-c-format msgid "" "In some cases the driver you need may not be available as a Debian package. " "You will then have to look if there is source code available in the internet " "and compile the driver yourself. How to do this is outside the scope of this " "manual. If no Linux driver is available, your last " "resort is to use the ndiswrapper package, which " "allows you to use a Windows driver." msgstr "有些情况下,您需要的驱动程序不包含在 Debian 软件包里面。必须在互联网上寻找它们的源码,并自己动手编译驱动程序。该如何做已经超出了本手册的范围。如果没有 Linux 驱动程序,您最后可以用 ndiswrapper 软件包,它让您使用 Windows 的驱动程序。" #. Tag: title #: hardware.xml:2575 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "&arch-title; 的一些已知问题" #. Tag: para #: hardware.xml:2576 #, no-c-format msgid "" "There are a couple of issues with specific network cards that are worth " "mentioning here." msgstr "有些特定的网卡事项需要在此提及。" #. Tag: title #: hardware.xml:2583 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "tulip 和 dfme 驱动程序之间的冲突" #. Tag: para #: hardware.xml:2585 #, no-c-format msgid "" "There are various PCI network cards that have the same PCI identification, " "but are supported by related, but different drivers. Some cards work with " "the tulip driver, others with the dfme " "driver. Because they have the same identification, the kernel cannot " "distinguish between them and it is not certain which driver will be loaded. " "If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "有些 PCI 网卡具有相同的 PCI 标识,但却由不同的驱动程序支持。有些网卡在 tulip 驱动程序下工作,其他的在 dfme 驱动程序下工作。因为它们具有相同的标识,内核不能辨别而无法加载合适的驱动程序。如果使用不正确的驱动程序,网卡可能不工作,或者工作不正常。" #. Tag: para #: hardware.xml:2595 #, no-c-format msgid "" "This is a common problem on Netra systems with a Davicom (DEC-Tulip " "compatible) NIC. In that case the tulip driver is " "probably the correct one. During the installation the solution is to switch " "to a shell and unload the wrong driver module using modprobe -r " "module (or both, if they are both " "loaded). After that you can load the correct module using " "modprobe module." msgstr "常见的问题出现在使用 Davicom (DEC-Tulip 兼容的) NIC 网卡的 Netra 系统上。这种情况下,tulip 驱动程序可能是正确的。安装过程中的解决方法是切换到一个 shell 并使用 modprobe -r module 卸载不正确的驱动程序模块 (如果都加载了,或者两个都卸载)。之后,您可以通过 modprobe module 加载正确的模块。" #. Tag: title #: hardware.xml:2610 #, no-c-format msgid "Sun B100 blade" msgstr "Sun B100 blade" #. Tag: para #: hardware.xml:2612 #, no-c-format msgid "" "The cassini network driver does not work with Sun B100 " "blade systems." msgstr "cassini 网络驱动程序不能工作在 Sun B100 刀片系统上。"