Bootloaders
A bootloader, is a computer program that is responsible for booting a computer. If it also provides an interactive menu with multiple boot choices then it's often called a boot manager. This page shows the basic steps you need to perform, if you for any reason want to switch bootloaders or apply some manual configuration.
The following bootloaders are available in Alpine Linux.
Syslinux
is the default light-weight bootloader used in Alpine.rEFInd
is an easy to use EFI boot menu that allows booting different operating systems.GRUB
is a standard linux boot loader.EFI Boot Stub
allows booting linux directly from a motherboard supporting UEFI or another bootloader.- Gummiboot can be used for UEFI Secure Boot.
rEFInd
For (U)EFI systems, the refind package can provide a graphical EFI boot menu that allows to boot operating systems that are found on the available partitions. As of now, refind is available in the testing repository. It can be safely installed by following the guidelines.
The below command installs the alpine-linux refind package:
# apk add refind@testing
The below command installs refind to the EFI partition
# refind-install --alldrivers
The --alldrivers
option includes all filesystem drivers instead of only the one needed to load the currently running kernel, to allow finding and booting operating systems from more partitions.
The above steps should be sufficient for most cases to start using refind as boot loader. The refind utility currently does not have Alpine Linux icon file. You can place this icon file in /boot/efi/EFI/refind/icons/ or /boot/EFI/refind/icons/ folder.
Proceed to below steps only if rebooting did not result in refind appearing as boot loader.
Manual configuration
And a first (default) boot menu line needs to be configured with Alpine's default boot parameters. Assuming the bootable partition is mounted at /media/sdXY it can be done like this (at time of writing):
# echo '"Alpine" "modules=loop,squashfs,sd-mod,usb-storage quiet initrd=\boot\intel-ucode.img initrd=\boot\amd-ucode.img initrd=\boot\initramfs-lts"' > /media/sdXY/boot/refind_linux.conf
The path in the config file needs to be relative to the partition that the kernel resides on. If /boot resides on its own separate partition, then
\boot
needs to be removed from the paths.There is also a second config file, refind.conf which is located inside the EFI partition. The config file is self-explanatory and has to be manually edited. Refer refind website as it is extremely rich in information.
To allow multiple linux installations to co-exist, it is better to keep the /boot folder (where kernel files reside) inside the "/" root partition and let it be mounted inside the efi/esp partition as shown:
Contents of /etc/fstab
If you're esp partition is mounted different from above setup, adjust the path in below files accordingly.
For default alpine sys mode installation, a sample refind.conf to dual boot Alpine Linux and windows will be:
Contents of /boot/efi/EFI/refind/refind.conf
If you use btrfs filesystem, for the above /etc/fstab setup, the necessary boot entry for Alpine Linux is as follows:
Contents of /boot/efi/EFI/refind/refind.conf
Syslinux
If you want to switch from another bootloader back to Syslinux, or if you for some reason want to install Syslinux manually, the following steps are required.
Install the syslinux package:
# apk add syslinux
If you're using GPT partitions, install the GPT MBR onto the drive you want to install the bootloader on (in this case /dev/sda):
# dd bs=440 count=1 conv=notrunc if=/usr/share/syslinux/gptmbr.bin of=/dev/sda
Or if you're using DOS partitions, install the DOS MBR instead:
# dd bs=440 count=1 conv=notrunc if=/usr/share/syslinux/mbr.bin of=/dev/sda
Next install the required Syslinux binaries. Despite being called extlinux
, Syslinux supports booting from FAT12/16/32, NTFS, ext2/3/4, btrfs, XFS, and UFS/FFS filesystems.
# extlinux --install /boot
The configuration file is located in /boot/extlinux.conf.
Alpine ships with a script update-extlinux
which automatically (re)generates this file, for example on updates to Syslinux. The settings for this script can be found in /etc/update-extlinux.conf, including the option to disable automatic overwriting of /boot/extlinux.conf.
You can also place additional menu entries in the /etc/update-extlinux.d/ directory, e.g. for dual booting.
Using EFI with syslinux
Alpine Linux installer automatically uses Grub, if EFI mode is detected. The below section is specifically about using EFI with syslinux:
Assuming /mnt is a FAT32 partition of type EF00 and /boot belongs to the rootfs created after running setup-disk
:
# mkdir -p /mnt/EFI/syslinux # cp /usr/share/syslinux/efi64/* /mnt/EFI/syslinux/ # cp /boot/extlinux.conf /mnt/EFI/syslinux/syslinux.cfg # cp /boot/vmlinuz* /mnt/EFI/syslinux/ # cp /boot/initramfs* /mnt/EFI/syslinux/
You may need to modify /mnt/EFI/syslinux/syslinux.cfg to change the paths to absolute paths (just add a / in front of the vmlinuz/initramfs entries), or copy the files to /mnt/EFI/syslinux instead (XXX: untested).
At the end, the file /mnt/EFI/syslinux/syslinux.cfg should look like this:
Contents of /mnt/EFI/syslinux/syslinux.cfg
And finally, add syslinux to EFI boot menu (assuming /dev/sda is your hard drive)
# apk add efibootmgr # efibootmgr -c -d /dev/sda -p 1 -l \\EFI\\syslinux\\syslinux.efi -L "ALPINE-SYSLINUX"
You can now verify that the boot entry has been added
efibootmgr
BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0001,0000,0002,... Boot001* ALPINE-SYSLINUX HD(1,GPT,xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)/FILE(\EFI\syslinux\syslinux.efi)
GRUB
To install GRUB in BIOS mode, (optionally) remove the Syslinux package and install the required GRUB packages:
# apk del syslinux # apk add grub grub-bios
For EFI, install GRUB's EFI package instead. Note that /boot has to be an EFI compatible filesystem like FAT32.
# apk add grub-efi efibootmgr
Next install the MBR and GRUB binaries to disk for BIOS mode:
# grub-install /dev/vda
For EFI mode:
# grub-install --target=x86_64-efi --efi-directory=/boot
then add this line to /etc/default/grub:
Contents of /etc/default/grub
GRUB ships with an automatic config generator, including some automatic detection of other operating systems installed on the device:
# grub-mkconfig -o /boot/grub/grub.cfg
This script can be configured via the /etc/default/grub file. See [1] for a list of available options.
EFI Boot Stub
To boot directly from your motherboard's UEFI boot menu, a boot entry needs to be created with either a UEFI shell or efibootmgr.
efibootmgr
Install efibootmgr:
# apk add efibootmgr
Create a boot entry. It's recommended to do this in a script, as efibootmgr does not allow editing entries.
Contents of add-bootentry
Where /dev/sdXY contains the EFI partition and /dev/sdXZ contains the root partition. If you are using linux-edge, replace lts
with edge
in the script
The kernel contains the exhaustive list of ways to specify the block device. For a more robust boot entry, it is recommended to use a persistent name such as the PARTUUID.
Optionally, set the newly created entry as the default:
# efibootmgr -n XXXX
Where XXXX
is the boot number of the new entry.
Using a UKI
Unified Kernel Image (UKI) is supported in UEFI only. It is possible to boot directly into a UKI. A UKI is a single file which contains the initfs, kernel and cmdline. While this is typically done in order to enable SecureBoot, it is perfectly feasible to skip enrolling the custom keys and leave SecureBoot off.
The page UEFI Secure Boot contains the instructions for setting an a UKI. Additionally, it is possible to install the UKI in the default fallback path used by most UEFI implementations. By installing the UKI into this path, the system will automatically boot into it if no other entries are defined. This can be automated as part of the kernel hook by adding the following to /etc/kernel-hooks.d/secureboot.conf
Contents of /etc/kernel-hooks.d/secureboot.conf
bootx64.efi is only correct for x86_64
systems. For other architectures the exact name will vary.