Jump to content

[HOW TO] OpenCore 0.7.3 > 0.7.4 differences


miliuco
 Share

10 posts in this topic

Recommended Posts

OpenCore 0.7.4 is available. Yo can get it here: https://github.com/acidanthera/OpenCorePkg/releases

 

@vit9696's usual Dortania message has not been published but official OpenCore version 0.7.4 has been released.

Note: This time the (shorter) message is here:

https://github.com/acidanthera/bugtracker/issues/1779#issuecomment-932981707

 

Main changes are in the changelog.


Changelog

  • Fixed Linux kernel sort order
  • Added Linux detection optional log detail
  • Fixed CPU core count detection for more legacy CPUs
  • Added ability to fully override autodetect Linux boot options
  • Added large BaseSystem support in AdviseFeatures
  • Updated builtin firmware versions for SMBIOS
  • Added tool to extract vendor secure boot certificate from GRUB shim file
  • Added BridgeOSHardwareModel NVRAM variable to fix T2 SecureBootModel on macOS 12
  • Changed Default Apple Secure Boot model to match SMBIOS for macOS 12
  • Fixed opencore-version not being added to NVRAM variables.

Secure boot and updates in Monterey
 

Until now we could have Apple Secure Boot full security in Big Sur but not in Monterey. You can read about Apple Secure Boot here.

Now we can also have full security in Monterey. To have full security it is necessary a SMBIOS model with Apple T2 security chip. If the SMBIOS model does not have T2, we can only have medium security. This is true on real Macs as well.
Note: installing RestrictEvents will not do anything to fix Secure Boot (all the changes in RestrictEvents are guarded by a special boot arg), it does nothing by default and only forces medium security with x86legacy model on any Mac model when enabled.

On the other hand, the need to change the SecureBootModel or SMBIOS model to update Monterey via OTA seems to have disappeared and it is not necessary to have RestrictEvents.kext for this task because the fix is included in OpenCore.


config.plist

  • UEFI >> Drivers >> added Comment (string) property (Arguments, Comment, Enabled and Path).
  • Booter >> Quirks >> SyncRuntimePermissions (boolean): usually is False but it can be useful to be True if there are early boot failures (e.g. halt black screen) when booting Linux kernels.
  • Misc >> Security >> changed Default SecureBootMode value to match SMBIOS model to fix Monterey updates. There is no need to change SecureBootModel value in the config, Default will work for everyone.
  • NVRAM >> added BridgeOSHardwareModel NVRAM variable to fix T2 SecureBootMode on Monterey. You do not need to add anything to NVRAM section. This is done internally by OpenCore itself.
  • PlatformInfo >> Generic >> fixed a problem when installing Monterey developer betas by adding large BaseSystem support in AdviseFeatures property. There is no need to enable AdviseFeatures as all the macOS 12 compatible firmware versions have been updated FirmwareFeatures value. AdviseFeatures was a temporary solution to a specific problem and as of now it does not make much sense to be used. Perhaps, only on legacy Mac models if they prefer not to spoof their Mac model and use -no_compat_check boot-arg.
    AdviseFeatures updates FirmwareFeatures (ExtendedFirmwareFeatures / ExtendedFirmwareFeaturesMask) with a new bit added: FW_FEATURE_SUPPORTS_LARGE_BASESYSTEM (0x800000000) - Without this bit, it is not possible to install macOS versions with large BaseSystem images, such as macOS 12.

Linux systems
 

It is highly recommended that people using macOS and Linux together carefully read the OpenLinuxBoot section of the OpenCore Configuration PDF. Linux detection has been improved. There are too many changes to be commented here by someone who barely use Linux. 

Note: SyncRuntimePermissions quirk may need to be set True to avoid early boot failure of the Linux kernel in some firmwares released after 2017.


Utilities
 

Added shim-to-cert.tool to extract OEM signing certificate public key (and full db, dbx if present) from GRUB shim file.

 

Quick guide for newbies

Changes in config.plist

  • UEFI >> Drivers >> added Comment (string) property. Each driver has now 4 keys: Arguments (string), Comment (string), Enabled (boolean) and Path (string).
  • Misc >> Security >> SecureBootMode >> Default value now matches SMBIOS model to fix Monterey updates.

Files to be replaced

  • BOOT folder
  • drivers and tools
  • OpenCore.efi file.

 

Edited by miliuco
  • Like 4
  • Thanks 3
Link to comment
Share on other sites

18 minutes ago, miliuco said:

Thank you @eSaF my friend, I think we are here too late, our age needs 😴

:thumbsup_anim:

Yes Brother I am off to get some well needed rest because we have another big day later with the release of Windows 11. :)

  • Like 1
  • Haha 1
Link to comment
Share on other sites

Posted (edited)

Kexts updated

 

It's advisable to install new versions of:

  • AppleALC 1.6.5 (Added layouts for devices)
  • CpuTscSync  1.0.5 (Fix issue with wakeup time)
  • FeatureUnlock 1.0.4 (Fix typo)
  • HibernationFixup 1.4.4 (Fix issues, automatically puts macOS into sleep/hibernate mode when WhenBatteryIsAtWarnLevel or WhenBatteryAtCriticalLevel bit is set)
  • MacHyperVSupport 0.7 (Fix debug messages, initial networking support)
  • RestrictEvents 1.0.5 (added Monterey software update support with any Mac model, this patch has been disabled when it has fixed in OpenCore)
  • VoodooPS2Conttroller 2.2.6 (Fixed some touchpads not waking after S3)
  • VoodooRMI 1.3.5 (Fix issues, added new device)
  • WhateverGreen 1.5.4 (fix screen issue on ICL platforms).

 

Edited by miliuco
  • Thanks 1
Link to comment
Share on other sites

Still no new releases of Lilu (1.5.6) and VirtualSMC (1.2.7), and no vitty informative message from @vit9696.

Is it OK to mix and match with last month releases of these two kexts? :unsure:

Edited by etorix
Link to comment
Share on other sites

So the release process is complete for this month and there was no change to these two kexts. Thanks!

Does this mean that there is nothing to fix or improve, or rather that the developers are overwhelmed and lack time (or the monthly cycle is too short)?

Link to comment
Share on other sites

Posted (edited)
19 minutes ago, etorix said:

So the release process is complete for this month and there was no change to these two kexts. Thanks!

Does this mean that there is nothing to fix or improve, or rather that the developers are overwhelmed and lack time (or the monthly cycle is too short)?

 

Sometimes a kext remains untouched for months, see IntelMausi as an example. But the most common is that improvements and modifications are made continuously. The problem is that this time the monthly message has not been published in Dortania, this message was always accompanied by the changelogs and links for the new versions of OpenCore and kexts.

Then, there are other ways to know what changes the kexts have undergone, such as https://dortania.github.io/builds/ where you look for each extension in the drop-down to know the changes that have been made in each compilation.

 

Lilu 1.5.6 is not included in the list of updated kexts for OpenCore 0.7.4 but in the builds list you can see that has had a change to help WhateverGreen to improve back light in laptops. Lilu has the same commit number 8b2d712 in both sites, Dortania and Acidanthera.

And VirtualSMC 1.2.7 has had also changes (fan monitoring support).

 

 

 

lilu.png

Edited by miliuco
  • Thanks 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...