Debian/മലയാളം/ഇന്സ്റ്റാളര്‍/മാന്വല്‍/boot-installer.po

msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2006-11-29 17:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n"
 * 1) SOME DESCRIPTIVE TITLE.
 * 2) FIRST AUTHOR , YEAR.
 * , fuzzy
 * , fuzzy

msgid "Booting the Installation System" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:4
 * , no-c-format

msgid "Booting the Installer on &arch-title;" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:9
 * , no-c-format

msgid "Alpha Console Firmware" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:20
 * , no-c-format

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:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:21
 * , no-c-format

msgid " SRM console, based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:31
 * , no-c-format

msgid " ARC, AlphaBIOS, or ARCSBIOS console, based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:38
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:47
 * , no-c-format

msgid "ARC requires that you use an MS-DOS partition table (as created by cfdisk ) for the boot disk. Therefore MS-DOS partition tables are the native 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:54
 * , no-c-format

msgid "Conversely, SRM is incompatible  Specifically, the bootsector format required by the Console Subsystem Specification conflicts with the placement of the DOS partition table.  with MS-DOS partition tables. Since Tru64 Unix uses the BSD disklabel format, this is the native partition format for SRM installations." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:63
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:76
 * , no-c-format

msgid "Because MILO 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:87
 * , no-c-format

msgid "The following table summarizes available and supported system type/console combinations (see  for the system type names). The word ARC below denotes any of the ARC-compliant consoles." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:95
 * , no-c-format

msgid "System Type" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:107
 * , no-c-format

msgid "Console Type Supported" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:108
 * , no-c-format

msgid "alcor" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:114
 * , no-c-format

msgid "ARC or SRM" msgstr ""
 * 1) . Tag: entry
 * 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
 * , no-c-format

msgid "avanti" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:117
 * , no-c-format

msgid "book1" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:120
 * , no-c-format

msgid "SRM only" msgstr ""
 * 1) . Tag: entry
 * 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
 * , no-c-format

msgid "cabriolet" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:123
 * , no-c-format

msgid "dp264" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:126
 * , no-c-format

msgid "eb164" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:129
 * , no-c-format

msgid "eb64p" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:132
 * , no-c-format

msgid "eb66" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:135
 * , no-c-format

msgid "eb66p" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:138
 * , no-c-format

msgid "jensen" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:141
 * , no-c-format

msgid "lx164" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:144
 * , no-c-format

msgid "miata" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:147
 * , no-c-format

msgid "mikasa" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:150
 * , no-c-format

msgid "mikasa-p" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:153
 * , no-c-format

msgid "nautilus" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:156
 * , no-c-format

msgid "ARC (see motherboard manual) or SRM" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:157
 * , no-c-format

msgid "noname" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:159
 * , no-c-format

msgid "noritake" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:162
 * , no-c-format

msgid "noritake-p" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:165
 * , no-c-format

msgid "pc164" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:168
 * , no-c-format

msgid "rawhide" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:171
 * , no-c-format

msgid "ruffian" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:174
 * , no-c-format

msgid "ARC only" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193
 * , no-c-format

msgid "sable" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:177
 * , no-c-format

msgid "sable-g" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:180
 * , no-c-format

msgid "sx164" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:183
 * , no-c-format

msgid "takara" msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:186
 * , no-c-format

msgid " xl " msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:189
 * , no-c-format

msgid " xlt " msgstr ""
 * 1) . Tag: entry
 * boot-installer.xml:192
 * , no-c-format

msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. For the SRM console, aboot, a small, platform-independent bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:200
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:209
 * , no-c-format

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: MILO and aboot ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:215
 * , no-c-format

msgid " MILO is itself a console, which replaces ARC or SRM in memory. MILO can be booted from both ARC and SRM and is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:221
 * , no-c-format

msgid " aboot is a small, platform-independent bootloader, which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:231
 * , no-c-format

msgid "" "Thus, three scenarios are generally possible, depending on the system's console firmware and whether or not MILO is available: \n" "SRM -&gt; aboot\n" "SRM -&gt; MILO\n" "ARC -&gt; MILO\n" " Because MILO 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 aboot on new installations of GNU/Linux, unless you wish to dual-boot with Windows NT." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:238
 * , no-c-format

msgid "The majority of AlphaServers and all current server and workstation products contain both SRM and AlphaBIOS in their firmware. For half-flash 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 arc command). For the reasons mentioned above, we recommend switching to SRM before installing &debian;." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:253
 * , no-c-format

msgid "As on other architectures, you should install the newest available revision of the firmware Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 &mdash; see  for more information.  before installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:264
 * , no-c-format

msgid "Booting with TFTP" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:283 boot-installer.xml:999 boot-installer.xml:1490 boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 boot-installer.xml:2500 boot-installer.xml:2596
 * , no-c-format

msgid "" "In SRM, Ethernet interfaces are named with the ewa prefix, and will be listed in the output of the show dev command, like this (edited slightly): \n" "&gt;&gt;&gt; show dev\n" "ewa0.0.0.9.0              EWA0              08-00-2B-86-98-65\n" "ewb0.0.0.11.0             EWB0              08-00-2B-86-98-54\n" "ewc0.0.0.2002.0           EWC0              00-06-2B-01-32-B0\n" " You first need to set the boot protocol:  \n" "&gt;&gt;&gt; set ewa0_protocols bootp\n" " Then check the medium type is correct:  \n" "&gt;&gt;&gt; set ewa0_mode mode \n" " You can get a listing of valid modes with &gt;&gt;&gt;set ewa0_mode ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:284
 * , no-c-format

