This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!
0.8.7 (3/1/2015)—This release provides bug fixes and refinements to existing features. Several changes should reduce the odds of rEFInd crashing because of assorted problems. Other changes improve Secure Boot handling, including improved Secure Boot detection in install.sh, recognition of KeyTool.efi and KeyTool-signed.efi as MOK manager utilities, and reporting of Secure Boot status for x86 (IA-32) systems in the rEFInd information screen. Filesystem detection is improved (again), and XFS has been added as a known filesystem. Detection of FreeBSD's BIOS-mode boot loader is improved, which should give more Mac users the right OS icon when booting FreeBSD in BIOS mode. Finally, I'm deprecating the use of fsx: notation for referring to filesystems. The numbering of filesystems is simply unreliable, and better alternatives (the use of partition GUIDs, partition names, and filesystem names) have been added in previous releases. The fsx: code remains in rEFInd, and if it's working for you, you can continue to use it; but sooner or later I'll remove that code, so you're advised to change your manual boot stanzas and other options that use it before that happens.
+
0.10.3 (4/24/2016)—This version features mostly modest changes and additions:
+
+
+
+
A new Linux script, refind-mkdefault, simplifies the task of resetting rEFInd as the default boot program. It's documented here. I've also written a new documentation page on the problem generally, which covers how to handle the problem in multiple OSes.
+
+
I've modified the SIP/CSR rotation code so that the SIP/CSR rotation tool will appear more reliably on Apple computers.
+
+
The NTFS driver has been improved to reduce the chances of it hanging randomly.
+
+
The code that excludes shell binaries from appearing in the main boot list has been altered to reduce the odds of an incorrect exclusion from occurring.
+
+
rEFInd now recognizes the fwupx64.efi program as a special case: If detected, this program is presented as a second-row option rather than as a regular boot loader. (This tool is used to update firmware on some computers.)
+
+
BIOS/CSM/legacy-mode OSes all now include the string Legacy in their descriptions on Macs.
+
+
+
+
+
+
0.10.2 (1/26/2016)—Changes to this version are relatively modest and focus on bug fixes:
+
+
+
+
A bug in refind-install under OS X could cause the mountesp script to be installed as a file called /usr/local/bin if that directory was absent. This bug has been fixed.
+
+
Another OS X refind-install bug caused the --usedefault option to not work properly. This has been fixed.
+
+
A Linux refind-install bug caused Secure Boot detection to fail in some cases. This has also been fixed.
+
+
The mvrefind script could fail to move the Windows boot loader file (bootmgfw.efi) under some circumstances. Another bug in the same script caused mvrefind to register rEFInd using its default filename (rEFInd Boot Manager) rather than the name Windows Boot Manager when moving rEFInd to the Windows boot manager's location. Both of these bugs have been squashed.
+
+
A long-standing but obscure bug/quirk affects some EFIs, such as that in the HP ProBook 6470b: These EFIs connect useless drivers to partitions with no known filesystems, before rEFInd can load filesystem drivers. The result is that drivers loaded by rEFInd could not read the partitions in question. This version of rEFInd works around this problem.
+
+
A bug introduced in rEFInd 0.10.1 caused custom volume badge icons (read from an icon directory specified by icons_dir in refind.conf) to be ignored. I've fixed this bug.
+
+
Finally, a small non-bug improvement: I've added centos.crt and centos.cer public-key files for CentOS to the keys directory.
+
+
+
+
+
+
0.10.1 (12/12/2015)—This version of the program features one big change that will affect very few people, another big behind-the-scenes change, and a number of small changes that will affect more people:
+
+
+
+
rEFInd now compiles and runs on ARM64 (aka AARCH64 or AA64) systems. To date, I've tested it only using QEMU, so this support is very preliminary, almost to the point of being theoretical.
+
+
I've made significant changes to the Makefiles used to compile rEFInd. This should have no effect on the way rEFInd functions, or even in how most programming tasks are done; but the changes should help simplify some future changes.
+
+
I've made font changes: I've removed Luxi Sans Mono and changed the default font from Nimbus Mono to Liberation Mono.
+
+
A bug that causes rEFInd to fail to detect boot loaders on removable media when rEFInd itself was launched from the fallback filename is now history.
+
+
Fedora, Red Hat, and CentOS use a special recovery kernel with a name beginning vmlinuz-0-rescue. This kernel could be newer than others, which would make it the default on in a "folded" set of kernels—a highly undesirable situation. I've therefore modified rEFInd's loader-sorting algorithm to move this rescue kernel to the end of the list, no matter what its time stamp reads.
+
+
I've added a workaround to gptsync to fix problems that caused it to skip through its menus using the defaults without taking user input on some Macs. I've also added 53746F72-6167-11AA-AA11-00306543ECAC (Apple Core Storage, gdisk type AF05) to the list of partition types that gptsync recognizes.
+
+
The refind-install script can now be run as a symbolic link in Linux, which means it can be run as a normal command.
+
+
I've fixed bugs in refind-install and in mkrlconf that could cause them to misidentify kernel options. See NEWS.txt for details.
+
+
I've moved the detailed description of refind-install from Installing rEFInd to a man page, and I've created HTML versions of the three man pages that the project now includes.
+
+
I've added kernel* as a pattern for matching Linux kernels, since Gentoo Linux names its kernels by this pattern.
+
+
I've updated LodePNG, which is the PNG graphics library that rEFInd uses, to version 20151024.
+
+
The rEFInd PPA now asks for confirmation before installing to the ESP when the package is first installed. Updates follow the instructions given on first installation. You can modify this setting by typing dpkg-reconfigure refind.
+
+
+
+
+
+
0.10.0 (11/8/2015)—I've given this version an extra-large version number bump because of some highly user-visible changes, especially for Mac users. Changes include:
+
+
+
+
I've swapped out the old icons for new ones. I've replaced the old
+ icons because the OS icons were becoming a hopeless mish-mash of
+ styles and because I wanted to consolidate the icon collection to use
+ a more limited set of original sources for record-keeping purposes.
+ If you prefer the old icons, you can continue to use them. After
+ upgrading, rename icons-backup to something else (say,
+ icons-classic) and add a line to refind.conf to
+ reference the new directory, as in icons_dir
+ icons-classic.
+
+
A new feature, spoof_osx_version, causes rEFInd to tell a
+ Mac that it's about to launch OS X. This alters how some Macs
+ initialize hardware, which can make secondary video chipsets work on
+ some Macs. See the comments in refind.conf-sample or on the
+ Using rEFInd page for details. This feature
+ has no effect on UEFI-based PCs.
+
+
Another new feature enables you to adjust a Mac's System Integrity
+ Protection (SIP) settings from within rEFInd. To use this feature,
+ you must adjust two lines in refind.conf: The new
+ csr_values line sets hexadecimal values through which you
+ can rotate using a new second-row tag that's activated by the new
+ scanfor line option of csr_rotate. Thus, you must
+ add or change both the scanfor and csr_values
+ lines. See the new rEFInd and System Integrity
+ Protection page for information on how to use this new feature.
+ Although this feature can work on UEFI-based PCs if they contain the
+ necessary NVRAM variable, such systems are unlikely to have this
+ variable, and it's unlikely to be useful even if it's present.
+
+
If the SIP NVRAM variable is set, rEFInd now displays its current
+ value in the About screen.
+
+
I've renamed several support scripts: install.sh to
+ refind-install, mvrefind.sh to mvrefind,
+ and mkrlconf.sh to mkrlconf. I've also added man
+ pages for mvrefind and mkrlconf.
+
+
Under OS X, refind-install now checks the machine's SIP
+ status and warns the user if it's active. To help with such
+ installations, the script can also now be run from a boot of the
+ Recovery HD.
+
+
Under Linux, refind-install and mkrlconf now use
+ /proc/cmdline as a source for the default boot options for
+ Linux kernels, rather than trying to extract them from GRUB
+ configuration files—except when the --root
+ option is used, in which case the script continues to use the GRUB
+ configuration files as a source of boot options. This change should
+ help rEFInd pick up exotic boot options that GRUB computes at boot
+ time, such as Btrfs subvolume options.
+
+
I've added a new script, called mountesp, which mounts the
+ ESP on Macs, using the same algorithm used by
+ refind-install. This should help Mac users who want to edit
+ their rEFInd configurations.
+
+
I've changed the default also_scan_dirs setting from
+ boot to boot,@/boot. This change helps rEFInd pick
+ up kernels from Btrfs volumes.
+
+
I've changed from .zip to a tarball (.tar.gz) as
+ the file format for the source code package. This change simply
+ reflects the fact that Linux is the only supported build environment
+ for rEFInd, and tarballs are more in line with that platform than are
+ .zip files. The primary binary file format remains a
+ .zip file, with Debian packages and RPMs also
+ available.
+
+
My 32-bit Mac Mini suffered from a bug that caused rEFInd's
+ icon-resizing code to hang in a conversion from floating-point to
+ integer values. I've therefore adjusted the icon-resizing code to
+ avoid doing floating-point computations. This change has a drawback,
+ though: It causes some images to acquire artifacts when resized,
+ particularly on 32-bit systems. If you run into such a problem, you
+ should scale your icon(s) or banner/background image so that it does
+ not need to be resized. Sorry, but between a system crash and minor
+ graphics artifacts, the graphics artifacts are the lesser of two
+ evils.
+
+
+
+
0.9.2 (9/19/2015)—Soon after releasing 0.9.1, I started receiving bug reports about problems with it and Shim 0.8. (See this thread for one such report.) It turns out that the problem was not a new bug in rEFInd, but rather a change from Shim 0.7 to Shim 0.8 that made it next to useless with rEFInd. Specifically, Shim 0.8 now de-registers itself from the EFI after a follow-on program launches another one. This is done to avoid problems in a boot path in which Shim launches fallback.efi, which in turn launches another Shim. This creates a new problem, though: rEFInd can validate just one binary before it's "cut off" from Shim. Since rEFInd's drivers are binaries, if you use a single driver, that means that you won't be able to launch anything that requires validation via Shim. I quickly discovered a workaround, which I've implemented in this release. I consider this a "band-aid" patch, though, because it relies on a quirk of Shim's logic to bypass its de-registration. As such, the workaround in this release may break with a future Shim. A true fix will take longer to develop. I want to release this workaround version to head off further problems in the near term, though. This version also introduces a new feature, which is also Shim-related: Since version 0.7, Shim has supported launching binaries other than grubx64.efi by passing them on the command line. (Actually, Shim 0.4 supported this, but it required a broken path specification.) I've added support for this feature to install.sh: Adding the --keepname option to install.sh causes the script to preserve rEFInd's regular filename and to register the approprirate follow-on parameters to have Shim launch rEFInd by that name. This works, but is likely to be more delicate than using the default Shim follow-on name of grubx64.efi. The advantage, of course, is that rEFInd needn't "lie" about its name, which makes for less confusion in filenames. For the moment, the RPM and Debian packages I build do not use this new naming feature, since I can't be sure what version of Shim might be picked up. These changes do not affect users who do not use Secure Boot.
+
+
0.9.1 (9/13/2015)—This version has improved the Discoverable Partitions Specification (DPS) support in a number of ways that should make it more reliable when /etc/fstab omits references to the root (/) partition or when the GPT read-only or do-not-automount options are used to control these features. A stray DPS-related debugging print command has also been removed. I've improved rEFInd's ability to guess the Linux distribution by having it examine /etc/lsb-release as well as /etc/os_release, and I've added an icon for Elementary OS. Finally, I've made improvements to rEFInd's handling of case-insensitive string comparisons, which were buggy on some EFIs, particularly when rEFInd was compiled with GNU-EFI. rEFInd is still at the mercy of the EFI and support libraries, but many problem cases should now be resolved.
+
+
0.9.0 (7/26/2015—This version gets a bump up to 0.9.0 mainly because of a highly user-visible new feature: kernel folding. With kernel folding active, multiple Linux kernels in a single directory appear as just one main-menu entry, which launches the most recent kernel (by file timestamp) by default. Older kernels appear on the first one's submenu (accessed by hitting F2 or Insert). You can disable this new feature by setting fold_linux_kernels false in refind.conf. Another new feature is support for the Discoverable Partitions Spec, which enables rEFInd to locate the Linux root (/) partition without a refind_linux.conf or /etc/fstab entry. I know of no distribution that automatically sets up its partitions in this way, but if and when this starts to happen, rEFInd will be ready. Other changes are relatively minor: The Debian postinst script now calls install.sh with --localkeys if sbsign and openssl are available, which helps if using the Ubuntu PPA on a system with custom Secure Boot keys; I've fixed a packaging bug that prevented IA32 versions of filesystem drivers and gptsync to not be built in the PPA; mkrlconf.sh now refuses to run under OS X; rEFInd now skips checking for BIOS-mode boot code on UEFI-based PCs, which should speed it up a little; I've fixed a bug that caused rEFInd to crash if it found an existing but empty refind_linux.conf file; I've made minor code changes to enable rEFInd to build under GCC 5.1; and I've added a new icon for Kali Linux (provided by Francesco D'Eugenio).
+
+
0.8.7 (3/1/2015)—This release provides bug fixes and refinements to existing features. Several changes should reduce the odds of rEFInd crashing because of assorted problems. Other changes improve Secure Boot handling, including improved Secure Boot detection in install.sh, recognition of KeyTool.efi and KeyTool-signed.efi as MOK manager utilities, and reporting of Secure Boot status for x86 (IA-32) systems in the rEFInd information screen. Filesystem detection is improved (again), and XFS has been added as a known filesystem. Detection of FreeBSD's BIOS-mode boot loader is improved, which should give more Mac users the right OS icon when booting FreeBSD in BIOS mode. A bug in install.sh that caused inappropriate installation to the filename bootx64.efi or bootia32.efi, and failure to update the computer's boot list, has been squashed. Finally, I'm deprecating the use of fsx: notation for referring to filesystems. The numbering of filesystems is simply unreliable, and better alternatives (the use of partition GUIDs, partition names, and filesystem names) have been added in previous releases. The fsx: code remains in rEFInd, and if it's working for you, you can continue to use it; but sooner or later I'll remove that code, so you're advised to change your manual boot stanzas and other options that use it before that happens.
0.8.6 (2/8/2015)—Most (but not all) of this release's changes focus on Windows dual-booting and Mac-specific issues. There's a new Windows 8 icon, which is now used by default as the Windows icon, although the old icon remains available and is used for Windows XP and earlier boots on Macs. If the NTFS driver is loaded, rEFInd will now exclude non-bootable NTFS volumes from the Mac boot list (this change does not affect UEFI-based PCs). A bug that caused misidentification of whole disks and NTFS volumes as being FAT has been fixed (again, this problem affected Macs, not PCs). A couple of Mac-specific install.sh bugs have been fixed, resulting in more reliable identification of the ESP and of the installation directory. Previous versions ignored a volume name of "HFS+ volume" because that name was produced by earlier versions of the rEFInd HFS+ driver for all HFS+ volumes; but the current HFS+ driver produces a real volume name, so I've removed that special case from the code. I've removed the r472 rEFIt commit, introduced in 0.8.5, because it was causing some BMP files to fail to load. Finally, the hideui token in refind.conf now accepts a value of badges, which has the effect of hiding the disk-type badges associated with OS launch icons.
+
@@ -54,8 +55,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
-
-