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
Things move fast on this forum, sorry, just spotted this!
Basically, I checked the 0.6.1 config file and didn't spot anything in my version which looked incompatible with 0.5.8, so installed that version instead; I just aimed for the oldest version I thought might work. I was having issues updating macOS on my old installation, which was 0.5.5 or 0.5.6, I think.
If you've already blessed the EFI volume you don't need to faff around doing it again. You can just go in, swap out the files, empty the trash, eject and reboot.
From @kcarney81's post above, I wonder if that SecureBootModel option might be the cause of my 0.6.1 woes as well? I'll try it when I'm not, erm, working.
I have posted this several times but I had the same bootpicker loop problem after 0.6.1 upgrade. I downgraded to 0.6.0 (had a backup copy of the entire 0.6.0 EFI). I then redid the upgrade very carefully including re-downloading all files (OC, config, Lilu, WhateverGreen, AppleMCEReportDisabler, NightshiftEnabler, OCBinaryData) - all files. The names don't change for many of the files so I imagine it is easy to get versions mixed up. This second 0.6.1 install worked perfectly. I made no changes to my system so it seems that I either messed up config.plist edits or had mixed versions of accessory files.
If you do 0.6.1 upgrade carefully, did the bootpicker loop happen on very first reboot? (After steps 2 and 3 on first post here). I ask because I went through all the config.plist edits at once and didn't do a reboot at incremental changes so not sure at what step the loop started.
So I did carefully steps 2,3 and 5 checking the config.plist at each step before rebooting when it indicated. All good.
One thing I find is that the command "sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery" doesn't seem to work for me. So the only deviation from the first post was to reboot and do a NVRAM reset (Opt-Command-P-R) and after second boot chime release keys and immediately press Command-R to go to recovery partition.
Mixing config files across versions will likely come back to bite you.
Hi Folks.
Does anyone know what I need to do in order to make my cmp 4.1 to correctly recognize the 1333 memory with OC?
At the moment I'm seeing my new RAM modules as old 1066, but they are 1333.
How can I edit the config file?
TIA
Does anyone know what I need to do in order to make my cmp 4.1 to correctly recognize the 1333 memory with OC?
At the moment I'm seeing my new RAM modules as old 1066, but they are 1333.
How can I edit the config file?
TIA
That is most probably a CPU restriction not OC. What is your CPU?
Note:
Although the memory speed of the UDIMMS is 1333 MHz, they will operate at 1066 MHz or 1333 MHz depending on the processor in the computer.
Mac Pro (Mid 2012 and earlier): How to remove or install memory - Apple Support
Learn how to remove memory from or install memory into your Mac Pro computer (Mid 2012 and Earlier).
Thanks for the clarification.
After reading your suggestion, I used my working config.plist for OpenCore 0.6.0 as the config.plist for OpenCore.0.6.1, instead of using the new version linked in the first post of this thread, and OpenCore 0.6.1 booted my Big Sure Beta 8 to completion to the login screen.
So, the problem seems to be with the template config.plist linked in the first post for this thread, at least for Big Sur betas.
That is most probably a CPU restriction not OC. What is your CPU?
Note:
Although the memory speed of the UDIMMS is 1333 MHz, they will operate at 1066 MHz or 1333 MHz depending on the processor in the computer.
Mac Pro (Mid 2012 and earlier): How to remove or install memory - Apple Support
Learn how to remove memory from or install memory into your Mac Pro computer (Mid 2012 and Earlier).support.apple.com
Thank you man.
I still have the old processors, I'm still a little bit worried about changing them.
hi! guys i read a lot of posts and i cannot find somebody with my trouble, i expect you can help me, i have a macpro 5,1 radeon 7950 flashed
Bay 1 2TB OWC clean
Bay 2 120SSD OWC mojave
i follow the instructions on post 1
and stops in step 3,
boots and loop at boot picker but it's a list not the icon screen,
i select mojave but loops again, i use the OC 0.6.1, and the config.plist
lately add a Disk with el capitan and boots!!
any help is welcome!
Bay 1 2TB OWC clean
Bay 2 120SSD OWC mojave
i follow the instructions on post 1
and stops in step 3,
boots and loop at boot picker but it's a list not the icon screen,
i select mojave but loops again, i use the OC 0.6.1, and the config.plist
lately add a Disk with el capitan and boots!!
any help is welcome!
After having untold amounts of problems trying to install big sur using the micropatcher I gave up and installed OpenCore. After amending the config plist I was able to install big sur without any problems, unfortuantly no WiFi but no matter I’ll update the card at some point.
Beta 5 was working quite well when the update to beta 6 turned up, upon trying to update I found myself exactly where I was with the micropatcher.
stage 1 of the install would complete the it just went into a bootloop, I did some more browsing around the forums and found this
This is a copy n paste
The trick is to un-enroll in the beta program and then re-enroll
Unroll:
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll
Enroll:
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed
I was stuck on Beta 5 and nothing including re-downloading the entire process worked. This worked first time I ran this in terminal and installed beta 5 and then updated to beta 6 7 and 8 flawlessly
Copied from the opencore forum on Facebook
Attachments
Interesting. However, I can't even get into Big Sur Terminal or Recovery to unroll and enroll.
I am in the same position - tried going back to OC 0.6.0 but no better. same boot loop - only on Big Sur Beta 8. Mojave boots fine. Catalina Boots fine...?
So I was able to get back into Beta 8 but only if VMM was toggled on. Seems odd. Did they change something in Beta 8 or am I missing something? I am using @h9826790 bundle.
Edit: And after a reboot it's not working anymore. Hmm...
Edit2: Don't know what happened but I was able to get back into Big Sur. It's working fine now.
Edit: And after a reboot it's not working anymore. Hmm...
Edit2: Don't know what happened but I was able to get back into Big Sur. It's working fine now.
Last edited:
I'm very sorry having to report some anomaly in OpenCore 0.6.1. I can't be much more specific. I've now been trying to update my OpenCore 0.6.0, which works great, to the newer 0.6.1 release for roughly two weeks. Unfortunately, no matter how I try to adapt my current config.plist to the new expected parameter syntax, I've always ended up in the infamous boot loop. This afternoon, I decided to start from scratch, so I downloaded the vanilla version of 0.6.1 from the first post of this thread, together with the basic config.plist from the very same post. I copied all that to the blessed EFI volume, inside the EFI folder and restarted my Mac Pro 5,1. A text-based Boot Picker appeared. Guess what. The loop is still there. Since I haven't modified that basic configuration of 0.6.1 in any way, I don't know how to proceed. I guess it must work for some or many of you, but it doesn't for me. And I insist: I haven't modified it in any way, shape or form. Is there a solution? Is there a way to debug an unmodified installation of 0.6.1?
EDIT: The loop I'm talking about has nothing to do with failed Big Sur beta installations. I haven't downloaded any betas of Big Sur. The loop is of OpenCore itself. No matter the operating system I choose (like Catalina, High Sierra or Snow Leopard), no system is started and the Boot Picker is displayed again, indefinitely.
EDIT: The loop I'm talking about has nothing to do with failed Big Sur beta installations. I haven't downloaded any betas of Big Sur. The loop is of OpenCore itself. No matter the operating system I choose (like Catalina, High Sierra or Snow Leopard), no system is started and the Boot Picker is displayed again, indefinitely.
Last edited:
I got a 10.15.7 update today but when I hit restart instead of updating it just restarts like normal, is something wrong happening?
I have the vmm flag enabled so I don't get why is not updating and the button to do so is just restarting the Mac
I have the vmm flag enabled so I don't get why is not updating and the button to do so is just restarting the Mac
Yeah, I'm not sure what's goin on with 0.6.1. I was able to install 10.15.7 with VMM on. I can't get into Big Sur Beta 8 unless I have VMM on. Does anyone have that problem? It's so odd to me. I have Spoofing false but it's just odd. I never needed VMM to get into Big Sur after install. Debating whether to reinstall Big Sur.
my issue is different, when I hit restart, it shows the apple logo and progress bar for a few seconds before just go black and restart the entire Mac.
I'm still on OC 0.6.0, not sure if it's safe to update to 0.6.1 knowing some are reporting getting looped back to the picker
Thank you, I guess. I wonder if the DEBUGging version can actually debug an error of the RELEASE version.
Not just Big Sur, my boot-loop issue was with Catalina, good ol' 10.15.3 (as it was).
Yes, that's indeed the case. There's something wrong in either 0.6.1 itself or with the config.plist provided, and it has nothing to do whatsoever with the specific operating system you are trying to boot. The boot affects OpenCore itself, not Catalina in any of its iterations.
Yes there is an error. @cdf
SecureBootModel needs to be either properly set (not only through the config file) or disabled. So for BigSur you will also need the board-id. The attached config file should let you boot. Let me know if it does not.Edit: I forgot that for dual CPU's you will need also
DisableMCEReporter.kext. ALso you can add WEG and LILU kexts.
Last edited:
Is that board-id spoofing a requirement for Big Sur? I use it personally for AMD hardware acceleration, but interesting if it's a requirement now.
@startergo, I've attached my config.plist. Do you see anything odd with it? I don't get what's going on with Big Sur.
EDIT: I'm not spoofing and didn't need to when in Big Sur until Beta 8.
EDIT: I'm not spoofing and didn't need to when in Big Sur until Beta 8.