Toggle sidebar Toggle sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
deeveedee said:
Thanks! While re-applying post-install patches with OCLP 1.2.1 (Release) to Sonoma 14.1.1, OCLP automatically downloaded the new KDK.
Click to expand...
Three quick questions from a neophyte.
1. How does one tell which KDK release is currently installed?
2.To install the new KDK release, I revert the current root patches and then after restart, reapply needed root patches which automatically installs the new KDK. Is that the correct procedure?
3. Why is keeping the KDK updated important?
Thank you, Jim
2013 Imac (14,1) using Sonoma 14.1.1 and OCLP 1.2.1
2011 MacAir (5,2) using Sonoma 14.1.1 and OCLP 1.2.1
 
  • Like
Reactions: amaze1499
PoloHofer said:
There's a new KdK for System 14.1.1

github.com

Release Kernel Debug Kit 14.1.1 build 23B81 · dortania/KdkSupportPkg

KDK for macOS 14.1.1 (23B81)
github.com github.com
Click to expand...
MBP5,2: successfully installed 14.1.1 from USB with OCLP 1.2.1. The new KDK is used during post-install patching.

This time made a clean install to internal SATA SSD - installed 14.1.1 to the end, after that ran migration assistant using a CCC data clone from my MBP11,1 production machine, then post-install patching.
(I use the same CCC data clone, with 14.1.1 installed over it, as bootable backup for the 11,1. Doing incremental CCC backups to it, in addition to Time Machine backups on separate disk).
Clean install became necessary after an OTA upgrade from 14.1 to 14.1.1 had failed halfway.

MBP5,2 and MBP11,1 running 14.1.1 now with 1.2.1. The former using KDK, the latter KDK-less patching (i.e. extra kexts in /Library/Extensions. Migration assistant had migrated these, which gave problems before deleting them manually from the 5,2's internal SSD).

So a 14-years old machine and a 10 years old running well with the latest Sonoma. Thanks developers!
 
Last edited:
  • Like
Reactions: olad, roysterdoyster, macinfo and 4 others
JimmyT72 said:
Three quick questions from a neophyte.
1. How does one tell which KDK release is currently installed?
2.To install the new KDK release, I revert the current root patches and then after restart, reapply needed root patches which automatically installs the new KDK. Is that the correct procedure?
3. Why is keeping the KDK updated important?
Thank you, Jim
2013 Imac (14,1) using Sonoma 14.1.1 and OCLP 1.2.1
2011 MacAir (5,2) using Sonoma 14.1.1 and OCLP 1.2.1
Click to expand...
Number 2 first, as it's easy: Yes, that is the recommended process, but you can shortcut that by simply reapplying the root patches (note that this is not the recommend procedure, but it will work if your hardware hasn't changed at all).
Number 1. Look in the /Library/Developers folder. That is where the KDKs are kept. Normally you will have only one KDK (but with two files, one is a backup pgk package file). If you have 2, look at the version numbers and keep the one (two files) for the latest installed macOS.
Number 3. KDKs are used and necessary during the root patching procedure. The OCLP app is quite good at picking the KDK closest to the current installed OS that will work. I don't think we need to delve further into why, unless you are interested in the programming involved. In that case you might venture to register on the Discord forum and ask there. That field is a definite "Black Box" for me.
 
Last edited:
  • Like
Reactions: 0134168, olad, deeveedee and 2 others
And here we go again, this time with the new Blender 4:

Screenshot 2023-11-15 alle 17.52.00.png
 
  • Like
Reactions: macinfo
davidlv said:
Number 2 first, as it's easy: Yes, that is the recommended process, but you can shortcut that by simply reapplying the root patches (note that this is not the recommend procedure, but it will work if your hardware hasn't changed at all).
Number 1. Look in the /Library/Developers folder. That is where the KDKs are kept. Normally you will have only one KDK (but with two files, one is a backup pgk package file). If you have 2, look at the version numbers and keep the one (two files) for the latest installed macOS.
Number 3. KDKs are used and necessary during the root patching procedure. The OCLP app is quite good at picking the KDKD closest to the current installed OS that will work. I don't think we need to delve further into why, unless you are interested in the programming involved. In that case you might venture to register on the Discord forum and ask there. That field is a definite "Black Box" for me.
Click to expand...
Thank you very much. Your answers were very clear. And yes, I think I can stop at your answer for #3. Ha. Old, neophyte here just trying to stay above water. My best!
 
  • Like
Reactions: olad and hvds
Reinstalled macOS 14.2b1 atop broken (boot looping) b2 and all is back to somewhat normal. Finding the b1 Install Assistant (19.2.01) required some digging since OCLP offers only the second beta in the app. Discord had b1, btw. 👏
14.2b1.jpgBeta 1 runs almost as well as 14.1.1 except for the Stocks Widget which needed to be re-installed. App is ok.
 
Last edited:
  • Like
