macOS 14 Sonoma on Unsupported Macs Thread

[davidlv]

After testing on an Apple M2, this issue is most likely Sonoma related.

On my iMac 15,1, booting Sonoma 14.0 with the latest OCLP 1.0.1, I have noticed the available SSD disk space decreased until it was missing about 12-15GB (about 54GB left available, but it should be 67GB+ or so). As the Apple blade SSD is only 128GB to start with, I was getting worried and booted to Ventura on an external Crucial 512GB SSD connected by USB. Disk Utility showed over 10 APFS snapshots, most about 2.5GB in size. I was able to delete all but the latest 2, which were smaller, about 350MB. So after rebooting to Sonoma on the internal Apple blade, my available disk space was restored!
Do you know how I can prevent the formation of those snapshots?
I have seen a setting in CCC that turns off snapshots, but nothing in the OS system preferences, at least as far as I know. I have known for some time that using Onyx, set to erase the Time Machine snapshots, and the following Terminal code;
Code: sudo tmutil thinLocalSnapshots / 10000000000 4
That you can usually regain space lost to Time Machine snapshots, but in this case, that code didn't work.
This is probably a OCLP/Sonoma related issue.

 

[Potsdamer]

I want to report three 15" MacBook Pro 11,5 Mid 2015 with Sonoma 14.0 using OCLP 1.0.0 being no problem, but after updated to OCLP 1.0.1 all 3 MacBook Pro in reboot process go to black screen. I used the code in Troubleshooting/

Stuck on boot after root patching ​

, and tried to apply OCLP 1.0.0, but they are the same, went to black screen as using OCLP 1.0.1.
Do we have any solution?
Thank you for all supporting!
Best,

​

 

[ThommiTechnik]

Thanks for your feedback. So I'll have to investigate further...

For those, who might have the same phenomena: go into System Preferences -> Trackpad. In the third tab (More gestures) unmark the first point (Turn pages), and mark it again. Voila, working swiping pages in Safari is back

 

[jshayya0184]

I'm still having widget-related (missing/blank things) issues on my 2017 MacBook Air with the Broadwell iGPU. (Intel HD Graphics 6000) Is this still a know issue? Here's what I mean:

 

[alfon_sico]

How could I confirm if mediaanalysisd is working?. After all night with Mac and photos on, idle status, still doesn't find any face or pet in my library

 

[muhal44]

Hi. Did you find any solution???. If you find any solution please share with me.

I saw a similar issue at the address below. They revealed the problem and fixed it for Intel cards. Maybe experts on the subject will take inspiration from this and solve it for broadcam as well.

macOS Sonoma Support · Issue #883 · OpenIntelWireless/itlwm

Intel Wi-Fi Drivers for macOS. Contribute to OpenIntelWireless/itlwm development by creating an account on GitHub.

github.com

My card is broadcom. I haven't solved my problem yet. However, they made a regulation for the OpenIntelWireless kext used for Intel cards and suggested it as a solution. If your card is Intel, you can find the installation of kexts at https://github.com/OpenIntelWireless and the Modified kext is available at https://github.com/OpenIntelWireless/itlwm/issues/883#issuecomment-1625204187.

Problem solved with Sonoma 14.1 (Beta 2) and OCLP 1.1.0

Hi. Did you find any solution???. If you find any solution please share with me.

I saw a similar issue at the address below. They revealed the problem and fixed it for Intel cards. Maybe experts on the subject will take inspiration from this and solve it for broadcam as well.

macOS Sonoma Support · Issue #883 · OpenIntelWireless/itlwm

Intel Wi-Fi Drivers for macOS. Contribute to OpenIntelWireless/itlwm development by creating an account on GitHub.

github.com

Problem solved with Sonoma 14.1 (Beta 2) and OCLP 1.1.0

 

[Sven G]

From the OCLP website:

OpenCore Legacy Patcher​

Experience macOS just like before

Getting Started→

Built with security in mind​

Supporting System Integrity Protection(SIP), FileVault 2, .im4m Secure Boot and Vaulting. For many machines, you're just as secure as a supported Mac.

[…]

So, after all these interesting - but also a little alarming - discussions on security, maybe it would be a good thing to have some form of official statement on the OCLP security situation and also some form of roadmap towards its improvement in the future…? Just an idea…

(For example, why can’t the restricted filesystem be re-enabled after root patching, in Ventura and Sonoma? In Monterey, this worked fine, but in Ventura (haven’t yet tried in Sonoma) it lead to Window Server crashes and also problems with Safari rendering webpages, IIRC. Why this? Could this, among other things, be improved upon? It would also be interesting to have more in-depth explanations in the guide, other than “in root patched Ventura SIP can’t be enabled outright”.)

 

[amaze1499]

How could I confirm if mediaanalysisd is working?. After all night with Mac and photos on, idle status, still doesn't find any face or pet in my library

