&boot-installer-intro-cd.xml; 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/ram append="devfs=mount,dall ramdisk_size=17000 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 ramdisk_size=17000 initrd (hd0,0)/boot/newinstall/initrd.gz and reboot. Note that the value of the ramdisksize may need to be adjusted for the size of the initrd image. From now on, there should be no difference between GRUB or LILO. 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. 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. 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 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. 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. &boot-installer-intro-net.xml; There are various ways to do a TFTP boot on i386. 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. 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. The etherboot project provides bootdiskettes and even bootroms that do a TFTPboot. When the installer boots, you will be presented with the boot prompt, boot:. 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 press Enter to boot the system. Information on boot parameters which might be useful can be found by pressing F3 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. 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. 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. 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.