1
# SOME DESCRIPTIVE TITLE.
2
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
7
"Project-Id-Version: PACKAGE VERSION\n"
8
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
9
"POT-Creation-Date: 2008-05-02 00:09+0000\n"
10
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
11
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
12
"Language-Team: LANGUAGE <LL@li.org>\n"
14
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
15
"Content-Transfer-Encoding: 8bit\n"
20
msgid "System Requirements"
26
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."
32
msgid "Supported Hardware"
38
msgid "Debian does not impose hardware requirements beyond the requirements of the Linux kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux kernel, libc, <command>gcc</command>, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with Debian."
44
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."
50
msgid "Supported Architectures"
56
msgid "Debian &release; supports twelve major architectures and several variations of each architecture known as <quote>flavors</quote>."
68
msgid "Debian Designation"
74
msgid "Subarchitecture"
86
msgid "Intel x86-based"
98
msgid "AMD64 & Intel EM64T"
122
msgid "ARM and StrongARM"
128
msgid "<entry>arm</entry>"
134
msgid "Netwinder and CATS"
188
msgid "<entry>32</entry>"
200
msgid "<entry>64</entry>"
218
msgid "MIPS (big endian)"
230
msgid "SGI IP22 (Indy/Indigo 2)"
242
msgid "SGI IP32 (O2)"
252
#: hardware.xml:119 hardware.xml:137
254
msgid "Broadcom BCM91250A (SWARM)"
258
#: hardware.xml:120 hardware.xml:138
260
msgid "sb1-bcm91250a"
264
#: hardware.xml:122 hardware.xml:140
266
msgid "Broadcom BCM91480B (BigSur)"
270
#: hardware.xml:123 hardware.xml:141
272
msgid "sb1a-bcm91480b"
278
msgid "MIPS (little endian)"
306
#: hardware.xml:133 hardware.xml:1086 hardware.xml:1101 hardware.xml:1111
312
#: hardware.xml:135 hardware.xml:1081 hardware.xml:1091 hardware.xml:1096 hardware.xml:1106
320
msgid "Motorola 680x0"
356
msgid "68k Macintosh"
362
msgid "<entry>mac</entry>"
368
msgid "<entry>VME</entry>"
392
msgid "IBM/Motorola PowerPC"
398
msgid "<entry>powerpc</entry>"
434
msgid "<entry>prep</entry>"
452
msgid "<entry>sun4u</entry>"
464
msgid "<entry>sun4v</entry>"
482
msgid "IPL from VM-reader and DASD"
494
msgid "IPL from tape"
506
msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages."
512
msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
516
#: hardware.xml:228 hardware.xml:687 hardware.xml:723 hardware.xml:801 hardware.xml:820 hardware.xml:906 hardware.xml:948 hardware.xml:1016 hardware.xml:1175
518
msgid "CPU, Main Boards, and Video Support"
524
msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks."
530
msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system."
536
msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:"
542
msgid "Hardware Type"
566
msgid "AlphaStation 500 5/266.300"
576
#: hardware.xml:271 hardware.xml:275 hardware.xml:279
584
msgid "AlphaStation 500 5/333...500"
596
msgid "AlphaStation 600/266...300"
608
msgid "AlphaStation 600/300...433"
614
msgid "<entry>XLT</entry>"
620
msgid "<entry>xlt</entry>"
632
msgid "AlphaBook1 (laptop)"
638
msgid "Alphabook1/Burns"
656
msgid "AlphaStation 200 4/100...166"
666
#: hardware.xml:297 hardware.xml:301 hardware.xml:305 hardware.xml:309 hardware.xml:313 hardware.xml:317 hardware.xml:321 hardware.xml:325
674
msgid "AlphaStation 200 4/233"
686
msgid "AlphaStation 205 4/133...333"
692
msgid "<entry>LX3</entry>"
698
msgid "AlphaStation 250 4/300"
704
msgid "<entry>M3+</entry>"
710
msgid "AlphaStation 255 4/133...333"
722
msgid "AlphaStation 300 4/266"
734
msgid "AlphaStation 400 4/166"
746
msgid "AlphaStation 400 4/233...300"
756
#: hardware.xml:329 hardware.xml:342 hardware.xml:343
782
msgid "AlphaPC164-LX"
800
msgid "AlphaPC164-SX"
822
#: hardware.xml:348 hardware.xml:357 hardware.xml:358
834
#: hardware.xml:350 hardware.xml:354
840
#: hardware.xml:351 hardware.xml:355
858
#: hardware.xml:363 hardware.xml:364 hardware.xml:365
870
#: hardware.xml:368 hardware.xml:369
890
msgid "DEC 2000 Model 300(S)"
894
#: hardware.xml:376 hardware.xml:384
900
#: hardware.xml:377 hardware.xml:381 hardware.xml:385 hardware.xml:446 hardware.xml:450 hardware.xml:468 hardware.xml:472 hardware.xml:476 hardware.xml:480 hardware.xml:484 hardware.xml:488 hardware.xml:492 hardware.xml:506 hardware.xml:510 hardware.xml:514 hardware.xml:518 hardware.xml:522 hardware.xml:556 hardware.xml:560 hardware.xml:564 hardware.xml:568 hardware.xml:582 hardware.xml:586 hardware.xml:590 hardware.xml:594 hardware.xml:601 hardware.xml:605 hardware.xml:609 hardware.xml:613 hardware.xml:617 hardware.xml:621 hardware.xml:625 hardware.xml:629 hardware.xml:633 hardware.xml:637 hardware.xml:641 hardware.xml:645 hardware.xml:649 hardware.xml:656 hardware.xml:660
902
msgid "<entry>N/A</entry>"
908
msgid "DEC 2000 Model 500"
932
msgid "Personal WorkStation 433a"
936
#: hardware.xml:391 hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419
942
#: hardware.xml:392 hardware.xml:396 hardware.xml:400 hardware.xml:404 hardware.xml:408 hardware.xml:412 hardware.xml:416 hardware.xml:420
950
msgid "Personal WorkStation 433au"
956
msgid "Personal WorkStation 466au"
962
msgid "Personal WorkStation 500a"
968
msgid "Personal WorkStation 500au"
974
msgid "Personal WorkStation 550au"
980
msgid "Personal WorkStation 600a"
986
msgid "Personal WorkStation 600au"
998
msgid "AlphaServer 1000 4/200"
1008
#: hardware.xml:427 hardware.xml:431 hardware.xml:435 hardware.xml:439
1016
msgid "AlphaServer 1000 4/233..266"
1026
#: hardware.xml:433 hardware.xml:437
1028
msgid "AlphaServer 1000 5/300"
1034
msgid "Mikasa-Pinnacle"
1040
msgid "Mikasa-Primo"
1070
msgid "Galaxy-Train/Nautilus Jr."
1092
#: hardware.xml:457 hardware.xml:461
1100
msgid "<entry>UDB</entry>"
1118
msgid "AlphaServer 1000A 4/233...266"
1130
msgid "AlphaServer 1000A 5/300"
1136
msgid "Noritake-Pinnacle"
1142
msgid "AlphaServer 1000A 5/333...500"
1148
msgid "Noritake-Primo"
1154
msgid "AlphaServer 800 5/333...500"
1158
#: hardware.xml:479 hardware.xml:487 hardware.xml:491
1166
msgid "AlphaStation 600 A"
1178
msgid "Digital Server 3300"
1184
msgid "Digital Server 3300R"
1190
msgid "PLATFORM 2000"
1194
#: hardware.xml:497 hardware.xml:498
1196
msgid "<entry>P2K</entry>"
1202
msgid "<entry>p2k</entry>"
1214
msgid "AlphaServer 1200 5/xxx"
1218
#: hardware.xml:505 hardware.xml:517
1220
msgid "Tincup/DaVinci"
1226
msgid "AlphaServer 4000 5/xxx"
1232
msgid "Wrangler/Durango"
1238
msgid "AlphaServer 4100 5/xxx"
1242
#: hardware.xml:513 hardware.xml:521
1250
msgid "Digital Server 5300"
1256
msgid "Digital Server 7300"
1268
msgid "DeskStation AlphaPC164-UX"
1272
#: hardware.xml:528 hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 hardware.xml:548
1278
#: hardware.xml:529 hardware.xml:533 hardware.xml:537 hardware.xml:541 hardware.xml:545 hardware.xml:549
1286
msgid "DeskStation RPL164-2"
1292
msgid "DeskStation RPL164-4"
1298
msgid "DeskStation RPX164-2"
1304
msgid "DeskStation RPX164-4"
1310
msgid "Samsung AlphaPC164-BX"
1322
msgid "AlphaServer 2000 4/xxx"
1334
msgid "AlphaServer 2000 5/xxx"
1340
msgid "Demi-Gamma-Sable"
1346
msgid "AlphaServer 2100 4/xxx"
1358
msgid "AlphaServer 2100 5/xxx"
1376
msgid "21164 PICMG SBC"
1400
msgid "AlphaServer DS15"
1412
msgid "AlphaServer DS25"
1424
msgid "AlphaServer ES45"
1434
#: hardware.xml:592 hardware.xml:631 hardware.xml:635
1454
msgid "AlphaServer DS10"
1458
#: hardware.xml:600 hardware.xml:648
1466
msgid "AlphaServer DS10L"
1478
msgid "AlphaServer DS20"
1484
msgid "Catamaran/Goldrush"
1490
msgid "AlphaServer DS20E"
1502
msgid "AlphaServer DS20L"
1514
msgid "AlphaServer ES40"
1524
#: hardware.xml:623 hardware.xml:624
1532
msgid "SMARTengine 21264 PCI/ISA SBC"
1574
msgid "Monet/Brisbane"
1592
msgid "AlphaServer GS160"
1596
#: hardware.xml:655 hardware.xml:659
1604
msgid "AlphaServer GS320"
1608
#: hardware.xml:664 hardware.xml:666
1610
msgid "<entry>XL</entry>"
1616
msgid "XL-233...266"
1622
msgid "<entry>xl</entry>"
1628
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."
1632
#: hardware.xml:688 hardware.xml:821
1634
msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
1638
#: hardware.xml:696 hardware.xml:829 hardware.xml:989
1640
msgid "<title>CPU</title>"
1646
msgid "Both AMD64 and Intel EM64T processors are supported."
1652
msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU."
1658
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."
1664
msgid "The supported platforms are:"
1676
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)."
1688
msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
1700
msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>."
1706
msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
1712
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."
1718
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."
1724
msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>."
1736
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."
1742
msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics."
1748
msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details."
1754
msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian."
1760
msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
1766
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."
1770
#: hardware.xml:1000
1772
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."
1776
#: hardware.xml:1017
1778
msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
1782
#: hardware.xml:1057
1784
msgid "CPU/Machine types"
1788
#: hardware.xml:1059
1790
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:"
1794
#: hardware.xml:1071
1800
#: hardware.xml:1071
1802
msgid "<entry>CPU</entry>"
1806
#: hardware.xml:1071
1812
#: hardware.xml:1072
1814
msgid "Debian subarchitecture"
1818
#: hardware.xml:1078
1820
msgid "DECstation 5000/1xx"
1824
#: hardware.xml:1079 hardware.xml:1089 hardware.xml:1094 hardware.xml:1104
1830
#: hardware.xml:1080 hardware.xml:1085
1836
#: hardware.xml:1083
1838
msgid "DECstation 5000/150"
1842
#: hardware.xml:1084 hardware.xml:1109
1848
#: hardware.xml:1088
1850
msgid "DECstation 5000/200"
1854
#: hardware.xml:1090
1860
#: hardware.xml:1093
1862
msgid "DECstation 5000/240"
1866
#: hardware.xml:1095 hardware.xml:1100
1872
#: hardware.xml:1098
1874
msgid "DECstation 5000/260"
1878
#: hardware.xml:1099
1884
#: hardware.xml:1103
1886
msgid "Personal DECstation 5000/xx"
1890
#: hardware.xml:1105 hardware.xml:1110
1896
#: hardware.xml:1108
1898
msgid "Personal DECstation 5000/50"
1902
#: hardware.xml:1115
1904
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."
1908
#: hardware.xml:1122
1910
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."
1914
#: hardware.xml:1132
1916
msgid "Supported console options"
1920
#: hardware.xml:1133
1922
msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options."
1926
#: hardware.xml:1144
1929
"If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n"
1930
"$ cu -l /dev/ttyS1 -s 9600\n"
1931
"</screen></informalexample> where the option <literal>-l</literal> (line) sets the serial port to use and <literal>-s</literal> (speed) sets the speed for the connection (9600 bits per second)."
1935
#: hardware.xml:1162
1937
msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps."
1941
#: hardware.xml:1176
1943
msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants."
1947
#: hardware.xml:1184
1949
msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future."
1953
#: hardware.xml:1192
1955
msgid "Kernel Flavours"
1959
#: hardware.xml:1194
1961
msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:"
1965
#: hardware.xml:1201
1967
msgid "<term>powerpc</term>"
1971
#: hardware.xml:1202
1973
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."
1977
#: hardware.xml:1212
1983
#: hardware.xml:1213
1985
msgid "The power64 kernel flavour supports the following CPUs:"
1989
#: hardware.xml:1217
1991
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."
1995
#: hardware.xml:1223
1997
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."
2001
#: hardware.xml:1228
2003
msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
2007
#: hardware.xml:1237
2009
msgid "<term>prep</term>"
2013
#: hardware.xml:1238
2015
msgid "This kernel flavour supports the PReP subarchitecture."
2019
#: hardware.xml:1246
2025
#: hardware.xml:1247
2027
msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled."
2031
#: hardware.xml:1260
2033
msgid "Power Macintosh (pmac) subarchitecture"
2037
#: hardware.xml:1262
2039
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."
2043
#: hardware.xml:1269
2045
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."
2049
#: hardware.xml:1277
2051
msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
2055
#: hardware.xml:1285
2057
msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
2061
#: hardware.xml:1301 hardware.xml:1436 hardware.xml:1480 hardware.xml:1509
2063
msgid "Model Name/Number"
2067
#: hardware.xml:1302
2073
#: hardware.xml:1308
2079
#: hardware.xml:1309
2081
msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
2085
#: hardware.xml:1310 hardware.xml:1313 hardware.xml:1316 hardware.xml:1319 hardware.xml:1322 hardware.xml:1325 hardware.xml:1328 hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1352 hardware.xml:1355
2091
#: hardware.xml:1312
2093
msgid "iMac Summer 2000, Early 2001"
2097
#: hardware.xml:1315
2103
#: hardware.xml:1318
2105
msgid "iBook, iBook SE, iBook Dual USB"
2109
#: hardware.xml:1321
2115
#: hardware.xml:1324
2121
#: hardware.xml:1327
2123
msgid "Power Macintosh Blue and White (B&W) G3"
2127
#: hardware.xml:1330
2129
msgid "Power Macintosh G4 PCI, AGP, Cube"
2133
#: hardware.xml:1333
2135
msgid "Power Macintosh G4 Gigabit Ethernet"
2139
#: hardware.xml:1336
2141
msgid "Power Macintosh G4 Digital Audio, Quicksilver"
2145
#: hardware.xml:1339
2147
msgid "Power Macintosh G5"
2151
#: hardware.xml:1342
2153
msgid "PowerBook G3 FireWire Pismo (2000)"
2157
#: hardware.xml:1345
2159
msgid "PowerBook G3 Lombard (1999)"
2163
#: hardware.xml:1348
2165
msgid "PowerBook G4 Titanium"
2169
#: hardware.xml:1351
2171
msgid "PowerBook G4 Aluminum"
2175
#: hardware.xml:1354
2181
#: hardware.xml:1357
2183
msgid "Performa 4400, 54xx, 5500"
2187
#: hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 hardware.xml:1376 hardware.xml:1379 hardware.xml:1382 hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1397 hardware.xml:1400 hardware.xml:1406 hardware.xml:1412 hardware.xml:1418
2193
#: hardware.xml:1360
2195
msgid "Performa 6360, 6400, 6500"
2199
#: hardware.xml:1363
2201
msgid "Power Macintosh 4400, 5400"
2205
#: hardware.xml:1366
2207
msgid "Power Macintosh 7200, 7300, 7500, 7600"
2211
#: hardware.xml:1369
2213
msgid "Power Macintosh 8200, 8500, 8600"
2217
#: hardware.xml:1372
2219
msgid "Power Macintosh 9500, 9600"
2223
#: hardware.xml:1375
2225
msgid "Power Macintosh (Beige) G3 Minitower"
2229
#: hardware.xml:1378
2231
msgid "Power Macintosh (Beige) Desktop, All-in-One"
2235
#: hardware.xml:1381
2237
msgid "PowerBook 2400, 3400, 3500"
2241
#: hardware.xml:1384
2243
msgid "PowerBook G3 Wallstreet (1998)"
2247
#: hardware.xml:1387
2249
msgid "Twentieth Anniversary Macintosh"
2253
#: hardware.xml:1390
2255
msgid "Workgroup Server 7250, 7350, 8550, 9650, G3"
2259
#: hardware.xml:1395
2261
msgid "Power Computing"
2265
#: hardware.xml:1396
2267
msgid "PowerBase, PowerTower / Pro, PowerWave"
2271
#: hardware.xml:1399
2273
msgid "PowerCenter / Pro, PowerCurve"
2277
#: hardware.xml:1404
2283
#: hardware.xml:1405
2285
msgid "C500, C600, J700, S900"
2289
#: hardware.xml:1410
2291
msgid "<entry>APS</entry>"
2295
#: hardware.xml:1411
2297
msgid "APS Tech M*Power 604e/2000"
2301
#: hardware.xml:1416 hardware.xml:1442
2307
#: hardware.xml:1417
2309
msgid "Starmax 3000, 4000, 5000, 5500"
2313
#: hardware.xml:1426
2315
msgid "PReP subarchitecture"
2319
#: hardware.xml:1443
2321
msgid "Firepower, PowerStack Series E, PowerStack II"
2325
#: hardware.xml:1445
2327
msgid "MPC 7xx, 8xx"
2331
#: hardware.xml:1447
2337
#: hardware.xml:1449
2339
msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx"
2343
#: hardware.xml:1451
2349
#: hardware.xml:1455 hardware.xml:1486
2355
#: hardware.xml:1456
2361
#: hardware.xml:1458
2363
msgid "Power 830/850/860 (6070, 6050)"
2367
#: hardware.xml:1460
2369
msgid "6030, 7025, 7043"
2373
#: hardware.xml:1462
2379
#: hardware.xml:1470
2381
msgid "CHRP subarchitecture"
2385
#: hardware.xml:1487
2387
msgid "B50, 43P-150, 44P"
2391
#: hardware.xml:1490
2397
#: hardware.xml:1491
2399
msgid "Pegasos I, Pegasos II"
2403
#: hardware.xml:1499
2405
msgid "APUS subarchitecture"
2409
#: hardware.xml:1515
2411
msgid "Amiga Power-UP Systems (APUS)"
2415
#: hardware.xml:1516
2417
msgid "A1200, A3000, A4000"
2421
#: hardware.xml:1524
2423
msgid "Nubus PowerMac subarchitecture (unsupported)"
2427
#: hardware.xml:1526
2429
msgid "NuBus systems are not currently supported by Debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
2433
#: hardware.xml:1563
2435
msgid "Non-PowerPC Macs"
2439
#: hardware.xml:1565
2441
msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
2445
#: hardware.xml:1574
2447
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."
2451
#: hardware.xml:1582
2453
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)."
2457
#: hardware.xml:1598
2459
msgid "S/390 and zSeries machine types"
2463
#: hardware.xml:1599
2465
msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance."
2469
#: hardware.xml:1621
2471
msgid "CPU and Main Boards Support"
2475
#: hardware.xml:1622
2477
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."
2481
#: hardware.xml:1633
2483
msgid "sun4, sun4c, sun4d, sun4m"
2487
#: hardware.xml:1635
2489
msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
2493
#: hardware.xml:1642
2495
msgid "The last Debian release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
2499
#: hardware.xml:1652
2501
msgid "<term>sun4u</term>"
2505
#: hardware.xml:1654
2507
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."
2511
#: hardware.xml:1667
2513
msgid "<term>sun4v</term>"
2517
#: hardware.xml:1669
2519
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."
2523
#: hardware.xml:1680
2525
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."
2529
#: hardware.xml:1689
2531
msgid "Graphics Card Support"
2535
#: hardware.xml:1690
2537
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."
2541
#: hardware.xml:1698
2543
msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;."
2547
#: hardware.xml:1707
2549
msgid "The X.Org X Window System is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
2553
#: hardware.xml:1716
2555
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 <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
2559
#: hardware.xml:1724
2561
msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
2565
#: hardware.xml:1734
2567
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."
2571
#: hardware.xml:1751
2577
#: hardware.xml:1752
2579
msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>"
2583
#: hardware.xml:1763 hardware.xml:1785 hardware.xml:1805 hardware.xml:1828
2585
msgid "Multiple Processors"
2589
#: hardware.xml:1764
2591
msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead."
2595
#: hardware.xml:1772
2597
msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config."
2601
#: hardware.xml:1787
2603
msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
2607
#: hardware.xml:1796
2609
msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support."
2613
#: hardware.xml:1806
2615
msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
2619
#: hardware.xml:1815
2621
msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config."
2625
#: hardware.xml:1829
2627
msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
2631
#: hardware.xml:1839
2633
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."
2637
#: hardware.xml:1845
2639
msgid "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config."
2643
#: hardware.xml:1862
2645
msgid "Installation Media"
2649
#: hardware.xml:1864
2651
msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
2655
#: hardware.xml:1875
2661
#: hardware.xml:1876
2663
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."
2667
#: hardware.xml:1882
2669
msgid "For CHRP, floppy support is currently broken."
2673
#: hardware.xml:1889
2675
msgid "CD-ROM/DVD-ROM"
2679
#: hardware.xml:1891
2681
msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI."
2685
#: hardware.xml:1898
2687
msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>."
2691
#: hardware.xml:1910
2693
msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux."
2697
#: hardware.xml:1920
2699
msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
2703
#: hardware.xml:1925
2705
msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>."
2709
#: hardware.xml:1934
2711
msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
2715
#: hardware.xml:1938
2717
msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card."
2721
#: hardware.xml:1953
2723
msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position."
2727
#: hardware.xml:1962
2729
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)."
2733
#: hardware.xml:1971
2735
msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:"
2739
#: hardware.xml:1983
2741
msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..."
2745
#: hardware.xml:1990
2751
#: hardware.xml:1992
2753
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."
2757
#: hardware.xml:1998
2759
msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines."
2763
#: hardware.xml:2003
2765
msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
2769
#: hardware.xml:2011
2771
msgid "USB Memory Stick"
2775
#: hardware.xml:2013
2777
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."
2781
#: hardware.xml:2025
2787
#: hardware.xml:2027
2789
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."
2793
#: hardware.xml:2037
2795
msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips\">This is the preferred installation technique for &arch-title;.</phrase>"
2799
#: hardware.xml:2043
2801
msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
2805
#: hardware.xml:2051
2807
msgid "Un*x or GNU system"
2811
#: hardware.xml:2053
2813
msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>."
2817
#: hardware.xml:2065
2819
msgid "Supported Storage Systems"
2823
#: hardware.xml:2067
2825
msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware."
2829
#: hardware.xml:2077
2831
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."
2835
#: hardware.xml:2084
2837
msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details."
2841
#: hardware.xml:2094
2843
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."
2847
#: hardware.xml:2104
2849
msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
2853
#: hardware.xml:2137
2855
msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)"
2859
#: hardware.xml:2146
2861
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."
2865
#: hardware.xml:2152
2867
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."
2871
#: hardware.xml:2158
2873
msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
2877
#: hardware.xml:2163
2879
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)."
2883
#: hardware.xml:2180
2885
msgid "Peripherals and Other Hardware"
2889
#: hardware.xml:2181
2891
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."
2895
#: hardware.xml:2187
2897
msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)."
2901
#: hardware.xml:2193
2903
msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux."
2907
#: hardware.xml:2199
2909
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."
2913
#: hardware.xml:2205
2915
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."
2919
#: hardware.xml:2211
2921
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."
2925
#: hardware.xml:2221
2927
msgid "Purchasing Hardware Specifically for GNU/Linux"
2931
#: hardware.xml:2223
2933
msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
2937
#: hardware.xml:2231
2939
msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all."
2943
#: hardware.xml:2236
2945
msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
2949
#: hardware.xml:2244
2951
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."
2955
#: hardware.xml:2255
2957
msgid "Avoid Proprietary or Closed Hardware"
2961
#: hardware.xml:2256
2963
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."
2967
#: hardware.xml:2263
2969
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."
2973
#: hardware.xml:2274
2975
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."
2979
#: hardware.xml:2286
2981
msgid "Windows-specific Hardware"
2985
#: hardware.xml:2287
2987
msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence."
2991
#: hardware.xml:2300
2993
msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware."
2997
#: hardware.xml:2321
2999
msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>."
3003
#: hardware.xml:2338
3005
msgid "Memory and Disk Space Requirements"
3009
#: hardware.xml:2340
3011
msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
3015
#: hardware.xml:2347
3017
msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
3021
#: hardware.xml:2364
3023
msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically."
3027
#: hardware.xml:2373
3029
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."
3033
#: hardware.xml:2381
3035
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."
3039
#: hardware.xml:2391
3041
msgid "FIXME: is this still true?"
3045
#: hardware.xml:2402
3047
msgid "Network Connectivity Hardware"
3051
#: hardware.xml:2403
3053
msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>"
3057
#: hardware.xml:2415
3059
msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
3063
#: hardware.xml:2421
3069
#: hardware.xml:2426
3071
msgid "Sun Happy Meal"
3075
#: hardware.xml:2431
3081
#: hardware.xml:2436
3083
msgid "Sun QuadEthernet"
3087
#: hardware.xml:2441
3089
msgid "MyriCOM Gigabit Ethernet"
3093
#: hardware.xml:2448
3095
msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work."
3099
#: hardware.xml:2454
3101
msgid "The list of supported network devices is:"
3105
#: hardware.xml:2459
3107
msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
3111
#: hardware.xml:2464
3113
msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
3117
#: hardware.xml:2469
3119
msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
3123
#: hardware.xml:2478
3125
msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>."
3129
#: hardware.xml:2488
3131
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."
3135
#: hardware.xml:2497
3137
msgid "Drivers Requiring Firmware"
3141
#: hardware.xml:2498
3143
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."
3147
#: hardware.xml:2504
3149
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 <quote>main</quote> section of the &debian; archive."
3153
#: hardware.xml:2515
3155
msgid "If the driver itself <emphasis>is</emphasis> supported, you may also be able to use the NIC during installation by copying the firmware from some medium to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy the firmware to that location for the installed system before the reboot at the end of the installation."
3159
#: hardware.xml:2527
3161
msgid "Wireless Network Cards"
3165
#: hardware.xml:2528
3167
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."
3171
#: hardware.xml:2535
3173
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."
3177
#: hardware.xml:2541
3179
msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
3183
#: hardware.xml:2555
3185
msgid "Known Issues for &arch-title;"
3189
#: hardware.xml:2556
3191
msgid "There are a couple of issues with specific network cards that are worth mentioning here."
3195
#: hardware.xml:2563
3197
msgid "Conflict between tulip and dfme drivers"
3201
#: hardware.xml:2565
3203
msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
3207
#: hardware.xml:2575
3209
msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
3213
#: hardware.xml:2583
3215
msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
3219
#: hardware.xml:2596
3221
msgid "Sun B100 blade"
3225
#: hardware.xml:2598
3227
msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
added
removed
po/nn/hardware.po
