[HOW TO] OpenCore 0.7.1 > 0.7.2 differences

[miliuco]

As always, I recommend to read the message from vit9696 with the summary of the work done during the month of July.

0.7.2 version brings OpenCore with fewer changes than we have seen in previous versions. Still, there have been more than 20 builds with some major modifications, especially in regards to bugs and security:

• Keyboard not responding in Windows BitLocker
• Handling libraries and tracking errors when compiling
• Removing unwanted spaces in CPU information strings
• SMBIOS data update
• Security improvements (changes in Apple Secure Boot model and APFS driver).

config.plist

• Misc > Security > SecureBootModel (String): new value added (x86legacy), this is the recommended value for Monterey on Macs and Hacks without a T2 chip for better security and compatibility. Previously, the recommended value was Default, equivalent to j137 (iMacPro1,1, December 2017, minimum macOS 10.3.2), this value must be used in macOS 10.15 and earlier. j137 does not work with Monterey.
• UEFI > AppleInput > GraphicsInputMirroring (boolean): This is to prevent keyboard input from not working in graphics-based applications such as Windows BitLocker that use non-Apple key input methods even when an AppleEvent key handler (e.g. CrScreenshotDxe.efi) is active. The recommended setting on all hardware is true.
  An interesting discussion about this is available on OpenCore bug tracker: OpenCore: Can't use usb keyboard on Windows BitLocker recovery menu.
• UEFI > APFS: Increased default APFS MinDate and MinVersion to macOS Big Sur for better security. These keys are the minimal allowed APFS driver date and version to be loaded. Examples:
  - MinDate and MinVersion 0 is default (currently Big Sur), leave this value if you are using Big Sur or Monterey
  - MinDate=20200306 and MinVersion=1412101001000000 is for Catalina 10.15.4 (19E287)
  - MinDate=20190820 and MinVersion=945275007000000 is for Mojave 10.14.6 (18G103)
  - MinDate and MinVersion -1 is disabled (not recommended).
  It's required to change MinDate and MinVersion in the APFS section for macOS versions older than Big Sur.
  Note: ocvalidate doesn’t check if MinDate and MinVersion values are valid for the installed version of macOS, you must check it by yourself.

Kexts

Some kexts have been modified, it is recommended to use the most recent versions. They all have internal improvements, here only significant changes are commented:

• AppleALC (Lilu boot args support)
• CpuTscSync (Monterey support)
• FeatureUnlock (Monterey support)
• Lilu (improved 32-bit performance)
• MacHyperVSupport (Monterey support)
• RestrictEvents (improved CPU detection, MacPro7,1 UI in About his Mac, better compatibility with macOS 10.15 and older)
• UEFIGraphicsFB (first version, basic display output without hardware acceleration on generic hardware)
• VirtualSMC (Monterey support)
• WhateverGreen (improved iGPU detection, updated documentation, better device-id spoofing support for AMD cards letting newer RX 6900 GPUs run without problems).

Many thanks to the OpenCore team.

 

[Ben42]

• UEFI > APFS: Increased default APFS MinDate and MinVersion to macOS Big Sur for better security. These keys are the minimal allowed APFS driver date and version to be loaded. Examples:
  - MinDate and MinVersion 0 is default (currently Big Sur), leave this value if you are using Big Sur or Monterey
  - MinDate=20210508 and MinVersion=1677120009000000 is for Big Sur 11.4 (20F71)
  - MinDate=20200306 and MinVersion=1412101001000000 is for Catalina 10.15.4 (19E287)
  - MinDate=20190820 and MinVersion=945275007000000 is for Mojave 10.14.6 (18G103)
  - MinDate and MinVersion -1 is disabled (not recommended).
  It's required to change MinDate and MinVersion in the APFS section for macOS versions older than Big Sur.

I'm a bit confused by this part....I dual boot Catalina and Big Sur so if I set the key value for Catalina will I be able to boot Big Sur or vice versa?

 

[wern]

@miliuco You might also mention that ocvalidate doesn't care about the APFS MinDate MinVersion entry. Not al users use BigSur, if you trust the ocvalidate utility (like me), you loose the ability to boot Mojave or Catalina. If that's the only macOS you're using, you won't be able to boot anymore.

 

[miliuco]

I'm a bit confused by this part....I dual boot Catalina and Big Sur so if I set the key value for Catalina will I be able to boot Big Sur or vice versa?

You'll be able to boot Big Sur writing the values for Catalina (I have tried), Big Sur loads its own version of the driver.
Booting Catalina with Big Sur values (0) doesn’t work.

 

[miliuco]

@miliuco You might also mention that ocvalidate doesn't care about the APFS MinDate MinVersion entry. Not al users use BigSur, if you trust the ocvalidate utility (like me), you loose the ability to boot Mojave or Catalina. If that's the only macOS you're using, you won't be able to boot anymore.

Do you mean that ocvalidate does not check if the values are correctly written? I have not noticed it. I'll check it out and add a comment to post 1. Thank you.

 

[wern]

Do you mean that ocvalidate does not check if the values are correctly written? I have not noticed it. I'll check it out and add a comment to post 1. Thank you.

With MinDate 0, MinVersion 0, ocvalidate outputs "No issues found" and you're not able to boot Mojave. Probably also Catalina, not yet tested.

 

[miliuco]

With MinDate 0, MinVersion 0, ocvalidate outputs "No issues found" and you're not able to boot Mojave. Probably also Catalina, not yet tested.

You're right, ocvalidate doesn't check if the numbers are valid for the installed macOS, only if both keys exist and their type is number.

 

[jaymonkey]

@miliuco,

VirtualSMC version 1.2.6 was also released yesterday but is missing from your OC 0.7.2 updated kexts list.

PS: Have also pinned your OC 0.7.1 -> 0.7.2 post so its at the top of the list.

Cheers
Jay

 

[miliuco]

@jaymonkey
VirtualSMC added. Thanks!

 

[miliuco]

@wern
Added note about ocvalidate. Thanks!