[install-guide/f21-branch: 21/32] Adding the Booting the Installer chapter
pbokoc
pbokoc at fedoraproject.org
Tue Dec 9 17:32:13 UTC 2014
commit 819a3cb54ca23afb5c1cd9c90c4e033670be9b69
Author: Petr Bokoc <pbokoc at redhat.com>
Date: Mon Dec 8 22:25:10 2014 +0100
Adding the Booting the Installer chapter
en-US/Booting_the_Installation.xml | 120 ++++++++++++++++++++++++++----------
en-US/VNC_Installations.xml | 2 +-
en-US/images/boot/boot-menu.png | Bin 0 -> 4112 bytes
3 files changed, 87 insertions(+), 35 deletions(-)
---
diff --git a/en-US/Booting_the_Installation.xml b/en-US/Booting_the_Installation.xml
index 0a17821..a067a23 100644
--- a/en-US/Booting_the_Installation.xml
+++ b/en-US/Booting_the_Installation.xml
@@ -6,50 +6,102 @@
<chapter id="chap-booting-the-installation">
<title>Booting the Installation</title>
<para>
- intro text
+ This chapter will explain how to boot the installer from local media or a network server as well as how to navigate the boot menu and use custom options.
</para>
- <section id="sect-booting-local-media">
- <title>Booting from Local Media</title>
+ <section id="sect-preparing-boot">
+ <title>Preparing to Boot</title>
<para>
- text
+ After you have made a bootable USB flash drive or a CD or DVD using the steps described in <xref linkend="sect-preparing-boot-media" />, you are ready to boot the installation. Note that the steps described below are generic and the exact steps will vary somewhat depending on your system - particularly on your motherboard manufacturer.
</para>
- </section>
-
- <section id="sect-booting-network">
- <title>Booting from a Network</title>
+ <warning>
+ <para>
+ There are no separate media provided for BIOS and UEFI systems; all of them can boot from the same ISO image. However, once you install &PRODUCT;, you can not switch between UEFI and BIOS. The system must run on the same firmware it was installed on; if you, for example, perform the installation on an UEFI system in UEFI mode, and then switch it to BIOS compatibility mode, &PRODUCT; will no longer boot and will require a reinstallation.
+ </para>
+ </warning>
+ <important>
+ <para>
+ &PRODUCT; does not support UEFI booting for 32-bit x86 systems. Only BIOS boot is supported on these systems.
+ </para>
+ <para>
+ Also note that &PRODUCT; only fully supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 or later will boot and work normally, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from <ulink url="http://www.uefi.org/specs/agreement/" />.
+ </para>
+ </important>
<para>
- text
+ To boot the &PRODUCT; installer, follow these steps:
</para>
+ <procedure>
+ <title>Booting the &PRODUCT; Installer</title>
+ <step>
+ <para>
+ Plug in the boot USB drive, or insert the boot CD or DVD into your computer's optical disc drive. Alternatively, if you plan on booting from a network boot (PXE) server, make sure that the network cable is plugged in.
+ </para>
+ </step>
+ <step>
+ <para>
+ Restart the system. Once it starts rebooting, it should display a prompt similar to the following (usually at the bottom of the screen):
+ </para>
+ <screen>
+Press F12 to select boot device, or Del to enter SETUP
+ </screen>
+ <para>
+ Follow the on-screen instructions to access the boot menu. If no instructions are displayed (some systems only display a graphical logo during early stages of boot), try pressing <keycap>F12</keycap>, <keycap>F11</keycap>, <keycap>F10</keycap> or <keycap>Del</keycap> several times; these are most commonly used keys. Note that there is usually a very short time window provided to access the menu; once it passes, you need to restart the system and try again.
+ </para>
+ <note>
+ <para>
+ Some older systems may not support choosing a boot device at startup. In that case, enter the system's SETUP (BIOS), and change the default boot order so that your boot media (CD, DVD, USB or network) have higher priority than internal hard drives.
+ </para>
+ </note>
+ </step>
+ <step>
+ <para>
+ When your system's boot menu opens, select an entry such as <guilabel>Boot from USB</guilabel> if you created a bootable USB drive, <guilabel>Boot from CD/DVD</guilabel> if you are using an optical disc to install &PRODUCT;, or <guilabel>Boot from PXE</guilabel> if you want to boot from a network location.
+ </para>
+ </step>
+ <step>
+ <para>
+ Wait until the boot menu is displayed. The boot menu is described further in this chapter.
+ </para>
+ </step>
+ </procedure>
</section>
<section id="sect-boot-menu">
<title>The Boot Menu</title>
<para>
- text
+ In most cases, when you boot the &PRODUCT; installer from your prepared boot media or server, the boot menu will the the first thing that appears. From this menu, you can either start the actual installation, or you can use the boot media to rescue an existing system.
</para>
-
- <section id="sect-boot-menu-x86-bios">
- <title>The Boot Menu on BIOS-based AMD and Intel Systems</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-boot-menu-x86-uefi">
- <title>The Boot Menu on UEFI-based AMD and Intel Systems</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-boot-menu-arm">
- <title>The Boot Menu on ARM Systems</title>
- <para>
- text
- </para>
- </section>
-
- </section>
-
+ <para>
+ The way the boot menu will look and function will vary somewhat depending on your system's firmware - BIOS systems use the <application>SYSLINUX</application> boot loader, and UEFI systems use <application>GRUB2</application>. However, both of the menus described below function very similarly from a user's point of view.
+ </para>
+ <para>
+ Use arrow keys to select an entry in the menu, and <keycap>Enter</keycap> to confirm your selection. The first two entries in the list will both proceed with the installation; the first one will start the installer directly, and the second one will verify the integrity of the boot media before starting the installation.
+ </para>
+ <para>
+ The final entry in the list is <guilabel>Troubleshooting</guilabel>; this is a submenu. Selecting this entry and pressing <keycap>Enter</keycap> will display a new set of selections, where you can choose to install in basic graphics mode (useful if you want to do a manual graphical installation but your system has issues with the default graphical installer), rescue an existing system, or test your system's memory modules for errors (on BIOS systems only). The troubleshooting menu also allows you to exit the boot menu and boot normally from your system's hard drive via the <guilabel>Boot from local drive</guilabel> option.
+ </para>
+ <para>
+ Every menu entry in the list is a predefined set of boot options, and these options can be customized to change some aspects of the installer's behavior. To edit the default set of boot options, press <keycap>Tab</keycap> on BIOS systems, or <keycap>e</keycap> on UEFI systems. The key to use is also displayed at the bottom of the screen.
+ </para>
+ <para>
+ When editing the default set of options, you can change the existing ones as well as append additional ones. Once you finish, press <keycap>Enter</keycap> on BIOS or <keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo> on UEFI to boot the installer using your customized options.
+ </para>
+ <figure>
+ <title>Editing boot options on a system with BIOS firmware</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/boot/boot-menu.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The boot menu.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <para>
+ All available <application>Anaconda</application> boot options are described in <xref linkend="sect-boot-options-available" />.
+ </para>
+ </section>
+
</chapter>
diff --git a/en-US/VNC_Installations.xml b/en-US/VNC_Installations.xml
index dca125a..1dadb28 100644
--- a/en-US/VNC_Installations.xml
+++ b/en-US/VNC_Installations.xml
@@ -279,7 +279,7 @@ Thu Feb 20 15:23:54 2014
</listitem>
<listitem>
<para>
- Follow the procedure for a VNC Installation using connect mode as described in the <xref linkend="proc-vnc-installations-connect-mode" />. However, when directed to boot the system, boot it from the PXE server as described in <xref linkend="sect-booting-network" />.
+ Follow the procedure for a VNC Installation using connect mode as described in the <xref linkend="proc-vnc-installations-connect-mode" />. However, when directed to boot the system, boot it from the PXE server.
</para>
</listitem>
</orderedlist>
diff --git a/en-US/images/boot/boot-menu.png b/en-US/images/boot/boot-menu.png
new file mode 100644
index 0000000..412af59
Binary files /dev/null and b/en-US/images/boot/boot-menu.png differ
More information about the docs-commits
mailing list