Contribute
Register

[HOW TO] OpenCore 0.7.0 > 0.7.1 differences

Joined
Dec 10, 2010
Messages
738
Motherboard
Gigabyte Z390 Aorus Elite
CPU
i9-9900K
Graphics
RX 580
Mobile Phone
  1. iOS
Please read the message from vit9696 with the best summary you can read about what's new in OpenCore 0.7.1.

This time we may think that we are facing a minor OpenCore update because we have to learn and modify an affordable number of features. Nothing comparable to June's update. However this is not entirely true. What happens is that the 0.7.0 update was huge, much more complex than usual.

This 0.7.1 update may seem simple compared to the previous one but it does not stop having important changes:
  • more than 60 builds have been released
  • some bugs have been fixed
  • documentation has been improved (adding debug docs updates)
  • OpenCanopy continues to receive improvements
  • builtin firmware versions have been updated
  • PCI device info dumping has been added to SysReport
  • new kext patcher for Lilu, supporting macOS from 10.6 to 12
  • For Monterey:
    OpenCore and kexts have been adapted to macOS 12 Monterey
    added BlueToolFixup to fix Bluetooth issues on macOS 12
  • For Windows 11:
    added a document containing requirements and potential paths to work around them
    added TpmInfo.efi tool to check TPM status.
config.plist

ACPI > Quirks > added SyncTableIds (boolean): to sync table OEM identifiers with the SLIC table to prevent licensing issues in older Windows operating systems. It can be False.

Kernel > Scheme > added CustomKernel(boolean): to support custom kernels from the Kernels directory located at the root of the ESP partition. For unsupported platforms including Atom and AMD that require modified versions of XNU kernel in order to boot. It can be False.

OpenCanopy
  • Fixed transparency click detection on OpenCanopy boot entries for the icon to be selected when clicking on the transparent areas. Note for artists: transparent areas of icons can have opacity=1% to ensure correct operation, although in theory it is not necessary with this OpenCanopy enhancement.
  • Added recommended Apple12 and Windows11 flavours.
  • Fixed various bugs.
  • Improved documentation.
Tools

TpmInfo.efi: to check Intel TPM capability on the platform, which allows using TPM 2.0 if enabled. The tool does not check whether TPM 2.0 is actually enabled or disabled. TpmInfo must be run from the UEFI Shell, if it is run from the picker it shows a text message so short that it is impossible to read what it says.

ocvalidate

Fix path length calculation and remove the wrong check for Misc > Entries > Path and Misc > Boot > PickerVariant. Sometimes ocvalidate showed an error message (path too long) even if it did not exceed 128 bytes. As per ocvalidate's Readme: "All the paths relative to OpenCore root must be 128 bytes total".

kexts

It's recommendable to update kexts to the new versions:
  • AirportBrcmFixup
  • AppleALC
  • BrcmPatchRAM
  • CPUFriend
  • IntelMausi
  • Lilu
  • NVMeFix
  • RestrictEvents
  • SidecarFixup
  • VirtualSMC
  • VoodooPS2
  • WhateverGreen.
 
Last edited:
Joined
Jul 11, 2012
Messages
450
Motherboard
Gigabyte GA Z68XP-UD3
CPU
i7 3770
Graphics
GT 210
Mac
  1. iMac
  2. Mac mini
Mobile Phone
  1. Android
Update went ok for me.
Side note: I've noticed that useful utilities such as OCConfigCompare and ProperTree are getting updates too (from time to time), even if they don't have a build number.
For example, the current version of OCConfigCompare displays syntax errors that weren't shown in the former version I had. ProperTree's "OC Clean Snapshot" now warns you if it detects inconsistencies in your kexts (duplicate CFBundleIdentifiers, in my case — because I have different versions of AppleALC.kext and RealtekRTL8111.kext in subfolders).
 
Joined
Dec 10, 2010
Messages
738
Motherboard
Gigabyte Z390 Aorus Elite
CPU
i9-9900K
Graphics
RX 580
Mobile Phone
  1. iOS
Note about TPM

The integration of TpmInfo.efi in OpenCore 0.7.1 has an obvious reason in the Windows 11 release that requires TPM to be installed. In some BIOSes TPM option is not found and PTT option does appear, both are equivalent but it is worth explaining how they differ.

TPM

