You should do this with every update. Adding up patches from different versions can have nasty side effects.
Always update, revert, reboot, patch, reboot.
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
Always update, revert, reboot, patch, reboot.
Thank you for the suggestion. Should always do it but was too - lazy.
It didn't help though. But on the way, during the unpatches state, these graphics-related things worked as expected. I.e. green Safari button, "show desktop". (of course no internal trackpad/keyboard, no wifi...)
At the risk of opening a can of worms that digresses into a crap-covered death spiral, I never need to revert root-patches before upgrading/applying root-patches.
I (happen to) have the same display settings in accessibility settings.
Didn't try the green Safari button in any Sonoma and OCLP version before today. For the "show desktop" functionality it was already so in 14.0, according to earlier of my posts.
It present I don't have a 14.0 installation for the MBP5,2 but will make one to try the green button.
BTW just running Ventura 13.6 on external SSD, booted with OCLP 1.2.0n, patched with 0.6.9. Green button and show-desktop fine.
Now re-patched this Ventura with 1.2.0n. Green button and show-desktop still fine.
Graphics looks much smoother in Ventura than in Sonoma, but will now install 14.0 over it for tests.
Edit: That is not well quantified and my be just a prejudice.
Last edited:
The patches are certainly applied, the screen resolution is relatively unreadable until application as font is much too small on a smallish hires screen. Whether or not the system has all the required patches that should be necessary is another point altogether though. Will maintain an update of the nightly builds as we go.
Are there any noticeable differences between Sonoma 14.1 Beta (23B5067a) and the RC1 (23B73)?
Hey all, was it here, or on the Ventura thread there were issues with Safari? Just thought I'd ask to make it quicker instead of trying to find the post. Anyway, just tested Safari full screen on a 17,1 iMac Sonoma 14.0, and Open Core 1.1.0, and all seems to be normal. Just providing feedback.
Not that I have noticed. Any amount of changes may have occurred under the covers (in fact that's a certainty) that do not affect the user interfaces that I use and so are not noticeable as such. But you know that right?
In other words, so far as my own use cases are concerned there are no show stoppers. But that doesn't mean you won't have any!
You can click on my spoiler button to see what Macs I'm running the RC on.
Last edited:
I haven't noticed any problem with Safari (my main browser) except with DRM content (video streaming)
But it depends a lot on the hardware (Metal, non-metal, iGPU or dGPU ...)
Just wanted to make sure you read "Stuck on Boot after root patches" in OCLP Issues
Last edited:
As mentioned, I was asking, so whoever it was would call out and respond, or at least get my feedback.
Yes, I usually don’t revert the patch, my list would be slightly different to @Ausdauersportler, I guess i’s ok because after update the patch and the snapshot don’t exist.
update, reboot, re-patch, reboot.
I think we may be confusing update macOS vs. update OCLP. In both cases, I never revert root patches. It's never been a problem for me and I've only read that it's necessary when changing graphics cards (hard to do in my MBP6,2). I've seen others revert root patches before performing migrations (with MA), but I haven't needed to perform MA after a macOS install, because I always perform MA as the last step of a new macOS install (where I've never needed to revert root-patches).
I guess you could say that I'm revert averse.
Hey all, I just found a big problem in Sonoma, but I have no way of knowing if it's related to the patcher or a Sonoma bug specifically. When I open Chess.app, all my audio is gone, and the only way to get it back is rebooting the system.
I did try a suggestion on Reedit where the suggestion was to quit coreaudiod in activity monitor, but it never restarted and still no audio.
Setup, iMac 17,1 Sonoma 14.0, patcher 1.1.0. By the way the suggestion was for someone on an M series Mac with no audio after Sonoma upgrade, which may mean it's not specific to Open core, but they also didn't mention Chess killing the audio. Their's just didn't work at all from the start.
I did try a suggestion on Reedit where the suggestion was to quit coreaudiod in activity monitor, but it never restarted and still no audio.
Setup, iMac 17,1 Sonoma 14.0, patcher 1.1.0. By the way the suggestion was for someone on an M series Mac with no audio after Sonoma upgrade, which may mean it's not specific to Open core, but they also didn't mention Chess killing the audio. Their's just didn't work at all from the start.
Hi, Just tested on my iMac 13,2 running 14.1 RC and OCLP 1.2.0 nightly and no problems with system sound after using the Chess app. Had to download the Chess speech package but that was it.
@deeveedee
I was talking about macOS updates. Thinking of OCLP updates, I reverted patches before update when it was so advised, not sure if it was updating to 0.6.8 due to a change in the patching process.
Maybe reverting the patch and reapplying again is a good practice, I don’t know if OCLP creates a new snapshot or deletes first the current active.
As you, I only do MA as last step of a macOS install.
I was talking about macOS updates. Thinking of OCLP updates, I reverted patches before update when it was so advised, not sure if it was updating to 0.6.8 due to a change in the patching process.
Maybe reverting the patch and reapplying again is a good practice, I don’t know if OCLP creates a new snapshot or deletes first the current active.
As you, I only do MA as last step of a macOS install.
The problem seemed to go away after i selected "Start Dictation" after chess app was opened. What seems to happen is once Chess was opened, all system sounds including feedback from the volume up / down was gone. So, I waited a few minutes then clicked on start dictation and sound was back, so not sure If I was quitting chess too soon, or what.
There's a pretty simple way to prevent any MacOS Updates from showing up via Software Update by edited the config.plist on the EFI drive. You will still get Safari and other updates, just not be bothered by the constant nagging to update to Sonoma. As a bonus, when or if you are ready to install some updates, just a quick re-install (or even a single boot to an unmodified OCLP USB Drive) of OCLP will bring it all back. I can't stand the red notification on the Settings Pane telling me there is a software update, so I really just do this for my sanity.
At the risk of being OT
oops, According to Google, "adverse and averse are both turn-offs, but adverse is something harmful, and averse is a strong feeling of dislike. Rainstorms can cause adverse conditions, and many people are averse to rain. If it's a force of nature working against you, use adverse."Now, is the fact that we have to reboot after every OCLP considered "a force of nature"?
In any case, I find I dislike rebooting very aversely.
Apple released macOS 14.1 (23B74)
Last edited:
I suspect that "always revert root-patches" is good advice when providing advice for an app like OCLP that customizes its operations for each Mac Model (and thus applies different post-install patches depending on the Mac Model). I recall Devs including 'revert root-patches' in the upgrade instructions for previous OCLP versions, and even in those cases, I didn't revert. It's quite possible that, because my Nvidia Tesla patches are so mature and are derived from patches first implemented with DosDude, that there isn't enough change (if any) to warrant reverting the patches.
OCLP behaves differently for different Mac Models. Each of us needs to adapt our processes and procedures based on what works for our Mac and our use cases.
Last edited:
Just curious, why hasn't this thread been stickied like all the other "unsupported" threads on other iterations?
Yes. I can manage using the steps @hvds mentioned but issue persists. I checked the settings you posted in your screenshot. My settings are similar but perhaps it may be due to non metal legacy card and poor ram of 4gb max that my machine has. ✌️
Also now that I am on Sanoma 14.0 I dont want to reinstall and go all the way. Maybe after updating to 14.1 after a while things may improve. 😀
Last edited:
Updated my MBA 7,2 (Early 2015) on 14.0 from OCLP 1.1.0 to 1.2.0n (2023-10-24T14:11:26-03:00) and my Photos no longer sits there telling me my "Mac Needs to Cool Down" and is syncing all of my photos/videos from iCloud. Fingers crossed this new library will also bring back People/Duplicates detection that has been broken for me since Ventura.