24-05-2021

The Refind Binary File Is Missing Aborting Installation Manual

Manual installation. You can place a refind_linux.conf file containing the kernel parameters in the same. Copy the fwupx64.efi binary and firmware files to esp. Manual installation. Tip: rEFInd can boot Linux in many ways. You can place a refind_linux.conf file containing the kernel parameters in the same directory as your kernel. Place KeyTool EFI binary in esp/ or esp/EFI/tools/ with the name KeyTool.efi or KeyTool-signed.efi.

  1. The Refind Binary File Is Missing Aborting Installation Manual Free
  2. The Refind Binary File Is Missing Aborting Installation Manual Pdf

rEFInd is a UEFIboot manager capable of launching EFISTUB kernels. It is a fork of the no-longer-maintained rEFIt and fixes many issues with respect to non-Mac UEFI booting. It is designed to be platform-neutral and to simplify booting multiple OSes.

Note: In the entire article esp denotes the mountpoint of the EFI system partition aka ESP.
  • 2Installing the rEFInd Boot Manager
    • 2.1Installation with refind-install script
      • 2.1.1Secure Boot
        • 2.1.1.2Using shim
    • 2.3Upgrading
  • 3Configuration
    • 3.1Passing kernel parameters
      • 3.1.1For kernels automatically detected by rEFInd
  • 5Tools
    • 5.3Key management tools
  • 6Tips and tricks
  • 7Troubleshooting
    • 7.1Btrfs subvolume support

Installation

Install the refind-efi package.

Installing the rEFInd Boot Manager

rEFInd has read-only drivers for ReiserFS, Ext2, Ext4, Btrfs, ISO-9660, HFS+, and NTFS. Additionally rEFInd can use drivers from the UEFI firmware i.e. FAT (and HFS+ on Macs or ISO-9660 on some systems).

Note: Your kernel and initramfs must reside on a file system that rEFInd can read.

To find additional drivers see The rEFInd Boot Manager: Using EFI Drivers: Finding Additional EFI Drivers.

To use the rEFInd, you must install it to the EFI system partition either using the refind-install script or by copying the files and setting up the boot entry manually.

Installation with refind-install script

The rEFInd package includes the refind-install script to simplify the process of setting rEFInd as your default EFI boot entry. The script has several options for handling differing setups and UEFI implementations. See refind-install(8) or read the comments in the install script for explanations of the various installation options.

For many systems it should be sufficient to simply run:

This will attempt to find and mount your ESP, copy rEFInd files to esp/EFI/refind/, and use efibootmgr to make rEFInd the default EFI boot application.

Alternatively you can install rEFInd to the default/fallback boot path esp/EFI/BOOT/bootx64.efi. This is helpful for bootable USB flash drives or on systems that have issues with the NVRAM changes made by efibootmgr:

Where /dev/sdXY is your EFI system partition.

Note: By default refind-install installs only the driver for the file system on which kernel resides. Additional file systems need to be installed manually or you can install all drivers with the --alldrivers option. This is useful for bootable USB flash drives e.g.:

After installing rEFInd's files to the ESP, verify that rEFInd has created refind_linux.conf containing the required kernel parameters (e.g. root=) in the same directory as your kernel. If it has not created this file, you will need to set up #Passing kernel parameters manually or you will most likely get a kernel panic on your next boot.

By default, rEFInd will scan all of your drives (that it has drivers for) and add a boot entry for each EFI bootloader it finds, which should include your kernel (since Arch enables EFISTUB by default). So you may have a bootable system at this point.

Tip: It is always a good idea to edit the default configuration file esp/EFI/refind/refind.conf to ensure that the default options work for you.
Warning: When refind-install is run in chroot (e.g. in live system when installing Arch Linux) /boot/refind_linux.conf is populated with kernel options from the live system not the one on which it is installed. You will need to edit /boot/refind_linux.conf and adjust the kernel options manually. See #refind_linux.conf for an example.

Secure Boot

See Managing Secure Boot for Secure Boot support in rEFInd.

Using PreLoader

See Secure Boot#Set up PreLoader to acquire signed PreLoader.efi and HashTool.efi binaries.

Execute refind-install with the option --preloader /path/to/preloader

Next time you boot with Secure Boot enabled, HashTool will launch and you will need to enroll the hash of rEFInd (loader.efi), rEFInd's drivers (e.g. ext4_x64.efi) and kernel (e.g. vmlinuz-linux).

See refind-install(8) for more information.