Last word in securing personal computers and servers has been the Trusted Platform Module (TPM) specification, a technology designed to provide security features.
TPM is a chip designed to perform cryptographic operations that includes several physical security mechanisms that make it resistant to alterations. It has specific security features to prevent malicious software from altering your system.
TPM is built into the CPU. If your computer has a processor from the last 6 years it is almost certain that it has a TPM.
In BIOS this option is usually in Advanced > Trusted computing or something similar. It can be TPM enable (auto) or disable.

PTT

Intel introduced a change, Intel Platform Trust Technology (PTT) architecture, which implements TPM in system firmware so computers with Intel PTT don't require a dedicated CPU. To your operating system, PTT looks and acts like TPM.
PTT is being deployed on low-power PCs, tablets and other devices that in the past could not bear the additional cost, complexity or other requirements demanded by hardware-based TPM.

So in BIOS you can have TPM or PTT, depending on the hardware manufacturer.
 
Joined
Oct 10, 2015
Messages
893
Motherboard
Z370 AORUS Gaming 3
CPU
i5-9600K
Graphics
RX 580
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. iOS
I still wonder if OpenCore will address Secure Boot.
 
Joined
Feb 23, 2020
Messages
132
Motherboard
Dell Precision M4700
CPU
i7-3740QM
Graphics
M4000
I still wonder if OpenCore will address Secure Boot.
what is there they could do? I guess they could try to get the releases signed by Microsoft but I'm not quite sure they'd be willing to sign something like OpenCore.

If you really wanted to use secureboot, they mention signing OpenCore.efi yourself plus all the drivers within their documentation. You'd need to enroll those keys though into your BIOS yourself. I haven't seen Windows 11 require Secureboot to be enabled, just that the feature exists.
 
Joined
Oct 10, 2015
Messages
893
Motherboard
Z370 AORUS Gaming 3
CPU
i5-9600K
Graphics
RX 580
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. iOS
what is there they could do? I guess they could try to get the releases signed by Microsoft but I'm not quite sure they'd be willing to sign something like OpenCore.

If you really wanted to use secureboot, they mention signing OpenCore.efi yourself plus all the drivers within their documentation. You'd need to enroll those keys though into your BIOS yourself. I haven't seen Windows 11 require Secureboot to be enabled, just that the feature exists.
I don’t need Secure Boot. However, since Windows 11 asks for some annoying requirements, some clarifications may be needed.
 
Joined
Aug 18, 2011
Messages
446
Motherboard
ASUS Z390-I Gaming
CPU
i5-9600K
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
Yes I realize that I may have to run the debug version of OC 0.7.1, but I thought I would ask this question here before going down that path.

This is only on my Z97 Gigabyte MB. I don't see any problems on my Z370 Asus Hackintosh with 0.7.1.

The OC selector comes up, displays version 071, I have a couple of boot devices; I select my Bug Sur SSD and the screen starts to fill with text - large font and then halts. Just about where it is going to boot the OSX image, I surmise.

I have carefully updated the config.plist and all the OC / BOOT files, and Resource directory.

Now if I replace my 070 (ocvalidate no issues) config.plist, with my 068 version of conflig.plist, the OC warns about invalid or missing schemas, but BOOTS into the OSX with no problems.

I then restarted the transition of my config.plist from 068 to 070, one schema at a time. I finally narrowed the change down to the NVRAM properties update. If I make any changes in that portion of the config.plist, in particular

7C436110-AB2A-4BBB-A880-FE41995C9F82 (APPLE_BOOT_VARIABLE_GUID)

entry, and in particular bring these properties up to date
prev-lang:kbd
run-efi-updater
which involves changing their data types and values, the no BOOT issue occurs.

This is in the ADD section of NVRAM.

Funny thing too is that if I copy/paste the original version of the 7C436110-AB2A-4BBB-A880-FE41995C9F82 key and children the problem remains. No boot.

Any suggestions?
 

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
2,367
Motherboard
Gigabyte Z97X-UD5H
CPU
i7-4790K
Graphics
HD 4600 / RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
Did you use the ClearNvram or ResetNvram tool and reboot the system from the OC GUI, before trying to boot in to macOS with the new 0.7.1 setup?

I am using a few Z97 boards and haven't had any issues like you are reporting, after updating their OC setup to 0.7.1.
 
Joined
Aug 18, 2011
Messages
446
Motherboard
ASUS Z390-I Gaming
CPU
i5-9600K
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
@Edhawk

Yes I tried ResetNvram tool. No difference. Am not aware of a ClearNvram option, or do you mean the same thing?

Anyhow would really appreciate it if you could share your NVRAM and children properties from your config.plist and Z97 MB with me. Thanks in advance.
 
Top