How did you get it to work?
I too im getting the error for missing apfs.efi when I try to bless the volume.
UPDATE: Nevermind I figured it out. Was not loading the correct partition...
Last edited:
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
How did you get it to work?
I too im getting the error for missing apfs.efi when I try to bless the volume.
UPDATE: Nevermind I figured it out. Was not loading the correct partition...
Just because you asked nicely 😋
Make sure to compile OC from latest master branch and populate ApECID if you want to enable Apple Secure Boot fully. Be aware, if you populate ApECID and wish to continue using your current Big Sur installation, the OS will fail to boot then reboot into recovery on its own as you will need to personalize your installation with the cMP connected to the internet. Once in recovery, open terminal and execute:
Code:
bless bless --folder "/Volumes/REPLACE_WITH_YOUR_VOLUME_NAME/System/Library/CoreServices" \
--bootefi --personalize --verboseYou don't need to personalize a clean installation with Apple Secure Boot fully enabled.
@cdf, @h9826790 uses a nice generic patch in his OC config to make NVMe drives appear internal .. Perhaps you can add that to your config as well?
Code:
<array>
<dict>
<key>Arch</key>
<string>Any</string>
<key>Base</key>
<string></string>
<key>Comment</key>
<string>IONVMeFamily Patch#External</string>
<key>Count</key>
<integer>0</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>RXh0ZXJuYWw=</data>
<key>Identifier</key>
<string>com.apple.iokit.IONVMeFamily</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data></data>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>17.0.0</string>
<key>Replace</key>
<data>SW50ZXJuYWw=</data>
<key>ReplaceMask</key>
<data></data>
<key>Skip</key>
<integer>0</integer>
</dict>
</array>Cheers
Hey everybody! I'm new here posting but reading for years now and Open Core made me sign up 
So first of all a big THANK YOU to all you guys providing awesome support for our old cMP rigs. It really means a lot being able to still run the latest OS.
That being said, I managed, thanks to the awesome guide on page 1, to setup my MacPro and have Big Sur running on my NVMe drive like a charm. Everything I need works perfect for me. The guide on page 1 was really top notch!
Right now, I do have one cosmetic "fix" I'm looking for that I can't seem to find myself, so asking for help here on this one:
I have a dual monitor setup. My main screen is connected to an RX580 via DVI and my aux screen is connected to the very same card via DisplayPort. The boot picker now shows on the aux screen BUT since I have my aux screen rotated to portrait mode rather than landscape, my boot picker is always rotated by 90° as well which isn't really much of a functional issue but is a bit hard to look at
So my question here is, is there any way to tell OpenCore to display the boot picker not on that particular aux screen via DisplayPort but rather take my main screen on the DVI port? That would be so awesome if someone is able to help me with that one.
Thanks a lot guys!
So first of all a big THANK YOU to all you guys providing awesome support for our old cMP rigs. It really means a lot being able to still run the latest OS.
That being said, I managed, thanks to the awesome guide on page 1, to setup my MacPro and have Big Sur running on my NVMe drive like a charm. Everything I need works perfect for me. The guide on page 1 was really top notch!
Right now, I do have one cosmetic "fix" I'm looking for that I can't seem to find myself, so asking for help here on this one:
I have a dual monitor setup. My main screen is connected to an RX580 via DVI and my aux screen is connected to the very same card via DisplayPort. The boot picker now shows on the aux screen BUT since I have my aux screen rotated to portrait mode rather than landscape, my boot picker is always rotated by 90° as well which isn't really much of a functional issue but is a bit hard to look at
So my question here is, is there any way to tell OpenCore to display the boot picker not on that particular aux screen via DisplayPort but rather take my main screen on the DVI port? That would be so awesome if someone is able to help me with that one.
Thanks a lot guys!
Yup, I made sure. I use OCBuilder to compile OC and most kexts. For kexts that aren't compiled through OCBuilder, I download the latest from github.
I'll have a look at it again this weekend to see what is keeping it from sleeping.
Hello,
Im having problems booting from a NVME (1TB) drive with OC. After I reboot from blessing all I see is a blank screen.
I tried it from an SSD (120gb) drive and it worked.
My question is the following:
Can I install OC and Catalina/Big Sur in the SSD and once I have it all working use carbon copy to copy everything to the NVME drive? What happens to the partition size if I do?
Thanks.
Im having problems booting from a NVME (1TB) drive with OC. After I reboot from blessing all I see is a blank screen.
I tried it from an SSD (120gb) drive and it worked.
My question is the following:
Can I install OC and Catalina/Big Sur in the SSD and once I have it all working use carbon copy to copy everything to the NVME drive? What happens to the partition size if I do?
Thanks.
If ResXtreme doesn't work, then your only hope almost down to SwitchResX.
But I am sure OC 0.6.3 + Big Sur can run 144Hz monitor. This is what I am using right now. Therefore, most likely nothing need to be fixed in the OpenCore cofig.
Just keep OC on your SSD, no point to move that if it works.
And you can install macOS to whichever driver you want (including the NVMe).
Thank you Martin, I end up using HDMI cable and I can choose the 100, 120 and 144 now.
related side tangent.. putting OC on the NVME is much slower than on another PCIe ssd or std sata ssd or std sata drive for me. In my testing OC fires up about 6 seconds after the chime on my PCI ssd vs between 30 sec to 1 min when the efi is on the nvme. So I'd recommend not using efi on the nvme if you want fast boots.
Hello
My Mac Pro 5,1 with Radeon RX580 flashed and Big Sur and SMBIOS Mac Pro 7.1
<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-27AD2F918AE68F61</string>
<key>FirmwareFeatures</key>
<data>
A1QM4A==
</data>
<key>FirmwareFeaturesMask</key>
<data>
P/8f/w==
</data>
<key>SystemProductName</key>
<string>MacPro7,1</string>
</dict>
I don't think need Lilu, WhateverGreen and graphic card PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) but, AppleMCEReporterDisabler.kext I needed?
In NVRAM I delete
<key>boot-args</key>
<string>-no_compat_check</string>
and
<string>boot-args</string>
or not?
My Mac Pro 5,1 with Radeon RX580 flashed and Big Sur and SMBIOS Mac Pro 7.1
<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-27AD2F918AE68F61</string>
<key>FirmwareFeatures</key>
<data>
A1QM4A==
</data>
<key>FirmwareFeaturesMask</key>
<data>
P/8f/w==
</data>
<key>SystemProductName</key>
<string>MacPro7,1</string>
</dict>
I don't think need Lilu, WhateverGreen and graphic card PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) but, AppleMCEReporterDisabler.kext I needed?
In NVRAM I delete
<key>boot-args</key>
<string>-no_compat_check</string>
and
<string>boot-args</string>
or not?
Last edited:
Its a borrowed SSD.
I finally got it to work. I don't know why but if I placed the NVME card in PCI2 it would not work. Moved it to PCI3 and now shows the boot menu.
Chrome works fine, I've just primarily switched to because of much lower CPU utilization. The machine still would lock up after a while, even without running Edge - but if you started Edge it will ALWAYS lock up. FWIW I found a number of GPUReset notifications in the system log right as the system would crash - so I'm assuming it's something in regards to the GPU I'm using - because my machines at work with RX 550 GPUs don't have this problem.
There is a PCIe switch build in for slot 3 and 4, may be that make the difference.
If you have time, and don't mind to help the others, may be you can try all slot 1,2,3,4, and see if only slot 3 & 4 can work as expected
Your cMP still with the Nano?
If yes, then most likely because macOS try to active the video engine that doesn't supported.
Remove the board ID in the SMBIOS section should able to fix this issue.
By the way, I put my nvmes right above the video card... (I think that's slot 2) with PCI SSD above that and USB 3 card in the top slot under the SATA Drives. (two different 5,1s). one has GTX 680 and the other a RX 580.
Sure some users can get that work in slot 2 (or slot 1).
But I wonder if in some cases, only slot 3 and 4 can works (e.g. depends on the adaptor, or the NVMe itself). If yes, then at least we know what we can suggest the others to try (when he can't boot OC from NVMe).
That is where I have my dual 970 EVO Plus NVMe disks (slot 2), mounted on a Syba SI-PEX40129. Syba requires a PCIe 3.0 x16 slot.
Thank you, I compared the two config .plist files and amended mine accordingly.
Hey presto WiFi
Attachments
Is this to avoid manually defining the external disk paths? This is how I hide mines in DeviceProperties:
Code:
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>
AA==
</data>
</dict>
Last edited:
I believe something might be wrong with your BootROM, could be corrupted? It takes few seconds from chime to Big Sur screen, excluding the 5 seconds delay you get from OpenCanopy selector. My EFI is on a 970 EVO Plus.
To clarify.. I get chime. then appx 6 seconds later, the open canopy boot screen/disk selector. (the appx 6 seconds varies based on #/types of drives installed)