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 --- eu/boot-installer/alpha.xml | 451 +++++++++++++++++++++++++++++ eu/boot-installer/arm.xml | 109 +++++++ eu/boot-installer/boot-installer.xml | 28 ++ eu/boot-installer/i386.xml | 542 +++++++++++++++++++++++++++++++++++ eu/boot-installer/ia64.xml | 115 ++++++++ eu/boot-installer/intro-cd.xml | 36 +++ eu/boot-installer/intro-hd.xml | 16 ++ eu/boot-installer/intro-net.xml | 19 ++ eu/boot-installer/m68k.xml | 192 +++++++++++++ eu/boot-installer/mips.xml | 43 +++ eu/boot-installer/parameters.xml | 277 ++++++++++++++++++ eu/boot-installer/powerpc.xml | 188 ++++++++++++ eu/boot-installer/s390.xml | 30 ++ eu/boot-installer/sparc.xml | 102 +++++++ eu/boot-installer/trouble.xml | 200 +++++++++++++ 15 files changed, 2348 insertions(+) create mode 100644 eu/boot-installer/alpha.xml create mode 100644 eu/boot-installer/arm.xml create mode 100644 eu/boot-installer/boot-installer.xml create mode 100644 eu/boot-installer/i386.xml create mode 100644 eu/boot-installer/ia64.xml create mode 100644 eu/boot-installer/intro-cd.xml create mode 100644 eu/boot-installer/intro-hd.xml create mode 100644 eu/boot-installer/intro-net.xml create mode 100644 eu/boot-installer/m68k.xml create mode 100644 eu/boot-installer/mips.xml create mode 100644 eu/boot-installer/parameters.xml create mode 100644 eu/boot-installer/powerpc.xml create mode 100644 eu/boot-installer/s390.xml create mode 100644 eu/boot-installer/sparc.xml create mode 100644 eu/boot-installer/trouble.xml (limited to 'eu/boot-installer') diff --git a/eu/boot-installer/alpha.xml b/eu/boot-installer/alpha.xml new file mode 100644 index 000000000..0613ddda4 --- /dev/null +++ b/eu/boot-installer/alpha.xml @@ -0,0 +1,451 @@ + + + + + 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 with MS-DOS partition tables. +Specifically, the bootsector format required by the Console +Subsystem Specification conflicts with the placement of the DOS +partition table. Since Tru64 Unix uses the BSD disklabel format, +this is the ``native'' partition format for SRM installations. + + + +Because GNU/Linux is the only operating system on Alpha that can be +booted from both console types, the choice will also depend on what +other operating systems you wish to run on the same machine. All +other Unix-like operating systems (Tru64 Unix, FreeBSD, OpenBSD, and +NetBSD) and OpenVMS can only boot from SRM, whereas Windows NT can +only boot from ARC. + + + +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 only (see motherboard manual) + + 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 or SRM + + + + + + + + +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 + + + + + +The UP1000 motherboard (subarchitecture name `nautilus') from Alpha +Processor, Inc. is different from all the others, in that it uses an +API-specific bootloader that runs under AlphaBIOS firmware. + + + +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 + + + + + +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. For example, to boot from +ewa0 and use a console on the first serial +port, you would type: + + + +>>> boot ewa0 -flags 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 from Floppies with the APB Boot Loader (UP1000) + + + +To boot on this platform, run \apb\apb.exe from the +`Utility/Run Maintenance Program' menu, and type + + +boot debian_install + + + at the APB prompt. + + + + + 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/eu/boot-installer/arm.xml b/eu/boot-installer/arm.xml new file mode 100644 index 000000000..fadc600e3 --- /dev/null +++ b/eu/boot-installer/arm.xml @@ -0,0 +1,109 @@ + + + + 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 tftpboot.img + NeTTrom command-> save-all + NeTTrom command-> setenv netconfig_eth0 flash + NeTTrom command-> setenv kernconfig tftp + + + + + +Only the last two of these interfere with normal disk booting, so it is +safe to save-all right before it, which will +store the network settings in case you need to boot from the network +again. Use the printenv command to review your +environment settings. Finally, if your cmdappend +NeTTrom variable has the option (which is +necessary to boot 2.4 kernels), 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/eu/boot-installer/boot-installer.xml b/eu/boot-installer/boot-installer.xml new file mode 100644 index 000000000..9bf77d2b2 --- /dev/null +++ b/eu/boot-installer/boot-installer.xml @@ -0,0 +1,28 @@ + + + +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/eu/boot-installer/i386.xml b/eu/boot-installer/i386.xml new file mode 100644 index 000000000..0867c918a --- /dev/null +++ b/eu/boot-installer/i386.xml @@ -0,0 +1,542 @@ + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + + +You may need to configure your hardware as indicated in +. Then put the CD-ROM into the drive, +and reboot. The system should boot up, and you should be presented +with the boot: prompt. Here you can enter your +boot arguments, or just hit &enterkey;. + + + + + + +If your system can't boot directly from CD-ROM, or you simply can't +seem to get it to work, don't despair; you can simply run +E:\install\boot.bat under DOS (replace +E: with whatever drive letter DOS assigns to +your CD-ROM drive) to start the installation process. Then, skip down +to . + + + +Also, if you're going to be installing from a FAT (DOS) partition, you +have the option of booting the installer from the hard disk. See + for more information on +installing via this method. + + + + + + + + Booting from a DOS partition + +&boot-installer-intro-hd.xml; + + + +Boot into DOS (not Windows) without any drivers being loaded. To do +this, you have to press F8 at exactly the right +moment (and optionally select the `safe mode command prompt only' +option). Enter the subdirectory for the flavor you chose, e.g., + + + +cd c:\current\compact + +. + +Next, execute install.bat. +The kernel will load and launch the installer system. + + + +Please note, there is currently a loadlin problem (#142421) which +precludes install.bat from being used with the +bf2.4 flavor. The symptom of the problem is an +invalid compressed format error. + + + + + + + Booting from linux using <command>LILO</command> or + <command>GRUB</command> + + +For LILO, you will need to configure two +essentials 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/ram + append="devfs=mount,dall" + + + +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/ram devfs=mount,dall +initrd (hd0,0)/boot/newinstall/initrd.gz + + + +and reboot. Please note, that you may need an additional parameter +ramdisk_size=size in KB, +depending on the image you are booting. From now on, there should be +no difference between GRUB or LILO. + + + +You can trace the initrd magic at work several +times during the boot. + + + + +before the kernel has even been loaded, LILO +displays a much longer Loading +imagelabel...... line with +more dots than usual, showing the progression of the RAM disk image +loading. + + + + +You should see the RAM disk driver +initialized +notice, near the real time clock initialization, proving that your +kernel supports the RAM disk feature. + + + + +Finally, if you don't see RAMDISK: ext2 filesystem +found at block 0 immediately after the partition +checks, it's probably because +your kernel miss the initrd feature. + + + + + + +You should now see the debian installer running. If you do not use any +removable medium, you want to check very early that your network +connection is working and before irreversibly +partitioning your hard disk. So you maybe need to +insmod some additional kernel modules for this, +for instance for your network interface. It's time +not to follow the order of steps suggested by +debian-installer. Leap directly to Mount a +Previously-Initialized Partition, and mount the partition +where you stored the modules that you extracted from +drivers.tgz (). + + + + + + + +Then switch to an other virtual terminal and use a shell (see +) to find drivers +in the just mounted /target +directory. insmod the ones you need. + + + +Go to in the +debian-installer installer menus, and +ping your favorite debian mirror at last. +Congratulations! + + + +Use Unmount a Partition if you have mounted one +in the previous +paragraph, safely go back to the partitioning steps at the start of +debian-installer and follow the regular procedure, +with the network as a bonus. At this stage, it is even possible +(only a bit risky) to completely wipe out all the previous partitions +on your hard drive for a very clean installation. The only risk is that +your hard drive will be un-bootable for a short period of time. + + + + + + Booting from USB memory stick + + +Lets 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. Advance according to ; the +kernel on 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 . +If you need to, you can also modify the boot floppy; see +. + + + +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 a 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. + + + +You can do two things at the boot: prompt. You can +press the function keys F1 through +F10 to view a few pages of helpful information, or +you can boot the system. + + + +Information on boot parameters which might be useful can be found by +pressing F4 through F7. 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 floppy=thinkpad). If you simply press &enterkey;, +that's the same as typing linux without any special +parameters. + + + +Once you press &enterkey;, you should see the message +Loading..., followed by +Uncompressing Linux..., and +then a screenful 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. + + + + Etherboot + + +The etherboot project +provides bootdiskettes and even bootroms that do a TFTPboot. + + + + + 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. + + + + + NIC or Motherboard that support PXE + + +It could be that your Network Interface Card or Motherboard provides +PXE boot functionality. +Which is a Intel re-implemention +of TFTP boot. + + + +Let us (&email-debian-boot-list;) know how did you manage it. +Please refer to this document. + + + + + + + i386 Boot Parameters + + +If you are booting from the boot floppy or from CD-ROM you will be +presented with the boot prompt, boot:. Details +about how to use boot parameters with the boot floppy can be found +in . If you are booting from an +existing operating system, you'll have to use other means to set boot +parameters. For instance, if you are installing from DOS, you can +edit the install.bat file with any text editor. + + + +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. The language chooser will not appear; 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. + + + diff --git a/eu/boot-installer/ia64.xml b/eu/boot-installer/ia64.xml new file mode 100644 index 000000000..7c6459479 --- /dev/null +++ b/eu/boot-installer/ia64.xml @@ -0,0 +1,115 @@ + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + Not yet written. + + + + Booting with TFTP + +&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 "elilo.efi"; +} + + + +Note that the goal is to get elilo.efi running on +the client. + + + +Create an ia64/ subdirectory in your tftpboot +directory, and populate it with the vmlinuz and +initrd.gz files from the Debian installer netboot +directory. + + + +Copy elilo.efi to your tftpboot directory and +make it world readable. This file can usually be found in the elilo +package in IA64 distributions, or in +/usr/lib/elilo or in a subdirectory of +/boot/efi. A suitable copy is provided in the +Debian installer netboot directory. + + + +Create an elilo.conf file in your tftpboot +directory. This will +be loaded by elilo.efi once it is running on the +client, and controls what +happens next, including the choice of kernel, initrd image, etc. An +example file is provided in the Debian installer netboot directory, review +the contents and update as needed for your choice of paths, etc. + +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. + + + + +Select the line saying Load File +[Acpi()/.../Mac()] and press &enterkey;. + + + + +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. + + + + + diff --git a/eu/boot-installer/intro-cd.xml b/eu/boot-installer/intro-cd.xml new file mode 100644 index 000000000..4959075fa --- /dev/null +++ b/eu/boot-installer/intro-cd.xml @@ -0,0 +1,36 @@ + + + + + +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 . + + \ No newline at end of file diff --git a/eu/boot-installer/intro-hd.xml b/eu/boot-installer/intro-hd.xml new file mode 100644 index 000000000..be5f65be3 --- /dev/null +++ b/eu/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 +. + + \ No newline at end of file diff --git a/eu/boot-installer/intro-net.xml b/eu/boot-installer/intro-net.xml new file mode 100644 index 000000000..79189195c --- /dev/null +++ b/eu/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/eu/boot-installer/m68k.xml b/eu/boot-installer/m68k.xml new file mode 100644 index 000000000..1d96afa9a --- /dev/null +++ b/eu/boot-installer/m68k.xml @@ -0,0 +1,192 @@ + + + + + Booting from Hard Disk + +&boot-installer-intro-hd.xml; + + + + 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 68k MacOS + + +At the MacOS desktop, start the Linux installation process by +double-clicking on the Penguin Prefs icon in +the debian directory. The +Penguin booter will start up. Go to the +Settings item in the +File menu, click the +Kernel tab. Select the kernel +(linux.bin) and ramdisk +(root.bin) images in the +debian directory by clicking on the corresponding +buttons in the upper right corner, and navigating the file select +dialogs to locate the files. 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 a CD-ROM + +&boot-installer-intro-cd.xml; + + + +Currently, the only &arch-title; subarchitecture that +supports CD-ROM booting is the BVME6000. The easiest route In that +case will be to use a +set of Debian CDs. +Simply insert your CD, reboot, and proceed to the next chapter. + + + + + + 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 m68k 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. + + + + + + Macintosh Limitations + + +In the case of Macintosh, 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 must +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. + + + + + + Penguin Boot Parameters + + +In the Penguin boot program, 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. + + + diff --git a/eu/boot-installer/mips.xml b/eu/boot-installer/mips.xml new file mode 100644 index 000000000..f1c27e517 --- /dev/null +++ b/eu/boot-installer/mips.xml @@ -0,0 +1,43 @@ + + + + + Booting with TFTP + + +After entering the command monitor use + + +bootp(): root=/dev/ram0 + + +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. + + + + + + Boot Parameters + + +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 + + + diff --git a/eu/boot-installer/parameters.xml b/eu/boot-installer/parameters.xml new file mode 100644 index 000000000..b8a9c9784 --- /dev/null +++ b/eu/boot-installer/parameters.xml @@ -0,0 +1,277 @@ + + + + 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 arguments) 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 your monitor is only capable of black-and-white, use the +mono boot argument. Otherwise, your +installation will use color, which is the default. + + + +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 Arguments + + +The installation system recognizes a few boot arguments which may be +useful. + + + + + +DEBCONF_PRIORITY + + +This parameter settings will set the highest 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. + + + + + + +DEBCONF_FRONTEND + + +This boot parameter controls the type of user interface used for the +installer. The current possible parameter settings are: + + + +DEBCONF_FRONTEND=noninteractive + +DEBCONF_FRONTEND=text + +DEBCONF_FRONTEND=newt + +DEBCONF_FRONTEND=slang + +DEBCONF_FRONTEND=ncurses + +DEBCONF_FRONTEND=bogl + +DEBCONF_FRONTEND=gtk + +DEBCONF_FRONTEND=corba + + + +The default front end is DEBCONF_FRONTEND=newt. +DEBCONF_FRONTEND=text may be preferable for +serial console installs. Other frontends but +newt are not available on default install +media, so this is not very useful right now. + + + + + + +BOOT_DEBUG + + +Passing this boot parameter will cause the boot to be more verbosely +logged. + + + +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 floppys 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. + + + + + +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 +chage 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 misbehaviour. + + + + + + + + diff --git a/eu/boot-installer/powerpc.xml b/eu/boot-installer/powerpc.xml new file mode 100644 index 000000000..6d001be6f --- /dev/null +++ b/eu/boot-installer/powerpc.xml @@ -0,0 +1,188 @@ + + + + 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 MacOSROM 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 linux.bin, yaboot, +yaboot.conf, and root.bin 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-safe +followed by a &enterkey;. The `safe' option uses the +video=ofonly argument for maximum +compatibility; you can try it if install +doesn't work. The Debian installation program should start. + + + + + + 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/eu/boot-installer/s390.xml b/eu/boot-installer/s390.xml new file mode 100644 index 000000000..1c4e3efec --- /dev/null +++ b/eu/boot-installer/s390.xml @@ -0,0 +1,30 @@ + + + + s390 Limitations + + +In order to run the installation system a working network setup and +telnet 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 telnet 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/eu/boot-installer/sparc.xml b/eu/boot-installer/sparc.xml new file mode 100644 index 000000000..81549db6b --- /dev/null +++ b/eu/boot-installer/sparc.xml @@ -0,0 +1,102 @@ + + + + Booting from NFS + + +To install the system via NFS, simply select +NFS for the location of the images and files +and follow the instructions provided. You will be prompted for the +server:/directory where the images are located. + + + + + + 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 boot net:dhcp to boot from +a TFTP and DHCP server. Some older OpenBoot revisions require using +the device name, such as boot le(); these +probably don't support 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 seem 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/eu/boot-installer/trouble.xml b/eu/boot-installer/trouble.xml new file mode 100644 index 000000000..2db641c44 --- /dev/null +++ b/eu/boot-installer/trouble.xml @@ -0,0 +1,200 @@ + + + + + Troubleshooting the Install Process + + + + + Floppy Disk Reliability + + + +The biggest problem for people installing Debian for the first time +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. + + + +There are, however, some limitations in our boot floppy set with +respect to supported hardware. Some Linux-supported platforms might +not be directly supported by our boot floppies. If this is the case, +you may have to create a custom boot disk (see +), or investigate network +installations. + + + +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. + + + + + + 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 +/target/var/log/debian-installer/ during the +installation, and /var/log/debian-installer/ +after the computer has been booted into the installed system. + + + + + + Submitting Bug Reports + + +If you still have problems, please submit a bug report. Send an email +to submit@bugs.debian.org. You +must include the following as the first lines of +the email: + + + +Package: installation-reports +Version: version + + + +Be sure to fill in version with the +version of the debian-installer that you used. The version number can +be found if you press F1 key on the +boot: prompt of your installation media. You should +also mention where did you download the installation media, or the +source of a CD you bought. + + + +You should also include the following information in your bug report. +If you use the program reportbug to submit your +report, this information will be included automatically. + + + + +flavor: flavor of image you are using + +architecture: &architecture; +model: your general hardware vendor and model +memory: amount of RAM +scsi: SCSI host adapter, if any +cd-rom: CD-ROM model and interface type, e.g., ATAPI +network card: network interface card, if any +pcmcia: details of any PCMCIA devices + + + + + +Depending on the nature of the bug, it also might be useful to report +whether you are installing to IDE or SCSI disks, other peripheral +devices such as audio, disk capacity, and the model of video card. + + + +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