Difference between revisions of "Systemd-boot"
(point to AUR) |
m (→Adding boot entries: Add note) |
||
(35 intermediate revisions by 12 users not shown) | |||
Line 1: | Line 1: | ||
− | + | [[Category:Boot loaders]] | |
− | + | [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 (with CONFIG_EFI_STUB enabled), grub.efi, and such. | |
− | [http://freedesktop.org/wiki/Software/gummiboot Gummiboot] is a | ||
− | |||
− | |||
− | |||
− | |||
== Installing == | == Installing == | ||
+ | {{Note|gummiboot assumes that your EFI System Partition is mounted on {{ic|/boot}}. If your ESP is mounted on {{ic|/boot/efi}} you have to call the following gummiboot install command with the additional {{ic|--path}} switch. This also means that gummiboot will not be able to update itself automatically and you will have to call {{ic|gummiboot --path /boot/efi 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. The rest of this article will assume that your ESP is mounted on {{ic|/boot}}.}} | ||
− | Install {{ | + | Install {{Pkg|gummiboot}} from [extra] and run the following to install gummiboot: |
− | + | # gummiboot install | |
− | + | This will automatically copy the gummiboot binary to your EFI System Partition and create a boot entry in the EFI Boot Manager. However, creating the boot entry requires that you are already running in EFI mode and are running kernel 3.8. If you are still running kernel 3.7 or have not booted in EFI mode, 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|/boot/EFI/BOOT/BOOTX64.EFI}} on x64 systems). Note that the installing process only has to be done once, updating will happen automatically. | |
− | # install | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Configuring == | == Configuring == | ||
− | The basic configuration is kept in {{ic| | + | The basic configuration is kept in {{ic|/boot/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 | + | * {{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. |
Example: | Example: | ||
− | {{hc| | + | {{hc|/boot/loader/loader.conf| |
default arch | default arch | ||
timeout 4 | timeout 4 | ||
Line 43: | Line 27: | ||
== Adding boot entries == | == Adding boot entries == | ||
− | + | Gummiboot searches for boot menu items in {{ic|/boot/loader/entries/*.conf}} – each file found must contain exactly one boot entry. The possible options are: | |
− | |||
− | |||
− | |||
− | |||
− | Gummiboot searches for boot menu items in {{ic| | ||
* {{ic|title}} – operating system name. '''Required.''' | * {{ic|title}} – operating system name. '''Required.''' | ||
− | * {{ic| | + | * {{ic|version}} – kernel version, shown only when multiple entries with same title exist. Optional. |
− | * {{ic| | + | * {{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; e.g. {{ic| | + | * {{ic|efi}} – EFI program to start, relative to your ESP ({{ic|/boot}}); 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. 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. | ||
An example entry for Arch Linux: | An example entry for Arch Linux: | ||
− | {{hc| | + | {{hc|/boot/loader/entries/arch.conf|2= |
title Arch Linux | title Arch Linux | ||
− | + | linux /vmlinuz-linux | |
− | + | initrd /initramfs-linux.img | |
− | + | options root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 ro | |
− | |||
}} | }} | ||
− | + | You can also add other EFI programs such as {{ic|\EFI\arch\grub.efi}}. | |
− | + | {{Note|Gummiboot will automatically check for binaries of a Windows Installation ({{ic|\EFI\Microsoft\Boot\Bootmgfw.efi}}) or an UEFI Shell ({{ic|\shellx64.efi}}) and display entries for them, so you don't have to create these manually.}} | |
− | + | == Inside the boot menu == | |
− | |||
− | |||
− | |||
− | + | TODO: document keybindings from http://freedesktop.org/wiki/Software/gummiboot | |
− | + | ==Troubleshooting== | |
+ | ====Transferring to new HDD causes breakage==== | ||
+ | Twice now I have transferred my installation from one disk to another, ESP included, and both times this broke my gummiboot setup. With a lot of trial and error, I have discovered that gummiboot does not like configuration files that have been tranfserred from one disk to another (I used rsync). | ||
− | + | To solve this, delete the $ESP/loader directory and all of its contents, and recreate the necessary configuration files. | |
− | + | Though it has no additional info, here is my [https://bbs.archlinux.org/viewtopic.php?pid=1193147#p1193147 relevent forum thread]. |
Revision as of 06:09, 19 March 2013
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 (with CONFIG_EFI_STUB enabled), grub.efi, and such.
Contents
Installing
/boot
. If your ESP is mounted on /boot/efi
you have to call the following gummiboot install command with the additional --path
switch. This also means that gummiboot will not be able to update itself automatically and you will have to call gummiboot --path /boot/efi 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 /boot
if you use gummiboot. The rest of this article will assume that your ESP is mounted on /boot
.Install gummiboot from [extra] and run the following to install gummiboot:
# gummiboot install
This will automatically copy the gummiboot binary to your EFI System Partition and create a boot entry in the EFI Boot Manager. However, creating the boot entry requires that you are already running in EFI mode and are running kernel 3.8. If you are still running kernel 3.7 or have not booted in EFI mode, 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 (/boot/EFI/BOOT/BOOTX64.EFI
on x64 systems). Note that the installing process only has to be done once, updating will happen automatically.
Configuring
The basic configuration is kept in /boot/loader/loader.conf
, with just two possible configuration options:
-
default
– default entry to select (without the.conf
suffix); can be a wildcard likearch-*
-
timeout
– menu timeout in seconds. If this is not set, the menu will only be shown when you hold the space key while booting.
Example:
/boot/loader/loader.conf
default arch timeout 4
Note that both options can be changed in the boot menu itself, which will store them as EFI variables.
Adding boot entries
Gummiboot searches for boot menu items in /boot/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 (/boot
); e.g./vmlinuz-linux
. Either this orlinux
(see below) is required.
-
options
– Command-line options to pass to the EFI program. Optional, but you will need at leastinitrd=efipath
androot=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.
An example entry for Arch Linux:
/boot/loader/entries/arch.conf
title Arch Linux linux /vmlinuz-linux initrd /initramfs-linux.img options root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 ro
You can also add other EFI programs such as \EFI\arch\grub.efi
.
\EFI\Microsoft\Boot\Bootmgfw.efi
) or an UEFI Shell (\shellx64.efi
) and display entries for them, so you don't have to create these manually.TODO: document keybindings from http://freedesktop.org/wiki/Software/gummiboot
Troubleshooting
Transferring to new HDD causes breakage
Twice now I have transferred my installation from one disk to another, ESP included, and both times this broke my gummiboot setup. With a lot of trial and error, I have discovered that gummiboot does not like configuration files that have been tranfserred from one disk to another (I used rsync).
To solve this, delete the $ESP/loader directory and all of its contents, and recreate the necessary configuration files.
Though it has no additional info, here is my relevent forum thread.