Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Please read OCLP docs about updates and please look up software release management (or ITIL)

You can - of course - ignore what has been developed in half a century or you can evolve and learn something new.

Leaning back and expecting others would deliver a software which makes thinking obsolete is really frightening to me.

I give you all a break - this is my last post here.
So reactionary. Considering your expertise in this field, we all lose, no winners here today.
 
Please read OCLP docs about updates and please look up software release management (or ITIL)

You can - of course - ignore what has been developed in half a century or you can evolve and learn something new.

Leaning back and expecting others would deliver a software which makes thinking obsolete is really frightening to me.

I give you all a break - this is my last post here.
Hey, man! you’re talking to some kindred spirits here! Some of us do read the OCLP docs. It is also okay to recognize that OCLP is a fluid project, and the docs change from time to time, as does the first post in this thread occasionally.

“give them a break” is not such a harsh thing to say or write. Not everybody here has as much experience with OCLP / computers, compared with you or me. I think everybody appreciates your insightful posts here… everybody’s here to learn something new also, that’s why so many people like your posts.
Don’t run away from here, we’ll will miss you too much if you do. 😉
 
Hopefully not their last post. I get the frustration with spending hours developing / debugging only to have people test unsupported modes and then complain about it not working (or worse, begging to have their critical data saved). As long as we're performing our experiments at our own risk and sharing our results for the benefit of others (without complaining and without asking to be saved from our mistakes), nothing wrong with that as far as I'm concerned.
 
I've used OCLP on a few Macs, so I know my way around it.

However, I recently got a new Mac Pro 5,1 and the BootROM has been flashed to 144.0.0.0.0. However, I'm still waiting until next week for my power cables to come in so I can use a Metal-capable GPU.

Can I try OCLP with my non-Metal HD 5770? I realize it won't be GPU-accelerated, but can I at least try the installation?
Quoting myself but just checking back in with an update.

OCLP works just fine with the original HD 5770! Yes, there were no graphics acceleration until I did the patch, but it works very well for normal desktop use.

My last hurdle is to see if when I swap in my 5700XT, it display video output well enough for me to rebuilt the patcher for graphics support.
 
  • Like
Reactions: Insidious
My last hurdle is to see if when I swap in my 5700XT, it display video output well enough for me to rebuilt the patcher for graphics support.
Not sure if this post applies to you. @jgleigh may have more to say about this. Maybe the issue is only a Ventura issue? Not sure. Even if just a Ventura issue, it's probably something to be aware of in case you plan to upgrade to Ventura from Monterey.
 
Last edited:
Buenas, estoy tratando de instalar Monterey en una MacBookPro8,2 y me da problemas después en el Post-Install Root Patch, ya la pc se reinicializa y se queda colgada en el proceso de reinicio. La tarjeta gráfica es AMD Radeon HD 6750M, 1024 MB, habría alguna solución para este problema, sobre todo en los kest.

He hecho el mismo proceso ya con el nuevo Open-Core-Patcher 0.6.6 y me da el mismo error. Me vendría bien una ayuda en este aspecto, Gracias.

Hi, I'm trying to install Monterey on a MacBookPro8,2 and it gives me problems after the Post-Install Root Patch, and the pc reboots and hangs in the reboot process. The graphics card is AMD Radeon HD 6750M, 1024 MB, there would be some solution for this problem, especially in the kest.

I have done the same process already with the new Open-Core-Patcher 0.6.6 and it gives me the same error. I could use some help in this regard, Thanks.
 
Such terrible performance on the latest update Safari 16.(seed 1) that it is most unusable. It took about 5 mins to write this post.
 
  • Wow
Reactions: Insidious
You applied OCLP post-install patches after updating Safari?

I did as far as I recall, but funnily enough a few minutes after posting that post a thought struck me to run the patches again just in case, and today things feel much smoother. I forgot I ran the patch today until I read your post! So what does that tell you! Ha ha...

Perhaps I only ran the patch on the OS level update and not realising I need to run it for Safari and maybe other updates too that come through Apples update system. Lesson learned and now I can stop drooling over a M2 Mac mini for now. ;)
 
Last edited:
  • Like
Reactions: deeveedee
Not sure if this post applies to you. @jgleigh may have more to say about this. Maybe the issue is only a Ventura issue? Not sure. Even if just a Ventura issue, it's probably something to be aware of in case you plan to upgrade to Ventura from Monterey.

@BeatCrazy 5700XT works fine in Monterey, but doesn't work in Ventura. You can see my setup in my signature.

No root patches required afaik.

Got it working! Even connected to my Pro Display XDR, but only at 5K?

@joevt shouldn't a 5700XT + Belkin Huawei VR cable work at 6K with the Pro Display XDR? See attached, on the System Info Displays screen I'm only showing 5120x2880.

Display.jpeg
System.jpeg
 
  • Like
Reactions: deeveedee
Got it working! Even connected to my Pro Display XDR, but only at 5K?

@joevt shouldn't a 5700XT + Belkin Huawei VR cable work at 6K with the Pro Display XDR? See attached, on the System Info Displays screen I'm only showing 5120x2880.
I don't think macOS shows the output resolution. Use SwitchResX, double click the selected Current Resolution to view the timing info. It should say pixel clock 1286 MHz and active pixels 6016x3384.
 
I don't think macOS shows the output resolution. Use SwitchResX, double click the selected Current Resolution to view the timing info. It should say pixel clock 1286 MHz and active pixels 6016x3384.
Looks like I'm good-to-go. Thanks for the tip.

Amazing this old girl can run Monterey and push an XDR. Way to go OCLP team!!
Screen Shot 2023-05-29 at 9.16.38 PM.png
 
  • Like
Reactions: TimmuJapan
Please read OCLP docs about updates and please look up software release management (or ITIL)

You can - of course - ignore what has been developed in half a century or you can evolve and learn something new.

Leaning back and expecting others would deliver a software which makes thinking obsolete is really frightening to me.

I give you all a break - this is my last post here.
Don’t do this! Your experience and insights are at the core of this forum! Many of us are here to learn!
 
  • Like
Reactions: K two
Don’t do this! Your experience and insights are at the core of this forum! Many of us are here to learn!
I agree, I hope that he doesn’t go. But I do want to point out that there are other brilliant users in these forums, for example dosdude1, and every post that I have ever seen of his is fair, kind, and respectful. He’s clearly a genius who has given back to society with his work. Other users here(including myself) have a pinprick of knowledge compared to Dosdude1. But despite his knowledge and ability, he treats us “muggles” with integrity and respect in his dealings here.
When brilliant people write public or private posts that have strong undertones of “you are all idiots,” it really makes for sour grapes. Google “lemmings metaphor”.

Food for thought.
 
Last edited:
Hello,

Have a MacPro 5,1 (bootrom 144.0.0.0.0) with a clean Mojave install nicely booting from an M.2 NVMe SSD on a PCIe card. Proceeded to install latest OCLP 0.6.7 and "blessed" the EFI of a USB installer with Monterey 12.6.6.

Now, upon boot, I select "EFI" and then "Install MacOS Monterey" from the USB, but then get a circle with a line thought it on a black screen and nothing else.

For reference Monterey installer was downloaded by OCLP 0.6.7 itself, but it failed to create a bootable USB (maybe a bug), so I used the "sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --nointeraction" command to create the bootable USB (which completed successfully and without error) and then installed OCLP on it's EFI partition.

Any ideas why OCLP 0.6.7 is not allowing the Monterey 12.6.6 bootable USB installer to even start?
 
Last edited:
Hello,

Have a MacPro 5,1 (bootrom 144.0.0.0.0) with a clean Mojave install on a wiped M.2 NVMe SSD on a PCIe card. Proceeded to install latest OCLP 0.6.7 and "blessed" the EFI of a USB installer with Monterey 12.6.6.

Now, upon boot, I select "EFI" and then "Install MacOS Monterey" from the USB, but then get a circle with a line thought it on a black screen and nothing else.

For reference Monterey installer was downloaded by OCLP 0.6.7 itself, but it failed to create a bootable USB (maybe a bug), so I used the "sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --nointeraction" command to create the bootable USB (which completed successfully and without error) and then installed OCLP on it's EFI partition.

Any ideas why OCLP 0.6.7 is not allowing the Monterey 12.6.6 bootable USB installer to even start?
if you want to boot monterey or older os's, you should try oclp 0.4.11 and all will work as you planned
 
if you want to boot monterey or older os's, you should try oclp 0.4.11 and all will work as you planned
Brilliant! Thank you!

I was able to get the USB to boot and install Monterey on top of Mojave by "downgrading" and using the older OCLP 0.4.11 !!!!

Only other thing I had to do is the root patching for the legacy WiFi and reboot to a fully functional Mac Pro 5,1 running Monterey 12.6.6

$1M question is why does OCLP 0.4.11 work and 0.6.7 fails???
 
Last edited:
  • Like
Reactions: Omega Mac
Brilliant! Thank you! I was able to get the USB to boot and install Monterey on top of Mojave using OCLP 0.4.11 !!!!

$1M question is why does 0.4.11 work and 0.6.7 fails???
Because later versions try to get Ventura running. Since multi boot environments require the EFI boot can cope with different OSes, OCLP can't automatically build and install the perfect match for you.
 
Because later versions try to get Ventura running. Since multi boot environments require the EFI boot can cope with different OSes, OCLP can't automatically build and install the perfect match for you.
I see, but then it's strange that OCLP did not just spin off a separate version tree if they abandoned Monterey in favor of Ventura. Like have an "M" series, a "V" series, etc... With the release of macOS 14 Sonoma, it would be nice to know at which build version Ventura support will stop and Sonoma support will start. As of now it does not seem obvious to anyone that installing the latest version will actually not work with Monterey, and I failed to see any mention of this anywhere in the docs...

Also, I updated to OCLP 0.6.7 on my other MacPro 5,1 and installed 12.6.6 from 12.6.5 and had no issues... So it seems only initial instals fail... seems very sketchy...
 
Last edited:
Because later versions try to get Ventura running. Since multi boot environments require the EFI boot can cope with different OSes, OCLP can't automatically build and install the perfect match for you.
But there's no harm in using newer versions of OCLP, right? I have a Mac Pro 5,1 and iMac 11,1 that seem to being doing fine with OCLP 0.6.7. I like the GUI improvements the OCLP team has made over the past few releases.
 
But there's no harm in using newer versions of OCLP, right? I have a Mac Pro 5,1 and iMac 11,1 that seem to being doing fine with OCLP 0.6.7. I like the GUI improvements the OCLP team has made over the past few releases.
That was my point as well. The interface and options (including updates process) have greatly improved, but support for “older” OS’s like Monterey almost dropped in favor of Ventura, and soon to be Sonoma, without clear feedback. Since OCLP can detect and patch for the specific Mac model hardware, why does it allow / promote the creation of a bootable USB installer of a version of MacOS it no longer fully supports and ends up failing to boot?
 
Today I installed Open Core on my Mac Pro 4,1>5,1 using the OCLP. Installed Monterey. All went well and it works really really well and I couldn't be happier. For some reason Monterey performs much better than Mojave (which is why I went back to High Sierra a while ago). However, I was away for an hour and came back and couldn't wake the Mac from sleep. In the end I just pulled the plug and rebooted.

Anything I can do to fix this? Aside from changing the obvious settings in System Preferences to never let the Mac go to sleep, which is not a good option. It's nice if the Mac can go to sleep when not in use.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.