macOS 14 Sonoma on Unsupported Macs Thread

[hvds]

MBP11,1: 14.6 installed from full installer to internal SSD over 14.5. Using OCLP 1.5.0 for EFI and root patching. Smooth process, good result.

As usual when installing this way, need to remove AppleIntelHD5000Graphics and AppleIntelFramebufferAzul kexts from /Library/Extensions before installation (or afterwards booted in safe mode). OTA installing removes them automatically. Root patching installs them again.

This MBP is still doing very well as my daily working machine. Many thanks to the developers!

 

[rehkram]

I use OTA to update mac mini 2009 Late from 14.4.1 to 14.6, the "About 35 minites remaining..." showing after downloaded KDK 23G80, how long do I have to wait?

As long as possible.

But I, and several others, have found that the install process tends to hang for reasons unknown but is very forgiving. So you can kill it and restart. I've done this successfully on several occasions.

The upgrade software design on Mac is, in my opinion, the best piece of code on the machine simply for its fault tolerance. Always have a good backup on hand though before long-pressing that button.

 

[Larz3n]

I'm coming up against a completely reproducible bug on Sonoma 14.6, OCLP 1.5. This is a Mac mini late 2012 that I use as a media server, although it's really a redundant backup to a Mac mini M1 I bought to replace it.

Sonoma 14.5 on OCLP 1.4.3 was actually very unstable for me: frequent kernel panics. 14.6 on OCLP 1.5 seems a lot better, in every respect but one: the TV app. I'm getting a crash when I click on any of the options in the Library. As I say, this is connected to my TV, so in many ways it is what the Mac is for… The beginning of the error is also screenshot. I've deleted the preferences and started again with a new library. With new preferences, the Apple TV and TV+ options are fine. It's the Library options that cause a near-immediate crash. I thought maybe one file might be corrupted, so removed all the contents, with the idea to add them back one time. It doesn't matter: it still crashes, even with an empty library. Interestingly, even going to home sharing to the Mac mini M1 (with the idea to reimport) also causes an immediate crash. I try to keep the Mac mini M1 file for-file-identical, including not running beta software on it so I could restore from its backup to the Mac mini late 2012. Its TV.app is working perfectly, with the same files. (incidentally, almost all are old or very old BBC shows or other video I've edited or clipped up: it's not some wrong-side-of-the-tracks .mkv! No judgment: I'm just saying I don't think this is virus or malware related, for troubleshooting purposes.)

Anyone run into this? All Google detailed specific searches are bad now as I'm sure we all know, but the most relevant thread seems to be this one on Reddit, though it's about Monterey. The problem is exactly mine though. If I read it right, the OP had Apple replace his hardware! Not exactly an option with a 2012 Frankenmac… The only other point of difference that I can see is I am running OCLP, which is why I'm posting here in case one of you guys thinks I've overlooked something.

Thanks!

I have the same issue with my MBP9,1 after updating to Sonoma 14.6 from 14.5. OCLP hasn’t changed during the update. I can view ATV+ films and series with no issues. Only when accessing local film overview, the app crashes.

 

[mikezang]

As long as possible.

But I, and several others, have found that the install process tends to hang for reasons unknown but is very forgiving. So you can kill it and restart. I've done this successfully on several occasions.

The upgrade software design on Mac is, in my opinion, the best piece of code on the machine simply for its fault tolerance. Always have a good backup on hand though before long-pressing that button.

Like you said, I aborted it and reboot it again, now I got the newest Sonoma 14.6

 

[waz0wski]

Updated my 6,1 TrashPro™ to 14.6 without issue - OTA update, OCLP 1.5
Did take a while and several reboots to complete

 

[Flyview]

Alright I'm seeing a very strange issue, not sure if it's new.

Machine:
Late 2013 15" Macbook Pro with dedicated graphics.

Software:
OCLP Sonoma