Reactions: amaze1499 and deeveedee
nekton1 said:
The 1.2 and 1.3 nightly OCLP root patch function does not work correctly with the November 13 Monterey 12.7.2 (21G1967) beta. The patcher finds that a nVidia Kepler root patch is required (screenshot) but fails with the following message (screenshot) and the internal display has a white line around dock. (On an iMac 12,2 with K2100M GPU).
Click to expand...
Here is the Monterey thread https://forums.macrumors.com/threads/macos-12-monterey-on-unsupported-macs-thread.2299557/page-366 maybe the better place for your issue - good (◔‿◔) 🤞
 
rbart said:
The 1.3.0n is exactly the same as the 1.2.1
Why always installing nightlies without checking what's new ?
Click to expand...
I simply was already on the nightly - that’s all ;-) so no need to go back to 1.2.1 cause it’s the same (at the moment). Reason for my post was the new KDK btw…
 
Sven G said:
And here we go again, this time with the new Blender 4:

View attachment 2312655
Click to expand...
Hmmm… from the Blender 4 release notes (so, it could perhaps depend both on Metal 2.2 being required and on dropped support, for Nvidia Kepler and Intel Haswell: not an OCLP issue?):

Graphics Cards​

  • The minimum required OpenGL version has been increased to 4.3 for Linux and Windows. (3478093183)
  • On macOS only Metal is supported now, and the OpenGL backend has been removed. A GPU with Metal 2.2 support is required. Intel Macs without an AMD GPU require a Skylake processor or higher. (cdb8a8929c)
  • Due to driver issues, support for Intel HD4000 series GPUs has been dropped.
 
  • Like
Reactions: il-rollino, roronl, jotzet and 1 other person
Hello everybody,

I have a MacBookPro14,1 , no touchbar, i managed to get OCLP working but i had a camera issue, so i downgraded to Ventura.

Facetime isn't working, Photobooth neither. The video is not capturing.

Does someone works on this issue ? Is someone know how to fix this ?

Kind regards 😛
 
  • Like
Reactions: K two
Jérôme C said:
Hello everybody,

I have a MacBookPro14,1 , no touchbar, i managed to get OCLP working but i had a camera issue, so i downgraded to Ventura.

Facetime isn't working, Photobooth neither. The video is not capturing.

Does someone works on this issue ? Is someone know how to fix this ?

Kind regards 😛
Click to expand...
Try a SMC/NVRAM reset? 😉
 
Screenshot 2023-11-16 at 19.50.30.png
Third Public Beta of macOS Sonoma 14.2 is working very fine in my MacPro 4,1>5,1 after a smooth OTA update. No BT of course but very nice performance after OCLP 1.2.1 new patching.
 
  • Like
Reactions: K two
JimmyT72 said:
Thank you very much. Your answers were very clear. And yes, I think I can stop at your answer for #3. Ha. Old, neophyte here just trying to stay above water. My best!
Click to expand...
I like davidlv's answers, very clear indeed. - So the following likely delves too deep.
Just to add for #3, if you want to see what happens in the code, in OCLP Github, the main place to look at is in resources/sys_patch/sys_patch.py. So KDK contains the utility kmutil, which was formerly part of macos but now it is extra, in KDK. kmutil is needed to massage kernel collections after adding/replacing kexts etc. (already in pre-OCLP times). After KDK is installed, kmutil can be looked at in Terminal. With caution, it has so many features. E.g. kmutil find lists all the kexts present with their location.
The other interesting piece of code is resources/kdk_handler.py.
Looking at the source is sometimes useful when trying to understand a failure situation, without asking the developers. It also gives a good impression for the high quality (and amount) of code in OCLP.
Excellent developers! (I'm not one of them).
 
  • Like
Reactions: davidlv and K two
houser said:
Just a luxury question if allowed and tolerated..
Some of the Aerial screensavers are very nice, but run the GPU out of town...
I don't expect a solution to this other than saying they are a nice pitch for new MacBooks 😉
I would assume the only way to run them quietly on an old-ish Mac without taxing the GPU and running the fans at full tilt would be to down-convert some of the best Screen Savers (should really be called GPU Hoggers) to lower display resolution and perhaps other friendlier codec. Might defeat the purpose by not looking good anymore anyway.
They run quietly on the Apple TV 😉
Ah well, if against all odds, there is a way to run them without upsetting the fans please comment.
Click to expand...
Did you find a solution? I completely agree it's a luxury question but it'd be cool if I could see these fluidly. I'm not knowledgeable enough to know if it's only the resolution or something else.

Thanks!
 
  • Like
Reactions: K two
HowowcanIgo said:
Did you find a solution? I completely agree it's a luxury question but it'd be cool if I could see these fluidly. I'm not knowledgeable enough to know if it's only the resolution or something else.

Thanks!
Click to expand...
No solution other than buying a computer with more FLOPS and MIPS. Aerial just require quite a bit of it. No way around it other than down-sizing them or something like that AFAIK. Which is unlikely 😉
 
Last edited:
  • Like
Reactions: HowowcanIgo and K two
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back