Jump to content

[HOW TO] OpenCore 1.0.1 >> 1.0.2 differences


miliuco
 Share

1 post in this topic

Recommended Posts

OpenCore 1.0.2 is out. As in the previous version, there are quite a few changes and improvements, although most of them are not noticeable to the end user if version 1.0.1 worked well. You can get it from Acidanthera.

 

Main changes

  • Docs: Update Booter >> Quirks >> FixupAppleEfiImages wording. FixupAppleEfiImages fixes permissions and section errors in macOS boot.efi images (see Note)
  • Fixed error in macrecovery when running headless
  • Added support for AMD_CPU_EXT_FAMILY_1AH
  • Updated builtin firmware versions for SMBIOS and the rest
  • Enabled XcpmExtraMsrs MSR_MISC_PWR_MGMT patch back on macOS 12+
  • Fixed XcpmExtraMsrs MSR_MISC_PWR_MGMT patch on macOS 15
  • Fixed boot device selection with VirtIO disk drives used for macOS installations
  • UEFI >> added Unload (Array) option to unload existing firmware drivers.

Note about FixupAppleEfiImages: Mac OS X boot.efi images contain WˆX permissions errors (in all versions) and in very old versions additionally contain illegal overlapping sections (affects 10.4 and 10.5 32-bit versions only). Modern, strict PE loaders will refuse to load these images unless additional mitigations are applied. Image loaders which enforce these stricter rules include the loader provided with current versions of OpenDuet, the loader in OVMF if compiled from Acidanthera and possibly the image loaders of some very recent 3rd party firmware (e.g. Microsoft).
This quirk detects these issues and pre-processes such images in memory so that a strict loader will accept them. On a system with such a modern, stricter loader this quirk is required to load Mac OS X 10.4 to macOS 10.12, and is required for all newer macOS when SecureBootModel is set to Disabled because pre-processing in memory is incompatible with UEFI Secure Boot, as the image loaded is not the image on disk, so you cannot sign files which are loaded in this way based on their original disk image contents.
This quirk is never applied during Apple Secure Boot for newer macOS. The Apple Secure Boot path in OpenCore includes its own separate mitigations for boot.efi WˆX issues.

 

Config.plist

  • UEFI >> Added Unload option (Array) to be filled with string entries containing the names of firmware drivers to unload before loading the Drivers section. Default: empty Array.

Kexts

  • AirportBrcmFixup 2.1.9
  • AppleALC 1.9.2
  • BrcmPatchRAM 2.6.9
  • CPUFriend 1.2.9
  • CpuTscSync 1.1.1
  • CryptexFixup 1.0.4
  • DebugEnhancer 1.1.0
  • FeatureUnlock 1.1.7
  • HibernationFixup 1.5.2
  • Lilu 1.6.9
  • RestrictEvents 1.1.5
  • VirtualSMC 1.3.4
  • VoodooInput 1.1.6
  • VoodooPS2 2.3.6
  • WhateverGreen 1.6.8.
Edited by miliuco
Fix typo
  • Like 3
  • Thanks 2
Link to comment
Share on other sites

 Share

×
×
  • Create New...