Thanks for the replies and advice. So when 14.6 comes out in a few weeks (or whenever it releases) I should just hold for awhile until I'm certain it's fully functional? And the patcher will automatically detect and ask to reinstall root patches as per comment before yours?
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
Thanks for the replies and advice. So when 14.6 comes out in a few weeks (or whenever it releases) I should just hold for awhile until I'm certain it's fully functional? And the patcher will automatically detect and ask to reinstall root patches as per comment before yours?
Just made the leap. Been on OCLP 1.3 and Ventura for a year or more and when they cleared 14,2 imacs for Sonoma 14.5 with OCLP 1.5, I decided to do it!
Backed up twice, installed over the Ventura installation. I do so little, but this iMac keeps going and going!
Thanks, developers!
Sleep is OK and so is running a 30" Cinema display under dual mode.
Life is good.
Yes I would always give it a few days just in case , Yes OCLP will ask to reinstall patches after a update just with Apple software updates OCLP may need minor/major tweaks to support it .
Question to the OC experts:
Is there any way to disable certain cores or a complete processor (i.e. in the OC setup) before booting further into any OS ?
This would come very handy in investigating things further on this side of cMP life.
(Spoiler: New signs of progress for getting Xeons with SSE4.1 running in cMP1,1 / 2,1)
Is there any way to disable certain cores or a complete processor (i.e. in the OC setup) before booting further into any OS ?
This would come very handy in investigating things further on this side of cMP life.
(Spoiler: New signs of progress for getting Xeons with SSE4.1 running in cMP1,1 / 2,1)
Last edited:
This post clearly don´t belong here, excuse me. But maybe some of yuo have experienced this.
From time to time, sice 15 years ago, I make a clean isntall and then use Migration Assistant to import myb account. This cleans the system a lot.
Today , for the first time, has failed. Both drives contain exactly the same macOS version.
ODD.
From time to time, sice 15 years ago, I make a clean isntall and then use Migration Assistant to import myb account. This cleans the system a lot.
Today , for the first time, has failed. Both drives contain exactly the same macOS version.
ODD.
You're more of an expert on migration than I am, so I hesitate to ask...
- Do you have OCLP post-install patches installed on the destination macOS?
- I don't read your language, but it appears that you are attempting to migrate from Time Machine backup - is that correct? If so, did you attempt to migrate directly from the other macOS volume instead?
Apple seeded macOS 14.6 Beta 3 (23G5066c) to developers
Around 900 mb for Sonoma 14.6 beta 3 after reverting patches on mid 2014 MacBook Pro again no issues to report on updating and patching again. Who else is hoping the M1 gets dropped from support around the same time as intel ? or the year after , if OCLP keeps going as long as the first M1 chip I think that would be impressive if not longer (anything is possible).
macOS 14.6b3 installed atop b2 OTA, OCLP v1.6n, runs as expected.
👏
👏
Last edited:
rMBP10,1 2012 updated from beta 2 to Sonoma beta 3 OTA successfully, OCLP nightly on board, auto-prompted to reinstall root patches.
I do not normally speak of issues, only gratitude to the Dev's, but wondering if anyone has had an issue with patching since ota 23G5066c?
I do not see the related kdk for this. MBP14,1 did not have an issues with the patching but the MacPro6,1 does.
I do not see an actual download for kdk14,6 23G5066c on GitHub or apples dev site.
I do not see the related kdk for this. MBP14,1 did not have an issues with the patching but the MacPro6,1 does.
I do not see an actual download for kdk14,6 23G5066c on GitHub or apples dev site.
Yeah simply rename current KDK to 23G5066c and patch to avoid that KDK for macOS 15 will be loaded! Works like a charm on my test MacPro 5,1 ;-)
(Rename both .pkg and .kdk folder in /Developer/KDK to avoid the wrong download)
by the way... are you renaming 23G5061 or 24A5279? going slowly but renamed 23G
Great to hear from you, I've also the upgraded to b3 on my 2015 macbook air and it's running as expected also. I would have a question to you though: since 1.6n compiling the OCLP app would crash on a mounting permission error due to a incorrect team id. After some digging in the code tree, I've found that if compiling from source I need to hqve the priviledged helper compile with make debug as stated in the readme of the directory. Are you also doing the same, using your apple team idon xcode or are you using some binary from elsewhere ?
Thanks for answering. When I said "don´t belong here" it´s because its a native supported mac, no OCLP. It´s the first time that Migration Assistant fails me in 15 years.
Hey all, I was playing around with the SIP settings in OCLP. I found that turning it fully on breaks booting, leaving it at the defaults, or turning it completely off seems to work fine. Since supported configurations support with SIP completely off, will turning it completely off in the OCLP settings still give a reliable system, or will it also break things?
Thanks
If I don't need it at all, i'd much rather just turn it off. I usually just leave it on for a supported OS, unless I need system access, but since OCLP already modifies it for patching, is it safe to just disable it all together
Thanks
If I don't need it at all, i'd much rather just turn it off. I usually just leave it on for a supported OS, unless I need system access, but since OCLP already modifies it for patching, is it safe to just disable it all together
Since version 1.0, I disable all,m except Apple Internals. Never had a problem.
So an update for iMac 14,2 27" late 2013 owners with stock configs except the HDDs:
The attached 30" Cinema Display shows occasional graphical glitches when scrolling in safari. After a sleep, the display powered up in 1280x800 mode. It's done this before under Monterey and Ventura, so it's just Apple display recognition and the plethora of adapters to make it work with the iMac.
Otherwise, it seems stable.
Thanks, when I got back to OCLP, I'll remember that. Put Monterey back for now, not because I was having issues, just want to be sure I get the latest EFI updates before support ends. Actually this past run with OCLP 1.5 and Sonoma 14.5 was very reliable with the few apps I use that have issues with Sonoma (as a whole) not oclp
Does anyone among our international users have the problem that the iCloud Desktop and Documents folders aren’t localized, anymore, in Sonoma 14.5…? For example, on the Italian system that I use, they should be named Scrivania and Documenti, in the Finder sidebar and Dock, but strangely they retain their English names (Desktop and Documents); I also tried this with another known language (Danish: should be Skrivebord and Dokumenter), and the same problem was present: they still were named in English. An Apple iCloud, Sonoma 14.5 or perhaps even OCLP 1.5.0 problem…? Or maybe something peculiar to my system? Who knows…
I use Danish as my language, and the names in Finder are "Skrivebord" (Desktop) and "Dokumenter" (Documents).
The folders you are referring to are may be controlled by settings in the iCloud system. Suggest you check which language is chosen at the bottom of this site: https://appleid.apple.com/account/manage
Mine is Danish.
Last edited: