path: root/docs/docs/stable/installer/en/setupBootloader.xml

<?xml version='1.0' encoding='UTF-8'?><section xmlns="http://docbook.org/ns/docbook" xmlns:ns="http://docbook.org/ns/docbook" xmlns:ns3="http://www.w3.org/2000/svg" xmlns:ns4="http://www.w3.org/1999/xlink" xmlns:ns42="http://www.w3.org/1998/Math/MathML" xmlns:ns5="http://www.w3.org/1999/xhtml" xmlns:xi="http://www.w3.org/2001/XInclude" xreflabel="Bootloader" version="5.0" xml:id="setupBootloader">
  <!--Lebarhon 2015 07 04 Project for Mageia 5. The UEFI and BIOS systems are so different I think it is better to split the page 
Lebarhon 2016 12 16 updated for Mageia 6.  20170209 updated SC-->
  <!--2018/02/06 apb: Modified the layout for a (hopefully) easier flow. Also commented-out setupBootloaderAddEntry (was section 24) and incorporated it here, at the end of this file.-->
  <!--2018/02/22 apb: Changed list styles.-->
  <!--2018/02/22 apb: Changed 'Advanced' list style.-->
  <!--2018/02/24 apb: Changed main list style.-->
  <!--2018/02/25 apb: Added xreflabel to this section.-->
  <!--2019/01/06 apb: Typo.-->
  <!--2019/01/06 apb: Use 'xi:include' for setupBootloaderAddEntry.xml, as that is how it is called by the inline-help drakx/perl routine.-->
  <!--2019/07/18 apb: Rewrite 1.1, to accomodate inclusion of rEFInd option, and modify 1.2.1, 1.2.2 accordingly.-->
  <!--2019/08/01 apb: 1.1.1 reworded to: GRUB2-efi or rEFInd may be used as the bootloader for a UEFI system. Added warning text for 1.2.2 Do not Touch MBR/ESP part.-->
  <!--2020/06/28 apb: 1.2.2 updated SC's to reflect changes to installer by Martin Whitaker (2020/06/27): Install to EFI/Boot. Adjust text to match.-->
  <info>
    <title xml:id="setupBootloader-ti1">Bootloader</title>
  </info>
  <section>
    <title>Available Bootloaders</title>
    <section>
      <title>Grub2</title>
      <itemizedlist>
        <para><emphasis role="bold">Grub2 on Legacy MBR/GPT
        systems</emphasis></para>
        <listitem>
          <para>GRUB2 (with or without graphical menu) will be used
          exclusively as the bootloader for a Legacy/MBR or Legacy/GPT
          system.</para>
        </listitem>
        <listitem>
          <para>By default, a new bootloader will be written into either the
          MBR (Master Boot Record) of your first hard drive or in the BIOS
          boot partition.</para>
        </listitem>
      </itemizedlist>
      <itemizedlist>
        <para><emphasis role="bold">Grub2-efi on UEFI
        systems</emphasis></para>
        <listitem>
          <para>GRUB2-efi or rEFInd may be used as the bootloader for a UEFI
          system.</para>
        </listitem>
        <listitem>
          <para>By default, a new bootloader (Grub2-efi) will be written into
          the ESP (EFI System Partition).</para>
          <para>If there are already UEFI-based operating systems installed on
          your computer (Windows 8 for example), the Mageia installer will
          detect the existing ESP created by Windows and add grub2-efi to it.
          If no ESP exists, then one will be created. Although it is possible
          to have several ESPs, only one is required, whatever the number of
          operating systems you have.</para>
        </listitem>
      </itemizedlist>
    </section>
    <section>
      <title>rEFInd</title>
      <itemizedlist>
        <para><emphasis role="bold">rEFInd on UEFI systems</emphasis></para>
        <listitem>
          <para>rEFInd has a nice graphical set of options, and can
          auto-detect installed EFI bootloaders. See:
          http://www.rodsbooks.com/refind/</para>
        </listitem>
      </itemizedlist>
      <note>
        <para>Please note that in order to be able to use the
        <literal>rEFInd</literal> option, an installed EFI System Partition
        must match your system architecture: if you have a 32bit EFI System
        Partition installed on a 64bit machine for instance, then the rEFInd
        option will not be displayed/available to you.</para>
      </note>
    </section>
  </section>
  <section>
    <info>
      <title xml:id="setupBootloader-ti2">Bootloader Setup</title>
    </info>
    <section>
      <title>Bootloader main options</title>
      <mediaobject>
        <imageobject condition="classical">
          <imagedata fileref="dx2-setupBootloader.png" align="center"/>
        </imageobject>
        <imageobject condition="live">
          <imagedata xml:id="setupBootloader-im1" fileref="live-setupBootloader.png"/>
        </imageobject>
      </mediaobject>
      <itemizedlist>
        <listitem>
          <para><emphasis role="bold">Bootloader to use</emphasis></para>
          <itemizedlist>
            <listitem>
              <para><guimenuitem>GRUB2</guimenuitem> (with either a graphical
              or a text menu), can be chosen for both <literal>Legacy
              MBR/BIOS</literal> systems and <literal>UEFI</literal>
              systems.</para>
            </listitem>
            <listitem>
              <para><guimenuitem>rEFInd</guimenuitem> (with a graphical menu)
              is an alternative option solely for use with
              <literal>UEFI</literal> systems.</para>
            </listitem>
          </itemizedlist>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Boot device</emphasis></para>
          <warning>
            <para>Don't change this unless you really know what you are
            doing.</para>
          </warning>
          <note>
            <para>There is no option to write GRUB to the boot sector of a
            partition (e.g: <filename>sda1</filename>), as this method is
            considered unreliable.</para>
          </note>
          <para>When using UEFI mode, then the <guilabel>Boot
          device</guilabel> will be listed as <guimenuitem>EFI System
          Partition</guimenuitem>.</para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Delay before booting the default
          image</emphasis></para>
          <para>This text box lets you set a delay, in seconds, before the
          default operating system is started up.</para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Security</emphasis></para>
          <para>This allows you to set a password for the bootloader. This
          means a username and password will be required when booting in order
          to select a booting entry or change settings. This is optional, and
          most people are not likely to have a need for it. The username is
          <literal>root</literal> and the password is the one chosen
          hereafter.</para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Password</emphasis></para>
          <para>Choose a password for the bootloader (optional)</para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Password (again)</emphasis></para>
          <para>Retype the password and DrakX will check that it matches with
          the one set above</para>
        </listitem>
      </itemizedlist>
      <para><emphasis>Advanced</emphasis></para>
      <itemizedlist>
        <listitem>
          <para><emphasis>Enable ACPI</emphasis></para>
          <para>ACPI (Advanced Configuration and Power Interface) is a
          standard for power management. It can save energy by stopping unused
          devices. Deselecting it could be useful if, for example, your
          computer does not support ACPI or if you think the ACPI
          implementation might cause some problems (for instance random
          reboots or system lockups).</para>
        </listitem>
        <listitem>
          <para><emphasis>Enable SMP</emphasis></para>
          <para>This option enables/disables symmetric multiprocessing for
          multi-core processors</para>
        </listitem>
        <listitem>
          <para><emphasis>Enable APIC</emphasis></para>
          <para>Enabling this gives the operating system access to the
          Advanced Programmable Interrupt Controller. APIC devices permit more
          complex priority models, and Advanced IRQ (Interrupt Request)
          management.</para>
        </listitem>
        <listitem>
          <para><emphasis>Enable Local APIC</emphasis></para>
          <para>Here you can set Local APIC, which manages all external
          interrupts for a specific processor in an SMP system</para>
        </listitem>
      </itemizedlist>
    </section>
    <section>
      <title>Bootloader Configuration</title>
      <para>If, in the previous section you selected <literal>rEFInd</literal>
      as the bootloader to use, you would then be presented with the options
      shown in the screenshot directly below. Otherwise, please instead move
      on to the subsequent screenshot for your options.</para>
      <mediaobject>
        <imageobject condition="classical">
          <imagedata align="center" fileref="rEFIndLoaderConfig.png"/>
        </imageobject>
        <imageobject condition="live">
          <imagedata align="center" fileref="live-rEFIndLoaderConfig.png"/>
        </imageobject>
      </mediaobject>
      <para>Your rEFInd configuration options:</para>
      <itemizedlist>
        <listitem>
          <para><emphasis role="bold">Install or update rEFInd in the EFI
          system partition.</emphasis></para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Install in /EFI/BOOT.</emphasis></para>
          <para>This option installs the bootloader in the /EFI/BOOT directory
          of the ESP (EFI System Partition). This can be useful when:</para>
          <para>(a) Installing onto a removable drive (e.g. a USB stick) that
          can be removed and plugged into a different machine. If the
          bootloader is stored in /EFI/BOOT, UEFI BIOS's will detect it and
          allow you to boot from that drive).</para>
          <para>(b) As a workaround where, due to a buggy UEFI BIOS, the newly
          written bootloader for Mageia will not be recognized at end of the
          installation.</para>
        </listitem>
      </itemizedlist>
      <para>If you did not select rEFInd as the bootloader to use in the
      previous section, then your bootloader configuration options are shown
      below:</para>
      <mediaobject>
        <imageobject condition="classical">
          <imagedata align="center" fileref="dx2-setupBootloader3.png"/>
        </imageobject>
        <imageobject condition="live">
          <imagedata fileref="live-setupBootloader3.png" align="center"/>
        </imageobject>
      </mediaobject>
      <itemizedlist>
        <listitem>
          <para><emphasis role="bold">Default</emphasis></para>
          <para>The operating system to be started up by default.</para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Append</emphasis></para>
          <para>This option lets you pass information to the kernel or tell
          the kernel to give you more information as it boots.</para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Probe foreign OS</emphasis></para>
          <para>If you already have other operating systems installed, Mageia
          attempts to add them to your new Mageia boot menu. If you don't want
          this behaviour, then untick the <guimenuitem>Probe Foreign
          OS</guimenuitem> option.</para>
        </listitem>
        <listitem>
          <para><emphasis role="bold">Install in /EFI/BOOT. </emphasis>(Note:
          this menu option only becomes available where the installer detects
          that a machine is in UEFI mode).</para>
          <para>This option installs the bootloader in the /EFI/BOOT directory
          of the ESP (EFI System Partition). This can be useful when:</para>
          <para>(a) Installing onto a removable drive (e.g. a USB stick) that
          can be removed and plugged into a different machine. If the
          bootloader is stored in /EFI/BOOT, UEFI BIOS's will detect it and
          allow you to boot from that drive).</para>
          <para>(b) As a workaround where, due to a buggy UEFI BIOS, the newly
          written bootloader for Mageia will not be recognized at end of the
          installation.</para>
        </listitem>
      </itemizedlist>
      <para><emphasis>Advanced</emphasis></para>
      <mediaobject>
        <imageobject condition="classical">
          <imagedata fileref="dx2-setupBootloader4.png" align="center"/>
        </imageobject>
        <imageobject condition="live">
          <imagedata fileref="live-setupBootloader4.png" align="center"/>
        </imageobject>
      </mediaobject>
      <itemizedlist>
        <listitem>
          <para><emphasis>Video mode</emphasis></para>
          <para>This sets the screen size and colour depth to be used by the
          boot menu. If you click the down-triangle you will be offered other
          size and colour depth options.</para>
        </listitem>
        <listitem>
          <para><emphasis>Do not touch ESP or MBR</emphasis></para>
          <para>Select this option if you don't want a bootable Mageia, but
          would rather chain-load it from another OS. You will get a warning
          that the bootloader is missing. Click <guimenuitem>Ok
          </guimenuitem>only if you are sure you understand the implications,
          and wish to proceed.</para>
          <warning>
            <para>Chain-loading via legacy bootloaders (GRUB Legacy and LiLo)
            is no longer supported by Mageia as it is likely to fail when
            attempting to boot this resulting installation of Mageia. If you
            use anything other than GRUB2 or rEFInd for this purpose, then you
            do so at your own risk!</para>
          </warning>
        </listitem>
      </itemizedlist>
      <mediaobject>
        <imageobject>
          <imagedata fileref="live-setupBootloader5.png" align="center"/>
        </imageobject>
      </mediaobject>
    </section>
  </section>
  <section>
    <title>Other Options</title>
    <section>
      <title>Using an existing bootloader</title>
      <para>The exact procedure for adding Mageia to an existing bootloader is beyond the scope of this documentation. However, in most cases it will involve running the relevant bootloader installation program, which should detect Mageia and automatically add an entry for it in the bootloader menu. See the documentation for the relevant operating system.</para>
    </section>
    <section>
      <title>Installing Without a Bootloader</title>
      <para>While you can opt to install Mageia without a bootloader (see
      section 2.1 Advanced), this is not recommended unless you absolutely
      know what you are doing, as without some form of bootloader your
      operating system will be unable to start.</para>
    </section>
    <xi:include href="setupBootloaderAddEntry.xml"/>
  </section>
</section>