msgid "" "Then, to boot from the first Ethernet interface, you would type: \n" "&gt;&gt;&gt; boot ewa0 -flags \"\"\n" " This will boot using the default kernel parameters as included in the netboot image." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:302
 * , no-c-format

msgid "If you wish to use a serial console, you must pass the console= parameter to the kernel. This can be done using the -flags argument to the SRM boot command. The serial ports are named the same as their corresponding files in /dev . 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 ewa0 and use a console on the first serial port, you would type:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:311
 * , no-c-format

msgid "&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 console=ttyS0&quot;" msgstr ""
 * 1) . Tag: screen
 * boot-installer.xml:323
 * , no-c-format

msgid "Booting from CD-ROM with the SRM Console" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:328
 * , no-c-format

msgid "" "Type \n" "&gt;&gt;&gt; boot xxxx -flags 0\n" " where xxxx is your CD-ROM drive in SRM notation." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:329
 * , no-c-format

msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:341
 * , no-c-format

msgid "To boot a CD-ROM from the ARC console, find your sub-architecture code name (see ), then enter \\milo\\linload.exe as the boot loader and \\milo\\ subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: You need to use \\milo\\ldmilo.exe as boot loader." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:342
 * , no-c-format

msgid "Booting from Floppies with the SRM Console" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:358
 * , no-c-format

msgid "" "At the SRM prompt ( &gt;&gt;&gt; ), issue the following command: \n" "&gt;&gt;&gt; boot dva0 -flags 0\n" " possibly replacing dva0 with the actual device name. Usually, dva0 is the floppy; type  \n" "&gt;&gt;&gt; show dev\n" " to see the list of devices (e.g., if you want to boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0 . If everything works OK, you will eventually see the Linux kernel boot." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:359
 * , no-c-format

msgid "" "If you want to specify kernel parameters when booting via aboot, use the following command: \n" "&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" " (typed on one line), substituting, if necessary, the actual SRM boot device name for dva0, the Linux boot device name for fd0 , and the desired kernel parameters for arguments ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:376
 * , no-c-format

msgid "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:388
 * , no-c-format

msgid "Booting from Floppies with the ARC or AlphaBIOS Console" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:398
 * , no-c-format

msgid "In the OS Selection menu, set linload.exe as the boot loader, and milo as the OS Path. Bootstrap using the newly created entry." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:400
 * , no-c-format

msgid "Booting with MILO" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:409
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:410
 * , no-c-format

msgid "" "If you want to specify all the bits explicitly (for example, to supply additional parameters), you can use a command like this: \n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" " If you are booting from something other than a floppy, substitute fd0 in the above example with the appropriate device name in Linux notation. The help command would give you a brief MILO command reference." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:416
 * , no-c-format

msgid "Booting from TFTP" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:435
 * , no-c-format

msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602
 * , no-c-format

msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607
 * , no-c-format

msgid "The installation method to support network booting is described in ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612
 * , no-c-format

msgid "Booting from TFTP on Netwinder" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:459
 * , no-c-format

msgid "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card (which is generally referred to as eth0 ) and a 100Mbps Tulip card. There may be problems loading the image via TFTP using the 100Mbps card so it is recommended that you use the 10Mbps interface (the one labeled with 10 Base-T )." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:460
 * , no-c-format

msgid "You need NeTTrom 2.2.1 or later to boot the installation system, and version 2.3.3 is recommended. Unfortunately, firmware files are currently not available for download because of license issues. If this situation changes, you may find new images at  ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:469
 * , no-c-format

msgid "" "When you boot your Netwinder you have to interrupt the boot process during the countdown. This allows you to set a number of firmware settings needed in order to boot the installer. First of all, start by loading the default settings: \n" "   NeTTrom command-&gt; load-defaults\n" " Furthermore, you must configure the network, either with a static address:  \n" "   NeTTrom command-&gt; setenv netconfig_eth0 flash\n" "   NeTTrom command-&gt; setenv eth0_ip 192.168.0.10/24\n" " where 24 is the number of set bits in the netmask, or a dynamic address:  \n" "   NeTTrom command-&gt; setenv netconfig_eth0 dhcp\n" " You may also need to configure the route1 settings if the TFTP server is not on the local subnet. Following these settings, you have to specify the TFTP server and the location of the image. You can then store your settings to flash.  \n" "   NeTTrom command-&gt; setenv kerntftpserver 192.168.0.1\n" "   NeTTrom command-&gt; setenv kerntftpfile boot.img\n" "   NeTTrom command-&gt; save-all\n" " Now you have to tell the firmware that the TFTP image should be booted:  \n" "   NeTTrom command-&gt; setenv kernconfig tftp\n" "   NeTTrom command-&gt; setenv rootdev /dev/ram\n" " If you use a serial console to install your Netwinder, you need to add the following setting:  \n" "   NeTTrom command-&gt; setenv cmdappend root=/dev/ram console=ttyS0,115200\n" " Alternatively, for installations using a keyboard and monitor you have to set:  \n" "   NeTTrom command-&gt; setenv cmdappend root=/dev/ram\n" " You can use the printenv command to review your environment settings. After you have verified that the settings are correct, you can load the image:  \n" "   NeTTrom command-&gt; boot\n" " In case you run into any problems, a detailed HOWTO is available." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:477
 * , no-c-format

msgid "Booting from TFTP on CATS" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:529
 * , no-c-format

msgid "On CATS machines, use boot de0: or similar at the Cyclone prompt." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:530
 * , no-c-format

msgid "Booting from CD-ROM" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:540
 * , no-c-format

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  configure your system for booting off a CD as described in , insert your CD, reboot, and proceed to the next chapter." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661
 * , no-c-format

msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669
 * , no-c-format

