Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I've tried it both ways actually. Target OC drive remains blessed regardless of whether or not I reset the nvram using PRAM reset.
That sounds like a modern miracle! I was not aware that the "blessed" condition of a path could survive the resetting of the memory where the blessed path indication resides!
Now, more seriously, are you blessing OC from outside of OC itself? Because, if you do it from inside, all sorts of havoc can result.
Hello again guys (@cdf , @h9826790 , @tsialex , etc..) those of us who are not experts in all this like me can never thank you enough for your knowledge, work and effort that you share here and that allows us to continue using our "mature mac's".
Following Post #1 everything as expected:
OC 0.6.8 Catalina migrated directly to 0.7.4 Big Sur (11.6), everything working without problems
Hardware Acceleration, Handoff, Thunderbolt 3, 10Gbe .......
Infinite thanks !!!!
Following Post #1 everything as expected:
OC 0.6.8 Catalina migrated directly to 0.7.4 Big Sur (11.6), everything working without problems
Hardware Acceleration, Handoff, Thunderbolt 3, 10Gbe .......
Infinite thanks !!!!
Huge thanks and kudos to CDF, Syncredic and other knowledgeable folks for keeping my Mac Pro current! Trying to update OpenCore to 7.04. I am unable to validate the config.plist. I've updated the config file, added the BigSur plus patch and removed the lateBloom kext and lateBloom text from config.plist. All edits validate UNTIL I add the BigSur patch. Terminal results of patch addition are:
plutil -convert xml1 config.plist && plutil config.plist
config.plist: Property List error: Close tag on line 313 does not match open tag array / JSON error: JSON text did not start with array or object and option to allow fragments not set.
I'm attaching my config.plist in the hope someone sees a solution.
Well.. I had to add .txt onto the config.plist file in order to select it for attachment?, but it is the plist file.
plutil -convert xml1 config.plist && plutil config.plist
config.plist: Property List error: Close tag on line 313 does not match open tag array / JSON error: JSON text did not start with array or object and option to allow fragments not set.
I'm attaching my config.plist in the hope someone sees a solution.
Well.. I had to add .txt onto the config.plist file in order to select it for attachment?, but it is the plist file.
After the last </dict> of the patch, you have <array/>. It should be </array>. Notice the position of the forward slash.
I searched and didn’t see anyone else talking about this, so here goes:
MP5,1 no crazy hardware. I was on 11.3 with 0.6.6; I finally found the time to upgrade to 0.7.4 and then go to 11.6. Everything checked out and was working, so I d/l the 11.6 update and it’s in a boot loop after it rebooted.
I booted into Mojave, swapped to the generic script I had setup that only has SurPlus injected. Same thing. I got frustrated, watched an episode of Buffy the VampSlayer and then got an idea: Set the VMM Flag to ON. I shouldn’t need it, but what the hell. I put the C in the string and it booted!
Update finished, and I turned it off. Stuck in the boot loop! All it says is “your Mac encountered a problem”. This is with the sample/generic plist with just Surplus, mind you. I rebuilt the plist, one thing at a time…OC, WiFi, etc. Still no dice unless VMM is ON.
Not sure why or what, but I have to have VMM turned ON to even boot. With 0.6.6 and 11.3 VMM was set to off.
ETA: Yes, HWAccel is setup
MP5,1 no crazy hardware. I was on 11.3 with 0.6.6; I finally found the time to upgrade to 0.7.4 and then go to 11.6. Everything checked out and was working, so I d/l the 11.6 update and it’s in a boot loop after it rebooted.
I booted into Mojave, swapped to the generic script I had setup that only has SurPlus injected. Same thing. I got frustrated, watched an episode of Buffy the VampSlayer and then got an idea: Set the VMM Flag to ON. I shouldn’t need it, but what the hell. I put the C in the string and it booted!
Update finished, and I turned it off. Stuck in the boot loop! All it says is “your Mac encountered a problem”. This is with the sample/generic plist with just Surplus, mind you. I rebuilt the plist, one thing at a time…OC, WiFi, etc. Still no dice unless VMM is ON.
Not sure why or what, but I have to have VMM turned ON to even boot. With 0.6.6 and 11.3 VMM was set to off.
ETA: Yes, HWAccel is setup
Last edited:
If you attach a copy of your configs, then perhaps we could take a look.
No, this is not possible with any OC setup.
If you have a dual-socket machine, you'll need to include the AppleMCEReporterDisabler kext. You might also want to try disabling the wireless card kexts. Other than that, I'm not seeing anything out of the ordinary here.
Mid 2010 5,1; Single 2.8 QC Xeon; Radeon RX580 8GB; no NVMe; 2 spinners (Mojave & TimeMachine) and 1 SSD (BigSur); 32GB RAM. The config I uploaded is what I’m running to get everything working.
The generic plist, that wouldn’t work with VMM off, only had SurPlus enabled. All configs need the VMM Flag on to boot, otherwise it’s a boot error. I thought it might be the WiFi, so I took that out from the current config and same results; had to have VMM on.
If you can think of something you want to look at further, let me know and I’ll happily provide. I’m baffled.
Not sure if you have mentioned where you derived your config.plist from, but it's missing a
-no_compat_check boot-args setting in the NVRAM section:
Yup. That’s part of the HW Acceleration. See First Post in this thread, under “Advanced Config”.
What are the direct disadvantages of leaving the VMM flag constantly on? Let's assume I do not care about the 5 % performance loss.
VMs effectively don't manage power, it's the host that do most power management. You are making macOS to think that it is running inside a VM.
SpeedStep disabled, CPU frequency is fixed.
If you want H/W Acceleration, then follow the guide in this post #1,314 by @h9826790. If you download the latest OC package in that post and examine the config.plist, you will notice
-no_compat_check is added to NVRAM key 7C436110-AB2A-4BBB-A880-FE41995C9F82 even though that config is spoofing an iMacPro1,1 (so should not need that boot-arg). It's does not do any harm and may fix your issue.HAHA. Well actually, when the blessed drive is missing.... the Apple bootstraper goes looking for a valid efi and boots that. Since the drive is the only with any efi at all, it always gets chosen or otherwise "effectively remains blessed" even though thats not what happened "technically". Common english phenomena.
So I didn't figure out the issue but I did figure out a way to get up and running.
I jumped on a 2014 MBP and used Open Core Legacy patcher GUI to patch the bootable usb with installation media. I was able to boot from the efi on that usb. Then I installed to a sata drive in the mac Pro. Once installed I ran the legacy patcher again on the USB but from the MacPro this time and it corrected all the symbios and stuff so now I've got DRM and Full hardware acceleration with hybridization as a MacPro 7,1 (not an iMacPro). Then I got my nvme up and running again and moved from my sata drive to a different sata drive powered by pcie.
One thing I did try while getting to this very stable setup is I tried hybridization as an iMacPro and it broke my efi installation. I'm not convinced that approach always works. OpenCore LEgacy patcher decided to hybridize my machine as a MacPro7,1.
Anyhow, I need to figure out how to configure this thing manually because the only way I've been able to get an efi was by running that gui and OpenCore Legacy Patcher is already using out of date open core. Could someone post their (fully working, drm + hdwr accl) config.plist so I can see what I'm doing wrong?
Thanks in advanced.
Perhaps. I’m more to sticking with what cdf publishes, but for shitsngiggles I’ll give it a go and see what happens at some point. Worst case it wont boot and I have to go into Mojave and waste 30m after hours.
I’d really like to not have the VMM on so power management can attempt to save the light bill.