macOS 14 Sonoma on Unsupported Macs Thread

[philippemarques]

I've been using the link on this page to grab the pre compiled binary:
I've applied bold font to the link to draw attention. Is there a different link I should be using?
Sorry, I deleted the post as they said not to share the links and i only saw that after i copied and pasted.

So, if they don't want the links copied and shared, how am I supposed to show people what link I'm using to make sure it's the right one?

Your download link is good,there's only one, it's the automated build from Github.

 

[rehkram]

I don't envy the Devs - the pressure to deliver an OCLP release on Oct 2 must be overwhelming. Devs - cheering for you and hoping for your success, without compromising your health and sanity.

They seem to be keeping a steady hand on the wheel. We should all support that and hope they will not feel rushed into releasing it before it's ready. Speaking as a former software developer and an end user of OCLP, patience is golden in this case.

For you guys who've been beta testing the Sonoma branch, I salute you! 🫡

 

[MacinMan]

Your download link is good,there's only one, it's the automated build from Github.

Right, I copied and pasted the GitHub page so if someone said anything it would be the exact same info people would get going to the page. I just wasn't sure if there were other links. However, since there were comments at the bottom about not sharing links, I deleted the initial post as to not violate that. Thanks again.

 

[deeveedee]

Speaking as a former software developer and an end user of OCLP, patience is golden in this case.

You're lucky. Speaking as a current software developer, I haven't met a patient customer.

EDIT: But my customer is always right. 😉

 

[mohkg]

is there any tutorial on how to build OCLP from the latest GitHub source or do we just rely on the nightly builds? I'm kind of new to building with python thanks

 

[deeveedee]

is there any tutorial on how to build OCLP from the latest GitHub source or do we just rely on the nightly builds? I'm kind of new to building with python thanks

https://forums.macrumors.com/threads/macos-14-sonoma-on-unsupported-macs-thread.2391630/post-32567276

It's in the Dev instructions. You need to add the sonoma-development branch and use Python.org's 3.11.5.

 

[mohkg]

https://forums.macrumors.com/threads/macos-14-sonoma-on-unsupported-macs-thread.2391630/post-32567276

It's in the Dev instructions. You need to add the sonoma-development branch and use Python.org's 3.11.5.

Installed python, created a developer folder under my admin account, next I type "cd ~/Developer/OpenCore-Legacy-Patcher/" and get the attached

 

[Rambear1998]

from ventura to sonoma. sonoma much smoother. however its much better to use static wallpaper rather than live wallpaper. live wallpaper consume so much of ram.

 

[deeveedee]

Installed python, created a developer folder under my admin account, next I type "cd ~/Developer/OpenCore-Legacy-Patcher/" and get the attached

I think I'd be doing you a disservice by explaining more. I'll defer to others.

EDIT: This is not meant to be a criticism of you, but more a general statement. Showing up in this thread without reading any of the history which has taken months of hard work to create and then expecting to have it all re-explained and answered again is frustrating. Probably just me.

 

[philippemarques]

Installed python, created a developer folder under my admin account, next I type "cd ~/Developer/OpenCore-Legacy-Patcher/" and get the attached

When i was more young, we say : RTFM

 

[oraculo666]

FYI: Tried 23A339 as a daily driver. Can't recommend it. Despite new ssd and 16gb of ram. Too many processes maxing out the chip in the background. system feels laggy and sluggish overall. There is s CGPDFservice running constantly in the background. Also photos/photoanalysis and music take huge amount of resources. CPU is always maxed out. Maybe this is a specific issue to this machine, however it's no fun at all. Maybe it's time to retire the 9,2.

I'm seeing this a lot too. Looks like CGPDFservice doing something to the pdf library I have on my computer. I hope it stops once it's done, my computer is running hot and it's already a hot day. 🥵

 

[deeveedee]

When i was more young, we say : RTFM

I still say it, and I'm old.

 

[mohkg]

I think I'd be doing you a disservice by explaining more. I'll defer to others.

EDIT: This is not meant to be a criticism of you, but more a general statement. Showing up in this thread without reading any of the history which has taken months of hard work to create and then expecting to have it all re-explained and answered again is frustrating. Probably just me.