msgid "To boot a CD-ROM from the Cyclone console prompt, use the command boot cd0:cats.bin " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:580
 * , no-c-format

msgid "Booting from Firmware" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:589
 * , no-c-format

msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:595
 * , no-c-format

msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:601
 * , no-c-format

msgid "Booting the NSLU2" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:612
 * , no-c-format

msgid "There are three ways how to put the installer firmware into flash:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:613
 * , no-c-format

msgid "Using the NSLU2 web interface" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:619
 * , no-c-format

msgid "Go to the administration section and choose the menu item Upgrade . You can then browse your disk for the installer image you have previously downloaded. Then press the Start Upgrade button, confirm, wait for a few minutes and confirm again. The system will then boot straight into the installer." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:620
 * , no-c-format

msgid "Via the network using Linux/Unix" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:631
 * , no-c-format

msgid "" "You can use upslug2 from any Linux or Unix machine to upgrade the machine via the network. This software is packaged for Debian. First, you have to put your NSLU2 in upgrade mode:  Disconnect any disks and/or devices from the USB ports.    Power off the NSLU2    Press and hold the reset button (accessible through the small hole on the back just above the power input).    Press and release the power button to power on the NSLU2.    Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button.    The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode.   See the <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image:  \n" "sudo upslug2 -i di-nslu2.bin\n" " Note that the tool also shows the MAC address of your NSLU2, which may come in handy to configure your DHCP server. After the whole image has been written and verified, the system will automatically reboot. Make sure you connect your USB disk again now, otherwise the installer won't be able to find it." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:632
 * , no-c-format

msgid "Via the network using Windows" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:693
 * , no-c-format

msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">a tool for Windows to upgrade the firmware via the network." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:694
 * , no-c-format

msgid "Booting from a CD-ROM" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 boot-installer.xml:2282 boot-installer.xml:2636
 * , no-c-format

msgid "Booting from Linux Using LILO or GRUB " msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:848
 * , no-c-format

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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:851
 * , no-c-format

msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the netboot/debian-installer/i386/initrd.gz file and its corresponding kernel netboot/debian-installer/i386/linux . This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:856
 * , no-c-format

msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the hd-media/initrd.gz file and its kernel, as well as copy a CD iso to the drive (make sure the file is named ending in .iso ). The installer can then boot from the drive and install from the CD image, without needing the network." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:866
 * , no-c-format

msgid "For LILO, you will need to configure two essential things in /etc/lilo.conf :  to load the initrd.gz installer at boot time;    have the vmlinuz kernel use a RAM disk as its root partition.   Here is a /etc/lilo.conf example:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:875
 * , no-c-format

msgid "" "image=/boot/newinstall/vmlinuz\n" "      label=newinstall\n" "      initrd=/boot/newinstall/initrd.gz\n" "      root=/dev/ram0\n" "      append=\"ramdisk_size=12000\"" msgstr ""
 * 1) . Tag: screen
 * boot-installer.xml:896
 * , no-c-format

msgid "For more details, refer to the initrd  4  and  lilo.conf  5  man pages. Now run lilo and reboot." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:896
 * , no-c-format

msgid "" "The procedure for GRUB is quite similar. Locate your menu.lst in the /boot/grub/ directory (sometimes in the /boot/boot/grub/ ), add the following lines: \n" "title New Install\n" "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" " and reboot." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:905
 * , no-c-format

msgid "Note that the value of the ramdisk_size may need to be adjusted for the size of the initrd image. From here on, there should be no difference between GRUB or LILO ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:916
 * , no-c-format

msgid "Booting from USB Memory Stick" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:927
 * , no-c-format

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 boot: prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:928
 * , no-c-format

msgid "Booting from Floppies" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 boot-installer.xml:2690
 * , no-c-format

msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:942 boot-installer.xml:2550
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:949
 * , no-c-format

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 root= 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 linux root=/dev/hdc at the boot prompt." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:955
 * , no-c-format

msgid "Note that on some machines, Control  Alt  Delete  does not properly reset the machine, so a hard 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:965
 * , no-c-format

msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the boot: prompt." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:974
 * , no-c-format

msgid "Once you press &enterkey;, you should see the message Loading..., followed by Uncompressing Linux... , 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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:980
 * , no-c-format

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 debian-installer is automatically launched." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:989
 * , no-c-format

msgid "There are various ways to do a TFTP boot on i386." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1023
 * , no-c-format

msgid "NIC or Motherboard that support PXE" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1029
 * , no-c-format

msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel re-implementation of TFTP boot. If so you may be able to configure your BIOS to boot from the network." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1030
 * , no-c-format

msgid "NIC with Network BootROM" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1041
 * , no-c-format

msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1042
 * , no-c-format

msgid "Let us ( &email-debian-boot-list; ) know how did you manage it. Please refer to this document." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1047
 * , no-c-format

msgid "Etherboot" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1055
 * , no-c-format

msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project provides bootdiskettes and even bootroms that do a TFTPboot." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1056
 * , no-c-format

msgid "The Boot Prompt" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1065
 * , no-c-format

msgid "" "When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and the boot prompt: \n" "Press F1 for help, or ENTER to boot:\n" " 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1066
 * , no-c-format

msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing F2 through F8 . If you add any parameters to the boot command line, be sure to type the boot method (the default is linux ) and a space before the first parameter (e.g., linux fb=false )." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1078
 * , no-c-format

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 integrated Lights Out (iLO) and HP's Integrated Remote Assistant (IRA). You can blindly press F1 In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses  Ctrl  F , 1 .  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 fb=false to the boot prompt, as described in the help text." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1087
 * , no-c-format

msgid "CD Contents" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1162
 * , no-c-format

