Difference between revisions of "Systemd-boot"

From ArchWiki
Jump to: navigation, search
m (Add page link.)
(Adding boot entries: add auto-* titles)
 
(181 intermediate revisions by 71 users not shown)
Line 1: Line 1:
 +
{{lowercase title}}
 
[[Category:Boot loaders]]
 
[[Category:Boot loaders]]
[[ja:Gummiboot]]
+
[[de:Gummiboot]]
[http://freedesktop.org/wiki/Software/gummiboot Gummiboot] is a UEFI boot manager written by Kay Sievers and Harald Hoyer. It is simple to configure, but can only start EFI executables, the Linux kernel [[EFISTUB]], UEFI Shell, grub.efi, and such.
+
[[es:Systemd-boot]]
 +
[[ja:Systemd-boot]]
 +
[[ru:Systemd-boot]]
 +
[[zh-hans:Systemd-boot]]
 +
{{Related articles start}}
 +
{{Related|Arch boot process}}
 +
{{Related|Boot loaders}}
 +
{{Related|Secure Boot}}
 +
{{Related|Unified Extensible Firmware Interface}}
 +
{{Related articles end}}
  
{{Warning|Gummiboot simply provides a boot menu for EFISTUB kernels. It does not directly launch a Linux Kernel like a traditional bootloader (GRUB, Syslinux) (hence it is called a Boot Manager, not a Boot Loader). In case you have issues booting EFISTUB kernels like in https://bugs.archlinux.org/task/33745 , you should use a bootloader which does not use EFISTUB, like [[GRUB]](2), [[UEFI_Bootloaders#SYSLINUX_6.xx|Syslinux 6.xx]] or [[UEFI_Bootloaders#ELILO|ELILO]]. [[UEFI_Bootloaders#Using_rEFInd|rEFInd]] also uses EFISTUB so that cannot be used in such cases.}}
+
'''systemd-boot''', previously called '''gummiboot''', is a simple UEFI boot manager which executes configured EFI images. The default entry is selected by a configured pattern (glob) or an on-screen menu. It is included with {{pkg|systemd}}, which is installed on Arch system by default.
  
{{Note|In the entire article {{ic|$esp}} denotes the mountpoint of the EFI System Partition aka ESP.}}
+
It is simple to configure but it can only start EFI executables such as the Linux kernel [[EFISTUB]], UEFI Shell, GRUB, the Windows Boot Manager.
  
 
== Installation ==
 
== Installation ==
  
Install {{Pkg|gummiboot}} and install gummiboot in ESP:
+
=== EFI boot ===
  
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars              # ignore if already mounted
+
# Make sure you are booted in UEFI mode.
# pacman -S gummiboot
+
# Verify [[Unified_Extensible_Firmware_Interface#Requirements_for_UEFI_variable_support|your EFI variables are accessible]].
# gummiboot --path=$esp install
+
# Mount your [[EFI System Partition]] (ESP) properly. {{ic|''esp''}} is used to denote the mountpoint in this article. {{Note|''systemd-boot'' cannot load EFI binaries from other partitions. It is therefore recommended to mount your ESP to {{ic|/boot}}. In case you want to separate {{ic|/boot}} from the ESP see [[#Manually]] for more information.}}
 +
# If the ESP is '''not''' mounted at {{ic|/boot}}, then copy your kernel and initramfs onto that ESP. {{Note|For a way to automatically keep the kernel updated on the ESP, have a look at [[EFISTUB#Using systemd]] for some systemd units that can be adapted. If your EFI System Partition is using automount, you may need to add {{ic|vfat}} to a file in {{ic|/etc/modules-load.d/}} to ensure the current running kernel has the {{ic|vfat}} module loaded at boot, before any kernel update happens that could replace the module for the currently running version making the mounting of {{ic|/boot/efi}} impossible until reboot.}}
 +
# Type the following command to install ''systemd-boot'': {{bc|1=# bootctl --path=''esp'' install}} It will copy the ''systemd-boot'' binary to your EFI System Partition ({{ic|''esp''/EFI/systemd/systemd-bootx64.efi}} and {{ic|''esp''/EFI/Boot/BOOTX64.EFI}} – both of which are identical – on x86-64 systems) and add ''systemd-boot'' itself as the default EFI application (default boot entry) loaded by the EFI Boot Manager.
 +
# Finally you must [[#Configuration|configure]] the boot loader to function properly.
  
This will automatically copy the gummiboot binary to your EFI System Partition and create a boot entry in the EFI Boot Manager. If you are not booted via EFI, creating the boot entry will fail. You should however still be able to boot gummiboot as it copies the binary to the default EFI binary location on your ESP ({{ic|$esp/EFI/boot/bootx64.efi}} on x64 systems) (unless a non-gummiboot {{ic|$esp/EFI/boot/bootx64.efi}} is already present).
+
=== BIOS boot ===
  
{{Note|
+
{{Warning|This is not recommended.}}
* The gummiboot command by default assumes that your EFI System Partition is mounted on {{ic|/boot}}. This means gummiboot in the ESP will not be updated automatically during pkg updates and you will have to call {{ic|1=gummiboot --path=$esp update}} after every package update. Additionally you will have to make sure that the kernel and initramfs are copied onto the ESP as gummiboot can't load EFI binaries from other partitions. It is therefore strongly recommended to mount your ESP to {{ic|/boot}} if you use gummiboot, in which case updating will happen automatically by the post_install script of {{Pkg|gummiboot}} during package updates.
+
You can successfully install ''systemd-boot'' if booted with in BIOS mode. 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 {{ic|''esp''/EFI/systemd/systemd-bootx64.efi}} ( or {{ic|systemd-bootia32.efi}} depending if your system firmware is 32 bit).
 +
 
 +
{{Note|the firmware interface of Dell Latitude series provides everything you need to setup EFI boot but the EFI Shell won't be able to write to the computer's ROM.}}
 +
 
 +
=== Updating ===
 +
 
 +
Unlike the previous separate ''gummiboot'' package, which updated automatically on a new package release with a {{ic|post_install}} script, updates of new ''systemd-boot'' versions must now be done manually by the user. However the procedure can be automated using pacman hooks.
 +
 
 +
==== Manually ====
 +
 
 +
''systemd-boot'' ({{man|1|bootctl|url=https://www.freedesktop.org/software/systemd/man/bootctl.html}}, {{man|8|systemd-efi-boot-generator|url=http://man7.org/linux/man-pages/man8/systemd-efi-boot-generator.8.html}}) assumes that your EFI System Partition is mounted on {{ic|/boot}}.
 +
 
 +
# bootctl update
 +
 
 +
If the ESP is not mounted on {{ic|/boot}}, the {{ic|1=--path=}} option can pass it. For example:
 +
 
 +
# bootctl --path=''esp'' update
 +
 
 +
{{Note|This is also the command to use when migrating from ''gummiboot'', before removing that package. If that package has already been removed, however, run {{ic|1=bootctl --path=''esp'' install}}.}}
 +
 
 +
==== Automatically ====
 +
 
 +
The [[AUR]] package {{AUR|systemd-boot-pacman-hook}} provides a [[Pacman#Hooks|Pacman hook]] to automate the update process. [[Install|Installing]] the package will add a hook which will be executed every time the {{Pkg|systemd}} package is upgraded.
 +
 
 +
Alternatively, place the following pacman hook in the {{ic|/etc/pacman.d/hooks/}} directory:
 +
 
 +
{{hc|/etc/pacman.d/hooks/systemd-boot.hook|2=
 +
[Trigger]
 +
Type = Package
 +
Operation = Upgrade
 +
Target = systemd
 +
 
 +
[Action]
 +
Description = Updating systemd-boot...
 +
When = PostTransaction
 +
Exec = /usr/bin/bootctl update
 +
}}
  
* If {{ic|gummiboot}} fails to create a boot entry, check whether all the conditions mentioned [[Unified_Extensible_Firmware_Interface#Requirements_for_UEFI_Variables_support_to_work_properly|here]] are met.}}
+
== Configuration ==
  
==Configuration ==
+
=== Basic configuration ===
  
=== Basic Configuration ===
+
The basic configuration is stored in {{ic|''esp''/loader/loader.conf}} file and it is composed by three options:
  
The basic configuration is kept in {{ic|$esp/loader/loader.conf}}, with just two possible configuration options:
+
* {{ic|default}} – default entry to select (without the {{ic|.conf}} suffix); can be a wildcard like {{ic|arch-*}}.
  
* {{ic|default}} – default entry to select (without the {{ic|.conf}} suffix); can be a wildcard like {{ic|arch-*}}
+
* {{ic|timeout}} – menu timeout in seconds. If this is not set, the menu will only be shown on key press during boot.
  
* {{ic|timeout}} – menu timeout in seconds. If this is not set, the menu will only be shown when you hold the space key while booting.
+
* {{ic|editor}} – whether to enable the kernel parameters editor or not. {{ic|1}} (default) is enabled, {{ic|0}} is disabled; since the user can add {{ic|1=init=/bin/bash}} to bypass root password and gain root access, it is strongly recommended to set this option to {{ic|0}}.
  
 
Example:
 
Example:
  
{{hc|$esp/loader/loader.conf|
+
{{hc|''esp''/loader/loader.conf|
 
default  arch
 
default  arch
 
timeout  4
 
timeout  4
 +
editor  0
 
}}
 
}}
  
Note that both options can be changed in the boot menu itself, which will store them as EFI variables.
+
{{Note|The first 2 options can be changed in the boot menu itself and changes will be stored as EFI variables.}}
  
{{Note|If no timeout is configured, which is the default setting, and no key pressed during bootup, the default entry is executed right away.}}
+
{{Tip|A basic configuration file example is located at {{ic|/usr/share/systemd/bootctl/loader.conf}}.}}
  
 
=== Adding boot entries ===
 
=== Adding boot entries ===
  
Gummiboot searches for boot menu items in {{ic|$esp/loader/entries/*.conf}} – each file found must contain exactly one boot entry. The possible options are:
+
{{Note|
 +
* ''bootctl'' will automatically check for "'''Windows Boot Manager'''" ({{ic|\EFI\Microsoft\Boot\Bootmgfw.efi}}), "'''EFI Shell'''" ({{ic|\shellx64.efi}}) and "'''EFI Default Loader'''" ({{ic|\EFI\Boot\bootx64.efi}}) at boot time. When detected, corresponding entries with titles {{ic|auto-windows}}, {{ic|auto-efi-shell}} and {{ic|auto-efi-default}}, respectively, will be automatically 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.
 +
* If you dual-boot Windows, it is strongly recommended to disable its default [[Dual boot with Windows#Fast_Start-Up|Fast Start-Up]] option.
 +
* Remember to load the intel [[microcode]] with {{ic|initrd}} if applicable.
 +
* You can find the {{ic|PARTUUID}} for your root partition with the command {{ic|1=blkid -s PARTUUID -o value /dev/sd''xY''}}, where {{ic|''x''}} is the device letter and {{ic|''Y''}} is the partition number. This is required only for your root partition, not {{ic|''esp''}}.}}
 +
 
 +
''bootctl'' searches for boot menu items in {{ic|''esp''/loader/entries/*.conf}} – each file found must contain exactly one boot entry. The possible options are:
  
 
* {{ic|title}} – operating system name. '''Required.'''
 
* {{ic|title}} – operating system name. '''Required.'''
Line 53: Line 115:
 
* {{ic|machine-id}} – machine identifier from {{ic|/etc/machine-id}}, shown only when multiple entries with same title and version exist. Optional.
 
* {{ic|machine-id}} – machine identifier from {{ic|/etc/machine-id}}, shown only when multiple entries with same title and version exist. Optional.
  
* {{ic|efi}} – EFI program to start, relative to your ESP ({{ic|$esp}}); e.g. {{ic|/vmlinuz-linux}}. Either this or {{ic|linux}} (see below) is '''required.'''
+
* {{ic|efi}} – EFI program to start, relative to your ESP ({{ic|''esp''}}); e.g. {{ic|/vmlinuz-linux}}. Either this or {{ic|linux}} (see below) is '''required.'''
  
* {{ic|options}} – Command-line options to pass to the EFI program. Optional, but you will need at least {{ic|1=initrd=''efipath''}} and {{ic|1=root=''dev''}} if booting Linux.
+
* {{ic|options}} – command line options to pass to the EFI program or kernel boot parameters. Optional, but you will need at least {{ic|1=initrd=''efipath''}} and {{ic|1=root=''dev''}} if booting Linux.
  
For Linux, you can specify {{ic|linux ''path-to-vmlinuz''}} and {{ic|initrd ''path-to-initramfs''}}; this will be automatically translated to {{ic|efi ''path''}} and {{ic|1=options initrd=''path''}} – this syntax is only supported for convenience and has no differences in function.
+
For Linux, you can specify {{ic|linux ''path-to-vmlinuz''}} and {{ic|initrd ''path-to-initramfs''}}; this will be automatically translated to {{ic|efi ''path''}} and {{ic|1=options initrd=''path''}} – this syntax is only supported for convenience and has no differences in function.  
  
An example entry for Arch Linux:
+
==== Standard root installations ====
  
{{hc|$esp/loader/entries/arch.conf|2=
+
Here is an example entry for a root partition without LVM or LUKS:
 +
 
 +
{{hc|''esp''/loader/entries/arch.conf|2=
 
title          Arch Linux
 
title          Arch Linux
 
linux          /vmlinuz-linux
 
linux          /vmlinuz-linux
Line 68: Line 132:
 
}}
 
}}
  
Please note in the example above that PARTUUID/PARTLABEL identifies a GPT partition, and differs from UUID/LABEL, which identifies a filesystem. Using the PARTUUID/PARTLABEL is advantageous because it is invariant if you reformat the partition with another filesystem. It's also useful if you don't have a filesystem on the partition (or use LUKS, which doesn't support LABELs).
+
Please note in the example above that {{ic|PARTUUID}}/{{ic|PARTLABEL}} identifies a GPT partition, and differs from {{ic|UUID}}/{{ic|LABEL}}, which identifies a filesystem. Using the {{ic|PARTUUID}}/{{ic|PARTLABEL}} is advantageous because it is invariant (i.e. unchanging) if you reformat the partition with another filesystem, or if the {{ic|/dev/sd* }}mapping changed for some reason. It is also useful if you do not have a filesystem on the partition (or use LUKS, which does not support {{ic|LABEL}}s).
 +
 
 +
{{Tip|An example entry file is located at {{ic|/usr/share/systemd/bootctl}}.}}
 +
 
 +
==== LVM root installations ====
 +
 
 +
{{Warning|''systemd-boot'' cannot be used without a separate {{ic|/boot}} filesystem outside of LVM.}}
 +
 
 +
Here is an example for a root partition using [[LVM|Logical Volume Management]]:
 +
 
 +
{{hc|''esp''/loader/entries/arch-lvm.conf|2=
 +
title          Arch Linux (LVM)
 +
linux          /vmlinuz-linux
 +
initrd        /initramfs-linux.img
 +
options        root=/dev/mapper/<VolumeGroup-LogicalVolume> rw
 +
}}
 +
 
 +
Replace {{ic|<VolumeGroup-LogicalVolume>}} with the actual VG and LV names (e.g. {{ic|1=root=/dev/mapper/volgroup00-lvolroot}}). Alternatively, it is also possible to use a UUID instead:
 +
....
 +
options  root=UUID=<UUID identifier> rw
 +
 
 +
Note that {{ic|1=root='''UUID'''=}} is used instead of {{ic|1=root='''PARTUUID'''=}}, which is used for Root partitions without LVM or LUKS.
 +
 
 +
==== Encrypted Root Installations ====
 +
 
 +
Here is an example configuration file for an encrypted root partition ([[Dm-crypt|DM-Crypt / LUKS]]) using the {{ic|encrypt}} [[mkinitcpio]] hook:
 +
 
 +
{{hc|''esp''/loader/entries/arch-encrypted.conf|2=
 +
title Arch Linux Encrypted
 +
linux /vmlinuz-linux
 +
initrd /initramfs-linux.img
 +
options cryptdevice=UUID=<UUID>:<mapped-name> root=/dev/mapper/<mapped-name> quiet rw
 +
}}
 +
 
 +
UUID is used in this example; {{ic|PARTUUID}} should be able to replace the UUID, if so desired. You may also replace the {{ic|/dev}} path with a regular UUID. {{ic|mapped-name}} is whatever you want it to be called. See [[Dm-crypt/System configuration#Boot loader]].
 +
 
 +
If you are using LVM, your cryptdevice line will look like this:
 +
 
 +
{{hc|''esp''/loader/entries/arch-encrypted-lvm.conf|2=
 +
title Arch Linux Encrypted LVM
 +
linux /vmlinuz-linux
 +
initrd /initramfs-linux.img
 +
options cryptdevice=UUID=<UUID>:MyVolGroup root=/dev/mapper/MyVolGroup-MyVolRoot quiet rw
 +
}}
  
 
You can also add other EFI programs such as {{ic|\EFI\arch\grub.efi}}.
 
You can also add other EFI programs such as {{ic|\EFI\arch\grub.efi}}.
  
{{Note|Gummiboot will automatically check for "'''Windows Boot Manager'''" ({{ic|\EFI\Microsoft\Boot\Bootmgfw.efi}}), "'''EFI Shell'''" ({{ic|\shellx64.efi}}) and "'''EFI Default Loader'''" ({{ic|\EFI\Boot\bootx64.efi}}), and display entries for them if they are present, so you don't have to manually create entries for them. However it does not autodetect other EFI applications (unlike rEFInd), so for booting the kernel, manual config entries must be created as mentioned above.}}
+
==== btrfs subvolume root installations ====
 +
 
 +
If booting a [[btrfs]] subvolume as root, amend the {{ic|options}} line with {{ic|rootflags<nowiki>=</nowiki>subvol<nowiki>=</nowiki><root subvolume>}}. In the example below, root has been mounted as a btrfs subvolume called 'ROOT' (e.g. {{ic|mount -o subvol<nowiki>=</nowiki>ROOT /dev/sdxY /mnt}}):
 +
 
 +
{{hc|''esp''/loader/entries/arch-btrfs-subvol.conf|2=
 +
title          Arch Linux
 +
linux          /vmlinuz-linux
 +
initrd        /initramfs-linux.img
 +
options        root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 rw rootflags<nowiki>=</nowiki>subvol<nowiki>=</nowiki>ROOT
 +
}}
 +
 
 +
A failure to do so will otherwise result in the following error message: {{ic|ERROR: Root device mounted successfully, but /sbin/init does not exist.}}
 +
 
 +
==== ZFS root installations ====
 +
 
 +
When booting from a [[ZFS]] dataset, add {{ic|zfs<nowiki>=</nowiki><root dataset>}} to the {{ic|options}} line. Here the root dataset has been set to 'zroot/ROOT/default':
 +
 
 +
{{hc|''esp''/loader/entries/arch-zfs.conf|2=
 +
title          Arch Linux ZFS
 +
linux          /vmlinuz-linux
 +
initrd        /initramfs-linux.img
 +
options        zfs=zroot/ROOT/default rw
 +
}}
 +
 
 +
When booting off of a ZFS dataset ensure that it has had the {{ic|bootfs}} property set with {{ic| zpool set bootfs<nowiki>=</nowiki><root dataset> <zpool>}}.
  
== Inside the boot menu ==
+
==== EFI Shells or other EFI apps ====
  
=== Keys ===
+
In case you installed EFI shells and other EFI application into the ESP, you can use the following snippets:
 +
 
 +
{{hc|''esp''/loader/entries/uefi-shell-v1-x86_64.conf|2=
 +
title  UEFI Shell x86_64 v1
 +
efi    /EFI/shellx64_v1.efi
 +
}}
 +
 
 +
{{hc|''esp''/loader/entries/uefi-shell-v2-x86_64.conf|2=
 +
title  UEFI Shell x86_64 v2
 +
efi    /EFI/shellx64_v2.efi
 +
}}
 +
 
 +
{{Expansion|Add example on how to boot into EFI firmware setup.}}
 +
 
 +
=== Support hibernation ===
 +
 
 +
See [[Suspend and hibernate]].
 +
 
 +
=== Kernel parameters editor with password protection ===
 +
 
 +
Alternatively you can install {{AUR|systemd-boot-password}} which supports {{ic|password}} basic configuration option. Use {{ic|sbpctl generate}} to generate a value for this option.
 +
 
 +
Install ''systemd-boot-password'' with the following command:
 +
 
 +
{{bc|1=# sbpctl install ''esp''}}
 +
 
 +
With enabled editor you will be prompted for your password before you can edit kernel parameters.
 +
 
 +
== Keys inside the boot menu ==
  
 
The following keys are used inside the menu:
 
The following keys are used inside the menu:
Line 84: Line 243:
 
* {{ic|-/T}} - decrease the timeout (stored in a non-volatile EFI variable)
 
* {{ic|-/T}} - decrease the timeout (stored in a non-volatile EFI variable)
 
* {{ic|+/t}} - increase the timeout (stored in a non-volatile EFI variable)
 
* {{ic|+/t}} - increase the timeout (stored in a non-volatile EFI variable)
* {{ic|e}} - edit the kernel command line
+
* {{ic|e}} - edit the kernel command line. It has no effect if the {{ic|editor}} config option is set to {{ic|0}}.
 
* {{ic|v}} - show the gummiboot and UEFI version
 
* {{ic|v}} - show the gummiboot and UEFI version
 
* {{ic|Q}} - quit
 
* {{ic|Q}} - quit
Line 103: Line 262:
 
=== Manual entry using efibootmgr ===
 
=== Manual entry using efibootmgr ===
  
If {{ic|gummiboot install}} command failed, you can create a EFI boot entry manually using {{ic|efibootmgr}} utility:
+
If {{ic|bootctl install}} command failed, you can create a EFI boot entry manually using {{Pkg|efibootmgr}}:
 +
 
 +
# efibootmgr -c -d /dev/sdX -p Y -l /EFI/systemd/systemd-bootx64.efi -L "Linux Boot Manager"
 +
 
 +
where {{ic|/dev/sdXY}} is the [[EFI System Partition]].
  
# efibootmgr -c -d /dev/sdX -p Y -l /EFI/gummiboot/gummibootx64.efi -L "Gummiboot"
+
=== Menu does not appear after Windows upgrade ===
  
where {{ic|/dev/sdXY}} is the EFISYS partition.
+
See [[UEFI#Windows changes boot order]].
  
== References ==
+
== See also ==
  
* http://freedesktop.org/wiki/Software/gummiboot/
+
* http://www.freedesktop.org/wiki/Software/systemd/systemd-boot/

Latest revision as of 06:05, 23 June 2017

systemd-boot, previously called gummiboot, is a simple UEFI boot manager which executes configured EFI images. The default entry is selected by a configured pattern (glob) or an on-screen menu. It is included with systemd, which is installed on Arch system by default.

It is simple to configure but it can only start EFI executables such as the Linux kernel EFISTUB, UEFI Shell, GRUB, the Windows Boot Manager.

Installation

EFI boot

  1. Make sure you are booted in UEFI mode.
  2. Verify your EFI variables are accessible.
  3. Mount your EFI System Partition (ESP) properly. esp is used to denote the mountpoint in this article.
    Note: systemd-boot cannot load EFI binaries from other partitions. It is therefore recommended to mount your ESP to /boot. In case you want to separate /boot from the ESP see #Manually for more information.
  4. If the ESP is not mounted at /boot, then copy your kernel and initramfs onto that ESP.
    Note: For a way to automatically keep the kernel updated on the ESP, have a look at EFISTUB#Using systemd for some systemd units that can be adapted. If your EFI System Partition is using automount, you may need to add vfat to a file in /etc/modules-load.d/ to ensure the current running kernel has the vfat module loaded at boot, before any kernel update happens that could replace the module for the currently running version making the mounting of /boot/efi impossible until reboot.
  5. Type the following command to install systemd-boot:
    # bootctl --path=esp install
    It will copy the systemd-boot binary to your EFI System Partition (esp/EFI/systemd/systemd-bootx64.efi and esp/EFI/Boot/BOOTX64.EFI – both of which are identical – on x86-64 systems) and add systemd-boot itself as the default EFI application (default boot entry) loaded by the EFI Boot Manager.
  6. Finally you must configure the boot loader to function properly.

BIOS boot

Warning: This is not recommended.

You can successfully install systemd-boot if booted with in BIOS mode. 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 ( or systemd-bootia32.efi depending if your system firmware is 32 bit).

Note: the firmware interface of Dell Latitude series provides everything you need to setup EFI boot but the EFI Shell won't be able to write to the computer's ROM.

Updating

Unlike the previous separate gummiboot package, which updated automatically on a new package release with a post_install script, updates of new systemd-boot versions must now be done manually by the user. However the procedure can be automated using pacman hooks.

Manually

systemd-boot (bootctl(1), systemd-efi-boot-generator(8)) assumes that your EFI System Partition is mounted on /boot.

# bootctl update

If the ESP is not mounted on /boot, the --path= option can pass it. For example:

# bootctl --path=esp update
Note: This is also the command to use when migrating from gummiboot, before removing that package. If that package has already been removed, however, run bootctl --path=esp install.

Automatically

The AUR 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, place the following pacman hook in the /etc/pacman.d/hooks/ directory:

/etc/pacman.d/hooks/systemd-boot.hook
[Trigger]
Type = Package
Operation = Upgrade
Target = systemd

[Action]
Description = Updating systemd-boot...
When = PostTransaction
Exec = /usr/bin/bootctl update

Configuration

Basic configuration

The basic configuration is stored in esp/loader/loader.conf file and it is composed by three options:

  • default – default entry to select (without the .conf suffix); can be a wildcard like arch-*.
  • timeout – menu timeout in seconds. If this is not set, the menu will only be shown on key press during boot.
  • editor – whether to enable the kernel parameters editor or not. 1 (default) is enabled, 0 is disabled; since the user can add init=/bin/bash to bypass root password and gain root access, it is strongly recommended to set this option to 0.

Example:

esp/loader/loader.conf
default  arch
timeout  4
editor   0
Note: The first 2 options can be changed in the boot menu itself and changes will be stored as EFI variables.
Tip: A basic configuration file example is located at /usr/share/systemd/bootctl/loader.conf.

Adding boot entries

Note:
  • bootctl will automatically check for "Windows Boot Manager" (\EFI\Microsoft\Boot\Bootmgfw.efi), "EFI Shell" (\shellx64.efi) and "EFI Default Loader" (\EFI\Boot\bootx64.efi) at boot time. When detected, corresponding entries with titles auto-windows, auto-efi-shell and auto-efi-default, respectively, will be automatically 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.
  • If you dual-boot Windows, it is strongly recommended to disable its default Fast Start-Up option.
  • Remember to load the intel microcode with initrd if applicable.
  • You can find the PARTUUID for your root partition with the command blkid -s PARTUUID -o value /dev/sdxY, where x is the device letter and Y is the partition number. This is required only for your root partition, not esp.

bootctl searches for boot menu items in esp/loader/entries/*.conf – each file found must contain exactly one boot entry. The possible options are:

  • title – operating system name. Required.
  • version – kernel version, shown only when multiple entries with same title exist. Optional.
  • machine-id – machine identifier from /etc/machine-id, shown only when multiple entries with same title and version exist. Optional.
  • efi – EFI program to start, relative to your ESP (esp); e.g. /vmlinuz-linux. Either this or linux (see below) is required.
  • options – command line options to pass to the EFI program or kernel boot parameters. Optional, but you will need at least initrd=efipath and root=dev if booting Linux.

For Linux, you can specify linux path-to-vmlinuz and initrd path-to-initramfs; this will be automatically translated to efi path and options initrd=path – this syntax is only supported for convenience and has no differences in function.

Standard root installations

Here is an example entry for a root partition without LVM or LUKS:

esp/loader/entries/arch.conf
title          Arch Linux
linux          /vmlinuz-linux
initrd         /initramfs-linux.img
options        root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 rw

Please note in the example above that PARTUUID/PARTLABEL identifies a GPT partition, and differs from UUID/LABEL, which identifies a filesystem. Using the PARTUUID/PARTLABEL is advantageous because it is invariant (i.e. unchanging) if you reformat the partition with another filesystem, or if the /dev/sd* mapping changed for some reason. It is also useful if you do not have a filesystem on the partition (or use LUKS, which does not support LABELs).

Tip: An example entry file is located at /usr/share/systemd/bootctl.

LVM root installations

Warning: systemd-boot cannot be used without a separate /boot filesystem outside of LVM.

Here is an example for a root partition using Logical Volume Management:

esp/loader/entries/arch-lvm.conf
title          Arch Linux (LVM)
linux          /vmlinuz-linux
initrd         /initramfs-linux.img
options        root=/dev/mapper/<VolumeGroup-LogicalVolume> rw

Replace <VolumeGroup-LogicalVolume> with the actual VG and LV names (e.g. root=/dev/mapper/volgroup00-lvolroot). Alternatively, it is also possible to use a UUID instead:

....
options  root=UUID=<UUID identifier> rw

Note that root=UUID= is used instead of root=PARTUUID=, which is used for Root partitions without LVM or LUKS.

Encrypted Root Installations

Here is an example configuration file for an encrypted root partition (DM-Crypt / LUKS) using the encrypt mkinitcpio hook:

esp/loader/entries/arch-encrypted.conf
title Arch Linux Encrypted
linux /vmlinuz-linux
initrd /initramfs-linux.img
options cryptdevice=UUID=<UUID>:<mapped-name> root=/dev/mapper/<mapped-name> quiet rw

UUID is used in this example; PARTUUID should be able to replace the UUID, if so desired. You may also replace the /dev path with a regular UUID. mapped-name is whatever you want it to be called. See Dm-crypt/System configuration#Boot loader.

If you are using LVM, your cryptdevice line will look like this:

esp/loader/entries/arch-encrypted-lvm.conf
title Arch Linux Encrypted LVM
linux /vmlinuz-linux
initrd /initramfs-linux.img
options cryptdevice=UUID=<UUID>:MyVolGroup root=/dev/mapper/MyVolGroup-MyVolRoot quiet rw

You can also add other EFI programs such as \EFI\arch\grub.efi.

btrfs subvolume root installations

If booting a btrfs subvolume as root, amend the options line with rootflags=subvol=<root subvolume>. In the example below, root has been mounted as a btrfs subvolume called 'ROOT' (e.g. mount -o subvol=ROOT /dev/sdxY /mnt):

esp/loader/entries/arch-btrfs-subvol.conf
title          Arch Linux
linux          /vmlinuz-linux
initrd         /initramfs-linux.img
options        root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 rw rootflags=subvol=ROOT

A failure to do so will otherwise result in the following error message: ERROR: Root device mounted successfully, but /sbin/init does not exist.

ZFS root installations

When booting from a ZFS dataset, add zfs=<root dataset> to the options line. Here the root dataset has been set to 'zroot/ROOT/default':

esp/loader/entries/arch-zfs.conf
title          Arch Linux ZFS
linux          /vmlinuz-linux
initrd         /initramfs-linux.img
options        zfs=zroot/ROOT/default rw

When booting off of a ZFS dataset ensure that it has had the bootfs property set with zpool set bootfs=<root dataset> <zpool>.

EFI Shells or other EFI apps

In case you installed EFI shells and other EFI application into the ESP, you can use the following snippets:

esp/loader/entries/uefi-shell-v1-x86_64.conf
title  UEFI Shell x86_64 v1
efi    /EFI/shellx64_v1.efi
esp/loader/entries/uefi-shell-v2-x86_64.conf
title  UEFI Shell x86_64 v2
efi    /EFI/shellx64_v2.efi

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Add example on how to boot into EFI firmware setup. (Discuss in Talk:Systemd-boot#)

Support hibernation

See Suspend and hibernate.

Kernel parameters editor with password protection

Alternatively you can install systemd-boot-passwordAUR which supports password 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.

Keys inside the boot menu

The following keys are used inside the menu:

  • Up/Down - select entry
  • Enter - boot the selected entry
  • d - select the default entry to boot (stored in a non-volatile EFI variable)
  • -/T - decrease the timeout (stored in a non-volatile EFI variable)
  • +/t - increase the timeout (stored in a non-volatile EFI variable)
  • e - edit the kernel command line. It has no effect if the editor config option is set to 0.
  • v - show the gummiboot and UEFI version
  • Q - quit
  • P - print the current configuration
  • h/? - help

These hotkeys will, when pressed inside the menu or during bootup, directly boot a specific entry:

  • l - Linux
  • w - Windows
  • a - OS X
  • s - EFI Shell
  • 1-9 - number of entry

Troubleshooting

Manual entry using efibootmgr

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

# efibootmgr -c -d /dev/sdX -p Y -l /EFI/systemd/systemd-bootx64.efi -L "Linux Boot Manager"

where /dev/sdXY is the EFI System Partition.

Menu does not appear after Windows upgrade

See UEFI#Windows changes boot order.

See also