Same experience here. It took ages, well let's say days, before any results showed up in photos. Photos deserves an overhaul for sure. Overall its pretty slow on even an M2.

 

[amaze1499]

I'm still having widget-related (missing/blank things) issues on my 2017 MacBook Air with the Broadwell iGPU. (Intel HD Graphics 6000) Is this still a know issue? Here's what I mean:

View attachment 2289053View attachment 2289054
View attachment 2289052

Which patcher version did you use? Those exact same issues went away on my machine after building a new open core and applying root patches using OCLP 1.0.1.

Having said that, this machine 9,2 is running 23B5056e though.

 

[Kokko78]

Mac mini (2012) updated with clean install to macOS Sonoma 14 and OCLP 1.0.1, all Ok.

 

[iMac-Oldschool]

I want to report three 15" MacBook Pro 11,5 Mid 2015 with Sonoma 14.0 using OCLP 1.0.0 being no problem, but after updated to OCLP 1.0.1 all 3 MacBook Pro in reboot process go to black screen. I used the code in Troubleshooting/

Stuck on boot after root patching ​

, and tried to apply OCLP 1.0.0, but they are the same, went to black screen as using OCLP 1.0.1.
Do we have any solution?
Thank you for all supporting!
Best,

​

Same problem with Sonoma 14.0 and Ventura 13.5.2 on an iMac 13,1 late 2012. After following the instructions in Troubleshooting, the systems booted, but without root patches and video acceleration.

There is also an external HDD attached via USB 2 running Sonoma 14.1. beta (23B5046f) which boots without problems, albeit very slowly. Only obvious problem is repeated logd errors on startup. I don't want to install beta software on the fusion drive and can only suggest waiting for the full release of 14.1.

 

[PoloHofer]

I want to report three 15" MacBook Pro 11,5 Mid 2015 with Sonoma 14.0 using OCLP 1.0.0 being no problem, but after updated to OCLP 1.0.1 all 3 MacBook Pro in reboot process go to black screen. I used the code in Troubleshooting/

Stuck on boot after root patching ​

, and tried to apply OCLP 1.0.0, but they are the same, went to black screen as using OCLP 1.0.1.
Do we have any solution?
Thank you for all supporting!
Best,

​

Updated 15" MacBook Pro 11,5 Mid 2015 to OCLP 1.01, computer boots without problems

 

[OKonnel]

From the OCLP website:

OpenCore Legacy Patcher​

Experience macOS just like before

Getting Started→

Built with security in mind​

Supporting System Integrity Protection(SIP), FileVault 2, .im4m Secure Boot and Vaulting. For many machines, you're just as secure as a supported Mac.

[…]

So, after all these interesting - but also a little alarming - discussions on security, maybe it would be a good thing to have some form of official statement on the OCLP security situation and also some form of roadmap towards its improvement in the future…? Just an idea…

(For example, why can’t the restricted filesystem be re-enabled after root patching, in Ventura and Sonoma? In Monterey, this worked fine, but in Ventura (haven’t yet tried in Sonoma) it lead to Window Server crashes and also problems with Safari rendering webpages, IIRC. Why this? Could this, among other things, be improved upon? It would also be interesting to have more in-depth explanations in the guide, other than “in root patched Ventura SIP can’t be enabled outright”.)

Really good question, @Sven G 😊
But a proverb teaches us that “you can’t have your cake and eat it too” (in Italian: "you can't have a barrel of wine full and your wife drunk")
Jokes aside, I hope your well-formulated question can stimulate someone to search and find a solution.

 

[mwidjaya]

But a proverb teaches us that “you can’t have your cake and eat it too”

You can't make an omelette without breaking a few eggs.

 

[MacNB2]

acceleration seems to work. seeing as i dont need bluetooth or the wifi because im hardwired and i dont need bluetooth for anything i turned it off, but upon start up it asked me to engage bluetooth but i opted not to

macOS GUI accelerations work...but maybe what @blauesliebe7 may be was asking (correct me if I am wrong) does H/W accelerations of Video decoding & encoding work ?. That is, with your RX 580 GPU :

1. e.g. can you play 4K HVEC or H.264 video clips without any significant CPU load ?
2. can you Encode any video clips to HEVC codec without any significant CPU load ?

That is, the RX 580 should doing all that work of Decoding and Encoding to confirm H/W Accelerations is working.

 

[MacNB2]

From the OCLP website:

Built with security in mind​

Supporting System Integrity Protection(SIP), FileVault 2, .im4m Secure Boot and Vaulting. For many machines, you're just as secure as a supported Mac.

That statement is true "For many machines" that do not require Root Patching.

Just run EtreCheck after installing OCLP and it will show your security issues if any.

 

[jshayya0184]

Which patcher version did you use? Those exact same issues went away on my machine after building a new open core and applying root patches using OCLP 1.0.1.