msgid "There are three basic variations of Debian Install CDs. The Business Card 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 Network Install 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1164
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1180
 * , no-c-format

msgid "The Debian Installer CD contains a small EFI partition where the ELILO 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1196
 * , no-c-format

msgid "Most of the details of how ELILO 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 ELILO 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1205
 * , no-c-format

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, Boot Option Maintenance Menu and EFI Shell (Built-in) . 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1217
 * , no-c-format

msgid "IMPORTANT" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1236
 * , no-c-format

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 exit at the shell prompt." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1237
 * , no-c-format

msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1249
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1256
 * , no-c-format

msgid "Select Boot Maintenance Menu from the menu with the arrow keys and press ENTER . This will display a new menu." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1262
 * , no-c-format

msgid "Select Boot From a File from the menu with the arrow keys and press ENTER . This will display a list of devices probed by the firmware. You should see two menu lines containing either the label Debian Inst [Acpi ... or Removable Media Boot . If you examine the rest of the menu line, you will notice that the device and controller information should be the same." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1268
 * , no-c-format

msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press ENTER . If you choose Removable Media Boot the machine will immediately start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1279
 * , no-c-format

msgid "You will only need this step if you chose Debian Inst [Acpi ... . The directory listing will also show [Treat like Removable Media Boot] on the next to the last line. Select this line with the arrow keys and press ENTER . This will start the boot load sequence." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1290
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1302
 * , no-c-format

msgid "Option 2: Booting from the EFI Shell" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1312
 * , no-c-format

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 EFI Shell [Built-in] . Boot the Debian Installer CD with the following steps:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1313
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1324
 * , no-c-format

msgid "Select EFI Shell from the menu with the arrow keys and press ENTER . 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 fs n : . All other recognized partitions will be named blk n : . If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1330
 * , no-c-format

msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the fs0: device although other devices with bootable partitions will also show up as fs n ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1344
 * , no-c-format

msgid "Enter fs n : and press ENTER to select that device where n is the partition number for the CDROM. The shell will now display the partition number as its prompt." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1351
 * , no-c-format

msgid "Enter elilo and press ENTER . This will start the boot load sequence." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1358
 * , no-c-format

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 fs n :elilo command at the shell prompt. Proceed to selecting the boot kernel and options." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1365
 * , no-c-format

msgid "Installing using a Serial Console" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1379
 * , no-c-format

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 [ BAUD baud serial console], where BAUD is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1381
 * , no-c-format

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 baud at the EFI shell." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1392
 * , no-c-format

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 console=ttyS1,57600n8 into the Boot: text window." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1399
 * , no-c-format

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 Params help menu for instructions on starting the installer in Text Mode." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1410
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1419
 * , no-c-format

msgid "Selecting the Boot Kernel and Options" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1428
 * , no-c-format

msgid "The boot loader will display a form with a menu list and a text window with a Boot: 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 General help screen explains the menu choices and the Params screen explains the common command line options." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1430
 * , no-c-format

msgid "Consult the General 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 Boot: 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:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1442
 * , no-c-format

msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1460
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1465
 * , no-c-format

msgid "Press ENTER . This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the Debian Installer." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1472
 * , no-c-format

msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1481
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1492
 * , no-c-format

msgid "Network booting an ia64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver elilo . On the client a new boot option must be defined in the EFI boot manager to enable loading over a network." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1526
 * , no-c-format

msgid "Configuring the Server" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1537
 * , no-c-format

msgid "" "A suitable TFTP entry for network booting an ia64 system looks something like this: \n" "host mcmuffin {\n" "       hardware ethernet 00:30:6e:1e:0e:83;\n" "       fixed-address 10.0.0.21;\n" "       filename \"debian-installer/ia64/elilo.efi\";\n" "}\n" " Note that the goal is to get elilo.efi running on the client." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1538
 * , no-c-format

msgid "Extract the netboot.tar.gz file into the directory used as the root for your tftp server. Typical tftp root directories include /var/lib/tftp and /tftpboot . This will create a debian-installer directory tree containing the boot files for an IA-64 system." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1548
 * , no-c-format

msgid "" "# cd /var/lib/tftp\n" "# tar xvfz /home/user/netboot.tar.gz\n" "./\n" "./debian-installer/\n" "./debian-installer/ia64/\n" "[...]" msgstr ""
 * 1) . Tag: screen
 * boot-installer.xml:1558
 * , no-c-format

msgid "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you need to make changes to this file, you can find it in the debian-installer/ia64/ 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 .conf instead of elilo.conf . See documentation provided in the elilo package for details." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1558
 * , no-c-format

msgid "Configuring the Client" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1575
 * , no-c-format

msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the Boot Option Maintenance Menu .  Add a boot option.    You should see one or more lines with the text Load File [Acpi/.../Mac] . 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.    Name the entry Netboot or something similar, save, and exit back to the boot options menu.   You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of elilo.efi from the server." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1576
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1608
 * , no-c-format

msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1617
 * , no-c-format

msgid "Choosing an Installation Method" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1630
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1632
 * , no-c-format

msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1640
 * , no-c-format

msgid "Make sure root=/dev/ram is one of your kernel parameters." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1645
 * , no-c-format

msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1650
 * , no-c-format

msgid "Amiga" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1667
 * , no-c-format

msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). In other words the cdrom is not bootable. " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1668
 * , no-c-format

msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter fb=false ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1674
 * , no-c-format

msgid "Atari" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1683
 * , no-c-format

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\"/>). In other words the cdrom is not bootable. " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1684
 * , no-c-format

msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter fb=false ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1691
 * , no-c-format

msgid "BVME6000" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1700
 * , no-c-format

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\"/>)." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1701
 * , no-c-format

