macOS 14 Sonoma on Unsupported Macs Thread

[houser]

>> still have wake from sleep issues, no login window (spinning icon). Tried some OCLP options and sleep settings. But every the same when try to start. someone an idea how to solve this.

Known issue and is discussed here now and then. Manual sleep works if that is an option at times.

The man pmset terminal commands below can be used to set this if you know what you are doing.
Possibly/likely this varies somewhat with different Mac models.
If anyone has solid results with a combo of these I would also be all ears as I have been meaning to hunt
this down on my rMBP 10,1 2012. Other Macs I use do not have these issues, both older and newer.

Usual caveat: if your Mac explodes it is not my fault.

Check your settings (numbers are minutes, 0 means don't)) :

pmset -g

All options manual info for pmset:

man pmset

Reset all these to default to begin with or if you screw up and want to get back to a default starting point:

sudo pmset restoredefaults

Here are the individual ones (sudo needed to set):

sudo pmset -a displaysleep 3
sudo pmset -a autopoweroff 0
sudo pmset -a powernap 0
sudo pmset -a standby 0
sudo pmset -a proximitywake 0
sudo pmset -a tcpkeepalive 0
sudo pmset -a hibernatemode 0
sudo pmset -a disksleep 3
sudo pmset -a sleep 5

 

[Tom.Tom]

Look at the CHANGELOGs mid-page here: https://github.com/dortania/OpenCore-Legacy-Patcher/releases and see what changed which might effect your particular Mac. 👀

Well, it must be something else or some combination of actions, as I did the OCLP update again and the problem did not come back. I'll do some more testing and see what happens.

 

[houser]

Well, it must be something else or some combination of actions, as I did the OCLP update again and the problem did not come back. I'll do some more testing and see what happens.

Yes, I have also noted that sometimes redoing the same steps reg. OCLP for the update is needed and sometimes in safe boot. I see no pattern though.

 

[chevyboy60013]

It looks like 1.4.3 has not been released as of yet. Since the awesome crew at oclp does an awesome job, i'm sure it will be released shortly.

 

[rbart]

Surely, you jest. "Infinite loop detected"? On what machine, which version of Sonoma...? etc, etc.

The infinite loop is not on my Mac …

 

[mpbb]

Ok, that was unreasonable but since RogueB posted that his MBP5,2 was running fine under 1.4.3n, followed by a flurry of other validations, waiting more than 48h was just too much for me to handle the itching. So I've just done it and "of course" it just went fine. My MBP5,2 is running now 14.4 and performance on Geekbench is marginally on the up side: + 0,3% on both GB4 & GB5. Beware though: if you, like me, launched 1.4.3n in python3 from a ~/Developer folder as by the book, don't be fooled, as I was but still in time to realize it, by the pop-up window after the 14.4 install reboot asking you to apply the root patches. This window is launched by the 1.4.2 previously-installed standalone binary and will "revert" to the 1.4.2 root patch (since I had root-patched to 1.4.3n before the 14.4 install in order to "dry run" while still on 14.3.1). Dismiss it, go to your ~/Developer folder and do the right thing. Thanks again and again to the devs and namely to Edu "Super Mario" Covas.

P.S.: Geekbench 6 gives a "whopping" +2,54 % performance increase. With half-full glasses, that's +3%

 

[cab_007]

In my case (MBP11,1, 14.4, 1.4.3n) SilentKnight reports "XProtect assessments enabled" (as does spctl --status).

Weird, I had not turned XProtect off and toggling the Automatic Updates option for "Install Security Responses and system files" did not enable.

I had to manually invoke: sudo spctl --global-enable
Then checking with SilentNight (or command line via spctl --status), I'm back to Enabled.

 

[Izzy67]

Known issue and is discussed here now and then. Manual sleep works if that is an option at times.

The man pmset terminal commands below can be used to set this if you know what you are doing.
Possibly/likely this varies somewhat with different Mac models.
If anyone has solid results with a combo of these I would also be all ears as I have been meaning to hunt
this down on my rMBP 10,1 2012. Other Macs I use do not have these issues, both older and newer.

Usual caveat: if your Mac explodes it is not my fault.

Check your settings:

pmset -g

All options manual info for pmset:

man pmset

Reset all these to default to begin with or if you screw up and want to get back to a default starting point:

sudo pmset restoredefaults

Here are the individual ones (sudo needed to set):

sudo pmset -a displaysleep 3
sudo pmset -a autopoweroff 0
sudo pmset -a powernap 0
sudo pmset -a standby 0
sudo pmset -a proximitywake 0
sudo pmset -a tcpkeepalive 0
sudo pmset -a hibernatemode 0
sudo pmset -a disksleep 3
sudo pmset -a sleep 5

thanks for the info, tried it yesterday and this morning wake from sleep worked fine. Hope to stays this way.

 

[houser]

thanks for the info, tried it yesterday and this morning wake from sleep worked fine. Hope to stays this way.

Sounds good. Would you be so kind and tell us what setting fixed your issue?

 

[Izzy67]

thanks for the info, tried it yesterday and this morning wake from sleep worked fine. Hope to stays this way.

unfortunately it did not work, just tried to wake again and it hangs/freeze again at login screen, spinning icon.

 

[deeveedee]

... But unfortunately even with SIP disabled and sudo vi I was not able to modify or rename that file.
It says read only.
Is there anyone who can explain, how I could modify that file?

Did you ever find your answer? If not, you might want to look at 'writing to the system partition' in docs like this. Before you experiment, have a solid/reliable backup and a way to recover. You might even want to experiment in a duplicate APFS volume that won't risk your production volume.

 

[PropClear]

iOS 17.4.1 final just dropped let's see if macOS 14.4.1 will follow also today ;-)

 

[K two]

iOS 17.4.1 final just dropped let's see if macOS 14.4.1 will follow also today ;-)

Nope.🍋

 

[tennisproha]

Upgraded to OCLP 1.4.2 and then macOS 14.4. Now I get this message after every boot up?

 

[eSaF-Eddie]

Upgraded to OCLP 1.4.2 and then macOS 14.4. Now I get this message after every boot up?

View attachment 2361742

There is an easy fix for that.

To remove this message do this:

1. On Finder, goto /Library/Logs/DiagnosticReports

2. delete file shutdown_stall*

3. delete file wake*

4. or delete all files here for that matter.
Also here: /private/var/tmp/kernel_panics/staged.

It will clear the pop up message.
Good luck.

 

[K two]

Your intel Mac just increased in value. https://www.macintouch.com/post/38804/major-security-flaw-in-apple-silicon/ 🧐

 

[StefanAM]

Your intel Mac just increased in value. https://www.macintouch.com/post/38804/major-security-flaw-in-apple-silicon/ 🧐

@deeveedee after reading this, your concerns about wifi patch is silly.

 

[deeveedee]

@StefanAM Why?

 

[StefanAM]

@StefanAM Why?

It was a joke, man!

 

[deeveedee]

@StefanAM Ok, I wasn't sure. Hopefully the MIT researchers found the Mx Wi-Fi vulnerability before others who didn't have such good intentions.

EDIT: I'm very glad to see that security is no longer off-topic for this thread (although I won't test it ). According to this, Apple has reviewed the claims and "concluded this issue does not pose an immediate risk to our users and is insufficient to bypass operating system security protections on its own." I'm sure we'll be learning more about the M1/M2/M3 vulnerabilities Correction: Apple does not yet appear to have responded to this security flaw. A research paper is here.

