[HOW TO] OpenCore 0.8.1 > 0.8.2 differences

[miliuco]

The OpenCore team has been working on different parts.

Adaptation to macOS 13 Ventura has been the one that has received the most contributions. Currently it is already possible to install and run Ventura in many hardware configurations. It's advisable tu update all used kexts if you want to try macOS 13 Ventura beta.
In addition, layouts have been added on AppleALC, all kexts have received more or less complete support for macOS 13, WhateverGreen allows you to have macOS 13 on SkyLake spoofing it as Kaby Lake, etc.

OpenCore 0.8.2

Main changes

• Fixed AppleCpuPmCfgLock and DummyPowerManagement on macOS 13
• Added macOS 13 support for AvoidRuntimeDefrag quirk
• Updated builtin firmware versions for SMBIOS
• Updated --restore-nosnoop info to avoid breaking sound in Windows or Linux at boot
• Added injected kext bundle version printing in DEBUG builds
• Added Linux compatibility for CreateVault scripts.

config.plist

 

Nothing to do.

Kexts

• AirportBcrmFixup 2.1.6: macOS 13 support
• AppleALC 1.7.3: layouts added, sleep fixes for certain layouts, macOS 13 support
• BrcmPatchRAM 2.6.3: macOS 13 support, improved macOS 12 support
• CPUFriend 1.2.6: macOS 13 support
• CpuTscSync 1.0.9: macOS 13 support
• DebugEnhancer 1.0.7: macOS 13 support
• FeatureUnlock 1.0.9: macOS 13 support
• HibernationFixup 1.4.6: macOS 13 support
• Lilu 1.6.1: macOS 13 support
• MacHyperVSupport 0.9: macOS 13 support, fixes and improvements
• NVMeFix 1.1.0: macOS 13 support. improved macOS 12 support
• RestrictEvents 1.8.0: macOS 13 support, fixes for real Macs, MacPro7,1 patch for Ventura
• VirtualSMC 1.3.0: macOS 13 support
• VoodooRMI 1.3.5: device updated
• WhateverGreen 1.6.0: macOS 13 support, fixes, Intel FAQ updated, spoof Skylake as Kaby Lake on macOS Ventura (13) and above.

Edited November 7, 2022 by miliuco

[etorix]

Thanks for the heads-up!

With Acidanthera having last published its usual monthly message in February, your monthly "differences" post is an invaluable reference.

 

On 7/5/2022 at 12:43 AM, miliuco said:

config.plist

 

 

Nothing to do.

Wow! That's a first in a long time. (And I certainly do NOT highlight this  to obscure all the work that was put in updating OpenCore and its range of companion kexts.)

Could it be a sign that version 1.0, and possibly some form of API/configuration freeze, is coming?

 

Edited July 6, 2022 by etorix
typo

[rafale77]

1 hour ago, etorix said:

Wow! That's a first in a long time. (And I certainly do NOT highlight this  to obscure all the work that was put in updating OpenCore and its range of comanion kexts.)

Could it be a sign that version 1.0, and possibly some form of API/configuration freeze, is coming?

 

From following the various changes at the commit level, I doubt it. It just so happens to not be needed this time around and it isn't the first time that no config.plist is needed.

We can see that the focus from 0.8.1 to 0.8.2 has been Ventura as opposed to fixing existing issues on prior MacOS versions. There are also a number of code factoring in WIP which have not made it in, in favor of implementing Ventura fixes.

[deeveedee]

I'm going to go out on a limb and predict that version 1.0.0 will be released after 0.9.9.

[miliuco]

@etorix  @rafale77 

 

Who knows? I sign up for the bet of @deeveedee 🙂

 

Let's not forget that, even with no visible changes to config.plist, there is a lot of work in the source code of many files (both OpenCore and some kexts).
It is true that in this version most of the efforts have been to support Ventura. For those who continue with Monterey or older systems there are not so many reasons to update but there are always improvements (updated --restore-nosnoop info, kext bundle version printing in DEBUG builds, Linux compatibility for Vault, new layouts in AppleALC...).