Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
A lot of changes in 0.5.4 along with
"Fixed CPU package detection on configurations with multiple CPUs"
Hopefully that will fix multiple CPU detection. Need to test.
Here are all the changes.
 
Last edited:
Just noticed this:
Code:
 This flag specifies whether HII resource section is generated into PE image.
#
  UEFI_HII_RESOURCE_SECTION      = TRUE
This might be related to the blob generated in the firmware, which is now optional? OC keeps updating as I write.
 
  • Like
Reactions: h9826790
cdf:said-
If you installed OC by following the guide, then from your original OC-booted Catalina system, you can simply select the clone in Startup Disk and reboot. In this case, you are still booting through OC, which is installed on the EFI partition of the original disk. For a successful boot, you may have to carry out step 5d in the guide. I don't think that CCC clones the EFI partition. In any case, the clone can still boot without OC. For a successful boot, you need to make sure that you have properly set -no_compat_check (see step 8 in the guide).

I tested a CCC Clone-
cdf: You are right
, CCC does not clone the EFI Partition so a clone of the original disk will not have OC (can’t be used like an original disk w/OC if it goes bad! - but will boot with -no_compat_check!
 
I tested a CCC Clone-
cdf: You are right
, CCC does not clone the EFI Partition so a clone of the original disk will not have OC (can’t be used like an original disk w/OC if it goes bad! - but will boot with -no_compat_check!

you can clone efi with this script:
 
you can clone efi with this script:
Be careful running these scripts if you are using Catalina since the partitions are different. The last time the above script was updated appears to 2 years ago. Thus, I would not use it with Catalina.
 
  • Like
Reactions: startergo
Hello

Mac Pro 4.1 = 5.1 I did everything according to the description. After step 6 when I started the catalina installation the Mac didn't restart anymore. (I couldn't go into recoveries before)

IMG_20200112_221300.jpg
 
Hello

Mac Pro 4.1 = 5.1 I did everything according to the description. After step 6 when I started the catalina installation the Mac didn't restart anymore. (I couldn't go into recoveries before)

View attachment 888229
VMM flag spoofing only works with Westmere Xeons (X56xx, E56xx, W56xx W36xx, L56xx).

Did you change your boot-args?

Code:
nvram boot-args="-no_compat_check"
 
Last edited:
VMM flag spoofing only works with Westmere Xeons (X56xx, E56xx, W56xx, L56xx).

Did you change your boot-args?

Code:
nvram boot-args="-no_compat_check"

