Sidebar 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.
MacRumors3590 said:
thanks but still no good. hmmm... what could it be?
Click to expand...
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:
  • Like
Reactions: 0134168
mpbb said:
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...
Click to expand...
interesting! thanks for the info.
 
mpbb said:
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...
Click to expand...
WOW!!! It works now.
Did what u said,
went back to oclp 1.5 and I erased all kdk files and it downloaded 23G5075b KDK and patched successfully!
Cheers Friend and thanks!
 
  • Like
Reactions: mpbb, K two and 0134168
I got my hands on 27" 2011 iMac (iMac12,2) fort dirt cheap last week and upgraded RAM, CPU and Storage (SSD).

Yesterday, I installed the hardware upgrades put the machine back together and installed macOS Sonoma 14.5 (23F79) After patching with OCLP and updating all kexts to the latest versions, I had no sound.

EDIT: The issue is caused by AppleALC.kext (1.9.1). I was using the latest nightly build from Dortania's Build Repo and it does not work. Reverted to the kext that comes with OCLP and Audio works again (1.6.3). This should be investigated though.
 
Last edited:
  • Like
Reactions: roronl
MacRumors3590 said:
WOW!!! It works now.
Did what u said,
went back to oclp 1.5 and I erased all kdk files and it downloaded 23G5075b KDK and patched successfully!
Cheers Friend and thanks!
Click to expand...
Really glad that it helped you so immediately and also glad that I know now that I won't need to refrain from updating to b4, even if it will be a bumpy ride (again). I just need to decide if I try the 1.6n way or start right away from 1.5. The rational choice should be 1.5 as there is a 99% chance that I will stumble on the same issue if I go the 1.6n route :). Cheers.
 
mpbb said:
Really glad that it helped you so immediately and also glad that I know now that I won't need to refrain from updating to b4, even if it will be a bumpy ride (again). I just need to decide if I try the 1.6n way or start right away from 1.5. The rational choice should be 1.5 as there is a 99% chance that I will stumble on the same issue if I go the 1.6n route :). Cheers.
Click to expand...
very true and thanks again!
 
  • Like
Reactions: mpbb
K two said:
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. 😓
Click to expand...
Thanks for that info. Trying to see which up to date OS would be best without the machine struggling to keep up.

I was able to get Windows 11 running "fine", but trying to see how far I can go with macOS. If not at the very minimum Monterey then perhaps a lightweight linux distro is the most sensible solution to continue receiving security updates.
 
  • Like
Reactions: K two
I have upgraded an iMac12,2 from 2011 I recently obtained with an i7-2600 and an NVIDIA Quadro 1100m (flashed it via SSH) to benefit from metal support. It's running macOS Sonoma 14.5 just fine.

The card is working fine but I can't enable Intel Quick Sync Video which is supported since Sandy Bridge. I was wondering this is SMBIOS related, because the 12,x models use AMD cards while 13,2 uses NVIDIA Cards.

I was wondering if SMBIOS spoofing could resolve the issue but the options for spoofing I tried (minimal and advanced) resulted in a crossed-out symbol on start. Any suggustions are welcome.
 
Last edited:
14.6 (23G80) seems fine on a rMBP 10,1 2012. Installed OTA without issues.

edit: also seems fine on MBA 3,2 2010 with OCLP 1.5 that loaded and merged the correct new KDK without issues so far.
FWIW, I will say that 14.6 was the OS version I thought would be end of the road for our legacy Intel Macs
but it appears now there is a decent chance that it might rather maybe be 15.6. Ah well, we shall see... ;)
 
Last edited:
  • Like
Reactions: rehkram and TOM1211
Gfrancony said:
Hi, it works with open core?
Click to expand...
Yes on my test MacPro5,1 with OCLP 1.6n and KDK without problems... (nearly the same hardware listet below but only 6core) my production MacPro5,1 and my other macs only getting the final releases. But all looks good so far so fingers crossed for maybe next week ;-) (but OCLP is not open core it's an open core "installer" but i think you're talking about oclp)
 
Last edited:
macOS 14.6 RC1 installed atop b4 OTA, OCLP v1.6n, runs better than expected.:apple::cool:
14.6 release.jpg👏 I stand corrected, this is an RC. 🙃😬
 
Last edited:
  • Like
Reactions: Steve Gosselin, macpro_mid2014, mpbb and 4 others
And macOS 14.6 release installed atop b4 OTA on non-metal machine, OCLP v1.6n (no need to revert to 1.5 as for b3 and b4 since OCLP downloaded the right KDK, most probably because, luckily enough, 23G80 > 23G75 (b4) (no laughs please) - even though still 23G80 (release) < 24A52 (b3) ...).
Capture d’écran 2024-07-24 à 01.39.44.png
 
  • Like
Reactions: K two and MacRumors3590
Imac 27, 13.2---recent 14.6, yesterdays 1.6n, OTA, this time when OCLP asks to repatch, there were 3 "ignore but click okay" boxes that appeared, usually there are only 2, I believe there is a fairly recent line added to the changelog. the mouse arrow appears more quickly, and things seem quicker.

My imagination, perhaps, we know how it goes.
 
  • Like
Reactions: K two, rehkram and jotzet
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