Originally written: 3/14/2012; last Web page update:
-7/26/2015, referencing rEFInd 0.9.0
+4/24/2016, referencing rEFInd 0.10.3
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!
As described in reference to version 0.9.2 on the Revisions page, rEFInd includes a
+ delicate and hackish workaround to a problem introduced by Shim
+ 0.8. Developing a better solution to that problem is a high
+ priority.
+
The support for booting legacy (BIOS) OSes on UEFI-based PCs
currently has a number of limitations. Most importantly, it works
off of the list of boot devices stored in the computer's NVRAM. I'd
@@ -173,11 +173,16 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
optical drives and uses generic icons rather than OS-specific
icons.
-
Currently, rEFInd can detect whether it's compiled for x86
- or x86-64 systems and displays this information in its
- "About" screen (AboutrEFInd() in main.c). I'd
- like to add detection for Itanium and ARM systems, but I have no
- way to test such changes.
+
rEFInd's Makefiles and, to a lesser extent, C code,
+ support x86, x86-64, and ARM64 CPUs. EFI is also
+ available for Itanium (IA-64) and ARM32 CPUs, so I'd like to add
+ this support.
+
+
Currently, rEFInd can detect whether it's compiled for x86,
+ x86-64, or ARM64 systems and displays this information in
+ its "About" screen (AboutrEFInd() in main.c). I'd
+ like to add detection for Itanium and 32-bit ARM systems, but I
+ have no way to test such changes.
Further to the preceding, rEFInd's GPT-scanning code (used to
extract partition names) includes assumptions about byte order, and
@@ -233,8 +238,20 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
removing rEFInd's drivers has caused the problem to go into
remission.
Another Mac-specific display problem relates to "retina" displays:
+ Some users report that rEFInd comes up in a lower resolution than
+ the screen supports, and that this setting persists into the running
+ OS X instance, and can't be adjusted using the usual OS X means.
+ Unfortunately, I lack the hardware necessary to experiment and find
+ a solution to this problem within rEFInd. Thus, a fix will have to
+ wait for me to get my hands on such hardware (which is not on my
+ immediate purchase list) or until somebody with such hardware and
+ the necessary skills submits a fix. (Note that a fix could
+ conceivably involve passing options to the OS X boot loader or
+ something else that would require trivial or no changes to
+ rEFInd.)
+
+
Some EFIs have bugs that cause the allegedly case-insensitive
StriCmp() function to perform a case-sensitive comparison.
This causes any number of bugs in file matching. For instance:
Changing the case of icon filename extensions (or various other
@@ -242,14 +259,10 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
"generic" ones; and rEFInd sometimes appears in its own menu (the
firmware sometimes returns an all-caps version of the filename, but
other times returns the filename with the correct case, causing a
- mismatch if the path includes lowercase elements). Some of these
- problems can be overcome by converting both strings to be compared
- to one case before doing the comparison, but others aren't so easy,
- since I think StriCmp() is being called internally to the
- EFI. In any event, it'd be nice to fix some of these problems.
- OTOH, this is a workaround for a bug on just one EFI
- implementation, and a dismal one at that, so I'm inclined to just
- let it go.
+ mismatch if the path includes lowercase elements). This problem is
+ worse when compiling rEFInd with GNU-EFI than with Tianocore.
+ Version 0.9.1 has made improvements on this score, but some issues
+ may continue to lurk.
The Shutdown option works correctly on Macs, but not on many UEFI-based
PCs. On such systems, Shutdown reboots the computer. This should be
@@ -330,6 +343,12 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
+
Currently, debugging rEFInd requires adding Print()
+ statements to the code. Adding a logging facility that supports
+ multiple log levels and writes the output to a file would help with
+ debugging, especially when dealing with problem reports from
+ users.
+
There's currently no way to create a manual boot stanza for a
BIOS-booted OS. This isn't a big priority for me personally, but I
can see how it could be for some people.
@@ -381,6 +400,10 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
GUI toolkit, so that a single code base can be used on any of the
major OSes.
+
The ability to produce audio output (at least a simple "beep") to signal
+ to visually impaired users when rEFInd is ready to accept input would be
+ helpful.
+
Improvements to the EFI drivers:
@@ -408,7 +431,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
-
Improvements to gptsync, install.sh, or other
+
Improvements to gptsync, refind-install, or other
support tools: