Skip to content

v0.13.2.AA
Compare
Choose a tag to compare
@dakanji dakanji released this 06 Apr 07:07
· 1087 commits to GOPFix since this release
v0.13.2.AA
f08637f
  • Synced with Upstream v0.13.2
    • Minimises Reading of 'HiddenTools' Variable
    • Fixes Menu Keystroke Event
      • Could cause RefindPlus to hang when processing keystrokes in menus
    • Misc Improvements (Skips items already implemented in RefindPlus)
    • Does not adopt upstream changes to non-volatile variable storage
    • Identifies JFS volumes if a third-party JFS driver is installed
    • Improves separation of filesystem name vs. partition name internally
    • Applies extensive memory management improvements
  • Fixes Ignoring the Upstream 'max' Resolution Setting
    • The setting was previously not ignored as was intended
  • Fixes Potential Memory Corruption Issues in the Ext2, Ext4 and HFS Drivers
    • Users should change earlier versions of these drivers for current ones
    • Copies available after building RefindPlus
    • The versions available upstream after the v0.13.1 releases were also improved
    • Additional improvements made to these drivers as well as to the NTFS driver in RefindPlus
  • Fixes a bug that corrupted the ConsoleOut handle on booting EFI Loaders when running GPUs with Mac EFI
    • This bug was introduced in v0.12.0.AN (Commit 8d5e4e3)
  • Fixes a bug that caused the option to return from folded Linux kernel submenus not to appear.
    • This bug was introduced in Upstream v0.9.0
  • Fixes Repeated Icon Scaling on HiDPI Monitors
    • Icons on HiDPI monitors were repeatedly scaled up on each return to the main screen from external screens
    • This bug was introduced in Upstream v0.10.3
  • Fixes Multiple Code Quality Issues
    • Fixes several issues identified by static analysis of the code base
    • Multiple issues of undetermined provenance and age
  • Corrects Default Timeout Setting
    • Was previously set to 20 seconds and not disabled as documented
  • Drops Switch to Graphics Mode on EFI Boot (When not Booting OpenCore)
    • Maintains default mode instead of switching to graphics mode when booting EFI loaders such as OpenCore
  • Improves APFS Remapping
    • Previously failed when using the 'ReScanAll' feature or when not running on Apple Firmware
    • Improves volume filtering
  • Improves Device Handle Connection
    • Now always runs the connection process a minimum of two (2) times
      This is because several links are only revealed after a first pass
    • Trades a typically imperceptible increase in boot time for improved stability and reliability
      NB: The first pass is silent and is not logged
  • Adds 'reload_gop' as Configuration Option
    • This allows switching the 'ReloadGOP from RAM' Feature, introduced in v0.12.0.AM,
      "ON" or "OFF" in the configuration file. Default is "OFF"
  • Now Specfically Logs Booting Clover Instances
    • Now separately identifies Clover instances in the debug log when these are booted
  • Changes Misc Token Names for Internal Consistency or to better reflect function
    • 'disable_mac_compat_check' to 'disable_compat_check'
    • 'set_mac_boot_args' to 'set_boot_args'
    • 'protect_mac_nvram' to 'protect_nvram'
    • 'reinforce_apfs' to 'sync_apfs'
  • Implements Upstream 'firmware_bootnum' manual stanzas (Skipped in v0.13.1.AA)
    • Misc fixes appear to have resolved previously experienced issues
  • Adds "active_csr" config token to allow implementing a CSR policy
    • Allows ensuring a particular CSR policy is always actively implemented
    • Previously passively left whatever was previously set unchanged.
  • Always Activates Certificate Write Prevention on Windows
    • Now always activated on Windows boot regardless of whether Legacy or UEFI Windows is detected
  • Adds OpenCore and Clover to "use_graphics_for"
    • The default screen mode on booting these boot loaders can now be set to graphics mode.
  • Incoporates a Variant of the Upstream Logging
    • Combines an equivalent of the upstream logging feature with the existing logging.
    • The previously disabled "log_level" configuration token can now take a numeric log level
      (0 to 4), with levels 1 to 4 giving increasing levels of detail.
    • Different to the upstream implementation, this feature is only available on DEBUG builds and as such,
      Level 0 does not disable the feature but activates the original logging form (logs some unique items).
Assets 3
Loading