Here we have instructions on the different boot loaders.
Grub is the default Linux bootloader that works on most systems.
To install a new Grub theme open Grub customizer and go to the appearance tab.
Click the plus symbol next to the theme option and select the archive of the theme you download.
To change the grub theme click on the dropdown menu next to theme and select the theme you want.
Then click save to save your new theme.
You can change your first boot option from Grub Customizer.
click the dropdown menu next to predefined to change your first boot option. or change the order of boot options on the list configuration page.
Plymouth is the fancy startup animations that you see in videos & distros. (please note Plymouth can be buggy on some systems)
Plymouth can only be installed from the AUR
to install it use your preferred AUR helper. In this example we use yay
yay -S plymouth-git
Add the Plymouth hook
plymouth to the
HOOKS array in mkinitcpio.conf. It must be added after
udev for it to work:
/etc/mkinitcpio.conf HOOKS=(base udev plymouth ...)
Copy the theme folders you downloaded to
list all Plymouth themes installed.
set Plymouth theme as default.
Theme is an example name in this.
plymouth-set-default-theme -R theme
To install the systemd-boot EFI boot manager, first make sure the system has booted in UEFI mode and that UEFI variables are accessible. This can be checked by running the command
efivar --list or, if efivar is not installed, by doing
ls /sys/firmware/efi/efivars (if the directory exists, the system is booted in UEFI mode).
esp will be used throughout this page to denote the ESP mountpoint, e.g.
/efi. This assumes that you have
chrooted to your system's mount point.
With the ESP mounted to
esp, use bootctl to install systemd-boot into the EFI system partition by running:
This will copy the systemd-boot boot loader to the EFI partition: on a x64 architecture system
/usr/lib/systemd/boot/efi/systemd-bootx64.efi will be copied to
esp/EFI/BOOT/BOOTX64.EFI. It will then set systemd-boot as the default EFI application (default boot entry) loaded by the EFI Boot Manager.
Note: Installing systemd-boot will overwrite any existing /EFI/BOOT/BOOTX64.EFI, for example Microsoft's version of this file.
Whenever there is a new version of systemd-boot, the boot manager can be optionally reinstalled by the user. This can be performed manually, or the update can be automatically triggered using pacman hooks. The two approaches are described thereafter.
Note: The boot manager is a standalone EFI executable and any version can be used to boot the system (partial updates do not apply, since pacman only installs the systemd-boot installer, not systemd-boot itself). However, new versions may add new features or fix bugs, so it is probably a good idea to update it anyway.
Use bootctl to update systemd-boot:
If the location of the ESP is non-standard (i.e., it is not
/boot/efi), you need to explicitly provide it using the
The package systemd-boot-pacman-hookAUR provides a Pacman hook to automate the update process. Installing the package will add a hook which will be executed every time the systemd package is upgraded. Alternatively, to replicate what the systemd-boot-pacman-hook package does without installing it, place the following pacman hook in the
/etc/pacman.d/hooks/100-systemd-boot.hook [Trigger] Type = Package Operation = Upgrade Target = systemd [Action] Description = Updating systemd-boot When = PostTransaction Exec = /usr/bin/bootctl update