If I let the computer sit plugged in with the screen on, after about 5 minutes it starts using up a lot of power from the dedicated GPU (I can see it in iStatMenus). As soon as I move the mouse, it goes away and the dedicated GPU turns off. This also happens if I turn the screen off (corner shortcut) immediately. I can also see VTDecoderXPCService running in Activity Monitor when this happens. It's as if the live screensaver is running, but that's set to never!

Steps to reproduce:
1) Make sure laptop is plugged in
2) Turn screen off with "hot corner" shortcut
3) Computer gets hot from using ~5A from the dedicated GPU

I believe this also happens if I close the lid, since I first noticed the computer was getting hot just sitting there closed but charging. I have "Prevent automatic sleeping on power adapter when the display is off" enabled.

What the hell?

Update...this seems to have gone away. I stopped using gfxstatus to set if I want the integrated or dedicated graphics card. Not sure if that's the fix or not, but for now it stopped doing it.

 

[highvoltage12v]

I updated my Mac Pro 6,1 (both D500) to 14.6 and Ventura 13.6.8. On both chromium and Chrome, i'm having red artifact-ing and zero functionality. Can't get into settings to turn off hardware acceleration. Has anyone else noticed this issue.

Downgrading (reinstalling older versions to a separate SSD) to 13.6.7 and 14.5 fixes the issues in chrome. Swapped the SSD's between the two Mac Pro's to rule out the D500's.


Still in older releases of Ventura and Sonoma i'm having pink artifacts. The next closest solution I found is to switch to Chrome Dev build (129.0.6628.3) and I haven't had any issues.

EDIT 8/6/24
I downgraded to chrome 127.0.6533.100. Immediately on first launch go to "chrome://flags/" and change ANGLE graphics backend to OpenGL. relaunch Chrome before it updates, Metal rendering is broken in chrome due to the AMD drivers from Monterey.
I also enabled "Display Compositor to use a new gpu thread" which allows Chrome to use both GPU's to render objects. I think performance is improved. See activity monitor screenshot.

 

[mikezang]

Like you said, I aborted it and reboot it again, now I got the newest Sonoma 14.6

Though I updated to 14.6, but The Chinese or Japanese IME can't work since 14.4.1, what can I do to solve this IME problems?

 

[mikezang]

When I run OCLP from source, I got error as below, what can I do?

Traceback (most recent call last):
File "/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/OpenCore-Patcher-GUI.command", line 6, in <module>
from opencore_legacy_patcher import main
File "/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/opencore_legacy_patcher/__init__.py", line 1, in <module>
from .application_entry import main
File "/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/opencore_legacy_patcher/application_entry.py", line 13, in <module>
from . import constants
File "/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/opencore_legacy_patcher/constants.py", line 10, in <module>
from .detections import device_probe
File "/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/opencore_legacy_patcher/detections/device_probe.py", line 17, in <module>
from ..support import utilities
File "/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/opencore_legacy_patcher/support/utilities.py", line 15, in <module>
import py_sip_xnu
ModuleNotFoundError: No module named 'py_sip_xnu'

 

[mikezang]

When I run OCLP from source, I got error as below, what can I do?

I sloved it!

 

[chrickers]

MBP11,1: 14.6 installed from full installer to internal SSD over 14.5. Using OCLP 1.5.0 for EFI and root patching. Smooth process, good result.

As usual when installing this way, need to remove AppleIntelHD5000Graphics and AppleIntelFramebufferAzul kexts from /Library/Extensions before installation (or afterwards booted in safe mode). OTA installing removes them automatically. Root patching installs them again.

This MBP is still doing very well as my daily working machine. Many thanks to the developers!

Thanks for Sharing! I have the same model but I'm still on Monterey. Good to know that Sonoma is working fine, just in case I have to upgrade

 

[Flyview]

Alright I'm seeing a very strange issue, not sure if it's new.

Machine:
Late 2013 15" Macbook Pro with dedicated graphics.

Software:
OCLP Sonoma