Having said that, this machine 9,2 is running 23B5056e though.

Using version 1.0.1 release, and 14.0 23A344. Did I have to revert root patches before applying the new ones when updating from OCLP 1.0.0 to 1.0.1?

 

[Sven G]

That statement is true "For many machines" that do not require Root Patching.

Just run EtreCheck after installing OCLP and it will show your security issues if any.

Well, that’s easy to know also without EtreCheck: currently, on a root patched machine with Ventura or Sonoma, SIP by default is lowered to 0x803. As for wider, non-SIP security issues, the question remains open (and probably much more difficult to assess)…

 

[Sven G]

Really good question, @Sven G 😊
But a proverb teaches us that “you can’t have your cake and eat it too” (in Italian: "you can't have a barrel of wine full and your wife drunk")
Jokes aside, I hope your well-formulated question can stimulate someone to search and find a solution.

In English, that would probably be “you can't have your cake and eat it too” (“non puoi avere la botte piena e la moglie ubriaca”)…

Anyway, with AMFIPass the devs succeeded in making something previously almost impossible: so, maybe there could be similar improvements also on the security front, who knows…

 

[deeveedee]

That statement is true "For many machines" that do not require Root Patching.

Just run EtreCheck after installing OCLP and it will show your security issues if any.

@OKonnel @Sven G I had forgotten about this security claim in the OCLP docs. This combined with how easy OCLP is to use make it even more important to have a data security warning displayed by OCLP during installation/patching and then each time the OCLP-patched Mac boots. When OCLP goes mainstream to Intel Mac users, most of whom will never read the docs and see this forum, it is only fair that they are alerted to the potential risks.

The warning displayed by OCLP during installation/patching and then again at each macOS boot should not in anyway change the fact that OCLP is performing a miracle (and breaking some eggs to make an omelette). It's a courtesy to users which allows them to make an informed decision. I hope that the Devs accept this recommendation and incorporate the warnings into this wonderful product.

EDIT: Without the addition of data security warnings, the unsuspecting user of OCLP will see "Built with security in mind" and "Experience macOS just like before." Those statements in OCLP documentation aren't saying "your data and identity are not as safe as they are on a fully-supported Apple Mac."

 

[MacinMan]

I am curious, on a patched install, is it still possible to run csrutil as it would on a supported OS to just disable SIP completely? Since the system has to be patched anyway to run on the unsupported machines, I would like to turn off all the Apple specific security stuff in that area, and just use the standard UNIX security UNLESS doing so would prevent software from running correctly. I know using crsutil doesn't affect software running on a fully supported OS, but what about the patched ones? Basically can I disable the security stuff from within the OS now, and not worry about having to use the patcher to do it.

Thanks

 

[deeveedee]

I am curious, on a patched install, is it still possible to run csrutil as it would on a supported OS to just disable SIP completely?

You could, but this breaks things. For example, with SIP disabled completely, you won't receive Apple OTA updates. The Devs chose their SIP setting very carefully to make sure that only enough was disabled to permit OCLP/Open Core to work.

See Khronokernel's blog here.

 

[MacinMan]

You could, but this breaks things. For example, with SIP disabled completely, you won't receive Apple OTA updates. The Devs chose their SIP setting very carefully make sure that only enough was disabled to permit OCLP/Open Core to work.

OK. As a whole, I'm not real familiar with SIP and what it controls. The main reason I've disabled it in the past was to make changes in the filesystem to parts it prohibits such as in system and other parts. Simply using sudo while SIP is on isn't enough it has to be disabled for full access to the filesystem, so that's the context I was asking in.

 

[MacNB2]

Well, that’s easy to know also without EtreCheck: currently, on a root patched machine with Ventura or Sonoma, SIP by default is lowered to 0x803. As for wider, non-SIP security issues, the question remains open (and probably much more difficult to assess)…

Agreed.
The point was, that OCLP statement is only applicable to unsupported Mac's not running Ventura or Sonoma (since all the systems with these latest OS's require their security to be lowered to enable Root patching).

Many non-techinal users are using OCLP purely with the belief that they need to run the latest OS so that receive all the Apple security fixes/updates without realising that they would, ironically, be reducing their security in order to run these latest OS's.

It a case of "Buyer be aware".

 

[deeveedee]

OK. As a whole, I'm not real familiar with SIP and what it controls. The main reason I've disabled it in the past was to make changes in the filesystem to parts it prohibits such as in system and other parts. Simply using sudo while SIP is on isn't enough it has to be disabled for full access to the filesystem, so that's the context I was asking in.

Ok - now that you are using OCLP, your Mac is booting with Open Core. It would be good for you to learn how Open Core's config.plist can be modified to disable SIP. When you modified the OC config.plist, SIP settings will be configured as desired at each boot.

EDIT: In your Open Core config.plist, look for this: