MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[tsialex]

You are right. I have tried all the suggestions above and none have worked. It looks like I have to reinstall Mojave on the NVMe. Thanks for the reply again.

About the RAID, I searched through the 337 pages of this thread and didn't find much other than people not be able to see their RAIDs after installing Catalina and Big Sur. I had used the now obsolete thread (https://forums.macrumors.com/thread...to-make-catalina-work-with-macpro5-1.2183978/) and (https://forums.macrumors.com/threads/catalina-on-raid-with-apfs-on-macpro-5-1.2216730/) where I was able to run 10.15.4 on my Amfeltec RAID but updating to 10.15.5 broke it.

There reason I tried using OC and RAID was that some people earlier in the thread mentioned that the way OC works may pave the way for running macOS off of RAIDs too. I guess I can start a new thread and find out. My intention was to use OC on the RAID if it works if not Update my NVMe Mojave to 11.2.3 using OC.

As for mentioning a potential macOS install problem here was to literally find out if it was an OC problem or not. It may look so at first but it is not, but if other users also run to the same problem as me when using OC then these posts are useful for them to point them to the right direction.

Apple never implemented booting from APFS RAID arrays because they wouldn't want to add even more complexity to sealed containers.

OpenCore won't magically make booting from APFS RAID supported, it's an APFS limitation plus the way Apple now seal the container.

 

[manielli]

Re-installed Mojave on the NVMe SSD and redid OC install, all is working fine now. Upgrading the NVMe SSD to Catalina right now. Is Big Sur 11.2.3 the last version that can be installed on NVMe SSDs?

 

[0134168]

Re-installed Mojave on the NVMe SSD and redid OC install, all is working fine now. Upgrading the NVMe SSD to Catalina right now. Is Big Sur 11.2.3 the last version that can be installed on NVMe SSDs?

Correct.

 

[manielli]

Correct.

Thank You.

I installed 11.2.3 without a problem, but left the computer so it can restore my data from iCloud. Came back to it and could not wake it up. I have done all the advanced config instructions for hardware acceleration too (not sure if that’s related or not). Is this a know issue with 5,1 and 11.2.3?

 

[0134168]

Thank You.

I installed 11.2.3 without a problem, but left the computer so it can restore my data from iCloud. Came back to it and could not wake it up. I have done all the advanced config instructions for hardware acceleration too (not sure if that’s related or not). Is this a know issue with 5,1 and 11.2.3?

Can´t tell you. What I did is cloning my Catalina SSD, then updated to Big Sur. Works like a charm. I work with Catalina, and boot from Big Sur from time to time for testing purposes.

 

[sfalatko]

Thank You.

I installed 11.2.3 without a problem, but left the computer so it can restore my data from iCloud. Came back to it and could not wake it up. I have done all the advanced config instructions for hardware acceleration too (not sure if that’s related or not). Is this a know issue with 5,1 and 11.2.3?

So you should have an HDD with Mojave (and a clean EFI partition), and Big Sur on the NVME with OC in the EFI partition of the NVME correct per the guide in post 1 correct? If you don’t have it set that way I would move OC to the NVME, delete it from the HDD, and rebless it on the NVME. You really need a clean Mojave install without OC to manage your machine and fix/make changes to OC.

If all of that is set up, I would reboot (you probably have to hold the power button for 10 seconds to get it to shut down) and see if you can select the Big Sur partition and boot into Big Sur with OC. No one has reported problems with 11.2.3 - it was only 11.3+ that is causing boot problems on the cmp.

 

[manielli]

So you should have an HDD with Mojave (and a clean EFI partition), and Big Sur on the NVME with OC in the EFI partition of the NVME correct per the guide in post 1 correct? If you don’t have it set that way I would move OC to the NVME, delete it from the HDD, and rebless it on the NVME. You really need a clean Mojave install without OC to manage your machine and fix/make changes to OC.

If all of that is set up, I would reboot (you probably have to hold the power button for 10 seconds to get it to shut down) and see if you can select the Big Sur partition and boot into Big Sur with OC. No one has reported problems with 11.2.3 - it was only 11.3+ that is causing boot problems on the cmp.