If I let the computer sit plugged in with the screen on, after about 5 minutes it starts using up a lot of power from the dedicated GPU (I can see it in iStatMenus). As soon as I move the mouse, it goes away and the dedicated GPU turns off. This also happens if I turn the screen off (corner shortcut) immediately. I can also see VTDecoderXPCService running in Activity Monitor when this happens. It's as if the live screensaver is running, but that's set to never!

Steps to reproduce:
1) Make sure laptop is plugged in
2) Turn screen off with "hot corner" shortcut
3) Computer gets hot from using ~5A from the dedicated GPU

I believe this also happens if I close the lid, since I first noticed the computer was getting hot just sitting there closed but charging. I have "Prevent automatic sleeping on power adapter when the display is off" enabled.

What the hell?

Problem came back. Finally figured out what it was. It wasn't VTDecoderXPCService at all, but mediaanalysisd running as soon as the computer became idle. It didn't use much CPU but was cranking out my dedicated GPU, making the computer hot. After looking into it, it looks like this has been a controversial thing for some years, Apple analyzing your photos for various AI objectives. I don't even have any photos in the Photos app. As I was frantically looking around for how to disable it, I found this:

https://appleinsider.com/inside/mac...mediaanalysisd-from-hogging-your-cpu-in-macos
https://forums.macrumors.com/thread...-scanning-your-files-without-consent.2377433/

I was about to disable SIP (or whatever is left of it after OCLP) and remove the plist when I noticed that OCLP itself has an option to disable mediaanalysisd! I would highly recommend this for people who leave their laptops plugged in, idle.

 

[rehkram]

Problem came back. Finally figured out what it was. It wasn't VTDecoderXPCService at all, but mediaanalysisd running as soon as the computer became idle. It didn't use much CPU but was cranking out my dedicated GPU, making the computer hot. After looking into it, it looks like this has been a controversial thing for some years, Apple analyzing your photos for various AI objectives. I don't even have any photos in the Photos app. As I was frantically looking around for how to disable it, I found this:

https://appleinsider.com/inside/mac...mediaanalysisd-from-hogging-your-cpu-in-macos
https://forums.macrumors.com/thread...-scanning-your-files-without-consent.2377433/

I was about to disable SIP (or whatever is left of it after OCLP) and remove the plist when I noticed that OCLP itself has an option to disable mediaanalysisd! I would highly recommend this for people who leave their laptops plugged in, idle.

Awesome discovery there. I recently took the back off an rMBP10,1 to put in a new battery, upgraded BT-Wifi card, and to clean the fans that were a nuisance. I will also keep an eye on mediaanalysisd and disable it if necessary.

 

[houser]

Awesome discovery there. I recently took the back off an rMBP10,1 to put in a new battery, upgraded BT-Wifi card, and to clean the fans that were a nuisance. I will also keep an eye on mediaanalysisd and disable it if necessary.

I have that disabled and it does not seem to change much as I recall. It is also not open knowledge exactly what mediaanalysisd does, apart from face recognition in Photos so you need it enabled if you use that.
The AI stuff is Internet grapevine and not in the evidence category AFAIK. Little Snitch does not report anything obvious there either.

 

[ronton3]

Set AssociatedBundleIdentifiers property in launch services as an array.

This new line has been added to the 1.6 changelog.

Does anyone know what it means?

 

[rehkram]

Well I would hazard a guess that it had been previously instantiated (i.e. defined) as a string (or something else). So changing it to an array would count as a correction. I believe plugging-in bundling functionality was a fairly recent addition to OCLP related to installation automation.

Defining it as a single element string might not show up at compile time, and depending on how the rest of the code used it, might not have broken anything. Non-fatal syntax error corrections are a common type of change made to earlier versions.

Somebody knows for sure, please feel free to correct my SWAG

 

[johny72]