ohh. I have single 3.33 (2012/Westmere. :(

nvram: Error setting variable - 'boot-args': (iokit/common) not permitted
 
New Quirk in OC:
OcAppleKernelLib: Implement IncreasePciBarSize quirk
"PCI Devices exposes its internal memory to the HOST via BAR windows. These memory windows are used to read and write card's internal memory. But PCI card puts a limitation on the size of these windows using some default values. However, these window sizes are configurable to expose a wider range of memory through one BAR. But it requires a E2PROM with new size value programmed, so that whenever PCI card is enumerated it gets wider memory range"
 
  • Like
Reactions: crjackson2134
New quirk for Xeons:
  • AppleXcpmForceBoost Type: plist boolean Failsafe: false
Description: Forces maximum performance in XCPM mode.

This patch writes 0xFF00 to MSR_IA32_PERF_CONTROL (0x199), effectively setting maximum multiplier for all the time.

Note: While this may increase the performance, this patch is strongly discouraged on all systems but those explicitly dedicated to scientific or media calculations. In general only certain Xeon models benefit from the patch.
 
( I have Intel Xeon w3680 ) I started again, after I reboot into recovery I can't configure the partition. 5.c)

"EFI found at IODeviceTree./efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point is ’/Volumes/EFI
No BootX creation requested
No Boot.efi creation requested
Can’t statfs /Volumes/EFI/EFI/OC/OpencOre-efi

what am I doing wrong? "nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found"
 

Attachments

  • 0DF44855-62F2-4AA6-B475-21DB40373D30.jpeg
    0DF44855-62F2-4AA6-B475-21DB40373D30.jpeg
    397.3 KB · Views: 214
  • 2008D644-70E5-436F-BA80-1F94A52C1D5F.jpeg
    2008D644-70E5-436F-BA80-1F94A52C1D5F.jpeg
    995 KB · Views: 243
  • 2B1E9A1B-8500-4954-BA21-6464CDFE0AD4.jpeg
    2B1E9A1B-8500-4954-BA21-6464CDFE0AD4.jpeg
    238.1 KB · Views: 251
Last edited:
All dual CPU's use this kext to avoid KP:
[automerge]1578915414[/automerge]
MacOS App to compile Opencore, common drivers and kexts that are used with OpenCore from source.When you click the Build button it will compile the latest commits to the sources using xcodebuild, nasm, and mtoc. Once compile has completed a OCBuilder_Completed folder with the Opencore EFI structure will be produced with all the Drivers, kexts and tools will be placed in the OCBuilder_Completed folder on the location of your selection.
 
Last edited:
  • Like
Reactions: w1z and h9826790
( I have Intel Xeon w3680 ) I started again, after I reboot into recovery I can't configure the partition. 5.c)

"EFI found at IODeviceTree./efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point is ’/Volumes/EFI
No BootX creation requested
No Boot.efi creation requested
Can’t statfs /Volumes/EFI/EFI/OC/OpencOre-efi

what am I doing wrong? "nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found"

can anyone help what the problem is? 10x already fails :(
-Disk A. Newly APFS-formatted drive (GUID scheme) OK
-Disk B. macOS Mojave (sata disk bay 1) OK
-Materials edited "config.plist" OK

Many Thanks!

They succeeded. After try 2, I skipped the smc reset. was a mistake. Many Thanks!! :)
 

Attachments

  • Screenshot 2020-01-13 at 13.58.36.png
    Screenshot 2020-01-13 at 13.58.36.png
    114.6 KB · Views: 195
  • Screenshot 2020-01-13 at 14.00.47.png
    Screenshot 2020-01-13 at 14.00.47.png
    37.5 KB · Views: 245
  • Screenshot 2020-01-13 at 14.02.10.png
    Screenshot 2020-01-13 at 14.02.10.png
    61.8 KB · Views: 240
Last edited:
All dual CPU's use this kext to avoid KP:
[automerge]1578915414[/automerge]
MacOS App to compile Opencore, common drivers and kexts that are used with OpenCore from source.When you click the Build button it will compile the latest commits to the sources using xcodebuild, nasm, and mtoc. Once compile has completed a OCBuilder_Completed folder with the Opencore EFI structure will be produced with all the Drivers, kexts and tools will be placed in the OCBuilder_Completed folder on the location of your selection.

Whats the benefit of using AppleMCEReporterDisabler.kext method instead of just removing the AppleIntelMCEReporter.kext from extensions folder?
 
Whats the benefit of using AppleMCEReporterDisabler.kext method instead of just removing the AppleIntelMCEReporter.kext from extensions folder?
Good question. Every update of Catalina will probably install the missing Kext. With the disabler kext you don't care.
 
  • Like
Reactions: aacemyan
Thanks for the heads up. so all I need to do is add the AppleMCEReporterDisabler.ketxt into the EFI/OC/kext folder? Or do i also need to copy the original AppleMCEReporter.kext from S/L/E into EFI/OC/kext?
 
Thanks for the heads up. so all I need to do is add the AppleMCEReporterDisabler.ketxt into the EFI/OC/kext folder? Or do i also need to copy the original AppleMCEReporter.kext from S/L/E into EFI/OC/kext?
Most probably you will only need the disabler, but if you still have KP then move the original there as well.
 
  • Like
Reactions: w1z
Partial success on my end! I have latest vesions of OpenCore, WEG, and Lilu. Have hardware accelleration enabled, removed AppleMCEReporter.kext, and disabled VMM flag. Catalina is working very well with exception of geekbench giving me half the score of 307/3756 for my dual Xeons. I vaguely remember someone else having this issue but can't recall the fix (if any).

1578964516443.png
 
so culprit is the VMM flag. Once enabled, score jumps back to normal. Is there another way of getting this fixed with VMM flag disabled?
 
So below are my scores for Geekbench 5 on Catalina


OC - No Spoof - No VM Flag - 659/6875
OC - No Spoof - VMM Flag - 625/6752

OC - iMac Pro Spoofing - VM Flag - 307/ 3756
OC - iMac Pro Spoofing - VMM Flag - 626/6713

I'd love to figure out whats going on with the score using VM flag on.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.