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
EDITED:
Hey guys,
Thanks for all the fast replies. I really appreciate it.
Okay - Let me revise the above procedure on my cMP to ensure I'll get it right this time (especially if it was a blessing problem). I originally figured it might be easier if I did things externally on my MacBook, but will keep it really simple and only use the cMP.
Again, the Big Sur 11.2.1 SSD (with all my stuff on it) appears to boot just fine to my MacBook as an external drive, so I've got some hope. I've since removed OC on it, to be safe and to start over.
So again, does this seem correct?
***************
(0) Reset cMP's NVRAM 3x (zapping PRAM 3x).
(1) Ensure that only one non-OC, bootable Mojave drive (which I have all set up) AND my SSD that now correctly has a functioning version of Big Sur 11.2.1 on it are in the cMP drive bays.
(2) Reboot into Mojave's recovery. Disable SIP. Reboot into Mojave again.
(Stuck at this part...as I've got an unflashed RX580...have been doing this blindly. I think this was part of my reason why to do this externally...or do this with a drive with OC on it so I could see what I was doing per the boot screen. It keeps shutting down if I put my non-OC drive in with Big Sur preinstalled on it.)
(3) Backup the ROM (thanks, tsialex) while I'm at it.
(4) Next, re-install MLo's OC 0.6.6 onto the SSD's EFI partition using Clover Config to mount the EFI drive. Leave MLo's config.plist alone. (Firmware should already be spoofed and no more messing with the VMM flag.)
(5) Close Clover Configurator.
(6) Run the Blesser.
(7) The OC's boot picker should show up and it should correctly boot into Big Sur 11.2.1?
Thanks, everyone.
Hey guys,
Thanks for all the fast replies. I really appreciate it.
Okay - Let me revise the above procedure on my cMP to ensure I'll get it right this time (especially if it was a blessing problem). I originally figured it might be easier if I did things externally on my MacBook, but will keep it really simple and only use the cMP.
Again, the Big Sur 11.2.1 SSD (with all my stuff on it) appears to boot just fine to my MacBook as an external drive, so I've got some hope. I've since removed OC on it, to be safe and to start over.
So again, does this seem correct?
***************
(0) Reset cMP's NVRAM 3x (zapping PRAM 3x).
(1) Ensure that only one non-OC, bootable Mojave drive (which I have all set up) AND my SSD that now correctly has a functioning version of Big Sur 11.2.1 on it are in the cMP drive bays.
(2) Reboot into Mojave's recovery. Disable SIP. Reboot into Mojave again.
(Stuck at this part...as I've got an unflashed RX580...have been doing this blindly. I think this was part of my reason why to do this externally...or do this with a drive with OC on it so I could see what I was doing per the boot screen. It keeps shutting down if I put my non-OC drive in with Big Sur preinstalled on it.)
(3) Backup the ROM (thanks, tsialex) while I'm at it.
(4) Next, re-install MLo's OC 0.6.6 onto the SSD's EFI partition using Clover Config to mount the EFI drive. Leave MLo's config.plist alone. (Firmware should already be spoofed and no more messing with the VMM flag.)
(5) Close Clover Configurator.
(6) Run the Blesser.
(7) The OC's boot picker should show up and it should correctly boot into Big Sur 11.2.1?
Thanks, everyone.
Last edited:
I just meant for blessing/ nvram manipulation.
Mavericks (and Yosemite) don't have SIP implemented. it came with El Capitan so no booting to recovery is needed for nvram manipulation. It can be done within the OS X.
Yosemite has SIP, buggy as hell, and only works for kexts/libraries signatures.
Best for user to evaluate and make a call depending on their setup.
I see. Even older/lesser than the K6000.
Anyway, best the user decides what they want to do.
Interesting. I thought it was in EC when they enabled it. I know Mavericks does not have it.
Actually just remembered I did a backup in Mavericks with the ROM tool. It said the extension was not signed but allowed.
Works fine with 10.8 to 10.14 - except with 10.10. I never tested with 10.7, but I've tried 10.6 and it won't work unless you install a lot of dependencies.
That's because your Mac finds OC first. But not having OC properly blessed is problematic for routing the blessing that may occur from an installer.
Boot into Mojave natively. Then enter the following in terminal:
sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery. This should get you into recovery.Okay -- Another update. Partial success, and we're finally getting somewhere.
So, what do I need to properly bring this all home where:
*** I can remove that emergency HD and continue to boot of the SSD...
**** Safely do OTA updates from here on out without fear of another disaster...
I'm assuming...the answer is: Reinstall OC on the SSD...bless...reboot into Big Sur...shut down...and then remove that emergency HD? Also, do I zap the PRAM again at any point?
Thanks, everyone for their help. Cheers!
(1) After backing up my BootROM on a non-OC version of Mojave (SIP disabled), I then proceeded to install ML's 0.6.6 (mount EFI with Clover Configurator), used the Bless utility, and rebooted. Rebooted with the boot screen and selected Mojave. So that part was stupidly easy. No issues.
(2) I put my original SSD into the cMP in with my Big Sur 11.2.1 installation on it -- but OC was removed on the SSD. It saw the SSD -- great! I selected it, and was finally able to boot from both the 11.2.1 recovery AND the drive. So that's good and at least I have ready access to my files.
Meanwhile, if I remove that emergency Mojave drive that has OC on it, I won't have OC anymore. Plus, what's weird is that "csrutil status" in Terminal shows me that weird "unsupported configuration" where everything with SIP is disabled except for "BaseSystem Verification: enabled". I'm assuming that's from M-Lo's OC v0.6.6 (config.plist?) and nothing to be worried about?
So, what do I need to properly bring this all home where:
*** I can remove that emergency HD and continue to boot of the SSD...
**** Safely do OTA updates from here on out without fear of another disaster...
I'm assuming...the answer is: Reinstall OC on the SSD...bless...reboot into Big Sur...shut down...and then remove that emergency HD? Also, do I zap the PRAM again at any point?
Thanks, everyone for their help. Cheers!
I'm trying to understand why not keep things simple? When I started using OC, I has running Mojave on one SSD into SATA1 bay. Then, I purchased a Syba card (see my signature for model) and 2 NVMe blades, one for Catalina+OC and one for Windows 10. I followed to the letter the first post instructions and everything worked perfect from the start.
Can you do the same? Set a default Mojave install on SATA1 bay, make sure everything works perfect with Mojave before touching OC. Then add a second drive into SATA2 bay and install there Catalina+OC EFI that
you build yourself. The idea is to have full control and knowledge of what you put into your Mac, look at the issues you experience by "trying" things.
Last edited:
@TECK - As an independent Mac consultant for over 25 years, one would hope and imagine that I did in fact do things to the letter and simply - particularly well before taking a chance on depending upon my cMP as a dependable Big Sur work Mac. That's why I've been so puzzled here.
In fact, I already did so with two different flavors of OC when Big Sur GM was released and did what you suggested above back then (actually Catalina the week before Big Sur was released, and then Big Sur GM). After struggling for whatever reason back then, I finally got it to work and things ran just fine for months. That's what has stumped me so greatly -- as I was genuinely trying to keep things just as simple as possible. Something seemed to be going wrong somewhere -- and please forgive me for publicly asking everyone as to why -- as maybe I missed something. This all should have gone like clockwork. This is a vastly different situation than a potentially lazy newbie who doesn't read the procedures or the threads.
Over the past few days, I eventually experimented with the external drive route for three reasons: (1) I was depending on my Big Sur reason for work reasons and was getting nowhere with the internal drive route, (2) my backup of my master drive is currently 150 miles away in it's cMP 5,1 twin and I needed my data ASAP, and (3) I was racing to get my dual-screen cMP working ASAP specifically to easily online book my 80-year-old father-in-law a COVID vaccine online yesterday - an impossible task yesterday with our state's faulty online booking system -- something infinitely more difficult than scoring concert tickets.
Hopefully this explains as to why things didn't seem so simple, @TECK -- Only this evening, and at my earliest opportunity, I was able to get my BootROM to @tsialex -- who generously gave me his time and assessment -- and it turns out that my NVRAM may indeed be failing. We'll have to see how things go.
In fact, I already did so with two different flavors of OC when Big Sur GM was released and did what you suggested above back then (actually Catalina the week before Big Sur was released, and then Big Sur GM). After struggling for whatever reason back then, I finally got it to work and things ran just fine for months. That's what has stumped me so greatly -- as I was genuinely trying to keep things just as simple as possible. Something seemed to be going wrong somewhere -- and please forgive me for publicly asking everyone as to why -- as maybe I missed something. This all should have gone like clockwork. This is a vastly different situation than a potentially lazy newbie who doesn't read the procedures or the threads.
Over the past few days, I eventually experimented with the external drive route for three reasons: (1) I was depending on my Big Sur reason for work reasons and was getting nowhere with the internal drive route, (2) my backup of my master drive is currently 150 miles away in it's cMP 5,1 twin and I needed my data ASAP, and (3) I was racing to get my dual-screen cMP working ASAP specifically to easily online book my 80-year-old father-in-law a COVID vaccine online yesterday - an impossible task yesterday with our state's faulty online booking system -- something infinitely more difficult than scoring concert tickets.
Hopefully this explains as to why things didn't seem so simple, @TECK -- Only this evening, and at my earliest opportunity, I was able to get my BootROM to @tsialex -- who generously gave me his time and assessment -- and it turns out that my NVRAM may indeed be failing. We'll have to see how things go.
Last edited:
What do I need to do to get the updates to show up in system preferences?
It says I'm up to date with 11.2 when 11.2.1 should be available. VMM flag on doesn't make a difference.
Thanks
Mac Pro 5,1 (mid 2010), OC 0.6.6, Config attached
EDIT: Solved, had to disconnect VPN for the update to show up, Mullvad app was causing the issue.
It says I'm up to date with 11.2 when 11.2.1 should be available. VMM flag on doesn't make a difference.
Thanks
Mac Pro 5,1 (mid 2010), OC 0.6.6, Config attached
EDIT: Solved, had to disconnect VPN for the update to show up, Mullvad app was causing the issue.
Last edited:
You need to use hybridization for 11.2.1. See the section in the first post "Hybridization and related settings" and implement the changes in your config.plist. With these settings you can disable the VMM setting.
Regards
My CMP (4,1 updated to 5,1 with the necessary firmware updates) is running Open Core quite happily (or so it appears): Mojave, Catalina, and Windows 10; each on their own drive. The Mojave OS is on the 2 Tb spinning hard drive. Catalina is on the next drive, a 1 Tb Samsung EVO 850 SSD. The Windows drive is on the last drive, a 1 Tb Samsung EVO 850 SSD.
A few days ago, I lost the USB ports front and rear that are connected directly to the motherboard. I could still use the add-on PCI USB/Firewire card. Nothing that I did seemed to fix that. And since I am running OpenCore, Apple's AHT or the newer hardware tester did not seem to run or load properly (didn't work at all, even after option + d).
As a last resort, I unplugged the cMP from the cord, at the machine, and left it that way for several minutes. When I plugged it back in I had the "native" USB ports again.
However, since that incident, Mojave has gotten increasingly sluggish to the point that now, even a click on the mouse results in a spinning color wheel. Catalina (which I am using right now) and Windows 10 do not suffer from any ill effects.
At the present, Mojave will not even completely shut down. Even when I shut down, and select that option, the cursor remains on the screen. The cursor can be moved around on a black screen. If I click the mouse I get a spinning color wheel. This went on for more than twenty minutes last night. I finally pressed the power button.
I tried Avast for Mac (free version) and it had no effect. However, in downloading the software, the download would slow down to 0 bps for a minute or two, before resuming. It took over an hour to download a file that should have only taken maybe five minutes (or less).
As I said previously, I can boot and get the correct boot picker all the time. If I choose Catalina, or Windows the process continues properly and the OS's work great.
I've not updated OpenCore in three or four months. That is my first inclination. However, I think I should also consider virus problems (I know, it's not likely) or a problem with the hard drive. The hard drive gives no such indications and is only about a tenth full, if that.
If the problem is a virus, then I need to get that resolved first. If it is a hardware problem, then I will probably have to replace the hard drive.
If I need to update OpenCore, then the question I have is: can that be done through Catalina, or do I need to do it through Mojave (since that's how I originally installed it)? Considering the current problems with Mojave I would probably be looking at a long time (several hours to several days) to do it.
I need the most conservative approach. If there is a virus, or even a remote possibility of a virus, then I absolutely must address that first. On Windows' machines there are root viruses that can be remedied only by doing a boot time scan. Since the cMP's are Intel machines, that might have to be done.
Thanks for any input.
A few days ago, I lost the USB ports front and rear that are connected directly to the motherboard. I could still use the add-on PCI USB/Firewire card. Nothing that I did seemed to fix that. And since I am running OpenCore, Apple's AHT or the newer hardware tester did not seem to run or load properly (didn't work at all, even after option + d).
As a last resort, I unplugged the cMP from the cord, at the machine, and left it that way for several minutes. When I plugged it back in I had the "native" USB ports again.
However, since that incident, Mojave has gotten increasingly sluggish to the point that now, even a click on the mouse results in a spinning color wheel. Catalina (which I am using right now) and Windows 10 do not suffer from any ill effects.
At the present, Mojave will not even completely shut down. Even when I shut down, and select that option, the cursor remains on the screen. The cursor can be moved around on a black screen. If I click the mouse I get a spinning color wheel. This went on for more than twenty minutes last night. I finally pressed the power button.
I tried Avast for Mac (free version) and it had no effect. However, in downloading the software, the download would slow down to 0 bps for a minute or two, before resuming. It took over an hour to download a file that should have only taken maybe five minutes (or less).
As I said previously, I can boot and get the correct boot picker all the time. If I choose Catalina, or Windows the process continues properly and the OS's work great.
I've not updated OpenCore in three or four months. That is my first inclination. However, I think I should also consider virus problems (I know, it's not likely) or a problem with the hard drive. The hard drive gives no such indications and is only about a tenth full, if that.
If the problem is a virus, then I need to get that resolved first. If it is a hardware problem, then I will probably have to replace the hard drive.
If I need to update OpenCore, then the question I have is: can that be done through Catalina, or do I need to do it through Mojave (since that's how I originally installed it)? Considering the current problems with Mojave I would probably be looking at a long time (several hours to several days) to do it.
I need the most conservative approach. If there is a virus, or even a remote possibility of a virus, then I absolutely must address that first. On Windows' machines there are root viruses that can be remedied only by doing a boot time scan. Since the cMP's are Intel machines, that might have to be done.
Thanks for any input.
I have done another search for any updates on USB issues on a Mac Pro 5,1 running Big Sur and could not find any update. Catalina does not have the following issues:
- HID devices on built in USB 2 are not recognized unless plugged in at boot
- USB 3 is flaky. My Brio camera does not work properly unless plugged in directly. On a hub it "stutters."
This all works nicely on Catalina with or without OC.
Are there any new discoveries?
- HID devices on built in USB 2 are not recognized unless plugged in at boot
- USB 3 is flaky. My Brio camera does not work properly unless plugged in directly. On a hub it "stutters."
This all works nicely on Catalina with or without OC.
Are there any new discoveries?
The USB works perfectly well on the motherboard now. That problem cleared up after I removed power from the computer.
The mouse and the keyboard are plugged into the USB 1 ports at the front. They were plugged into those ports when I booted the computer several days ago and had the failure. The mouse and keyboard worked on the add-on USB 3 ports.
The USB 1 ports went back to normal function after removing and reapplying power to the computer.
There have been no further failures of USB ports.
The main problem now is that Mojave is essentially unusable, for what reason, I do not know.
The mouse and the keyboard are plugged into the USB 1 ports at the front. They were plugged into those ports when I booted the computer several days ago and had the failure. The mouse and keyboard worked on the add-on USB 3 ports.
The USB 1 ports went back to normal function after removing and reapplying power to the computer.
There have been no further failures of USB ports.
The main problem now is that Mojave is essentially unusable, for what reason, I do not know.