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. 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. 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. The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see ). 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. 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. The only method of installation available to Q40/Q60 is from the hard drive (see ). In other words the cdrom is not bootable. &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. 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 . 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 . 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 . FIXME The installation program should start automatically, so you can continue below at . Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000. &boot-installer-intro-cd.xml; &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;. 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.