msgid "Macintosh" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1711
 * , no-c-format

msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). In other words the cdrom is not bootable. Macs do not have a working 2.4.x kernel." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1712
 * , no-c-format

msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter mac53c9x=1,0 . Hardware with two such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as mac53c9x=-1,0 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1719
 * , no-c-format

msgid "MVME147 and MVME16x" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1734
 * , no-c-format

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\"/>). In other words the cdrom is not bootable. " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1735
 * , no-c-format

msgid "Q40/Q60" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1745
 * , no-c-format

msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). In other words the cdrom is not bootable. " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1746
 * , no-c-format

msgid "Booting from a Hard Disk" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1757
 * , no-c-format

msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1763 boot-installer.xml:2361
 * , no-c-format

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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1769 boot-installer.xml:2367
 * , no-c-format

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 for details)." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1778
 * , no-c-format

msgid "The three different types of ramdisks are cdrom, hd-media , and nativehd . These ramdisks differ only in their source for installation packages. The cdrom ramdisk uses a cdrom to get debian-installer packages. The hd-media ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the nativehd ramdisk uses the net to install packages." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1786
 * , no-c-format

msgid "Booting from AmigaOS" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1807
 * , no-c-format

msgid "In the Workbench, start the Linux installation process by double-clicking on the StartInstall icon in the debian directory." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1808
 * , no-c-format

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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1814
 * , no-c-format

msgid "Booting from Atari TOS" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1829
 * , no-c-format

msgid "At the GEM desktop, start the Linux installation process by double-clicking on the bootstra.prg icon in the debian directory and clicking Ok at the program options dialog box." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1830
 * , no-c-format

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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1837
 * , no-c-format

msgid "Booting from MacOS" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1852
 * , no-c-format

msgid "You must retain the original Mac system and boot from it. It is essential that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the shift 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1853
 * , no-c-format

msgid "Macs require the Penguin bootloader. If you do not have the tools to handle a Stuffit archive, &penguin19.hfs; is an hfs disk image with Penguin unpacked. <xref linkend=\"create-floppy\"/> describes how to copy this image to a floppy." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1864
 * , no-c-format

msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the Penguin Prefs icon in the Penguin directory. The Penguin booter will start up. Go to the Settings item in the File menu, click the Kernel tab. Select the kernel ( vmlinuz ) and ramdisk ( initrd.gz ) images in the install directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1873
 * , no-c-format

msgid "To set the boot parameters in Penguin, choose File -&gt; Settings..., then switch to the Options tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select File -&gt; Save Settings as Default ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1888
 * , no-c-format

msgid "Close the Settings dialog, save the settings and start the bootstrap using the Boot Now item in the File menu." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1897
 * , no-c-format

msgid "The Penguin 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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1904
 * , no-c-format

msgid "Booting from Q40/Q60" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:1919
 * , no-c-format

msgid "FIXME" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1921
 * , no-c-format

msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1925
 * , no-c-format

msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:1937
 * , no-c-format

msgid "After booting the VMEbus systems you will be presented with the LILO Boot: prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2009
 * , no-c-format

msgid "type i6000 &enterkey; to install a BVME4000/6000" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2020
 * , no-c-format

msgid "type i162 &enterkey; to install an MVME162" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2025
 * , no-c-format

msgid "type i167 &enterkey; to install an MVME166/167" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2030
 * , no-c-format

msgid "You may additionally append the string TERM=vt100 to use vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey; ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2037
 * , no-c-format

msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2049
 * , no-c-format

msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2054
 * , no-c-format

msgid "SGI TFTP Booting" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2070 boot-installer.xml:2117
 * , no-c-format

msgid "" "After entering the command monitor use \n" "bootp:\n" " on SGI machines to boot linux and to begin installation of the Debian Software. In order to make this work you may have to unset the netaddr environment variable. Type  \n" "unsetenv netaddr\n" " in the command monitor to do this." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2071
 * , no-c-format

msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 boot-installer.xml:2233
 * , no-c-format

msgid "" "On the Broadcom BCM91250A and BCM91480B evaluation boards, 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: \n" "ifconfig eth0 -auto\n" " Once you have obtained an IP address, you can load SiByl with the following command:  \n" "boot 192.168.1.1:/boot/sibyl\n" " 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2091 boot-installer.xml:2195
 * , no-c-format

msgid "Boot Parameters" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2741
 * , no-c-format

msgid "On SGI machines you can append boot parameters to the bootp: command in the command monitor." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2118
 * , no-c-format

msgid "" "Following the bootp: 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: \n" "bootp:/boot/tftpboot.img\n" " Further kernel parameters can be passed via append :" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2123
 * , no-c-format

msgid "bootp: append=\"root=/dev/sda1\"" msgstr ""
 * 1) . Tag: screen
 * boot-installer.xml:2133
 * , no-c-format

msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the /boot/sibyl.conf file on the TFTP server and add your parameters to the extra_args variable." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2140 boot-installer.xml:2234
 * , no-c-format

msgid "Cobalt TFTP Booting" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2159 boot-installer.xml:2221
 * , no-c-format

msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in /nfsroot . When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2160
 * , no-c-format

msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2170
 * , no-c-format

msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2179
 * , no-c-format

msgid "You cannot pass any boot parameters directly. Instead, you have to edit the /nfsroot/default.colo file on the NFS server and add your parameters to the args variable." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2222
 * , no-c-format

msgid "s390 Limitations" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2250
 * , no-c-format

msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2251
 * , no-c-format

msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2256
 * , no-c-format

msgid "s390 Boot Parameters" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2267
 * , no-c-format

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 for more information about S/390-specific boot parameters." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2268
 * , no-c-format

msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP and New World PowerMacs. On PowerMacs, hold the c key, or else the combination of Command, Option , Shift , and Delete keys together while booting to boot from the CD-ROM." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2322
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2331
 * , no-c-format

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 yaboot on the CD at the OF prompt, such as" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2340
 * , no-c-format

msgid "0 &gt; boot cd:,\\install\\yaboot" msgstr ""
 * 1) . Tag: screen
 * boot-installer.xml:2349
 * , no-c-format

msgid "Booting from Hard Disk" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2355
 * , no-c-format

msgid "Booting CHRP from OpenFirmware" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2376
 * , no-c-format

msgid "Not yet written." msgstr ""
 * 1) . Tag: emphasis
 * boot-installer.xml:2380
 * , no-c-format

msgid "Booting OldWorld PowerMacs from MacOS" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2385
 * , no-c-format

msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the BootX application icon. Click on the Options button and select Use Specified RAM Disk . This will give you the chance to select the ramdisk.image.gz file. You may need to select the No Video Driver checkbox, depending on your hardware. Then click the Linux button to shut down MacOS and launch the installer." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2386
 * , no-c-format

msgid "Booting NewWorld Macs from OpenFirmware" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2404
 * , no-c-format

msgid "" "You will have already placed the vmlinux, initrd.gz , yaboot , and yaboot.conf 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 Option , Command (cloverleaf/Apple) , o , and f keys all together. After a few seconds you will be presented with the Open Firmware prompt. At the prompt, type \n" "0 &gt; boot hd: x ,yaboot\n" " replacing x 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 ide0: instead of hd: . In a few more seconds you will see a yaboot prompt  \n" "boot:\n" " At yaboot's boot: prompt, type either install or install video=ofonly followed by a &enterkey;. The video=ofonly argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2405
 * , no-c-format

msgid "Booting from USB memory stick" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2440
 * , no-c-format

msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2441
 * , no-c-format

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 Command  Option  o  f  all together while booting (see <xref linkend=\"invoking-openfirmware\"/>)." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2447
 * , no-c-format

msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment ofpath cannot work that out automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk , /pci@f2000000/usb@1b,1/disk@1 , and /pci@f2000000/usb@1b,1/hub@1/disk@1 work." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2459
 * , no-c-format

msgid "" "Having worked out the device path, use a command like this to boot the installer: \n" "boot usb0/disk : 2 ,\\\\:tbxi\n" " The 2 matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the ,\\\\:tbxi part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. yaboot ) in the directory previously blessed with hattrib -b ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2471
 * , no-c-format

msgid "The system should now boot up, and you should be presented with the boot: prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2485
 * , no-c-format

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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2491
 * , no-c-format

msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2524
 * , no-c-format

msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command boot enet:0 . PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try boot server_ipaddr, file , client_ipaddr ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2528
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2543
 * , no-c-format

msgid "To boot from the boot-floppy-hfs.img floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2555
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2561
 * , no-c-format

msgid "After booting, the root.bin 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2568
 * , no-c-format

msgid "PowerPC Boot Parameters" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2579
 * , no-c-format

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 video=atyfb:vmode:6, which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to video=aty128fb:vmode:6 ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2580
 * , no-c-format

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 boot net to boot from a TFTP and RARP server, or try boot net:bootp or boot net:dhcp to boot from a TFTP and BOOTP or DHCP server. Some older OpenBoot revisions require using the device name, such as boot le ; these probably don't support BOOTP nor DHCP." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2620
 * , no-c-format

msgid "Most OpenBoot versions support the boot cdrom 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2676
 * , no-c-format

msgid "" "To boot from floppy on a Sparc, use \n" "Stop-A -&gt; OpenBoot: \"boot floppy\"\n" " Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is Bad magic number in disk label - Can't open disk label package . 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2691
 * , no-c-format

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\"> ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2703
 * , no-c-format

msgid "" "If you are booting from the floppy, and you see messages such as \n" "Fatal error: Cannot read partition\n" "Illegal or malformed device name\n" " then it is possible that floppy booting is simply not supported on your machine." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2710
 * , no-c-format

msgid "IDPROM Messages" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2722
 * , no-c-format

msgid "If you cannot boot because you get messages about a problem with IDPROM, 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 for more information." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2723
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2742
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2749
 * , no-c-format

msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO, 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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2756
 * , no-c-format

msgid "" "When the kernel boots, a message \n" "Memory: avail k/ total k available\n" " should be emitted early in the process. total 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 mem= ram  parameter, where ram is set to the amount of memory, suffixed with k for kilobytes, or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2765
 * , no-c-format

msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations) . 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 console= device argument to the kernel, where device is your serial device, which is usually something like ttyS0 ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2781
 * , no-c-format

msgid "For &arch-title; the serial devices are ttya or ttyb . Alternatively, set the input-device and output-device OpenPROM variables to ttya ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2794
 * , no-c-format

msgid "Debian Installer Parameters" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:2805
 * , no-c-format

msgid "The installation system recognizes a few additional boot parameters With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic.  which may be useful." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2806
 * , no-c-format

msgid "debconf/priority" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:2823
 * , no-c-format

msgid "This parameter sets the lowest priority of messages to be displayed. Short form: priority " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2824
 * , no-c-format

msgid "The default installation uses priority=high . 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2829
 * , no-c-format

msgid "If you add priority=medium as boot parameter, you will be shown the installation menu and gain more control over the installation. When priority=low is used, all messages are shown (this is equivalent to the expert boot method). With priority=critical, the installation system will display only critical messages and try to do the right thing without fuss." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2836
 * , no-c-format

msgid "DEBIAN_FRONTEND" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:2850
 * , no-c-format

msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are:   DEBIAN_FRONTEND=noninteractive      DEBIAN_FRONTEND=text      DEBIAN_FRONTEND=newt      DEBIAN_FRONTEND=gtk    The default frontend is DEBIAN_FRONTEND=newt . DEBIAN_FRONTEND=text may be preferable for serial console installs. Generally only the newt frontend is available on default install media. On architectures which support it, the graphical installer uses the gtk frontend." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2851
 * , no-c-format

msgid "BOOT_DEBUG" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:2880
 * , no-c-format

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.)" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2881
 * , no-c-format

msgid "BOOT_DEBUG=0" msgstr ""
 * 1) . Tag: userinput
 * boot-installer.xml:2890
 * , no-c-format

msgid "This is the default." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2891
 * , no-c-format

msgid "BOOT_DEBUG=1" msgstr ""
 * 1) . Tag: userinput
 * boot-installer.xml:2895
 * , no-c-format

msgid "More verbose than usual." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2896
 * , no-c-format

msgid "BOOT_DEBUG=2" msgstr ""
 * 1) . Tag: userinput
 * boot-installer.xml:2900
 * , no-c-format

msgid "Lots of debugging information." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2901
 * , no-c-format

msgid "BOOT_DEBUG=3" msgstr ""
 * 1) . Tag: userinput
 * boot-installer.xml:2905
 * , no-c-format

msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2906
 * , no-c-format

msgid "INSTALL_MEDIA_DEV" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:2920
 * , no-c-format

msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0 " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2921
 * , no-c-format

msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2927
 * , no-c-format

msgid "debian-installer/framebuffer" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:2937
 * , no-c-format

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 debian-installer/framebuffer=false, or fb=false for short. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2938
 * , no-c-format

msgid "The video=vga16:off argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2948
 * , no-c-format

msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2954
 * , no-c-format

msgid "Such problems have been reported on hppa." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2958
 * , no-c-format

msgid "Because of display problems on some systems, framebuffer support is disabled by default 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 debian-installer/framebuffer=true or fb=true for short." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2962
 * , no-c-format

msgid "debian-installer/theme" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:2976
 * , no-c-format

msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a dark theme that was designed for visually impaired users. Set the theme by booting with parameter debian-installer/theme= dark or theme= dark  ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2977
 * , no-c-format

msgid "debian-installer/probe/usb" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:2990
 * , no-c-format

msgid "Set to false to prevent probing for USB on boot, if that causes problems." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:2991
 * , no-c-format

msgid "netcfg/disable_dhcp" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3000 boot-installer.xml:3153
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3001
 * , no-c-format

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 netcfg/disable_dhcp=true to prevent configuring the network with DHCP and to enter the information manually." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3008
 * , no-c-format

msgid "hw-detect/start_pcmcia" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3019
 * , no-c-format

msgid "Set to false to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3020
 * , no-c-format

msgid "preseed/url" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3030
 * , no-c-format

msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: url ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3031
 * , no-c-format

msgid "preseed/file" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3041
 * , no-c-format

msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: file ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3042
 * , no-c-format

msgid "auto-install/enabled" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3052
 * , no-c-format

msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. Short form: auto=true See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3053
 * , no-c-format

msgid "cdrom-detect/eject" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3064
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3065
 * , no-c-format

msgid "Set to false 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3074
 * , no-c-format

msgid "ramdisk_size" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3085
 * , no-c-format

msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3086
 * , no-c-format

msgid "mouse/left" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3094
 * , no-c-format

msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to true ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3095
 * , no-c-format

msgid "directfb/hw-accel" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3104
 * , no-c-format

msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to true when booting the installer." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3105
 * , no-c-format

msgid "rescue/enable" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3115
 * , no-c-format

msgid "Set to true to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3116
 * , no-c-format

msgid "Using boot parameters to answer questions" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3127
 * , no-c-format

msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3128
 * , no-c-format

msgid "debian-installer/locale" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3140
 * , no-c-format

msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. Short form: locale . For example, use locale=de_CH to select German as language and Switserland as country." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3141
 * , no-c-format

msgid "Set to true if you want to disable DHCP and instead force static network configuration." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3154
 * , no-c-format

msgid "tasksel:tasksel/first" msgstr ""
 * 1) . Tag: term
 * boot-installer.xml:3163
 * , no-c-format

msgid "Can be used to select tasks that are not available from the interactive task list, such as the kde-desktop task. See <xref linkend=\"pkgsel\"/> for additional information. Short form: tasks ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3164
 * , no-c-format

msgid "Passing parameters to kernel modules" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3178
 * , no-c-format

msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3179
 * , no-c-format

msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3192
 * , no-c-format

msgid "" "The syntax to use to set parameters for modules is: \n" " module_name . parameter_name = value \n" " If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:" msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3199
 * , no-c-format

msgid "3c509.xcvr=3 3c509.irq=10" msgstr ""
 * 1) . Tag: screen
 * boot-installer.xml:3209
 * , no-c-format

msgid "Troubleshooting the Installation Process" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3221
 * , no-c-format

msgid "CD-ROM Reliability" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3226
 * , no-c-format

msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3227
 * , no-c-format

msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3234
 * , no-c-format

msgid "There are two very simple things that you should try first." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3240
 * , no-c-format

msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3245
 * , no-c-format

msgid "If the installer fails to recognize a CD-ROM, try just running the option Detect and mount CD-ROM  a second time. Some DMA related isses with older CD-ROM drives are known to be resolved in this way." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3251
 * , no-c-format

msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3261
 * , no-c-format

msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3267
 * , no-c-format

msgid "Common issues" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3275
 * , no-c-format

msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3278
 * , no-c-format

msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3284
 * , no-c-format

msgid "Some older CD-ROM drives do not work correctly if direct memory access (DMA) is enabled." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3291
 * , no-c-format

msgid "How to investigate and maybe solve issues" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3302
 * , no-c-format

msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3303
 * , no-c-format

msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3308
 * , no-c-format

msgid "" "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from. \n" "$ md5sum debian-testing-i386-netinst.iso \n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso \n" " Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3314
 * , no-c-format

msgid "" "$ dd if=/dev/cdrom | \\\n" "> head -c `stat --format=%s debian-testing-i386-netinst.iso ` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 records in\n" "262668+0 records out\n" "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" msgstr ""
 * 1) . Tag: screen
 * boot-installer.xml:3327
 * , no-c-format

msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3332
 * , no-c-format

msgid "Switch to VT4 or view the contents of /var/log/syslog (use nano as editor) to check for any specific error messages. After that, also check the output of dmesg ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3344
 * , no-c-format

msgid "" "Check in the output of dmesg if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" " If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the drive, you can try loading it manually using modprobe ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3351
 * , no-c-format

msgid "Check that there is a device node for your CD-ROM drive under /dev/ . In the example above, this would be /dev/hdc . There should also be a /dev/cdroms/cdrom0 ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3365
 * , no-c-format

msgid "" "Use the mount command to check if the CD-ROM is already mounted; if not, try mounting it manually: \n" "$ mount /dev/ hdc /cdrom\n" " Check if there are any error messages after that command." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3373
 * , no-c-format

msgid "" "Check if DMA is currently enabled: \n" "$ cd /proc/ ide / hdc \n" "$ grep dma settings\n" "using_dma     1       0       1       rw\n" " A 1 means it is enabled. If it is, try disabling it:  \n" "$ echo -n \"using_dma:0\" >settings\n" " Make sure that you are in the directory for the device that corresponds to your CD-ROM drive." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3383
 * , no-c-format

msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3397
 * , no-c-format

msgid "Floppy Disk Reliability" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3412
 * , no-c-format

msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3414
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3419
 * , no-c-format

msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a different floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3428
 * , no-c-format

msgid "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the third floppy." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3437
 * , no-c-format

msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3443
 * , no-c-format

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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3449
 * , no-c-format

msgid "Boot Configuration" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3458
 * , no-c-format

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\"/>." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3460
 * , no-c-format

msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that CONFIG_DEVFS is set in your kernel. The installer requires CONFIG_DEVFS ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3467
 * , no-c-format

msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic. " msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3474
 * , no-c-format

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 mem=512m ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3480
 * , no-c-format

msgid "Common &arch-title; Installation Problems" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3491
 * , no-c-format

msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3492
 * , no-c-format

msgid "Some systems have floppies with inverted DCLs . If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter floppy=thinkpad ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3497
 * , no-c-format

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 hd= cylinders, heads , sectors ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3503
 * , no-c-format

msgid "If you have a very old machine, and the kernel hangs after saying Checking 'hlt' instruction..., then you should try the no-hlt boot argument, which disables this test." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3512
 * , no-c-format

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 fb=false video=vga16:off 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3519
 * , no-c-format

msgid "System Freeze During the PCMCIA Configuration Phase" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3533
 * , no-c-format

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 hw-detect/start_pcmcia=false boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3534
 * , no-c-format

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 exclude port 0x800-0x8ff 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 . Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3544
 * , no-c-format

msgid "System Freeze while Loading the USB Modules" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3561
 * , no-c-format

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 debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from being loaded." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3562
 * , no-c-format

msgid "Interpreting the Kernel Startup Messages" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3576
 * , no-c-format

msgid "During the boot sequence, you may see many messages in the form can't find something, or  something not present , can't initialize something  , or even this driver release depends on something  . 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\"/>)." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3578
 * , no-c-format

msgid "Bug Reporter" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3603
 * , no-c-format

msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3604
 * , no-c-format

msgid "Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3615
 * , no-c-format

msgid "Submitting Installation Reports" msgstr ""
 * 1) . Tag: title
 * boot-installer.xml:3626
 * , no-c-format

msgid "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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3627
 * , no-c-format

msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages ( apt-get install installation-report reportbug ) and run the command reportbug installation-report ." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3634
 * , no-c-format

msgid "" "Please use this template when filling out installation reports, and file the report as a bug report against the installation-reports pseudo package, by sending it to submit@bugs.debian.org . \n" "Package: installation-reports\n" "\n" "Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n" "Image version: &lt;Full URL to image you downloaded is best&gt;\n" "Date: &lt;Date and time of the install&gt;\n" "\n" "Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n" "Processor:\n" "Memory:\n" "Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n" "\n" "Output of lspci -nn and lspci -vnn:\n" "\n" "Base System Installation Checklist:\n" "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" "\n" "Initial boot:          [ ]\n" "Detect network card:   [ ]\n" "Configure network:     [ ]\n" "Detect CD:             [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives:    [ ]\n" "Partition hard drives: [ ]\n" "Install base system:   [ ]\n" "Clock/timezone setup:  [ ]\n" "User/password setup:   [ ]\n" "Install tasks:         [ ]\n" "Install boot loader:   [ ]\n" "Overall install:       [ ]\n" "\n" "Comments/Problems:\n" "\n" "&lt;Description of the install, in prose, and any thoughts, comments\n" "     and ideas you had during the initial install.&gt;\n" " 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." msgstr ""
 * 1) . Tag: para
 * boot-installer.xml:3641
 * , no-c-format