I figured it out but build keeps failing.

 

[deeveedee]

I figured it out but build keeps failing.

A bit of advice ... do not post anything like this on OCLP Discord unless you want to have your hat handed to you.

EDIT: Figuring out how to get unstuck is going to be critical to knowing how to use it. If not, wait for the next pre-built version.

EDIT2: BTW, if it seems like I'm being harsh, it's only because I know you're more capable than you give yourself credit. Just take your time and figure it out. Post your results when you've finished.

 

[mohkg]

A bit of advice ... do not post anything like this on OCLP Discord unless you want to have your hat handed to you.

EDIT: Figuring out how to get unstuck is going to be critical to knowing how to use it. If not, wait for the next pre-built version.

EDIT2: BTW, if it seems like I'm being harsh, it's only because I know you're more capable than you give yourself credit. Just take your time and figure it out. Post your results when you've finished.

might be my python version ill keep trying thanks

 

[K two]

At this point in time, it may be prudent to chill until macOS 14.1 and OCLP 1.0.1 are released?? 🤷‍♂️

 

[macOS XP]

At this point in time, it may be prudent to chill until macOS 14.1 and OCLP 1.0.1 are released?? 🤷‍♂️

On your main machine, definetely. However I think it is pretty important for the devs that there are people beta-testing and reporting bugs in the meantime.

 

[rehkram]

At this point in time, it may be prudent to chill until macOS 14.1 and OCLP 1.0.1 are released?? 🤷‍♂️

Or a clean install back to the last working scenario perhaps, then chilling.

 

[Saltacharcos]

If you can install the last MacOS that was supported, that might help, as that indicates that there might be a firmware issue. Test it with Silent Knight if you have not already if the firmware is correct?

Thanks for the reply.

That's just the problem, I can't update the firmware (I guess for the same reason, the model value). I didn't know about Silent Knight, I'll look it up now.

update

Well...silent knight doesn't recognize the iMac model either

 

[rehkram]

On your main machine, definetely. However I think it is pretty important for the devs that there are people beta-testing and reporting bugs in the meantime.

That assumes they are reading this forum. Given the need to avoid the distractions caused by an issue that might only be on a single m/c with broken software or hardware it's possible they don't dive into everything reported here. I may be wrong.

 

[deeveedee]

That assumes they are reading this forum. Given the need to avoid the distractions caused by an issue that might only be on a single m/c with broken software or hardware it's possible they don't dive into everything reported here. I may be wrong.

If they are paying close attention to this thread, they're laughing their asses off or sobbing uncontrollably.

 

[hvds]

Hello to all,

Downloaded Sonoma RC2 OTA onto iMac 13,2 (Late 2012 with fusion drive) and installation went without a problem, however, on patch application of OCLP 0.9.6 nightly, patching failed with an error code 71 (see attached) The only thing I did different, than routine installation, is revert patches before invoking OTA update in order to try Delta download.

I downloaded full installer from Mr. Macintosh website, created a thumb drive installer and installed Sonoma over previous (OTA) effort, but was greeted by same error (71) message.

I booted into Monterey (separate volume) and it was fully functional, including graphic acceleration, Wi-Fi, Bluetooth, etc. There was an update to that OS to 12.7 (from 12.6.9) which I applied without trouble, but when I applied latest OCLP 0.6.9 patching failed with a different message, than one elicited by Sonoma.

Final result: neither Sonoma nor Monterey are accelerated, though fully functional otherwise. Catalina volume functions without an issue.

If anyone has experienced similar problems, or had seen such error messages before, I would greatly appreciate any input.

Installation of Sonoma and Monterey updates on MacBook Pro 5,2 (2009) went without issues, and same OCLP 0.6.9 patches functioned without any errors.

First attachment is Sonoma generated error, second (with dark background) is Monterey associated error message. View attachment 2282199 i View attachment 2282200

