According to your screenshot, you're missing a space after --mount, and later after --file.
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
According to your screenshot, you're missing a space after --mount, and later after --file.
The issue with FeatureUnlock has been addressed with a more targeted patching approach:
github.com
So expect it to return to the guide for the next release. That means not only Night Shift but also AirPlay support.
Refactor FeatureUnlock · acidanthera/FeatureUnlock@4161389
Add Sidecar support to unsupported models. Contribute to acidanthera/FeatureUnlock development by creating an account on GitHub.
github.com
So expect it to return to the guide for the next release. That means not only Night Shift but also AirPlay support.
Great news.The issue with FeatureUnlock has been addressed with a more targeted patching approach:
Refactor FeatureUnlock · acidanthera/FeatureUnlock@4161389
Add Sidecar support to unsupported models. Contribute to acidanthera/FeatureUnlock development by creating an account on GitHub.
So expect it to return to the guide for the next release. That means not only Night Shift but also AirPlay support.
Was SecureBootModel also set to Default? This is also required.
@cdf - I have it set to DISABLED so that I can boot Catalina as well. It did install with it set to DISABLED and am currently booting Monterey with it set to DISABLED. In post #1 I didnt' read it to mean that it had to be set to DEFAULT to install and run Monterey. Did I miss read that?
What I am doing at present is booting Mojave natively when needed, booting Catalina when I need to run VMWARE, and generally now booting Monterey (until today it had been Big Sur) for general day-to-day use. I still have a Legacy WIndows install that I use either with VMWARE or rarely booting directly. Everything is more complicated now that I am using a Radeon RX560 without a native Apple bootscreen.
I am still working through how everything is going to settle out - which version of macOS on which drive and where I put OpenCore. At this moment I am using a RescueCD to boot Catalina and Monterey.
Last edited:
The macOS section of post #1 provides two recommendations for installing and updating macOS:
- Clean install with full installer in Mojave and later or OTA update in Big Sur and later
- SecureBootModel is set to Disabled
- VMM flag is enabled
- Clean install with full installer in Big Sur and later or OTA update in Big Sur and later
- SecureBootModel is set to Default
- Hybridization is used
- Firmware features are updated
Yes. But if you plan to disable SecureBootModel (or not update the firmware features) after installing or updating macOS, then you should probably stick with the VMM approach. The point of the second recommendation above (besides the added security) is to avoid modifying settings whenever installing or updating.
@cdf - thanks. That clears it up for me and I see that I missed that in post #1. I initially mixed the two methods with fully implementing either.
My setup is complicated by wanting to keep using Catalina for VMware. I don't need OpenCore to boot Catalina only to upgrade and for that I need VMM.
For Big Sur and Monterey method #2 looks better. For now I think I will make a RescueCD with method #2 which will allow me to boot and keep Monterey up to date. I will create a RescueCD with Method #1 for the infrequent times when Catalina needs to be updated.
One question I would have is can Catalina be booted with SecureBootModel set to Default?
As always I really appreciate your help.
Regards,
sfalatko
Last edited:
By sticking with the VMM approach I assume you are saying that I can basically do what I have been doing for Catalina, which is use VMM to run updates, and run without VMM normally...and then Monterrey will boot fine with SecureBootModel disabled... But I should probably install it with SecureBootModel=default..
That will suit me fine. I have been used to using VMM to update Catalina anyway, and for the next 6 months or so I will continue primarily running Catalina, I still have a few key pieces of software that have not been updated to run on Monterey and will be some time before they are. But I there are a few things I will occasionally boot up Monterey for...
So anyway this approach will help me make sure that I don't boot either Monterey or Catalina with the wrong OC configuration (if I were trying to use SecureBootModel=default.
I didn't understand your comment about "or not update the firmware features"
Yes. Together with MacPro7,1 spoofing, SecureBootModel should allow for booting macOS 10.15.1 and later.
I was referring to the second recommendation in post #9,674, which involves not only SecureBootModel but also firmware features.
This should probably be clarified. Big Sur is correct before spoofing (x86legacy), and Catalina is correct after spoofing the MacPro7,1 board ID.
yes I Know that is the comment I don't understand in the post you just quoted.
Its not entirely clear to me what the FirmwareFeatures (and the mask) value enables or disables... and why I would want to enable or disable that.. in conjunction with the above conversation about using SecureBootModel to install Monterey and then turn that off and use VMM for updates after that.
FirmwareFeatures expose the capabilities of a Mac, such as APFS and large base system support, both of which are required for Monterey. Because the MacPro5,1 lacks the FirmwareFeatures bit for large base system support, we need to add it before we can install Monterey. But there is an exception: the installer will skip checking for the bit if the VMM flag is enabled.
In Monterey, SecureBootModel is required for Software update on T2 models. This requirement applies to us because we spoof a T2 model (MacPro7,1). But once again, there is an exception: the VMM flag.
Therefore, you can either use SecureBootModel and FirmwareFeatures for the full supported-Mac experience, or just stick with the VMM flag, which is perhaps a more robust solution for you.
Attempting the 0.7.5 upgrade now...since the Guide has been totally rewritten I had to go through line by line to figure out what is being done differently now compared to earlier... Some questions...
I notice that BIOSVersion is no longer being set to 999.0.0.0.0. Is this no longer needed or wanted in hybridization mode?
I notice the actual SPOOF'd ID has been changed also, it used to be iMac I think, now is it 7,1? Is there any problem using that with Catalina still?
I notice it is reverted back to NightShiftEnabler instead of the FeatureUnlock (but I also saw your comments on the forum that in 0.7.6 this may go back to FeatureUnlock. Just verifying this...
For Monterey, you added the optional FirmwareFeatures and UpdateNVRAM... (I am going to use that only to upgrade Monterrey and then after that I will revert back to without it and use VMM for updating Monterrey. This is for reasons of compatilibity with Catalina. Do I understand correctly that is a valid working mode?)
You didn't mention SecureBootModel in that section about Monterey, but I see that earlier in the guide for optional settings for BigSur+, so that will also be used by me only temporarily to upgrade/install Monterey, after that I will set it back to Disabled in order to be compatible also with Catalina.
Thanks in advance for clarifications...
I notice that BIOSVersion is no longer being set to 999.0.0.0.0. Is this no longer needed or wanted in hybridization mode?
I notice the actual SPOOF'd ID has been changed also, it used to be iMac I think, now is it 7,1? Is there any problem using that with Catalina still?
I notice it is reverted back to NightShiftEnabler instead of the FeatureUnlock (but I also saw your comments on the forum that in 0.7.6 this may go back to FeatureUnlock. Just verifying this...
For Monterey, you added the optional FirmwareFeatures and UpdateNVRAM... (I am going to use that only to upgrade Monterrey and then after that I will revert back to without it and use VMM for updating Monterrey. This is for reasons of compatilibity with Catalina. Do I understand correctly that is a valid working mode?)
You didn't mention SecureBootModel in that section about Monterey, but I see that earlier in the guide for optional settings for BigSur+, so that will also be used by me only temporarily to upgrade/install Monterey, after that I will set it back to Disabled in order to be compatible also with Catalina.
Thanks in advance for clarifications...
Got it. I'll use it to install, but Monterey will run perfectly fine without it after install and without VMM, right?
Man, I'm sorry I'm so dense, but I'm still confused about what I will be missing in Monterey if I turn those features off and use VMM for updating. Once I leave Catalina behind entirely...then I will definitely go with the newer approach, its only because I need to try to create an OC config that will work for both Catalina and Monterey.
This is what I'm about to try:
- CCC clone my Catalina volume to a new drive (will be upgraded to Monterey)
- Boot to the cloned Catalina Volume, using VMM
- Update the OC configuration according to 0.7.5 guide. This includes also the various needed things for installing Monterrey: FirmwareFeatures, SecureBootModel, UpdateNVRAM
- Run the Apple System Update to update to Monterey. It will get to a point and reboot
- When it reboots, do NOT use VMM, I will be now using the new OC configuration with the stuff mentioned above in point#3 (and without VMM)
- Finish the Monterey upgrade, several reboots will happen. Get it done.
- Go back and change the OC configuration to remove the three changes mentioned in step#3 above, reverting back to the default config.plist settings from CDF guide.
- Use that OC configuration to boot either in Catalina or to Monterey.
- When I need to update either Catalina or Monterey I will set VMM with everything else the same and run system update.
- When I finally turn my back on Catalina once and for all, I will get rid of the VMM approach and change the OC config back to using the items mentioned in point#3 above.
Last edited:
Good question. With BlacklistAppleUpdate, OpenCore already prevents unwanted firmware updates by blocking MultiUpdater.efi, so spoofing the BIOSVersion is really a superfluous practice, the effectiveness of which is questionable: Since getting a Matt card, I've tested many installs and updates without spoofing the BIOSVersion, and I've notice that spoofing the BIOSVersion does not prevent the staging of firmware updates (MultiUpdater.efi and related files will appear on the ESP nevertheless).
More problematic is the data that gets written to the NVRAM during macOS installations. That's why it's important to maintain the health of the firmware chip by periodically reflashing a clean BootROM.
No problem for Catalina. But for Mojave make sure to keep -no_compat_check and disable SecureBootModel.
Correct. There was an issue with FeatureUnlock. Hopefully it's fixed now.
That should work. But you could probably also just keep SecureBootModel disabled and not apply the new FirmwareFeatures (keeping UpdateNVRAM false), and then just use the VMM flag to install and update Monterey.
Correct. But see my response above.
You won't be missing anything. However, with the VMM flag, you have to enable it before updating and disable it after.
If you're already using the VMM flag, then as I've mentioned above, you should be able to skip FirmwareFeatures, SecureBootModel, UpdateNVRAM in step 3, and keep the VMM flag for step 5. While I haven't tested this in Catalina, it should work (this is recommendation #1 in the macOS section of the guide). Let me know how it goes!
I am having an odd problem with my MacPro 5,1 is running Catalina 10.15.7 using OpenCore 0.7.4.
With Catalina as the only disk in my system on a SATA Samsung 870 EVO
Catalina is selected as the Startup Disk in System Preferences.
I am able to boot from cold boot and shutdown without any issue; however, when I do a restart, the startup screen terminates with the stop symbol, circle with a diagonal through it. This is reproducible.
I may have changed a setting in my config.plist inadvertently as I have been using OpenCore 0.7.4 since it was released without this issue.
What could be causing this problem? I have attached my 0.7.4 config.plist. Many thanks.
With Catalina as the only disk in my system on a SATA Samsung 870 EVO
Catalina is selected as the Startup Disk in System Preferences.
I am able to boot from cold boot and shutdown without any issue; however, when I do a restart, the startup screen terminates with the stop symbol, circle with a diagonal through it. This is reproducible.
I may have changed a setting in my config.plist inadvertently as I have been using OpenCore 0.7.4 since it was released without this issue.
What could be causing this problem? I have attached my 0.7.4 config.plist. Many thanks.
Another thing I just noticed in this 0.7.5 update that has changed is several things related to DeviceProperties. Several things were removed, and a couple of them were changed from data fields to integer fields...
Might explain why my first attempt to upgrade did not work at all...froze indefinitely during the final reboot and after power recycle, would freeze halfway through the boot pretty much every time, and left the volume corrupted. Which screams that there is something wrong with SurPlus...but I think I have that configured correctly, so I'm not sure...
Might explain why my first attempt to upgrade did not work at all...froze indefinitely during the final reboot and after power recycle, would freeze halfway through the boot pretty much every time, and left the volume corrupted. Which screams that there is something wrong with SurPlus...but I think I have that configured correctly, so I'm not sure...
Sorry if this is not the right place to ask, since this issue is not addressed in post #1, but can anyone comment on the use of Acidanthera's HibernationFixup kext on a Mac Pro 5,1? My Mac has been an insomniac for a long time and, no matter what I do, it always wakes up a couple of seconds after it goes to sleep. Is there a reliable solution? Is that kext any use for us? TIA.
It was replaced about three years ago. That shouldn’t be the cause, but I’ll get a new one, just in case. Thanks.
EDIT: Fixed this issue with a pram reset (3x).
Hi all - Congrats to all the fine work done in this community. Truly awesome.
Having a problem where my Mac Pro 5,1 is always booting to Windows. I was trying upgrade to Martin Lo's package from open core which I had previously manually installed. I replaced the OC files (and not the other files in the EFI folder). The machine is always booting to the Windows SSD.
Windows and MacOS are on different physical SSDs. If I remove the Windows SSD, the machine boots fine to macOS. I know the upgrade to Martin Lo's package was successful, because I now have a graphics boot picker (which was previously text). But with Windows & MacOS SSDs inserted into the Mac Pro the Open Core boot picker doesn't show and the machine always boots to Windows.
I have tried booting to MacOS and then inserting the windows SSD and changing the startup disk settings in MacOS with no luck. Also tried selecting MacOS with control pressed (obviously option to boot to Windows doesn't show in that situation because I need to remove the Windows SSD to get the boot picker).
Any ideas on how to get the open core boot picker back with both SSD installed? Perhaps, there a choose startup disk option in Windows?
Hi all - Congrats to all the fine work done in this community. Truly awesome.
Having a problem where my Mac Pro 5,1 is always booting to Windows. I was trying upgrade to Martin Lo's package from open core which I had previously manually installed. I replaced the OC files (and not the other files in the EFI folder). The machine is always booting to the Windows SSD.
Windows and MacOS are on different physical SSDs. If I remove the Windows SSD, the machine boots fine to macOS. I know the upgrade to Martin Lo's package was successful, because I now have a graphics boot picker (which was previously text). But with Windows & MacOS SSDs inserted into the Mac Pro the Open Core boot picker doesn't show and the machine always boots to Windows.
I have tried booting to MacOS and then inserting the windows SSD and changing the startup disk settings in MacOS with no luck. Also tried selecting MacOS with control pressed (obviously option to boot to Windows doesn't show in that situation because I need to remove the Windows SSD to get the boot picker).
Any ideas on how to get the open core boot picker back with both SSD installed? Perhaps, there a choose startup disk option in Windows?
Last edited: