Skip to content

Commit

Permalink
Add how to boot Clear via GRUB.
Browse files Browse the repository at this point in the history 
Add dual-boot-linux link to the multi-boot doc.

Signed-off-by: Bun K Tan <bun.k.tan@intel.com>
  • Loading branch information
@bktan8
bktan8 committed Dec 18, 2019
1 parent 0351271 commit 417bd72
Show file tree
Hide file tree
Showing 2 changed files with 161 additions and 23 deletions.
182 changes: 160 additions & 22 deletions source/tutorials/multi-boot/dual-boot-linux.rst
View file
@@ -1,14 +1,16 @@
.. _dual-boot-linux:

Dual-boot |CL-ATTR| with Another GRUB-based Linux\* Distro
Dual-boot |CL-ATTR| with Any GRUB-based Linux\* Distro
##########################################################

In this tutorial, we show how to install another GRUB-based Linux\* distro
alongside |CL|. To do so, we resize the existing Linux root partition to
make enough room to install |CL|. Then we configure the |CL| bootloader,
:command:`systemd-boot`, which enables you to dual-boot |CL| and an existing
Linux distro. Although we use Ubuntu\* 19.04 Desktop as the example here,
these instructions also work for other distros such as Mint Linux, Kubuntu\*, Fedora\*, CentOS\*, among others.
In this tutorial, we show how to install |CL| alongside any GRUB-based
Linux\* distro. To do so, we resize the existing Linux root partition to
make room to install |CL|. Then we show 3 methods to dual-boot |CL|
with an existing Linux distro.

Although we use Ubuntu\* 19.04 Desktop as the example here,
these instructions also work for other distros such as Mint\*, Kubuntu\*,
Fedora\*, CentOS\*, among others.

.. contents::
:local:
Expand Down Expand Up @@ -37,6 +39,8 @@ Install |CL| with Advanced Installation
#. Complete the :guilabel:`Required Options` until you reach
:guilabel:`Select Installation Media`. See Figure 1.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-01.png
:scale: 100%
:alt: Required options
Expand All @@ -47,6 +51,8 @@ Install |CL| with Advanced Installation

#. Select the “Advanced Installation” option. See Figure 2.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-02.png
:scale: 100%
:alt: Advanced Installation
Expand All @@ -60,6 +66,8 @@ Install |CL| with Advanced Installation
a. Select the Ubuntu root partition (in this example: /dev/sda2).
Right-click it and select “Resize/Move”. See Figure 3.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-03.png
:scale: 100%
:alt: Ubuntu root partition
Expand All @@ -76,6 +84,8 @@ Install |CL| with Advanced Installation
The resulting free space appears in the “Free space following
(MiB)”. Click the “Resize/Move” button. See Figure 4.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-04.png
:scale: 100%
:alt: Resize Ubuntu root
Expand All @@ -84,6 +94,8 @@ Install |CL| with Advanced Installation

#. Click the green checkmark button to proceed. See Figure 5.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-05.png
:scale: 100%
:alt: New unallocated space
Expand All @@ -97,12 +109,16 @@ Install |CL| with Advanced Installation

#. Set the name to “CLR_BOOT”. See Figure 6 and Figure 7.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-06.png
:scale: 100%
:alt: Name CLR_BOOT partition

Figure 6: Name CLR_BOOT partition

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-07.png
:scale: 100%
:alt: Resulting CLR_BOOT main screen
Expand All @@ -122,6 +138,8 @@ Install |CL| with Advanced Installation

#. Click the “Add” button. See Figure 8.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-08.png
:scale: 100%
:alt: Create CLR_SWAP partition
Expand All @@ -139,6 +157,8 @@ Install |CL| with Advanced Installation

#. Click the “Add” button. See Figure 9.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-09.png
:scale: 100%
:alt: Create CLR_ROOT partition
Expand All @@ -148,6 +168,8 @@ Install |CL| with Advanced Installation
#. Click the green checkmark button to create the newly-defined partitions.
See Figure 10.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-10.png
:scale: 100%
:alt: Partitions to be created
Expand All @@ -157,6 +179,8 @@ Install |CL| with Advanced Installation
#. Close the GParted window, and the |CL| installer will reappear with
the newly-defined partitions to use. See Figure 11.

.. rst-class:: dropshadow

.. figure:: ../../_figures/multi-boot/dual-boot-linux-11.png
:scale: 100%
:alt: |CL| installer partitions defined
Expand All @@ -166,23 +190,34 @@ Install |CL| with Advanced Installation
#. Complete the remaining steps of :guilabel:`Required Options` to
to install |CL|. Complete any :guilabel:`Advanced Options` as desired.

Ways to boot |CL|
*****************
Three Methods to Boot |CL|
**************************

Although we installed |CL| last, Ubuntu is still the default boot OS.
There are three methods to boot |CL|:

#. Make systemd-boot, the boot loader that |CL| uses, the default
boot loader to boot |CL| and also chain-boot GRUB; therefore, boot
Ubuntu. See Method 1.

Although we installed |CL| last, Ubuntu is still the default boot OS. There are several ways to boot |CL|:
#. Use GRUB to chain-boot systemd-boot, therefore boot |CL|.
See Method 2.

#. Use your BIOS “Boot Menu” to select and boot |CL|.
This is temporary and will not make |CL| the default boot OS.
Refer to your system's manual on how to bring up the "Boot Menu".

#. Make systemd-boot, the boot loader that |CL| uses, the default
boot loader to boot |CL| and chain-boot GRUB; therefore, boot
Ubuntu. Follow the next section to implement this.
Method 1: Use systemd-boot to Boot |CL| and also Chain-boot GRUB
================================================================

Make systemd-boot Default Bootloader and chain-boot GRUB
********************************************************
systemd-boot is the bootloader used by |CL|. Because |CL| was installed
after a GRUB-based distro, GRUB is still the default bootloader.
In this method, we make systemd-boot the default bootloader instead and
also provide a path to chain-boot GRUB.

#. Boot up the |CL| installer image.

#. Open a terminal window.

#. Identify the EFI system partition, Ubuntu root partition, and |CL| root
partition.

Expand Down Expand Up @@ -214,23 +249,23 @@ Make systemd-boot Default Bootloader and chain-boot GRUB
The above example output contains these partitions:

* /dev/sda1 is the EFI system partition originally created by Ubuntu
* ``/dev/sda1`` is the EFI system partition originally created by Ubuntu
and shared with |CL|
* /dev/sda2 is the Ubuntu root partition
* /dev/sda3 is the swap partition for |CL|
* /dev/sda4 is the |CL| root partition
* ``/dev/sda2`` is the Ubuntu root partition
* ``/dev/sda3`` is the swap partition for |CL|
* ``/dev/sda4`` is the |CL| root partition

The remaining steps will work with these partitions.

#. Mount these partitions
#. Mount these partitions.

.. code-block:: bash
sudo mkdir /mnt/clearlinux
sudo mount /dev/sda4 /mnt/clearlinux/
sudo mount /dev/sda1 /mnt/clearlinux/boot
#. Make systemd-boot the default bootloader
#. Make systemd-boot the default bootloader.

.. code-block:: bash
Expand Down Expand Up @@ -276,6 +311,109 @@ Make systemd-boot Default Bootloader and chain-boot GRUB
Figure 12: systemd-boot menu showing GRUB
Method 2: Use GRUB to Boot |CL|
===============================
In this method, we keep GRUB as the default bootloader, but configure it
to chain-boot systemd-boot, thus allowing us to boot |CL|. Again, we're using
Ubuntu as our working example.
#. Boot up Ubuntu.
#. Open a terminal window.
#. Set a timeout value for the GRUB menu so it will be visible at boot time and
allow you select one which OS to boot.
a. sudoedit :file:`/etc/default/grub`
.. code-block:: bash
sudoedit /etc/default/grub
#. Set the ``GRUB_TIMEOUT`` variable to a desired value.
#. Create a menu entry for systemd-boot bootloader.
a. Identify the UUID for EFI system partition that systemd-boot resides on.
The example below shows the UUID for the EFI system on /dev/sda1 is
"A5A0-337D".
.. code-block:: bash
sudo blkid
Example output:
.. code-block:: console
:emphasize-lines: 1
/dev/sda1: UUID="A5A0-337D" TYPE="vfat" PARTLABEL="CLR_BOOT" PARTUUID="ee664fec-1ade-40d0-9ce4-c08805003c8d"
/dev/sda2: UUID="219969c5-1106-4e9f-b6f5-8188d7d94b8b" TYPE="ext4" PARTUUID="00bdf0dc-264d-493c-bf23-a85105011175"
/dev/sda3: UUID="65221b07-33cb-40b7-9812-ea484c7606c9" TYPE="swap" PARTLABEL="CLR_SWAP" PARTUUID="5a7926b4-bd11-4bad-b932-cc31c0a75d27"
/dev/sda4: UUID="0bedd545-58a7-4f34-b22a-c50bb4a1c2f5" TYPE="ext4" PARTLABEL="CLR_ROOT" PARTUUID="2d60cd03-5739-4cd5-adcc-51a107cde388"
#. sudoedit :file:`/etc/grub.d/40_custom` and add a menu entry
for |CL| using UUID from the previous step (for example):
.. code-block:: console
:linenos:
:emphasize-lines: 7-10
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Clear Linux OS' {
search --fs-uuid --no-floppy --set=root A5A0-337D
chainloader (${root})/EFI/org.clearlinux/bootloaderx64.efi
}
#. Update GRUB.
.. code-block:: bash
sudo update-grub
#. Reboot.
#. At the GRUB boot menu, select :guilabel:`Clear Linux OS` to boot |CL|.
#. Log in.
#. Open a terminal window.
#. By default, any future calls to :command:`clr-boot-manager`, such as
after a kernel update by :command:`swupd` or setting the timeout
value for systemd-boot, will modify the UEFI boot order
which will result in making systemd-boot the first boot
entry and you won't be able to boot Ubuntu any longer. And in order
to boot Ubuntu first, you must change the UEFI boot order back.
To prevent :command:`clr-boot-manager` from touching the UEFI boot
order, which is especially important in a dual-boot setup,
follow these steps:
.. code-block:: bash
sudo mkdir -p /etc/kernel
sudo tee -a /etc/kernel/update_efi_vars << EOF
false
EOF
.. tip::
The default installation of |CL| does not set a timeout value for
systemd-boot. Thus, you will not see the systemd-boot menu and the
default kernel will boot right away.
To set a timeout value (for example: 25 seconds), enter:
.. code-block:: bash
sudo clr-boot-manager set-timeout 25
.. _download the live desktop image: https://clearlinux.org/downloads
.. _Downloads: https://clearlinux.org/downloads
Expand Down
2 changes: 1 addition & 1 deletion source/tutorials/multi-boot/multi-boot.rst
View file
Expand Up @@ -17,4 +17,4 @@ Detailed procedures
:maxdepth: 1

dual-boot-win

dual-boot-linux

0 comments on commit 417bd72

Please sign in to comment.