Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Updated OC with Martin Lo's package ( 0.7.3 V2 ) on a MacPro 4.1->5.1 and macOS Monterrey Public Beta 4. All was smooth and is running perfectly. Also tried ( can I say it? ) to upgrade to Beta 7 after the upgrade, but just the same "Firmware Error" that takes me back to Beta 4. At least is working fine with SurPlus+Martin Lo's OC+Beta 4.
 
Sorry for the noob question but here it is.
How do I install this patch ? Instructions somewhere ?

I only know Ben Sova Patched Sur with Big Sur 11.2.3

I honestly have no idea where to start and the tools I need to download.
sorry once again
 
You need to bless open core again and it will work.
I'm sorry for the basics, but I'd like to check the bless command. Let's assume that the partition containing OpenCore is disk0s1. Is it correct to use the command "diskutil mount /dev/disk0s1" / "bless -mount /Volumes/EFI -setBoot" in this case?
But I'm able to start Big Sur 11.6, OpenCore is not loaded?
 
Last edited:
I just updated OC from 0.6.6 to 0.7.3 with SurPlus, proceeded from Catalina 10.15.7 straight to 11.6 and it works like a charm! 💯
 
Well that's just incredible. A Mac that originally came with Leopard or Snow Leopard can run Monterey. Very impressive. I still think it's better to go with a 6,1 or 7,1, but nice to see people keeping the classic cheesegrater going. I'm stuck on Catalina on my 2012 MBP, which is fine, but I'll have to decide what to do when the security updates end. Since they are bringing back some ports on the new MPBs I might opt for one of those, but it's nice having the built-in DVD player for watching movies when traveling.
 
Well that's just incredible. A Mac that originally came with Leopard or Snow Leopard can run Monterey. Very impressive. I still think it's better to go with a 6,1 or 7,1, but nice to see people keeping the classic cheesegrater going. I'm stuck on Catalina on my 2012 MBP, which is fine, but I'll have to decide what to do when the security updates end. Since they are bringing back some ports on the new MPBs I might opt for one of those, but it's nice having the built-in DVD player for watching movies when traveling.
If the 6,1 or 7,1 were positioned as an actual replacement to the 5,1 I would agree, but they are not. The 6,1 has serious issues and is not really upgradable. The 7,1 doesn't make financial sense if your aren't using your computer to use all that power to generate income.
 
If the 6,1 or 7,1 were positioned as an actual replacement to the 5,1 I would agree, but they are not. The 6,1 has serious issues and is not really upgradable. The 7,1 doesn't make financial sense if your aren't using your computer to use all that power to generate income.

That's a largely inaccurate blanket statement about the 6,1. A more correct statement would be, "The 6,1 can have serious issues." That's true, but I think the majority of problems are due to an overheated GPU or user caused damage when trying to upgrade the CPU. I also think there's a glitch in Apple's driver for the D300 GPUs in Catalina & beyond that can cause kernel panics. The upgradability depends what you are trying to upgrade. Memory, storage, & external via TB2 are no problem. Can't upgrade the GPUs, but the D700s are still pretty good. Mine works great for photo editing, even 61 MP RAW files are no problem. I don't need to do 4K or 8K video editing and if you do then a 7,1 is the obvious choice.

I can't imagine too many scenarios where you'd need something more powerful than a 6,1 unless you are making money doing things that require the capability. And since you're making money the expense of the 7,1 isn't a problem.
 
  • Like
Reactions: flygbuss and JohnD
Force shutdown, wait a few seconds, then start up again, see if the installation can continue after that.

If not, perform a 3x NVRAM reset.

So far, I received one report about racing condition may still there. But I am not sure if that user installed OC and SurPlus correctly. Need more time to confirm what’s happening there.

Also, his case shows the same symptom as the patch is not there (about 70% chance the cMP hangs during boot, but not infinite reboot). So, I suspect your problem isn’t SurPlus related, but just coincidentally fall into a boot loop due to another reason.
Appreciate the help! I tried force shutdown this morning but that did not help. Will try 3x NVRAM reset when I get home. Will I need to re-bless after the NVRAM reset?
 
Appreciate the help! I tried force shutdown this morning but that did not help. Will try 3x NVRAM reset when I get home. Will I need to re-bless after the NVRAM reset?
Depends on your hard drive config.

Assuming there is no other boot drive in the cMP, and you are using my package. Then OC should stay enabled after 3x NVRAM reset.

If you aren't sure, then you better remove all other drives, but just leave the macOS drive, and the OpenCore drive (if not on the same one) installed.

If still doesn't work. Then please try to boot to Big Sur recovery partition, and re-install Big Sur from there (no need to format any drive, just re-install Big Sur on top of your existing one. All user data should be preserved).
 
Sorry for the noob question but here it is.
How do I install this patch ? Instructions somewhere ?

I only know Ben Sova Patched Sur with Big Sur 11.2.3

