Contribute
Register

[HOW TO] OpenCore 0.7.7 > 0.7.8 differences

Status
Not open for further replies.
Joined
Dec 10, 2010
Messages
1,367
Motherboard
Gigabyte Z390 Aorus Elite
CPU
i9-9900K
Graphics
RX 6600 XT
Mobile Phone
  1. iOS
You can download OpenCore 0.7.8 from Acidanthera and Dortania, where there is a short message by vit9696.

Main changes
  • Documented a bug on some Intel Visual BIOS (e.g. Intel NUC) whereby if any boot option refers to a path on a USB drive, then that is the only boot option shown when any USB drive is inserted. A solution is proposed.
  • Updated SIP disable default value: OpenCore uses 0x27F while csrutil disable sets 0x7F on macOS Big Sur and Monterey and 0x77 on Catalina.
Drivers
  • AudioDxe: Fixed bug (introduced in 0.7.7) not disabling unused channels.
  • OpenCanopy: Fixed crash on no mouse support in password verify.
  • OpenLinuxBoot: Added support for .contentFlavour and .contentDetails files and other updates and improvements.
Utilities
  • Ocvalidate: Warn on insecure DmgLoading (Disabled or Any) with SecureBootModel non-Disabled (it causes critical error in runtime).
Kexts

  • AirportBrcmFixup 2.1.4 (Added boot-arg and property brcmfx-delay to better support Monterey and other improvements)
  • AppleALC 1.6.9 (Added or updated codecs: ALC897, ALCS1220A. ALC294, ALC1220 and other improvements)
  • FeatureUnlock 1.0.6 (Refactored code files, improved performance during patching, added Universal Control unlocking only in 12.3 beta for now)
  • Lilu 1.6.0 (Improvements)
  • RestrictEvents 1.0.7 (Fixed detecting CPU core count on Intel CPU with altered topology)
  • WhateverGreen 1.5.7 (Fixed maximum backlight level on Ice Lake IGPUs).
Thank you OpenCore Team!!!
 
Last edited:
Hi! Looks like SystemAudioVolumeDB has been removed from NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 in Sample.plist (was present in 0.7.7).
Is it an oversight or can we get rid of that key if not needed?

N.B.: ocvalidate says "no issue" with or without that key. Boots ok without, for me. :thumbup:
 
Last edited:
Hi! Looks like SystemAudioVolumeDB has been removed from NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 in Sample.plist (was present in 0.7.7).
Is it an oversight or can we get rid of that key if not needed?

N.B.: ocvalidate says "no issue" with or without that key. Boots ok without, for me. :thumbup:
SystemAudioVolumeDB is not a mandatory key, it can be present or not, that's why the tool considers valid the config.plist file.
In fact this variable is included in the OpenCore 0.7.8 configuration PDF in section 9.5 Other Variables: "The following variables may be useful for certain configurations". This may change in future versions of OpenCore.
 
SystemAudioVolumeDB is not a mandatory key, it can be present or not, that's why the tool considers valid the config.plist file.
In fact this variable is included in the OpenCore 0.7.8 configuration PDF in section 9.5 Other Variables: "The following variables may be useful for certain configurations". This may change in future versions of OpenCore.
Until now I thought that the keys present in Sample.plist were mandatory... ;) Good to know that it's not the case or that it might be the case for one version and not any more for the next.
 
It would appear that the current release version of OCAT is still only for OC 0.7.7 and those of us who want to update through it will need to wait for the OCAT 0.7.8-compatible version to be released - hopefully soon.

EDIT: OC version 0.7.8-compatible release of OCAT is now up on Github (for some reason, the previous version I had wouldn't see the update and I had to DL the new version instead). Afterward, I used OCAT for the first time to update OC to 0.7.8 and it was so much smoother than doing so by hand-copying and pasting all the necessary files. No errors in OCvalidate, either.
 
Last edited:
Basically the only difference for config.plist this time is the removal of SystemAudioVolumeDB.
 
Nothing under NVRAM->Add is technically necessary. They're just NVRAM entries that OpenCore can add, such as boot-args. You could technically get rid of it and set up boot-args and SIP through recovery.

SystemAudioVolumeDB I think was a way to set the volume for AudioDXE for boot chime, though I'm not 100% sure about that. I think it now reads either one or two values from NVRAM which macOS sets. This means that the boot chime volume should be the same as the last set volume in macOS.
 
after rest nvram opencore not detect windows but detect debian and mac
I know how to return it back manually
how to prevent that to occure
 
@mbatrawi
How do you return it back manually?
 
Status
Not open for further replies.
Back
Top