I have the OC in EFI partition of a USB Flash. The HDD with Mojave is intact. Held down the power button and rebooted back into Big Sur. Right now I switched to Mojave and back to Big Sur, keyboard and mouse were not working, even though they were working at the bootpicker screen. Held down power button again and rebooted to Big Sur without a problem. It looks like it is just being a bit finicky, other than that it is working well.

Isn't it better to keep the OC on the EFI of a USB drive, so that I can remove it when I encounter problems so I can boot back into Mojave by resetting NVRAM? I guess the Big Sur on the NVMe SSD would be useless without OC, so I might as well keep OC on the EFI of the NVMe?

 

[Dewdman42]

The USB flash drive will work. You can also alternatively use the EFI of any other drive other then the one in drive bay #1

In other words, by default the Mac would try to boot the first bootable drive it finds. On my system it it first attempts a drive that is on a PCIe card (but is not NVMe), then it attempts drive bay #1, then drive bay #2, etc.. So I make sure my PCIe drives have no OS on them and I put generic Mojave on drive bay #1 and I use an EFI on any other drive other then my PCIe card nor drive bay #1...so that the EFI will only be booted if it has been explicitly blessed to do so.

That way, if I clear NVRAM or even just pull that EFI flash drive out...then the default will be for the Mac to look in a certain order for the first bootable drive, which I have made sure is always my native non-OC Mojave drive.

I used to use a different drive in my system for the EFI, but then later switched to using a flash USB with the EFI...either way can work fine. Its just a fallback for me, once I learned more about OC and became more comfortable it has become extremely unusual for that to ever happen to be honest...But still its good that if there is any problem, I can just clear the NVRAM, boot to Mojave and fix whatever needs to be fixed in OC to get it working again. Since its on a USB flash, I don't even have to zap the NVRAM right away either if I want to do that.. I also keep installer media on that USB flash so that in a very worst case scenario I could hypothetically boot the USB flash itself into the installer or recovery mode.

 

[Dewdman42]

ps - if you haven't been following other related threads, by the way, you should know that BigSur is nebulous to use on the 5,1 at this time. You can't go past 11.2.3 really. Most are choosing to stick with Catalina for the time being, including myself. And I personally have my doubts that even 11.2.3 might be messing with the NVRAM in ways that could confuse Mojave or Catalina if and when you're trying to switch back and forth...but its not clear right now... FWIW.

 

[manielli]

ps - if you haven't been following other related threads, by the way, you should know that BigSur is nebulous to use on the 5,1 at this time. You can't go past 11.2.3 really. Most are choosing to stick with Catalina for the time being, including myself. And I personally have my doubts that even 11.2.3 might be messing with the NVRAM in ways that could confuse Mojave or Catalina if and when you're trying to switch back and forth...but its not clear right now... FWIW.

