From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 7 Oct 2005 19:51:38 +0000 Subject: move manual to top-level directory, split out of debian-installer package --- fi/boot-installer/alpha.xml | 441 +++++++++++++++++++++++++++++++++ fi/boot-installer/arm.xml | 113 +++++++++ fi/boot-installer/boot-installer.xml | 32 +++ fi/boot-installer/hppa.xml | 12 + fi/boot-installer/i386.xml | 379 ++++++++++++++++++++++++++++ fi/boot-installer/ia64.xml | 464 +++++++++++++++++++++++++++++++++++ fi/boot-installer/intro-cd.xml | 35 +++ fi/boot-installer/intro-hd.xml | 16 ++ fi/boot-installer/intro-net.xml | 19 ++ fi/boot-installer/m68k.xml | 371 ++++++++++++++++++++++++++++ fi/boot-installer/mips.xml | 100 ++++++++ fi/boot-installer/mipsel.xml | 12 + fi/boot-installer/parameters.xml | 351 ++++++++++++++++++++++++++ fi/boot-installer/powerpc.xml | 247 +++++++++++++++++++ fi/boot-installer/s390.xml | 30 +++ fi/boot-installer/sparc.xml | 89 +++++++ fi/boot-installer/trouble.xml | 274 +++++++++++++++++++++ 17 files changed, 2985 insertions(+) create mode 100644 fi/boot-installer/alpha.xml create mode 100644 fi/boot-installer/arm.xml create mode 100644 fi/boot-installer/boot-installer.xml create mode 100644 fi/boot-installer/hppa.xml create mode 100644 fi/boot-installer/i386.xml create mode 100644 fi/boot-installer/ia64.xml create mode 100644 fi/boot-installer/intro-cd.xml create mode 100644 fi/boot-installer/intro-hd.xml create mode 100644 fi/boot-installer/intro-net.xml create mode 100644 fi/boot-installer/m68k.xml create mode 100644 fi/boot-installer/mips.xml create mode 100644 fi/boot-installer/mipsel.xml create mode 100644 fi/boot-installer/parameters.xml create mode 100644 fi/boot-installer/powerpc.xml create mode 100644 fi/boot-installer/s390.xml create mode 100644 fi/boot-installer/sparc.xml create mode 100644 fi/boot-installer/trouble.xml (limited to 'fi/boot-installer') diff --git a/fi/boot-installer/alpha.xml b/fi/boot-installer/alpha.xml new file mode 100644 index 000000000..d43770c8b --- /dev/null +++ b/fi/boot-installer/alpha.xml @@ -0,0 +1,441 @@ + + + + + Alpha Console Firmware + + +Console firmware is stored in a flash ROM and started when an Alpha +system is powered up or reset. There are two different console +specifications used on Alpha systems, and hence two classes of console +firmware available: + + + + + + + SRM console, based on the Alpha Console Subsystem + specification, which provides an operating environment for OpenVMS, Tru64 + UNIX, and Linux operating systems. + + + + + ARC, AlphaBIOS, or ARCSBIOS console, based on the + Advanced RISC Computing (ARC) specification, which provides an operating + environment for Windows NT. + + + + + + +From the user's perspective, the most important difference between SRM +and ARC is that the choice of console constrains the possible +disk-partitioning scheme for the hard disk which you wish to boot off +of. + + + +ARC requires that you use an MS-DOS partition table (as created by +cfdisk) for the boot disk. Therefore MS-DOS partition +tables are the native partition format when booting from +ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may +prefer to partition your disks from the firmware menus before +installing Linux. + + + +Conversely, SRM is incompatible + + +Specifically, the bootsector format required by the Console Subsystem +Specification conflicts with the placement of the DOS partition table. + + + with MS-DOS partition tables. Since Tru64 Unix uses the BSD +disklabel format, this is the native partition format for +SRM installations. + + + +GNU/Linux is the only operating system on Alpha that can be booted from +both console types, but &debian; &release; only supports booting on +SRM-based systems. If you have an Alpha for which no version of SRM is +available, if you will be dual-booting the system with Windows NT, or if +your boot device requires ARC console support for BIOS initialization, +you will not be able to use the &debian; &release; installer. You can +still run &debian; &release; on such systems by using other install +media; for instance, you can install Debian woody with MILO and upgrade. + + + +Because MILO is not available for any of the Alpha +systems currently in production (as of February 2000), and because it +is no longer necessary to buy an OpenVMS or Tru64 Unix license to have +SRM firmware on your older Alpha, it is recommended that you use SRM +when possible. + + + +The following table summarizes available and supported system +type/console combinations (see for the +system type names). The word ARC below denotes any of the +ARC-compliant consoles. + + + + + + + System Type + Console Type Supported + + + + + + alcor + ARC or SRM + + avanti + ARC or SRM + + book1 + SRM only + + cabriolet + ARC or SRM + + dp264 + SRM only + + eb164 + ARC or SRM + + eb64p + ARC or SRM + + eb66 + ARC or SRM + + eb66p + ARC or SRM + + jensen + SRM only + + lx164 + ARC or SRM + + miata + ARC or SRM + + mikasa + ARC or SRM + + mikasa-p + SRM only + + nautilus + ARC (see motherboard manual) or SRM + + noname + ARC or SRM + + noritake + SRM only + + noritake-p + SRM only + + pc164 + ARC or SRM + + rawhide + SRM only + + ruffian + ARC only + + sable + SRM only + + sable-g + SRM only + + sx164 + ARC or SRM + + takara + ARC or SRM + + xl + ARC only + + xlt + ARC only + + + + + + + + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. For the SRM +console, aboot, a small, platform-independent +bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on +aboot. + + + +The following paragraphs are from the woody install manual, and are +included here for reference; they may be useful to someone at a later +date when Debian supports MILO-based installs again. + + + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. There are two +mainstream Linux loaders: MILO and aboot. + + + +MILO is itself a console, which replaces ARC or SRM in +memory. MILO can be booted from both ARC and SRM and is +the only way to bootstrap Linux from the ARC console. +MILO is platform-specific (a different MILO +is needed for each system type) and exist only for those systems, for +which ARC support is shown in the table above. See also the +(unfortunately outdated) MILO HOWTO. + + + +aboot is a small, platform-independent bootloader, which +runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on +aboot. + + + +Thus, three scenarios are generally possible, depending on the +system's console firmware and whether or not MILO is +available: + + +SRM -> aboot +SRM -> MILO +ARC -> MILO + + +Because MILO is not available for any of the Alpha +systems currently in production (as of February 2000), and because it +is no longer necessary to buy an OpenVMS or Tru64 Unix license to have +SRM firmware on your older Alpha, it is recommended that you use SRM and +aboot on new installations of GNU/Linux, unless you wish +to dual-boot with Windows NT. + + + +The majority of AlphaServers and all current server and workstation +products contain both SRM and AlphaBIOS in their firmware. For +half-flash machines such as the various evaluation boards, +it is possible to switch from one version to another by reflashing the +firmware. Also, once SRM is installed, it is possible to run +ARC/AlphaBIOS from a floppy disk (using the arc +command). For the reasons mentioned above, we recommend switching to +SRM before installing &debian;. + + + +As on other architectures, you should install the newest available +revision of the firmware + + +Except on Jensen, where Linux is not supported on firmware versions +newer than 1.7 — see +for more information. + + + before installing &debian;. +For Alpha, firmware updates can be obtained from +Alpha Firmware Updates. + + + + + + Booting with TFTP + + +In SRM, Ethernet interfaces are named with the ewa +prefix, and will be listed in the output of the show dev command, +like this (edited slightly): + + +>>> show dev +ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65 +ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54 +ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0 + + +You first need to set the boot protocol: + + +>>> set ewa0_protocol bootp + + +Then check the medium type is correct: + + +>>> set ewa0_mode mode + + +You can get a listing of valid modes with >>>set ewa0_mode. + + + +Then, to boot from the first Ethernet interface, you would type: + + +>>> boot ewa0 -flags "" + + +This will boot using the default kernel parameters as included in the +netboot image. + + + +If you wish to use a serial console, you must +pass the console= parameter to the kernel. +This can be done using the -flags argument to +the SRM boot command. The serial ports are +named the same as their corresponding files in +/dev. Also, when specifying additional kernel +parameters, you must repeat certain default options that are needed by +the &d-i; images. For example, to boot from ewa0 +and use a console on the first serial port, you would type: + + +>>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0" + + + + + + Booting from CD-ROM with the SRM Console + + +Type + + +>>> boot xxxx -flags 0 + + +where xxxx is your CD-ROM drive in SRM notation. + + + + + + Booting from CD-ROM with the ARC or AlphaBIOS Console + + +To boot a CD-ROM from the ARC console, find your sub-architecture code +name (see ), then enter +\milo\linload.exe as the boot loader and +\milo\subarch (where +subarch is the proper subarchitecture name) +as the OS Path in the `OS Selection Setup' menu. Ruffians make an +exception: You need to use \milo\ldmilo.exe as +boot loader. + + + + + + + Booting from Floppies with the SRM Console + + +At the SRM prompt (>>>), issue the following +command: + + +>>> boot dva0 -flags 0 + + +possibly replacing dva0 with the actual device +name. Usually, dva0 is the floppy; type + + +>>> show dev + + +to see the list of devices (e.g., if you want to boot from a CD). +Note that if you are booting via MILO, -flags argument +is ignored, so you can just type boot dva0. +If everything works OK, you will eventually see the Linux kernel boot. + + + +If you want to specify kernel parameters when booting via +aboot, use the following command: + + +>>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments" + + +(typed on one line), substituting, if necessary, the actual SRM boot +device name for dva0, the Linux boot device name for +fd0, and the desired kernel parameters for +arguments. + + + +If you want to specify kernel parameters when booting via +MILO, you will have to interrupt bootstrap once you get +into MILO. See . + + + + + + Booting from Floppies with the ARC or AlphaBIOS Console + + + +In the OS Selection menu, set linload.exe as the boot +loader, and milo as the OS Path. Bootstrap using the +newly created entry. + + + + + Booting with MILO + + +MILO contained on the bootstrap media is configured to proceed straight +to Linux automatically. Should you wish to intervene, all you need is to +press space during MILO countdown. + + + +If you want to specify all the bits explicitly (for example, to supply +additional parameters), you can use a command like this: + + +MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 + + +If you are booting from something other than a floppy, substitute +fd0 in the above example with the appropriate device name +in Linux notation. The help command would give you a brief +MILO command reference. + + + diff --git a/fi/boot-installer/arm.xml b/fi/boot-installer/arm.xml new file mode 100644 index 000000000..505a05323 --- /dev/null +++ b/fi/boot-installer/arm.xml @@ -0,0 +1,113 @@ + + + + Booting from TFTP + +&boot-installer-intro-net.xml; + + Booting from TFTP on NetWinder + + + +NetWinders have two network interfaces: The 10Mbps NE2000-compatible +card is eth0 and the 100Mbps Tulip card is +eth1. + + + +You need NeTTrom 2.2.1 or later to boot the +installation system. NeTTrom 2.3.3 is recommended: get these files +from +: + + + +nettrom-2.3-3.armv4l.rpm + + + + +nettrom-2.3.3.bin + + + + +nettrom-2.3.3.bin.md5sum + + + + + + +After rebooting and interrupting the boot process during the countdown, you +must first configure the network either with a static address: + + + NeTTrom command-> setenv eth0_ip 192.168.0.10/24 + + +where 24 is the number of set bits in the netmask, or a dynamic address: + + + NeTTrom command-> boot diskless + + +You may also need to configure the route1 +settings if the TFTP +server is not on the local subnet. The rest of the config is pretty +standard (the save-all step is optional): + + + NeTTrom command-> setenv kerntftpserver 192.168.0.1 + NeTTrom command-> setenv kerntftpfile boot.img + NeTTrom command-> save-all + NeTTrom command-> setenv netconfig_eth0 flash + NeTTrom command-> setenv kernconfig tftp + NeTTrom command-> setenv rootdev /dev/ram + NeTTrom command-> setenv cmdappend root=/dev/ram + + +Only the last four of these interfere with normal disk booting, so it is +safe to issue save-all right before them, which will +store the network settings in case you need to boot from the network +again. + +If you want to use the serial console to install your NetWinder, you also +need the following setting: + + + NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200 + + +Use the printenv command to review your +environment settings. Finally, if your cmdappend +NeTTrom variable has the option, you must +remove it so the downloaded kernel can boot with its attached ramdisk. + + + + + Booting from TFTP on CATS + + + +On CATS machines, use boot de0: or similar at the +Cyclone prompt. + + + + + + + + Booting from CD-ROM + +&boot-installer-intro-cd.xml; + + + +To boot a CD-ROM from the Cyclone console prompt, use the command +boot cd0:cats.bin + + + diff --git a/fi/boot-installer/boot-installer.xml b/fi/boot-installer/boot-installer.xml new file mode 100644 index 000000000..ab8ab9784 --- /dev/null +++ b/fi/boot-installer/boot-installer.xml @@ -0,0 +1,32 @@ + + + +Booting the Installation System + + + + + Booting the Installer on &arch-title; + + + + + +&boot-installer-alpha.xml; +&boot-installer-arm.xml; + +&boot-installer-i386.xml; +&boot-installer-ia64.xml; +&boot-installer-m68k.xml; +&boot-installer-mips.xml; + +&boot-installer-s390.xml; +&boot-installer-powerpc.xml; +&boot-installer-sparc.xml; + + + +&boot-installer-parameters.xml; +&boot-installer-trouble.xml; + + diff --git a/fi/boot-installer/hppa.xml b/fi/boot-installer/hppa.xml new file mode 100644 index 000000000..619d3eaf1 --- /dev/null +++ b/fi/boot-installer/hppa.xml @@ -0,0 +1,12 @@ + + + + + + + + + + + diff --git a/fi/boot-installer/i386.xml b/fi/boot-installer/i386.xml new file mode 100644 index 000000000..1e05a3ee8 --- /dev/null +++ b/fi/boot-installer/i386.xml @@ -0,0 +1,379 @@ + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + + + + + + + + + Booting from Linux Using <command>LILO</command> or + <command>GRUB</command> + + +To boot the installer from hard disk, you must first download +and place the needed files as described in . + + + +If you intend to use the hard drive only for booting and then +download everything over the network, you should download the +netboot/debian-installer/i386/initrd.gz file and its +corresponding kernel. This will allow you to repartition the hard disk +from which you boot the installer, although you should do so with care. + + + +Alternatively, if you intend to keep an existing partition on the hard +drive unchanged during the install, you can download the +hd-media/initrd.gz file and its kernel, as well as +copy a CD iso to the drive (make sure the file is named ending in +.iso). The installer can then boot from the drive +and install from the CD image, without needing the network. + + + +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: + + + + +image=/boot/newinstall/vmlinuz + label=newinstall + initrd=/boot/newinstall/initrd.gz + root=/dev/ram0 + append="devfs=mount,dall ramdisk_size=12000" + + +For more details, refer to the +initrd +4 and +lilo.conf +5 man pages. Now run +lilo and reboot. + + + +The procedure for GRUB is quite similar. Locate your +menu.lst in the /boot/grub/ +directory (sometimes in the /boot/boot/grub/), +add the following lines: + + +title New Install +kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000 +initrd (hd0,0)/boot/newinstall/initrd.gz + + +and reboot. If the boot fails, you can try adding +devfs=mount,dall to the kernel line. + + + + +Note that the value of the ramdisk_size may need to be +adjusted for the size of the initrd image. +From here on, there should be no difference between GRUB +or LILO. + + + + + + Booting from USB Memory Stick + + +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 you should be presented with +the boot: prompt. Here you can enter optional boot +arguments, or just hit &enterkey;. + + + +In case your computer doesn't support booting from USB memory devices, +you can still use a single floppy to do the initial boot and then +switch to USB. Boot your system as described in ; +the kernel on the boot floppy should detect your USB stick automatically. +When it asks for the root floppy, simply press &enterkey;. You should see +&d-i; starting. + + + + + + Booting from Floppies + + +You will have already downloaded the floppy images you needed and +created floppies from the images in . + + + + +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. + + + +For installing from an LS-120 drive (ATAPI version) with a set of +floppies, you need to specify the virtual location for the floppy +device. This is done with the root= boot +argument, giving the device that the ide-floppy driver maps the device +to. For example, if your LS-120 drive is connected as the first IDE +device (master) on the second cable, you enter +linux root=/dev/hdc at the boot prompt. +Installation from LS-120 is only supported by 2.4 and later kernels. + + + +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. + + + +The floppy disk will be accessed, and you should then see a screen +that introduces the boot floppy and ends with the boot: +prompt. + + + +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 . + + + +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. + + + + + Booting with TFTP + +&boot-installer-intro-net.xml; + + + +There are various ways to do a TFTP boot on i386. + + + + NIC or Motherboard that support PXE + + +It could be that your Network Interface Card or Motherboard provides +PXE boot functionality. +This is a Intel re-implemention +of TFTP boot. If so you may be able to configure your BIOS to boot from the +network. + + + + + NIC with Network BootROM + + +It could be that your Network Interface Card provides +TFTP boot functionality. + + + +Let us (&email-debian-boot-list;) know how did you manage it. +Please refer to this document. + + + + + Etherboot + + +The etherboot project +provides bootdiskettes and even bootroms that do a TFTPboot. + + + + + + The Boot Prompt + + +When the installer boots, you should be presented with a friendly graphical +screen showing the Debian logo and the boot prompt: + + +Press F1 for help, or ENTER to boot: + + +At the boot prompt +you can either just press &enterkey; to boot the installer with +default options or enter a specific boot method and, optionally, boot +parameters. + + + +Information on available boot methods and on boot parameters which might +be useful can be found by pressing F2 through +F7F8. If you add any parameters to +the boot command line, be sure to type the boot method (the default is +linux) and a space before the first parameter (e.g., +linux debconf/priority=medium). + + + +If you are installing the system via a remote management device that +provides a text interface to the VGA console, you may not be able to +see the initial graphical splash screen upon booting the installer; +you may even not see the boot prompt. Examples of these devices include +the text console of Compaq's integrated Lights Out (iLO) +and HP's Integrated Remote Assistant (IRA). +You can blindly press F1 + + + +In some cases these devices will require special escape sequences to +enact this keypress, for example the IRA uses Ctrl +F , 1. + + + + to bypass this screen and view the help text. Once you are +past the splash screen and at the help text your keystrokes will be echoed +at the prompt as expected. To prevent the installer from using the +framebuffer for the rest of the installation, you will also want to add +debian-installer/framebuffer=false to the boot prompt, +as described in the help text. + + + + + diff --git a/fi/boot-installer/ia64.xml b/fi/boot-installer/ia64.xml new file mode 100644 index 000000000..9afc8b61e --- /dev/null +++ b/fi/boot-installer/ia64.xml @@ -0,0 +1,464 @@ + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + + CD Contents + + + +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. + + + + + +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. + + + +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. + + + +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. + + + +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. + + + + + IMPORTANT + +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. + + + + + Option 1: Booting from the Boot Option Maintenance Menu + + + + + + + +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. + + + +Select Boot Maintenance Menu from the menu +with the arrow keys and press ENTER. +This will display a new menu. + + + +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. + + + +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. + + + +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. + + + + + + +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. + + + + + + Option 2: Booting from the EFI Shell + + +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: + + + + + + +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. + + + +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. + + + + +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. + + + +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. + + + +Enter elilo and press ENTER. +This will start the boot load sequence. + + + + + + +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. + + + + + + + Installing using a Serial Console + + + +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. + + + +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. + + + +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. + + + + +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. + + + +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. + + + + + Selecting the Boot Kernel and Options + + + +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. + + + +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: + + + + + + +Select the kernel version and installation mode most +appropriate to your needs with the arrow keys. + + + +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. + + + +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. + + + + + + +Proceed to the next chapter to continue the installation where you will +set up the language locale, network, and disk partitions. + + + + + + Booting with TFTP + + +Booting an IA64 system from the network is similar to a CD boot. +The only difference is how the installation kernel is loaded. +The EFI Boot Manager can load and start programs from a server on +the network. +Once the installation kernel is loaded and starts, the system install +will proceed thru the same steps as the CD install with the exception +that the packages of the base install will be loaded from the network +rather than the CD drive. + + + +&boot-installer-intro-net.xml; + + + +Network booting an ia64 system requires two architecture-specific actions. +On the boot server, DHCP and TFTP must be configured to deliver +elilo. +On the client a new boot option must be defined in the EFI boot manager +to enable loading over a network. + + + + + Configuring the Server + + +A suitable TFTP entry for network booting an ia64 system looks something +like this: + + +host mcmuffin { + hardware ethernet 00:30:6e:1e:0e:83; + fixed-address 10.0.0.21; + filename "debian-installer/ia64/elilo.efi"; +} + + +Note that the goal is to get elilo.efi running on +the client. + + + +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. + + + + +# cd /var/lib/tftp +# tar xvfz /home/user/netboot.tar.gz +./ +./debian-installer/ +./debian-installer/ia64/ +[...] + + +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. + + + + + + Configuring the Client + + +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. + + + +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. + + + +Proceed to the next chapter to continue the installation where +you will set up the language locale, network, and the disk partitions. + + + + diff --git a/fi/boot-installer/intro-cd.xml b/fi/boot-installer/intro-cd.xml new file mode 100644 index 000000000..8a3e1b20a --- /dev/null +++ b/fi/boot-installer/intro-cd.xml @@ -0,0 +1,35 @@ + + + + + +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. + + + +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. + + + +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. + + + +If you have problems booting, see . + + diff --git a/fi/boot-installer/intro-hd.xml b/fi/boot-installer/intro-hd.xml new file mode 100644 index 000000000..569a87fb0 --- /dev/null +++ b/fi/boot-installer/intro-hd.xml @@ -0,0 +1,16 @@ + + + + + +Booting from an existing operating system is often a convenient +option; for some systems it is the only supported method of +installation. + + + +To boot the installer from hard disk, you will have already completed +downloading and placing the needed files in +. + + diff --git a/fi/boot-installer/intro-net.xml b/fi/boot-installer/intro-net.xml new file mode 100644 index 000000000..79189195c --- /dev/null +++ b/fi/boot-installer/intro-net.xml @@ -0,0 +1,19 @@ + + + + + +Booting from the network requires that you have a network +connection and a TFTP network boot server (DHCP, RARP, or BOOTP). + + + +Older systems such as the 715 might require the use of an RBOOT server +instead of a BOOTP server. + + + +The installation method to support network booting is described in . + + \ No newline at end of file diff --git a/fi/boot-installer/m68k.xml b/fi/boot-installer/m68k.xml new file mode 100644 index 000000000..1dc18c6ec --- /dev/null +++ b/fi/boot-installer/m68k.xml @@ -0,0 +1,371 @@ + + + + Choosing an Installation Method + + + +Some &arch-title; subarchs have the option of booting using either a +2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x +linux kernel. The installer should also require less memory when using +a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk +and 2.4.x uses tmpfs. + + + +If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; +kernel parameter. + + + + + +Also, if you are using a 2.2.x linux kernel, then you must make sure you +are using a ramdisk built to accommodate it, see the +MANIFEST. +In general, this means you need to use the initrd22.gz ramdisk from the respective +directory. + + + +Make sure root=/dev/ram is one of your kernel +parameters. + + + +If you're having trouble, check +cts's &arch-title; debian-installer FAQ. + + + + + + + + + + + + + + Amiga + + +The only method of installation available to amiga is the hard drive +(see ). +In other words the cdrom is not bootable. + + + +Amiga does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +debian-installer/framebuffer=false. + + + + + Atari + + +The installer for atari may be started from either the hard +drive (see ) or from floppies +(see ). +In other words the cdrom is not bootable. + + + +Atari does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +debian-installer/framebuffer=false. + + + + + BVME6000 + + +The installer for BVME6000 may be started from a cdrom +(see ), floppies +(see ), or the net +(see ). + + + + + Macintosh + + +The only method of installation available to mac is from +the hard drive (see ). +In other words the cdrom is not bootable. +Macs do not have a working 2.4.x kernel. + + + +If your hardware uses a 53c9x-based scsi bus, then you may need to +include the kernel parameter mac53c9x=1,0. +Hardware with two such scsi buses, such as the Quadra 950, will need +mac53c9x=2,0 instead. Alternatively, the +parameter can be specified as mac53c9x=-1,0 +which will leave autodetection on, but which will disable SCSI +disconnects. Note that specifying this parameter is only necessary +if you have more than one hard disk; otherwise, the system will run +faster if you do not specify it. + + + + + MVME147 and MVME16x + + +The installer for MVME147 and MVME16x may be started from +either floppies (see ) +or the net (see ). +In other words the cdrom is not bootable. + + + + + Q40/Q60 + + +The only method of installation available to Q40/Q60 is +from the hard drive (see ). +In other words the cdrom is not bootable. + + + + + + + Booting from a Hard Disk + +&boot-installer-intro-hd.xml; + + + +At least six different ramdisks may be used to boot from the hard +drive, three different types each with and without support for a +2.2.x linux kernel (see +MANIFEST +for details). + + + +The three different types of ramdisks are cdrom, +hd-media, and nativehd. These +ramdisks differ only in their source for installation packages. +The cdrom ramdisk uses a cdrom to get +debian-installer packages. The hd-media ramdisk +uses an iso image file of a cdrom currently residing on a hard disk. +Finally, the nativehd ramdisk uses the net to +install packages. + + + + + + + + + + + + Booting from AmigaOS + + +In the Workbench, start the Linux installation +process by double-clicking on the StartInstall icon +in the debian directory. + + + +You may have to press the &enterkey; key twice after the Amiga +installer program has output some debugging information into a window. +After this, the screen will go grey, there will be a few seconds' +delay. Next, a black screen with white text should come up, displaying +all kinds of kernel debugging information. These messages may scroll +by too fast for you to read, but that's OK. After a couple of +seconds, the installation program should start automatically, so you +can continue down at . + + + + + + Booting from Atari TOS + + +At the GEM desktop, start the Linux installation process by +double-clicking on the bootstra.prg icon in the +debian directory and clicking +Ok at the program options dialog box. + + + +You may have to press the &enterkey; key after the Atari +bootstrap program has output some debugging information into a +window. After this, the screen will go grey, there will be a few +seconds' delay. Next, a black screen with white text should come up, +displaying all kinds of kernel debugging information. These messages +may scroll by too fast for you to read, but that's OK. After a couple +of seconds, the installation program should start automatically, so +you can continue below at . + + + + + + Booting from MacOS + + +You must retain the original Mac system and +boot from it. It is essential that, when booting +MacOS in preparation for booting the Penguin linux loader, you +hold the shift key down to prevent extensions from +loading. If you don't use MacOS except for loading linux, you can +accomplish the same thing by removing all extensions and control +panels from the Mac's System Folder. Otherwise extensions may be left +running and cause random problems with the running linux kernel. + + + +Macs require the Penguin +bootloader. If you do not have the tools to handle +a Stuffit archive, &penguin19.hfs; is an +hfs disk image with Penguin unpacked. + describes how to copy this +image to a floppy. + + + +At the MacOS desktop, start the Linux installation process by +double-clicking on the Penguin Prefs icon in +the Penguin directory. The +Penguin booter will start up. Go to the +Settings item in the +File menu, click the +Kernel tab. Select the kernel +(vmlinuz) and ramdisk +(initrd.gz) images in the +install directory by clicking on the corresponding +buttons in the upper right corner, and navigating the file select +dialogs to locate the files. + + + +To set the boot parameters in Penguin, choose File -> +Settings..., then switch to the +Options tab. Boot parameters may be typed in to +the text entry area. If you will always want to use these settings, +select File -> Save Settings as +Default. + + + +Close the Settings +dialog, save the settings and start the bootstrap using the +Boot Now item in the +File menu. + + + +The Penguin booter will output some debugging +information into a window. After this, the screen will go grey, there +will be a few seconds' delay. Next, a black screen with white text +should come up, displaying all kinds of kernel debugging +information. These messages may scroll by too fast for you to read, +but that's OK. After a couple of seconds, the installation program +should start automatically, so you can continue below at +. + + + + + + Booting from Q40/Q60 + + + +FIXME + + + +The installation program should start automatically, so you can +continue below at . + + + + + + + + Booting from a CD-ROM + + +Currently, the only &arch-title; subarchitecture that +supports CD-ROM booting is the BVME6000. + + + +&boot-installer-intro-cd.xml; + + + + + Booting with TFTP + +&boot-installer-intro-net.xml; + + + +After booting the VMEbus systems you will be presented with the LILO +Boot: prompt. At that prompt enter one of the +following to boot Linux and begin installation proper of the Debian +software using vt102 terminal emulation: + + + + + + + +type i6000 &enterkey; to install a BVME4000/6000 + + + + +type i162 &enterkey; to install an MVME162 + + + + +type i167 &enterkey; to install an MVME166/167 + + + + + + +You may additionally append the string +TERM=vt100 to use vt100 terminal emulation, +e.g., i6000 TERM=vt100 &enterkey;. + + + + + + + Booting from Floppies + + +For most &arch-title; architectures, booting from a local filesystem is the +recommended method. + + + +Booting from the boot floppy is supported only for Atari and VME +(with a SCSI floppy drive on VME) at this time. + + + diff --git a/fi/boot-installer/mips.xml b/fi/boot-installer/mips.xml new file mode 100644 index 000000000..f237aa957 --- /dev/null +++ b/fi/boot-installer/mips.xml @@ -0,0 +1,100 @@ + + + + + Booting with TFTP + + + SGI Indys TFTP Booting + + +After entering the command monitor use + + +bootp(): + + +on SGI Indys to boot linux and to begin installation of the Debian +Software. In order to make this +work you may have to unset the netaddr environment +variable. Type + + +unsetenv netaddr + + +in the command monitor to do this. + + + + + + Broadcom BCM91250A TFTP Booting + + +On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot +loader via TFTP which will then load and start the Debian installer. In +most cases, you will first obtain an IP address via DHCP but it is also +possible to configure a static address. In order to use DHCP, you can +enter the following command on the CFE prompt: + + +ifconfig eth0 -auto + + +Once you have obtained an IP address, you can load SiByl with the following +command: + + +boot 192.168.1.1:/boot/sibyl + + +You need to substitute the IP address listed in this example with either +the name or the IP address of your TFTP server. Once you issue this +command, the installer will be loaded automatically. + + + + + + Boot Parameters + + + SGI Indys TFTP Booting + + +On SGI Indys you can append boot parameters to the +bootp(): command in the command monitor. + + + +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: + + +bootp():/boot/tftpboot.img + + +Further kernel parameters can be passed via append: + + +bootp(): append="root=/dev/sda1" + + + + + + + Broadcom BCM91250A TFTP Booting + + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the /boot/sibyl.conf file on the TFTP +server and add your parameters to the extra_args +variable. + + + + + diff --git a/fi/boot-installer/mipsel.xml b/fi/boot-installer/mipsel.xml new file mode 100644 index 000000000..270390c53 --- /dev/null +++ b/fi/boot-installer/mipsel.xml @@ -0,0 +1,12 @@ + + + + + + + + + + + diff --git a/fi/boot-installer/parameters.xml b/fi/boot-installer/parameters.xml new file mode 100644 index 000000000..5cd71f381 --- /dev/null +++ b/fi/boot-installer/parameters.xml @@ -0,0 +1,351 @@ + + + + Boot Parameters + + +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. + + + +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. + + + +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 +. + + + +When the kernel boots, a message + + +Memory:availk/totalk available + + +should be emitted early in the process. +total should match the total amount of RAM, +in kilobytes. If this doesn't match the actual amount of RAM you have +installed, you need to use the +mem=ram parameter, +where ram is set to the amount of memory, +suffixed with k for kilobytes, or m for +megabytes. For example, both mem=65536k and +mem=64m mean 64MB of RAM. + + + +If you are booting with a serial console, generally the kernel will +autodetect +this (although not on DECstations). +If you have a videocard (framebuffer) and a keyboard also attached to +the computer which you wish to boot via serial console, you may have +to pass the +console=device +argument to the kernel, where device is +your serial device, which is usually something like +ttyS0. + + + +For &arch-title; the serial devices are ttya or +ttyb. +Alternatively, set the input-device and +output-device OpenPROM variables to +ttya. + + + + + Debian Installer Parameters + + +The installation system recognizes a few additional boot parameters + + + +Note that the kernel accepts a maximum of 8 command line options and +8 environment options (including any options added by default for the +installer). If these numbers are exceeded, 2.4 kernels will drop any +excess options and 2.6 kernels will panic. +With kernel 2.6.9 or newer, you can use 32 +command line options and 32 environment options. + + + + which may be useful. + + + + + +debconf/priority + + +This parameter sets the lowest priority of messages to be displayed. + + + +The default installation uses debconf/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. + + + +If you add debconf/priority=medium as boot parameter, you +will be shown the installation menu and gain more control over the installation. +When debconf/priority=low is used, all messages are shown +(this is equivalent to the expert boot method). +With debconf/priority=critical, the installation system +will display only critical messages and try to do the right thing without fuss. + + + + + + +DEBIAN_FRONTEND + + +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=slang + +DEBIAN_FRONTEND=ncurses + +DEBIAN_FRONTEND=bogl + +DEBIAN_FRONTEND=gtk + +DEBIAN_FRONTEND=corba + + + +The default front end is DEBIAN_FRONTEND=newt. +DEBIAN_FRONTEND=text may be preferable for +serial console installs. Generally only the +newt frontend is available on default install +media, so this is not very useful right now. + + + + + + +BOOT_DEBUG + + +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.) + + + +BOOT_DEBUG=0 +This is the default. + + + +BOOT_DEBUG=1 +More verbose than usual. + + + +BOOT_DEBUG=2 +Lots of debugging information. + + + +BOOT_DEBUG=3 + + +Shells are run at various points in the boot process to allow detailed +debugging. Exit the shell to continue the boot. + + + + + + + + + + +INSTALL_MEDIA_DEV + + +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 + + + +The boot floppy, which normally scans all floppies and USB storage +devices it can to find the root floppy, can be overridden by this +parameter to only look at the one device. + + + + + +debian-installer/framebuffer + + +Some architectures use the kernel framebuffer to offer installation in +a number of languages. If framebuffer causes a problem on your system +you can disable the feature by the parameter +debian-installer/framebuffer=false. Problem +symptoms are error messages about bterm or bogl, a blank screen, or +a freeze within a few minutes after starting the install. + + + +The video=vga16:off argument may also be used +to disable the framebuffer. Such problems have been reported on a Dell +Inspiron with Mobile Radeon card. + + + +Such problems have been reported on the Amiga 1200 and SE/30. + + + +Such problems have been reported on hppa. + + + +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. + + + + + +debian-installer/probe/usb + + +Set to false to prevent probing for USB on +boot, if that causes problems. + + + + + +netcfg/disable_dhcp + + +By default, the &d-i; automatically probes for network configuration +via DHCP. If the probe succeeds, you won't have a chance to review and +change the obtained settings. You can get to the manual network setup +only in case the DHCP probe fails. + + + +If you have a DHCP server on your local network, but want to avoid it +because e.g. it gives wrong answers, you can use the parameter +netcfg/disable_dhcp=true to prevent configuring +the network with DHCP and to enter the information manually. + + + + + +hw-detect/start_pcmcia + + +Set to false to prevent starting PCMCIA +services, if that causes problems. Some laptops are well known for +this misbehavior. + + + + + +preseed/url + + +Specify the url to a preconfiguration file to download and use in +automating the install. See . + + + + + +preseed/file + + +Specify the path to a preconfiguration file to load to +automating the install. See . + + + + + +cdrom-detect/eject + + +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. + + + +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. + + + + + +ramdisk_size + + +If you are using a 2.2.x kernel, you may need to set &ramdisksize;. + + + + + +rescue/enable + + +Set to true to enter rescue mode rather than +performing a normal installation. See . + + + + + + + + diff --git a/fi/boot-installer/powerpc.xml b/fi/boot-installer/powerpc.xml new file mode 100644 index 000000000..214c176d4 --- /dev/null +++ b/fi/boot-installer/powerpc.xml @@ -0,0 +1,247 @@ + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + + +Currently, the only &arch-title; subarchitectures that support CD-ROM +booting are PReP and New World PowerMacs. On PowerMacs, hold the +c key, or else the combination of +Command, Option, +Shift, and Delete +keys together while booting to boot from the CD-ROM. + + + +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. + + + +If your system doesn't boot directly from CD-ROM, you can still use +the CD-ROM to install the system. On NewWorlds, you can also use an +OpenFirmware command to boot from the CD-ROM manually. Follow the +instructions in for booting from +the hard disk, except use the path to yaboot on the +CD at the OF prompt, such as + + +0 > boot cd:,\install\yaboot + + + + + + + Booting from Hard Disk + +&boot-installer-intro-hd.xml; + + Booting CHRP from OpenFirmware + + + + Not yet written. + + + + + Booting OldWorld PowerMacs from MacOS + + +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. + + + + + + + Booting NewWorld Macs from OpenFirmware + + +You will have already placed the vmlinux, +initrd.gz, yaboot, and +yaboot.conf files at the root level of your HFS +partition in . +Restart the computer, and immediately (during the chime) hold down the +Option, Command (cloverleaf/Apple), +o, and f keys all together. After +a few seconds you will be presented with the Open Firmware prompt. +At the prompt, type + + +0 > boot hd:x,yaboot + + +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 + + +boot: + + +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. + + + + + + + Booting from USB memory stick + + +Currently, NewWorld PowerMac systems are known to support USB booting. + + + + + +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. + +To get to the prompt, hold down +Command Option +o f all together while +booting (see ). + + + +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. + + + +Having worked out the device path, use a command like this to boot the +installer: + + +boot usb0/disk:2,\\:tbxi + + +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. + + + +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;. + + + +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 . + + + + + Booting with TFTP + +&boot-installer-intro-net.xml; + + + +Currently, PReP and New World PowerMac systems support netbooting. + + + +On machines with Open Firmware, such as NewWorld Power Macs, enter the +boot monitor (see ) and +use the command boot enet:0. PReP and CHRP boxes +may have different ways of addressing the network. On a PReP machine, +you should try +boot server_ipaddr,file,client_ipaddr. + + + + + + + Booting from Floppies + + +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. + + + +You will have already downloaded the floppy images you needed and +created floppies from the images in . + + + +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. + + +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. + + + +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. + + + + + + PowerPC Boot Parameters + + +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 . + + + diff --git a/fi/boot-installer/s390.xml b/fi/boot-installer/s390.xml new file mode 100644 index 000000000..1413f795c --- /dev/null +++ b/fi/boot-installer/s390.xml @@ -0,0 +1,30 @@ + + + + s390 Limitations + + +In order to run the installation system a working network setup and +ssh session is needed on S/390. + + + +The booting process starts with a network setup that prompts you for +several network parameters. If the setup is successful, you will login +to the system by starting a ssh session which will launch the +standard installation system. + + + + + + s390 Boot Parameters + + +On S/390 you can append boot parameters in the parm file. This file can +either be in ASCII or EBCDIC format. Please read +Device Drivers and Installation Commands +for more information about S/390-specific boot parameters. + + + diff --git a/fi/boot-installer/sparc.xml b/fi/boot-installer/sparc.xml new file mode 100644 index 000000000..81cad25e7 --- /dev/null +++ b/fi/boot-installer/sparc.xml @@ -0,0 +1,89 @@ + + + + Booting with TFTP + +&boot-installer-intro-net.xml; + + + +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. Some older OpenBoot revisions require using +the device name, such as boot le(); these +probably don't support BOOTP nor DHCP. + + + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + + +Most OpenBoot versions support the boot cdrom +command which is simply an alias to boot from the SCSI device on ID 6 +(or the secondary master for IDE based systems). You may have to use +the actual device name for older OpenBoot versions that don't support +this special command. Note that some problems have been reported on Sun4m +(e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM. + + + + + + + Booting from Floppies + + +To boot from floppy on a Sparc, use + + +Stop-A -> OpenBoot: "boot floppy" + + +Be warned that the newer Sun4u (ultra) architecture does not support +floppy booting. A typical error message is Bad magic +number in disk label - Can't open disk label package. +Furthermore, a number of Sun4c models (such as the IPX) do not support +the compressed images found on the disks, so also are not supported. + + + +Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from +booting (instead of not supporting booting at all). The appropriate +OBP update can be downloaded as product ID 106121 from +. + + + +If you are booting from the floppy, and you see messages such as + + +Fatal error: Cannot read partition +Illegal or malformed device name + + +then it is possible that floppy booting is simply not supported on +your machine. + + + + + IDPROM Messages + + +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. + + + diff --git a/fi/boot-installer/trouble.xml b/fi/boot-installer/trouble.xml new file mode 100644 index 000000000..831d6aab5 --- /dev/null +++ b/fi/boot-installer/trouble.xml @@ -0,0 +1,274 @@ + + + + + Troubleshooting the Installation Process + + + + + Floppy Disk Reliability + + + +The biggest problem for people using floppy disks to install Debian +seems to be floppy disk reliability. + + + +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. + + + +If you are having the installation stall at a particular floppy, the +first thing you should do is re-download the floppy disk image and +write it to a different floppy. Simply +reformatting the old +floppy may not be sufficient, even if it appears that the floppy was +reformatted and written with no errors. It is sometimes useful to try +writing the floppy on a different system. + + + +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. + + + +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. + + + + + Boot Configuration + + + +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 . + + + +If you are booting with your own kernel instead of the one supplied +with the installer, be sure that CONFIG_DEVFS is set in +your kernel. The installer requires +CONFIG_DEVFS. + + + +Often, problems can be solved by removing add-ons and peripherals, and +then trying booting again. Internal modems, sound +cards, and Plug-n-Play devices can be especially problematic. + + + +If you have a large amount of memory installed in your machine, more +than 512M, and the installer hangs when booting the kernel, you may +need to include a boot argument to limit the amount of memory the +kernel sees, such as mem=512m. + + + + + + Common &arch-title; Installation Problems + + +There are some common installation problems that can be solved or avoided by +passing certain boot parameters to the installer. + + + +Some systems have floppies with inverted DCLs. If you receive +errors reading from the floppy, even when you know the floppy is good, +try the parameter floppy=thinkpad. + + + +On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 +disk drivers), the IDE drive may not be properly recognized. Again, +try it first without the parameters and see if the IDE drive is +recognized properly. If not, determine your drive geometry +(cylinders, heads, and sectors), and use the parameter +hd=cylinders,heads,sectors. + + + +If you have a very old machine, and the kernel hangs after saying +Checking 'hlt' instruction..., then +you should try the no-hlt boot argument, which +disables this test. + + + +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 +debian-installer/framebuffer=false or +video=vga16:off to disable the framebuffer +console. Only the English +language will be available during the installation due to limited +console features. See for details. + + + + + System Freeze During the PCMCIA Configuration Phase + + +Some laptop models produced by Dell are known to crash when PCMCIA device +detection tries to access some hardware addresses. Other laptops may display +similar problems. If you experience such a problem and you don't need PCMCIA +support during the installation, you can disable PCMCIA using the +hw-detect/start_pcmcia=false boot parameter. You can +then configure PCMCIA after the installation is completed and exclude the +resource range causing the problems. + + + +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. + + + + + + System Freeze while Loading the USB Modules + + +The kernel normally tries to install USB modules and the USB keyboard driver +in order to support some non-standard USB keyboards. However, there are some +broken USB systems where the driver hangs on loading. A possible workaround +may be disabling the USB controller in your mainboard BIOS setup. Another option +is passing the debian-installer/probe/usb=false parameter +at the boot prompt, which will prevent the modules from being loaded. + + + + + + + Interpreting the Kernel Startup Messages + + + +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 ). + + + + + + + Bug Reporter + + +If you get through the initial boot phase but cannot complete the +install, the bug reporter menu choice may be helpful. It copies system +error logs and configuration information to a user-supplied floppy. +This information may provide clues as to what went wrong and how to +fix it. If you are submitting a bug report you may want to attach +this information to the bug report. + + + +Other pertinent installation messages may be found in +/var/log/ during the +installation, and /var/log/debian-installer/ +after the computer has been booted into the installed system. + + + + + + Submitting Installation Reports + + +If you still have problems, please submit an installation report. We also +encourage installation reports to be sent even if the installation is +successful, so that we can get as much information as possible on the largest +number of hardware configurations. Please use this template when filling out +installation reports, and file the report as a bug report against the +installation-reports pseudo package, by sending it to +submit@bugs.debian.org. + + +Package: installation-reports + +Debian-installer-version: <Fill in date and from where you got the image> +uname -a: <The result of running uname -a on a shell prompt> +Date: <Date and time of the install> +Method: <How did you install? What did you boot off? If network + install, from where? Proxied?> + +Machine: <Description of machine (eg, IBM Thinkpad R32)> +Processor: +Memory: +Root Device: <IDE? SCSI? Name of device?> +Root Size/partition table: <Feel free to paste the full partition + table, with notes on which partitions are mounted where.> +Output of lspci and lspci -n: + +Base System Installation Checklist: +[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it + +Initial boot worked: [ ] +Configure network HW: [ ] +Config network: [ ] +Detect CD: [ ] +Load installer modules: [ ] +Detect hard drives: [ ] +Partition hard drives: [ ] +Create file systems: [ ] +Mount partitions: [ ] +Install base system: [ ] +Install boot loader: [ ] +Reboot: [ ] + +Comments/Problems: + +<Description of the install, in prose, and any thoughts, comments + and ideas you had during the initial install.> + + +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. + + + + -- cgit v1.2.3