Don't be scared by the length of this page! Only portions of this page apply to any given user, and most people can install rEFInd from an RPM or Debian package in a matter of seconds or by using the install.sh script in minute or two.
+ +Once you've obtained a rEFInd binary file, as described on the preceding page, you must install it to your computer's EFI System Partition (ESP) (or conceivably to some other location). The details of how you do this depend on your OS and your computer (UEFI-based PC vs. Macintosh). The upcoming sections provide details. See the Contents sidebar to the left for links to specific installation procedures. For most Linux users, an RPM or Debian package is the best way to go. If your Linux system doesn't support these formats, though, or if you're running OS X, using the install.sh script can be a good way to go. If you're using Windows, you'll have to install manually.
-Important: A rEFInd zip file, when uncompressed, creates a directory called refind-version, where version is the version number. This directory includes a subdirectory called refind that holds the boot loader, along with another that holds documentation, as well as miscellaneous files in refind-version itself. When I refer to "the refind directory" on this page, I mean the directory with that precise name, not the refind-version directory that is its parent.
+Once you've uncompressed a rEFInd binary zip file, you can copy the entire refind directory into your EFI System Partition's (ESP's) EFI directory on UEFI-based PCs, so that rEFInd resides in EFI/refind. If you've tried rEFInd using a CD-R image file, you can copy the files from the EFI/refind directory on the CD to create an equivalent directory on the ESP. To avoid confusion, though, you should delete the rEFInd binary file for the CPU type your computer does not use. To the best of my knowledge, all UEFI-based PCs use 64-bit CPUs, so you should keep the refind_x64.efi binary and delete the refind_ia32.efi binary. Most Intel-based Macs also have 64-bit EFI implementations, so you should do the same thing; but very early Intel-based Macs have 32-bit EFIs (and sometimes 32-bit CPUs), which require the refind_ia32.efi file. You can determine whether your Mac needs the x86-64 or IA32 build by typing the following command in a Mac Terminal window:
+ + + +Installing rEFInd Using an RPM or Debian Package File
+ + +I provide RPM and Debian package files for rEFInd; and starting with version 0.8.1, I'm maintaining an Ubuntu PPA for rEFInd. If you have a working RPM-based or Debian-based Linux installation that boots in EFI mode, using one of these files is likely to be the easiest way to install rEFInd: You need only download the file and issue an appropriate installation command. In some cases, double-clicking the package in your file manager will install it. If that doesn't work, a command like the following will install the RPM on an RPM-based system:
+ +# rpm -Uvh refind-0.9.2-1.x86_64.rpm+ +
On a Debian-based system, the equivalent command is:
+ +# dpkg -i refind_0.9.2-1_amd64.deb+ +
Either command produces output similar to that described for using the install.sh script, so you can check it for error messages and other signs of trouble. The package file installs rEFInd and registers it with the EFI to be the default boot loader. The script that runs as part of the installation process tries to determine if you're using Secure Boot, and if so it will try to configure rEFInd to launch using shim; however, this won't work correctly on all systems. Ubuntu 12.10 users who are booting with Secure Boot active should be wary, since the resulting installation will probably try to use Ubuntu's version of shim, which won't work correctly with rEFInd. The shim program provided with more recent versions of Ubuntu should work correctly.
+ + +If you're using Ubuntu, you should be able to install the PPA as follows:
+ +$ sudo apt-add-repository ppa:rodsmith/refind +$ sudo apt-get update +$ sudo apt-get install refind+ +
The PPA version will update automatically with your other software, which you might or might not want to have happen. It's also built with GNU-EFI rather than with TianoCore. This last detail should have no practical effects, but it might be important if you've got a buggy EFI or if there's some undiscovered rEFInd bug that interacts with the build environment.
+ +Since version 0.6.3, the installation script makes an attempt to install rEFInd in a bootable way even if you run the script from a BIOS-mode boot, and therefore the RPM and Debian packages do the same. I cannot guarantee that this will work, though, and even if it does, some of the tricks that install.sh uses might not persist for long. You might therefore want to use mvrefind.sh to move your rEFInd installation to another name after you boot Linux for the first time from rEFInd.
+ +Since version 0.6.2-2, my package files have installed the rEFInd binaries to /usr/share/refind-version, the documentation to /usr/share/doc/refind-version, and a few miscellaneous files elsewhere. (The PPA package omits the version number from the file paths.) Upon installation, the package runs the install.sh script to copy the files to the ESP. This enables you to re-install rEFInd after the fact by running install.sh, should some other tool or OS wipe the ESP or should the installation go awry. In such cases you can use install.sh or install manually.
+ + +Installing rEFInd Using install.sh under Linux or Mac OS X
+ + + +If you're using Linux or Mac OS X, the easiest way to install rEFInd is to use the install.sh script. This script automatically copies rEFInd's files to your ESP or other target location and makes changes to your firmware's NVRAM settings so that rEFInd will start the next time you boot. If you've booted to OS X or in non-Secure-Boot EFI mode to Linux on a UEFI-based PC, install.sh will probably do the right thing, so you can get by with the quick instructions. If your setup is unusual, if your computer uses Secure Boot, or if you want to create a USB flash drive with rEFInd on it, you should read the extra instructions for this utility.
+ + +Quick install.sh Instructions
+ + + + +By default, the install.sh script installs rEFInd to your disk's ESP. Under Mac OS X, you can instead install rEFInd to your current OS X boot partition by passing the script the --notesp option, or to a non-boot HFS+ partition by using the --ownhfs devicefile option. Under either OS, you can install to something other than the currently-running OS by using the --root /mountpoint option. (See Table 1 for details.)
+ +Under Linux, install.sh will be most reliable if your ESP is already mounted at /boot or /boot/efi, as described in more detail in the Installing rEFInd Manually Using Linux section. (If you installed Linux in EFI mode, chances are your ESP is properly mounted.) If your ESP is not so mounted, install.sh will attempt to locate and mount an ESP, but this action is not guaranteed to work correctly. If you run install.sh from a BIOS/legacy-mode boot, particularly on a computer that also runs Windows, you should be aware that the tricks the script uses to install itself from BIOS mode are rather delicate. You can convert to a more conventional configuration using the mvrefind.sh script after you've booted in EFI mode.
+ +Prior to version 0.8.4, install.sh installed rEFInd to the OS X root partition by default. I changed this because the default configuration for OS X 10.10 ("Yosemite") makes this placement unusable. Instead, install.sh now installs to the ESP under OS X, just as it does under Linux. If you're upgrading a working install of rEFInd to the OS X root partition, it's best to pass the --notesp option to install.sh. This option is described in more detail shortly.
+ +A sample run under Linux looks something like this:
-$ ioreg -l -p IODeviceTree | grep firmware-abi +# ./install.sh +Installing rEFInd on Linux.... +ESP was found at /boot/efi using vfat +Installing driver for ext4 (ext4_x64.efi) +Copied rEFInd binary files + +Copying sample configuration file as refind.conf; edit this file to configure +rEFInd. + + +Installation has completed successfully.+ +
The output under OS X is a bit different:
+ ++$ ./install.sh +Not running as root; attempting to elevate privileges via sudo.... +Password: +Installing rEFInd on OS X.... +Installing rEFInd to the partition mounted at /Volumes/ESP +Found suspected Linux partition(s); installing ext4fs driver. +Installing driver for ext4 (ext4_ia32.efi) +Copied rEFInd binary files + +Copying sample configuration file as refind.conf; edit this file to configure +rEFInd. + + +WARNING: If you have an Advanced Format disk, *DO NOT* attempt to check the +bless status with 'bless --info', since this is known to cause disk corruption +on some systems!! + + +Installation has completed successfully. + +Unmounting install dir+ +
In either case, the details of the output differ depending on your existing configuration and how you ran the program. Unless you see an obvious warning or error, you shouldn't be concerned about minor deviations from these examples. If you run into such a situation, or if you want to install in an unusual way, read on....
+ +Note that the change to an ESP location for rEFInd with version 0.8.4 means that, if you upgrade rEFInd from an earlier version, you may notice a rEFInd boot option in the rEFInd menu. This option will boot the old version of rEFInd (or the new one, if something went wrong and the old version continues to boot). You can rid yourself of the unwanted boot menu by deleting the old files or by using dont_scan_dirs or dont_scan_files in refind.conf. Before you do this, you should use rEFInd to identify the unwanted files—the filename and volume identifier appear under the icons when you highlight the option. You can then locate and delete them from within OS X. Before you delete the old files, though, you may want to copy over any changes you've made to the rEFInd configuration, icons, and other support files.
+ + +Extra install.sh Instructions
+ + +Some details that can affect how the script runs include the following:
+ +-
+
+
- If you run the script as an ordinary user, it attempts to acquire + root privileges by using the sudo command. This works + on Mac OS X and some Linux installations (such as under Ubuntu or if + you've added yourself to the sudo users list), but on some + Linux installations this will fail. On such systems, you should run + install.sh as root. + +
- Under OS X, you can run the script with a mouse by opening a Terminal + session and then dragging-and-dropping the install.sh file to + the Terminal window. You'll need to press the Return or Enter key to + run the script. + +
- If you're using OS X 10.7's Whole Disk Encryption (WDE) feature, or the + loogical volumes feature in OS X 10.10, you must install rEFInd + to the ESP or to a separate HFS+ partition. The default in rEFInd 0.8.4 + and later is to install to the ESP. If you prefer to use a separate + HFS+ volume, the --ownhfs device-file option to install.sh is + required. + +
- If you're not using WDE or logical volumes, you can install + rEFInd to the OS X root (/) partition by using the + --notesp option to install.sh. Using this option is + recommended when upgrading from a working rEFInd installation in this + location. + +
- If you're replacing rEFIt with rEFInd on a Mac, there's a chance that + install.sh will warn you about the presence of a program + called /Library/StartupItems/rEFItBlesser and ask if you want + to delete it. This program is designed to keep rEFIt set as the boot + manager by automatically re-blessing it if the default boot manager + changes. This is obviously undesirable if you install rEFInd as your + primary boot manager, so it's generally best to remove this program. If + you prefer to keep your options open, you can answer N when install.sh asks if you want to + delete rEFItBlesser, and instead manually copy it elsewhere. If you + subsequently decide to go back to using rEFIt as your primary boot + manager, you can restore rEFItBlesser to its place. + +
- If you're using OS X and an Advanced Format disk, heed the warning that + install.sh displays and do not use bless + --info to check your installation status; this combination has + been reported to cause disk corruption on some Macs! + +
- If you intend to boot BIOS-based OSes on a UEFI-based PC, you + must edit the refind.conf file's scanfor line + to enable the relevant searches. This is not necessary on Macs, + though; because of the popularity of dual boots with Windows on Macs, + the BIOS/legacy scans are enabled by default on Macs. + +
- On Linux, install.sh checks the filesystem type of the + /boot directory and, if a matching filesystem driver is + available, installs it. Note that the "/boot directory" may be + on a separate partition or it may be part of your root (/) + filesystem, in which case the driver for your root filesystem is + installed. This feature is unlikely to work properly from an emergency + system, although it might if you have a separate /boot + partition and if you mount that partition at /boot in your + emergency system, and the ESP at /boot/efi. + +
- On OS X, install.sh checks your partition tables for signs of + a Linux installation. If such a sign is found, the script installs the + EFI filesystem driver for the Linux ext4 filesystem. This will enable + rEFInd to read your Linux kernel if it's on an ext2, ext3, or + ext4 filesystem. Note that some configurations will require a + /boot/refind_linux.conf file, which can be reliably generated + only under Linux. (The mkrlconf.sh script that comes with + rEFInd will do this job once you've booted Linux.) In the meantime, you + can launch GRUB from rEFInd or press F2 or Insert twice after + highlighting the Linux option in rEFInd. This will enable you to enter + a root=/dev/whatever specification, + where /dev/whatever is the device + identifier of your Linux root (/) filesystem. + +
- If you run install.sh on Linux and if + /boot/refind_linux.conf doesn't already exist, + install.sh creates this file and populates it with a few + sample entries. If /boot is on a FAT partition (or HFS+ on a + Mac), or if it's on an ext2fs, ext3fs, ext4fs, ReiserFS, or HFS+ + partition and you install an appropriate driver, the + result is that rEFInd will detect your kernel and will probably boot it + correctly. Some systems will require manual tweaking to + refind_linux.conf, though—for instance, to add + dolvm to the boot options on Gentoo systems that use LVM. + +
- If you pass the --shim option to the script (along with a + filename for a shim binary), the script sets up for a Secure Boot + configuration via shim. By default, this causes the rEFInd binary to be + renamed as grubx64.efi. Recent versions of shim support + passing the name of the follow-on program to shim via a parameter, + though. If you want to use this feature, you can pass the + --keepname option to install.sh. + +
In addition to these quirks, you should be aware of some options that install.sh supports to enable you to customize your installation in various ways. The syntax for install.sh is as follows:
+ ++install.sh [--notesp | --usedefault device-file | --root mount-point | \ + --ownhfs device-file ] [--keepname ] \ + [--nodrivers | --alldrivers] [--shim shim-filename] [--localkeys] [--yes]-
The result should read either EFI32 or EFI64, indicating that you should use the refind_ia32.efi or refind_x64.efi binary, respectively.
+The details of the options are summarized in Table 1. Broadly speaking, they come in four classes: installation location options (--notesp, --usedefault, and --root), driver options (--nodrivers and --alldrivers), Secure Boot options (--shim and --localkeys), and a user input option (--yes). Using some of these options in unusual conditions can generate warnings and prompts to confirm your actions. In particular, using --shim or --localkeys when you're not booted in Secure Boot mode, or failing to use --shim when you are booted in Secure Boot mode, will generate a query and a request to confirm your installation. Consult the Managing Secure Boot page for more on this topic.
+ +| Option | +Explanation | +
|---|---|
| --notesp | +This option, which is valid only under OS X, tells install.sh to install rEFInd to the OS X root partition rather than to the ESP. This behavior was the default in rEFInd 0.8.3 and earlier, so you may want to use it when upgrading installations of that version, unless you used --esp (which is now the default behavior, although the --esp option no longer exists) or --ownhfs. You may also want to use --notesp on new installations if you're sure you're not using whole-disk encryption or logical volumes. | +
| --usedefault device-file | +You can install rEFInd to a disk using the default/fallback filename of EFI/BOOT/bootx64.efi (and EFI/BOOT/bootia32.efi, if the 32-bit build is available) using this option. The device-file should be an unmounted ESP, or at least a FAT partition, as in --usedefault /dev/sdc1. Your computer's NVRAM entries will not be modified when installing in this way. The intent is that you can create a bootable USB flash drive or install rEFInd on a computer that tends to "forget" its NVRAM settings with this option. This option is mutually exclusive with --notesp and --root. | +
| --ownhfs device-file | +This option should be used only under OS X. It's used to install rEFInd to an HFS+ volume other than a standard Mac boot volume. The result should be that rEFInd will show up in the Mac's own boot manager. More importantly, suspend-to-RAM operations may work correctly. Note that this option requires an HFS+ volume that is not currently an OS X boot volume. This can be a data volume or a dedicated rEFInd partition. The ESP might also work, if it's converted to use HFS+. | +
| --root /mount-point | +This option is intended to help install rEFInd from a "live CD" or other emergency system. To use it, you should mount your regular installation at /mount-point, including your /boot directory (if it's separate) at /mount-point/boot and (on Linux) your ESP at that location or at /mount-point/boot/efi. The install.sh script then installs rEFInd to the appropriate location—on Linux, /mount-point/boot/EFI/refind or /mount-point/boot/efi/EFI/refind, depending on where you've mounted your ESP. Under OS X, this option is only useful in conjunction with --notesp, in which case rEFInd will install to /mount-point/EFI/refind. The script also adds an entry to your NVRAM for rEFInd at this location. You cannot use this option with --usedefault. Note that this option is not needed when doing a dual-boot Linux/OS X installation; just install normally in OS X. | +
| --nodrivers | +Ordinarily install.sh attempts to install the driver required to read /boot on Linux. This attempt works only if you're using ext2fs, ext3fs, ext4fs, or ReiserFS on the relevant partition. If you want to forego this driver installation, pass the --nodrivers option. This option is the implicit when you use --usedefault. | +
| --alldrivers | +When you specify this option, install.sh copies all the driver files for your architecture. You may want to remove unused driver files after you use this option, especially if your computer uses Secure Boot. Note that some computers hang or fail to work with any drivers if you use this option, so use it with caution. | +
| --shim shim-filename or --preloader preloader-filename | +If you pass this option to install.sh, the script will copy the specified shim program file to the target directory, copy the MokManager.efi file from the shim program file's directory to the target directory, copy the 64-bit version of rEFInd as grubx64.efi, and register shim with the firmware. (If you also specify --usedefault, the NVRAM registration is skipped. If you also use --keepname, the renaming to grubx64.efi is skipped.) When the target file is identified as PreLoader, much the same thing happens, but install.sh copies HashTool.efi instead of MokManager.efi and copies rEFInd as loader.efi rather than as grubx64.efi. The intent is to simplify rEFInd installation on a computer that uses Secure Boot; when so set up, rEFInd will boot in Secure Boot mode, with one caveat: The first time you boot, MokManager/HashTool will launch, and you must use it to locate and install a public key or register rEFInd as a trusted application. The rEFInd public key file will be located in the rEFInd directory's keys subdirectory under the name refind.cer. Note that I'm not providing a shim binary myself, but you can download one from here. Some distributions also provide their own shim programs, so can point to them—for instance, in /boot/efi/EFI/fedora/shim.efi. | +
| --localkeys | +This option tells install.sh to generate a new Machine Owner Key (MOK), store it in /etc/refind.d/keys as refind_local.*, and re-sign all the 64-bit rEFInd binaries with this key before installing them. This is the preferable way to install rEFInd in Secure Boot mode, since it means your binaries will be signed locally rather than with my own key, which is used to sign many other users' binaries; however, this method requires that both the openssl and sbsign binaries be installed. The former is readily available in most distributions' repositories, but the latter is not, so this option is not the default. | +
| --keepname | +This option is useful only in conjunction with --shim. It tells install.sh to keep rEFInd's regular filename (typically refind_x64.efi) when used with shim, rather than rename the binary to grubx64.efi. This change cuts down on the chance of confusion because of filename issues; however, this feature requires that shim be launched with a command-line parameter that points to the rEFInd binary under its real name. versions of shim prior to 0.7 do not properly support this feature. (Version 0.4 supports it but with a buggy interpretation of the follow-on loader specification.) If your NVRAM variables become corrupted or are forgotten, this feature may make rEFInd harder to launch. This option is incompatible with --usedefault and is unavailable when run under OS X or without the --shim option. If the script discovers an existing rEFInd installation under EFI/BOOT or EFI/Microsoft/Boot and no other rEFInd installation when this option is used, it will abort. | +
| --yes | +This option causes the script to assume a Y input to every yes/no prompt that can be generated under certain conditions, such as if you specify --shim but install.sh detects no evidence of a Secure Boot installation. This option is intended mainly for use by scripts such as those that might be used as part of an installation via an RPM or Debian package. | +
After you run install.sh, you should peruse the script's output to ensure that everything looks OK. install.sh displays error messages when it encounters errors, such as if the ESP is mounted read-only or if you run out of disk space. You may need to correct such problems manually and re-run the script. In some cases you may need to fall back on manual installation, which gives you better control over details such as which partition to use for installation.
-Of course, before you can install the files, you must be able to access the ESP. The details of this task vary from one OS to another. If you have a choice, I recommend using Linux for rEFInd installation on UEFI PCs and OS X on Macs. (On Macs, you can optionally use OS X's main partition rather than the ESP for this purpose.) Windows provides relatively primitive tools for accessing the ESP and manipulating the EFI's boot list. I also describe some options for naming rEFInd that may be useful on some systems. Finally, I describe how to install some extra tools that you may find useful but that are not included with rEFInd.
+ +Installing rEFInd Manually
+ + +Sometimes the install.sh script just won't do the job, or you may need to install using an OS that it doesn't support, such as Windows. In these cases, you'll have to install rEFInd the old-fashioned way, using file-copying commands and utilities to add the program to your EFI's boot loader list. I describe how to do this with Linux, OS X, Windows, and the EFI shell.
-Installing rEFInd Using Linux
+Installing rEFInd Manually Using Linux
-Accessing the ESP is easiest from Linux: The ESP is usually mounted at /boot/efi. You can verify that this is the case by using the df command:
+On a UEFI-based PC, you'll normally install rEFInd to the ESP, which is usually mounted at /boot/efi. You can verify that this is the case by using the df command:
$ df /boot/efi @@ -117,28 +490,28 @@ Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 191284 16604 174681 9% /boot/efi-
This example shows that /dev/sda1 is mounted at /boot/efi, which is a typical configuration. (The ESP can be on another disk or partition, but /dev/sda1 is the most common place for an ESP.) If your output shows /boot or / under the Mounted on column, then your ESP isn't mounted. If you get a df: `/boot/efi': No such file or directory error message, then the /boot/efi directory doesn't even exist. In such cases, you may need to jump through some extra hoops, as described on my EFI Boot Loader Installation page.
+ + +This example shows that /dev/sda1 is mounted at /boot/efi, which is a typical configuration. (The ESP can be on another disk or partition, but /dev/sda1 is the most common place for an ESP.) If your output shows /boot or / under the Mounted on column, then your ESP isn't mounted. (An exception is if you're mounting the ESP at /boot. This is an unusual configuration. If you're using it, you can proceed, making suitable adjustments to subsequent commands.) If you get a df: `/boot/efi': No such file or directory error message, then the /boot/efi directory doesn't even exist. In such cases, you may need to jump through some extra hoops, as described on my EFI Boot Loader Installation page.
Assuming the ESP is mounted at /boot/efi, you can install the rEFInd files as follows (you must be root to issue these commands, or precede each of them with sudo):
-
-
- Type cp -r refind /boot/efi/EFI/ from the refind-version directory in which the refind directory exists. This copies all the files that rEFInd needs to work. +
- Type cp -r refind /boot/efi/EFI/ from the refind-version directory in which the refind directory exists. This copies all the files that rEFInd needs to work. Note that this includes all of rEFInd's drivers. This command also copies the rEFInd binaries as signed by me; if you prefer to re-sign the binaries yourself, you'll have to do so before or during the copy operation, as described on the Managing Secure Boot page.
- Type cd /boot/efi/EFI/refind to change into rEFInd's new directory on the ESP. -
- Type rm refind_ia32.efi to remove the IA32 binary if you're using an x86-64 (64-bit) system; or type rm refind_x64.efi to remove the x86-64 binary if you're using an x86 (32-bit) system. You can optionally rename the binary you keep as refind.efi, but this isn't required. - -
- Rename the configuration file by typing mv refind.conf-sample refind.conf. Consult the Editing the rEFInd Configuration File page for information on how to adjust your options. +
- Type rm refind_ia32.efi to remove the IA32 binary if you're using an x86-64 (64-bit) system; or type rm refind_x64.efi to remove the x86-64 binary if you're using an x86 (32-bit) system. (Note that you must keep the version that's the correct bit width for your EFI; if you've installed a 32-bit Linux on a 64-bit PC with a 64-bit EFI, you'd keep refind_x64.efi. - + -
- On a UEFI-based system, type efibootmgr -c -l \\EFI\\refind\\refind_x64.efi -L rEFInd to add rEFInd to your EFI's list of available boot loaders, which it stores in NVRAM. (Adjust the path to the binary as required if you install somewhere else.) You may need to install this program on some systems; it's a standard part of most distributions' repositories. +
- On a UEFI-based system, type efibootmgr -c -l \\EFI\\refind\\refind_x64.efi -L rEFInd to add rEFInd to your EFI's list of available boot loaders, which it stores in NVRAM. Adjust the path to the binary as required if you install somewhere else. You may also need to include additional options if your ESP isn't on /dev/sda1 or if your configuration is otherwise unusual; consult the efibootmgr man page for details. You may need to install this program on some systems; it's a standard part of most distributions' repositories. Also, if you're installing in Secure Boot mode, you must normally register shim.efi rather than the rEFInd binary, and rename refind_x64.efi to grubx64.efi. Shim 0.7 and later enables you to keep rEFInd's usual name by adding a -u "shim.efi refind_x64.efi" option to your efibootmgr command line, though. Change the filenames to the ones used by your actual Shim and rEFInd binaries, respectively.
- If other boot loaders are already installed, you can use efibootmgr to adjust their boot order. For instance, efibootmgr -o 3,7,2 sets the firmware to try boot loader #3 first, followed by #7, followed by #2. (The program should have displayed a list of boot loaders when you added yours in the preceding step.) Place rEFInd's number first to set it as the default boot program. @@ -150,46 +523,118 @@ Filesystem 1K-blocks Used Available Use% Mounted on
- Open a Terminal window in which you'll type the following commands. +
- If you want to install rEFInd on your ESP, you must first mount it. You can do this by typing mkdir /Volumes/esp followed by sudo mount_msdos /dev/disk0s1 /Volumes/esp. Note that this step is optional. Also, you may need to change /dev/disk0s1 to something else if your ESP is at an unusual location. Use a tool such as my GPT fdisk (gdisk) to examine your partition table to find your ESP if necessary. +
- Type sudo mkdir -p /efi/refind to create a suitable directory for rEFInd. If you want to place rEFInd on your ESP, you should adjust the pathname appropriately, as in /Volumes/esp/efi/refind if you mounted your ESP as described in the previous step. Alternatively, you can use the Finder to create the directory. +
- Copy the files in the refind subdirectory of the rEFInd binary package to the like-named directory you've just created. You can do this in the Finder or by typing sudo cp -r refind/* /efi/refind/ in your Terminal window after changing into the rEFInd package's main directory. + -
- Remove the file for the version of rEFInd you're not using, as in sudo rm /efi/refind/refind_ia32.efi on a Mac with a 64-bit EFI or sudo rm /efi/refind/refind_x64.efi on a Mac with a 32-bit EFI. +
- If this is your first installation, type sudo mv /efi/refind/refind.conf-sample /efi/refind/refind.conf (adjusting the path as necessary) to rename the sample configuration file so that it will serve as a real configuration file. (Again, you can do this with the Finder, if you prefer.) +
- Type sudo bless --setBoot --folder /efi/refind --file /efi/refind/refind_x64.efi to tell the computer to use rEFInd as the primary boot program. (Adjust the path and filename as necessary if you're placing rEFInd somewhere else or using the 32-bit version.) If you're installing rEFInd to an ESP (or to any partition other than the OS X system partition), you may need to add --mount /Volumes/mounpoint to the command, where /Volumes/mounpoint is the location where you've mounted the partition. +
- Open a Terminal window in which you'll type the following + commands. + +
- If you want to install rEFInd on your ESP, you must first mount it. You + can do this by typing mkdir /Volumes/esp followed by + sudo mount -t msdos /dev/disk0s1 /Volumes/esp. Note + that you may need to change /dev/disk0s1 to something else if + your ESP is at an unusual location. Type diskutil + list or use a tool such as my GPT fdisk (gdisk) + to examine your partition table to find your ESP if necessary. + +
- Type sudo mkdir -p /Volumes/esp/efi/refind to create a + suitable directory for rEFInd. If you want to place rEFInd on the OS X + root partition, you should adjust the pathname appropriately, as in + /efi/refind. Alternatively, you can use the Finder to create + the directory. + +
- Copy the files in the refind subdirectory of the rEFInd binary + package to the like-named directory you've just created. You can do + this in the Finder or by typing sudo cp -r refind/* + /Volumes/esp/efi/refind/ in your Terminal window after + changing into the rEFInd package's main directory. + +
- Remove the file for the version of rEFInd you're not using, as in + sudo rm Volumes/esp/efi/refind/refind_ia32.efi on a Mac + with a 64-bit EFI or sudo rm + /Volumes/esp/efi/refind/refind_x64.efi on a Mac with a 32-bit + EFI. + +
- Optionally, remove the drivers directory for the architecture you're + not using—/Volumes/esp/efi/refind/drivers_ia32 or + /Volumes/esp/efi/refind/drivers_x64, as appropriate. You may + also want to remove some or all of the drivers for the architecture you + are using; if you don't need them, they'll slow down the start process. + See the page on drivers for more on this + topic. Note that Apple's firmware includes its own HFS+ driver, so the + HFS+ driver provided with rEFInd is useless on Macs. + +
- If this is your first installation, type sudo mv + /Volumes/esp/efi/refind/refind.conf-sample + /Volumes/esp/efi/refind/refind.conf (adjusting the path as + necessary) to rename the sample configuration file so that it will + serve as a real configuration file. (Again, you can do this with the + Finder, if you prefer.) + +
- "Bless" rEFInd by typing one of the following two commands:
+
-
+
- If you're installing rEFInd on the ESP, type sudo bless --mount /Volumes/esp --setBoot --file + /Volumes/esp/efi/refind/refind_x64.efi --shortform, adjusting + the mount point and exact path to the file as appropriate for your + installation. +
- If you're installing rEFInd to an ordinary HFS+ volume, type sudo bless --setBoot --folder /efi/refind --file + /efi/refind/refind_x64.efi. (Adjust the path and filename as + necessary if you're placing rEFInd somewhere else or using the + 32-bit version.) +
+
+ - If you don't want to reboot immediately after installing rEFInd, you + may optionally unmount the ESP by typing sudo + umount /dev/disk0s1 or sudo umount + /Volumes/esp. This step isn't strictly required, but if you want + to keep the ESP out of your directory tree, it can be useful.
- Type xcopy /E refind S:\EFI\refind\ to copy the refind directory tree to the ESP's EFI directory. If you omit the trailing backslash from this command, xcopy will ask if you want to create the refind directory. Tell it to do so. -
- Type cd S: to change to the ESP. +
- Type S: to change to the ESP.
- Type cd EFI\refind to change into the refind subdirectory -
- Type del refind_ia32.efi to delete the unused 32-bit version of rEFInd. (Windows only supports EFI boots on 64-bit EFI implementations and in 64-bit versions of Windows.) +
- You may want to selectively delete some of the drivers in the drivers_x64 or drivers_ia32 directory, depending on your architecture and needs. Unnecessary drivers will slow the rEFInd start process, and can even cause the drivers you need to not work or cause a system crash. See the page on drivers for more on this topic.
- Type rename refind.conf-sample refind.conf to rename rEFInd's configuration file. + + +
- Type bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi to set rEFInd as the default EFI boot program. Note that {bootmgr} is entered as such; that's not a notation for a variable. Also, change refind_x64.efi to refind_ia32.efi on systems with 32-bit EFIs. Such computers are rare, and most of them are tablets. Check your Windows bit depth to determine which binary you should use. + +
- If you like, type bcdedit /set {bootmgr} description "rEFInd description" to set a description (change rEFInd description as you see fit). +
- You can rename files on the ESP. as described in the next section, Alternative Naming Options. +
- You can rename files on the ESP. as described later, in Alternative Naming Options. -
- You can boot from an optical disc into an emergency OS to do the job. Ubuntu, for instance, provides an EFI-bootable installer with a "try before installation" mode. You'll need to type sudo apt-get install efibootmgr to install efibootmgr, but you can then use that program as described earlier. (If you're using Ubuntu, you'll need to precede the command with sudo. +
- You can boot from an optical disc into an emergency OS to do the job. Ubuntu, for instance, provides an EFI-bootable installer with a "try before installation" mode. You'll need to type sudo apt-get install efibootmgr to install efibootmgr, but you can then use that program as described earlier. (If you're using Ubuntu, you'll need to precede the command with sudo. If you use an Ubuntu image, you can install rEFInd via its PPA, which is an easy way to do the job. (In fact, the rEFInd PPA depends on the efibootmgr package, so you shouldn't need to manually install it.) The PPA approach may even be easier than installing from Windows using its tools, at least if you're familiar with Linux and have an Ubuntu desktop image handy.
- You may be able to use rEFInd's bootable CD image to use rEFInd to boot an OS that's been installed but rendered inoperable because of changes to your boot order. You can then use efibootmgr, bless, or some other tool to restore rEFInd as the default boot loader.
- x86-64 (64-bit) shell 2 + +
- x86 (32-bit) shell 2 + +
- Alternate x86-64 (64-bit) shell 2 for older EFIs + +
- If you haven't installed rEFInd previously, unpack its zip file to a + FAT partition. This can be the ESP itself or another partition, such as + a USB flash drive. If you're simply repairing a lost NVRAM entry, you + needn't move your existing rEFInd files. + +
- Identify your filesystems, which are labelled with the form fsn:, as in fs0: for the first + filesystem, fs1: for the second, and so on. Type the + filesystem number followed by the Enter key to begin using it. You can + then type ls or dir to see the contents of the filesystem. + Chances are your ESP will be fs0:, but it could be something + else. (The following steps assume your ESP is fs0:; you'll + need to adjust them if it's not.) If rEFInd's source files are on + another device, you must identify it, too. + + + +
- If necessary, create a directory for rEFInd by typing mkdir fs0:\EFI\refind. (If the fs0:\EFI + directory doesn't already exist, you must create it first, + though.) + +
- Change to the directory in which rEFInd's files exist. + +
- Type cp refind_x64.efi fs0:\EFI\refind to + copy the rEFInd binary file. (Adjust the name if you're using a 32-bit + computer.) + +
- Type cp refind.conf-sample + fs0:\EFI\refind\refind.conf to copy and rename the sample rEFInd + configuration file. + +
- Type cp -r icons fs0:\EFI\refind\ to copy + rEFInd's icons. + +
- Optionally, type cp -r drivers_x64 + fs0:\EFI\refind\ to copy rEFInd's 64-bit drivers. (You could + instead copy the 32-bit drivers or limit yourself to just the drivers + you need, of course.) + +
- Type fs0:, if necessary, to change to the + ESP. + +
- Type cd \EFI\refind to change to rEFInd's + installation directory. + +
- If you want to edit rEFInd's options, type edit + refind.conf and use the shell's built-in text editor to do so. + Press F2 followed by the Enter key to save your changes and F3 to + exit. + +
- Type bcfg boot dump -b to see a list of + existing NVRAM entries. Pay attention to their numbers (labelled + Option: and Variable:, with the latter number + preceded by the string Boot, as in Boot0007). You'll + want to create a boot entry for rEFInd using a number that's not in + use. + +
- Type bcfg boot add 3 + fs0:\EFI\refind\refind_x64.efi "rEFInd", adjusting the number + (3 in this example), filesystem (fs0:), and filename + (\EFI\refind\refind_x64.efi) as necessary for your system. If + you're used to Linux, be sure to use backslashes (\), not + Linux-style forward slashes (/), as directory separators. Note + that some shells may ignore the number you entered and use another one, + so watch for this possibility. + +
- Type bcfg boot mv 3 0, substituting + the option number for the entry you created for 3. This moves rEFInd to the top of the boot + order. + +
- Type reset to reboot the computer. + +
- EFI/BOOT/bootarch.efi—This name + is the official EFI fallback filename. It's most commonly used on + bootable removable disks, but it can be used on hard disks. It's + typically used only if no NVRAM entry points to a valid boot + loader. + +
- EFI/Microsoft/Boot/bootmgfw.efi—This + filename has no official special standing in the EFI specification, but + as a practical matter, many EFI implementations use it as a fallback + boot loader in addition to or instead of + EFI/BOOT/bootarch.efi. In fact, some give it such a + high precedence that you can't boot anything that's not given this + name! + +
- The script renames rEFInd in a way that's sensitive to its source and + destination directories—for instance, mvrefind.sh knows + that rEFInd (or shim, for Secure Boot installations) must be called + bootx64.efi on a 64-bit installation in + /boot/efi/EFI/BOOT, so it looks for rEFInd under that name + when copying from this directory, or it renames rEFInd to that name + when copying to it. + +
- The script creates a new NVRAM entry for rEFInd when it copies to any + location but EFI/BOOT or EFI/Microsoft/Boot. It + refuses to copy to such locations if it's not run from an EFI-mode + boot. + +
- The script knows enough to back up existing boot loaders stored in + EFI/BOOT or EFI/Microsoft/Boot when copying to these + locations. For the former location, the script backs up + EFI/BOOT as EFI/BOOT-rEFIndBackup; for the latter, it + moves EFI/Microsoft/Boot/bootmgfw.efi to + EFI/Microsoft/bootmgfw.efi. + +
- Access your ESP and install rEFInd to it, as described in earlier sections. +
- Access your ESP, as described in earlier sections. -
- Look for an existing directory called EFI/BOOT or EFI/Microsoft/BOOT. If neither of these directories exist, skip the next step. (Note that FAT is case-insensitive, so the name may vary in case.) +
- Look for an existing directory called EFI/BOOT or EFI/Microsoft/Boot. If neither of these directories exist, skip the next step. (Note that FAT is case-insensitive, so the name may vary in case.) -
- Rename the existing directory to something else. For EFI/BOOT, try renaming it to EFI/Oldboot. For EFI/Microsoft/BOOT, rename the Microsoft directory—say, to MS. Thus, you'll have EFI/MS and its contents, including EFI/MS/BOOT. +
- Rename the existing directory or boot loader file to something else. For EFI/BOOT, try renaming it to EFI/Oldboot. For EFI/Microsoft/Boot, move or rename the bootmgfw.efi file it contains. For instance, you can move it to EFI/Microsoft. This will keep the boot loader accessible to rEFInd's menu, while preventing the firmware from launching it automatically. -
- Rename/move your EFI/refind directory to EFI/BOOT (or EFI/Microsoft/BOOT, if that directory existed and you've renamed it—but you'll first need to create a new EFI/Microsoft directory). +
- Rename/move your EFI/refind directory to EFI/BOOT. If you're working from EFI/Microsoft/Boot, you should move the contents of your rEFInd directory to EFI/Microsoft/Boot. -
- Rename EFI/BOOT/refind_x64.efi to the name of the boot loader it's replacing—it should become EFI/BOOT/bootx64.efi or EFI/Microsoft/BOOT/bootmgfw.efi. +
- Rename EFI/BOOT/refind_x64.efi to the name of the boot loader it's replacing—it should become EFI/BOOT/bootx64.efi or EFI/Microsoft/Boot/bootmgfw.efi.
- On a UEFI-based PC, under any OS, you should be able to replace your + old rEFInd file with the new one. Make sure that the new rEFInd has the + same name as the old one, and that it's for the correct CPU type. Since + UEFI launches boot programs by filename, a simple file replacement will + suffice to launch the new version. If the new version includes new + icons, you may want to copy some or all of them. + +
- On a Mac, you can copy over the old rEFInd binary file from + Linux and it will usually work, provided you copy directly + over the old file (rather than rename or delete the old file and then + copy the new one in its place). The same caveats about icons as apply + to UEFI-based PCs apply in this case. This method requires an extra + step in Mac OS X, though.... + +
- In OS X, if you copy over the original file with the new one, you'll + probably have to re-bless it to make it work. + +
- Under Linux or OS X, you can re-run the install.sh script. In + most cases this works fine, but you'll end up with a duplicate of the + icons directory (icons-backup, which holds the original icons, + whereas icons holds the icons from the new package). Normally + this just wastes some disk space; but if you've customized your icons, + you'll need to copy your altered icons back. Under Linux, versions + 0.6.2 and later of install.sh search for rEFInd in several + locations on the ESP, and will upgrade whatever is found. The same is + true with versions 0.8.5 and later under OS X when installing to the + ESP. If you install to a location other than the ESP under OS X, be + sure to include the same option to install.sh + (--notesp or --ownhfs) to replace the original rather + than create a new installation to the ESP. + +
- Under an RPM- or Debian-based Linux distribution, you can use your + package system to install a newer version of the RPM or Debian package + that I provide. This will upgrade the files in your Linux filesystem + and re-run the install.sh script, so as with the previous + options, you'll waste a little disk space on duplicated icons, but the + process should otherwise work quite well. + +
- If you installed using my Ubuntu PPA or a package provided by an OS + distribution (such as the packages that ship with Arch and ALT Linux), + performing a system update will probably update rEFInd, too. Depending + on how the package was created, though, this update might or might not + install the update to the ESP; you might need to manually re-run the + installation script. Consult your distribution's documentation for + details. My Ubuntu PPA will automatically run install.sh after + the package is installed. + +
- shell.efi—This - file, placed in the ESP's efi/tools directory, adds the +
- shell.efi—This + file, placed in the ESP's EFI/tools directory, adds the ability to launch a text-mode EFI shell from rEFInd. Note that the download link is to a 64-bit binary that must be renamed before rEFInd - will recognize it. - -
- gptsync.efi—This program creates a Arch + Linux wiki, and on other sites; try a Web search if the shell you + find doesn't work to your satisfaction. + +
- Memtest86—This + is a popular tool for performing basic hardware tests, and especially + memory tests. rEFInd recognizes this program when it is stored in the + EFI/tools, EFI/tools/memtest, + EFI/tools/memtest86, EFI/memtest, or + EFI/memtest86 directory, with a program filename of + memtest86.efi, memtest86_x64.efi, + memtest86x64.efi, or bootx64.efi. (Change + x64 to ia32 on IA-32 systems.) Be sure to download + the EFI version of the program. If you get the USB flash drive version, + you should mount the flash drive's ESP (partition 2) and copy the + EFI/BOOT directory to your own ESP's + EFI/tools/memtest or other Memtest86 directory name, as just + specified. rEFInd should then recognize it, provided the + showtools line includes the memtest or + memtest86 token. + +
- gptsync.efi or gptsync_arch.efi—This program creates a hybrid MBR from your regular GPT disk. A hybrid MBR is a dangerous hack that enables Windows and OS X to coexist on a Macintosh disk. If you're using a - UEFI-based PC, a hybrid MBR will be useless at best, so you shouldn't - create one, and it's safest to not install gptsync.efi. If - you're using a hybrid MBR to enable dual-booting Windows and OS X on a - Mac, though, placing this program file in the ESP's or Mac boot - partition's efi/tools directory will enable you to regenerate - your hybrid MBR should some other tool convert the MBR to a standard - protective MBR. You can obtain the file from the original rEFIt package. - -
- diskpart.efi—This is a disk partitioning utility that's - similar to one of the same name in Microsoft Windows. You can obtain it - from Intel's - site as part of a package with a few other tools. Place it in the - efi/tools subdirectory of the ESP and rEFInd will detect it - and give you the option to use it. - -
- Rescue Linux—If the file efi/rescue/elilo.efi - exists, it will be given a special entry in the boot list. The intent - seems to be to launch Linux in a rescue mode, but I've not gotten it to - work. + UEFI-based PC, a hybrid MBR is likely to be useless at best, so you + shouldn't create one, and it's safest to not install + gptsync.efi. If you're using a hybrid MBR to enable + dual-booting Windows and OS X on a Mac, though, placing this program + file in the ESP's or Mac boot partition's EFI/tools directory + will enable you to regenerate your hybrid MBR should some other tool + convert the MBR to a standard protective MBR. You can obtain the file + from the original rEFIt + package, or beginning with rEFInd 0.6.9, an updated version is + included in the rEFInd package. The rEFInd version of gptsync_arch.efi uses a more sophisticated algorithm + for determining what GPT partitions to duplicate in the MBR and it + includes additional safeguards to minimize the risk of damage should + you run the program on a disk that might have been damaged. The + original rEFIt version of the program usually goes by the filename + gptsync.efi, whereas the updated rEFInd version ships with an + architecture code, as in gptsync_x64.efi or + gptsync_ia32.efi. The rEFInd install.sh script + installs gptsync_arch.efi when run + under OS X, but not when run on Linux. In addition to installing the + program, you must edit refind.conf, uncomment the + showtools line, and add gptsync to its list of + options. + +
- Drivers—You can install drivers to extend the capabilities + of the EFI. rEFInd ships with filesystem drivers for ext2fs, ext4fs, and + ReiserFS, which can enable you to boot a Linux kernel with EFI stub + support from an ext2fs, ext3fs, ext4fs, or ReiserFS partition. (rEFInd also + provides ISO-9660 and HFS+ drivers.) You can find additional drivers + from other sources, although they're still on the scarce side. See the + Using EFI Drivers page for more on this + topic. + +
- Secure Boot files—If you're running on a system that + supports Secure Boot, chances are you'll need extra support files, such + as shim.efi and MokManager.efi. I describe these in + detail on the Managing Secure Boot + page. + +
- iPXE—This tool provides the + ability to boot a computer from a network server. Consult the + BUILDING.txt file in the rEFInd source code package for + information on building and installing these tools. You must also + activate rEFInd's support by adding the netboot option to the + scanfor and/or showtools lines in + refind.conf. Network-boot/iPXE support is currently + experimental; I recommend that only developers or those who are + willing to use "bleeding-edge" software try it. Once activated, rEFInd + will present a new menu item for booting from the network server. + rEFInd itself will normally be installed locally. (You can deliver + rEFInd as a network-boot image, but that image will be able to boot + only OSes on the local disk.)
- Boot into Linux. + +
- Type efibootmgr as root to obtain a list of your boot loader entries. Each entry includes a boot number, as in Boot0003 or Boot0027. + +
- Remove all of the boot loader entries except rEFInd's by using efibootmgr's -b bootnum option to specify the boot entry and -B to delete it. For instance, typing efibootmgr -b 0027 -B as root deletes boot entry Boot0027. Issue a separate efibootmgr command for each boot entry. + +
- Re-install rEFInd using the install script. It's unclear from the original post if this meant installing from Linux or from OS X. + +
- Install rEFInd to an HFS+ volume using the --ownhfs option to install.sh. Unfortunately, this solution requires either creating a small HFS+ volume for rEFInd or using an already-existing non-bootable HFS+ volume (if you've got one for data storage, for example). + +
- Type sudo pmset -a autopoweroff 0 in a Terminal window. This solution is likely to work if sleep operations work normally up to a point, but fail after about three hours. + +
- A malfunctioning BIOS/legacy boot—If you installed Linux in BIOS/legacy mode, as most online documentation suggests, it could be that your hybrid MBR is missing or damaged. The usual symptom of this problem is that rEFInd shows a generic Linux penguin icon and that selecting it produces a message to the effect that a bootable OS could not be found. As hybrid MBRs are ugly and dangerous, I recommend avoiding them if possible, so my preferred solution to this problem is to set up EFI filesystem drivers and boot that way; however, fixing the hybrid MBR may be an easier solution. This is especially true if you installed a 32-bit version of Linux on a 64-bit Mac (or a 64-bit version on a rare Mac with a 64-bit CPU but a 32-bit EFI). + +
- EFI filesystem driver problems—Ideally, rEFInd should be able to load and run your Linux kernel directly, but this approach normally requires you to have a working EFI driver for the filesystem that holds your Linux kernel. This won't always be the case; and even if it is installed, there can be interference from other drivers, so you may need to remove the drivers that you don't use. If drivers are the root of your problem, you won't see any Linux options, or you'll see the one penguin icon (as above) with no others that point to your Linux kernel(s). + +
- Boot from an emergency Windows recovery disk. If you don't have one, you can prepare one from a working Windows system as described here. + +
- Type diskpart to enter the Windows disk-partitioning tool. + +
- In diskpart, type sel disk 0 followed by list vol. You should see a set of partitions. This step is intended to help you identify your ESP, which will probably be the only FAT32 partition on the disk. (If you have multiple disks, you may need to try again with sel disk 1 or higher.) Note the volume number of your ESP. + +
- Type sel vol 1, changing 1 to whatever the ESP's volume number is. + +
- Type assign letter=S: to assign the ESP a Windows disk identifier of S:. (You can use another letter if you prefer.) + +
- Type exit to exit from diskutil. + +
- Type cd /d s:\EFI\Microsoft\Boot\ to change into the Windows boot loader directory. (If this directory doesn't exist, you may need to create it first with mkdir. If rEFInd or some other boot loader occupies this directory, back it up first. + +
- Type bootrec /fixboot. + +
- Type bcdboot c:\Windows /s s: /f ALL. Note that this command should set the Windows boot loader as the default. Omit /f ALL if you don't want to adjust the EFI's default boot program. + +
- Reboot and hope it works! If the computer boots straight to Windows and you want to use rEFInd, use bcdedit in Windows, as described in step 9 of the Installing rEFInd Manually Using Windows section of this page. + +
- You must first determine where rEFInd is installed. This can be any of
+ several locations:
+
+
-
+
+
- If you installed rEFInd 0.8.3 or earlier with the default options, + or if you used the --notesp option with rEFInd 0.8.4 or + later, it will be /EFI/refind on your main partition + +
- If you installed rEFInd 0.8.4 or later with the default options, or + if you used the --esp option with rEFInd 0.8.3 or earlier, + it will be in EFI/refind or EFI/BOOT on the + ESP. + +
- If you used the --ownhfs option to install.sh, + rEFInd will be in the System/Library/CoreServices + directory on the volume you specified. + +
- If you installed rEFInd manually, it will be wherever you put + it. + +
- In all cases, there could be duplicate (inactive) rEFInd files in + unexpected places. This is particularly true if you tried + installing rEFInd multiple times, each with different options to + install.sh. Thus, if you delete rEFInd and it still comes + up, you may have deleted the wrong files. (Note that dragging files + to the Trash may have no effect, though—at least, not until + you empty the Trash.) + +
- If necessary, mount the ESP or rEFInd-specific HFS+ volume, as + described in Installing rEFInd Manually Using Mac OS + X. + +
- Verify that rEFInd is installed in the directory noted in step #1. If a + refind.conf file is present, rEFInd is almost certainly + installed in that directory. If not, it's not rEFInd there and you + should not proceed. Be extra cautious about deleting the + System/Library/CoreServices directory, since that's + the default location of the OS X boot loader! Never delete this + directory from your OS X root (/) partition, only from the + partition you specified to install.sh using the + --ownhfs option. + +
- Once you've identified the rEFInd directory, delete it, or at least the + rEFInd boot file. This file may be called refind_x64.efi, + bootx64.efi, boot.efi, or conceivably something else. + You may need to use sudo rm at the command line to accomplish + this task, as in sudo rm -r + /Volumes/esp/EFI/refind. + +
On some systems, efibootmgr won't do what you expect. On such systems, you may have better luck renaming the rEFInd files, as described in the Alternative Naming Options section.
-Installing rEFInd Using Mac OS X
+Installing rEFInd Manually Using Mac OS X
- - -The procedure for installing rEFInd on a Mac is similar to that for installing it under Linux, except that you can install it to the OS X's system directory rather than to the ESP, and you must use the bless utility rather than efibootmgr. To be precise, you should follow these steps:
- --
+
Before installing rEFInd on a Mac, you must determine whether it uses a 32-bit or 64-bit EFI implementation. Most Intel-based Macs have 64-bit EFIs, so you should use the refind_x64.efi file with them; but very early Intel-based Macs have 32-bit EFIs (and sometimes 32-bit CPUs), which require the refind_ia32.efi file. You can determine whether your Mac needs the x86-64 or IA32 build by typing the following command in a Mac Terminal window:
-+$ ioreg -l -p IODeviceTree | grep firmware-abi +-
The result should include either EFI32 or EFI64, indicating that you should use the refind_ia32.efi or refind_x64.efi binary, respectively.
-You should also be aware of your OS X version and installation options. If you used whole-disk encryption (WDE) or a logical volume for installation, you cannot install to the OS X root partition; you must install to the ESP or to a separate HFS+ partition. WDE became an option with OS X 10.7 and logical volumes are the default in OS X 10.10. If in doubt, proceed with an installation to the ESP or to a separate HFS+ partition.
-The procedure for installing rEFInd on a Mac is similar to that for installing it under Linux, except that you must use the bless utility rather than efibootmgr to register the program with the firmware. Also, you'll probably have to mount your ESP manually, since that's not done by default under OS X. To be precise, you should follow these steps:
--
-
When you reboot, your Mac should bring up the rEFInd menu, and should continue to do so thereafter. If you make changes that break this association, you can re-run the bless command (if necessary, restoring the rEFInd files first). This might be necessary after installing system updates from Apple.
+When you reboot, your Mac should bring up the rEFInd menu, and should continue to do so thereafter. If you make changes that break this association, you can re-run the bless command (if necessary, restoring the rEFInd files first). This might be necessary after installing system updates from Apple or if you upgrade rEFInd to a newer version.
-If you're replacing rEFIt, you may discover that rEFInd works on the first boot, but the system reverts back to rEFIt or a direct boot to OS X on the second boot. To fix this problem, you can remove the rEFItBlesser program, which is located at /Library/StartupItems/rEFItBlesser. This program attempts to keep rEFIt set as the default boot loader, but it also has the purpose of protecting the computer from launching the wrong OS after waking from sleep. If you want that protection, my suggestion is to install rEFIt and rEFItBlesser and then replace the refit.efi file with refind_x64.efi or refind_ia32.efi (renaming it to refit.efi. Used in this way, rEFInd will still look for its own configuration file, refind.conf, so you'll need to move it but not rename it. If you don't move the icons from the rEFInd package, your icons will continue to look like rEFIt icons, and you'll be missing the new icons for specific Linux distributions that rEFInd provides.
+If you're replacing rEFIt, you may discover that rEFInd works on the first boot, but the system reverts back to rEFIt or a direct boot to OS X on the second boot. To fix this problem, you can remove the rEFItBlesser program, which is located at /Library/StartupItems/rEFItBlesser. This program attempts to keep rEFIt set as the default boot loader, but it also has the purpose of protecting the computer from launching the wrong OS after waking from sleep. If you want that protection, my suggestion is to install rEFIt and rEFItBlesser and then replace the refit.efi file with refind_x64.efi or refind_ia32.efi (renaming it to refit.efi). Used in this way, rEFInd will still look for its own configuration file, refind.conf, so you'll need to move it but not rename it. If you don't move the icons from the rEFInd package, your icons will continue to look like rEFIt icons, and you'll be missing the new icons for specific Linux distributions that rEFInd provides. One final caveat: It's conceivable that rEFItBlesser is what's causing filesystem corruption for some users, so if you've been having this problem with rEFIt, it might be worth disabling this program and not using it with rEFInd.
If you want to remove rEFInd from your system, you can delete its files. The Mac will revert to booting using whatever standard boot loader it can find. Alternatively, you can use bless to bless another EFI boot loader. The GUI Startup Disk utility in System Preferences provides a simplified interface that enables you to select which OS X installation to boot, but it doesn't look for non-Apple boot loaders, so you can't use it to enable rEFInd.
-Installing rEFInd Using Windows
+Installing rEFInd Manually Using Windows
-To install rEFInd under Windows, you must first find a way to access the ESP, which Windows normally hides from view. One way to accomplish this goal, and to proceed forward once the ESP is accessible, is as follows:
+ + +I know relatively little about Windows EFI management tools; however, I do know that at least two relevant tools exist: the standard bcdedit and the third-party EasyUEFI.
+ +The EasyUEFI tool is a free (as in beer) GUI tool for managing EFI boot programs. I've only tried it once, and it seemed fairly intuitive and easy to use, but I don't have detailed instructions on how to use it. If you want to use EasyUEFI, you'll have to use it in place of bcdedit at the end of the following procedure.
+ + + +Attempt this method of installation only on a UEFI-based PC; this method will not work on Windows that's installed on a Mac in BIOS/CSM/legacy mode. To install rEFInd under Windows, you must first find a way to access the ESP, which Windows normally hides from view. One way to accomplish this goal, and to proceed forward once the ESP is accessible, is as follows:
-
@@ -201,97 +646,627 @@ Filesystem 1K-blocks Used Available Use% Mounted on
Unfortunately, I know of no Windows tool that's equivalent to efibootmgr under Linux or bless under OS X. (Such a tool must exist, but I don't know what it is. If you do, please e-mail me a pointer!) This can make adding rEFInd to your system a bit tricky, particularly if your firmware provides few boot options. In the best of all possible worlds, you'll be able to use your firmware's user interface to add rEFInd to your firmware's own boot manager; however, far too many EFI implementations lack even this modest capability. If you're stuck in this boat, you have several options, such as:
+At this point, when you reboot, rEFInd should appear as your new default boot program. If it doesn't work for you, you have several other options, such as:
-
-
Installing rEFInd Manually Using an EFI Shell
+ + + + +If you can't currently boot any OS (say, because a firmware update has wiped your NVRAM entries), you may find it convenient to install rEFInd using an EFI version 2 shell. Unfortunately, the bcfg command described here is not available in the EFI version 1 shell, and the version 2 shell is unusable on many firmware implementations prior to 2.3.1. Thus, this procedure won't work for all systems.
+ +In addition to emergency situations, using bcfg can be desirable if efibootmgr or other OS-hosted tools don't do the job. This happens under VirtualBox, for instance. An alternative in such cases can be to use alternative names for rEFInd.
+ +To begin, you must have a way to launch your shell. Unfortunately, this can pose a dilemma, since without rEFInd or some other boot manager, many EFI implementations lack the means to launch a shell. Some will do so, though, if the shell is stored as shellx64.efi (for x86-64) or shellia32.efi (for x86) in the root directory of the ESP. Thus, you can try copying your shell file there. You can obtain EFI 2 shells here:
+ +-
+
+
Note that the IA32 shell included in rEFInd's CD-R image version is a version 1 shell, so you can't use it for this purpose. You can, however, copy rEFInd's files from the CD-R. You can even launch the version 1 shell included with rEFInd and then use that to launch a version 2 shell. The x86-64 shell on the CD-R is the alternate shell, which should work on any x86-64 computer. Once you've booted the shell, you can proceed as follows:
+ +-
+
+
With any luck, rEFInd will start up at this point. If not, you can check your settings using a shell or an emergency system for your OS of choice. In an EFI shell, you might type bcfg boot dump -b to view your boot loader entries and verify that rEFInd appears at the top of the list. Be sure to check the pathname for typos. If you continue to have problems, you might look into giving rEFInd a fallback filename that your firmware will recognize.
+Alternative Naming Options
-Some EFI implementations do a poor job of honoring the boot options set via Linux's efibootmgr or other tools. You may also lack access to such utilities, such as if you must install rEFInd in Windows. In such cases, you may need to change the boot loader's name so that the EFI will see it as the default boot loader. rEFInd should then boot when your NVRAM lacks information on specific boot loaders to use. To do this, follow these steps:
+Some EFI implementations do a poor job of honoring the boot options set via Linux's efibootmgr or other tools. You may also lack access to such utilities, such as if you must install rEFInd in Windows. In such cases, you may need to change the boot loader's name so that the EFI will see it as the default boot loader. rEFInd should then boot when your NVRAM lacks information on specific boot loaders to use. Broadly speaking, there are two alternative names that are most useful:
+ +-
+
+
If you need to use one of these names, or something more exotic, you can do so in either of two ways: You can use the mvrefind.sh script to move your installation in one step, or you can move and rename your files manually.
+ + +Using mvrefind.sh
+ + +The easiest way to move a rEFInd installation, at least in Linux, is to use the mvrefind.sh script. If you installed from one of my RPM or Debian packages, this script should be installed in /usr/sbin, so you can use it like a regular Linux command; otherwise you'll need to install it to your path yourself or type its complete path. Either way, it works much like the Linux mv command, but you pass it the directory in which a rEFInd installation appears and a target location:
+ ++# mvrefind.sh /boot/efi/EFI/BOOT /boot/efi/EFI/refind ++ +
This example moves rEFInd from /boot/efi/EFI/BOOT to /boot/efi/EFI/refind. It differs from mv in several ways: + +
-
+
+
The mvrefind.sh script is likely to be useful in resolving boot problems—if your system won't boot, you can try copying the installation to /boot/efi/EFI/BOOT, /boot/efi/EFI/Microsoft/Boot, and /boot/efi/EFI/refind in turn, testing the boot process after each attempt. (These filenames all assume your ESP is mounted at /boot/efi.) You could also copy a BIOS-mode install from /boot/efi/EFI/BOOT or /boot/efi/EFI/Microsoft/Boot to /boot/efi/EFI/refind to make it more robust against Windows repairs (assuming your firmware isn't broken).
+ + +Renaming Files Manually
+ + +You can move and rename rEFInd manually from any OS by following these steps:
-
-
When you reboot, rEFInd should come up. With any luck, it will detect your old boot loader as an option, if one was installed before.
+ +Upgrading rEFInd
+ + +If you've installed an earlier version of rEFInd, you can upgrade a bit more easily than you can install directly:
+ +-
+
+
In all cases, if the new version includes new or altered configuration file options, you may need to manually update your configuration file. Alternatively, if you've used the default configuration file, you can replace your working refind.conf with refind.conf-sample from the rEFInd zip file. (When using install.sh, this file will be copied to rEFInd's installation directory under its original name, so you can rename it within that directory to replace the old file.)
+ +If you're upgrading to rEFInd from rEFIt, you can simply run the install.sh script as described earlier or perform a manual installation. Once installed, rEFInd will take over boot manager duties. You'll still be able to launch rEFIt from rEFInd; a rEFIt icon will appear in rEFInd's menu. You can eliminate this option by removing the rEFIt files, which normally reside in /EFI/refit.
+Installing Additional Components
-rEFInd includes the ability to launch any EFI program; however, rEFInd detects only certain programs. These include boot loaders in traditional locations and a handful of other programs. To launch these other programs, you must download and install them separately from rEFInd:
+rEFInd includes the ability to launch any EFI program; however, rEFInd detects only certain programs. These include boot loaders in traditional locations and a handful of other programs. To launch most of these other programs, you must download and install them separately from rEFInd:
-
-
I've seen links to other versions of these tools from time to time on the Web, so if you try one of these programs and it crashes or behaves strangely, try performing a Web search; you may turn up something that works better for you than the one to which I've linked.
+ +Fixing Macintosh Boot Problems
+ + +I've received a few reports of a sluggish boot process (a delay of about 30 seconds before starting rEFInd) on some Macs after installing rEFInd, as well as some other Mac-specific peculiarities. I've been unable to replicate thess problems myself, and their true causes remains mysterious to me. I have found several possible solutions, though: Using the --shortform option, using the fallback filename, moving rEFInd to an HFS+ volume, clearing NVRAM entries, fixing wake problems, and fixing a failure to find Linux.
+ + +Using the --shortform Option
+ + +Prior to version 0.8.5, these instructions and the install.sh script omitted the --shortform option from the bless command when installing rEFInd to the ESP. An rEFInd user, however, discovered that using the option eliminated the 30-second delay, so it is now the default with 0.8.5's install.sh, and is specified in the instructions. If you installed rEFInd 0.8.4 or earlier, you may want to re-install or re-bless rEFInd using this option.
+ +There is one caveat, though: The man page for bless notes that --shortform notes that its use can come "at the expense of boot time performance." Thus, it's not clear to me that this option might not actually create problems on some computers. (It's eliminated the boot delay on my 2014 MacBook Air and has no detrimental effect on an old 32-bit Mac Mini that's never had a boot delay problem, though.) Thus, if you have problems with rEFInd 0.8.5 or later, you might try running bless, as described in Installing rEFInd Manually Using OS X's step 8, but omit the --shortform option.
+ + +Using the Fallback Filename
+ + +I've received a few reports that installing rEFInd to the ESP using the fallback filename (EFI/BOOT/bootx64.efi on most systems, or EFI/BOOT/bootia32.efi on very old Macs) can work around a sluggish boot problem. In fact, version 0.8.4's install.sh script copied the rEFInd binary to this name when run under OS X. (Version 0.8.5 switches to using --shortform with the more conventional EFI/refind/refind_x64.efi or EFI/refind/refind_ia32.efi name, as just noted.) If you installed to a name other than EFI/BOOT/BOOT{ARCH}, either manually or by using the 0.8.5 or later install.sh, renaming (and re-blessing) the installation is worth trying.
+ + +Moving rEFInd to an HFS+ Volume
+ + +Most of the reports of sluggish Macintosh boots I've seen note that the user installed rEFInd to the ESP rather than to the OS X root partition. Some users have reported that re-installing rEFInd to the OS X root partition clears up the problem. This is obviously a straightforward solution to the problem, if it works. (This location is not an option when using WDE or OS X logical volumes.) Note that rEFInd can launch boot loaders that are stored on any partition that the EFI can read no matter where it's installed; therefore, you'll still be able to launch boot loaders stored on the ESP (or elsewhere) if you install it in this way.
+ +A variant of this solution is to create a small (~100MiB) HFS+ volume to be used exclusively by rEFInd. You can then install rEFInd to that volume with the --ownhfs option to install.sh, as in ./install.sh --ownhfs /dev/disk0s6 if the volume is /dev/disk0s6. This approach has the advantage that it can be managed via OS X's own Startup Disk tool in System Preferences.
+ +The biggest drawback to storing rEFInd on an HFS+ volume is that you won't be able to edit the rEFInd configuration file or move rEFInd-related binaries from an EFI shell if you install it in this way, since Apple's HFS+ driver for EFI is read-only. (The same is true of rEFInd's HFS+ driver, so it won't help you overcome this limitation.) You may also be limited in making changes to your rEFInd configuration from Linux or other OSes, too, since Linux's HFS+ drivers disable write support by default on volumes with an active journal. You can force write access by using the force option to mount; however, this procedure is noted as being risky in the Linux HFS+ documentation, so I don't recommend doing this on a regular basis on the OS X boot volume. This isn't as risky if you use a dedicated HFS+ rEFInd partition, though. You could even mount it as the Linux /boot partition, in which case it would also hold the Linux kernel and related files.
+ +A variant of this solution is suggested in this blog post, which recommends placing rEFInd on an HFS+ volume on the first SATA channel. (In the blogger's case, that channel used to hold an optical drive, but that drive was replaced by a hard disk.)
+ + +Clearing the NVRAM Entries
+ + +Another possible solution is documented in a Web forum post. Be aware, though, that this procedure involves using the efibootmgr utility on Macs, which has been known to damage the firmware on some Macs. Other reports indicate that this problem has been fixed with 3.3.0 and later kernels. Thus, I present this information cautiously and with a strong "use at your own risk" warning. If you care to proceed, I recommend you update your Linux kernel to the latest possible version and then proceed as follows:
+ +-
+
+
Fixing Wake Problems
+ + +Some people have reported that installing rEFInd causes problems with resuming from a suspended OS X session. I know of two workarounds to such problems:
+ +-
+
+
I've recently acquired a 2014 MacBook Air, but I haven't yet had the chance to try to reproduce this problem and find a workaround. It's on my to-do list, though.
+ + +Fixing a Failure to Find Linux
+ + +Some users report that rEFInd doesn't detect Linux, or won't boot it when it is found. Broadly speaking, there are two common causes of this problem:
+ +-
+
+
If you suspect that your hybrid MBR is damaged, you can try re-creating it with my GPT fdisk (gdisk) program. The GPT fdisk hybrid MBR documentation covers this procedure in detail. You can run gdisk from either OS X or Linux, although you may need to install it, particularly in OS X.
+ +If you suspect driver problems, you'll need to mount your ESP (as described in the manual OS X installation instructions), locate the rEFInd drivers_x64 directory, and adjust its contents. Make sure you have a driver for the filesystem that holds your Linux kernel. If you don't know what filesystem this is, it's probably ext4fs. rEFInd ships with several filesystem drivers, including one for ext4fs. You should also remove unnecessary filesystem drivers. I've seen several reports of one driver interfering with others' operation. The biggest culprit seems to be the HFS+ driver when used on Macs.
+ + + + +Fixing Windows Boot Problems
+ + +Most Windows boot problems are best addressed on Windows-specific sites, so I recommend you make the rounds of Windows forums to solve such problems. There is one that deserves mention here, though: If you accidentally erase the Windows boot loader file, EFI/Microsoft/Boot/bootmgfw.efi, you won't be able to boot Windows. The simplest solution is to restore this file from a backup you prepared ahead of time. If you don't have such a backup, though, you can restore it as follows:
+ +-
+
+
For more information, see this SuperUser question and answer.
+ + +Uninstalling rEFInd
+ + +If you decide you don't want to keep rEFInd, you can uninstall it. Doing so is a matter of removing the rEFInd files from your ESP (or from your OS X boot partition, if you installed the program there). The exact details of how to do this vary from one OS to another, though; and in some cases there are alternatives to completely uninstalling rEFInd that are easier to implement.
+ + +Uninstalling rEFInd from Linux
+ + +In Linux, a command like the following, typed as root, should remove rEFInd:
+ ++# rm -r /boot/efi/EFI/refind ++ +
You must type this command as root (or use sudo in some environments, such as under Ubuntu). This example assumes that your ESP is mounted at /boot/efi and that rEFInd is installed in EFI/refind on that partition. If you've mounted your ESP elsewhere, or installed rEFInd elsewhere, you should adjust the command appropriately.
+ +If you installed via an RPM or Debian package in Linux, using your package manager will remove the package files, but not the files that the installer places on your ESP. Thus, you must uninstall those files manually, as just described. To complete the job, you'll also have to remove /boot/refind_linux.conf, and perhaps the /etc/refind.d directory.
+ + +Uninstalling rEFInd from OS X
+ + +The easiest way to restore the standard OS X boot loader on a Mac is not to uninstall rEFInd; it's to bypass it. This can be accomplished with the Startup Disk item in the System Preferences panel:
+ +
+ +
Select your startup disk (Macintosh HD OS X, 10.10.1 in this example) and then click Restart. The computer should reboot into OS X, bypassing rEFInd.
+ +I recommend stopping here, because the procedure for completely removing rEFInd from a Mac depends on your installation method and tends to be challenging for many Mac users, who are unfamiliar with the necessary command-line tools. Basically, you must reverse the steps described earlier, in Installing rEFInd Manually Using Mac OS X:
+ +-
+
+
Uninstalling rEFInd from Windows
+ + +From Windows, you must reverse the directions for installing in Windows—type mountvol S: /S to mount your ESP as S:, then navigate to the S:\EFI directory and delete the refind subdirectory.
+ + +Post-Uninstallation Activity (UEFI-Based PCs)
+ + +On a UEFI-based PC, when the computer boots and cannot find the rEFInd files, it should move on to the next boot loader in its list. In my experience, some EFI firmware implementations remove boot loaders they can't find from their NVRAM lists, so nothing else will be required, provided you have another working boot loader in your firmware's list. If your firmware doesn't automatically clean up its NVRAM entries, rEFInd's entry will do little harm; however, you can delete it with the efibootmgr utility in Linux:
+ ++# efibootmgr --verbose +Timeout: 10 seconds +BootOrder: 0000,0007 +Boot0000* rEFInd HD(2,1b8,64000,f1b7598e-baa8-16ea-4ef6-3ff3b606ac1e)File(\EFI\refind\refind_x64.efi) +Boot0007* CD/DVD Drive BIOS(3,0,00)PATA: HP DVD Writer 1040r . +# efibootmgr --delete-bootnum --bootnum 0000 +Timeout: 10 seconds +BootOrder: 0007 +Boot0007* CD/DVD Drive+ + + +
This example shows use of efibootmgr's --verbose (-v) option to display boot programs so as to identify which one is rEFInd, followed by --delete-bootnum (-B) to delete a boot program and --bootnum (-b) to identify which one to delete. Of course, in this example there's not much else left, so you'd presumably want to install another boot program at this point! If you already have another one installed, you may want to check the BootOrder line to determine which one will take precedence when you reboot. If you don't like what it shows, you can adjust it with the --bootorder (-o) option; consult efibootmgr's man page for details.
+ +If you're not using Linux, you may be able to find a utility that serves +a similar function. Under Windows, the bcdedit command, described +in the section on installing rEFInd under Windows, +may work, although I've not attempted this.
+-
copyright © 2012 by Roderick W. Smith
+copyright © 2012–2015 by Roderick W. Smith
This document is licensed under the terms of the GNU Free Documentation License (FDL), version 1.3.
@@ -299,7 +1274,7 @@ Filesystem 1K-blocks Used Available Use% Mounted on - +Comments on rEFInd and OS X 10.10 (Yosemite)
Return to my main Web page.