^Thanks for dispelling some of my ignorance. Can I conclude that OCLP is only marginally better, if at all, than regular OpenCore as far as booting macOS > 11.2.3 on a Mac Pro 5,1? In other words, no certainty that it will often boot the latest releases or betas of Big Sur and Monterey ALMOST reliably?
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 Mac OS 11.3 has broken support for older Mac Pros
- Thread starter VitaminK
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
- Status
I can confidently say that OpenCore Legacy patcher has no benifit over following the MacRumor's guide besides making it simpler for the end user. You'll end up with basically the same product if you put the time and work in.
- If you want to nitpick, we do add patches some might not care about like SMC model spoofing to avoid SMC updates, add DRM patches for AMD, audio patches for HDMI, enhanced NVMe power management, etc. Some could argue this is bloat for their setup and so a machine built with the guide is actually better for kernel usage
Upgrading Big Sur 11.2.3 in a Parallels virtual machine to 11.4, on my 5,1 Mac Pro running 11.2.3. Well now, isn't this interesting?
EDIT: Stuck again? On a virtual machine? Seriously? This has to be a clue. Virtualized hardware exhibiting the same behavior as bare metal.
EDIT 2: 11.4 installed fine after another reboot, but many attempts to install Monterey get stuck halfway through the progress bar every time. I was attempting to upgrade from a Catalina VM, so maybe I'll try a native install, upgrade from a fresh Mojave install, and upgrade from a fresh Big Sur install.
EDIT: Stuck again? On a virtual machine? Seriously? This has to be a clue. Virtualized hardware exhibiting the same behavior as bare metal.
EDIT 2: 11.4 installed fine after another reboot, but many attempts to install Monterey get stuck halfway through the progress bar every time. I was attempting to upgrade from a Catalina VM, so maybe I'll try a native install, upgrade from a fresh Mojave install, and upgrade from a fresh Big Sur install.
Last edited:
Thanks.
I use Martin's OC, 0.70 version.
I have Mojave in an adapter to SSD on Bay 1.
OC is on EFI's Mojave.
I have a PCIe dual SSD bootable card with only one SSD that I managed to install latest Catalina (no luck with directly installing BS 11.2.3).
I tried then to update from Catalina to BS 11.2.3.
It reboot with the Installer present in the Picker.
Then it tried to install but same as when I tried to directly install BS, the progress bar is at 10%, then the mouse pointer shows up, then it reboot... Endlessly.
I tried NVRAM reset 5 times during the reboot, and I tried force shutdown, and start, but same story...
Anyone have a clue why even BS 11.2.3 won't go to the installation screen?
Thanks in advance.
Go back to the start!
Get Mojave running natively on an SSD i.e. no OC.
Now follow these instructions exactly to upgrade to Catalina https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/
Use the vanilla OC and standard SSD's i.e. no PCie.
Now download 11.2.3 and upgrade
It is working for me.
- Upgrading on a MacBook Pro running 11.4 FAILED!
- Upgrading on cMP 5,1 running Catalina worked like a charm.
- After that, I can run Parallels. Not that VMware will not work on cMP running Big Sur. It forces an unsupported HyperVisor.
- I was even able to clone and upgrade that to Monterey
How's the performance in Paralles haralds? I tried running BS in a Parallels vm a few months ago and it was terribly slow. Unusable. VMware was worse though from what I remember.
Hello everyone. Let's try to keep the noise down in here. This is not a support group - there are other groups for that. This group is for those of us trying to solve the race condition that affects our 5,1 Mac Pro's as of Big Sur 11.3b3. Thanks.
I guess I'm another lucky cMP user with 11.4 running perfectly smooth since update a few days ago and no issues with booting whatsoever after ~20 reboots/shutdowns also while switching between MacOS and Win10.
My setup is as follows in case I can help you somehow solve the mystery:
-Mac Pro 5,1 (2012) single cpu W3680, 24GB of RAM
-Bootrom appears in system info as 9144.0.6.7.0, but i'm guessing that's some sort of spoof/error?
-Running OpenCore 0.6.7, Martin Lo's package with just HWAccel and MP 7,1 Board ID added.
Hardware:
-SATA SSD in Bay1 with OC and Big Sur - Crucial MX500 with TRIM enabled
-HDD in Bay2 with just data formatted in APFS
-NVMe Kingston KC1000 with Win10 in a generic ICY BOX adapter in PCIe slot 4
(-RME HDSPe AIO audio interface in slot 3 - probably not relevant)
-Radeon RX5600 XT in slot 1, display connected via DP (this caused me some issues with booting in the past so might be worth mentioning)
Updated directly from 11.2.3, the update preparation took forever - about 30mins i'd say, but then after a few reboots (which i believe were always the case while updating Big Sur, not only with 11.3/11.4) the system loaded normally and everything seems to be working fine ever since.
My setup is as follows in case I can help you somehow solve the mystery:
-Mac Pro 5,1 (2012) single cpu W3680, 24GB of RAM
-Bootrom appears in system info as 9144.0.6.7.0, but i'm guessing that's some sort of spoof/error?
-Running OpenCore 0.6.7, Martin Lo's package with just HWAccel and MP 7,1 Board ID added.
Hardware:
-SATA SSD in Bay1 with OC and Big Sur - Crucial MX500 with TRIM enabled
-HDD in Bay2 with just data formatted in APFS
-NVMe Kingston KC1000 with Win10 in a generic ICY BOX adapter in PCIe slot 4
(-RME HDSPe AIO audio interface in slot 3 - probably not relevant)
-Radeon RX5600 XT in slot 1, display connected via DP (this caused me some issues with booting in the past so might be worth mentioning)
Updated directly from 11.2.3, the update preparation took forever - about 30mins i'd say, but then after a few reboots (which i believe were always the case while updating Big Sur, not only with 11.3/11.4) the system loaded normally and everything seems to be working fine ever since.
Not only you (due to the off-topic Parallels comment), but the sudden rush of new people posting completely off-topic posts that aren't contributing any useful information towards solving this issue. I'm not afraid to call anyone out if I need to direct a comment to someone in particular, LOL
You're probably not as lucky as you think. ALL 5,1 Mac Pro's have this issue, but due to different combinations of hardware, some experience the problem more often than others. Given that the issue is with Apple's new bootstrap code, every single machine has the issue. My record number of successful reboots is 22x, but shortly after that, I had about a 50% failure rate - it's that unpredictable. I hope you're using a test machine, as a single failed boot can completely corrupt your boot drive, and all drives attached.
As for the boot ROM, you're using Martin's config, which spoofs the boot ROM version to a high number in order to avoid any unwanted firmware update attempts. While Apple will not be providing us with any more firmware updates, we're spoofing a different machine so it's possible an attempt to flash the iMac Pro's firmware could happen (and if it does, you have a brick).
Is it off-topic? You mentioned it earlier in the page yourself and it could be a reasonable solution for some if it works well and macOS BS 11.3+ ends up being permanently broken on cMP.Not only you (due to the off-topic Parallels comment), but the sudden rush of new people posting completely off-topic posts that aren't contributing any useful information towards solving this issue. I'm not afraid to call anyone out if I need to direct a comment to someone in particular, LOL
Sounds like the same experience I'm having. This shouldn't be happening at all though, and if this is indicative of the race condition, in a virtual machine, it really narrows down the focus of the issue. I'll let @tsialex and other devs comment on that theory though.
I'm not looking for a solution to running the OS in a VM. My post indicates the race condition may be present in a VM as well, which is very interesting towards solving the issue. Discussing the performance of an OS in a VM does not contribute any meaningful information towards solving this issue. Hope that clears up the misunderstanding.
It does clear it up and it was a rhetorical question. But I'll answer my own question to help clear it up for you and for the benefit of others who may hesitate to contribute after reading your previous comment which may discourage them from doing so. It's not off-topic at all and it contributes to the conversation. So much so that I will ask it again.
Have users running BS in Parallels found the experience sufficient for running the OS and their tasks? I found it very slow on Parallels and VMWare Fusion but I tried it months ago. Has it gotten any better?
Please do not use such statements in this thread as it implies untrue statements in this context. Selecting and booting the operating system is a part of the system performance. If the booting process is not yielding consistent results the system "is not working fine". It is physically impossible to keep the machine powered on forever. There either will be a lightning strike, a power blackout etc. which will force the machine to reboot/shut down and realize the system is not working fine.
My Parallels BS VM has one single purpose: to test drive particular software updates that I feel might misbehave on my physical Big Sur. Once I'm sure they are stable on the virtual machine (which runs reasonably fast, considering everything's virtualized), I shut it down and then I install the relevant software on my "real" Big Sur 11.2.3.
IMO yes, please see the thread title. Feel free to open a new thread and discuss how Parallels and Big Sur 11.3+ runs in a 5,1 Mac Pro.
Thanks for bringing this back on topic folks. This is a critical topic that needs direct and focused attention for resolution.
I'm not claiming there isn't anything fishy going on under the bonnet because that's far from my expertise, i'm just saying that so far my user experience is as normal as it could be and i wouldn't even know about this thread if i had not followed the forums. But still, since there's no definite conclusion on what's causing this issue - how can you know for sure that every cMP is affected and i'm also gonna encounter the problem sooner or later?
After 49 pages in this forum there is a conclusion that cMP's have an issue booting 11.3 and later found through multiple trials/errors. You think yours will be excluded for some unknown reason? Why not testing 20 or more boots and coming back with the results confirming or denying the issue?
- Status