X-Git-Url: https://code.delx.au/refind/blobdiff_plain/514e47ab9e1a2ed6c82e8ddbd8f78e04bfc3a057..c9ff72d4b0e75b0683497678aff962911a9364fe:/NEWS.txt diff --git a/NEWS.txt b/NEWS.txt index e0a3e84..36fb2fb 100644 --- a/NEWS.txt +++ b/NEWS.txt @@ -1,6 +1,89 @@ -0.2.5 (?/??/2012): +0.2.8 (?/??/2012): ------------------ +- Fixed (maybe) a bug that caused rEFInd to crash when returning from an + EFI shell or other programs on Macs, particularly when rEFInd used + graphical mode. I'm not 100% sure this bug is squashed because I still + don't understand the cause and I only have one Mac for testing. See + comments in the ReinitRefitLib() function in refit/lib.c for more + details. + +- Added new refind.conf option: scan_all_linux_kernels, which causes Linux + kernels that lack ".efi" extensions to be included in scans for EFI boot + loaders. This may help integration with Linux distributions that don't + give their kernels such names by default. Beware, though: It can detect + unwanted files, such as older non-stub-loader kernels or .icns files used + to give kernels with .efi extensions custom icons. + +- Improved EFI boot loader detection on boards with Gigabyte's Hybrid EFI, + and perhaps other EFIs with a buggy StriCmp() function. Files with both + ".efi" and ".EFI" extensions should now be detected as boot loaders. + +- Fixed a bug that caused rEFInd to fail to scan for drivers if the + filesystem driver didn't set a volume name (that is, if the relevant + field was set to NULL rather than even an empty string). In such + situations, rEFInd now reports the volume name as "Unknown". + +0.2.7 (4/19/2012): +------------------ + +- After much trial and tribulation, I've overcome a GNU-EFI limitation and + enabled rEFInd to load EFI drivers. This feature was present in the + original build of rEFIt but was removed in the versions that could + compile under Linux, but now it's back -- and still being compiled under + Linux! To use it, you should place your drivers in a convenient directory + on the ESP (or whatever partition you use to launch rEFInd) and add a + "scan_driver_dirs" entry to refind.conf to tell rEFInd where to look. (As + always, you should specify the driver directory relative to the root of + the filesystem.) Note that you can't launch drivers from another + filesystem; they must be on the same volume that holds rEFInd. Those who + compile from source code should note that implementing this feature + necessitated using a more recent version of the GNU-EFI library. I'm + currently using version 3.0p, and version 3.0i does NOT work. I don't + know where the change occurred, but you may need to upgrade your GNU-EFI + installation. + +- Fixed bug that caused rEFInd to show up in its own menu sometimes. + +- Added new refind.conf token: also_scan_dirs. When scanning volumes for + EFI boot loaders, rEFInd always scans the root directory and every + subdirectory of the /EFI directory, but it doesn't recurse into these + directories. The also_scan_dirs token adds more directories to the scan + list. It defaults to "elilo,boot", but you can set it to any directory or + directories you like. + +0.2.6 (4/14/2012): +------------------ + +- Added "volume" keyword to configuration file's stanza options. This + option changes the volume from which subsequent files (specified by + "loader" and "icon") are loaded. You pass "volume" the name/label of the + FILESYSTEM you want to use (not the GPT partition name), or a number + followed by a colon (e.g., "1:"). The former should reliably identify a + filesystem, assuming the name is unique. The latter assigns numbers based + on the order in which they're scanned, which may not be as reliable but + should work when a volume is unnamed. + +- Fixed bug in 0.2.5 that caused failure of Linux initial RAM disk + mapping on some (but not all) systems. Affected computers include at + least some Intel motherboards, maybe others. + +0.2.5 (4/9/2012): +----------------- + +- Fixed bug that caused an inability to associate initial RAM disks with + Linux kernels stored in a volume's root directory. + +- Volume badges (that override default badges) are now stored in + .VolumeBadge.icns. Although undocumented, rEFInd formerly loaded custom + volume badges from .VolumeIcon.icns. This carryover from rEFIt was a + confusing name, given the next (new) feature, so I've changed and + documented the name.... + +- Added ability to set a default icon for a loader stored in the root + directory of a volume: The icon is stored in .VolumeIcon.icns. This icon + is also used for Mac OS X volumes booted from the standard location. + - Fixed bug that caused icons to drop back to generic icons when rEFInd was launched in certain ways (such as from an EFI shell in rEFInd's directory) on certain systems.