# SOME DESCRIPTIVE TITLE. # FIRST AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: d-i-manual_boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2013-04-16 19:15+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #: boot-installer.xml:4 #, no-c-format msgid "Booting the Installation System" msgstr "" #. Tag: title #: boot-installer.xml:9 #, no-c-format msgid "Booting the Installer on &arch-title;" msgstr "" #. Tag: para #: boot-installer.xml:15 #, no-c-format msgid "" "If you have any other operating systems on your system that you wish to keep " "(dual boot setup), you should make sure that they have been properly shut " "down before you boot the installer. Installing an " "operating system while another operating system is in hibernation (has been " "suspended to disk) could result in loss of, or damage to the state of the " "suspended operating system which could cause problems when it is rebooted." msgstr "" #. Tag: para #: boot-installer.xml:26 #, no-c-format msgid "" "For information on how to boot the graphical installer, see ." msgstr "" #. Tag: title #: boot-installer.xml:37 #, no-c-format msgid "Booting from TFTP" msgstr "" #. Tag: para #: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127 #: boot-installer.xml:1650 boot-installer.xml:1759 #, 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 "" #. Tag: para #: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132 #: boot-installer.xml:1655 boot-installer.xml:1764 #, no-c-format msgid "" "Older systems such as the 715 might require the use of an RBOOT server " "instead of a BOOTP server." msgstr "" #. Tag: para #: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137 #: boot-installer.xml:1660 boot-installer.xml:1769 #, no-c-format msgid "" "The installation method to support network booting is described in ." msgstr "" #. Tag: title #: boot-installer.xml:64 #, no-c-format msgid "Booting from CD-ROM" msgstr "" #. Tag: para #: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746 #: boot-installer.xml:1426 boot-installer.xml:1798 #, 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 "" #. Tag: para #: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757 #: boot-installer.xml:1437 boot-installer.xml:1809 #, 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 "" #. Tag: para #: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765 #: boot-installer.xml:1445 boot-installer.xml:1817 #, 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 "" #. Tag: para #: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773 #: boot-installer.xml:1453 boot-installer.xml:1825 #, no-c-format msgid "" "If you have problems booting, see ." msgstr "" #. Tag: title #: boot-installer.xml:107 #, no-c-format msgid "Booting from Firmware" msgstr "" #. Tag: para #: boot-installer.xml:113 #, 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 "" #. Tag: para #: boot-installer.xml:119 #, 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 "" #. Tag: title #: boot-installer.xml:131 #, no-c-format msgid "Booting the SS4000-E" msgstr "" #. Tag: para #: boot-installer.xml:132 #, no-c-format msgid "" "Due to limitations in the SS4000-E firmware, it unfortunately is not " "possible to boot the installer without the use of a serial port at this " "time. To boot the installer, you will need a serial nullmodem cable; a " "computer with a serial port A USB " "serial converter will also work. ; and a ribbon cable " "with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the " "other This cable is often found in older " "desktop machines with builtin 9-pin serial ports. ." msgstr "" #. Tag: para #: boot-installer.xml:153 #, no-c-format msgid "" "To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable " "to connect to the serial port of the SS4000-E, and reboot the machine. You " "need to use a serial terminal application to communicate with the machine; a " "good option on a &debian; GNU/Linux is to use the cu " "program, in the package of the same name. Assuming the serial port on your " "computer is to be found on /dev/ttyS0, use the " "following command line:" msgstr "" #. Tag: screen #: boot-installer.xml:165 #, no-c-format msgid "cu -lttyS0 -s115200" msgstr "" #. Tag: para #: boot-installer.xml:167 #, no-c-format msgid "" "If using Windows, you may want to consider using the program " "hyperterminal. Use a baud rate of 115200, 8 bits word " "length, no stop bits, and one parity bit." msgstr "" #. Tag: para #: boot-installer.xml:173 #, no-c-format msgid "When the machine boots, you will see the following line of output:" msgstr "" #. Tag: screen #: boot-installer.xml:179 #, no-c-format msgid "" "No network interfaces found\n" "\n" "EM-7210 ver.T04 2005-12-12 (For ver.AA)\n" "== Executing boot script in 1.000 seconds - enter ^C to abort" msgstr "" #. Tag: para #: boot-installer.xml:181 #, no-c-format msgid "" "At this point, hit Control-C to interrupt the boot loader Note that you have only one second to do so; if you miss " "this window, just powercycle the machine and try again. . " "This will give you the RedBoot prompt. Enter the following commands:" msgstr "" #. Tag: screen #: boot-installer.xml:194 #, no-c-format msgid "" "load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n" "load -v -r -b 0x01008000 -m ymodem zImage\n" "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r " "0x01800000" msgstr "" #. Tag: para #: boot-installer.xml:196 #, no-c-format msgid "" "After every load command, the system will expect a file " "to be transmitted using the YMODEM protocol. When using cu, make sure you " "have the package lrzsz installed, then hit enter, " "followed by the ~< escape sequence to start an external " "program, and run sb initrd.gz or sb vmlinuz." msgstr "" #. Tag: para #: boot-installer.xml:205 #, no-c-format msgid "" "Alternatively, it is possible to load the kernel and ramdisk using HTTP " "rather than YMODEM. This is faster, but requires a working HTTP server on " "the network. To do so, first switch the bootloader to RAM mode:" msgstr "" #. Tag: screen #: boot-installer.xml:211 #, no-c-format msgid "" "fis load rammode\n" "g" msgstr "" #. Tag: para #: boot-installer.xml:213 #, no-c-format msgid "" "This will seemingly restart the machine; but in reality, it loads redboot to " "RAM and restarts it from there. Not doing this step will cause the system to " "hang in the necessary ip_address step that comes next." msgstr "" #. Tag: para #: boot-installer.xml:219 #, no-c-format msgid "" "You will need to hit Ctrl-C again to interrupt the boot. Then: " "\n" "ip_address -l 192.168.2.249 -h " "192.168.2.4\n" "load -v -r -b 0x01800000 -m http /initrd.gz\n" "load -v -r -b 0x01008000 -m http /zImage\n" "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r " "0x01800000\n" " Where 192.168.2.249 " "is the IP address of the installed system and 192.168.2.4 the IP address of the HTTP server containing the kernel and " "ramdisk files." msgstr "" #. Tag: para #: boot-installer.xml:229 #, no-c-format msgid "The installer will now start as usual." msgstr "" #. Tag: title #: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1420 #: boot-installer.xml:1792 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" #. Tag: title #: boot-installer.xml:349 #, no-c-format msgid "Booting from Windows" msgstr "" #. Tag: para #: boot-installer.xml:350 #, no-c-format msgid "To start the installer from Windows, you can either" msgstr "" #. Tag: para #: boot-installer.xml:355 #, no-c-format msgid "" "obtain CD-ROM/DVD-ROM or USB memory " "stick installation media as described in respective or" msgstr "" #. Tag: para #: boot-installer.xml:363 #, no-c-format msgid "" "download a standalone Windows executable, which is available as tools/win32-" "loader/stable/win32-loader.exe on the &debian; mirrors," msgstr "" #. Tag: para #: boot-installer.xml:371 #, no-c-format msgid "" "If you use an installation CD or DVD, a pre-installation program should be " "launched automatically when you insert the disc. In case Windows does not " "start it automatically, or if you are using a USB memory stick, you can run " "it manually by accessing the device and executing setup.exe." msgstr "" #. Tag: para #: boot-installer.xml:379 #, no-c-format msgid "" "After the program has been started, a few preliminary questions will be " "asked and the system will be prepared to reboot into the &debian-gnu; " "installer." msgstr "" #. Tag: title #: boot-installer.xml:389 #, no-c-format msgid "Booting from DOS using loadlin" msgstr "" #. Tag: para #: boot-installer.xml:390 #, no-c-format msgid "" "Boot into DOS (not Windows). To do this, you can for instance boot from a " "recovery or diagnostic disk." msgstr "" #. Tag: para #: boot-installer.xml:395 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-" "ROM drive, e.g. \n" "d:\n" " else make sure you have first prepared your hard " "disk as explained in , and change the " "current drive to it if needed." msgstr "" #. Tag: para #: boot-installer.xml:405 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., " "\n" "cd \\&x86-install-dir;\n" " If you prefer using the graphical installer, " "enter the gtk sub-directory. \n" "cd gtk\n" " Next, execute install.bat. " "The kernel will load and launch the installer system." msgstr "" #. Tag: title #: boot-installer.xml:423 #, no-c-format msgid "" "Booting from Linux using LILO or GRUB" msgstr "" #. Tag: para #: boot-installer.xml:426 #, no-c-format msgid "" "To boot the installer from hard disk, you must first download and place the " "needed files as described in ." msgstr "" #. Tag: para #: boot-installer.xml:431 #, 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/&architecture;/initrd.gz file and its " "corresponding kernel netboot/debian-installer/&architecture;/" "linux. This will allow you to repartition the hard disk from " "which you boot the installer, although you should do so with care." msgstr "" #. Tag: para #: boot-installer.xml:441 #, 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 (or DVD) 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/DVD image, " "without needing the network." msgstr "" #. Tag: para #: boot-installer.xml:450 #, 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 "" #. Tag: screen #: boot-installer.xml:471 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz" msgstr "" #. Tag: para #: boot-installer.xml:471 #, no-c-format msgid "" "For more details, refer to the initrd 4 and " "lilo.conf 5 man pages. Now run lilo and " "reboot." msgstr "" #. Tag: para #: boot-installer.xml:480 #, no-c-format msgid "" "The procedure for GRUB1 is quite similar. Locate your " "menu.lst in the /boot/grub/ " "directory (or sometimes /boot/boot/grub/) and add an " "entry for the installer, for example (assuming /boot is " "on the first partition of the first disk in the system):" msgstr "" #. Tag: screen #: boot-installer.xml:488 #, no-c-format msgid "" "title New Install\n" "root (hd0,0)\n" "kernel /boot/newinstall/vmlinuz\n" "initrd /boot/newinstall/initrd.gz" msgstr "" #. Tag: para #: boot-installer.xml:490 #, no-c-format msgid "" "The procedure for GRUB2 is very similar. The file is " "named grub.cfg instead of menu.lst. An entry for the installer would be for instance for example:" msgstr "" #. Tag: screen #: boot-installer.xml:496 #, no-c-format msgid "" "menuentry 'New Install' {\n" "insmod part_msdos\n" "insmod ext2\n" "set root='(hd0,msdos1)'\n" "linux /boot/newinstall/vmlinuz\n" "initrd /boot/newinstall/initrd.gz\n" "}" msgstr "" #. Tag: para #: boot-installer.xml:498 #, no-c-format msgid "" "From here on, there should be no difference between GRUB " "or LILO." msgstr "" #. Tag: title #: boot-installer.xml:507 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" #. Tag: para #: boot-installer.xml:508 #, no-c-format msgid "" "Let's assume you have prepared everything from and . Now just plug your USB " "stick into some free USB connector and reboot the computer. The system " "should boot up, and unless you have used the flexible way to build the stick " "and not enabled it, you should be presented with the boot: " "prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: title #: boot-installer.xml:522 boot-installer.xml:1699 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para #: boot-installer.xml:523 boot-installer.xml:1707 #, no-c-format msgid "" "You will have already downloaded the floppy images you needed and created " "floppies from the images in ." msgstr "" #. Tag: para #: boot-installer.xml:530 #, 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 "" #. Tag: para #: boot-installer.xml:536 #, 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 " "install root=/dev/hdc at the boot prompt." msgstr "" #. Tag: para #: boot-installer.xml:546 #, 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 "" #. Tag: para #: boot-installer.xml:555 #, 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 "" #. Tag: para #: boot-installer.xml:561 #, 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 ." msgstr "" #. Tag: para #: boot-installer.xml:570 #, 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 "" #. Tag: title #: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250 #: boot-installer.xml:1304 boot-installer.xml:1644 boot-installer.xml:1753 #, no-c-format msgid "Booting with TFTP" msgstr "" #. Tag: para #: boot-installer.xml:604 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title #: boot-installer.xml:610 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para #: boot-installer.xml:611 #, no-c-format msgid "" "It could be that your Network Interface Card or Motherboard provides PXE " "boot functionality. This is a Intel " "re-implementation of TFTP boot. If so, you may be able to configure your " "BIOS to boot from the network." msgstr "" #. Tag: title #: boot-installer.xml:622 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para #: boot-installer.xml:623 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." msgstr "" #. Tag: para #: boot-installer.xml:628 #, no-c-format msgid "" "Let us (&email-debian-boot-list;) know how did you manage it. " "Please refer to this document." msgstr "" #. Tag: title #: boot-installer.xml:636 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para #: boot-installer.xml:637 #, no-c-format msgid "" "The etherboot project " "provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title #: boot-installer.xml:647 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para #: boot-installer.xml:648 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical " "screen showing the &debian; logo and a menu: \n" "Installer boot menu\n" "\n" "Install\n" "Graphical install\n" "Advanced options >\n" "Help\n" "Install with speech synthesis\n" "\n" "Press ENTER to boot or TAB to edit a menu entry\n" " Depending on the installation method you are " "using, the Graphical install option may not be available. Bi-" "arch images additionally have a 64 bit variant for each install option, " "right below it, thus almost doubling the number of options." msgstr "" #. Tag: para #: boot-installer.xml:660 #, no-c-format msgid "" "For a normal installation, select either the Install or the " "Graphical install entry — using either the arrow keys " "on your keyboard or by typing the first (highlighted) letter, the " "Install entry is already selected by default — and " "press &enterkey; to boot the installer." msgstr "" #. Tag: para #: boot-installer.xml:668 #, no-c-format msgid "" "The Advanced options entry gives access to a second menu that " "allows to boot the installer in expert mode, in rescue mode and for " "automated installs." msgstr "" #. Tag: para #: boot-installer.xml:674 #, no-c-format msgid "" "If you wish or need to add any boot parameters for either the installer or " "the kernel, press &tabkey;. This will display the default boot command for " "the selected menu entry and allow to add additional options. The help " "screens (see below) list some common possible options. Press &enterkey; to " "boot the installer with your options; pressing &escapekey; will return you " "to the boot menu and undo any changes you made." msgstr "" #. Tag: para #: boot-installer.xml:683 #, no-c-format msgid "" "Choosing the Help entry will result in the first help screen " "being displayed which gives an overview of all available help screens. To " "return to the boot menu after the help screens have been displayed, type " "'menu' at the boot prompt and press &enterkey;. All help screens have a boot " "prompt at which the boot command can be typed: \n" "Press F1 for the help index, or ENTER to boot:\n" " At this boot prompt you can either just press " "&enterkey; to boot the installer with default options or enter a specific " "boot command and, optionally, boot parameters. A number of boot parameters " "which might be useful can be found on the various help screens. If you do " "add any parameters to the boot command line, be sure to first type the boot " "method (the default is install) and a space before " "the first parameter (e.g., install fb=false)." msgstr "" #. Tag: para #: boot-installer.xml:701 #, no-c-format msgid "" "The keyboard is assumed to have a default American English layout at this " "point. This means that if your keyboard has a different (language-specific) " "layout, the characters that appear on the screen may be different from what " "you'd expect when you type parameters. Wikipedia has a schema of the US keyboard layout which can be used as a " "reference to find the correct keys to use." msgstr "" #. Tag: para #: boot-installer.xml:711 #, no-c-format msgid "" "If you are using a system that has the BIOS configured to use serial " "console, you may not be able to see the initial graphical splash screen upon " "booting the installer; you may even not see the boot menu. The same can " "happen if you are installing the system via a remote management device that " "provides a text interface to the VGA console. Examples of these devices " "include the text console of Compaq's integrated Lights Out " "(iLO) and HP's Integrated Remote Assistant (IRA)." msgstr "" #. Tag: para #: boot-installer.xml:721 #, no-c-format msgid "" "To bypass the graphical boot screen you can either blindly press &escapekey; " "to get a text boot prompt, or (equally blindly) press H " "followed by &enterkey; to select the Help option described " "above. After that your keystrokes should be echoed at the prompt. To prevent " "the installer from using the framebuffer for the rest of the installation, " "you will also want to add vga=normal fb=false to the " "boot prompt, as described in the help text." msgstr "" #. Tag: title #: boot-installer.xml:781 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para #: boot-installer.xml:783 #, 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 "" #. Tag: para #: boot-installer.xml:799 #, 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 "" #. Tag: para #: boot-installer.xml:815 #, 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 "" #. Tag: para #: boot-installer.xml:824 #, 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 "" #. Tag: para #: boot-installer.xml:836 #, 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 "" #. Tag: title #: boot-installer.xml:855 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para #: boot-installer.xml:856 #, 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 "" #. Tag: title #: boot-installer.xml:868 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para #: boot-installer.xml:875 #, 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 "" #. Tag: para #: boot-installer.xml:881 #, 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 "" #. Tag: para #: boot-installer.xml:887 #, 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 "" #. Tag: para #: boot-installer.xml:898 #, 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 "" #. Tag: para #: boot-installer.xml:909 #, 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 "" #. Tag: para #: boot-installer.xml:921 #, 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 "" #. Tag: title #: boot-installer.xml:931 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para #: boot-installer.xml:932 #, 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 "" #. Tag: para #: boot-installer.xml:943 #, 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 "" #. Tag: para #: boot-installer.xml:949 #, 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 fsn:. All other " "recognized partitions will be named blkn:. If you inserted the CD just before entering the " "shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" #. Tag: para #: boot-installer.xml:963 #, 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 fsn." msgstr "" #. Tag: para #: boot-installer.xml:970 #, no-c-format msgid "" "Enter fsn: 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 "" #. Tag: para #: boot-installer.xml:977 #, no-c-format msgid "" "Enter elilo and press ENTER. This will " "start the boot load sequence." msgstr "" #. Tag: para #: boot-installer.xml:984 #, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " "and options." msgstr "" #. Tag: title #: boot-installer.xml:998 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para #: boot-installer.xml:1000 #, 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 "" #. Tag: para #: boot-installer.xml:1011 #, 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 "" #. Tag: para #: boot-installer.xml:1018 #, 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 "" #. Tag: para #: boot-installer.xml:1029 #, 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 "" #. Tag: para #: boot-installer.xml:1038 #, 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 "" #. Tag: title #: boot-installer.xml:1047 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para #: boot-installer.xml:1049 #, 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 "" #. Tag: para #: boot-installer.xml:1061 #, 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 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 "" #. Tag: para #: boot-installer.xml:1079 #, no-c-format msgid "" "Select the kernel version and installation mode most appropriate to your " "needs with the arrow keys." msgstr "" #. Tag: para #: boot-installer.xml:1084 #, 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 "" #. Tag: para #: boot-installer.xml:1091 #, 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 "" #. Tag: para #: boot-installer.xml:1100 boot-installer.xml:1236 #, 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 "" #. Tag: para #: boot-installer.xml:1111 #, no-c-format msgid "" "Booting an IA-64 system from the network is similar to a CD boot. The only " "difference is how the installation kernel is loaded. The EFI Boot Manager " "can load and start programs from a server on the network. Once the " "installation kernel is loaded and starts, the system install will proceed " "through the same steps as the CD install with the exception that the " "packages of the base install will be loaded from the network rather than the " "CD drive." msgstr "" #. Tag: para #: boot-installer.xml:1145 #, no-c-format msgid "" "Network booting an IA-64 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 "" #. Tag: title #: boot-installer.xml:1156 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para #: boot-installer.xml:1157 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 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 "" #. Tag: para #: boot-installer.xml:1167 #, 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 "" #. Tag: screen #: boot-installer.xml:1177 #, 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 "" #. Tag: para #: boot-installer.xml:1177 #, 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 "" #. Tag: title #: boot-installer.xml:1194 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para #: boot-installer.xml:1195 #, 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 "" #. Tag: para #: boot-installer.xml:1227 #, 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 "" #. Tag: title #: boot-installer.xml:1253 boot-installer.xml:1277 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para #: boot-installer.xml:1254 #, 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 "" #. Tag: title #: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:2031 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para #: boot-installer.xml:1278 #, no-c-format msgid "" "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." msgstr "" #. Tag: para #: boot-installer.xml:1283 #, 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 "" #. Tag: screen #: boot-installer.xml:1293 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title #: boot-installer.xml:1307 boot-installer.xml:1344 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para #: boot-installer.xml:1308 #, 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 "" #. Tag: para #: boot-installer.xml:1318 #, 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 "" #. Tag: para #: boot-installer.xml:1327 #, 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." msgstr "" #. Tag: para #: boot-installer.xml:1345 #, 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 "" #. Tag: title #: boot-installer.xml:1360 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para #: boot-installer.xml:1361 #, no-c-format msgid "" "In order to run the installation system a working network setup and ssh " "session is needed on S/390." msgstr "" #. Tag: para #: boot-installer.xml:1366 #, 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 "" #. Tag: title #: boot-installer.xml:1377 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para #: boot-installer.xml:1378 #, 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. It needs to be fixed-width with 80 " "characters per line. A sample parm file parmfile.debian " "is provided with the installation images. If a parameter is too long to fit " "into the 80 characters limit it can simply be continued in the first column " "of the next line. All the lines are concatenated without spaces when being " "passed to the kernel." msgstr "" #. Tag: para #: boot-installer.xml:1395 #, no-c-format msgid "" "If you boot the installer in a logical partition (LPAR) or virtual machine " "(VM) where a lot of devices are visible, you can instruct the kernel to " "restrict the list to a fixed set of devices. This is advised for the " "installer's boot process if a lot of disks are visible, most likely in LPAR " "mode. The cio_ignore option supports both a blacklist (to " "only disallow a few devices) and a whitelist (to only allow specific " "devices): \n" " # blacklist: just ignore the two devices 300 and 301\n" " cio_ignore=0.0.0300-0.0.0301\n" " # whitelist: ignore everything but 1150, FD00, FD01 and FD02\n" " cio_ignore=all,!0.0.1150,!0.0.fd00-0.0.fd02\n" " Please note that all devices numbers' hex digits " "need to be specified in lower case. Furthermore if this boot parameter is " "used all devices need to be listed: this includes at least disks, network " "devices and the console. To be considered during the installer's boot " "process the above option needs to be added to parmfile.debian." msgstr "" #. Tag: para #: boot-installer.xml:1460 #, no-c-format msgid "" "Currently, the only &arch-title; subarchitectures that support CD-ROM " "booting are PReP/CHRP (though not all systems) 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 " "factory default CD/DVD drive." msgstr "" #. Tag: para #: boot-installer.xml:1469 #, no-c-format msgid "" "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open " "Firmware prompt first (see ), then " "type \n" "0 > boot fw/node/sbp-2/disk:,\\install\\yaboot\n" " for an alternative way to boot from the internal " "factory default CD/DVD drive type" msgstr "" #. Tag: screen #: boot-installer.xml:1480 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: para #: boot-installer.xml:1482 #, 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 "" #. Tag: para #: boot-installer.xml:1491 #, no-c-format msgid "" "To boot &debian; CD/DVD on Pegasos II machine, hold Esc key " "immediately after pressing the power-on button, when SmartFirmware prompt " "appears, type" msgstr "" #. Tag: screen #: boot-installer.xml:1497 #, no-c-format msgid "boot cd install/pegasos" msgstr "" #. Tag: title #: boot-installer.xml:1503 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para #: boot-installer.xml:1509 #, 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 "" #. Tag: para #: boot-installer.xml:1515 #, no-c-format msgid "" "To boot the installer from hard disk, you will have already completed " "downloading and placing the needed files as described in ." msgstr "" #. Tag: title #: boot-installer.xml:1535 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para #: boot-installer.xml:1536 #, no-c-format msgid "" "If you set up BootX in , 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 "" #. Tag: title #: boot-installer.xml:1554 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para #: boot-installer.xml:1555 #, 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 . You will now have to boot " "into OpenFirmware (see ). At the " "prompt, type \n" "0 > 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 "" #. Tag: title #: boot-installer.xml:1587 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para #: boot-installer.xml:1588 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para #: boot-installer.xml:1594 #, no-c-format msgid "" "Make sure you have prepared everything from . 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. See ." msgstr "" #. Tag: para #: boot-installer.xml:1603 #, 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 "" #. Tag: para #: boot-installer.xml:1615 #, 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 "" #. Tag: para #: boot-installer.xml:1629 #, 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 "" #. Tag: para #: boot-installer.xml:1635 #, 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 ." msgstr "" #. Tag: para #: boot-installer.xml:1668 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para #: boot-installer.xml:1672 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " "monitor (see ) and use the command " "\n" "0 > boot enet:0\n" " If this doesn't work, you might have to add the " "filename like this: \n" "0 > boot enet:0,yaboot\n" " PReP and CHRP boxes may have different ways of " "addressing the network. On a PReP machine, you should try " "\n" "boot net:server_ipaddr,file,client_ipaddr\n" " On some PReP systems (e.g. Motorola PowerStack " "machines) the command help boot may give a " "description of syntax and available options." msgstr "" #. Tag: para #: boot-installer.xml:1700 #, 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 "" #. Tag: para #: boot-installer.xml:1712 #, 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 "" #. Tag: para #: boot-installer.xml:1718 #, 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 "" #. Tag: para #: boot-installer.xml:1725 #, 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 "" #. Tag: title #: boot-installer.xml:1736 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para #: boot-installer.xml:1737 #, 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 "" #. Tag: para #: boot-installer.xml:1777 #, no-c-format msgid "" "On machines with OpenBoot, simply enter the boot monitor on the machine " "which is being installed (see ). 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. You can pass " "extra boot parameters to &d-i; at the end of the boot " "command." msgstr "" #. Tag: para #: boot-installer.xml:1832 #, 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)." msgstr "" #. Tag: title #: boot-installer.xml:1841 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para #: boot-installer.xml:1842 #, 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 " "Sun NVRAM FAQ for more " "information." msgstr "" #. Tag: title #: boot-installer.xml:1861 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para #: boot-installer.xml:1862 #, no-c-format msgid "" "Some users may need specific support because of e.g. some visual impairment. " "USB braille displays are detected " "automatically (not serial displays connected via a serial-to-USB converter), " "but most other Most accessibility features have to be enabled manually. On machines that support it, the boot menu emits a beep when it is " "ready to receive keystrokes. Some boot parameters can then be appended to enable accessibility features (see also ). Note that " "on most architectures the boot loader interprets your keyboard as a QWERTY " "keyboard." msgstr "" #. Tag: title #: boot-installer.xml:1882 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para #: boot-installer.xml:1883 #, no-c-format msgid "" "USB braille displays should be automatically detected. A textual version of " "the installer will then be automatically selected, and support for the " "braille display will be automatically installed on the target system. You " "can thus just press &enterkey; at the boot menu. Once brltty is started, you can choose a braille table by entering the " "preference menu. Documentation on key bindings for braille devices is " "available on the brltty website." msgstr "" #. Tag: title #: boot-installer.xml:1898 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para #: boot-installer.xml:1899 #, no-c-format msgid "" "Serial braille displays cannot safely be automatically detected (since that " "may damage some of them). You thus need to append the " "brltty=driver,port,table boot parameter to " "tell brltty which driver it should use. " "driver should be replaced by the two-letter " "driver code for your terminal (see the BRLTTY manual). port should be " "replaced by the name of the serial port the display is connected to, " "ttyS0 is the default, ttyUSB0 " "can be typically used when using a serial-to-USB converter. " "table is the name of the braille table to be used " "(see the BRLTTY manual); the " "English table is the default. Note that the table can be changed later by " "entering the preference menu. Documentation on key bindings for braille " "devices is available on the brltty website." msgstr "" #. Tag: title #: boot-installer.xml:1922 boot-installer.xml:2929 #, no-c-format msgid "Software Speech Synthesis" msgstr "" #. Tag: para #: boot-installer.xml:1923 #, no-c-format msgid "" "Support for software speech synthesis is available on all installer images " "which have the graphical installer, i.e. all netinst, CD and DVD images, and " "the netboot gtk variant. It can be activated by selecting it in the boot " "menu by typing s &enterkey;. The textual version of " "the installer will then be automatically selected, and support for software " "speech synthesis will be automatically installed on the target system." msgstr "" #. Tag: para #: boot-installer.xml:1932 #, no-c-format msgid "" "The first question (language) is spoken in english, and the remainder of " "installation is spoken in the selected language (if available in " "espeak)." msgstr "" #. Tag: para #: boot-installer.xml:1938 #, no-c-format msgid "" "The default speech rate is quite slow. To make it faster, press " "CapsLock6. To make it " "slower, press CapsLock5. The default volume should be medium. To make it louder, press " "CapsLock2. To make it " "quieter, press CapsLock1. To get more details on the browsing shortcuts, see the Speakup guide." msgstr "" #. Tag: title #: boot-installer.xml:1957 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para #: boot-installer.xml:1958 #, no-c-format msgid "" "Support for hardware speech synthesis devices is available on all installer " "images which have the graphical installer, i.e. all netinst, CD and DVD " "images, and the netboot gtk variant. You thus need to select a " "Graphical install entry in the boot menu." msgstr "" #. Tag: para #: boot-installer.xml:1965 #, no-c-format msgid "" "Hardware speech synthesis devices cannot be automatically detected. You thus " "need to append the speakup.synth=driver boot parameter to tell speakup which driver it should use. driver " "should be replaced by the driver code for your device (see driver code list). The textual version of the " "installer will then be automatically selected, and support for the speech " "synthesis device will be automatically installed on the target system." msgstr "" #. Tag: title #: boot-installer.xml:1980 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para #: boot-installer.xml:1981 #, no-c-format msgid "" "Some accessibility devices are actual boards that are plugged inside the " "machine and that read text directly from the video memory. To get them to " "work framebuffer support must be disabled by using the vga=normal fb=false boot " "parameter. This will however reduce the number of available languages." msgstr "" #. Tag: para #: boot-installer.xml:1989 #, no-c-format msgid "" "If desired a textual version of the bootloader can be activated before " "adding the boot parameter by typing h &enterkey;." msgstr "" #. Tag: title #: boot-installer.xml:1997 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para #: boot-installer.xml:1998 #, no-c-format msgid "" "For users with low vision, the installer can use a high-contrast theme that " "makes it more readable. To enable it, append the theme=dark boot parameter." msgstr "" #. Tag: title #: boot-installer.xml:2007 #, no-c-format msgid "Preseeding" msgstr "" #. Tag: para #: boot-installer.xml:2008 #, no-c-format msgid "" "Alternatively, &debian; can be installed completely automatically by using " "preseeding. This is documented in ." msgstr "" #. Tag: title #: boot-installer.xml:2016 #, no-c-format msgid "Accessibility of the installed system" msgstr "" #. Tag: para #: boot-installer.xml:2017 #, no-c-format msgid "" "Documentation on accessibility of the installed system is available on the " "Debian Accessibility wiki " "page." msgstr "" #. Tag: para #: boot-installer.xml:2032 #, 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 "" #. Tag: para #: boot-installer.xml:2039 #, 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 "" #. Tag: para #: boot-installer.xml:2046 #, no-c-format msgid "" "Information on many boot parameters can be found in the 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 ." msgstr "" #. Tag: title #: boot-installer.xml:2058 #, no-c-format msgid "Boot console" msgstr "" #. Tag: para #: boot-installer.xml:2060 #, no-c-format msgid "" "If you are booting with a serial console, generally the kernel will " "autodetect this. If you have a videocard (framebuffer) and a keyboard also " "attached to the computer which you wish to boot via serial console, you may " "have to pass the console=device argument to the kernel, where device " "is your serial device, which is usually something like ttyS0." msgstr "" #. Tag: para #: boot-installer.xml:2072 #, no-c-format msgid "" "You may need to specify parameters for the serial port, such as speed and " "parity, for instance console=ttyS0,9600n8; other " "typical speeds may be 57600 or 115200." msgstr "" #. Tag: para #: boot-installer.xml:2078 #, no-c-format msgid "" "In order to ensure the terminal type used by the installer matches your " "terminal emulator, the parameter TERM=type can be added. Note that the installer only supports " "the following terminal types: linux, bterm, ansi, vt102 and " "dumb. The default for serial console in &d-i; is " "vt102. If you are using a virtualization tool which " "does not provide conversion into such terminals types itself, e.g. QEMU/KVM, " "you can start it inside a screen session. That will " "indeed perform translation into the screen terminal type, " "which is very close to vt102." msgstr "" #. Tag: para #: boot-installer.xml:2094 #, 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 "" #. Tag: title #: boot-installer.xml:2106 #, no-c-format msgid "&debian; Installer Parameters" msgstr "" #. Tag: para #: boot-installer.xml:2107 #, 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 "" #. Tag: para #: boot-installer.xml:2120 #, no-c-format msgid "" "A number of parameters have a short form that helps avoid the " "limitations of the kernel command line options and makes entering the " "parameters easier. If a parameter has a short form, it will be listed in " "brackets behind the (normal) long form. Examples in this manual will " "normally use the short form too." msgstr "" #. Tag: term #: boot-installer.xml:2132 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para #: boot-installer.xml:2133 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para #: boot-installer.xml:2137 #, 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 "" #. Tag: para #: boot-installer.xml:2144 #, 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 "" #. Tag: term #: boot-installer.xml:2158 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para #: boot-installer.xml:2159 #, 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. Some specialized types of install media may only offer a " "limited selection of frontends, but the newt and " "text frontends are available on most default install " "media. On architectures that support it, the graphical installer uses the " "gtk frontend." msgstr "" #. Tag: term #: boot-installer.xml:2190 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para #: boot-installer.xml:2191 #, 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 "" #. Tag: userinput #: boot-installer.xml:2200 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para #: boot-installer.xml:2201 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput #: boot-installer.xml:2205 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para #: boot-installer.xml:2206 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput #: boot-installer.xml:2210 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para #: boot-installer.xml:2211 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput #: boot-installer.xml:2215 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para #: boot-installer.xml:2216 #, 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 "" #. Tag: term #: boot-installer.xml:2230 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para #: boot-installer.xml:2231 #, 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 "" #. Tag: para #: boot-installer.xml:2237 #, 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 "" #. Tag: term #: boot-installer.xml:2248 #, no-c-format msgid "log_host" msgstr "" #. Tag: term #: boot-installer.xml:2249 #, no-c-format msgid "log_port" msgstr "" #. Tag: para #: boot-installer.xml:2250 #, no-c-format msgid "" "Causes the installer to send log messages to a remote syslog on the " "specified host and port as well as to a local file. If not specified, the " "port defaults to the standard syslog port 514." msgstr "" #. Tag: term #: boot-installer.xml:2261 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para #: boot-installer.xml:2262 #, no-c-format msgid "" "Can be used to force the installer to a lowmem level higher than the one the " "installer sets by default based on available memory. Possible values are 1 " "and 2. See also ." msgstr "" #. Tag: term #: boot-installer.xml:2272 #, no-c-format msgid "noshell" msgstr "" #. Tag: para #: boot-installer.xml:2273 #, no-c-format msgid "" "Prevents the installer from offering interactive shells on tty2 and tty3. " "Useful for unattended installations where physical security is limited." msgstr "" #. Tag: term #: boot-installer.xml:2282 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para #: boot-installer.xml:2283 #, 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 using the parameter vga=normal fb=false. Problem symptoms are error " "messages about bterm or bogl, a blank screen, or a freeze within a few " "minutes after starting the install." msgstr "" #. Tag: para #: boot-installer.xml:2292 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para #: boot-installer.xml:2296 #, 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 "" #. Tag: term #: boot-installer.xml:2310 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para #: boot-installer.xml:2311 #, 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 " "theme=dark." msgstr "" #. Tag: term #: boot-installer.xml:2323 boot-installer.xml:2556 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "" #. Tag: para #: boot-installer.xml:2324 #, no-c-format msgid "" "By default, the &d-i; automatically probes for network configuration via " "IPv6 autoconfiguration and 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 automatic configuration fails." msgstr "" #. Tag: para #: boot-installer.xml:2331 #, no-c-format msgid "" "If you have an IPv6 router or a DHCP server on your local network, but want " "to avoid them because e.g. they give wrong answers, you can use the " "parameter netcfg/disable_autoconfig=true to prevent " "any automatic configuration of the network (neither v4 nor v6) and to enter " "the information manually." msgstr "" #. Tag: term #: boot-installer.xml:2342 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para #: boot-installer.xml:2343 #, 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 "" #. Tag: term #: boot-installer.xml:2353 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para #: boot-installer.xml:2354 #, no-c-format msgid "" "Set to true to enable support for Serial ATA RAID " "(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note " "that this support is currently experimental. Additional information can be " "found on the &debian; Installer Wiki." msgstr "" #. Tag: term #: boot-installer.xml:2365 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para #: boot-installer.xml:2366 #, no-c-format msgid "" "Specify the url to a preconfiguration file to download and use for " "automating the install. See ." msgstr "" #. Tag: term #: boot-installer.xml:2375 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para #: boot-installer.xml:2376 #, no-c-format msgid "" "Specify the path to a preconfiguration file to load for automating the " "install. See ." msgstr "" #. Tag: term #: boot-installer.xml:2385 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para #: boot-installer.xml:2386 #, no-c-format msgid "" "Set to true to display questions even if they have " "been preseeded. Can be useful for testing or debugging a preconfiguration " "file. Note that this will have no effect on parameters that are passed as " "boot parameters, but for those a special syntax can be used. See for details." msgstr "" #. Tag: term #: boot-installer.xml:2398 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para #: boot-installer.xml:2399 #, no-c-format msgid "" "Delay questions that are normally asked before preseeding is possible until " "after the network is configured. See for " "details about using this to automate installs." msgstr "" #. Tag: term #: boot-installer.xml:2410 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para #: boot-installer.xml:2411 #, no-c-format msgid "" "During installations from serial or management console, the regular virtual " "consoles (VT1 to VT6) are normally disabled in /etc/inittab. Set to true to prevent this." msgstr "" #. Tag: term #: boot-installer.xml:2422 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para #: boot-installer.xml:2423 #, 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 "" #. Tag: para #: boot-installer.xml:2432 #, 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 "" #. Tag: term #: boot-installer.xml:2443 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "" #. Tag: para #: boot-installer.xml:2444 #, no-c-format msgid "" "By setting this option to false, the package " "management system will be configured to not automatically install " "Recommends, both during the installation and for the " "installed system. See also ." msgstr "" #. Tag: para #: boot-installer.xml:2451 #, no-c-format msgid "" "Note that this option allows to have a leaner system, but can also result in " "features being missing that you might normally expect to be available. You " "may have to manually install some of the recommended packages to obtain the " "full functionality you want. This option should therefore only be used by " "very experienced users." msgstr "" #. Tag: term #: boot-installer.xml:2463 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para #: boot-installer.xml:2464 #, no-c-format msgid "" "By default the installer requires that repositories be authenticated using a " "known gpg key. Set to true to disable that " "authentication. Warning: insecure, not recommended." msgstr "" #. Tag: term #: boot-installer.xml:2475 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para #: boot-installer.xml:2476 #, no-c-format msgid "" "This parameter should already be set to a correct value where needed; set it " "only it you see errors during the boot that indicate the ramdisk could not " "be loaded completely. The value is in kB." msgstr "" #. Tag: term #: boot-installer.xml:2486 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para #: boot-installer.xml:2487 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " "performing a normal installation. See ." msgstr "" #. Tag: title #: boot-installer.xml:2500 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para #: boot-installer.xml:2501 #, 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 . Some specific examples are listed below." msgstr "" #. Tag: term #: boot-installer.xml:2513 #, no-c-format msgid "debian-installer/language (language)" msgstr "" #. Tag: term #: boot-installer.xml:2514 #, no-c-format msgid "debian-installer/country (country)" msgstr "" #. Tag: term #: boot-installer.xml:2515 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para #: boot-installer.xml:2516 #, no-c-format msgid "" "There are two ways to specify the language, country and locale to use for " "the installation and the installed system." msgstr "" #. Tag: para #: boot-installer.xml:2521 #, no-c-format msgid "" "The first and easiest is to pass only the parameter locale. Language and country will then be derived from its value. You can " "for example use locale=de_CH to select German as " "language and Switzerland as country (de_CH.UTF-8 will be " "set as default locale for the installed system). Limitation is that not all " "possible combinations of language, country and locale can be achieved this " "way." msgstr "" #. Tag: para #: boot-installer.xml:2530 #, no-c-format msgid "" "The second, more flexible option is to specify language " "and country separately. In this case locale can optionally be added to specify a specific default locale for " "the installed system. Example: language=en country=DE " "locale=en_GB.UTF-8." msgstr "" #. Tag: term #: boot-installer.xml:2542 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para #: boot-installer.xml:2543 #, no-c-format msgid "" "Can be used to automatically load installer components that are not loaded " "by default. Examples of optional components that may be useful are " "openssh-client-udeb (so you can use scp during the installation) and " "ppp-udeb (see )." msgstr "" #. Tag: para #: boot-installer.xml:2557 #, no-c-format msgid "" "Set to true if you want to disable IPv6 " "autoconfiguration and DHCP and instead force static network configuration." msgstr "" #. Tag: term #: boot-installer.xml:2566 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para #: boot-installer.xml:2567 #, no-c-format msgid "" "By default the installer will use the http protocol to download files from " "&debian; mirrors and changing that to ftp is not possible during " "installations at normal priority. By setting this parameter to " "ftp, you can force the installer to use that protocol " "instead. Note that you cannot select an ftp mirror from a list, you have to " "enter the hostname manually." msgstr "" #. Tag: term #: boot-installer.xml:2580 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para #: boot-installer.xml:2581 #, 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 for additional information." msgstr "" #. Tag: title #: boot-installer.xml:2595 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para #: boot-installer.xml:2596 #, 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 "" #. Tag: para #: boot-installer.xml:2609 #, 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 "" #. Tag: para #: boot-installer.xml:2616 #, 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 "" #. Tag: screen #: boot-installer.xml:2626 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title #: boot-installer.xml:2632 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para #: boot-installer.xml:2633 #, no-c-format msgid "" "Sometimes it may be necessary to blacklist a module to prevent it from being " "loaded automatically by the kernel and udev. One reason could be that a " "particular module causes problems with your hardware. The kernel also " "sometimes lists two different drivers for the same device. This can cause " "the device to not work correctly if the drivers conflict or if the wrong " "driver is loaded first." msgstr "" #. Tag: para #: boot-installer.xml:2642 #, no-c-format msgid "" "You can blacklist a module using the following syntax: " "module_name.blacklist=yes. " "This will cause the module to be blacklisted in /etc/modprobe.d/" "blacklist.local both during the installation and for the " "installed system." msgstr "" #. Tag: para #: boot-installer.xml:2650 #, no-c-format msgid "" "Note that a module may still be loaded by the installation system itself. " "You can prevent that from happening by running the installation in expert " "mode and unselecting the module from the list of modules displayed during " "the hardware detection phases." msgstr "" #. Tag: title #: boot-installer.xml:2666 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title #: boot-installer.xml:2671 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para #: boot-installer.xml:2672 #, 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 — even after booting " "successfully from CD-ROM — fail to recognize the CD-ROM or return " "errors while reading from it during the installation." msgstr "" #. Tag: para #: boot-installer.xml:2679 #, no-c-format msgid "" "There are many different possible causes for these problems. We can only " "list some common issues and provide general suggestions on how to deal with " "them. The rest is up to you." msgstr "" #. Tag: para #: boot-installer.xml:2685 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para #: boot-installer.xml:2690 #, no-c-format msgid "" "If the CD-ROM does not boot, check that it was inserted correctly and that " "it is not dirty." msgstr "" #. Tag: para #: boot-installer.xml:2696 #, 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 issues with very old CD-ROM " "drives are known to be resolved in this way." msgstr "" #. Tag: para #: boot-installer.xml:2706 #, 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 "" #. Tag: para #: boot-installer.xml:2712 #, 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 "" #. Tag: title #: boot-installer.xml:2720 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para #: boot-installer.xml:2723 #, 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 "" #. Tag: para #: boot-installer.xml:2740 #, no-c-format msgid "" "Some very old CD-ROM drives do not work correctly if direct memory " "access (DMA) is enabled for them." msgstr "" #. Tag: title #: boot-installer.xml:2751 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para #: boot-installer.xml:2752 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para #: boot-installer.xml:2757 #, no-c-format msgid "" "Check that your BIOS actually supports booting from CD-ROM (only an issue " "for very old systems) and that CD booting is enabled in the BIOS." msgstr "" #. Tag: para #: boot-installer.xml:2764 #, 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 "" #. Tag: screen #: boot-installer.xml:2777 #, 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 "" #. Tag: para #: boot-installer.xml:2782 #, 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 " "&arch-kernel; 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 "" #. Tag: para #: boot-installer.xml:2794 #, 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 "" #. Tag: para #: boot-installer.xml:2801 #, 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 controller, " "you can try loading it manually using modprobe." msgstr "" #. Tag: para #: boot-installer.xml:2815 #, 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/cdrom." msgstr "" #. Tag: para #: boot-installer.xml:2823 #, 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 "" #. Tag: para #: boot-installer.xml:2833 #, no-c-format msgid "" "Check if DMA is currently enabled: \n" "$ cd /proc/ide/hdc\n" "$ grep using_dma settings\n" "using_dma 1 0 1 rw\n" " A 1 in the first column after " "using_dma 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 "" #. Tag: para #: boot-installer.xml:2848 #, 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 "" #. Tag: title #: boot-installer.xml:2863 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para #: boot-installer.xml:2865 #, no-c-format msgid "" "The biggest problem for people using floppy disks to install &debian; seems " "to be floppy disk reliability." msgstr "" #. Tag: para #: boot-installer.xml:2870 #, 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 "" #. Tag: para #: boot-installer.xml:2879 #, 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 "" #. Tag: para #: boot-installer.xml:2888 #, 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 "" #. Tag: para #: boot-installer.xml:2894 #, 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 "" #. Tag: para #: boot-installer.xml:2900 #, 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 "" #. Tag: title #: boot-installer.xml:2909 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para #: boot-installer.xml:2911 #, 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 " "." msgstr "" #. Tag: para #: boot-installer.xml:2920 #, no-c-format msgid "" "In some cases, malfunctions can be caused by missing device firmware (see " " and )." msgstr "" #. Tag: para #: boot-installer.xml:2931 #, no-c-format msgid "" "If software speech synthesis does not work, there is most probably an issue " "with your sound board, usually because either the driver for it is not " "included in the installer, or because it has unusual mixer level names which " "are set to muted by default. You should thus submit a bug report which " "includes the output of the following commands, run on the same machine from " "a Linux system which is known to have sound working (e.g., a live CD)." msgstr "" #. Tag: userinput #: boot-installer.xml:2942 #, no-c-format msgid "dmesg" msgstr "" #. Tag: userinput #: boot-installer.xml:2944 #, no-c-format msgid "lspci" msgstr "" #. Tag: userinput #: boot-installer.xml:2946 #, no-c-format msgid "lsmod" msgstr "" #. Tag: userinput #: boot-installer.xml:2948 #, no-c-format msgid "amixer" msgstr "" #. Tag: title #: boot-installer.xml:2956 boot-installer.xml:3067 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para #: boot-installer.xml:2957 #, 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 "" #. Tag: para #: boot-installer.xml:3008 #, 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 to disable the framebuffer console. Only a reduced set of " "languages will be available during the installation due to limited console " "features. See for details." msgstr "" #. Tag: title #: boot-installer.xml:3022 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para #: boot-installer.xml:3023 #, no-c-format msgid "" "Some very old 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 "" #. Tag: para #: boot-installer.xml:3033 #, 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 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 "" #. Tag: para #: boot-installer.xml:3068 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title #: boot-installer.xml:3074 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para #: boot-installer.xml:3075 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, " "for example an ATI card and a Sun Creator 3D. In some cases, this may result " "in the video output getting misdirected soon after the system boots. In " "typical cases, the display will only show: \n" "Remapping the kernel... done\n" "Booting Linux...\n" " To work around this, you can either pull out one " "of the video cards, or disable the one not used during the OpenProm boot " "phase using a kernel parameter. For example, to disable an ATI card, you " "should boot the installer with video=atyfb:off." msgstr "" #. Tag: para #: boot-installer.xml:3089 #, no-c-format msgid "" "Note that you may also have to manually add this parameter to the silo " "configuration (edit /target/etc/silo.conf before " "rebooting) and, if you installed X11, modify the video driver in /" "etc/X11/xorg.conf." msgstr "" #. Tag: title #: boot-installer.xml:3100 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para #: boot-installer.xml:3101 #, no-c-format msgid "" "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if " "they do boot, there may be inexplicable failures during the installation. " "Most problems have been reported with SunBlade systems." msgstr "" #. Tag: para #: boot-installer.xml:3107 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title #: boot-installer.xml:3116 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para #: boot-installer.xml:3118 #, 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 )." msgstr "" #. Tag: title #: boot-installer.xml:3143 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para #: boot-installer.xml:3144 #, no-c-format msgid "" "If you get through the initial boot phase but cannot complete the install, " "the menu option Save debug logs may be helpful. " "It lets you store system error logs and configuration information from the " "installer to a floppy, or download them using 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 "" #. Tag: para #: boot-installer.xml:3155 #, 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 "" #. Tag: title #: boot-installer.xml:3166 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para #: boot-installer.xml:3167 #, 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 "" #. Tag: para #: boot-installer.xml:3174 #, no-c-format msgid "" "Note that your installation report will be published in the Debian Bug " "Tracking System (BTS) and forwarded to a public mailing list. Make sure that " "you use an e-mail address that you do not mind being made public." msgstr "" #. Tag: para #: boot-installer.xml:3180 #, 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 (aptitude " "install installation-report reportbug), configure " "reportbug as explained in , and run the command reportbug installation-reports." msgstr "" #. Tag: para #: boot-installer.xml:3190 #, no-c-format msgid "" "Alternatively you can 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: <How did you boot the installer? CD? floppy? network?>\n" "Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\n" "\n" "Output of lspci -knn (or lspci -nn):\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" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\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 ""