1
# SOME DESCRIPTIVE TITLE.
2
# Copyright (C) YEAR Free Software Foundation, Inc.
3
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
8
"Project-Id-Version: PACKAGE VERSION\n"
9
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
10
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
11
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
12
"Language-Team: LANGUAGE <LL@li.org>\n"
14
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
15
"Content-Transfer-Encoding: ENCODING\n"
17
#: boot-installer.xml:4
20
msgid "Booting the Installation System"
23
#: boot-installer.xml:9
26
msgid "Booting the Installer on &arch-title;"
29
#: boot-installer.xml:20
32
msgid "Alpha Console Firmware"
35
#: boot-installer.xml:21
38
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:"
41
#: boot-installer.xml:31
44
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."
47
#: boot-installer.xml:38
50
msgid "<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT."
53
#: boot-installer.xml:47
56
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."
59
#: boot-installer.xml:54
62
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."
65
#: boot-installer.xml:63
68
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."
71
#: boot-installer.xml:76
74
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."
77
#: boot-installer.xml:87
80
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."
83
#: boot-installer.xml:95
86
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."
89
#: boot-installer.xml:107
95
#: boot-installer.xml:108
98
msgid "Console Type Supported"
101
#: boot-installer.xml:114
107
#: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 boot-installer.xml:184 boot-installer.xml:187
113
#: boot-installer.xml:117
119
#: boot-installer.xml:120
125
#: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181
131
#: boot-installer.xml:123
137
#: boot-installer.xml:126
143
#: boot-installer.xml:129
149
#: boot-installer.xml:132
155
#: boot-installer.xml:135
161
#: boot-installer.xml:138
167
#: boot-installer.xml:141
173
#: boot-installer.xml:144
179
#: boot-installer.xml:147
185
#: boot-installer.xml:150
191
#: boot-installer.xml:153
197
#: boot-installer.xml:156
203
#: boot-installer.xml:157
206
msgid "ARC (see motherboard manual) or SRM"
209
#: boot-installer.xml:159
215
#: boot-installer.xml:162
221
#: boot-installer.xml:165
227
#: boot-installer.xml:168
233
#: boot-installer.xml:171
239
#: boot-installer.xml:174
245
#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193
251
#: boot-installer.xml:177
257
#: boot-installer.xml:180
263
#: boot-installer.xml:183
269
#: boot-installer.xml:186
275
#: boot-installer.xml:189
278
msgid "<entry>xl</entry>"
281
#: boot-installer.xml:192
284
msgid "<entry>xlt</entry>"
287
#: boot-installer.xml:200
290
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>."
293
#: boot-installer.xml:209
296
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."
299
#: boot-installer.xml:215
302
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>."
305
#: boot-installer.xml:221
308
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>."
311
#: boot-installer.xml:231
314
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>."
317
#: boot-installer.xml:238
321
"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"
325
"</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."
328
#: boot-installer.xml:253
331
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;."
334
#: boot-installer.xml:264
337
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>."
340
#: boot-installer.xml:283 boot-installer.xml:892 boot-installer.xml:1384 boot-installer.xml:1889 boot-installer.xml:1971 boot-installer.xml:2311 boot-installer.xml:2407
343
msgid "Booting with TFTP"
346
#: boot-installer.xml:284
350
"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"
351
">>> show dev\n"
352
"ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n"
353
"ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n"
354
"ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n"
355
"</screen></informalexample> You first need to set the boot protocol: <informalexample><screen>\n"
356
">>> set ewa0_protocol bootp\n"
357
"</screen></informalexample> Then check the medium type is correct: <informalexample><screen>\n"
358
">>> set ewa0_mode <replaceable>mode</replaceable>\n"
359
"</screen></informalexample> You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>."
362
#: boot-installer.xml:302
366
"Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>\n"
367
">>> boot ewa0 -flags \"\"\n"
368
"</screen></informalexample> This will boot using the default kernel parameters as included in the netboot image."
371
#: boot-installer.xml:311
374
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:"
377
#: boot-installer.xml:323
380
msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0""
383
#: boot-installer.xml:328
386
msgid "Booting from CD-ROM with the SRM Console"
389
#: boot-installer.xml:329
393
"Type <informalexample><screen>\n"
394
">>> boot xxxx -flags 0\n"
395
"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation."
398
#: boot-installer.xml:341
401
msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console"
404
#: boot-installer.xml:342
407
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."
410
#: boot-installer.xml:358
413
msgid "Booting from Floppies with the SRM Console"
416
#: boot-installer.xml:359
420
"At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>\n"
421
">>> boot dva0 -flags 0\n"
422
"</screen></informalexample> possibly replacing <filename>dva0</filename> with the actual device name. Usually, <filename>dva0</filename> is the floppy; type <informalexample><screen>\n"
423
">>> show dev\n"
424
"</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."
427
#: boot-installer.xml:376
431
"If you want to specify kernel parameters when booting via <command>aboot</command>, use the following command: <informalexample><screen>\n"
432
">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n"
433
"</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>."
436
#: boot-installer.xml:388
439
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\"/>."
442
#: boot-installer.xml:398
445
msgid "Booting from Floppies with the ARC or AlphaBIOS Console"
448
#: boot-installer.xml:400
451
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."
454
#: boot-installer.xml:409
457
msgid "Booting with MILO"
460
#: boot-installer.xml:410
463
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."
466
#: boot-installer.xml:416
470
"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"
471
"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n"
472
"</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."
475
#: boot-installer.xml:435
478
msgid "Booting from TFTP"
481
#: boot-installer.xml:441 boot-installer.xml:898 boot-installer.xml:1402 boot-installer.xml:1895 boot-installer.xml:2317 boot-installer.xml:2413
484
msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
487
#: boot-installer.xml:446 boot-installer.xml:903 boot-installer.xml:1407 boot-installer.xml:1900 boot-installer.xml:2322 boot-installer.xml:2418
490
msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
493
#: boot-installer.xml:451 boot-installer.xml:908 boot-installer.xml:1412 boot-installer.xml:1905 boot-installer.xml:2327 boot-installer.xml:2423
496
msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
499
#: boot-installer.xml:459
502
msgid "Booting from TFTP on NetWinder"
505
#: boot-installer.xml:461
508
msgid "NetWinders have two network interfaces: The 10Mbps NE2000-compatible card is <filename>eth0</filename> and the 100Mbps Tulip card is <filename>eth1</filename>."
511
#: boot-installer.xml:467
514
msgid "You need NeTTrom 2.2.1 or later to boot the installation system. NeTTrom 2.3.3 is recommended: get these files from <ulink url=\"ftp://ftp.netwinder.org/pub/netwinder/firmware/\"></ulink>:"
517
#: boot-installer.xml:476
520
msgid "nettrom-2.3-3.armv4l.rpm"
523
#: boot-installer.xml:481
526
msgid "nettrom-2.3.3.bin"
529
#: boot-installer.xml:486
532
msgid "nettrom-2.3.3.bin.md5sum"
535
#: boot-installer.xml:491
539
"After rebooting and interrupting the boot process during the countdown, you must first configure the network either with a static address: <informalexample><screen>\n"
540
" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n"
541
"</screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen>\n"
542
" NeTTrom command-> boot diskless\n"
543
"</screen></informalexample> You may also need to configure the <userinput>route1</userinput> settings if the TFTP server is not on the local subnet. The rest of the config is pretty standard (the save-all step is optional): <informalexample><screen>\n"
544
" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n"
545
" NeTTrom command-> setenv kerntftpfile boot.img\n"
546
" NeTTrom command-> save-all\n"
547
" NeTTrom command-> setenv netconfig_eth0 flash\n"
548
" NeTTrom command-> setenv kernconfig tftp\n"
549
" NeTTrom command-> setenv rootdev /dev/ram\n"
550
" NeTTrom command-> setenv cmdappend root=/dev/ram\n"
551
"</screen></informalexample> Only the last four of these interfere with normal disk booting, so it is safe to issue <command>save-all</command> right before them, which will store the network settings in case you need to boot from the network again. If you want to use the serial console to install your NetWinder, you also need the following setting: <informalexample><screen>\n"
552
" NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n"
553
"</screen></informalexample> Use the <command>printenv</command> command to review your environment settings. Finally, if your <envar>cmdappend</envar> NeTTrom variable has the <option>noinitrd</option> option, you must remove it so the downloaded kernel can boot with its attached ramdisk."
556
#: boot-installer.xml:527
559
msgid "Booting from TFTP on CATS"
562
#: boot-installer.xml:529
565
msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt."
568
#: boot-installer.xml:540
571
msgid "Booting from CD-ROM"
574
#: boot-installer.xml:546 boot-installer.xml:599 boot-installer.xml:1021 boot-installer.xml:1852 boot-installer.xml:2099 boot-installer.xml:2453
577
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=\"i386\"> 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."
580
#: boot-installer.xml:557 boot-installer.xml:610 boot-installer.xml:1032 boot-installer.xml:1863 boot-installer.xml:2110 boot-installer.xml:2464
583
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."
586
#: boot-installer.xml:565 boot-installer.xml:618 boot-installer.xml:1040 boot-installer.xml:1871 boot-installer.xml:2118 boot-installer.xml:2472
589
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."
592
#: boot-installer.xml:573 boot-installer.xml:626 boot-installer.xml:1048 boot-installer.xml:1879 boot-installer.xml:2126 boot-installer.xml:2480
595
msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
598
#: boot-installer.xml:580
601
msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>"
604
#: boot-installer.xml:593 boot-installer.xml:1015 boot-installer.xml:1840 boot-installer.xml:2093 boot-installer.xml:2447
607
msgid "Booting from a CD-ROM"
610
#: boot-installer.xml:731
613
msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
616
#: boot-installer.xml:734
619
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\"/>."
622
#: boot-installer.xml:739
625
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/i386/initrd.gz</filename> file and its corresponding kernel. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
628
#: boot-installer.xml:747
631
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."
634
#: boot-installer.xml:756
637
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:"
640
#: boot-installer.xml:777
644
"image=/boot/newinstall/vmlinuz\n"
645
" label=newinstall\n"
646
" initrd=/boot/newinstall/initrd.gz\n"
648
" append=\"<phrase condition=\"sarge\">devfs=mount,dall </phrase>ramdisk_size=12000\""
651
#: boot-installer.xml:777
654
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."
657
#: boot-installer.xml:786
661
"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"
662
"title New Install\n"
663
"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n"
664
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
665
"</screen></informalexample> and reboot. <phrase condition=\"sarge\">If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to the <quote>kernel</quote> line. </phrase>"
668
#: boot-installer.xml:799
671
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>."
674
#: boot-installer.xml:810
677
msgid "Booting from USB Memory Stick"
680
#: boot-installer.xml:811
683
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;."
686
#: boot-installer.xml:820
689
msgid "In case your computer doesn't support booting from USB memory devices, you can still use a single floppy to do the initial boot and then switch to USB. Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel on the boot floppy should detect your USB stick automatically. When it asks for the root floppy, simply press &enterkey;. You should see &d-i; starting."
692
#: boot-installer.xml:833 boot-installer.xml:1952 boot-installer.xml:2353 boot-installer.xml:2501
695
msgid "Booting from Floppies"
698
#: boot-installer.xml:834 boot-installer.xml:2361
701
msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
704
#: boot-installer.xml:841
707
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."
710
#: boot-installer.xml:847
713
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>linux root=/dev/hdc</userinput> at the boot prompt. Installation from LS-120 is only supported by 2.4 and later kernels."
716
#: boot-installer.xml:858
719
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."
722
#: boot-installer.xml:867
725
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."
728
#: boot-installer.xml:873
731
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\"/>."
734
#: boot-installer.xml:882
737
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."
740
#: boot-installer.xml:916
743
msgid "There are various ways to do a TFTP boot on i386."
746
#: boot-installer.xml:922
749
msgid "NIC or Motherboard that support PXE"
752
#: boot-installer.xml:923
755
msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implemention of TFTP boot. If so you may be able to configure your BIOS to boot from the network."
758
#: boot-installer.xml:934
761
msgid "NIC with Network BootROM"
764
#: boot-installer.xml:935
767
msgid "It could be that your Network Interface Card provides TFTP boot functionality."
770
#: boot-installer.xml:940
773
msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
776
#: boot-installer.xml:948
782
#: boot-installer.xml:949
785
msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
788
#: boot-installer.xml:958
791
msgid "The Boot Prompt"
794
#: boot-installer.xml:959
798
"When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and the boot prompt: <informalexample><screen>\n"
799
"Press F1 for help, or ENTER to boot:\n"
800
"</screen></informalexample> At the boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot method and, optionally, boot parameters."
803
#: boot-installer.xml:971
806
msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <phrase condition=\"sarge\"><keycap>F7</keycap></phrase><phrase condition=\"etch\"><keycap>F8</keycap></phrase>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux debconf/priority=medium</userinput>)."
809
#: boot-installer.xml:981
812
msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. 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). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>debian-installer/framebuffer=false</userinput> to the boot prompt, as described in the help text."
815
#: boot-installer.xml:1056
821
#: boot-installer.xml:1058
824
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."
827
#: boot-installer.xml:1074
830
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."
833
#: boot-installer.xml:1090
836
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."
839
#: boot-installer.xml:1099
842
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."
845
#: boot-installer.xml:1111
848
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."
851
#: boot-installer.xml:1130
857
#: boot-installer.xml:1131
860
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."
863
#: boot-installer.xml:1143
866
msgid "Option 1: Booting from the Boot Option Maintenance Menu"
869
#: boot-installer.xml:1150
872
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."
875
#: boot-installer.xml:1156
878
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."
881
#: boot-installer.xml:1162
884
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."
887
#: boot-installer.xml:1173
890
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."
893
#: boot-installer.xml:1184
896
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."
899
#: boot-installer.xml:1196
902
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."
905
#: boot-installer.xml:1206
908
msgid "Option 2: Booting from the EFI Shell"
911
#: boot-installer.xml:1207
914
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:"
917
#: boot-installer.xml:1218
920
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."
923
#: boot-installer.xml:1224
926
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."
929
#: boot-installer.xml:1238
932
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>."
935
#: boot-installer.xml:1245
938
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."
941
#: boot-installer.xml:1252
944
msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
947
#: boot-installer.xml:1259
950
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."
953
#: boot-installer.xml:1273
956
msgid "Installing using a Serial Console"
959
#: boot-installer.xml:1275
962
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."
965
#: boot-installer.xml:1286
968
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."
971
#: boot-installer.xml:1293
974
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."
977
#: boot-installer.xml:1304
980
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."
983
#: boot-installer.xml:1313
986
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."
989
#: boot-installer.xml:1322
992
msgid "Selecting the Boot Kernel and Options"
995
#: boot-installer.xml:1324
998
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."
1001
#: boot-installer.xml:1336
1004
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:"
1007
#: boot-installer.xml:1354
1010
msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
1013
#: boot-installer.xml:1359
1016
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."
1019
#: boot-installer.xml:1366
1022
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."
1025
#: boot-installer.xml:1375
1028
msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
1031
#: boot-installer.xml:1386
1034
msgid "Booting an IA64 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 thru 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."
1037
#: boot-installer.xml:1420
1040
msgid "Network booting an ia64 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."
1043
#: boot-installer.xml:1431
1046
msgid "Configuring the Server"
1049
#: boot-installer.xml:1432
1053
"A suitable TFTP entry for network booting an ia64 system looks something like this: <informalexample><screen>\n"
1055
" hardware ethernet 00:30:6e:1e:0e:83;\n"
1056
" fixed-address 10.0.0.21;\n"
1057
" filename \"debian-installer/ia64/elilo.efi\";\n"
1059
"</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client."
1062
#: boot-installer.xml:1442
1065
msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system."
1068
#: boot-installer.xml:1452
1072
"# cd /var/lib/tftp\n"
1073
"# tar xvfz /home/user/netboot.tar.gz\n"
1075
"./debian-installer/\n"
1076
"./debian-installer/ia64/\n"
1080
#: boot-installer.xml:1452
1083
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."
1086
#: boot-installer.xml:1469
1089
msgid "Configuring the Client"
1092
#: boot-installer.xml:1470
1095
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."
1098
#: boot-installer.xml:1502
1101
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."
1104
#: boot-installer.xml:1511
1107
msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions."
1110
#: boot-installer.xml:1524
1113
msgid "Choosing an Installation Method"
1116
#: boot-installer.xml:1526
1119
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."
1122
#: boot-installer.xml:1534
1125
msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter."
1128
#: boot-installer.xml:1541
1131
msgid "Also, if you are using a 2.2.x linux kernel, then you must make sure you are using a ramdisk built to accommodate it, see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>. In general, this means you need to use the initrd22.gz ramdisk from the respective directory."
1134
#: boot-installer.xml:1549
1137
msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters."
1140
#: boot-installer.xml:1554
1143
msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>."
1146
#: boot-installer.xml:1571
1152
#: boot-installer.xml:1572
1155
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>"
1158
#: boot-installer.xml:1578
1161
msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>."
1164
#: boot-installer.xml:1587
1170
#: boot-installer.xml:1588
1173
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>"
1176
#: boot-installer.xml:1595
1179
msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>."
1182
#: boot-installer.xml:1604
1188
#: boot-installer.xml:1605
1191
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\"/>)."
1194
#: boot-installer.xml:1615
1200
#: boot-installer.xml:1616
1203
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."
1206
#: boot-installer.xml:1623
1209
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."
1212
#: boot-installer.xml:1638
1215
msgid "MVME147 and MVME16x"
1218
#: boot-installer.xml:1639
1221
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>"
1224
#: boot-installer.xml:1649
1230
#: boot-installer.xml:1650
1233
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>"
1236
#: boot-installer.xml:1661
1239
msgid "Booting from a Hard Disk"
1242
#: boot-installer.xml:1667 boot-installer.xml:2172
1245
msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
1248
#: boot-installer.xml:1673 boot-installer.xml:2178
1251
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\"/>."
1254
#: boot-installer.xml:1682
1257
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)."
1260
#: boot-installer.xml:1690
1263
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."
1266
#: boot-installer.xml:1711
1269
msgid "Booting from AmigaOS"
1272
#: boot-installer.xml:1712
1275
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."
1278
#: boot-installer.xml:1718
1281
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\"/>."
1284
#: boot-installer.xml:1733
1287
msgid "Booting from Atari TOS"
1290
#: boot-installer.xml:1734
1293
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."
1296
#: boot-installer.xml:1741
1299
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\"/>."
1302
#: boot-installer.xml:1756
1305
msgid "Booting from MacOS"
1308
#: boot-installer.xml:1757
1311
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."
1314
#: boot-installer.xml:1768
1317
msgid "Macs require the <command>Penguin</command> bootloader. If you do not have the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=\"create-floppy\"/> describes how to copy this image to a floppy."
1320
#: boot-installer.xml:1777
1323
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."
1326
#: boot-installer.xml:1792
1329
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>."
1332
#: boot-installer.xml:1801
1335
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."
1338
#: boot-installer.xml:1808
1341
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\"/>."
1344
#: boot-installer.xml:1823
1347
msgid "Booting from Q40/Q60"
1350
#: boot-installer.xml:1825
1356
#: boot-installer.xml:1829
1359
msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>."
1362
#: boot-installer.xml:1841
1365
msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000."
1368
#: boot-installer.xml:1913
1371
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:"
1374
#: boot-installer.xml:1924
1377
msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
1380
#: boot-installer.xml:1929
1383
msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
1386
#: boot-installer.xml:1934
1389
msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
1392
#: boot-installer.xml:1941
1395
msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>."
1398
#: boot-installer.xml:1953
1401
msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method."
1404
#: boot-installer.xml:1958
1407
msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time."
1410
#: boot-installer.xml:1974 boot-installer.xml:2021
1413
msgid "SGI Indys TFTP Booting"
1416
#: boot-installer.xml:1975
1420
"After entering the command monitor use <informalexample><screen>\n"
1422
"</screen></informalexample> on SGI Indys to boot linux and to begin installation of the Debian Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>\n"
1423
"unsetenv netaddr\n"
1424
"</screen></informalexample> in the command monitor to do this."
1427
#: boot-installer.xml:1994 boot-installer.xml:2043
1430
msgid "Broadcom BCM91250A TFTP Booting"
1433
#: boot-installer.xml:1995
1437
"On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: <informalexample><screen>\n"
1438
"ifconfig eth0 -auto\n"
1439
"</screen></informalexample> Once you have obtained an IP address, you can load SiByl with the following command: <informalexample><screen>\n"
1440
"boot 192.168.1.1:/boot/sibyl\n"
1441
"</screen></informalexample> You need to substitute the IP address listed in this example with either the name or the IP address of your TFTP server. Once you issue this command, the installer will be loaded automatically."
1444
#: boot-installer.xml:2018 boot-installer.xml:2552
1447
msgid "Boot Parameters"
1450
#: boot-installer.xml:2022
1453
msgid "On SGI Indys you can append boot parameters to the <command>bootp():</command> command in the command monitor."
1456
#: boot-installer.xml:2027
1460
"Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n"
1461
"bootp():/boot/tftpboot.img\n"
1462
"</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:"
1465
#: boot-installer.xml:2037
1468
msgid "bootp(): append=\"root=/dev/sda1\""
1471
#: boot-installer.xml:2044
1474
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."
1477
#: boot-installer.xml:2061
1480
msgid "s390 Limitations"
1483
#: boot-installer.xml:2062
1486
msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
1489
#: boot-installer.xml:2067
1492
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 a ssh session which will launch the standard installation system."
1495
#: boot-installer.xml:2078
1498
msgid "s390 Boot Parameters"
1501
#: boot-installer.xml:2079
1504
msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-devices;\">Device Drivers and Installation Commands</ulink> for more information about S/390-specific boot parameters."
1507
#: boot-installer.xml:2133
1510
msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP 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."
1513
#: boot-installer.xml:2142
1516
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."
1519
#: boot-installer.xml:2151
1522
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"
1525
#: boot-installer.xml:2160
1528
msgid "0 > boot cd:,\\install\\yaboot"
1531
#: boot-installer.xml:2166
1534
msgid "Booting from Hard Disk"
1537
#: boot-installer.xml:2187
1540
msgid "Booting CHRP from OpenFirmware"
1543
#: boot-installer.xml:2191
1546
msgid "Not yet written."
1549
#: boot-installer.xml:2196
1552
msgid "Booting OldWorld PowerMacs from MacOS"
1555
#: boot-installer.xml:2197
1558
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."
1561
#: boot-installer.xml:2215
1564
msgid "Booting NewWorld Macs from OpenFirmware"
1567
#: boot-installer.xml:2216
1571
"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\"/>. Restart the computer, and immediately (during the chime) hold down the <keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and <keycap>f</keycap> keys all together. After a few seconds you will be presented with the Open Firmware prompt. At the prompt, type <informalexample><screen>\n"
1572
"0 > boot hd:<replaceable>x</replaceable>,yaboot\n"
1573
"</screen></informalexample> replacing <replaceable>x</replaceable> with the partition number of the HFS partition where the kernel and yaboot files were placed, followed by a &enterkey;. On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few more seconds you will see a yaboot prompt <informalexample><screen>\n"
1575
"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The Debian installation program should start."
1578
#: boot-installer.xml:2251
1581
msgid "Booting from USB memory stick"
1584
#: boot-installer.xml:2252
1587
msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
1590
#: boot-installer.xml:2258
1593
msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. To get to the prompt, hold down <keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref linkend=\"invoking-openfirmware\"/>)."
1596
#: boot-installer.xml:2270
1599
msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
1602
#: boot-installer.xml:2282
1606
"Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
1607
"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:tbxi\n"
1608
"</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>."
1611
#: boot-installer.xml:2296
1614
msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
1617
#: boot-installer.xml:2302
1620
msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
1623
#: boot-installer.xml:2335
1626
msgid "Currently, PReP and New World PowerMac systems support netbooting."
1629
#: boot-installer.xml:2339
1632
msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <command>boot enet:0</command>. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>."
1635
#: boot-installer.xml:2354
1638
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."
1641
#: boot-installer.xml:2366
1644
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."
1647
#: boot-installer.xml:2372
1650
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."
1653
#: boot-installer.xml:2379
1656
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."
1659
#: boot-installer.xml:2390
1662
msgid "PowerPC Boot Parameters"
1665
#: boot-installer.xml:2391
1668
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> ."
1671
#: boot-installer.xml:2431
1674
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. Some older OpenBoot revisions require using the device name, such as <userinput>boot le()</userinput>; these probably don't support BOOTP nor DHCP."
1677
#: boot-installer.xml:2487
1680
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). You may have to use the actual device name for older OpenBoot versions that don't support this special command. Note that some problems have been reported on Sun4m (e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM."
1683
#: boot-installer.xml:2502
1687
"To boot from floppy on a Sparc, use <informalexample><screen>\n"
1688
"Stop-A -> OpenBoot: \"boot floppy\"\n"
1689
"</screen></informalexample> Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is <computeroutput>Bad magic number in disk label - Can't open disk label package</computeroutput>. Furthermore, a number of Sun4c models (such as the IPX) do not support the compressed images found on the disks, so also are not supported."
1692
#: boot-installer.xml:2514
1695
msgid "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from booting (instead of not supporting booting at all). The appropriate OBP update can be downloaded as product ID 106121 from <ulink url=\"http://sunsolve.sun.com\"></ulink>."
1698
#: boot-installer.xml:2521
1702
"If you are booting from the floppy, and you see messages such as <informalexample><screen>\n"
1703
"Fatal error: Cannot read partition\n"
1704
"Illegal or malformed device name\n"
1705
"</screen></informalexample> then it is possible that floppy booting is simply not supported on your machine."
1708
#: boot-installer.xml:2533
1711
msgid "IDPROM Messages"
1714
#: boot-installer.xml:2534
1717
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."
1720
#: boot-installer.xml:2553
1723
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."
1726
#: boot-installer.xml:2560
1729
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."
1732
#: boot-installer.xml:2567
1735
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\"/>."
1738
#: boot-installer.xml:2576
1742
"When the kernel boots, a message <informalexample><screen>\n"
1743
"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available\n"
1744
"</screen></informalexample> should be emitted early in the process. <replaceable>total</replaceable> should match the total amount of RAM, in kilobytes. If this doesn't match the actual amount of RAM you have installed, you need to use the <userinput>mem=<replaceable>ram</replaceable></userinput> parameter, where <replaceable>ram</replaceable> is set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM."
1747
#: boot-installer.xml:2592
1750
msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. 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>."
1753
#: boot-installer.xml:2605
1756
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>."
1759
#: boot-installer.xml:2616
1762
msgid "Debian Installer Parameters"
1765
#: boot-installer.xml:2617
1768
msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 kernels will panic. <phrase condition=\"etch\">With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options.</phrase> </para> </footnote> which may be useful."
1771
#: boot-installer.xml:2638
1774
msgid "debconf/priority"
1777
#: boot-installer.xml:2639
1780
msgid "This parameter sets the lowest priority of messages to be displayed."
1783
#: boot-installer.xml:2643
1786
msgid "The default installation uses <userinput>debconf/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."
1789
#: boot-installer.xml:2650
1792
msgid "If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>debconf/priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>debconf/priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
1795
#: boot-installer.xml:2664
1798
msgid "DEBIAN_FRONTEND"
1801
#: boot-installer.xml:2665
1804
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=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end 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, so this is not very useful right now."
1807
#: boot-installer.xml:2701
1813
#: boot-installer.xml:2702
1816
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.)"
1819
#: boot-installer.xml:2711
1822
msgid "BOOT_DEBUG=0"
1825
#: boot-installer.xml:2712
1828
msgid "This is the default."
1831
#: boot-installer.xml:2716
1834
msgid "BOOT_DEBUG=1"
1837
#: boot-installer.xml:2717
1840
msgid "More verbose than usual."
1843
#: boot-installer.xml:2721
1846
msgid "BOOT_DEBUG=2"
1849
#: boot-installer.xml:2722
1852
msgid "Lots of debugging information."
1855
#: boot-installer.xml:2726
1858
msgid "BOOT_DEBUG=3"
1861
#: boot-installer.xml:2727
1864
msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
1867
#: boot-installer.xml:2741
1870
msgid "INSTALL_MEDIA_DEV"
1873
#: boot-installer.xml:2742
1876
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>"
1879
#: boot-installer.xml:2748
1882
msgid "The boot floppy, which normally scans all floppies and USB storage devices it can to find the root floppy, can be overridden by this parameter to only look at the one device."
1885
#: boot-installer.xml:2758
1888
msgid "debian-installer/framebuffer"
1891
#: boot-installer.xml:2759
1894
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>debian-installer/framebuffer=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."
1897
#: boot-installer.xml:2768
1900
msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card."
1903
#: boot-installer.xml:2774
1906
msgid "Such problems have been reported on the Amiga 1200 and SE/30."
1909
#: boot-installer.xml:2778
1912
msgid "Such problems have been reported on hppa."
1915
#: boot-installer.xml:2782
1918
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>."
1921
#: boot-installer.xml:2795
1924
msgid "debian-installer/probe/usb"
1927
#: boot-installer.xml:2796
1930
msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems."
1933
#: boot-installer.xml:2805
1936
msgid "netcfg/disable_dhcp"
1939
#: boot-installer.xml:2806
1942
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."
1945
#: boot-installer.xml:2813
1948
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."
1951
#: boot-installer.xml:2824
1954
msgid "hw-detect/start_pcmcia"
1957
#: boot-installer.xml:2825
1960
msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
1963
#: boot-installer.xml:2835
1969
#: boot-installer.xml:2836
1972
msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>."
1975
#: boot-installer.xml:2845
1978
msgid "preseed/file"
1981
#: boot-installer.xml:2846
1984
msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>."
1987
#: boot-installer.xml:2855
1990
msgid "cdrom-detect/eject"
1993
#: boot-installer.xml:2856
1996
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."
1999
#: boot-installer.xml:2865
2002
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."
2005
#: boot-installer.xml:2876
2008
msgid "ramdisk_size"
2011
#: boot-installer.xml:2877
2014
msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;."
2017
#: boot-installer.xml:2885
2020
msgid "rescue/enable"
2023
#: boot-installer.xml:2886
2026
msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
2029
#: boot-installer.xml:2904
2032
msgid "Troubleshooting the Installation Process"
2035
#: boot-installer.xml:2909
2038
msgid "Floppy Disk Reliability"
2041
#: boot-installer.xml:2911
2044
msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability."
2047
#: boot-installer.xml:2916
2050
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."
2053
#: boot-installer.xml:2925
2056
msgid "If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a <emphasis>different</emphasis> floppy. 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."
2059
#: boot-installer.xml:2935
2062
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."
2065
#: boot-installer.xml:2941
2068
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."
2071
#: boot-installer.xml:2950
2074
msgid "Boot Configuration"
2077
#: boot-installer.xml:2952
2080
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\"/>."
2083
#: boot-installer.xml:2959
2086
msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>."
2089
#: boot-installer.xml:2966
2092
msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
2095
#: boot-installer.xml:2972
2098
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>."
2101
#: boot-installer.xml:2983
2104
msgid "Common &arch-title; Installation Problems"
2107
#: boot-installer.xml:2984
2110
msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
2113
#: boot-installer.xml:2989
2116
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>."
2119
#: boot-installer.xml:2995
2122
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>."
2125
#: boot-installer.xml:3004
2128
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."
2131
#: boot-installer.xml:3011
2134
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>debian-installer/framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
2137
#: boot-installer.xml:3026
2140
msgid "System Freeze During the PCMCIA Configuration Phase"
2143
#: boot-installer.xml:3027
2146
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."
2149
#: boot-installer.xml:3037
2152
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."
2155
#: boot-installer.xml:3054
2158
msgid "System Freeze while Loading the USB Modules"
2161
#: boot-installer.xml:3055
2164
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>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded."
2167
#: boot-installer.xml:3069
2170
msgid "Interpreting the Kernel Startup Messages"
2173
#: boot-installer.xml:3071
2176
msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)."
2179
#: boot-installer.xml:3096
2182
msgid "Bug Reporter"
2185
#: boot-installer.xml:3097
2188
msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It copies system error logs and configuration information to a user-supplied floppy. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report."
2191
#: boot-installer.xml:3106
2194
msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/debian-installer/</filename> after the computer has been booted into the installed system."
2197
#: boot-installer.xml:3117
2200
msgid "Submitting Installation Reports"
2203
#: boot-installer.xml:3118
2207
"If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations. Please use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
2208
"Package: installation-reports\n"
2210
"Debian-installer-version: <Fill in date and from where you got the image>\n"
2211
"uname -a: <The result of running uname -a on a shell prompt>\n"
2212
"Date: <Date and time of the install>\n"
2213
"Method: <How did you install? What did you boot off? If network\n"
2214
" install, from where? Proxied?>\n"
2216
"Machine: <Description of machine (eg, IBM Thinkpad R32)>\n"
2219
"Root Device: <IDE? SCSI? Name of device?>\n"
2220
"Root Size/partition table: <Feel free to paste the full partition\n"
2221
" table, with notes on which partitions are mounted where.>\n"
2222
"Output of lspci and lspci -n:\n"
2224
"Base System Installation Checklist:\n"
2225
"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
2227
"Initial boot worked: [ ]\n"
2228
"Configure network HW: [ ]\n"
2229
"Config network: [ ]\n"
2231
"Load installer modules: [ ]\n"
2232
"Detect hard drives: [ ]\n"
2233
"Partition hard drives: [ ]\n"
2234
"Create file systems: [ ]\n"
2235
"Mount partitions: [ ]\n"
2236
"Install base system: [ ]\n"
2237
"Install boot loader: [ ]\n"
2240
"Comments/Problems:\n"
2242
"<Description of the install, in prose, and any thoughts, comments\n"
2243
" and ideas you had during the initial install.>\n"
2244
"</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state."
added
removed
po/pot/boot-installer.pot
