systemd-boot

To install systemd-boot, first make sure that the system is booted into UEFI mode and UEFI variables are accessible. This can be verified by running efivar --list or, if efivar is not installed, by running ls /sys/firmware/efi/efivars (if the directory exists, the system is booted into UEFI mode.)

Throughout, esp will denote the ESP mountpoint, e.g. or . This assumes that you have chrooted to the system's mount point.

Use to install systemd-boot to the ESP:

# bootctl install

This will copy the systemd-boot EFI boot manager to the ESP: on an x64 architecture system /usr/lib/systemd/boot/efi/systemd-bootx64.efi will be copied to esp/EFI/systemd/systemd-bootx64.efi and , and systemd-boot will be set as the default EFI application.

To conclude the installation, configure systemd-boot.

A separate /boot partition of type "Linux extended boot" (XBOOTLDR) can be created to keep the kernel and initramfs separate from the ESP. This is particularly helpful to dual boot with Windows with an existing ESP that is too small.

Prepare an ESP as usual and create another partition for XBOOTLDR on the same physical drive. The XBOOTLDR partition must have a partition type GUID of . The size of the XBOOTLDR partition should be large enough to accommodate all of the kernels you are going to install.

During install, mount the ESP to and the XBOOTLDR partition to .

Once in chroot, use the command:

# bootctl --esp-path=/efi --boot-path=/boot install

To conclude the installation, configure systemd-boot.

Whenever there is a new version of systemd-boot, the EFI boot manager can be optionally reinstalled by the user. This can be done manually or automatically; the two approaches are described thereafter.

Use bootctl to update systemd-boot:

# bootctl update

To update systemd-boot automatically, either use a systemd service or a pacman hook. The two methods are described below.

As of version 250, systemd ships with . Enabling this service will update the bootloader upon the next boot.

The package adds a pacman hook which is executed every time systemd is upgraded.

Rather than installing systemd-boot-pacman-hook, you may prefer to manually place the following file in :

If you have Secure Boot enabled, you may want to add a pacman hook to automatically re-sign the kernel and bootloader upon every upgrade of the respective packages:

Make sure that the parameters point to your signing key and certificate. For better understanding of this hook, consult and .

The loader configuration is stored in the file . See loader.conf(5) § OPTIONS for details.

A loader configuration example is provided below:

''esp''/loader/loader.conf

default  arch.conf
timeout  4
console-mode max
editor   no

systemd-boot will search for boot menu items in and additionally in if using XBOOTLDR. Note that entries in esp can only use files (e.g. kernels, initramfs, images, etc.) in esp. Similarly, entries in can only use files in .

The possible options are:

• – operating system name. Required.
• – kernel version, shown only when multiple entries with same title exist. Optional.
• – machine identifier from , shown only when multiple entries with same title and version exist. Optional.
• efi – EFI program to start, relative to your ESP (esp); e.g. . Either this parameter or linux (see below) is required.
• – space-separated command line options to pass to the EFI program or kernel parameters. Optional, but you will need at least if booting Linux. This parameter can be omitted if the root partition is assigned the correct Root Partition Type GUID as defined in Discoverable Partitions Specification and if the mkinitcpio hook is present.

For Linux boot, you can also use linux instead of efi. Or in addition to . The syntax is:

• linux or followed by the relative path of the corresponding files in the ESP; e.g. ; this will be automatically translated into and – this syntax is only supported for convenience and has no differences in function.

An example of loader files launching Arch from a volume labeled arch_os and loading Intel CPU microcode is:

systemd-boot will automatically check at boot time for Windows Boot Manager at the location , UEFI shell and EFI Default Loader /EFI/BOOT/bootx64.efi, as well as specially prepared kernel files found in . When detected, corresponding entries with titles , and , respectively, will be generated. These entries do not require manual loader configuration. However, it does not auto-detect other EFI applications (unlike rEFInd), so for booting the Linux kernel, manual configuration entries must be created.

In case you installed an EFI shell with the package , systemd-boot will auto-detect and create a new entry if the EFI file is placed in . To perform this and example command after installing the package would be:

# cp /usr/share/edk2-shell/x64/Shell.efi /boot/shellx64.efi

Otherwise in case you installed other EFI applications into the ESP, you can use the following snippets.

systemd-boot cannot launch binaries from partitions other than the ESP or the XBOOTLDR partition, but it can run an external script to do so.

First we need to install (will be the interpreter to be used) and using the EFI shell (as explained above) we can use the map command to take notes of the FS alias (ex: HD0a66666a2) and the full path of the destination EFI file (ex: EFI\Microsoft\Boot\Bootmgfw.efi).

Then using the exit command we can boot back into Linux where we can create the new entry. To do so we need to first create in the root of the esp mount point a .nsh filename with the FS alias, a colon and the EFI path, here an example:

Once we created this file we can proceed to create the loader entry to run the script:

''esp''/loader/entries/windows.conf

title  Windows
efi     /shellx64.efi
options -nointerrupt -noconsolein -noconsoleout windows.nsh

Its important that the efi path matches where the edk2-shell has been copied in the esp partition, and the last argument of options matches the .nsh filename in the root of the esp partition. Also note that the edk2-shell EFI file can be moved to avoid the entry auto-creation of systemd-boot.

systemd-boot will automatically add an entry to boot into UEFI Firmware Setup if your device's firmware supports rebooting into setup from the OS.

See Suspend and hibernate.

Alternatively you can install which supports basic configuration option. Use sbpctl generate to generate a value for this option.

Install systemd-boot-password with the following command:

# sbpctl install esp

With enabled editor you will be prompted for your password before you can edit kernel parameters.

See for the available key bindings inside the boot menu.

The boot manager is integrated with the systemctl command, allowing you to choose what option you want to boot after a reboot. For example, suppose you have built a custom kernel and created an entry file to boot into it, you can just launch

$ systemctl reboot --boot-loader-entry=arch-custom.conf

and your system will reboot into that entry maintaining the default option intact for subsequent boots. To see a list of possible entries pass the option.

If you want to boot into the firmware of your motherboard directly, then you can use this command:

$ systemctl reboot --firmware-setup

Unified kernel images in are automatically sourced by systemd-boot, and do not need an entry in . (Note that unified kernel images must have a extension to be identified by systemd-boot.)

Grml is a small live system with a collection of software for system administration and rescue.

In order to install Grml on the ESP, we only need to copy the kernel , the initramfs initrd.img, and the squashed image from the iso file to the ESP. To do so, first download grml64-small.iso and mount the file (the mountpoint is henceforth denoted mnt); the kernel and initramfs are located in , and the squashed image resides in .

Next, create a directory for Grml in your ESP,

# mkdir -p esp/grml

and copy the above-mentioned files in there:

# cp mnt/boot/grml64small/vmlinuz esp/grml
# cp mnt/boot/grml64small/initrd.img esp/grml
# cp mnt/live/grml64-small/grml64-small.squashfs esp/grml

In the last step, create an entry for the systemd-boot loader: In create a file with the following content:

For an overview of the available boot options, consult the cheatcode for Grml.

If you need a bootloader for BIOS systems that follows The Boot Loader Specification, then systemd-boot can be pressed into service on BIOS systems. The Clover boot loader supports booting from BIOS systems and provides a simulated EFI environment.

If booted in BIOS mode, you can still install systemd-boot, however this process requires you to tell firmware to launch systemd-boot's EFI file at boot, usually via two ways:

• you have a working EFI Shell somewhere else.
• your firmware interface provides a way of properly setting the EFI file that needs to be loaded at boot time.

If you can do it, the installation is easier: go into your EFI Shell or your firmware configuration interface and change your machine's default EFI file to esp/EFI/systemd/systemd-bootx64.efi.

If the command failed, you can create a EFI boot entry manually using efibootmgr:

# efibootmgr --create --disk /dev/sdX --part Y --loader "\EFI\systemd\systemd-bootx64.efi" --label "Linux Boot Manager" --unicode

where /dev/sdXY is the EFI system partition.

If for any reason you need to create an EFI boot entry from Windows, you can use the following commands from an Administrator prompt:

> bcdedit /copy {bootmgr} /d "Linux Boot Manager"
> bcdedit /set {guid} path \EFI\systemd\systemd-bootx64.efi

Replace with the id returned by the first command. You can also set it as the default entry using

> bcdedit /default {guid}

See UEFI#Windows changes boot order.