[HOW TO] OpenCore 0.6.3 > 0.6.4 differences

[rheneas]

I had a similar experience trying to update to 0.6.4. After updating kexts, I tried to update the config.plist according to changes detailed in the Differences.PDF. I also submitted my updated config.plist to the OpenCore Sanity Checker https://opencore.slowgeek.com/ for my Skylake machine, and made the few changes it recommended. Test boots hung.

I was successful updating from 0.6.3 on my backup drive and main drive with sound, USB and sleep working.

 

[miliuco]

I had a similar experience trying to update to 0.6.4. After updating kexts, I tried to update the config.plist according to changes detailed in the Differences.PDF. I also submitted my updated config.plist to the OpenCore Sanity Checker https://opencore.slowgeek.com/ for my Skylake machine, and made the few changes it recommended. Test boots hung.

I was successful updating from 0.6.3 on my backup drive and main drive with sound, USB and sleep working.

How does the failure occur? Can you detail more?
Upload here the config.plist file that you made for 0.6.4 and we will see it.

 

[rheneas]

Thanks. The failure occurred quickly. Verbose mode displayed for about 3/4 of my screen and then just hung, if I remember correctly. I have attached my "test" 0.6.4 config.plist and the analysis by Sanity Checker.

 

[miliuco]

Thanks. The failure occurred quickly. Verbose mode displayed for about 3/4 of my screen and then just hung, if I remember correctly. I have attached my "test" 0.6.4 config.plist and the analysis by Sanity Checker.

Ok. Wait for me to review the files and I'll tell you something around here.

 

[miliuco]

Thanks. The failure occurred quickly. Verbose mode displayed for about 3/4 of my screen and then just hung, if I remember correctly. I have attached my "test" 0.6.4 config.plist and the analysis by Sanity Checker.

The main error I think is given by the PlayChime key within UEFI - Audio, this key was previously of type boolean (True False) but it has changed to type String. You can read in the first post:
"In UEFi / Audio, PlayChime key has changed its type, from boolean to string. Options are:
Auto - checks the NVRAM to see if the chime is set but not muted
Disabled - disables chime unconditionally
Enabled - enables chime unconditionally.
It can be left empty. "
I've changed this but there are more changes (see below).

Note: Sanity checker doesn't show error but it doesn't show that key either, it probably doesn't seem a key wellformed and it's skipped.

 

[Feartech]

The main error I think is given by the PlayChime key within UEFI - Audio, this key was previously of type boolean (True False) but it has changed to type String. You can read in the first post:
"In UEFi / Audio, PlayChime key has changed its type, from boolean to string. Options are:
Auto - checks the NVRAM to see if the chime is set but not muted
Disabled - disables chime unconditionally
Enabled - enables chime unconditionally.
It can be left empty. "
I've changed this just for you to test because it's the only major bug I've seen. I attach the new EFI (just that change). Try and tell me if now macOS starts fine with 0.6.4.

Note: Sanity checker doesn't show error but it doesn't show that key either, it probably doesn't seem a key wellformed and it's skipped.

when you download new OC version, make your changes in your config.plist and then use the ocvalidate tool to make sure there are no errors

 

[miliuco]

when you download new OC version, make your changes in your config.plist and then use the ocvalidate tool to make sure there are no errors

Yes, that tool is more useful for these things than Sanity checker, thanks for the reminder.

 

[miliuco]

Thanks. The failure occurred quickly. Verbose mode displayed for about 3/4 of my screen and then just hung, if I remember correctly. I have attached my "test" 0.6.4 config.plist and the analysis by Sanity Checker.

Indeed, as @Feartech says, if you do ocvalidate (it is in Utilities folder of each OC version, you must use the version whose config.plist you want to check) these errors appear in your config.plist file:

OPENCORE / OpenCore 0.6.4 / OC / Utilities / ocvalidate> ./ocvalidate
OCS: Missing key Patch, context <Booter>!
OCS: No type match for Tools at 5 index, expected type integer got dict, context <Misc>!
OCS: Failed to parse data field as value with type data and <30: b5: c2: 28: 98: d6> contents, context <ROM>!
OCS: Failed to calculate size of Enabled field containing <empty> as type integer, context <PlayChime>!

They must be repaired one by one:

• add Patch key in Booter
• modify Tools key
• to use MAC address as ROM you have to write, as Data, the MAC without double dots or other characters in the plist file editor, if you write it in text editor you have to do it as Base64, but you have the MAC as is, even with double dots, directly as text
• the change of type in the PlayChime key (already commented).

With those 4 changes it no longer gives an error in ocvalidate. This is the valid EFI.

 

[rheneas]

when you download new OC version, make your changes in your config.plist and then use the ocvalidate tool to make sure there are no errors

Thanks, much appreciated!

 

[rheneas]

Indeed, as @Feartech says, if you do ocvalidate (it is in Utilities folder of each OC version, you must use the version whose config.plist you want to check) these errors appear in your config.plist file:

OPENCORE / OpenCore 0.6.4 / OC / Utilities / ocvalidate> ./ocvalidate
OCS: Missing key Patch, context <Booter>!
OCS: No type match for Tools at 5 index, expected type integer got dict, context <Misc>!
OCS: Failed to parse data field as value with type data and <30: b5: c2: 28: 98: d6> contents, context <ROM>!
OCS: Failed to calculate size of Enabled field containing <empty> as type integer, context <PlayChime>!

They must be repaired one by one:

• add Patch key in Booter
• modify Tools key
• to use MAC address as ROM you have to write, as Data, the MAC without double dots or other characters in the plist file editor, if you write it in text editor you have to do it as Base64, but you have the MAC as is, even with double dots, directly as text
• the change of type in the PlayChime key (already commented).

With those 4 changes it no longer gives an error in ocvalidate. This is the valid EFI.

Thanks for the valuable lesson and for correcting my config.plist. Happy New Year!