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
With the latest OCLP 1.5.0 commits (as of this post), non-metal is still not working in 14.4.
For those who are stubborn like me, who refuse to follow directions and must test Sonoma 14.4 on their non-metal Macs (despite all the warnings), you'll need to revert root patches after a failed 14.4 test. Do your 14.4 testing in a separate APFS volume that you can afford to lose. Set a temporary root password for your testing and save the root password in an easily accessible text file. If you boot 14.4 and experience the login window crash, you may lose keyboard entry and thus won't be able to enter your root password to revert root patches with OCLP. As a work-around, copy your temporary root password from the text file and paste it into the OCLP root password dialog.
Java users on macOS 14 running on Apple silicon systems should skip macOS 14.4 and update directly to macOS 14.4.1
Java users on macOS 14 running on Apple silicon systems should consider delaying the macOS 14.4 update
EDIT: This might only apply to Apple Silicon machines and then wouldn't have any impact to OCLP users.
Last edited:
What does this have to do with macOS 14.4 and OCLP? 🤷♂️
Java users on macOS 14 running on Apple silicon systems should skip macOS 14.4 and update directly to macOS 14.4.1
Java users on macOS 14 running on Apple silicon systems should consider delaying the macOS 14.4 updateblogs.oracle.com
He was just trying to make us unsupported folks who are stuck on 14.3.1 feel better about our predicament
MacBook Pro 5,2 (no metal GPU)
I installed OCLP 1.5n (OC now 0.99) onto the internal SSD, and rebooted into a unique volume where 14.4 RC already resided (installed from another volume). I was actually able to log into the system using an external USB keyboard and mouse, both routed via hub plugged into USB port on the machine. The desktop was a blank screen until I reset NVRAM, thereafter machine booted into the true desktop, and there were actually items present in the menu bar. Launched OCLP 1.5n and was still able to enter password to apply patches. I had Ethernet plugged in and OCLP did download latest KDK before fully completing the patching process. Rebooted, and logged in, got to desktop, just to be automatically logged out. I kept re-logging, and with each re-login I was able to access more items on the desktop. In the end, while there was no menu bar, machine no longer looped, and graphics were fully (?) accelerated. Internal trackpad and keyboard were fully functional, including backlight. Applications could be launched from (fully functional) dock using the mouse. Some documents associated with applications could also be accessed. MacBook Pro can go to sleep and “wake-up” without issues.
Launched system settings from the dock, and selected update to 14.4, the formal release (via OTA).
OS 14.4 installed without problems,; keyboard and mouse were still functional, and after couple of login loops (and re-logging) I was able to reach desktop.
Again, there was no menu bar, and I was no longer able to reapply patches due to loss of focus (can't type into specific field to apply root password). However, graphics were still fully accelerated, trackpad works as well. Keyboard is backlit, and pressing key elicits sound, implying the keyboard is active, but there is “no focus” as to where to send signal. Implication here is (?) that whatever changes were instituted with final release, did not directly affect patched graphic system items, and, there is a reasonable hope that non-metal machine may be able to function.
In conclusion, only two (visible) items remained to be "enhanced" by the great OCLP team: menu bar and focus (both issues were already reported by other posters).
iMac 13,2 (metal capable machine) runs incredibly well on OCLP 1.5n, and as previously reported, time from startup to login screen is greatly reduced.
I can connect to MacBook Pro 5,2 from iMac 13,2 and transfer files, so basic connectivity is also functional.
Great work by OC and OCLP teams.
Hope this may help.
I installed OCLP 1.5n (OC now 0.99) onto the internal SSD, and rebooted into a unique volume where 14.4 RC already resided (installed from another volume). I was actually able to log into the system using an external USB keyboard and mouse, both routed via hub plugged into USB port on the machine. The desktop was a blank screen until I reset NVRAM, thereafter machine booted into the true desktop, and there were actually items present in the menu bar. Launched OCLP 1.5n and was still able to enter password to apply patches. I had Ethernet plugged in and OCLP did download latest KDK before fully completing the patching process. Rebooted, and logged in, got to desktop, just to be automatically logged out. I kept re-logging, and with each re-login I was able to access more items on the desktop. In the end, while there was no menu bar, machine no longer looped, and graphics were fully (?) accelerated. Internal trackpad and keyboard were fully functional, including backlight. Applications could be launched from (fully functional) dock using the mouse. Some documents associated with applications could also be accessed. MacBook Pro can go to sleep and “wake-up” without issues.
Launched system settings from the dock, and selected update to 14.4, the formal release (via OTA).
OS 14.4 installed without problems,; keyboard and mouse were still functional, and after couple of login loops (and re-logging) I was able to reach desktop.
Again, there was no menu bar, and I was no longer able to reapply patches due to loss of focus (can't type into specific field to apply root password). However, graphics were still fully accelerated, trackpad works as well. Keyboard is backlit, and pressing key elicits sound, implying the keyboard is active, but there is “no focus” as to where to send signal. Implication here is (?) that whatever changes were instituted with final release, did not directly affect patched graphic system items, and, there is a reasonable hope that non-metal machine may be able to function.
In conclusion, only two (visible) items remained to be "enhanced" by the great OCLP team: menu bar and focus (both issues were already reported by other posters).
iMac 13,2 (metal capable machine) runs incredibly well on OCLP 1.5n, and as previously reported, time from startup to login screen is greatly reduced.
I can connect to MacBook Pro 5,2 from iMac 13,2 and transfer files, so basic connectivity is also functional.
Great work by OC and OCLP teams.
Hope this may help.
Last edited:
I thought it'd be useful if people are running into issues with OCLP and 14.4 since these issues with protected memory access may affect other applications.
Non-metal support for 14.4 has been added to OCLP 1.5.0n.
EDIT: ... which now appears to be 1.4.3n?
EDIT: ... which now appears to be 1.4.3n?
New fixes in the current Nightly -
1.4.3
- Update non-Metal Binaries for macOS Sonoma:
- Resolve TeraScale 2 screen recording kernel panic
- Resolve Dock location after changing screen resolution
- Resolve 14.4 loginwindow crashes 👏
- Update PatcherSupportPkg to #1.4.9
Last edited:
Seems more good things are on the horizon:
(still in development, so please don’t ask where to get it right now)
EDIT: Sorry, haven’t seen this was already posted.
(still in development, so please don’t ask where to get it right now)
EDIT: Sorry, haven’t seen this was already posted.
Last edited:
Latest OCLP 1.4.3n (with Commit bbc8902) has fixed Login Window crash on my Mac with non-metal Nvidia Tesla. Well done Devs. Still testing, but Sonoma 14.4 appears to be working well.
So, in terms of trying OCLP again what version should I wait for in the nightlies to become final? I have 1.4.2 installed, however i keep hearing good things about the 1.5 branch so should I wait for that over 1.4.3, before doing the install again? I'd like to have the most amount of fixes / improvements on the main install first before having to update again.
OK, wasn't sure i thought maybe the 1.4.3 coming was an emergency fix maybe while 1.5 was being worked onThe v.1.5.0n changes are in v.1.4.3n.
So the managers just decided the 1.4.3(n) name was more appropriate than 1.5.0(n) for some reason?
Easy to confirm by going back through the recent commits to see what has been updated. 🤷♂️
The issues currently being reported as problems on Supported Macs with macOS v.14.4 are predominantly being seen on Apple Silicon Macs. 
Well, as you know I did Sonoma 14.3 / 14.3.1 on my iMac 17,1 for a couple weeks and overall I was satisfied with using it as a daily driver. Sure, there are things that would work better in a supported OS but I can keep an external install for that since it's minimal. I am really just waiting for Sonoma to be as polished as possible before fully trusting it long term. So that's why I am just watching the update status as people try the new version of the patcher as they come out. I had tried Ventura on here too and that is a bit more polished but Apple tried to force a Sonoma update and I didn't ask for it or even click something as others have mentioned to initiate it. So i figured I would wait for Sonoma to be in a place of being solid to just go to it without having to worry about forced upgrades.The issues currently being reported as problems on Supported Macs with macOS v.14.4 are predominantly being seen on Apple Silicon Macs.
why don't you mention the specs of your machine. Putting them into your signature is good common practice in this thread.
I'm finally sitting down to respond to comments here. As far as me repeating myself The main reason I reverted to Monterey was in the event I had to call Apple regarding the phantom device situation I just needed to be sure to have a supported OS installed. There were some other questions I had about compatibility which I wasn't sure if they were OCLP related, or strictly Sonoma related. After looking things up and testing things in a Sonoma VM running on top of Monterey. I feel it's pretty safe to continue with OCLP. I've mainly just been watching the thread regarding 14.4 and the OCLP updates. What I have taken away most of the remaining issues that remain are pre-metal macs.
There was one issue I was having with chrome under Sonoma that doesn't seem to exist with Monerey but I don't know if it's OCLP related or not. That is with text to speech, whenever I'd hit option+esc to have text read in Chrome it would always stop speaking within a few seconds regardless if all the text was read or not. Using the text to speech function with Firefox, or Safari works fine under Sonoma, it was just chrome, so if anyone here with a patched mac that needs accessability features could comment would appreciate it. Thanks.
There was one issue I was having with chrome under Sonoma that doesn't seem to exist with Monerey but I don't know if it's OCLP related or not. That is with text to speech, whenever I'd hit option+esc to have text read in Chrome it would always stop speaking within a few seconds regardless if all the text was read or not. Using the text to speech function with Firefox, or Safari works fine under Sonoma, it was just chrome, so if anyone here with a patched mac that needs accessability features could comment would appreciate it. Thanks.
Also here, OCLP 1.4.3n going well with Sonoma 14.4:
MBP5,2 (non-Metal): EFI and post-install patched with new OCLP. 14.4 was already installed. Proper KDK loaded during post-install patching.
I had my usual difficulties with getting the external USB hub with keyboard/mouse to respond but it worked eventually.
Internal (and external) keyboard/trackpad work fine after patching, as does wifi etc. Fast graphics response.
MBP11,1 (Haswell) my workhorse: EFI and post-install patched now also with new OCLP. On external SSD for now, internal has 14.4 still with OCLP 1.4.2 release.
Wonderful achievement by the developers. Thank you!
Last edited:
Apparently Edu Covas has updated 8h ago the OCLP changelog and a 1.4.3 (instead of 1.5.0) version with non-metal issues solved is coming out of the oven...