I doubt OCLP will ever become deterministic….but nice there is a fix for this nasty problem.
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.
macOS 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I Concur !!
In my case, I simply applied the Post Install patches from 1.2.0 nightly, and left the SSD EFI under 1.0.1
(in the interest of being cautious, on this primary Late 2009 iMac 10,1 running Sonoma 14.0)
Photos is yet again working in all its glory. All 33,000+ pictures and 1900 videos, ...and Yes, Pets works too, once you name them.
Yesterday, the new 1.1 stable version of OCLP popped up on my MacBookAir 5,2.
I installed it right away and saw no issues whatsoever. Just a small annoyance. With the previous OCLP 1.0.1, I had dual-boot configuration with Linux using OpenLinuxBoot.efi and ext4_x64.efi, now that is gone. I'll have to do it again.
I installed it right away and saw no issues whatsoever. Just a small annoyance. With the previous OCLP 1.0.1, I had dual-boot configuration with Linux using OpenLinuxBoot.efi and ext4_x64.efi, now that is gone. I'll have to do it again.
Good to know. I was hesitant to take the leap since they had quite a challenge to get the T1 packages working again.
If you read an earlier post by me, I had a slip up when the Ventura was installed it wanted to do the update to Sonoma. Dummy me thinking I'd have the choice to not install it like in the past, I clicked it. Well it took off running and auto installed and broke everything with OCLP 1.0.0.
My Ventura install seems pretty solid so not sure why I need to take any risks. I have a 2016 MacBook Pro 13,3
Yeah, I saw that notification when I downloaded Ventura earlier. Speaking of which, I've got it up and running - and fingers crossed that I enjoy the same positive experiences as yours.
Anyone know how to open the oclp.App from a booted USB installer using Terminal?
Last edited:
Read this to see how to run OCLP in terminal and get command-line help. Look for "Running OpenCore Legacy Patcher."
Thanks.
I would like to request that the oclp.app show up under the Utilities menu in the usb Installer hehe.
this way if you hose your system by patching it wrong you can un-patch it easily.
Cheers!!!
It's a good suggestion. I should have read your initial question more carefully. OCLP needs python which you won't have if you boot a macOS installer and access terminal via the installer menu. I see what you want to do, but I'm not sure you can do it with OCLP. You may need to mount volumes and manually delete files. By the time you figure it out, you could probably have added an APFS volume and installed a new macOS.
Built OCLP 1.2.0n with educovas' non-metal Photos app commit and Photos launches without crashing in Sonoma 14.0 (Release) on MBP6,2.
When I was attempting to build the OCLP-Patcher binary, I kept getting an 'hdiutil: create failed - Resource busy' error that wouldn't go away (even after a reboot). I ran diskutil FirstAid on the Ventura 13.6 Volume (where I'm building OCLP) and that fixed my issue. I don't know if it was actually a disk error or if Disk Utility forced an umount of a resource.
When I was attempting to build the OCLP-Patcher binary, I kept getting an 'hdiutil: create failed - Resource busy' error that wouldn't go away (even after a reboot). I ran diskutil FirstAid on the Ventura 13.6 Volume (where I'm building OCLP) and that fixed my issue. I don't know if it was actually a disk error or if Disk Utility forced an umount of a resource.
I used the 1.2.0 Nightly OCLP and Photos is back working. solved the crash issues. 👍
Thanks, I also had the hdutil message a few times. Related to the dmg creation I think.
Good to know diskutil helps. I re-downloaded OCLP.
Another minor issue is there. When you open Safari, on clicking green full screen button nothing happens and Safari goes into mild hang. if you right click to quit safari from dock icon no action is there. If you click on apple icon on left menu corner there is no action.
Only way to quit safari is open a finder window, then click on apple menu and select force quit.
i wonder if any one else faces this issue. This issue was there from 1.1.0 OCLP.
I am now on Nightly 1.2.0 build of OCLP but this issue is still there. Maybe some bug.
Only way to quit safari is open a finder window, then click on apple menu and select force quit.
i wonder if any one else faces this issue. This issue was there from 1.1.0 OCLP.
I am now on Nightly 1.2.0 build of OCLP but this issue is still there. Maybe some bug.
Yep. Without spoofing the UC controls aren't there. With spoofing all the options are available in the 'Advanced' button in the Displays system prefs. Some of the time it works, other times it doesn't see my iPad, and I can't work out how to figure out what changes.
But it seems that I'm the only person having this issue, because I've searched high and low for an answer and come up with nothing. So that leads me to wondering whether my wireless/BT card is faulty. But if that were the case, then wouldn't my keyboard and trackpad keep disconnecting as well?
Thank OCLP team members, you are great to support the MacOS.
My MacBook Pro 2014, the log screen problem is happening on whatever version on OCLP, now is running 1.2.0 Nigthly.
My MacBook Pro 2017, it work normally, after I update each of version of OCLP, the Continuity Camera seems not function. When I clean reinstall by updated OCLP, then the Continuity Camera came back.
Wish we can let OCLP to perfect patcher on coming version.
My MacBook Pro 2014, the log screen problem is happening on whatever version on OCLP, now is running 1.2.0 Nigthly.
My MacBook Pro 2017, it work normally, after I update each of version of OCLP, the Continuity Camera seems not function. When I clean reinstall by updated OCLP, then the Continuity Camera came back.
Wish we can let OCLP to perfect patcher on coming version.
It is news of OCLP, I saw pop up on new on today. Wish everybody enjoy the OCLP
Continuity camera doesn't work and Photos crashes here too when trying tu use Memories.
MacbookPro 11,5 running 14.0 and OCLP 1.2.0n
Crashed Thread: 9 Dispatch queue: com.apple.photos.metalrenderer-compile
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [2549]
Not seeing this on MBP6,2 with non-metal Nvidia Tesla. This sounds like something very specific to the graphics. Are you seeing this with your HD3000?
Yes, also seeing it here (MBP5,2, 14.1RC, 1.2.0n). Clicking into any non-Safari window or the desktop revives the Apple menu so one can force quit safari.
Hang happens also when just hovering over the green button. Safari isn't very active in activity monitor while hanging (2% CPU).
Full screen mode seems to work though (selected from pulldown menu) as well as reverting it with esc.
Maybe this has to do with the slightly changed behaviour of the green button, in relation to opt/alt.
Also the behaviour of the "show desktop" has changed - e.g. clicking into the desktop enables it. But in my case the windows won't disappear with any "show desktop" click/key.
Last edited:
I have found that especially when going to 1.2.0 one needs to revert firstly and then re-patch. I have a 2012 MacBook 8.1 and battled until I did that - now is stable but very slow. Maybe 8Gb not enough RAM for Sonoma.
So you are seeing on non-metal Nvidia. I haven't tested 14.1 yet. Is this specific to 14.1 (because I'm not seeing it with non-metal Nvidia in 14.0 with OCLP 1.2.0n)?
EDIT: @hvds and @Dilli I am not seeing the Safari issue. I have the following System Settings > Accessibility > Display settings. Do these resolve your issue?
Last edited:
"stable but very slow" sounds like the post-install patches didn't get re-applied. Sonoma 14.0 and Ventura 13.6 have similar performance for me after OCLP 1.2.0n.
EDIT: My Mac has 8GB RAM.
EDIT2: I never need to revert root-patches before applying/upgrading root-patches
Last edited:
You've probably already posted somewhere, but would you mind posting your current OC config.plist and your Wi-Fi card model?
EDIT: Also post the result of 'kextstat | grep -i bluetool'
You should do this with every update. Adding up patches from different versions can have nasty side effects.
Always update, revert, reboot, patch, reboot.