Tip: The signed HashTool is only capable of accessing the partition it was launched from. This means if your kernel is not on the ESP, you will not be able to enroll its hash from HashTool. You can workaround this by using #KeyTool, since it is capable of enrolling a hash in MokList and is not limited to one partition. Remember to enroll KeyTool's hash before using it.
Using shim

Installshim-signedAUR. Read Secure Boot#shim, but skip all file copying.

Using hashes

To use only hashes with shim, execute refind-install with the option --shim /path/to/shim

Next time you boot with Secure Boot enabled, MokManager will launch and you will need to enroll the hash of rEFInd (grubx64.efi), rEFInd's drivers (e.g. ext4_x64.efi) and kernel (e.g. vmlinuz-linux).

Using Machine Owner Key

To sign rEFInd with a Machine Owner Key (MOK), install sbsigntools.

Tip: If you already have created a MOK, place the files in the directory /etc/refind.d/keys with the names refind_local.key (PEM format private key), refind_local.crt (PEM format certificate) and refind_local.cer (DER format certificate).

Execute refind-install with the options --shim /path/to/shim and --localkeys:

refind-install will create the keys for you and sign itself and its drivers. You will need to sign the kernel with the same key, e.g.:

Tip: The kernel signing can be automated with a pacman hook, e.g.:

Once in MokManager add refind_local.cer to MoKList. refind_local.cer can be found inside a directory called keys in the rEFInd's installation directory, e.g. esp/EFI/refind/keys/refind_local.cer.

See refind-install(8) for more information.

Using your own keys

Follow Secure Boot#Using your own keys to create keys.

Create directory /etc/refind.d/keys and place Signature Database (db) key and certificates in it. Name the files: refind_local.key (PEM format private key), refind_local.crt (PEM format certificate) and refind_local.cer (DER format certificate).

When running install script add option --localkeys, e.g.:

rEFInd EFI binaries will be signed with the supplied key and certificate.

Manual installation

Tip: rEFInd can boot Linux in many ways. See The rEFInd Boot Manager: Methods of Booting Linux for coverage of the various approaches.

If the refind-install script does not work for you, rEFInd can be set up manually.

First, copy the executable to the ESP:

If you want to install rEFInd to the default/fallback boot path replace esp/EFI/refind/ with esp/EFI/BOOT/ in the following instructions and copy rEFInd EFI executable to esp/EFI/BOOT/bootx64.efi:

Then use efibootmgr to create a boot entry in the UEFI NVRAM, where /dev/sdX and Y are the device and partition number of your EFI system partition. If you are installing rEFInd to the default/fallback boot path esp/EFI/BOOT/bootx64.efi, you can skip this step.

At this point, you should be able to reboot into rEFInd, but it will not be able to boot your kernel. If your kernel does not reside on your ESP, rEFInd can mount your partitions to find it - provided it has the right drivers.

rEFInd automatically loads all drivers from the subdirectories drivers and drivers_arch (e.g. drivers_x64) in its install directory.

Now rEFInd should have a boot entry for your kernel, but it will not pass the correct kernel parameters. Set up #Passing kernel parameters. You should now be able to boot your kernel using rEFInd. If you are still unable to boot or if you want to tweak rEFInd's settings, many options can be changed with a configuration file:

The sample configuration file is well commented and self-explanatory.

Unless you have set textonly in the configuration file, you should copy rEFInd's icons to get rid of the ugly placeholders:

You can try out different fonts by copying them and changing the font setting in refind.conf:

Tip: Pressing F10 in rEFInd will save a screenshot to the top level directory of the ESP.

Upgrading

Pacman updates the rEFInd files in /usr/share/refind/ and will not copy new files to the ESP for you. If refind-install worked for your original installation of rEFInd, you can rerun it to copy the updated files. The new configuration file will be copied as refind.conf-sample so that you can integrate changes into your existing configuration file using a diff tool. If your rEFInd required #Manual installation, you will need to figure out which files to copy yourself.

Pacman hook

You can automate the update process using a pacman hook:

Where the Exec= may need to be changed to the correct update command for your setup. If you did #Manual installation, you could create your own update script to call with the hook.

Tip: If you setup rEFInd with #Secure Boot, you may want to additionally add the option --yes to the refind-install command. It will prevent the command from failing if it gets executed when Secure Boot is disabled. See refind-install(8) for more information.

Configuration

The rEFInd configuration refind.conf is located in the same directory as the rEFInd EFI application (usually esp/EFI/refind or esp/EFI/BOOT). The default configuration file contains extensive comments explaining all its options, see Configuring the Boot Manager for more detailed explanations.