EDIT2: This M1 Security Flaw is a good lesson about why computer security requires multiple lines of defense.

 

[K two]

Apologizing for opening this can-of-worms.🙅‍♂️

 

[LanceMahe]

I have an MBP 10.1 mid 2012. i7 4-core, 16GB ram, 750GB ssd. Running Big Sur very well.
I want to upgrade to Sonoma 14xx with the help of the latest OCLP, alas it doesn't work. The graphic cards are not compatible and
OCLP 1.4.2 does not resolve the issue. If anyone could advise me, I would be very happy.

 

[Paul Deemer]

Hardware Requirements:
Sonoma will likely require at least 25 GB of hard drive space available and will be most compatible on these models of Macs:

iMac (2019 and later)
Mac Pro (2019 and later)
iMac Pro (2017 and later)
Mac mini (2018 and later)
MacBook Air (2018 and later)
Mac Studio (2022 and later)
MacBook Pro (2018 and later)

Accordingly, the following models capable of running macOS Ventura will not be able to be upgraded to macOS Sonoma:

2015 MacBook Pro
2015 MacBook Air
2017 MacBook
2017 iMac
2015 Mac mini


Short Answer is your MacBook is too old and not compatible with Sonoma

 

[Bigwaff]

Should be supported. Why do you believe the GPU is not supported?

Supported Models | OpenCore Legacy Patcher

 

[DeltaMac]

Yes, your MBPro is a supported graphics card to upgrade to Sonoma (supported by OCLP, anyway)
Perhaps you are not following the steps to make your bootable installer, including adding the OpenCore EFI partition.
If you need a slightly newer version of the OCLP app now, you can get the current nightly build of OCLP quite easily here . (click on the link GUI (Graphical Based App) to download that nightly build, which is currently version 1.4.3)

The oldest Mac I am currently using is an early 2008 iMac, with Sonoma 4.3.1 I am waiting for OCLP to support next update to Sonoma 4.4.1 (which I predict will be released ASAP, due to the various issues that have been reported with Sonoma 4.4), but wait for a OCLP release that claims to add support for non-metal GPUs, if you like. But, OCLP should support your MacBookPro10,1 now, as it does have a "metal" GPU.
What is the actual error that you get when you try to install with the current OpenCore version?
Are you just running the Sonoma installer app while booted to your present system? or, are you booting to the Sonoma installer