Hello RogueB,
it looks to me that at least the first patching failure for your iMac 13,2 has to do with KDK not working correctly (this assumption can of course be wrong). The Python code which invokes KDK for rebuilding the kernel cache etc is on Github under resources/sys_patch/sys_patch.py lines 287 ff if I read it correctly.

Did the post-install patch try to load a KDK at all? (it should have used the one from 14.0b7 as closest match as the proper one for 14.0 release seems to be not yet there).
Maybe the problem goes away once the proper KDK is available and thus freshly loaded by the patcher.
Otherwise you could have a look at your /Library/Developer/KDKs and delete the KDK... folders which are in there, to force the patcher to freshly load whatever KDK seems appropriate.
I'm not sure I've seen this error before, but could be, in the early days of KDK usage by the patcher.

 

[mpbb]

Just to drop my 2 cents, I've have had no issues upgrading my early-2015 13" Macbook Air MBA 7,2 from Ventura to Sonoma 14.0 using the standard upgrade procedure (was just prompted yesterday), after having installed OCLP 0.6.9 using the current nightly build.
Bluetooth and Wifi working fine. Actually Wi-fi seems faster . So far no issues at all as far I can tell. Thanks, Devs !

 

[deeveedee]

I added an APFS volume on my MBP6,2 and performed a clean install of Sonoma 14.0 Release. After applying post-install patches to 14.0, I was able to upgrade to 14.1 Beta. I did not re-apply post install patches after the 14.0->14.1 upgrade. My MBP6,2 boots 14.1 Beta without issues as long as I do not apply post-install patches to 14.1, so 14.1 Beta issues on non-metal Tesla don't appear to be with the OC EFI. Not complaining, just reporting. Still amazing that 14.1 'works' at this stage.

My 'working' Sonoma 14.0 volume continues to work fine with patching.

EDIT: For those having issues with installing Sonoma or upgrading to 14.1, I have found that a low-latency, reliable wired Ethernet connection helps a lot. Since there is no native Wi-Fi on legacy Macs without the post install patches, having the wired Ethernet helps. And not just any network connection... On slower or higher latency wired connections, I've experienced Sonoma install/upgrade failures.

EDIT: For example, my 14.1 upgrade succeeded when I had a wired Ethernet connection directly to my router. Sonoma 14.0->14.1 upgrade failed when I attempted the upgrade with a low-quality Ethernet-Over-Power connection.

Not enough of a statistical sample to draw conclusions - just reporting.

EDIT2: It's been said before, but it's important. Unless something changes, we are not able to upgrade non-metal Macs with incremental macOS updates. Do not revert patches on non-metal Macs before upgrading macOS. On non-metal, upgrade macOS with the post-install patches installed and accept the pain of a full installer download.

I am typing this in Firefox on MBP6,2 running Sonoma 14.1 Beta (no post-install patches). Performance is surprisingly snappy.

 

[philippemarques]

Update OTA worked from sonoma 14.0 to sonoma beta 14.1
Lost acceleration, wifi, should be patched.
Installation to 14.0 worked well, stay at sonoma 14.0

###################################

# OpenCore Legacy Patcher (0.6.9) #

###################################
Log file set:
~/Library/Logs/Dortania/OpenCore-Patcher_0.6.9_2023-09-28_23-54-31-927705.log
2023-09-28 23:54:34.310 Python[2508:28792] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
Entry point set: MainFrame
Initializing Main Menu Frame
Initializing Root Patch Display Frame
Found GPU (0): 8086:126
Pulling KDK list from KdkSupportPkg API

No direct match found for 23B5046f, falling back to closest match

Closest Match: 23A5337a (14.0)
Corrupted KDK found (KDK_14.0_23A5337a.kdk), removing due to missing file: System/Library/Extensions/AFTK_Kext.kext

Following KDK is recommended:
- KDK Build: 23A5337a
- KDK Version: 14.0
- KDK URL: N/A

Checking if new patches are needed

Available patches:
- Graphics: Intel Sandy Bridge
- Networking: Modern Wireless
- Miscellaneous: Legacy Keyboard Backlight

EDIT : KDK corrupted, re-downloaded, after post root-patch ( yesterday OCLP with Opencore 0.9.5 ) reboot hangs.