Passing kernel parameters

There are two methods for setting the kernel parameters that rEFInd will pass to the kernel.

For kernels automatically detected by rEFInd

For automatically detected kernels you can either specify the kernel parameters explicitly in /boot/refind_linux.conf or rely on rEFInd's ability to identify the root partition and kernel parameters. See Methods of Booting Linux: For Those With Foresight or Luck: The Easiest Method for more information.

Tip: rEFInd will automatically choose the Arch Linux icon (os_arch.png) for the boot entry when /etc/os-release is on the same partition as the kernel. If your /boot is a separate partition see Configuring the Boot Manager: Setting OS Icons.

For rEFInd to support the naming scheme of Arch Linux kernels and thus allow matching them with their respective initramfs images, you must uncomment and edit extra_kernel_version_strings option in refind.conf. E.g.:

Note:
  • rEFInd only supports detecting one initramfs image per kernel, meaning it will not detect fallback initramfs nor microcode images. They must be specified manually.
  • Without the above extra_kernel_version_strings line, the %v variable in refind_linux.conf will not work for Arch Linux kernels.
refind_linux.conf

If rEFInd automatically detects your kernel, you can place a refind_linux.conf file containing the kernel parameters in the same directory as your kernel. You can use /usr/share/refind/refind_linux.conf-sample as a starting point. The first uncommented line of refind_linux.conf will be the default parameters for the kernel. Subsequent lines will create entries in a submenu accessible using +, F2, or Insert.

Alternatively, try running mkrlconf as root. It will attempt to find your kernel in /boot and automatically generate refind_linux.conf. The script will only set up the most basic kernel parameters, so be sure to check the file it created for correctness.

If you do not specify an initrd= parameter, rEFInd will automatically add it by searching for common RAM disk filenames in the same directory as the kernel. If you need multiple initrd= parameters, you must specify them manually in refind_linux.conf. For example, a microcode passed before the initramfs:

The Refind Binary File Is Missing Aborting Installation Manual Free

Warning:initrd path is relative to the root of the file system on which the kernel resides. This could be initrd=/boot/initramfs-%v.img or, if /boot is a separate partition (e.g. the ESP), initrd=/initramfs-%v.img.
Note: rEFInd replaces %v in refind_linux.conf with the kernel's version (by extracting if from the file name). For rEFInd to support Arch Linux kernels, the extra_kernel_version_strings in esp/EFI/refind/refind.conf must be edited as instructed in #For kernels automatically detected by rEFInd.

The Refind Binary File Is Missing Aborting Installation Manual Pdf

Without configuration

This article or section needs expansion.

