… Another glitch, which sometimes happens: many apps - especially the “heavy” ones - suddenly won’t launch anymore, after bouncing in the Dock for some seconds; and this can usually be fixed by issuing a sudo purge in the Terminal: so, probably, memory-related (BTW, Howard of The Eclectic Light Company has often said that the Finder has a memory leak in Sonoma, but I don’t know if this glitch can be related to that).
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
My MacBook Pro 2014 is clean install to 14.2 and using 1.3, but the login error still happened, it cause stop all application when screen lock start.
Afterwards the error popup window will show.
Afterwards the error popup window will show.
What about photo app? memmories crash the app on my both haswell Imac 14,1 and MM 7,1 with 14,2.macOS 14.3 Dev. Beta OTA, OCLP v.1.3.0 - installed atop 14.2 with no drama, runs as expected.
View attachment 2324235
Try switching between discrete graphics or integrated one. Memories will work but only on discrete graphics for me if that’s a option.
As I don't do updates via OTA I wasn't aware of the new OCLP feature to download the KDKs automatically when needed. Just learned this from Mr. Macintosh's today's new video which contains plenty of useful information for OCLP 1.3.0
Never heard that it's necessary to revert and thus always overwrote...
Sorry, but your answer is a bit confusing, bro. First of all it's not clear to what the "No" refers to. To the first part of the question or the second? And your second sentence refers to the MacOS update in a different context and does not really answer the original question either...
You should read the change log of the OCLP development and never give advices based on rumors you have never heard of.
You might end up with patches from different generations of OCLP messing up your installation. When you update OpenCore and immediately update your system with a new version of macOS you would not need to revert patches since patches are overwritten by a new macOS version.
Hi K two, I had no idea what OpenCanopy was, and I'm sure I'm not alone in this. You mention it regularly. So I did a search, and found that it's part of the main OpenCore package (i.e. not OCLP per se). So are you saying OpenCanopy is installed by OCLP to perform the boot picking process?
"...based on rumors I have never heard of..."? This somehow sounds impossible to me
...I'm not sure I got your message correctly. I expressively did not give any advice cause I simply don't have sufficient background information about the processes. I just repeat that I never read or heard in any of the forums or tutorials that patches need to be reverted before installing updates i.e. latest patches. And since I never ran into issues after installing the latest patches over the previous ones, I just confirmed that I always overwote successfully... vielleicht nur ein Mißverständnis... 
When booting OCLP OpenCanopy is what is seen, applying the Space bar offers more options like reset NVRAM.
When booting OCLP OpenCanopy is what is seen, applying the Space bar offers more options like reset NVRAM.
Got it, thanks. For those of us not at all familiar with the original OpenCore (not OCLP which most of us know fairly well by now), here's a link to some documentation. It seems to have been built for the Hackintosh community originally and presumably picked up by the devs for OCLP use.
OpenCanopy
A GitHub Pages hosted website that mirrors OpenCorePkg Configuration.pdf
dreamwhite.github.io
Apple Hardware I support:
MacBook Pro 12,1;
successfully updated to Sonoma v14.2 (23C64) using OCLP 1.3.0 public release.
Just patience was needed (took several hours) and the post install patches applied, after slow, wonky, login.
iMac 10,1;
successfully updated to Sonoma v14.2 (23C64) using OCLP 1.3.0 public release.
Smooth update, done relatively quickly as compared to the above MacBook Pro, and the post install patches applied, after login.
MacBook Pro 12,1;
successfully updated to Sonoma v14.2 (23C64) using OCLP 1.3.0 public release.
Just patience was needed (took several hours) and the post install patches applied, after slow, wonky, login.
iMac 10,1;
successfully updated to Sonoma v14.2 (23C64) using OCLP 1.3.0 public release.
Smooth update, done relatively quickly as compared to the above MacBook Pro, and the post install patches applied, after login.
Just Installed somona 14.2 on a new partion using oclp 1.3.0 but when it gats to the login screen I just get not full size grey screen.If I boot into safe mode I get grey screen with lots of vertical black lines
I have a 5.1 gtx680 ventura is working fine
any help please thanks
I have a 5.1 gtx680 ventura is working fine
any help please thanks
Last edited:
The move from pre 0.6.8 to post 0.6.7 made the revert-patching process necessary and today still a lot of people might be caught by surprise. So I always recommend on any Monterey+ macOS version (Big Sur does not allow to revert patches because the original snapshot is dropped after a short while) to revert patches before patching again."...based on rumors I have never heard of..."? This somehow sounds impossible to me
Just never seeing a problem is not really enough evidence. Even if you never encounter in future such a problem after ignoring the revert process. There are problems documented and I just pointed out where to find the docs.
P.S.:
I have never seen any object in the Kuiper Belt with my own eyes and there are millions around. Some were called planets for a short time.
P.P.S:
Revert patches as in revert patches.
Last edited:
@Sven G I know you also use VMware Fusion, and Parallels Desktop. Have you gotten 3D acceleration to work under an OCLP patched system yet? Ventura, or Sonoma? That's been my hangup for embracing OCLP right now. I need 3D acceleration to work in VM's especially windows because I have some old 32 bit Games that won't run on the 64-bit only systems. So, putting them in a windows VM is the solution for sticking with the current macOS. Running macOS Mojave, is the mac native solution without needing a VM, but that means going back even older unsupported versions to fix the issue. Right now I can use VMs on natively supported Monterey, but it's what to do after that I'm still looking into. Getting a new Mac is an option, but I'm not sure the Apple Silicon macs could run 32-bit x86 code, even in a VM.
So, trying to find the best solution for my intel iMac 27" late 2015.
So, trying to find the best solution for my intel iMac 27" late 2015.
It seems with reverting we both meant a different thing from the beginning. I understood the original question in a way whether the old patches should be deleted (reverted) first before installing a new version of OCLP and the new patches. From your last message I now understand that you talk about a downgrade. So we were talking about two different things obviously which also explains why I did not really understand your first comments.
3D acceleration works fine on my machine (MBP11,3, with Intel iGPU and Nvidia dGPU) for Windows and Linux VMs, both in Fusion and Parallels; while it hasn’t worked anymore since upgrading to Sonoma for macOS VMs (paravirtualization). But this might also depend on the specific machine: for example, I don’t know how it is for AMD GPUs…
Right. Adding to your last sentence, kexts in /Library/Extensions are not removed while installing a new macOS version. They seem to be essential in KDK-less patching (as for my MBP11,1).
They get removed by reverting root patches (or by removing them manually), and are put there while root patching.
Even if they are the correct versions, they may not harmonize with the not-yet-patched system (as in my case).
The solution is simple: if there is a boot loop or login loop after installing new macOS (caused by WindowServer crashing), boot in safe mode then apply the root patches, and all fine. See my previous post #4,147 .
Sorry for the longish explanation of my special case - and correct me if this is the wrong interpretation.
Last edited:
MacBook Pro 11,4 15" mid-2015 flawless update via settings....went rather quickly and running smoothly. Fans ran a bit more than typically have in past updates but has settled down now.
Not 100% sure, but there has been code added to get rid of the additional extensions. Since I do not own a single KDK less patched system I am kind of blind on this eye. At least command line arguments are there.
Take a look at the current changelog.md on the Github page (referring to 1.2.0)
- Add new arguments:
- --cache_os: Cache necessary patcher files for OS to be installed (ex. KDKs)
- --prepare_for_update: Clean up patcher files for OS to be installed (ex. /Library/Extensions)