I honestly have no idea where to start and the tools I need to download.
sorry once again
You should start with this version of OpenCore installed by the OCLP tool. It is a highly automated way to install it, has some hardware detection included and nevertheless it will need you to read the docs and follow the instructions before having success. Use the latest nightly build of the OCLP TUI (not GUI) version to install OpenCore.

Important: Have a backup of your data and a Ben Sova Patched Sur UBS installer ready in case you fail completely.
 
Thanks for the references and help but this looks way to complicated for my software knowledge. I guess this is the end for my cMP. I better get a M1 Mac Mini and have peace of mind, afterall, I don’t want to lose all my data or worst, brick my cMP.
Much appreciate the help, once again.
 
Thanks for the references and help but this looks way to complicated for my software knowledge. I guess this is the end for my cMP. I better get a M1 Mac Mini and have peace of mind, afterall, I don’t want to lose all my data or worst, brick my cMP.
Much appreciate the help, once again.
Actually, there is no need to be a coder or extremely knowledgeable to install opencore and big sur. In fact, you can download the latest h9826790 opencore package where everything is configured for you. Nevertheless, that is your own choice.
 
  • Like
Reactions: dksoutha
@Syncretic , I was working hard on tweaking OpenCore's config.plist today. But in the end I couldn't find the cause. So I decided to revert to the Latebloom version. For the Latebloom version, Cold/Warm boot is successfully booted within two times. However, SurPlus requires 5 to 10 forced reboots.
I'm using a FusionDrive that I configured myself, could this be the cause? The EFI area that the Mac recognizes to boot is the EFI area of the HDD part of this FusionDrive. The FusionDrive configuration behaves strangely at this point. For example, if the SSD part of the FusionDrive is always fixed at disk1s1, the HDD part can be disk0s1 or disk2s1 at every boot. The SSD section is also rarely variable. Is this disk number fluctuation causing a bad situation?


@m1ndless , I also did a PRAM reset and OpenCore started behaving strangely. As a result, I gave up on SurPlus. Perhaps I could have used SurPlus without any problems if I had not done the PRAM reset.
After I did the PRAM reset, nothing showed up on the display until the desktop view. Whether it's SurPlus or Latebloom.
Before the PRAM reset, I could see the Apple logo and the progress bar. What's your situation?
After the hard reset it's back to normal for me. I just found it weird that single instance when I did the 3x reset i seem to have went back temporarily to the boot hang like it was when the race condition was still there.

Another strange thing it seems that my mac pro has lost the ability to sleep. Anyone else experiencing this? Tried everything there is to reset but it seems I can't get it to sleep (display will off but cpu light still remains solid)

Would you have any ideas @h9826790
 
Depends on your hard drive config.

Assuming there is no other boot drive in the cMP, and you are using my package. Then OC should stay enabled after 3x NVRAM reset.

If you aren't sure, then you better remove all other drives, but just leave the macOS drive, and the OpenCore drive (if not on the same one) installed.

If still doesn't work. Then please try to boot to Big Sur recovery partition, and re-install Big Sur from there (no need to format any drive, just re-install Big Sur on top of your existing one. All user data should be preserved).
There is another route to avoid recovery partition, but it has some other caveats as well:
From Mavericks you can bless or change the csr-active-config without rebooting as there is no protection for the NVRAM. The problems are:
1. You need a video card as Kepler (Titan works fine) which has drivers for a broad spectrum of macOS. I don't know how RX-580 works without acceleration although it may be usable.
2. Mavericks does not recognize APFS so the latest macOS selectable from the startup disk is HS (providing HS is installed on HFS+ partition). So from Mavericks you can boot to HS and from there anywhere else. No recovery boot is needed nor a boot screen.
 
First of all:

THANK YOU SO MUCH! This fix is absolutely awesome.

One thing I'm thinking about right now is this:

Ever since within the config of SurPlus wet set it to a max kernel version, does that mean that if I update my system, let's say to 11.7 if it ever comes, then I'll be stuck in a no boot situation again because SurPlus isn't loaded anymore because the kernel is newer than what was put as max into the config file?

In that case, what would I have to enter into that config file to like cover all future updates of 11.x for example?
 
First of all:

THANK YOU SO MUCH! This fix is absolutely awesome.

One thing I'm thinking about right now is this:

Ever since within the config of SurPlus wet set it to a max kernel version, does that mean that if I update my system, let's say to 11.7 if it ever comes, then I'll be stuck in a no boot situation again because SurPlus isn't loaded anymore because the kernel is newer than what was put as max into the config file?

In that case, what would I have to enter into that config file to like cover all future updates of 11.x for example?
A Big Sur kernel version number (20.x.x) will never be greater than the current Monterrey one (21.x.x), so for Big Sur you are safe for all future Security Updates. Obviously I'm talking specifically about the kernel version number, not any possible future Apple modification to the kernel code itself.
 