Reason: Add 'Full auto detection' using Discoverable Partitions Specification and /etc/fstab reading. (Discuss in Talk:REFInd#)

If you merely install rEFInd onto the ESP and launch it without any further ado (say via UEFI shell or KeyTool) you still get a menu to boot from via autodetection, with no configuration required whatsoever.

This is because rEFInd has a fallback mechanism that can:

  • Identify the root partition (for root= parameter ) via the Discoverable Partitions Specification or /etc/fstab.
  • Detect kernel options (ro or rw) from GPT partition attributes (using attribute 60 'read-only') or /etc/fstab.
Note: rEFInd does not support escape codes (e.g. for spaces) in /etc/fstab.
The refind binary file is missing aborting installation manual free

Manual boot stanzas

If your kernel is not autodetected, or if you simply want more control over the options for a menu entry, you can manually create boot entries using stanzas in refind.conf. Ensure that scanfor includes manual or these entries will not appear in rEFInd's menu. Kernel parameters are set with the options keyword. rEFInd will append the initrd= parameter using the file specified by the initrd keyword in the stanza. If you need additional initrds (e.g. for Microcode), you can specify them in options (and the one specified by the initrd keyword will be added to the end).

Manual boot stanzas are explained in Creating Manual Boot Stanzas.

It is likely that you will need to change volume to match either a filesystem's LABEL, a PARTLABEL, or a PARTUUID of the partition where the kernel image resides. See Persistent block device naming#by-label for examples of assigning a volume label. If volume is not specified it defaults to volume from which rEFInd was launched (typically EFI system partition).

Warning:loader and initrd paths are relative to the root of volume. If /boot is a separate partition (e.g. the ESP), the loader and initrd paths would be /vmlinuz-linux and /initramfs-linux.img, respectively.

Installation alongside an existing UEFI Windows installation

Note: The usual caveats of Dual boot with Windows apply.

rEFInd is compatible with the EFI system partition created by a UEFI Windows installation, so there is no need to create or format another FAT32 partition when installing Arch alongside Windows. Simply mount the existing ESP and install rEFInd as usual. By default, rEFInd's autodetection feature should recognize any existing Windows/recovery bootloaders.

Note: In some cases, Windows behaves differently (low resolution boot screen, OEM logo replaced by Windows logo, black screen after boot screen, artifacting). If you face such issues, try setting use_graphics_for +,windows in esp/EFI/refind/refind.conf or adding graphics on to the Windows boot stanza.

Tools

This article or section is a candidate for moving to Unified Extensible Firmware Interface.

Notes: Although rEFInd has a special interface for these common tools, they are not a feature of rEFInd. (Discuss in Talk:REFInd#template:move at refind#tools: to uefi)

rEFInd supports running various 3rd-party tools. Tools need to be installed separately. Edit showtools in refind.conf to choose which ones to show.

UEFI shell

See Unified Extensible Firmware Interface#UEFI Shell.

Copy shellx64.efi to the root of the EFI system partition.

Memtest86

Install memtest86-efiAUR and copy it to esp/EFI/tools/.

Key management tools

rEFInd can detect Secure Boot key management tools if they are placed in rEFInd's directory on ESP, esp/ or esp/EFI/tools/.

HashTool

Follow #Using PreLoader and HashTool.efi will be placed in rEFInd's directory.

MokManager

Follow #Using shim and MokManager will be placed in rEFInd's directory.

KeyTool

Install efitools.

Place KeyTool EFI binary in esp/ or esp/EFI/tools/ with the name KeyTool.efi or KeyTool-signed.efi.

See Secure Boot#Using KeyTool for instructions on signing KeyTool.efi.

GPT fdisk (gdisk)

Download the gdisk EFI application and copy gdisk_x64.efi to esp/EFI/tools/.

iPXE

This article or section is out of date.

Reason: iPXE is not packaged in refind-efi anymore. (Discuss in Talk:REFInd#)

refind-efi contains the iPXE UEFI binaries, you just need to copy them to esp/EFI/tools/.

fwupdate

Install and setup fwupd.

Copy the fwupx64.efi binary and firmware file to esp/EFI/tools/:

Poweroff or reboot

rEFInd reportedly have poweroff and reboot menu entries built in. Since this list of tools is the most extensive of its kind in this wiki, users of UEFI shell, or other UEFI boot managers, such as systemd-boot, might be interested in powerofforreboot.efiAUR.

Tips and tricks

Using drivers in UEFI shell

This article or section is a candidate for moving to Unified Extensible Firmware Interface#UEFI drivers.

Notes: rEFInd's drivers are not the only ones that can be loaded. Move all generic information about UEFI drivers to one article. (Discuss in Talk:REFInd#)

To use rEFInd's drivers in UEFI shell load them using command load and refresh mapped drives with map -r.

Now you can access your file system from UEFI shell.

Manual

Setting efifb resolution

If the resolution in refind.conf is set to an incorrect value, on all systems except Apple Macs rEFInd will display a list of supported resolutions. For Apple Macs it will silently use the default resolution.

To determine framebuffer resolutions supported by efifb, copy /usr/share/gnu-efi/apps/x86_64/modelist.efi from gnu-efi-libs to the root of ESP. Enter the UEFI shell and run modelist.efi.

Set one in refind.conf. Reboot and check if settings has been applied with dmesg | grep efifb.

Troubleshooting

Btrfs subvolume support

Auto detection

To allow kernel auto detection on a Btrfs subvolume uncomment and edit also_scan_dirs in refind.conf.

Next add subvol=subvolume to rootflags in refind_linux.conf and then prepend subvolume to the initrd path.

Manual boot stanza

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):

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

Apple Macs

mactel-bootAUR is an experimental bless utility for Linux. If that does not work, use bless from within OSX to set rEFInd as the default boot entry:

VirtualBox

The Refind Binary File Is Missing Aborting Installation Manual

Currently, VirtualBox will only boot the default esp/EFI/BOOT/bootx64.efi path, so refind-install needs to be used with at least the --usedefault option. See VirtualBox#Installation in EFI mode for more information.

See also

  • The rEFInd Boot Manager by Roderick W. Smith.
  • /usr/share/refind/docs/README.txt
Retrieved from 'https://wiki.archlinux.org/index.php?title=REFInd&oldid=576367'