macOS 14 Sonoma on Unsupported Macs Thread

[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:

 

[MacinMan]

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:
View attachment 2289127

I'll look into that. I just want to use macOS as any other Unix OS with the exception of the Mac Desktop. That's really what I've wanted from the beginning after getting used to the UNIX operating system. I didn't really make a big deal on supported Macs and pretty much just used Apple's defaults. Now that Apple no longer supports this configuration, I would like to be a bit more open in how I use and configure the OS as long as it won't break things, and maybe use it with a more standard Unix Config without all the Apple specifics unless absolutely necessary for things to work.

So, I'll look over the settings and learn what each does before changing anything. Thanks.

 

[deeveedee]

@MacinMan Your Open Core config.plist is overwritten each time you "Build and Install Open Core" with OCLP. You can configure SIP in the OCLP GUI before you generate a new Open Core EFI (eliminating the need to manually edit your OC config.plist). Use Khronokernel's blog to know what each bit does.

 

[deeveedee]

Do you know how I can prevent the formation of those snapshots?

I've done it before, but it's been a while. It's a configuration that you can search for. Google might be your friend.

 

[MacinMan]

@MacinMan Your Open Core config.plist is overwritten each time you "Build and Install Open Core" with OCLP. You can configure SIP in the OCLP GUI before you generate a new Open Core EFI (eliminating the need to manually edit your OC config.plist). Use Khronokernel's blog to know what each bit does.

Looking at it now, and yes, was aware I could change settings, rebuild and install the boot loader. Thanks again.
EDIT: OK, I have a better understanding now. I will decide what I need on and off and set accordingly.

 

[davidlv]

I've done it before, but it's been a while. It's a configuration that you can search for. Google might be your friend.

The related Google search (prevent Time Machine snapshots) refers to Time Machine settings (options, etc.) that are (so far in my experience) impossible to find in Sonoma (or even Ventura if I am not mistaken).
I vaguely remember seeing them in an older OS (maybe Mojave?).
Thanks for the tip anyway.

 

[Sven G]

@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."

This hypothetical warning, however, should be easy to disable for power users (in the same way that you can easily disable the boot picker): personally, I would be quite annoyed by a warning at every boot…

 

[INK1]

Just installed Sonoma 14.0 on my iMac 27" from 2010. Windows 11 in Parallels 14.3.2. Everything seems to be working ok, however I can only boot using USB with OCLP 1.0.0. Tried updating to OCLP 1.0.1, but the iMac get stuck booting. Tried booting from internal SSD also using OCLP 1.0.1 - not working

 

[Sven G]

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

Personally, I’d rather prefer to have SIP enabled as much as (im)possible; also many Linux distros are slowly becoming of the “immutable” kind, that is similarly to macOS’s SSV, with the core OS not modifiable: so, the future seems to be more and better security, not only for macOS but also for other OSes.

 

[deeveedee]

This hypothetical warning, however, should be easy to disable for power users (in the same way that you can easily disable the boot picker): personally, I would be quite annoyed by a warning at every boot…

Agree that the "warning at boot" should be configurable. Would you agree that the warning during OCLP upgrade/install/patching should not be disabled and should appear every time?

EDIT: Of course, you could always just fork your own version that does not have the warning. 🤣

 

[Sven G]

Agree that the "warning at boot" should be configurable. Would you agree that the warning during OCLP upgrade/install/patching should not be disabled and should appear every time?

That sounds quite reasonable…

 

[Potsdamer]

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

Updated two 15" MacBook Pro 11,5 Mid 2015 to Sonoma 14.1 Beta 1 and OCLP 1.0.1, computers boot with the same problems, going to black screens. Any suggestion?

 

[deeveedee]

One other suggestion for OCLP... OCLP GUI allows submitted analytics to be enabled/disabled via a slider. If analytics are enabled, I'd like to see the analytics that are being submitted to OCLP Devs in the same way that macOS lets me view a crash report before it is submitted to Apple.

 

[MacinMan]

Personally, I’d rather prefer to have SIP enabled as much as (im)possible; also many Linux distros are slowly becoming of the “immutable” kind, that is similarly to macOS’s SSV, with the core OS not modifiable: so, the future seems to be more and better security, not only for macOS but also for other OSes.

I'll have to look into that. Wasn't aware that was being included in more Linux Distros.

 

[mikelets456]

I updated my 11,4 (MBP mid 2015) and 5,5 (MBP Mid 2009) with OCLP 1.0.1 and Sonoma 14.0---My thoughts on the 5,5 that was updated to 8 GB ram and 1TB SSD:

--It took a little to get this running properly (needed a 3.0 USB hub, usb mouse and usb keyboard). I installed via USB installer 1.0.0 then downloaded 1.0.1. There was a KDK package that took a while to install that fixed all the problems.
I have Wifi, keyboard, touchpad, etc. Maps still doesn't work, but that's okay. Photos, music, etc all work.

--I've only used 14.0 for about a day so it has to settle in, but I believe 1.0.0 (1.0.1) and Monterrey are the better combination for my 5,5.

 

[MacinMan]

Just thought I would mention that I just tried the latest version of the Second Life Viewer on Sonoma running on my late 2015, iMac patched with OpenCore 1.0.1, ran perfectly and graphics performance was good. So, anyone who plays around with Second Life should be OK.

 

[deeveedee]

There have been questions asked earlier in this thread about when Apple will discontinue Intel-based Mac support. Could someone check my logic here? ...

We just received a Big Sur update from Apple and Apple is still publishing Safari updates for Big Sur. Big Sur was released in 2020. It is 2023. If Apple discontinues Intel support in a macOS release 2-3 years from now, that means that Apple will be supporting Intel-based Macs for another 5-6 years. That's a long life expectancy for OCLP. And there will certainly be users who use their OCLP-patched Macs well beyond the end of Apple's official support.

It's not unreasonable to expect that OCLP could enjoy a life expectancy of 10 years. By that time, I would expect that the OCLP penetration into the large number of Intel-based Macs would be quite substantial (no longer a "small project").

 

[MacinMan]

There have been questions asked earlier in this thread about when Apple will discontinue Intel-based Mac support. Could someone check my logic here? ...

We just received a Big Sur update from Apple and Apple is still publishing Safari updates for Big Sur. Big Sur was released in 2020. It is 2023. If Apple discontinues Intel support in a macOS release 2-3 years from now, that means that Apple will be supporting Intel-based Macs for another 5-6 years. That's a long life expectancy for OCLP. And there will certainly be users who use their OCLP-patched Macs well beyond the end of Apple's official support.

It's not unreasonable to expect that OCLP could enjoy a life expectancy of 10 years.

As far as I know, 11.7.10 was the last update for Big sur. If there was newer, I don't know about it, but the speculation in the community of Apple users it's the last. Especially since Sonoma is out now.

 

[deeveedee]

As far as I know, 11.7.10 was the last update for Big sur. If there was newer, I don't know about it, but the speculation in the community of Apple users it's the last. Especially since Sonoma is out now.

I believe you are correct, but my question wasn't about the life expectancy of Big Sur.

 

[MacinMan]

I believe you are correct, but my question wasn't about the life expectancy of Big Sur.

We can still somewhat calculate your other question based on that. Monterey will end support next year, and so on. Apple originally said 2 years for the Apple Silicon transition. So, it seems like Apple is killing off more and more intel Macs each release. macOS 15 could be the last intel supported macOS, or even Sonoma since there are so few intel macs left on native support.

 

[PoloHofer]

Updated two 15" MacBook Pro 11,5 Mid 2015 to Sonoma 14.1 Beta 1 and OCLP 1.0.1, computers boot with the same problems, going to black screens. Any suggestion?

I am not an expert, but maybe this can help. Though it's for Monterey and Macbook 11,3:

Black Screen on MacBookPro11,3 in macOS Monterey​

Due to Apple dropping NVIDIA Kepler support in macOS Monterey, MacBookPro11,3's GMUX has difficulties switching back to the iGPU to display macOS correctly. (opens new window)To work-around this issue, boot the MacBookPro11,3 in Safe Mode and once macOS is installed, run OCLP's Post Install Root Patches to enable GPU Acceleration for the NVIDIA dGPU.

• Safe Mode can be started by holding Shift + Enter when selecting macOS Monterey in OCLP's Boot Menu.

another idea: -reset PRAM an VRAM

last idea: Start from another disk: Are the KDKs in Library Developper still there? (KDK_14.0_23A5337a.kdk)

Remember: I'm not an expert. That's what I would do.

 

[deeveedee]

We can still somewhat calculate your other question based on that.

Great! Please perform your own calculation and see if you agree with my projected 5-6 years of Intel-based Mac support. I trust you, so I don't need to see your work

 

[MacinMan]

Great! Please perform your own calculation and see if you agree with my projected 5-6 years of Intel-based Mac support. I trust you, so I don't need to see your work

Well, we're talking Apple here too, so anything can happen.

 

[Potsdamer]

I am not an expert, but maybe this can help. Though it's for Monterey and Macbook 11,3:

Black Screen on MacBookPro11,3 in macOS Monterey​

Due to Apple dropping NVIDIA Kepler support in macOS Monterey, MacBookPro11,3's GMUX has difficulties switching back to the iGPU to display macOS correctly. (opens new window)To work-around this issue, boot the MacBookPro11,3 in Safe Mode and once macOS is installed, run OCLP's Post Install Root Patches to enable GPU Acceleration for the NVIDIA dGPU.

• Safe Mode can be started by holding Shift + Enter when selecting macOS Monterey in OCLP's Boot Menu.

another idea: -reset PRAM an VRAM

last idea: Start from another disk: Are the KDKs in Library Developper still there? (KDK_14.0_23A5337a.kdk)

Remember: I'm not an expert. That's what I would do.

Thank you for your assistance!
I have tried boot in Safe Mode, but they went not through.
-reset PRAM an VRAM did not help, the same going too black greens.
I think KDKs are still there, it depends on Developer, take out or let there. I'm not an expert, too. Thank you so much!

 

[emmab2006]

Such a shame that doing this on a 2017 Macbook Pro with a T1 chip Basically destroys the machine if you downgrade it. Hopefully there will be some way in the future to not destroy the T1 Chip and let us run Sonoma. I think everyone who contributes to this project is amazing. What you guys do is amazing!