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.
I

Izzy67

macrumors newbie
Oct 21, 2015
10
3
After upgrade to Sonoma 14.4 OCLP 1.4.2 i had wake from sleep issues (black screen fan running high), Did a complete reinstall Sonoma 14.4 with OCLP 1.4.2 (no recovery), but 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.
Have 5K imac 2014, i7, 32 gb ram, AMD Radeon R9 M295X GPU, 1TB Fusion drive.
someone an idea how to solve this.
 
H

houser

macrumors 6502
Oct 29, 2006
401
527
Izzy67 said:
>> 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.
Click to expand...
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)) :
Code: 
pmset -g

All options manual info for pmset:
Code: 
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:
Code: 
sudo pmset restoredefaults

Here are the individual ones (sudo needed to set):
Code: 
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
 
Last edited:
  • Like
Reactions: tsialex, K two, roronl and 2 others
H

houser

macrumors 6502
Oct 29, 2006
401
527
Tom.Tom said:
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.
Click to expand...
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.
 
C

chevyboy60013

macrumors 6502
Sep 18, 2021
457
242
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.
 
mpbb

mpbb

macrumors member
Jun 15, 2014
39
36
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.
Sonoma@MBP.png

P.S.: Geekbench 6 gives a "whopping" +2,54 % performance increase. With half-full glasses, that's +3% :cool:
 
Last edited:
  • Like
Reactions: K two and hvds
C

cab_007

macrumors regular
Dec 11, 2020
150
203
hvds said:
In my case (MBP11,1, 14.4, 1.4.3n) SilentKnight reports "XProtect assessments enabled" (as does spctl --status).
Click to expand...
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.
 
  • Like
Reactions: JedNZ and hvds
I

Izzy67

macrumors newbie
Oct 21, 2015
10
3
houser said:
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:
Code: 
pmset -g

All options manual info for pmset:
Code: 
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:
Code: 
sudo pmset restoredefaults

Here are the individual ones (sudo needed to set):
Code: 
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
Click to expand...
thanks for the info, tried it yesterday and this morning wake from sleep worked fine. Hope to stays this way.
 
  • Like
Reactions: houser
I

Izzy67

macrumors newbie
Oct 21, 2015
10
3
Izzy67 said:
thanks for the info, tried it yesterday and this morning wake from sleep worked fine. Hope to stays this way.
Click to expand...
unfortunately it did not work, just tried to wake again and it hangs/freeze again at login screen, spinning icon.
 
deeveedee

deeveedee

macrumors 65816
May 2, 2019
1,449
2,111
Peoria, IL United States
TommesPommes said:
... 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?
Click to expand...
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.
 
  • Like
Reactions: m4v3r1ck
eSaF-Eddie

eSaF-Eddie

macrumors newbie
May 4, 2023
15
29
tennisproha said:
Upgraded to OCLP 1.4.2 and then macOS 14.4. Now I get this message after every boot up?

View attachment 2361742
Click to expand...
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.
 
  • Like
  • Love
Reactions: olad, macpro_mid2014, amaze1499 and 5 others
deeveedee

deeveedee

macrumors 65816
May 2, 2019
1,449
2,111
Peoria, IL United States
@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.
 
Last edited:
  • Like
Reactions: retiarius, olad, macpro_mid2014 and 1 other person
L

LanceMahe

macrumors newbie
Nov 14, 2010
27
5
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.
 
P

Paul Deemer

macrumors member
Dec 17, 2023
54
58
Greenville, SC
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
 
  • Wow
  • Angry
Reactions: K two and rehkram
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