Thanks for all the info. I have indeed put the OC EFI on a USB Flash drive with a bootable installer of Mojave and Catalina there just in case anything goes wrong again. I have my non-OC Mojave HDD in Bay 1, what is the harm of putting OC on the EFI of the NVMe which is running 11.2.3 (If anything happens that NVMe's macOS is not accessible anyways). And I am aware of the haziness of the 11.2.3, and since I had to nuke my Mojave NVMe, I was thinking of getting a faster NVMe like the 2TB 980 Pro (I know my 5,1's x4 PCIe 2.0 of Slot 4 is bottleneck for this NVMe. I am just trying to future proof it, especially because the PCIe 3.0 NVMe's are not that much cheaper) and use this 970 Evo for the PS5 once the expansion slot is enabled on PS5. For the time being I am trying 11.2.3 on this NVMe and see how stable it is. I am obviously concerned about not being able to even get the security updates for Big Sur from now on, but I can't stop having this grin on my face seeing how flawlessly this 5,1 is running with 24TB of NVMe RAID, 48TB on HighPoint RAID enclosure. Granted it was doing the same without a problem on Mojave too but now I can even unlock and fill passwords with my Apple Watch to this 12 year old Mac.

 

[sfalatko]

I have the OC in EFI partition of a USB Flash. The HDD with Mojave is intact. Held down the power button and rebooted back into Big Sur. Right now I switched to Mojave and back to Big Sur, keyboard and mouse were not working, even though they were working at the bootpicker screen. Held down power button again and rebooted to Big Sur without a problem. It looks like it is just being a bit finicky, other than that it is working well.

Isn't it better to keep the OC on the EFI of a USB drive, so that I can remove it when I encounter problems so I can boot back into Mojave by resetting NVRAM? I guess the Big Sur on the NVMe SSD would be useless without OC, so I might as well keep OC on the EFI of the NVMe?

Keeping it on USB Flash is perfectly fine - that's the way I use OC. I missed you saying that earlier in the thread. I generally boot Catalina without OC but with no_compat_check. I only use OC for updates to Catalina or to boot Big Sur and have full continuity. I haven't used Big Sur for a while as I am waiting to see if the community can sort out the boot issues.

I assume your keyboard and mouse are USB? Several people reported issues with USB in Big Sur. Search this thread - it seems that the issues got better in 11.2.3 but some still needed to use a USB hub which solved their USB issues.

As for future proofing and further investments I would wait to see if Big Sur can be sorted out. Otherwise we have another year+ of security updates to Catalina but after that may need to get a new/different mac....

 

[manielli]

Keeping it on USB Flash is perfectly fine - that's the way I use OC. I missed you saying that earlier in the thread. I generally boot Catalina without OC but with no_compat_check. I only use OC for updates to Catalina or to boot Big Sur and have full continuity. I haven't used Big Sur for a while as I am waiting to see if the community can sort out the boot issues.

I assume your keyboard and mouse are USB? Several people reported issues with USB in Big Sur. Search this thread - it seems that the issues got better in 11.2.3 but some still needed to use a USB hub which solved their USB issues.

As for future proofing and further investments I would wait to see if Big Sur can be sorted out. Otherwise we have another year+ of security updates to Catalina but after that may need to get a new/different mac....

I am using Magic Mouse and Magic Keyboard without a problem. That sleep issue hasn't happened again. When I booted back into Big Sur and the Mouse and Keyboard were not working I plugged the Magic Keyboard with USB and still didn't let me login to Big Sur, so I had to reboot. I am having Flash Drive with OC EFI on one of the front USB ports and haven't any issues. I am also using Sonnet PCIe USB 3.2 Gen 1 card for my other devices. My other devices that are connected to that card are also fine so far. I just ordered Sonnet USB 3.2 Gen 2 last week too to take almost full advantage of the PCIe in slot x4 and get better read write speeds with the two HighPoint RAID enclosures.

 

[manielli]

Spoke too soon, just did a few disk speed tests on my devices connected to SonnetTech PCIe USB 3 card and everything seems to be running at USB 2 speeds.

Actually some devices are running at USB 3, some are USB 2 levels (such as the HighPoint RAID enclosure), I need to investigate this further. Will let you know.

 

[manielli]

I stand corrected I am getting USB 3.0 speeds on the SonnetTech PCIe USB ports too.

 

[Chrisl33]

Finally got a chance to try and install Catalina again but no luck, don't know what I am doing wrong. Tried updating OC, blessed the drive again, made the changes in the .plist, even removed the Apple folder from the EFI as was suggested. It goes through the install but then still restarts in Mojave. Very frustrating.

 

[tsialex]

Finally got a chance to try and install Catalina again but no luck, don't know what I am doing wrong. Tried updating OC, blessed the drive again, made the changes in the .plist, even removed the Apple folder from the EFI as was suggested. It goes through the install but then still restarts in Mojave. Very frustrating.

Not being capable of changing the default boot drive/bless is on of the first signs of BootROM/NVRAM corruption. Start your diagnose by checking your VSS store space.

OpenCore on the Mac Pro

Thank you @tsialex as always! Your knowledge overwhelms me! I have fixed my problem just reflashing BootROM using the reconstructed one that you made it for me. Now everything is ok again

forums.macrumors.com

 

[Chrisl33]

Not being capable of changing the default boot drive/bless is on of the first signs of BootROM/NVRAM corruption. Start your diagnose by checking your VSS store space.

OpenCore on the Mac Pro

Thank you @tsialex as always! Your knowledge overwhelms me! I have fixed my problem just reflashing BootROM using the reconstructed one that you made it for me. Now everything is ok again

forums.macrumors.com

Alex, thank you for your quick reply, I am not very confident with this ROMtool bit and when I went to dump the rom I got the attached message. (I have a 2010 5.1 dual 3.46.)

 

[tsialex]

Alex, thank you for your quick reply, I am not very confident with this ROMtool bit and when I went to dump the rom I got the attached message. (I have a 2010 5.1 dual 3.46.)View attachment 1802192

You have to check the model of the U8700 CI on the backplane, right next the two mini-PCIe power connectors. I'm gonna send you a PM with detailed instructions on how to dump correctly and how to gather everything needed for a diagnostic, check your PMs.

 

[JMVB]

Finally got a chance to try and install Catalina again but no luck, don't know what I am doing wrong. Tried updating OC, blessed the drive again, made the changes in the .plist, even removed the Apple folder from the EFI as was suggested. It goes through the install but then still restarts in Mojave. Very frustrating.

 

[cdf]

^ Ugh. Just a reminder: The first post of this thread already details the entire process. Not only is the first post the original resource for installing OpenCore on legacy Apple hardware, it is also a wiki, so if something is unclear, it is easily updated. In fact, it receives frequent updates. Look for one today.

 

[0134168]

I followed that same guide. Works like a charm. I didn´t update the OC since then, as it works prefect.

 

[cdf]

The guide has been updated to OpenCore version 0.7.1.

This update simply requires two changes to the sample configuration file (see Part 3 of the guide). Also note that the functionality of NightShiftEnabler has been incorporated into the Acidanthera-maintained SidecarFixup.

 

[mode11]

@cdf I'm in the process of updating from OC 0.5.9 to 0.7.1. In the guide on page 1, it seems to say you should open your existing config.plist and make changes as necessary. It seems safer to open the fresh sample config.plist that's been set up for the specific new version of OC, and make changes to that instead? Or am I missing something?

Basically, to then go through all the changes in part II to enable HW acceleration, Night Shift etc.

Also, the guide does each of the changes individually, presumably as some people won't want e.g. HW acceleration. Is it safe to make all the changes at once, assuming you validate the config.plist before overwriting the one in EFI? Saves a bunch of mounting and rebooting.

 

[cdf]

@cdf I'm in the process of updating from OC 0.5.9 to 0.7.1. In the guide on page 1, it seems to say you should open your existing config.plist and make changes as necessary. It seems safer to open the fresh sample config.plist that's been set up for the specific new version of OC, and make changes to that instead? Or am I missing something?

Basically, to then go through all the changes in part II to enable HW acceleration, Night Shift etc.

That's right. In your case, you should start from the new sample and reapply the advanced configuration. The update procedure in the guide really only applies to updating from the previous version, i.e., going from 0.7.0 to 0.7.1.

Also, the guide does each of the changes individually, presumably as some people won't want e.g. HW acceleration. Is it safe to make all the changes at once, assuming you validate the config.plist before overwriting the one in EFI? Saves a bunch of mounting and rebooting.

Yes. You can certainly make all the changes at once, but it might be a good idea to still verify your config with plutil after each change to narrow down any issues. Moving the file back to the EFI volume and rebooting can be done just once, after you've made all the changes.

 

[TECK]

The guide has been updated to OpenCore version 0.7.1.

Plistlib Generator 1.1.3 was released with support for OC 0.7.1 (see notable changes), you will need to perform several minor changes to your current setup.py file, prior executing the usual upgrade process.