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
Your
ExposeSensitiveData needs proper setting and your NVRAM begs for a triple chime cleanup.Hi, my Samsung SSD 960 EVO PCI NVMe boot drive on my OpenCore Mac Pro 5.1 is failing. Can I replace it with any newer NVMe (for example 990 Pro 2 TB) or do I have to watch out for something? Are all NVMe's compatible with the OpenCore Mac Pro 5.1 setup? Thank you.
No, several blades are incompatible with a Mac, even more with a MacPro5,1. If you don’t want to heave headaches, see the PCIe SSDs NVMe + AHCI stickie thread for the tested models.
PCIe SSDs - NVMe & AHCI
This is a general info thread for blade SSDs that can be used in the Mac Pro. This is a WikiPost so anyone with the proper credentials may edit it. NVMe SSDs can be used as a boot drive in the MP5,1 and MP6,1 with the latest firmware installed (beginning with version 140.0.0.0.0 for MP5,1 and...
forums.macrumors.com
The best compatibility for a Samsung model available today is the 970EVO+. 990 Pro is one of the Samsung blades that require firmware updates and a PCIe switched adapter, I’d stick to the 970 EVO+ or any other tested blade.
Great, thank you so much for the detailed information.No, several blades are incompatible with a Mac, even more with a MacPro5,1. If you don’t want to heave headaches, see the PCIe SSDs NVMe + AHCI stickie thread for the tested models.
PCIe SSDs - NVMe & AHCI
This is a general info thread for blade SSDs that can be used in the Mac Pro. This is a WikiPost so anyone with the proper credentials may edit it. NVMe SSDs can be used as a boot drive in the MP5,1 and MP6,1 with the latest firmware installed (beginning with version 140.0.0.0.0 for MP5,1 and...
The best compatibility for a Samsung model available today is the 970EVO+. 990 Pro is one of the Samsung blades that require firmware updates and a PCIe switched adapter, I’d stick to the 970 EVO+ or any other tested blade.
👍Just saw that there is also a chapter about PCIe adaptors. One is marked as being able to boot into Windows.
I have a Angelbirds Wings PX1. But in this category nothing is mentioned about the boot compatibility. Is it known if it is possible or not to boot into Windows with the Angelbirds Wings PX1? Or is it only possible with the HighPoint SSD7101A-1?
Thank you.
Last edited:
0.9.4 is here
I will check what's new
checked the manual about the updated version
seems to work with the old config
added three new kexts lilu, whatever and appleALC
it's been working fine for a while
edited
after checking cdf manual
added two lines
I will check what's new
checked the manual about the updated version
seems to work with the old config
added three new kexts lilu, whatever and appleALC
it's been working fine for a while
edited
after checking cdf manual
added two lines
Last edited:
Great, thank you so much for the detailed information.
Just saw that there is also a chapter about PCIe adaptors. One is marked as being able to boot into Windows.
I have a Angelbirds Wings PX1. But in this category nothing is mentioned about the boot compatibility. Is it known if it is possible or not to boot into Windows with the Angelbirds Wings PX1? Or is it only possible with the HighPoint SSD7101A-1?
Thank you.
It's completely possible to boot Windows from a NVMe blade, but only Windows UEFI installed supports booting from NVMe. This will require OC ProtectSecureBoot enabled to block Windows UEFI SecureBoot signing your BootROM and trashing the NVRAM with certificates/PKs/etc - you can brick your Mac Pro over time with the SecureBoot mess.
Any boot coups from Windows Updates will also trash your MacPro BootROM, so, to completely avoid that, I'd go with BootCamp/CSM/legacy Windows with a SATA SSD and boot it from the native Apple BootPicker via EnableGOP, since OC do not support legacy Windows installs.
FYI Goldfish64 is working on changing this: https://github.com/acidanthera/OpenCorePkg/pull/482
Thank you for the explanations. I have a Windows UEFI on a hard disk with OC ProtectSecureBoot enabled. But I didn't understand the risks. Thank you so much for the enlightenment and the alternatives approach.
Since Windows Updates boot coups can bypass OC, be sure to check if your BootROM wasn't signed by SecureBoot and flash back your BootROM backup image if it happened. Better be sure than sorry.
Good idea. Thanks. Do you have instructions posted somebody where I can follow along? I never did this before. I made a BootROM backup before I started with OC.
There are several ways to check it, like binwalk/UEFITool (see the first post of BootROM thread for that) or if you are not comfortable with the command line/UEFITool you can run Macschrauber dumper.
I'll send you a PM.
The guide has been updated to OpenCore version 0.9.4.
The sign of OCLP are from my original setup with 0.7.6 a while ago. But last weekend I have not used OCLP to update OpenCore.
Yes I can confirm only one EFI folder.
Thanks for your advice will do this next time I boot my cMP
but if you use OC, you need change config too- this config from old OCLP and your opencore not work properlyThe sign of OCLP are from my original setup with 0.7.6 a while ago. But last weekend I have not used OCLP to update OpenCore.
Yes I can confirm only one EFI folder.
Thanks for your advice will do this next time I boot my cMP
For years I always had some Bluetooth interference (erratic/hanging/lagging behavior of my Magic Mouse) from my USB 3 PCI Card on my Mac Pro 5.1 depending on what is connected. I finally found a solution. This is a digression from OpenCore, but maybe some of you find this information helpful anyway.
The solution is to put a ferrite bead on the end of the USB cable. This solved my problems almost 100 %.
I found 5mm ferrite beads in a nearby shop for a good price. 5mm fitted perfectly on my extension cables. I put one on the end of the cable which connect to a small 10Gb/s USB-Hub I have on the desktop. From my second and last output on my PCI Card I put one ferrite bead on the end of the cable connected to an external HDD Enclosure I use now and then.
I also have a Logitech web cam which have been the worse for interference, so to make sure I put a 5mm bead close to the cam as well to test, I have the cam connected to the hub.
I can feel a little 'pull' in the mouse a few times if I have a lot connected the same time and my machine is writing to disk etc., but I would say this completely solved my Magic Mose Bluetooth problems.
Had some Magic Mose problems before too which was not related to USB/Bluetooth, but a PRAM reset fixed those problems.
The solution is to put a ferrite bead on the end of the USB cable. This solved my problems almost 100 %.
I found 5mm ferrite beads in a nearby shop for a good price. 5mm fitted perfectly on my extension cables. I put one on the end of the cable which connect to a small 10Gb/s USB-Hub I have on the desktop. From my second and last output on my PCI Card I put one ferrite bead on the end of the cable connected to an external HDD Enclosure I use now and then.
I also have a Logitech web cam which have been the worse for interference, so to make sure I put a 5mm bead close to the cam as well to test, I have the cam connected to the hub.
I can feel a little 'pull' in the mouse a few times if I have a lot connected the same time and my machine is writing to disk etc., but I would say this completely solved my Magic Mose Bluetooth problems.
Had some Magic Mose problems before too which was not related to USB/Bluetooth, but a PRAM reset fixed those problems.
I have a 2010 Mac Pro 5,1 with a Radeon RX 580 8 GB graphics card. I have been using Martin's opencore for 3 years, upgrading to Mojave and then to Catalina back when I started.
I just added a drive and anticipated updating to Monterey and ran into a bit of a snag. Reading the various posts on this forum has given me some ideas, but no fix.
I got the "a required firmware update could not be installed" error upon trying to instal Monterey onto a new drive. I am able to install Big Sur, but not Monterey.
I am using opencore 0.9.3 and I did alter the config.plist by a change the cpuid1mask (the A to C), and UpdateSMBIOS to false.
I have searched the forums and found - You need to "update" the firmware features in PlatformNVRAM (see Complete your setup>Spoofing and enabling missing features in post #1) - so I looked at post #1, spoofing and enabling missing features, and then under - For a better experience when installing and updating Monterey, you'll also need to "update" the firmware features: - , but I couldn't understand what lines needed to be changed and what the lines need to be changed to.
Some of the choices were:
I wasn't sure if I am supposed to find the line that show in the replace section and make it look like the find section or the other way around.
My apologies for the long post. I would really like to find a way to get to Monterey on my mac, seeing how this may be my last upgrade
Thank you for any assistance.
I just added a drive and anticipated updating to Monterey and ran into a bit of a snag. Reading the various posts on this forum has given me some ideas, but no fix.
I got the "a required firmware update could not be installed" error upon trying to instal Monterey onto a new drive. I am able to install Big Sur, but not Monterey.
I am using opencore 0.9.3 and I did alter the config.plist by a change the cpuid1mask (the A to C), and UpdateSMBIOS to false.
I have searched the forums and found - You need to "update" the firmware features in PlatformNVRAM (see Complete your setup>Spoofing and enabling missing features in post #1) - so I looked at post #1, spoofing and enabling missing features, and then under - For a better experience when installing and updating Monterey, you'll also need to "update" the firmware features: - , but I couldn't understand what lines needed to be changed and what the lines need to be changed to.
Some of the choices were:
| Find ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ | Replace ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ |
|---|---|
| <key>PlatformInfo</key> <dict> ⋮ <key>PlatformNVRAM</key> <dict> ⋮ <key>FirmwareFeatures</key> <data> </data> <key>FirmwareFeaturesMask</key> <data> </data> ⋮ <dict/> ⋮ <key>UpdateNVRAM</key> <false/> ⠀ ⠀ | <key>PlatformInfo</key> <dict> ⋮ <key>PlatformNVRAM</key> <dict> ⋮ <key>FirmwareFeatures</key> <data> A1QMwAgAAAA= </data> <key>FirmwareFeaturesMask</key> <data> P/8f/wgAAAA= </data> ⋮ <dict/> ⋮ <key>UpdateNVRAM</key> <true/> |
I wasn't sure if I am supposed to find the line that show in the replace section and make it look like the find section or the other way around.
My apologies for the long post. I would really like to find a way to get to Monterey on my mac, seeing how this may be my last upgrade
Thank you for any assistance.
there are two strategies
Martin's=cdf1 and cdf2
these are two different strategies and should not be combined (at least that's what I understand from my experience)
in order to follow strategy 2 you must use the config.plist configured step by step according to the method from post#1, in addition, in order to successfully use this strategy, you must reconstruct bootrom using the tsialex method - as I understand it (maybe devs will correct me) it just produces Firmware update
as for asking you to find matching lines - just use the edit->find in text editor menu
Martin's=cdf1 and cdf2
these are two different strategies and should not be combined (at least that's what I understand from my experience)
in order to follow strategy 2 you must use the config.plist configured step by step according to the method from post#1, in addition, in order to successfully use this strategy, you must reconstruct bootrom using the tsialex method - as I understand it (maybe devs will correct me) it just produces Firmware update
as for asking you to find matching lines - just use the edit->find in text editor menu
@Gustav Holdoff - first you don't HAVE TO have a reconstructed bootrom but that is a very good idea. What most are recommending is to do a deep NVRAM reset prior to upgrading macOS (even point releases) since recent updates store a lot of info in NVRAM so if it is in need of garbage collection the update can push it over the edge.
For upgrading to Monterey you are correct - pick one method.
@Q3nxNHsMi - I would say you are close. I have had success with method "2" where you need spoofing and firmware features. From the example you show in your post you are supposed to take the "base" config.plist shown on the left and add the lines shown on the right. If you choose this method then you do not set the VMM flag.
Post your config.plist and you will get pointers on how to fix it.
Regards,
sfalatko
Thank you sfalatko and Gustav Holdoff
I think another thing that I am doing incorrectly is that I have installed opencore on each of the drives that I have connected to my mac pro, for each of the operating systems I have tried. I have a drive for each, Big Sur, Catalina, and Mojave. I also think that each of these has a different version of opencore.
Was the MP 5,1's last official operating system High Sierra, or was it Mojave with the change of the graphics card?
From what I see from that method #2, I would have to boot back to Mojave and re-install opencore to get access to the other operating systems? Then try to install Monterey? I have attached the config file that is in my Big Sur set up.
Thank you very much for your kind assistance.
@Q3nxNHsMi
No, OC resides on a single drive and the rest of the drives do not have OC EFI, you leave them intact. Does not matter which drive you put OC on, it does matter than you set up this drive as a boot drive.
From there you have two options: either you craft a config.plist that will cater for different settings for different OSes or you boot all the OSes that do not need OC with native boot picker and the rest with OC (previous option still standing if you have/need to run more than one OS that is not supported).
Last official OS for 5,1 was Mojave + Metal GPU upgrade.
From there you have two options: either you craft a config.plist that will cater for different settings for different OSes or you boot all the OSes that do not need OC with native boot picker and the rest with OC (previous option still standing if you have/need to run more than one OS that is not supported).
Last official OS for 5,1 was Mojave + Metal GPU upgrade.
Thank you, I had a thought when I watched some videos and heard mention of "the drive where have your efi-opencore installed," that I may have misunderstood that it goes on all boot drives.
Now, I doubt it is just a matter of removing it from all the drives except for the one, but hopefully?
Thank you for your assistance.
@Q3nxNHsMi
Since there are a lot of efi with opencore, and it’s not clear which one is blessed, in order to avoid inconvenience and surprises,
I would first decide on which disk I will leave opencore (preferably on sata -not nvme), then boot into recovery,
found using terminal command "diskutil list" this disk, mount EFI partition and bless (see the bless opencore section in post#1)
then, booting into any running macos, I opened efi on each disk one by one, using the clover configurator (it is attached as an additional program to opencore in Martin Lo's version) and deleted opencore on all no needed disks
I would first decide on which disk I will leave opencore (preferably on sata -not nvme), then boot into recovery,
found using terminal command "diskutil list" this disk, mount EFI partition and bless (see the bless opencore section in post#1)
then, booting into any running macos, I opened efi on each disk one by one, using the clover configurator (it is attached as an additional program to opencore in Martin Lo's version) and deleted opencore on all no needed disks