Thanks for the references and help but this looks way to complicated for my software knowledge. I guess this is the end for my cMP. I better get a M1 Mac Mini and have peace of mind, afterall, I don’t want to lose all my data or worst, brick my cMP.
Much appreciate the help, once again.
Hi, Starting with OpenCore is actually not as difficult or as dangerous as many of the discussions seem to suggest. From your signature you've already done a lot to your 5,1 so you're clearly not a complete level 1. I simply followed cdf's instructions on this thread (and I mean really, really follow each instruction one at a time). I now have 11.6 installed and I'm looking forward to Monterey. I'm still baffled by most of the discussions, but hey.
 
  • Like
Reactions: paalb
This is fantastic! Your research and debugging with latebloom has taken a long time and it has successfully paid off, helping many others with our beloved Mac Pros.

I tried to donate but my Paypal doesn't allow donations to your country. Do you have any crypto (BTC/ETH/ADA/XLM) addresses I can send to?
I've posted my findings about the MacOS 11.3+ "race condition" bug, along with a patch I'm calling SurPlus, in a github repository. All the details are there, and I'm not sure there's any benefit in reposting them all here. (Yes, I had to write my own debugger; the boot hangs generally happened before the boot was far enough along for MacOS' remote debugging facility to work, so drastic measures were required.)

This thread will serve for questions (hopefully with answers), comments, and discussion regarding SurPlus.

In a nutshell: our Classic Macs will live to fight another day. As of now, latebloom is deprecated. Install the three-byte SurPlus patch in your OpenCore config.plist and boot Big Sur or Monterey just as you would Catalina or Mojave.

PLEASE: If you're going to post in this thread because you're having trouble getting the patch to work, please include your OpenCore config.plist file as an attachment. Without that, it's very difficult to offer assistance.
 
I got your one installed and it it showed 9144.0.7.3, but I got the same error as before installing Monterey 12 beta 6 to an NVME. It went to about 80% install progress, the screen went blank, it went to do a restart then nothing, dead. No chime.

I'm about to put in my old HDD and then wipe the NVME again then re-bless Opencore.

Thanks for your help, I tried - it doesn't look like it wants to work. Sorry.

What I did get is a more responsive running open core boot screen so that’s a nice win.

I recovered it back to normal more quickly this time.
 
Last edited:
I've updated my config and 11,6 is on it way down fingers crossed
all went well till it rebooted now stuck in a boot loop with Big Sur
here's my config, think somethings wrong to upload I've changed the extension to zip
just delete zip and replace with plst
Update to this post, I’ve installed 0,7,3 v2 and big sur booted right up and finished it installation but no Bluetooth. I’ve applied the surplus patch to 0,6,8 now I have Bluetooth and all booting correctly. However upgrading Catalina to Monterey throws a firmware error 🤔🤔🤔
 
I had an isuue updating - I added the surplus edits to the 0.7.3 config, neglected to disable latebloom then updated from 11.2.3 - 11.6 on NVME. Couldn't boot in to Big Sur after that. :)

I ran csrutil status and found that it was in a hybrid setting, all were disabled except base verification something or other (I can't remember the exact name) So this was probably part of the issue.

Pulled all my production drives, NVRAM reset, and booted natively into my mojave fallback drive then disabled latebloom, and reblessed my opencore / time machine drive.

Then reinstered Big Sur drive, after a few reboots got 11.6 running smoothly. On first reboot it went into recovery and I just said reboot again, and THEN it worked.

Perhaps this was caused because I left latebloom enabled (I didn't realise it was enabled by default), and since latebloom is now redundant this should hopefully not be an issue for future updates.
 
Last edited:
The biggest highlight of 2021 is SurPlus! (And that’s with the backdrop of the new James Bond film being released imminently!)

I haven’t tried it yet but I’ve read through all the technicals and been following the forums on latebloom but hadn’t had the chance to take the plunge.

I have a MacPro 4,1, Dual X5675 (A weird CPU choice but works great and keeps the heat down!), 48GB RAM, RX580, 8TB PCIe x16 (4x2TB NVMe Software RAID0), 8TB HDD (6x 2TB HDD Software RAID6) with Dual Apple Cinema 30” (Old School) Displays currently stuck at 11.2.3 and I’m very much looking forward to upgrading to 11.6

I wanted to give a big shout out to Syncretic and this incredible discovery and achievement! (So much so that I had to create a macrumors forum account to do so) - donation to follow!
 
  • Like
Reactions: pawkor and philhyde
That's a largely inaccurate blanket statement about the 6,1. A more correct statement would be, "The 6,1 can have serious issues." That's true, but I think the majority of problems are due to an overheated GPU or user caused damage when trying to upgrade the CPU.
No one ever uses their GPU anyways.... /s

In other words, that is not a inaccurate blanket statement, its the truth.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.