Hello. Thank you for allowing me to be here. Now I want to buy a 5.1 Mac Pro with an RX560 graphics card. Sonoma needed me for the machine. My question is, what do I need to do to install Sonoma on this Mac Pro? Thank you very much in advance for your help!

 

[johny72]

I also asked in the previous one because a friend also has a 5.1 Mac Pro and Radeon Nitro RX 580 8GB video card, I have a boot screen, OCLP 1.5, but it does not go through the installation. What could be the problem with him?

 

[RAMtheSSD]

Perhaps, in more abbreviated form? Although my problem is in Sonoma and the subject of the previous entry was not, the previous entry in this thread did suggest a possible solution to my Bluetooth problem. The solution suggested that the bluetooth problem in my cMP was not due to kext issues but to having a USB drive connected to Mac Pro and that removing it followed by a PRAM reset would result in Bluetooth function; I did and there was Bluetooth function but no wifi --the opposite of the previous state. I assumed the issue might be fixed by another reboot (why not? removing a thumb drive fixed Bluetooth after lots of ineffective but time consuming tinkering didn't) and it did not. The problem is that nothing has brought Bluetooth back including further reboots. Now, no information appears when Bluetooth is selected in the system report.

Someone might be thinking that I did not look well enough out there, however, thus far, they'd be incorrect. ((AFAIK)), the bluetooth problem was solved and integrated into a release of OCLP. I used 1.5.0 and it did work when the USB drive was pulled off so, whatever this is, it isn't the same thing as what was fixed by running Bluetooth in a VM --as I understood the explanation.

Any feedback concerning how I could get more people to read and reply is welcomed

 

[dcabq]

Thanks again to @houser and @makra !

Issues fixed...and a MacBook 10,1 (very great stuff) running fine on Sonoma !

Now, what about automatic update : enable or disable ? what is your feeling ?


View attachment 2402148


Serviteur,

Disable. When a new update is available, then OTA update.

 

[dcabq]

I use OTA to update mac mini 2009 Late from 14.4.1 to 14.6, the "About 35 minites remaining..." showing after downloaded KDK 23G80, how long do I have to wait?

Keep waiting till it comes back after reboot and apply OCLP 1.5

 

[mwidjaya]

OTA to latest 14.6 on the MBP9,1.

Seems to be running fine.

But for a day later to further OTA to 14.6.1 successfully.

 

[Gfrancony]

Hi, Sonoma 14.6.1 works with OCLP? Please

 

[hvds]

MBP11,1: 14.6 installed from full installer to internal SSD over 14.5. Using OCLP 1.5.0 for EFI and root patching. Smooth process, good result.

As usual when installing this way, need to remove AppleIntelHD5000Graphics and AppleIntelFramebufferAzul kexts from /Library/Extensions before installation (or afterwards booted in safe mode). OTA installing removes them automatically. Root patching installs them again.

This MBP is still doing very well as my daily working machine. Many thanks to the developers!

MBP11,1: likewise, installed 14.6.1 over 14.6 without problems.

 

[hvds]

Hi, Sonoma 14.6.1 works with OCLP? Please

just verified for an MBP11,1 (late 2013, 13").

What type of machine do you have? Which macOS is it currently running? which OCLP version?
Who should be able to answer your question with confidence on the day 14.6.1 is released, for so many different machines.
Apple would (have to) know for Apple-supported machines and test all of them prior to release. Also they know exactly what the changes are in the OS which makes testing easier. - I guess this is one of the reasons support has to end at some point for older models - else the total effort grows and grows.

So for our Apple-unsupported (OCLP supported) machines the advice would be to: either wait until someone has proven that it works for your hardware, or try yourself in a safe environment.
That could be: an external SSD with a clone of your current system onto which you install the new macOS, leaving your working SSD untouched. Preferentially install from a full installer rather than OTA from system settings (provides a better starting point for re-installation if something goes wrong). Then the post-install patches.
If this works well, install to your working SSD and patch it. (Anyway, backup the working SSD at least before any upgrades.)