42
#: boot-installer.xml:38
44
msgid "Alpha Console Firmware"
48
#: boot-installer.xml:39
50
msgid "Console firmware is stored in a flash ROM and started when an Alpha system is powered up or reset. There are two different console specifications used on Alpha systems, and hence two classes of console firmware available:"
54
#: boot-installer.xml:49
56
msgid "<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems."
60
#: boot-installer.xml:56
62
msgid "<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT."
66
#: boot-installer.xml:65
68
msgid "From the user's perspective, the most important difference between SRM and ARC is that the choice of console constrains the possible disk-partitioning scheme for the hard disk which you wish to boot off of."
72
#: boot-installer.xml:72
74
msgid "ARC requires that you use an MS-DOS partition table (as created by <command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition tables are the <quote>native</quote> partition format when booting from ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may prefer to partition your disks from the firmware menus before installing Linux."
78
#: boot-installer.xml:81
80
msgid "Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> Specifically, the bootsector format required by the Console Subsystem Specification conflicts with the placement of the DOS partition table. </para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD disklabel format, this is the <quote>native</quote> partition format for SRM installations."
84
#: boot-installer.xml:94
86
msgid "GNU/Linux is the only operating system on Alpha that can be booted from both console types, but &debian; &release; only supports booting on SRM-based systems. If you have an Alpha for which no version of SRM is available, if you will be dual-booting the system with Windows NT, or if your boot device requires ARC console support for BIOS initialization, you will not be able to use the &debian; &release; installer. You can still run &debian; &release; on such systems by using other install media; for instance, you can install Debian woody with MILO and upgrade."
90
#: boot-installer.xml:105
92
msgid "Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM when possible."
96
#: boot-installer.xml:113
98
msgid "The following table summarizes available and supported system type/console combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). The word <quote>ARC</quote> below denotes any of the ARC-compliant consoles."
102
#: boot-installer.xml:125
108
#: boot-installer.xml:126
110
msgid "Console Type Supported"
114
#: boot-installer.xml:132
120
#: boot-installer.xml:133 boot-installer.xml:136 boot-installer.xml:142 boot-installer.xml:148 boot-installer.xml:151 boot-installer.xml:154 boot-installer.xml:157 boot-installer.xml:163 boot-installer.xml:166 boot-installer.xml:169 boot-installer.xml:178 boot-installer.xml:187 boot-installer.xml:202 boot-installer.xml:205
126
#: boot-installer.xml:135
132
#: boot-installer.xml:138
138
#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:160 boot-installer.xml:172 boot-installer.xml:181 boot-installer.xml:184 boot-installer.xml:190 boot-installer.xml:196 boot-installer.xml:199
144
#: boot-installer.xml:141
150
#: boot-installer.xml:144
156
#: boot-installer.xml:147
162
#: boot-installer.xml:150
168
#: boot-installer.xml:153
174
#: boot-installer.xml:156
180
#: boot-installer.xml:159
186
#: boot-installer.xml:162
192
#: boot-installer.xml:165
198
#: boot-installer.xml:168
204
#: boot-installer.xml:171
210
#: boot-installer.xml:174
216
#: boot-installer.xml:175
218
msgid "ARC (see motherboard manual) or SRM"
222
#: boot-installer.xml:177
228
#: boot-installer.xml:180
234
#: boot-installer.xml:183
240
#: boot-installer.xml:186
246
#: boot-installer.xml:189
252
#: boot-installer.xml:192
258
#: boot-installer.xml:193 boot-installer.xml:208 boot-installer.xml:211
264
#: boot-installer.xml:195
270
#: boot-installer.xml:198
276
#: boot-installer.xml:201
282
#: boot-installer.xml:204
288
#: boot-installer.xml:207
290
msgid "<entry>xl</entry>"
294
#: boot-installer.xml:210
296
msgid "<entry>xlt</entry>"
300
#: boot-installer.xml:218
302
msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. For the SRM console, <command>aboot</command>, a small, platform-independent bootloader, is used. See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>."
306
#: boot-installer.xml:227
308
msgid "The following paragraphs are from the woody install manual, and are included here for reference; they may be useful to someone at a later date when Debian supports MILO-based installs again."
312
#: boot-installer.xml:233
314
msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. There are two mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>."
318
#: boot-installer.xml:239
320
msgid "<command>MILO</command> is itself a console, which replaces ARC or SRM in memory. <command>MILO</command> can be booted from both ARC and SRM and is the only way to bootstrap Linux from the ARC console. <command>MILO</command> is platform-specific (a different <command>MILO</command> is needed for each system type) and exist only for those systems, for which ARC support is shown in the table above. See also the (unfortunately outdated) <ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>."
324
#: boot-installer.xml:249
326
msgid "<command>aboot</command> is a small, platform-independent bootloader, which runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>."
330
#: boot-installer.xml:256
333
"Thus, three scenarios are generally possible, depending on the system's console firmware and whether or not <command>MILO</command> is available: <informalexample><screen>\n"
337
"</screen></informalexample> Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM and <command>aboot</command> on new installations of GNU/Linux, unless you wish to dual-boot with Windows NT."
341
#: boot-installer.xml:271
343
msgid "The majority of AlphaServers and all current server and workstation products contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</quote> machines such as the various evaluation boards, it is possible to switch from one version to another by reflashing the firmware. Also, once SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk (using the <command>arc</command> command). For the reasons mentioned above, we recommend switching to SRM before installing &debian;."
347
#: boot-installer.xml:282
349
msgid "As on other architectures, you should install the newest available revision of the firmware<footnote> <para> Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 — see <ulink url=\"&url-jensen-howto;\"></ulink> for more information. </para> </footnote> before installing &debian;. For Alpha, firmware updates can be obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>."
353
#: boot-installer.xml:301 boot-installer.xml:1050 boot-installer.xml:1577 boot-installer.xml:2074 boot-installer.xml:2156 boot-installer.xml:2245 boot-installer.xml:2591 boot-installer.xml:2700
355
msgid "Booting with TFTP"
359
#: boot-installer.xml:302
362
"In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> prefix, and will be listed in the output of the <userinput>show dev</userinput> command, like this (edited slightly): <informalexample><screen>\n"
363
">>> show dev\n"
364
"ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n"
365
"ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n"
366
"ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n"
367
"</screen></informalexample> You first need to set the boot protocol: <informalexample><screen>\n"
368
">>> set ewa0_protocols bootp\n"
369
"</screen></informalexample> Then check the medium type is correct: <informalexample><screen>\n"
370
">>> set ewa0_mode <replaceable>mode</replaceable>\n"
371
"</screen></informalexample> You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>."
375
#: boot-installer.xml:320
378
"Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>\n"
379
">>> boot ewa0 -flags \"\"\n"
380
"</screen></informalexample> This will boot using the default kernel parameters as included in the netboot image."
384
#: boot-installer.xml:329
386
msgid "If you wish to use a serial console, you <emphasis>must</emphasis> pass the <userinput>console=</userinput> parameter to the kernel. This can be done using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</userinput> command. The serial ports are named the same as their corresponding files in <userinput>/dev</userinput>. Also, when specifying additional kernel parameters, you must repeat certain default options that are needed by the &d-i; images. For example, to boot from <userinput>ewa0</userinput> and use a console on the first serial port, you would type:"
390
#: boot-installer.xml:341
392
msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0""
396
#: boot-installer.xml:346
398
msgid "Booting from CD-ROM with the SRM Console"
402
#: boot-installer.xml:347
405
"The &debian; install CDs include several preconfigured boot options for VGA and serial consoles. Type <informalexample><screen>\n"
406
">>> boot xxxx -flags 0\n"
407
"</screen></informalexample> to boot using VGA console, where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. To use serial console on the first serial device, type <informalexample><screen>\n"
408
">>> boot xxxx -flags 1\n"
409
"</screen></informalexample> and for console on the second serial port, type"
413
#: boot-installer.xml:362
415
msgid ">>> boot xxxx -flags 2"
419
#: boot-installer.xml:368
421
msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console"
425
#: boot-installer.xml:369
427
msgid "To boot a CD-ROM from the ARC console, find your sub-architecture code name (see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload.exe</filename> as the boot loader and <filename>\\milo\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</replaceable> is the proper subarchitecture name) as the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: You need to use <filename>\\milo\\ldmilo.exe</filename> as boot loader."
431
#: boot-installer.xml:385
433
msgid "Booting from Floppies with the SRM Console"
437
#: boot-installer.xml:386
440
"At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>\n"
441
">>> boot dva0 -flags 0\n"
442
"</screen></informalexample> possibly replacing <filename>dva0</filename> with the actual device name. Usually, <filename>dva0</filename> is the floppy; type <informalexample><screen>\n"
443
">>> show dev\n"
444
"</screen></informalexample> to see the list of devices (e.g., if you want to boot from a CD). Note that if you are booting via MILO, <command>-flags</command> argument is ignored, so you can just type <command>boot dva0</command>. If everything works OK, you will eventually see the Linux kernel boot."
448
#: boot-installer.xml:403
451
"If you want to specify kernel parameters when booting via <command>aboot</command>, use the following command: <informalexample><screen>\n"
452
">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n"
453
"</screen></informalexample> (typed on one line), substituting, if necessary, the actual SRM boot device name for <filename>dva0</filename>, the Linux boot device name for <filename>fd0</filename>, and the desired kernel parameters for <filename>arguments</filename>."
457
#: boot-installer.xml:415
459
msgid "If you want to specify kernel parameters when booting via <command>MILO</command>, you will have to interrupt bootstrap once you get into MILO. See <xref linkend=\"booting-from-milo\"/>."
463
#: boot-installer.xml:425
465
msgid "Booting from Floppies with the ARC or AlphaBIOS Console"
469
#: boot-installer.xml:427
471
msgid "In the OS Selection menu, set <command>linload.exe</command> as the boot loader, and <command>milo</command> as the OS Path. Bootstrap using the newly created entry."
475
#: boot-installer.xml:436
477
msgid "Booting with MILO"
481
#: boot-installer.xml:437
483
msgid "MILO contained on the bootstrap media is configured to proceed straight to Linux automatically. Should you wish to intervene, all you need is to press space during MILO countdown."
487
#: boot-installer.xml:443
490
"If you want to specify all the bits explicitly (for example, to supply additional parameters), you can use a command like this: <informalexample><screen>\n"
491
"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n"
492
"</screen></informalexample> If you are booting from something other than a floppy, substitute <filename>fd0</filename> in the above example with the appropriate device name in Linux notation. The <command>help</command> command would give you a brief MILO command reference."
496
#: boot-installer.xml:462
42
#: boot-installer.xml:37
498
44
msgid "Booting from TFTP"
502
#: boot-installer.xml:468 boot-installer.xml:1056 boot-installer.xml:1595 boot-installer.xml:2080 boot-installer.xml:2597 boot-installer.xml:2706
48
#: boot-installer.xml:43 boot-installer.xml:646 boot-installer.xml:1185 boot-installer.xml:1676 boot-installer.xml:1785
504
50
msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
508
#: boot-installer.xml:473 boot-installer.xml:1061 boot-installer.xml:1600 boot-installer.xml:2085 boot-installer.xml:2602 boot-installer.xml:2711
54
#: boot-installer.xml:48 boot-installer.xml:651 boot-installer.xml:1190 boot-installer.xml:1681 boot-installer.xml:1790
510
56
msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
514
#: boot-installer.xml:478 boot-installer.xml:1066 boot-installer.xml:1605 boot-installer.xml:2090 boot-installer.xml:2607 boot-installer.xml:2716
60
#: boot-installer.xml:53 boot-installer.xml:656 boot-installer.xml:1195 boot-installer.xml:1686 boot-installer.xml:1795
516
62
msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
520
#: boot-installer.xml:486
522
msgid "Booting from TFTP on Netwinder"
526
#: boot-installer.xml:487
528
msgid "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card (which is generally referred to as <literal>eth0</literal>) and a 100Mbps Tulip card. There may be problems loading the image via TFTP using the 100Mbps card so it is recommended that you use the 10Mbps interface (the one labeled with <literal>10 Base-T</literal>)."
532
#: boot-installer.xml:496
534
msgid "You need NeTTrom 2.2.1 or later to boot the installation system, and version 2.3.3 is recommended. Unfortunately, firmware files are currently not available for download because of license issues. If this situation changes, you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>."
538
#: boot-installer.xml:504
541
"When you boot your Netwinder you have to interrupt the boot process during the countdown. This allows you to set a number of firmware settings needed in order to boot the installer. First of all, start by loading the default settings: <informalexample><screen>\n"
542
" NeTTrom command-> load-defaults\n"
543
"</screen></informalexample> Furthermore, you must configure the network, either with a static address: <informalexample><screen>\n"
544
" NeTTrom command-> setenv netconfig_eth0 flash\n"
545
" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n"
546
"</screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen>\n"
547
" NeTTrom command-> setenv netconfig_eth0 dhcp\n"
548
"</screen></informalexample> You may also need to configure the <userinput>route1</userinput> settings if the TFTP server is not on the local subnet. Following these settings, you have to specify the TFTP server and the location of the image. You can then store your settings to flash. <informalexample><screen>\n"
549
" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n"
550
" NeTTrom command-> setenv kerntftpfile boot.img\n"
551
" NeTTrom command-> save-all\n"
552
"</screen></informalexample> Now you have to tell the firmware that the TFTP image should be booted: <informalexample><screen>\n"
553
" NeTTrom command-> setenv kernconfig tftp\n"
554
" NeTTrom command-> setenv rootdev /dev/ram\n"
555
"</screen></informalexample> If you use a serial console to install your Netwinder, you need to add the following setting: <informalexample><screen>\n"
556
" NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n"
557
"</screen></informalexample> Alternatively, for installations using a keyboard and monitor you have to set: <informalexample><screen>\n"
558
" NeTTrom command-> setenv cmdappend root=/dev/ram\n"
559
"</screen></informalexample> You can use the <command>printenv</command> command to review your environment settings. After you have verified that the settings are correct, you can load the image: <informalexample><screen>\n"
560
" NeTTrom command-> boot\n"
561
"</screen></informalexample> In case you run into any problems, a <ulink url=\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</ulink> is available."
565
#: boot-installer.xml:556
567
msgid "Booting from TFTP on CATS"
571
#: boot-installer.xml:557
573
msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt."
577
#: boot-installer.xml:567
66
#: boot-installer.xml:64
579
68
msgid "Booting from CD-ROM"
583
#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1214 boot-installer.xml:2037 boot-installer.xml:2383 boot-installer.xml:2744
72
#: boot-installer.xml:70 boot-installer.xml:336 boot-installer.xml:804 boot-installer.xml:1462 boot-installer.xml:1824
585
74
msgid "The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
589
#: boot-installer.xml:584 boot-installer.xml:754 boot-installer.xml:1225 boot-installer.xml:2048 boot-installer.xml:2394 boot-installer.xml:2755
78
#: boot-installer.xml:81 boot-installer.xml:347 boot-installer.xml:815 boot-installer.xml:1473 boot-installer.xml:1835
591
80
msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
595
#: boot-installer.xml:592 boot-installer.xml:762 boot-installer.xml:1233 boot-installer.xml:2056 boot-installer.xml:2402 boot-installer.xml:2763
84
#: boot-installer.xml:89 boot-installer.xml:355 boot-installer.xml:823 boot-installer.xml:1481 boot-installer.xml:1843
597
86
msgid "Even if you cannot boot from CD-ROM, you can probably install the Debian system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive."
601
#: boot-installer.xml:600 boot-installer.xml:770 boot-installer.xml:1241 boot-installer.xml:2064 boot-installer.xml:2410 boot-installer.xml:2771
90
#: boot-installer.xml:97 boot-installer.xml:363 boot-installer.xml:831 boot-installer.xml:1489 boot-installer.xml:1851
603
92
msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
607
#: boot-installer.xml:607
609
msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>"
613
#: boot-installer.xml:616
96
#: boot-installer.xml:107
615
98
msgid "Booting from Firmware"
619
#: boot-installer.xml:622
102
#: boot-installer.xml:113
621
104
msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines."
625
#: boot-installer.xml:628
108
#: boot-installer.xml:119
627
110
msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely."
631
#: boot-installer.xml:639
114
#: boot-installer.xml:130
633
116
msgid "Booting the NSLU2"
637
#: boot-installer.xml:640
120
#: boot-installer.xml:131
639
122
msgid "There are three ways how to put the installer firmware into flash:"
643
#: boot-installer.xml:646
126
#: boot-installer.xml:137
645
128
msgid "Using the NSLU2 web interface"
649
#: boot-installer.xml:647
132
#: boot-installer.xml:138
651
134
msgid "Go to the administration section and choose the menu item <literal>Upgrade</literal>. You can then browse your disk for the installer image you have previously downloaded. Then press the <literal>Start Upgrade</literal> button, confirm, wait for a few minutes and confirm again. The system will then boot straight into the installer."
655
#: boot-installer.xml:658
138
#: boot-installer.xml:149
657
140
msgid "Via the network using Linux/Unix"
661
#: boot-installer.xml:659
144
#: boot-installer.xml:150
664
147
"You can use <command>upslug2</command> from any Linux or Unix machine to upgrade the machine via the network. This software is packaged for Debian. First, you have to put your NSLU2 in upgrade mode: <orderedlist> <listitem><para> Disconnect any disks and/or devices from the USB ports. </para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> <listitem><para> Press and hold the reset button (accessible through the small hole on the back just above the power input). </para></listitem> <listitem><para> Press and release the power button to power on the NSLU2. </para></listitem> <listitem><para> Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button. </para></listitem> <listitem><para> The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. </para></listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image: <informalexample><screen>\n"
670
#: boot-installer.xml:720
153
#: boot-installer.xml:211
672
155
msgid "Via the network using Windows"
676
#: boot-installer.xml:721
159
#: boot-installer.xml:212
678
161
msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware via the network."
682
#: boot-installer.xml:737 boot-installer.xml:1208 boot-installer.xml:2025 boot-installer.xml:2377 boot-installer.xml:2738
165
#: boot-installer.xml:223
167
msgid "Booting the SS4000-E"
171
#: boot-installer.xml:224
173
msgid "Due to limitations in the SS4000-E firmware, it unfortunately is not possible to boot the installer without the use of a serial port at this time. To boot the installer, you will need a serial nullmodem cable; a computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB serial converter will also work. </para> </footnote>; and a ribbon cable with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older desktop machines with builtin 9-pin serial ports. </para> </footnote>."
177
#: boot-installer.xml:245
179
msgid "To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable to connect to the serial port of the SS4000-E, and reboot the machine. You need to use a serial terminal application to communicate with the machine; a good option on a Debian GNU/Linux is to use the <command>cu</command> program, in the package of the same name. Assuming the serial port on your computer is to be found on <filename>/dev/ttyS0</filename>, use the following command line:"
183
#: boot-installer.xml:257
185
msgid "cu -lttyS0 -s115200"
189
#: boot-installer.xml:259
191
msgid "If using Windows, you may want to consider using the program <classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word length, no stop bits, and one parity bit."
195
#: boot-installer.xml:265
197
msgid "When the machine boots, you will see the following line of output:"
201
#: boot-installer.xml:271
204
"No network interfaces found\n"
206
"EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
207
"== Executing boot script in 1.000 seconds - enter ^C to abort"
211
#: boot-installer.xml:273
213
msgid "At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-s4ke-sec\"> <para> Note that you have only one second to do so; if you miss this window, just powercycle the machine and try again. </para> </footnote>. This will give you the RedBoot prompt. Enter the following commands:"
217
#: boot-installer.xml:286
220
"load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
221
"load -v -r -b 0x01008000 -m ymodem zImage\n"
222
"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000"
226
#: boot-installer.xml:288
228
msgid "After every <command>load</command> command, the system will expect a file to be transmitted using the YMODEM protocol. When using cu, make sure you have the package <classname>lrzsz</classname> installed, then hit enter, followed by the <quote>~<</quote> escape sequence to start an external program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</command>."
232
#: boot-installer.xml:297
234
msgid "Alternatively, it is possible to load the kernel and ramdisk using HTTP rather than YMODEM. This is faster, but requires a working HTTP server on the network. To do so, first switch the bootloader to RAM mode:"
238
#: boot-installer.xml:303
246
#: boot-installer.xml:305
248
msgid "This will seemingly restart the machine; but in reality, it loads reboot to RAM and restarts it from there. Not doing this step will cause the system to hang in the necessary ip_address step that comes next."
252
#: boot-installer.xml:311
254
msgid "You will need to hit Ctrl-C again to interrupt the boot. Then:"
258
#: boot-installer.xml:315
261
"ip_address -l 192.168.2.249 -h 192.168.2.4\n"
262
"load -v -r -b 0x01800000 -m http /initrd.gz\n"
263
"load -v -r -b 0x01008000 -m http /zImage\n"
264
"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000"
268
#: boot-installer.xml:317
270
msgid "The installer will now start as usual."
274
#: boot-installer.xml:330 boot-installer.xml:798 boot-installer.xml:1456 boot-installer.xml:1818
684
276
msgid "Booting from a CD-ROM"
688
#: boot-installer.xml:844
280
#: boot-installer.xml:437
690
282
msgid "Booting from Windows"
694
#: boot-installer.xml:845
286
#: boot-installer.xml:438
696
288
msgid "To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>."
700
#: boot-installer.xml:851
292
#: boot-installer.xml:444
702
294
msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>."
706
#: boot-installer.xml:859
298
#: boot-installer.xml:452
708
300
msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to start the &debian; installer."
712
#: boot-installer.xml:899
304
#: boot-installer.xml:492
714
306
msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
718
#: boot-installer.xml:902
310
#: boot-installer.xml:495
720
312
msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>."
724
#: boot-installer.xml:907
316
#: boot-installer.xml:500
726
318
msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
730
#: boot-installer.xml:917
322
#: boot-installer.xml:510
732
msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD image, without needing the network."
324
msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network."
736
#: boot-installer.xml:926
328
#: boot-installer.xml:519
738
330
msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:"
742
#: boot-installer.xml:947
334
#: boot-installer.xml:540
745
337
"image=/boot/newinstall/vmlinuz\n"
751
#: boot-installer.xml:947
343
#: boot-installer.xml:540
753
345
msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot."
757
#: boot-installer.xml:956
349
#: boot-installer.xml:549
351
msgid "The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):"
355
#: boot-installer.xml:557
760
"The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the following lines: <informalexample><screen>\n"
761
358
"title New Install\n"
762
"kernel (hd0,0)/boot/newinstall/vmlinuz\n"
763
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
764
"</screen></informalexample> and reboot."
360
"kernel /boot/newinstall/vmlinuz\n"
361
"initrd /boot/newinstall/initrd.gz"
768
#: boot-installer.xml:967
365
#: boot-installer.xml:559
770
msgid "Note that the value of the <userinput>ramdisk_size</userinput> may need to be adjusted for the size of the initrd image. From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
367
msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
774
#: boot-installer.xml:978
371
#: boot-installer.xml:568
776
373
msgid "Booting from USB Memory Stick"
780
#: boot-installer.xml:979
377
#: boot-installer.xml:569
782
379
msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
786
#: boot-installer.xml:992 boot-installer.xml:2137 boot-installer.xml:2646
383
#: boot-installer.xml:582 boot-installer.xml:1725
788
385
msgid "Booting from Floppies"
792
#: boot-installer.xml:993 boot-installer.xml:2654
389
#: boot-installer.xml:583 boot-installer.xml:1733
794
391
msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
798
#: boot-installer.xml:1000
395
#: boot-installer.xml:590
800
397
msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on."
804
#: boot-installer.xml:1006
401
#: boot-installer.xml:596
806
403
msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt."
810
#: boot-installer.xml:1016
407
#: boot-installer.xml:606
812
409
msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting."
816
#: boot-installer.xml:1025
413
#: boot-installer.xml:615
818
415
msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
822
#: boot-installer.xml:1031
419
#: boot-installer.xml:621
824
421
msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>."
828
#: boot-installer.xml:1040
425
#: boot-installer.xml:630
830
427
msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched."
431
#: boot-installer.xml:640 boot-installer.xml:1167 boot-installer.xml:1308 boot-installer.xml:1362 boot-installer.xml:1670 boot-installer.xml:1779
433
msgid "Booting with TFTP"
834
#: boot-installer.xml:1074
437
#: boot-installer.xml:664
836
439
msgid "There are various ways to do a TFTP boot on i386."
840
#: boot-installer.xml:1080
443
#: boot-installer.xml:670
842
445
msgid "NIC or Motherboard that support PXE"
846
#: boot-installer.xml:1081
449
#: boot-installer.xml:671
848
451
msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network."
852
#: boot-installer.xml:1092
455
#: boot-installer.xml:682
854
457
msgid "NIC with Network BootROM"
858
#: boot-installer.xml:1093
461
#: boot-installer.xml:683
860
463
msgid "It could be that your Network Interface Card provides TFTP boot functionality."
864
#: boot-installer.xml:1098
467
#: boot-installer.xml:688
866
469
msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
870
#: boot-installer.xml:1106
473
#: boot-installer.xml:696
872
475
msgid "Etherboot"
876
#: boot-installer.xml:1107
479
#: boot-installer.xml:697
878
481
msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
882
#: boot-installer.xml:1117
485
#: boot-installer.xml:707
884
487
msgid "The Boot Screen"
888
#: boot-installer.xml:1118
491
#: boot-installer.xml:708
891
494
"When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and a menu: <informalexample><screen>\n"
931
#: boot-installer.xml:1169
534
#: boot-installer.xml:759
933
536
msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use."
937
#: boot-installer.xml:1179
540
#: boot-installer.xml:769
939
542
msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
943
#: boot-installer.xml:1189
546
#: boot-installer.xml:779
945
msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>fb=false</userinput> to the boot prompt, as described in the help text."
548
msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text."
949
#: boot-installer.xml:1249
552
#: boot-installer.xml:839
951
554
msgid "CD Contents"
955
#: boot-installer.xml:1251
558
#: boot-installer.xml:841
957
560
msgid "There are three basic variations of Debian Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a Debian mirror site in order to install the extra packages one would want for a complete system . The set of Debian CDs can install a complete system from the wide range of packages without needing access to the network."
961
#: boot-installer.xml:1267
564
#: boot-installer.xml:857
963
566
msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems."
967
#: boot-installer.xml:1283
570
#: boot-installer.xml:873
969
572
msgid "The Debian Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below."
973
#: boot-installer.xml:1292
576
#: boot-installer.xml:882
975
578
msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed."
979
#: boot-installer.xml:1304
582
#: boot-installer.xml:894
981
584
msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option."
985
#: boot-installer.xml:1323
588
#: boot-installer.xml:913
987
590
msgid "IMPORTANT"
991
#: boot-installer.xml:1324
594
#: boot-installer.xml:914
993
596
msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt."
997
#: boot-installer.xml:1336
600
#: boot-installer.xml:926
999
602
msgid "Option 1: Booting from the Boot Option Maintenance Menu"
1003
#: boot-installer.xml:1343
606
#: boot-installer.xml:933
1005
608
msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization."
1009
#: boot-installer.xml:1349
612
#: boot-installer.xml:939
1011
614
msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu."
1015
#: boot-installer.xml:1355
618
#: boot-installer.xml:945
1017
620
msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same."
1021
#: boot-installer.xml:1366
624
#: boot-installer.xml:956
1023
626
msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step."
1027
#: boot-installer.xml:1377
630
#: boot-installer.xml:967
1029
632
msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence."
1033
#: boot-installer.xml:1389
636
#: boot-installer.xml:979
1035
638
msgid "These steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options."
1039
#: boot-installer.xml:1399
642
#: boot-installer.xml:989
1041
644
msgid "Option 2: Booting from the EFI Shell"
1045
#: boot-installer.xml:1400
648
#: boot-installer.xml:990
1047
650
msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with the following steps:"
1051
#: boot-installer.xml:1411
654
#: boot-installer.xml:1001
1053
656
msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization."
1057
#: boot-installer.xml:1417
660
#: boot-installer.xml:1007
1059
662
msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive."
1063
#: boot-installer.xml:1431
666
#: boot-installer.xml:1021
1065
668
msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>."
1069
#: boot-installer.xml:1438
672
#: boot-installer.xml:1028
1071
674
msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt."
1075
#: boot-installer.xml:1445
678
#: boot-installer.xml:1035
1077
680
msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
1081
#: boot-installer.xml:1452
684
#: boot-installer.xml:1042
1083
686
msgid "As with option 1, these steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options."
1087
#: boot-installer.xml:1466
690
#: boot-installer.xml:1056
1089
692
msgid "Installing using a Serial Console"
1093
#: boot-installer.xml:1468
696
#: boot-installer.xml:1058
1095
698
msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured."
1099
#: boot-installer.xml:1479
702
#: boot-installer.xml:1069
1101
704
msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell."
1105
#: boot-installer.xml:1486
708
#: boot-installer.xml:1076
1107
710
msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window."
1111
#: boot-installer.xml:1497
714
#: boot-installer.xml:1087
1113
716
msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode."
1117
#: boot-installer.xml:1506
720
#: boot-installer.xml:1096
1119
722
msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation."
1123
#: boot-installer.xml:1515
726
#: boot-installer.xml:1105
1125
728
msgid "Selecting the Boot Kernel and Options"
1129
#: boot-installer.xml:1517
732
#: boot-installer.xml:1107
1131
734
msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options."
1135
#: boot-installer.xml:1529
738
#: boot-installer.xml:1119
1137
740
msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:"
1141
#: boot-installer.xml:1547
744
#: boot-installer.xml:1137
1143
746
msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
1147
#: boot-installer.xml:1552
750
#: boot-installer.xml:1142
1149
752
msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified."
1153
#: boot-installer.xml:1559
756
#: boot-installer.xml:1149
1155
758
msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the Debian Installer."
1159
#: boot-installer.xml:1568 boot-installer.xml:1704
762
#: boot-installer.xml:1158 boot-installer.xml:1294
1161
764
msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
1165
#: boot-installer.xml:1579
768
#: boot-installer.xml:1169
1167
770
msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
1171
#: boot-installer.xml:1613
774
#: boot-installer.xml:1203
1173
776
msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network."
1177
#: boot-installer.xml:1624
780
#: boot-installer.xml:1214
1179
782
msgid "Configuring the Server"
1183
#: boot-installer.xml:1625
786
#: boot-installer.xml:1215
1186
789
"A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
1214
#: boot-installer.xml:1645
817
#: boot-installer.xml:1235
1216
819
msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details."
1220
#: boot-installer.xml:1662
823
#: boot-installer.xml:1252
1222
825
msgid "Configuring the Client"
1226
#: boot-installer.xml:1663
829
#: boot-installer.xml:1253
1228
831
msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server."
1232
#: boot-installer.xml:1695
835
#: boot-installer.xml:1285
1234
837
msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the Debian Installer."
1238
#: boot-installer.xml:1717
1240
msgid "Choosing an Installation Method"
1244
#: boot-installer.xml:1719
1246
msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs."
1250
#: boot-installer.xml:1727
1252
msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter."
1256
#: boot-installer.xml:1732
1258
msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters."
1262
#: boot-installer.xml:1737
1264
msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>."
1268
#: boot-installer.xml:1754
1274
#: boot-installer.xml:1755
1276
msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
1280
#: boot-installer.xml:1761
1282
msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>."
1286
#: boot-installer.xml:1770
1292
#: boot-installer.xml:1771
1294
msgid "The installer for atari may be started from either the hard drive (see <xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
1298
#: boot-installer.xml:1778
1300
msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>."
1304
#: boot-installer.xml:1787
1310
#: boot-installer.xml:1788
1312
msgid "The installer for BVME6000 may be started from a cdrom (see <xref linkend=\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)."
1316
#: boot-installer.xml:1798
1322
#: boot-installer.xml:1799
1324
msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel."
1328
#: boot-installer.xml:1806
1330
msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but which will disable SCSI disconnects. Note that specifying this parameter is only necessary if you have more than one hard disk; otherwise, the system will run faster if you do not specify it."
1334
#: boot-installer.xml:1821
1336
msgid "MVME147 and MVME16x"
1340
#: boot-installer.xml:1822
1342
msgid "The installer for MVME147 and MVME16x may be started from either floppies (see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
1346
#: boot-installer.xml:1832
1352
#: boot-installer.xml:1833
1354
msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
1358
#: boot-installer.xml:1844
1360
msgid "Booting from a Hard Disk"
1364
#: boot-installer.xml:1850 boot-installer.xml:2456
1366
msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
1370
#: boot-installer.xml:1856 boot-installer.xml:2462
1372
msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in <xref linkend=\"boot-drive-files\"/>."
1376
#: boot-installer.xml:1865
1378
msgid "At least six different ramdisks may be used to boot from the hard drive, three different types each with and without support for a 2.2.x linux kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> for details)."
1382
#: boot-installer.xml:1873
1384
msgid "The three different types of ramdisks are <filename>cdrom</filename>, <filename>hd-media</filename>, and <filename>nativehd</filename>. These ramdisks differ only in their source for installation packages. The <filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer packages. The <filename>hd-media</filename> ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the <filename>nativehd</filename> ramdisk uses the net to install packages."
1388
#: boot-installer.xml:1894
1390
msgid "Booting from AmigaOS"
1394
#: boot-installer.xml:1895
1396
msgid "In the <command>Workbench</command>, start the Linux installation process by double-clicking on the <guiicon>StartInstall</guiicon> icon in the <filename>debian</filename> directory."
1400
#: boot-installer.xml:1901
1402
msgid "You may have to press the &enterkey; key twice after the Amiga installer program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue down at <xref linkend=\"d-i-intro\"/>."
1406
#: boot-installer.xml:1916
1408
msgid "Booting from Atari TOS"
1412
#: boot-installer.xml:1917
1414
msgid "At the GEM desktop, start the Linux installation process by double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</filename> directory and clicking <guibutton>Ok</guibutton> at the program options dialog box."
1418
#: boot-installer.xml:1924
1420
msgid "You may have to press the &enterkey; key after the Atari bootstrap program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>."
1424
#: boot-installer.xml:1939
1426
msgid "Booting from MacOS"
1430
#: boot-installer.xml:1940
1432
msgid "You must retain the original Mac system and boot from it. It is <emphasis>essential</emphasis> that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the <keycap>shift</keycap> key down to prevent extensions from loading. If you don't use MacOS except for loading linux, you can accomplish the same thing by removing all extensions and control panels from the Mac's System Folder. Otherwise extensions may be left running and cause random problems with the running linux kernel."
1436
#: boot-installer.xml:1951
1438
msgid "Macs require the <command>Penguin</command> bootloader, which can be downloaded from <ulink url=\"&url-m68k-mac;\">the Linux/mac68k sourceforge.net project</ulink>. If you do not have the tools to handle a <command>Stuffit</command> archive, you can put it on a MacOS-formatted floppy using a second GNU/Linux machine of any architecture and the <command>hmount</command>, <command>hcopy</command>, and <command>humount</command> tools from the <classname>hfsutils</classname> suite."
1442
#: boot-installer.xml:1962
1444
msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in the <filename>Penguin</filename> directory. The <command>Penguin</command> booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</filename> directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files."
1448
#: boot-installer.xml:1977
1450
msgid "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> <guimenuitem>Settings...</guimenuitem>, then switch to the <guilabel>Options</guilabel> tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</guimenuitem>."
1454
#: boot-installer.xml:1986
1456
msgid "Close the <guilabel>Settings</guilabel> dialog, save the settings and start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the <guimenu>File</guimenu> menu."
1460
#: boot-installer.xml:1993
1462
msgid "The <command>Penguin</command> booter will output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>."
1466
#: boot-installer.xml:2008
1468
msgid "Booting from Q40/Q60"
1472
#: boot-installer.xml:2010
1478
#: boot-installer.xml:2014
1480
msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>."
1484
#: boot-installer.xml:2026
1486
msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000."
1490
#: boot-installer.xml:2098
1492
msgid "After booting the VMEbus systems you will be presented with the LILO <prompt>Boot:</prompt> prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:"
1496
#: boot-installer.xml:2109
1498
msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
1502
#: boot-installer.xml:2114
1504
msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
1508
#: boot-installer.xml:2119
1510
msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
1514
#: boot-installer.xml:2126
1516
msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>."
1520
#: boot-installer.xml:2138
1522
msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method."
1526
#: boot-installer.xml:2143
1528
msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time."
1532
#: boot-installer.xml:2159 boot-installer.xml:2206
841
#: boot-installer.xml:1311 boot-installer.xml:1335
1534
843
msgid "SGI TFTP Booting"
1538
#: boot-installer.xml:2160
847
#: boot-installer.xml:1312
1541
850
"After entering the command monitor use <informalexample><screen>\n"
1587
#: boot-installer.xml:2222
879
#: boot-installer.xml:1351
1589
881
msgid "bootp(): append=\"root=/dev/sda1\""
1593
#: boot-installer.xml:2229 boot-installer.xml:2323
1595
msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP server and add your parameters to the <replaceable>extra_args</replaceable> variable."
1599
#: boot-installer.xml:2248 boot-installer.xml:2310
885
#: boot-installer.xml:1365 boot-installer.xml:1402
1601
887
msgid "Cobalt TFTP Booting"
1605
#: boot-installer.xml:2249
891
#: boot-installer.xml:1366
1607
893
msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:"
1611
#: boot-installer.xml:2259
897
#: boot-installer.xml:1376
1613
899
msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation."
1617
#: boot-installer.xml:2268
903
#: boot-installer.xml:1385
1619
msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port."
905
msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way."
1623
#: boot-installer.xml:2311
909
#: boot-installer.xml:1403
1625
911
msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable."
1629
#: boot-installer.xml:2339
915
#: boot-installer.xml:1418
1631
917
msgid "s390 Limitations"
1635
#: boot-installer.xml:2340
921
#: boot-installer.xml:1419
1637
923
msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
1641
#: boot-installer.xml:2345
927
#: boot-installer.xml:1424
1643
929
msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system."
1647
#: boot-installer.xml:2356
933
#: boot-installer.xml:1435
1649
935
msgid "s390 Boot Parameters"
1653
#: boot-installer.xml:2357
939
#: boot-installer.xml:1436
1655
941
msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images."
1659
#: boot-installer.xml:2417
945
#: boot-installer.xml:1496
1661
947
msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM."
1665
#: boot-installer.xml:2426
951
#: boot-installer.xml:1505
1667
953
msgid "OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files."
1671
#: boot-installer.xml:2435
957
#: boot-installer.xml:1514
1673
959
msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as"
1677
#: boot-installer.xml:2444
963
#: boot-installer.xml:1523
1679
965
msgid "0 > boot cd:,\\install\\yaboot"
1683
#: boot-installer.xml:2450
969
#: boot-installer.xml:1529
1685
971
msgid "Booting from Hard Disk"
975
#: boot-installer.xml:1535
977
msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
981
#: boot-installer.xml:1541
983
msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
1689
#: boot-installer.xml:2482
987
#: boot-installer.xml:1561
1691
989
msgid "Booting OldWorld PowerMacs from MacOS"
1695
#: boot-installer.xml:2483
993
#: boot-installer.xml:1562
1697
995
msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
1701
#: boot-installer.xml:2501
999
#: boot-installer.xml:1580
1703
1001
msgid "Booting NewWorld Macs from OpenFirmware"
1707
#: boot-installer.xml:2502
1005
#: boot-installer.xml:1581
1710
1008
"You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
1782
#: boot-installer.xml:2647
1080
#: boot-installer.xml:1726
1784
1082
msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
1788
#: boot-installer.xml:2659
1086
#: boot-installer.xml:1738
1790
1088
msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
1794
#: boot-installer.xml:2665
1092
#: boot-installer.xml:1744
1796
1094
msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
1800
#: boot-installer.xml:2672
1098
#: boot-installer.xml:1751
1802
1100
msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
1806
#: boot-installer.xml:2683
1104
#: boot-installer.xml:1762
1808
1106
msgid "PowerPC Boot Parameters"
1812
#: boot-installer.xml:2684
1110
#: boot-installer.xml:1763
1814
1112
msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
1818
#: boot-installer.xml:2724
1116
#: boot-installer.xml:1803
1820
msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server."
1118
msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
1824
#: boot-installer.xml:2778
1122
#: boot-installer.xml:1858
1826
1124
msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
1830
#: boot-installer.xml:2787
1128
#: boot-installer.xml:1867
1832
1130
msgid "IDPROM Messages"
1836
#: boot-installer.xml:2788
1134
#: boot-installer.xml:1868
1838
1136
msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
1842
#: boot-installer.xml:2807
1140
#: boot-installer.xml:1887
1142
msgid "Accessibility"
1146
#: boot-installer.xml:1888
1148
msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically, but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
1152
#: boot-installer.xml:1905
1154
msgid "USB Braille Displays"
1158
#: boot-installer.xml:1906
1160
msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
1164
#: boot-installer.xml:1921
1166
msgid "Serial Braille Displays"
1170
#: boot-installer.xml:1922
1172
msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-driver-codes;\">driver code list</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-table-codes;\">table code list</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
1176
#: boot-installer.xml:1944
1178
msgid "Hardware Speech Synthesis"
1182
#: boot-installer.xml:1945
1184
msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select the <quote>Graphical install</quote> entry in the boot menu."
1188
#: boot-installer.xml:1951
1190
msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
1194
#: boot-installer.xml:1966
1196
msgid "Board Devices"
1200
#: boot-installer.xml:1967
1202
msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
1206
#: boot-installer.xml:1975
1208
msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
1212
#: boot-installer.xml:1983
1214
msgid "High-Contrast Theme"
1218
#: boot-installer.xml:1984
1220
msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
1224
#: boot-installer.xml:1999
1844
1226
msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
1848
#: boot-installer.xml:2814
1230
#: boot-installer.xml:2006
1850
1232
msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
1854
#: boot-installer.xml:2821
1236
#: boot-installer.xml:2013
1856
1238
msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
1860
#: boot-installer.xml:2830
1242
#: boot-installer.xml:2022
1863
1245
"When the kernel boots, a message <informalexample><screen>\n"
1869
#: boot-installer.xml:2846
1251
#: boot-installer.xml:2038
1871
msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
1253
msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename><footnote> <para> In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. </para> </footnote>."
1875
#: boot-installer.xml:2858
1257
#: boot-installer.xml:2062
1877
1259
msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
1881
#: boot-installer.xml:2869
1263
#: boot-installer.xml:2073
1883
1265
msgid "Debian Installer Parameters"
1887
#: boot-installer.xml:2870
1269
#: boot-installer.xml:2074
1889
1271
msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
1893
#: boot-installer.xml:2883
1275
#: boot-installer.xml:2087
1895
1277
msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
1899
#: boot-installer.xml:2895
1281
#: boot-installer.xml:2099
1901
1283
msgid "debconf/priority (priority)"
1905
#: boot-installer.xml:2896
1287
#: boot-installer.xml:2100
1907
1289
msgid "This parameter sets the lowest priority of messages to be displayed."
1911
#: boot-installer.xml:2900
1293
#: boot-installer.xml:2104
1913
1295
msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
1917
#: boot-installer.xml:2907
1299
#: boot-installer.xml:2111
1919
1301
msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
1923
#: boot-installer.xml:2921
1305
#: boot-installer.xml:2125
1925
1307
msgid "DEBIAN_FRONTEND"
1929
#: boot-installer.xml:2922
1311
#: boot-installer.xml:2126
1931
1313
msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
1935
#: boot-installer.xml:2951
1317
#: boot-installer.xml:2155
1937
1319
msgid "BOOT_DEBUG"
1941
#: boot-installer.xml:2952
1323
#: boot-installer.xml:2156
1943
1325
msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
1946
1328
#. Tag: userinput
1947
#: boot-installer.xml:2961
1329
#: boot-installer.xml:2165
1949
1331
msgid "BOOT_DEBUG=0"
1953
#: boot-installer.xml:2962
1335
#: boot-installer.xml:2166
1955
1337
msgid "This is the default."
1958
1340
#. Tag: userinput
1959
#: boot-installer.xml:2966
1341
#: boot-installer.xml:2170
1961
1343
msgid "BOOT_DEBUG=1"
1965
#: boot-installer.xml:2967
1347
#: boot-installer.xml:2171
1967
1349
msgid "More verbose than usual."
1970
1352
#. Tag: userinput
1971
#: boot-installer.xml:2971
1353
#: boot-installer.xml:2175
1973
1355
msgid "BOOT_DEBUG=2"
1977
#: boot-installer.xml:2972
1359
#: boot-installer.xml:2176
1979
1361
msgid "Lots of debugging information."
1982
1364
#. Tag: userinput
1983
#: boot-installer.xml:2976
1365
#: boot-installer.xml:2180
1985
1367
msgid "BOOT_DEBUG=3"
1989
#: boot-installer.xml:2977
1371
#: boot-installer.xml:2181
1991
1373
msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
1995
#: boot-installer.xml:2991
1377
#: boot-installer.xml:2195
1997
1379
msgid "INSTALL_MEDIA_DEV"
2001
#: boot-installer.xml:2992
1383
#: boot-installer.xml:2196
2003
1385
msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
2007
#: boot-installer.xml:2998
1389
#: boot-installer.xml:2202
2009
1391
msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
2013
#: boot-installer.xml:3008
1395
#: boot-installer.xml:2212
2019
#: boot-installer.xml:3009
1401
#: boot-installer.xml:2213
2021
1403
msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
2025
#: boot-installer.xml:3019
1407
#: boot-installer.xml:2223
1413
#: boot-installer.xml:2224
1415
msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
1419
#: boot-installer.xml:2233
2027
1421
msgid "debian-installer/framebuffer (fb)"
2031
#: boot-installer.xml:3020
2033
msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
2037
#: boot-installer.xml:3029
2039
msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card."
2043
#: boot-installer.xml:3035
2045
msgid "Such problems have been reported on the Amiga 1200 and SE/30."
2049
#: boot-installer.xml:3039
1425
#: boot-installer.xml:2234
1427
msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
1431
#: boot-installer.xml:2243
2051
1433
msgid "Such problems have been reported on hppa."
2055
#: boot-installer.xml:3043
1437
#: boot-installer.xml:2247
2057
1439
msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
2061
#: boot-installer.xml:3057
1443
#: boot-installer.xml:2261
2063
1445
msgid "debian-installer/theme (theme)"
2067
#: boot-installer.xml:3058
1449
#: boot-installer.xml:2262
2069
1451
msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
2073
#: boot-installer.xml:3070 boot-installer.xml:3320
1455
#: boot-installer.xml:2274 boot-installer.xml:2505
2075
1457
msgid "netcfg/disable_dhcp"
2079
#: boot-installer.xml:3071
1461
#: boot-installer.xml:2275
2081
1463
msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
2085
#: boot-installer.xml:3078
1467
#: boot-installer.xml:2282
2087
1469
msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
2091
#: boot-installer.xml:3089
1473
#: boot-installer.xml:2293
2093
1475
msgid "hw-detect/start_pcmcia"
2097
#: boot-installer.xml:3090
1479
#: boot-installer.xml:2294
2099
1481
msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
2103
#: boot-installer.xml:3100
1485
#: boot-installer.xml:2304
2105
1487
msgid "disk-detect/dmraid/enable (dmraid)"
2109
#: boot-installer.xml:3101
1491
#: boot-installer.xml:2305
2111
1493
msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">Debian Installer Wiki</ulink>."
2115
#: boot-installer.xml:3112
1497
#: boot-installer.xml:2316
2117
1499
msgid "preseed/url (url)"
2121
#: boot-installer.xml:3113
1503
#: boot-installer.xml:2317
2123
1505
msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
2127
#: boot-installer.xml:3122
1509
#: boot-installer.xml:2326
2129
1511
msgid "preseed/file (file)"
2133
#: boot-installer.xml:3123
1515
#: boot-installer.xml:2327
2135
1517
msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
2139
#: boot-installer.xml:3132
1521
#: boot-installer.xml:2336
2141
1523
msgid "preseed/interactive"
2145
#: boot-installer.xml:3133
1527
#: boot-installer.xml:2337
2147
1529
msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
2151
#: boot-installer.xml:3145
1533
#: boot-installer.xml:2349
2153
1535
msgid "auto-install/enable (auto)"
2157
#: boot-installer.xml:3146
1539
#: boot-installer.xml:2350
2159
1541
msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
2163
#: boot-installer.xml:3157
1545
#: boot-installer.xml:2361
2165
1547
msgid "finish-install/keep-consoles"
2169
#: boot-installer.xml:3158
1551
#: boot-installer.xml:2362
2171
1553
msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
2175
#: boot-installer.xml:3169
1557
#: boot-installer.xml:2373
2177
1559
msgid "cdrom-detect/eject"
2181
#: boot-installer.xml:3170
1563
#: boot-installer.xml:2374
2183
1565
msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
2187
#: boot-installer.xml:3179
1569
#: boot-installer.xml:2383
2189
1571
msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
2193
#: boot-installer.xml:3190
1575
#: boot-installer.xml:2394
1577
msgid "base-installer/install-recommends (recommends)"
1581
#: boot-installer.xml:2395
1583
msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
1587
#: boot-installer.xml:2402
1589
msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
1593
#: boot-installer.xml:2414
2195
1595
msgid "debian-installer/allow_unauthenticated"
2199
#: boot-installer.xml:3191
1599
#: boot-installer.xml:2415
2201
1601
msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
2205
#: boot-installer.xml:3202
1605
#: boot-installer.xml:2426
2207
1607
msgid "ramdisk_size"
2211
#: boot-installer.xml:3203
1611
#: boot-installer.xml:2427
2213
1613
msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
2217
#: boot-installer.xml:3213
2219
msgid "mouse/protocol"
2223
#: boot-installer.xml:3214
2225
msgid "For the gtk frontend (graphical installer), users can set the mouse protocol to be used by setting this parameter. Supported values are<footnote> <para> See the man page for <citerefentry><refentrytitle>directfbrc</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for additional information. </para> </footnote>: <userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, <userinput>MS</userinput>, <userinput>MS3</userinput>, <userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>. In most cases the default protocol should work correctly."
2229
#: boot-installer.xml:3236
2231
msgid "mouse/device"
2235
#: boot-installer.xml:3237
2237
msgid "For the gtk frontend (graphical installer), users can specify the mouse device to be used by setting this parameter. This is mostly useful if the mouse is connected to a serial port (serial mouse). Example: <userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>."
2241
#: boot-installer.xml:3248
2247
#: boot-installer.xml:3249
2249
msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>."
2253
#: boot-installer.xml:3258
2255
msgid "directfb/hw-accel"
2259
#: boot-installer.xml:3259
2261
msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. Set this parameter to <userinput>true</userinput> to enable it."
2265
#: boot-installer.xml:3269
1617
#: boot-installer.xml:2437
2267
1619
msgid "rescue/enable"
2271
#: boot-installer.xml:3270
1623
#: boot-installer.xml:2438
2273
1625
msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
2277
#: boot-installer.xml:3281
1629
#: boot-installer.xml:2449
2279
1631
msgid "Using boot parameters to answer questions"
2283
#: boot-installer.xml:3282
1635
#: boot-installer.xml:2450
2285
1637
msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
2289
#: boot-installer.xml:3294
1641
#: boot-installer.xml:2462
1643
msgid "debian-installer/language (language)"
1647
#: boot-installer.xml:2463
1649
msgid "debian-installer/country (country)"
1653
#: boot-installer.xml:2464
2291
1655
msgid "debian-installer/locale (locale)"
2295
#: boot-installer.xml:3295
2297
msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country."
1659
#: boot-installer.xml:2465
1661
msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
1665
#: boot-installer.xml:2470
1667
msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
1671
#: boot-installer.xml:2479
1673
msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
2301
#: boot-installer.xml:3306
1677
#: boot-installer.xml:2491
2303
1679
msgid "anna/choose_modules (modules)"
2307
#: boot-installer.xml:3307
1683
#: boot-installer.xml:2492
2309
1685
msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
2313
#: boot-installer.xml:3321
1689
#: boot-installer.xml:2506
2315
1691
msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
2319
#: boot-installer.xml:3330
1695
#: boot-installer.xml:2515
2321
1697
msgid "mirror/protocol (protocol)"
2325
#: boot-installer.xml:3331
1701
#: boot-installer.xml:2516
2327
1703
msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
2331
#: boot-installer.xml:3344
1707
#: boot-installer.xml:2529
2333
1709
msgid "tasksel:tasksel/first (tasks)"
2337
#: boot-installer.xml:3345
1713
#: boot-installer.xml:2530
2339
1715
msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
2343
#: boot-installer.xml:3359
1719
#: boot-installer.xml:2544
2345
1721
msgid "Passing parameters to kernel modules"
2349
#: boot-installer.xml:3360
1725
#: boot-installer.xml:2545
2351
1727
msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
2355
#: boot-installer.xml:3373
1731
#: boot-installer.xml:2558
2357
1733
msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
2361
#: boot-installer.xml:3380
1737
#: boot-installer.xml:2565
2364
1740
"The syntax to use to set parameters for modules is: <informalexample><screen>\n"
2370
#: boot-installer.xml:3390
1746
#: boot-installer.xml:2575
2372
1748
msgid "3c509.xcvr=3 3c509.irq=10"
2376
#: boot-installer.xml:3396
1752
#: boot-installer.xml:2581
2378
1754
msgid "Blacklisting kernel modules"
2382
#: boot-installer.xml:3397
1758
#: boot-installer.xml:2582
2384
1760
msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
2388
#: boot-installer.xml:3406
1764
#: boot-installer.xml:2591
2390
1766
msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
2394
#: boot-installer.xml:3414
1770
#: boot-installer.xml:2599
2396
1772
msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
2400
#: boot-installer.xml:3431
1776
#: boot-installer.xml:2616
2402
1778
msgid "Troubleshooting the Installation Process"
2406
#: boot-installer.xml:3436
1782
#: boot-installer.xml:2621
2408
1784
msgid "CD-ROM Reliability"
2412
#: boot-installer.xml:3437
1788
#: boot-installer.xml:2622
2414
1790
msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation."
2418
#: boot-installer.xml:3444
1794
#: boot-installer.xml:2629
2420
1796
msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
2424
#: boot-installer.xml:3450
1800
#: boot-installer.xml:2635
2426
1802
msgid "There are two very simple things that you should try first."
2430
#: boot-installer.xml:3455
1806
#: boot-installer.xml:2640
2432
1808
msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
2436
#: boot-installer.xml:3461
1812
#: boot-installer.xml:2646
2438
1814
msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way."
2442
#: boot-installer.xml:3471
1818
#: boot-installer.xml:2656
2444
1820
msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
2448
#: boot-installer.xml:3477
1824
#: boot-installer.xml:2662
2450
1826
msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
2454
#: boot-installer.xml:3485
1830
#: boot-installer.xml:2670
2456
1832
msgid "Common issues"
2460
#: boot-installer.xml:3488
1836
#: boot-installer.xml:2673
2462
1838
msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
2466
#: boot-installer.xml:3494
1842
#: boot-installer.xml:2679
2468
1844
msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)."
2472
#: boot-installer.xml:3501
1848
#: boot-installer.xml:2686
2474
1850
msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled."
2478
#: boot-installer.xml:3512
1854
#: boot-installer.xml:2697
2480
1856
msgid "How to investigate and maybe solve issues"
2484
#: boot-installer.xml:3513
1860
#: boot-installer.xml:2698
2486
1862
msgid "If the CD-ROM fails to boot, try the suggestions listed below."
2490
#: boot-installer.xml:3518
1866
#: boot-installer.xml:2703
2492
1868
msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using."
2496
#: boot-installer.xml:3524
1872
#: boot-installer.xml:2709
2499
1875
"If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
2572
#: boot-installer.xml:3608
1948
#: boot-installer.xml:2793
2574
1950
msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
2578
#: boot-installer.xml:3623
1954
#: boot-installer.xml:2808
2580
1956
msgid "Floppy Disk Reliability"
2584
#: boot-installer.xml:3625
1960
#: boot-installer.xml:2810
2586
1962
msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability."
2590
#: boot-installer.xml:3630
1966
#: boot-installer.xml:2815
2592
1968
msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
2596
#: boot-installer.xml:3639
1972
#: boot-installer.xml:2824
2598
1974
msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
2602
#: boot-installer.xml:3648
1978
#: boot-installer.xml:2833
2604
1980
msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
2608
#: boot-installer.xml:3654
1984
#: boot-installer.xml:2839
2610
1986
msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
2614
#: boot-installer.xml:3660
1990
#: boot-installer.xml:2845
2616
1992
msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
2620
#: boot-installer.xml:3669
1996
#: boot-installer.xml:2854
2622
1998
msgid "Boot Configuration"
2626
#: boot-installer.xml:3671
2002
#: boot-installer.xml:2856
2628
2004
msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
2632
#: boot-installer.xml:3678
2008
#: boot-installer.xml:2863
2634
2010
msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
2638
#: boot-installer.xml:3684
2014
#: boot-installer.xml:2869
2640
2016
msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>."
2644
#: boot-installer.xml:3695 boot-installer.xml:3797
2020
#: boot-installer.xml:2880 boot-installer.xml:2982
2646
2022
msgid "Common &arch-title; Installation Problems"
2650
#: boot-installer.xml:3696
2026
#: boot-installer.xml:2881
2652
2028
msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
2656
#: boot-installer.xml:3701
2032
#: boot-installer.xml:2886
2658
2034
msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>."
2662
#: boot-installer.xml:3707
2038
#: boot-installer.xml:2892
2664
2040
msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>."
2668
#: boot-installer.xml:3716
2044
#: boot-installer.xml:2901
2670
2046
msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test."
2674
#: boot-installer.xml:3723
2050
#: boot-installer.xml:2908
2676
2052
msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>."
2680
#: boot-installer.xml:3741
2056
#: boot-installer.xml:2926
2682
2058
msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
2686
#: boot-installer.xml:3755
2062
#: boot-installer.xml:2940
2688
2064
msgid "System Freeze During the PCMCIA Configuration Phase"
2692
#: boot-installer.xml:3756
2068
#: boot-installer.xml:2941
2694
2070
msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
2698
#: boot-installer.xml:3766
2074
#: boot-installer.xml:2951
2700
2076
msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
2704
#: boot-installer.xml:3783
2080
#: boot-installer.xml:2968
2706
2082
msgid "System Freeze while Loading USB Modules"
2710
#: boot-installer.xml:3784
2086
#: boot-installer.xml:2969
2712
2088
msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>nousb</userinput> parameter at the boot prompt."
2716
#: boot-installer.xml:3798
2092
#: boot-installer.xml:2983
2718
2094
msgid "There are some common installation problems that are worth mentioning."
2722
#: boot-installer.xml:3804
2098
#: boot-installer.xml:2989
2724
2100
msgid "Misdirected video output"
2728
#: boot-installer.xml:3805
2104
#: boot-installer.xml:2990
2731
2107
"It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
added
removed
po/pot/boot-installer.pot
