diff options
Diffstat (limited to 'en/boot-installer')
| -rw-r--r-- | en/boot-installer/accessibility.xml | 8 | ||||
| -rw-r--r-- | en/boot-installer/boot-installer.xml | 9 | ||||
| -rw-r--r-- | en/boot-installer/graphical.xml | 10 | ||||
| -rw-r--r-- | en/boot-installer/hppa.xml | 12 | ||||
| -rw-r--r-- | en/boot-installer/ia64.xml | 464 | ||||
| -rw-r--r-- | en/boot-installer/intro-net.xml | 7 | ||||
| -rw-r--r-- | en/boot-installer/mips.xml | 9 | ||||
| -rw-r--r-- | en/boot-installer/parameters.xml | 28 | ||||
| -rw-r--r-- | en/boot-installer/sparc.xml | 46 | ||||
| -rw-r--r-- | en/boot-installer/trouble.xml | 67 |
10 files changed, 18 insertions, 642 deletions
diff --git a/en/boot-installer/accessibility.xml b/en/boot-installer/accessibility.xml index 13c332da5..9fe810d76 100644 --- a/en/boot-installer/accessibility.xml +++ b/en/boot-installer/accessibility.xml @@ -7,10 +7,10 @@ Some users may need specific support because of e.g. some visual impairment. -<phrase arch="ia64;powerpc;ppc64el;x86">USB braille displays are detected +<phrase arch="ppc64el;x86">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> -<phrase arch="arm;hppa;mips;mipsel;mips64el;sparc">Most</phrase> +<phrase arch="arm;mipsel;mips64el">Most</phrase> accessibility features have to be enabled manually. <phrase arch="x86">On machines that support it, the boot menu emits beeps when it is ready to receive keystrokes. It beeps once on BIOS systems, @@ -56,7 +56,7 @@ selection of choices has to be made (e.g. during task selection), one can type </para> </sect2> - <sect2 arch="ia64;powerpc;ppc64el;x86"> + <sect2 arch="ppc64el;x86"> <title>USB Braille Displays</title> <para> @@ -72,7 +72,7 @@ url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>. </para> </sect2> - <sect2 arch="ia64;powerpc;ppc64el;x86"> + <sect2 arch="ppc64el;x86"> <title>Serial Braille Displays</title> <para> diff --git a/en/boot-installer/boot-installer.xml b/en/boot-installer/boot-installer.xml index aaf704786..e3dd9fd65 100644 --- a/en/boot-installer/boot-installer.xml +++ b/en/boot-installer/boot-installer.xml @@ -5,14 +5,13 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="arm;any-x86;ia64;mips;mipsel;mips64el;s390;powerpc;ppc64el;sparc"> + <sect1 arch="arm;any-x86;mipsel;mips64el;s390;ppc64el"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> <!-- structure inside out for this chapter. Each arch has a document. --> -<!-- Note: arch hppa is currently missing --> -<warning arch="any-x86;powerpc"><para> +<warning arch="any-x86"><para> If you have any other operating systems on your system that you wish to keep (dual boot setup), you should make sure that they have been properly @@ -31,13 +30,9 @@ For information on how to boot the graphical installer, see </para></note> &boot-installer-arm.xml; -<!-- &boot-installer-hppa.xml; --> &boot-installer-x86.xml; -&boot-installer-ia64.xml; -&boot-installer-mips.xml; &boot-installer-s390.xml; &boot-installer-powerpc.xml; -&boot-installer-sparc.xml; &boot-installer-graphical.xml; </sect1> diff --git a/en/boot-installer/graphical.xml b/en/boot-installer/graphical.xml index dd4e65b8e..2d0987c42 100644 --- a/en/boot-installer/graphical.xml +++ b/en/boot-installer/graphical.xml @@ -44,7 +44,10 @@ Look for <filename>netboot/gtk/mini.iso</filename>. </footnote>, which is mainly useful for testing. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id="gtk-miniiso-powerpc"> @@ -58,7 +61,10 @@ Look for <filename>netboot/gtk/mini.iso</filename>. </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems. -</para><para> +</para> +--> + +<para> Just as with the text-based installer it is possible to add boot parameters when starting the graphical installer. diff --git a/en/boot-installer/hppa.xml b/en/boot-installer/hppa.xml deleted file mode 100644 index 3bf892313..000000000 --- a/en/boot-installer/hppa.xml +++ /dev/null @@ -1,12 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect2 arch="hppa"> - <title></title> -<para> - -<!-- Placeholder document; please write and include in - boot-installer.xml and build/templates/docstruct.ent --> - -</para> - </sect2> diff --git a/en/boot-installer/ia64.xml b/en/boot-installer/ia64.xml deleted file mode 100644 index 30be38d30..000000000 --- a/en/boot-installer/ia64.xml +++ /dev/null @@ -1,464 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect2 arch="ia64"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - - <note> - <title>CD Contents</title> - -<para> - -There are three basic variations of &debian; Install CDs. -The <emphasis>Business Card</emphasis> 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 <emphasis>Network Install</emphasis> 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. -</para> - </note> - -<para> - -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. - -</para><para> - -The &debian; Installer CD contains a small EFI partition where the -<command>ELILO</command> 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. - -</para><para> - -Most of the details of how <command>ELILO</command> 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 <command>ELILO</command> -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. - -</para><para> - -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, -<command>Boot Option Maintenance Menu</command> and -<command>EFI Shell (Built-in)</command>. -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. - -</para> - - <warning> - <title>IMPORTANT</title> -<para> -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 <command>exit</command> at the shell prompt. -</para> - </warning> - - <sect3 arch="ia64" id="bootable-cd"> - <title>Option 1: Booting from the Boot Option Maintenance Menu</title> -<para> - -</para> - -<itemizedlist> - -<listitem><para> -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. -</para></listitem> - -<listitem><para> -Select <command>Boot Maintenance Menu</command> from the menu -with the arrow keys and press <command>ENTER</command>. -This will display a new menu. -</para></listitem> - -<listitem><para> -Select <command>Boot From a File</command> from the menu -with the arrow keys and press <command>ENTER</command>. -This will display a list of devices probed by the firmware. -You should see two menu lines containing either the label -<command>Debian Inst [Acpi ...</command> or -<command>Removable Media Boot</command>. -If you examine the rest of the menu line, you will notice that -the device and controller information should be the same. -</para></listitem> - -<listitem><para> -You can choose either of the entries that refer to the CD/DVD -drive. -Select your choice with the arrow keys and press <command>ENTER</command>. -If you choose <command>Removable Media Boot</command> the machine -will immediately start the boot load sequence. -If you choose <command>Debian Inst [Acpi ...</command> instead, it -will display a directory listing of the bootable portion of the -CD, requiring you to proceed to the next (additional) step. -</para></listitem> - -<listitem><para> -You will only need this step if you chose -<command>Debian Inst [Acpi ...</command>. -The directory listing will also show -<command>[Treat like Removable Media Boot]</command> on the next to -the last line. -Select this line with the arrow keys and press <command>ENTER</command>. -This will start the boot load sequence. -</para></listitem> - -</itemizedlist> - -<para> - -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. - -</para> - </sect3> - - <sect3 arch="ia64" id="boot-with-efi"> - <title>Option 2: Booting from the EFI Shell</title> -<para> - -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 <command>EFI Shell [Built-in]</command>. -Boot the &debian; Installer CD with the following steps: - -</para> - -<itemizedlist> - -<listitem><para> -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. -</para></listitem> - -<listitem><para> -Select <command>EFI Shell</command> from the menu with the arrow keys -and press <command>ENTER</command>. -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 -<filename>fs<replaceable>n</replaceable>:</filename>. -All other recognized partitions will be named -<filename>blk<replaceable>n</replaceable>:</filename>. -If you inserted the CD just before entering the shell, this may -take a few extra seconds as it initializes the CD drive. -</para> -</listitem> - -<listitem><para> -Examine the output from the shell looking for the CDROM drive. -It is most likely the <filename>fs0:</filename> device although -other devices with bootable partitions will also show up as -<filename>fs<replaceable>n</replaceable></filename>. -</para></listitem> - -<listitem><para> -Enter <command>fs<replaceable>n</replaceable>:</command> and press -<command>ENTER</command> to select that -device where <replaceable>n</replaceable> is the partition number for the -CDROM. The shell will now display the partition number as its prompt. -</para></listitem> - -<listitem><para> -Enter <command>elilo</command> and press <command>ENTER</command>. -This will start the boot load sequence. -</para></listitem> - -</itemizedlist> - -<para> - -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 -<command>fs<replaceable>n</replaceable>:elilo</command> command at -the shell prompt. -Proceed to selecting the boot kernel and options. - -</para> - - </sect3> - - <sect3 arch="ia64" id="serial-console"> - <title>Installing using a Serial Console</title> - -<para> - -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 -[<replaceable>BAUD</replaceable> baud serial console], where -<replaceable>BAUD</replaceable> is the speed of your serial console. -Menu items for the most typical baud rate settings on the ttyS0 -device are preconfigured. - -</para><para> - -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 -<command>baud</command> at the EFI shell. - -</para><para> - -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 -<command>console=ttyS1,57600n8</command> into -the <classname>Boot:</classname> text window. - -</para> - -<note><para> -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 <classname>Params</classname> -help menu for instructions on starting the installer in Text Mode. -</para></note> - -<warning><para> -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. -</para></warning> - </sect3> - - <sect3 arch="ia64" id="kernel-option-menu"> - <title>Selecting the Boot Kernel and Options</title> - -<para> - -The boot loader will display a form with a menu list and a text -window with a <classname>Boot:</classname> 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 <classname>General</classname> help screen explains the menu -choices and the <classname>Params</classname> screen explains -the common command line options. - -</para><para> - -Consult the <classname>General</classname> help screen for the -description of the kernels and install modes most appropriate -for your installation. -You should also consult <xref linkend="boot-parms"/> below for any additional -parameters that you may want to set in the <classname>Boot:</classname> -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: - -</para> - -<itemizedlist> - -<listitem><para> -Select the kernel version and installation mode most -appropriate to your needs with the arrow keys. -</para></listitem> - -<listitem><para> -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. -</para></listitem> - -<listitem><para> -Press <command>ENTER</command>. This will load and start the -kernel. -The kernel will display its usual initialization messages followed -by the first screen of the &debian; Installer. -</para></listitem> - -</itemizedlist> - -<para> - -Proceed to the next chapter to continue the installation where you will -set up the language locale, network, and disk partitions. - -</para> - </sect3> - </sect2> - - <sect2 arch="ia64" id="boot-tftp-ia64"><title>Booting with TFTP</title> - -<para> -Booting an IA-64 system from the network is similar to a CD boot. -The only difference is how the installation kernel is loaded. -The EFI Boot Manager can load and start programs from a server on -the network. -Once the installation kernel is loaded and starts, the system install -will proceed through the same steps as the CD install with the exception -that the packages of the base install will be loaded from the network -rather than the CD drive. - -</para> - -&boot-installer-intro-net.xml; - -<para> - -Network booting an IA-64 system requires two architecture-specific actions. -On the boot server, DHCP and TFTP must be configured to deliver -<command>elilo</command>. -On the client a new boot option must be defined in the EFI boot manager -to enable loading over a network. - -</para> - - <sect3 arch="ia64" id="boot-tftp-server"> - <title>Configuring the Server</title> -<para> - -A suitable TFTP entry for network booting an IA-64 system looks something -like this: - -<informalexample><screen> -host mcmuffin { - hardware ethernet 00:30:6e:1e:0e:83; - fixed-address 10.0.0.21; - filename "debian-installer/ia64/elilo.efi"; -} -</screen></informalexample> - -Note that the goal is to get <command>elilo.efi</command> running on -the client. - -</para><para> - -Extract the <filename>netboot.tar.gz</filename> file into the directory used -as the root for your tftp server. Typical tftp root directories include -<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. -This will create a <filename>debian-installer</filename> directory -tree containing the boot files for an IA-64 system. - -</para><para> - -<informalexample><screen> -# cd /var/lib/tftp -# tar xvfz /home/user/netboot.tar.gz -./ -./debian-installer/ -./debian-installer/ia64/ -[...] -</screen></informalexample> - -The <filename>netboot.tar.gz</filename> contains an -<filename>elilo.conf</filename> file that should work for most configurations. -However, should you need to make changes to this file, you can find it in the -<filename>debian-installer/ia64/</filename> 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 -<filename>.conf</filename> instead of <filename>elilo.conf</filename>. -See documentation provided in the <classname>elilo</classname> package -for details. - -</para> - </sect3> - - <sect3 arch="ia64" id="boot-tftp-client"> - <title>Configuring the Client</title> -<para> - -To configure the client to support TFTP booting, start by booting to -EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. - -<itemizedlist> -<listitem><para> - -Add a boot option. - -</para></listitem> -<listitem><para> - -You should see one or more lines with the text -<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. 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. - -</para></listitem> -<listitem><para> - -Name the entry <userinput>Netboot</userinput> or something similar, -save, and exit back to the boot options menu. - -</para></listitem> -</itemizedlist> - -You should see the new boot option you just created, and selecting it -should initiate a DHCP query, leading to a TFTP load of -<filename>elilo.efi</filename> from the server. - -</para><para> - -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. - -</para><para> - -Proceed to the next chapter to continue the installation where -you will set up the language locale, network, and disk partitions. - -</para> - </sect3> - </sect2> diff --git a/en/boot-installer/intro-net.xml b/en/boot-installer/intro-net.xml index 1c7512165..a2d6a896d 100644 --- a/en/boot-installer/intro-net.xml +++ b/en/boot-installer/intro-net.xml @@ -7,12 +7,9 @@ Booting from the network requires that you have a network connection and a TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server for automatic network configuration). -</para><para arch="hppa"> +</para> -Older systems such as the 715 might require the use of an RBOOT server -instead of a BOOTP server. - -</para><para> +<para> The server-side setup to support network booting is described in <xref linkend="install-tftp"/>. diff --git a/en/boot-installer/mips.xml b/en/boot-installer/mips.xml deleted file mode 100644 index 7781679dc..000000000 --- a/en/boot-installer/mips.xml +++ /dev/null @@ -1,9 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="mips;mips64el;mipsel" id="boot-tftp-mips"><title>Booting with TFTP</title> - -&boot-installer-intro-net.xml; - - </sect2>
\ No newline at end of file diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml index bbc2837c1..91d981406 100644 --- a/en/boot-installer/parameters.xml +++ b/en/boot-installer/parameters.xml @@ -66,16 +66,6 @@ terminal type, which is very close to <literal>vt102</literal>. </para> -<para arch="sparc"> - -For &arch-title; the serial devices are <filename>ttya</filename> or -<filename>ttyb</filename>. -Alternatively, set the <envar>input-device</envar> and -<envar>output-device</envar> OpenPROM variables to -<filename>ttya</filename>. - -</para> - </sect2> <sect2 id="installer-args"><title>&debian; Installer Parameters</title> @@ -248,21 +238,7 @@ you can disable the feature using the parameter Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install. -</para><para arch="hppa"> - -Such problems have been reported on hppa. - -</para><note arch="sparc"><para> - -Because of display problems on some systems, framebuffer support is -<emphasis>disabled by default</emphasis> 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 <userinput>debian-installer/framebuffer=true</userinput> or -<userinput>fb=true</userinput> for short. - -</para></note></listitem> +</para></listitem> </varlistentry> <varlistentry arch="not-s390"> @@ -433,7 +409,7 @@ disable that authentication. </para></listitem> </varlistentry> -<varlistentry arch="mips;mipsel;mips64el"> +<varlistentry arch="mipsel;mips64el"> <term>ramdisk_size</term> <listitem><para> diff --git a/en/boot-installer/sparc.xml b/en/boot-installer/sparc.xml deleted file mode 100644 index e5c39e742..000000000 --- a/en/boot-installer/sparc.xml +++ /dev/null @@ -1,46 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect2 arch="sparc" id="boot-tftp-sparc"><title>Booting with TFTP</title> - -&boot-installer-intro-net.xml; - -<para> - -On machines with OpenBoot, simply enter the boot monitor on the -machine which is being installed (see -<xref linkend="invoking-openboot"/>). -Use the command <userinput>boot net</userinput> to boot from a TFTP -and RARP server, or try <userinput>boot net:bootp</userinput> or -<userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP -or DHCP server. You can pass extra boot parameters to &d-i; at the end -of the <userinput>boot</userinput> command. - -</para> - </sect2> - - - <sect2 arch="sparc"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - -<para> - -Most OpenBoot versions support the <userinput>boot cdrom</userinput> -command which is simply an alias to boot from the SCSI device on ID 6 -(or the secondary master for IDE based systems). - -</para> - </sect2> - - <sect2 arch="sparc"><title>IDPROM Messages</title> -<para> - -If you cannot boot because you get messages about a problem with -<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which -holds configuration information for you firmware, has run out. See the -<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more -information. - -</para> - </sect2> diff --git a/en/boot-installer/trouble.xml b/en/boot-installer/trouble.xml index 4f6859e69..cbaae23a0 100644 --- a/en/boot-installer/trouble.xml +++ b/en/boot-installer/trouble.xml @@ -356,73 +356,6 @@ installer. </para> </sect3> -<!-- outdated - <sect3> - <title>System Freeze while Loading USB Modules</title> -<para> - -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 <userinput>nousb</userinput> parameter at the boot prompt. - -</para> - </sect3> ---> - - </sect2> - - <sect2 arch="sparc" id="sparc-boot-problems"> - <title>Common &arch-title; Installation Problems</title> -<para> - -There are some common installation problems that are worth mentioning. - -</para> - <sect3> - <title>Misdirected video output</title> -<para> - -It is fairly common for &arch-title; to have two video cards in one machine, -for example an ATI card and a Sun Creator 3D. In some cases, this may result -in the video output getting misdirected soon after the system boots. In -typical cases, the display will only show: - -<informalexample><screen> -Remapping the kernel... done -Booting Linux... -</screen></informalexample> - -To work around this, you can either pull out one of the video cards, or -disable the one not used during the OpenProm boot phase using a kernel -parameter. For example, to disable an ATI card, you should boot the -installer with <userinput>video=atyfb:off</userinput>. - -</para><para> - -Note that you may also have to manually add this parameter to the silo -configuration (edit <filename>/target/etc/silo.conf</filename> before -rebooting) and, if you installed X11, modify the video driver in -<filename>/etc/X11/xorg.conf</filename>. - -</para> - </sect3> - - <sect3> - <title>Failure to Boot or Install from CD-ROM</title> -<para> - -Some Sparc systems are notoriously difficult to boot from CD-ROM and -even if they do boot, there may be inexplicable failures during the -installation. Most problems have been reported with SunBlade systems. - -</para><para> - -We recommend to install such systems by netbooting the installer. - -</para> - </sect3> </sect2> <sect2 id="kernel-msgs"> |