All going smoothly just like last time. Thanks for the assist before.
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 that warning regarding b4. Appreciated. Was about to do that update so will hold off.
The final 14.6 release should be very close regardless and might need a fix for the patcher then at some point I guess. b3 is stable here with latest OCLP 1.5 stable release so it can wait as 14.6 has no new features AFAIK, and looks like a code cleanup and under the hood stuff-release.
Updating to Sonoma beta 4 from beta 3 reverting patches 900 mb update using OCLP 1.6n , no issues here on mid 2014 MacBook Pro.
Since I know you have an rMBP10,1 I just finished updating this one from 14.6 b3 to b4, also installed latest nightly OCLP 1.6.0n (2024-07-16) just for luck.
No issues during the update except for a power outage in the middle of the first run when a major lightning storm came through
This morning after restarting the update workflow from scratch all ran as expected and so far everything seems to be AOK
BTW I've started trying to simplify what's going on as much as possible during updates. So I powered off the other Mac, and pulled the HDMI plug out of the rMBP for the external display.
I figure this can only improve the chances of getting a clean run, and also free-up more bandwidth. You're far less likely to "find" anything untested for bugs, or "edge case exceptions", as slacker programmers prefer to call them.
Last edited:
Thanks for the heads-up. Appreciated as always! Might give it a go then if the RC do not arrive next week or so which some rumour sites have guessed it will. Hopefully 14.6 will be a keeper. My rMBP runs well as is on b3..and I am travelling a bit so don't want a backup/restore project right now. Also running the sequoia branch of OCLP and this is a multi boot with 6 partitions these days so not the time to jinx anything. Good chance for "edge case exceptions" here. We shall see.I figure this can only improve the chances of getting a clean run, and also free-up more bandwidth. You're far less likely to "find" anything untested for bugs, or "edge case exceptions", as slacker programmers prefer to call them.
P.S. Will also find use for the name Edge Case Exceptions as a bandname if I ever join a band again
Never heard that term before.
macOS 14.6b4 installed atop b3 OTA, OCLP v1.6n, runs as expected.
👏
👏
After two days with Sonoma 14.6 beta 4 on a rMBP10,1 + nightly I'm impressed. Fans are not running at all this morning, Activity Monitor is looking good.
As expected it was pretty busy after first login, now it's running like a supported Mac, at least on the surface. It's the best Sonoma update to date, for me anyway, YMMV
KIS principle: My advice, after some hard-won experience, is to keep it simple during the update. Unplug- or switch off any external devices you don't really need & take them off line. Reconnect them only after all is up & running nominally. Remember that the Apple- and Dortania devs can't test their code with every possible permutation of devices.
I'm glad I'm using a self-contained device (laptop) for this with all the essential OEM peripherals on board. It makes it real simple to clean up.
As expected it was pretty busy after first login, now it's running like a supported Mac, at least on the surface. It's the best Sonoma update to date, for me anyway, YMMV
KIS principle: My advice, after some hard-won experience, is to keep it simple during the update. Unplug- or switch off any external devices you don't really need & take them off line. Reconnect them only after all is up & running nominally. Remember that the Apple- and Dortania devs can't test their code with every possible permutation of devices.
I'm glad I'm using a self-contained device (laptop) for this with all the essential OEM peripherals on board. It makes it real simple to clean up.
So as I know you have the same rMBP, I bit the bullet and can concur that 14.6b4 is running well on my rMBP 10,1 with no issues during install. A friend who used to code for Apple a long time ago mentioned that very often one of the last few things they tended to fix and optimise in the last few point releases of an OS is power management. Causality and correlation I guess, but this is probably the least of fan spinning I have seen on Sonoma so far. And it used to be quite the issue with constant spinning early on. Ah well. Enjoying the moment while probably jinxing it
Last edited:
thanks but this is Not working on any of my 5,1 machines.. I get the same patcher error.
I simply went back to 14.6B3 and this fixes the issue.
Cheers
The fans on mine spin a bit when using the external monitor via HDMI but not as much as in previous versions. Actually they've just stopped entirely again. It's quiet... too quiet...So as I know you have the same rMBP, I bit the bullet and can concur that 14.6b4 is running well on my rMBP 10,1 with no issues during install. A friend who used to code for Apple a long time ago mentioned that very often one of the last few things they tended to fix and optimise in the last few point releases of an OS is power management. Causality and correlation I guess, but this is probably the least of fan spinning I have seen on Sonoma so far. And it used to be quite the issue with constant spinning early on. Ah well. Enjoying the moment while probably jinxing it
As I struggled myself, installing a Canon Pixma MX 495 on my macOS Sonoma, just want to share the solution for others looking for the solution:
Cheers
IJ Scan Utility2 Ver.2.4.0 (Mac) Not working in OS 13 (Ventura) for Pixma MX 490 Series
Cheers
On our late 2008 Aluminum MacBook, OCLP made it run way too hot, so Mojave via Dosdude1 is as far as we got. YMMV! Good luck. 😓
The KDK for b4 is here: https://github.com/dortania/KdkSupportPkg/releases/tag/23G5075b
It happened to me while updating from b2 to b3. For some unknown reason, when OCLP detected the b3 download, it prompted for the download of the 23G5075b KDK. Later on when I patched, the output said that he expected KDK 24A5279h but would anyway merge wit "second-best" 23G5075b, then I had the same error as you. Note that error appears on the "kext cache rebuild" phase so actually the patching was Ok but the error was on the cache rebuild command. It is apparently not related to OCLP or even 14.6 but to this specific KDK. You should be able to reproduce it by typing "sudo kextcache -i /" in the terminal.
Unlike you, to get a working beta I deleted all the KDKs, reverted to OCLP 1.5, and after some minutes I had OCLP asking me to downlad and patch with 24A5279h. It patched smoothly and I could even upgrade back to OCLP 1.6n since now the patcher would merge with "first-best" 24A5279h.
It seems that the same is happening with b3 -> b4, but now with 23G5066c instead of 24A5279h. Right now I've downloaded b4 and 23G5075b was downloaded again. I guess I'll have to delete it and download manually 23G5066c. The instruction given above by Stefan seem in line with this, I only just don't get why "Rename inside /Library/Developer/KDK's, KDK_14.6_23G5066c.kdk to KDK_14.6_23G5075b.kdk" since the patcher is asking for "first-best" 23G5066c actually...
P.S.: Ok, I'm even more surprised that actually 23G5066c was actually download (by OCLP ?), and the patcher is complaining that "found 14.6 (23G5075b), expected 14.6 (23G5066c)" ... Will update to the latest nightly to check if something is changed...
Last edited: