hvds
macrumors 6502a
MBP11,1 (Haswell) fine with 15.2db3 (24C5079e) / OCLP 2.1.2, on external SSD.
Installed from USB installer (a separate partition on the target SSD).
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 15 Sequoia on Unsupported Macs Thread
- Thread starter flagers
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Installed from USB installer (a separate partition on the target SSD).
Mystere65
macrumors regular
I figured it was the missing AVX
Those in here using a mid 2014 MacBook Pro can I ask does your Mac power on properly? e.g
On mine i log in see the desktop then it automatically powers down when unplugged
(im trying to work out if its because my battery is passed its best) if i plug it in after powering down 9/10 it just goes back to the desktop without having to log in again.
On mine i log in see the desktop then it automatically powers down when unplugged
(im trying to work out if its because my battery is passed its best) if i plug it in after powering down 9/10 it just goes back to the desktop without having to log in again.
macpro_mid2014
macrumors 6502a
The background of this is quite interesting:
This commit to the WebKit JavaScript engine is the reason for this AVX problem to happen: https://github.com/WebKit/WebKit/commit/c15e741266db8ff9df309ce9971eda1cfd9021cc
It removes the runtime check for the availability of the AVX instruction set on all macOS derived platforms, together with a comment which indicates that the runtime check was necessary for the lack of AVX support in Rosetta2 - leaving open the question why the check needed to be removed.
Further research reveals that with Sequoia AVX(2) support has actually been added to Rosetta2, so now all supported Apple platforms do support AVX.
Recompiling JavaScriptCore with that check readded shouldn't be difficult - but I don't know whether the compiled binary would be easy to get into the installed Safari/WebKit nowadays.
if you want to power on the mac even if no battery installed or if you are using non-OEM battery , enable "Disable Firmware Throttling" in OCLP and build the EFI .
if you have random shutdowns or can't get past the login screen , enable " Disable Thunderbolt" .
I've these 2 options enabled and all my problems related to Crashes/Random Shutdown/Throttling disappeared.
Thank you for nothing!
Apparently, newcomers are ignored here on purpose! No help or information!
Good luck here on the forum.
Apparently, newcomers are ignored here on purpose! No help or information!
Good luck here on the forum.
K two
macrumors 68020
PropClear
macrumors regular
say hello to 15.1.1 | 24B91
(iOS 18.1.1 etc also)
Update:
Legacy Mac’s updated so far OTA macOS 15.1 -> 15.1.1 24B91 with newest OCLP 2.1.2 final (KDK or MetallibSupportPkg when needed) without problems! MacPro 4,1 | 5,1 iMac 11,1 | 11,2 | 12,2 | 14,1 | 15,1 MacBookPro 6,2 | 10,1 | 11,1 | 12,1 | 14,1 | 14,2 MacBookAir 6,1 MacMini 6,1 | 6,2 | 7,1 👌
(iOS 18.1.1 etc also)
Update:
Legacy Mac’s updated so far OTA macOS 15.1 -> 15.1.1 24B91 with newest OCLP 2.1.2 final (KDK or MetallibSupportPkg when needed) without problems! MacPro 4,1 | 5,1 iMac 11,1 | 11,2 | 12,2 | 14,1 | 15,1 MacBookPro 6,2 | 10,1 | 11,1 | 12,1 | 14,1 | 14,2 MacBookAir 6,1 MacMini 6,1 | 6,2 | 7,1 👌
Last edited:
hvds
macrumors 6502a
MBP11,1: fine with 15.1.1 / OCLP 2.1.2. Installed from USB installer to internal SSD.
(For metallib, the post-install patching picked 24B2083 which belongs to 15.1 for the M4. Seems OK.)
Attachments
K two
macrumors 68020
macOS 15.1.1 installed atop 15.1 OTA, OCLP 2.1.2 runs as expected. 😎
👏
👏
macpro_mid2014
macrumors 6502a
Ok, I tested on my MBP11,2.
It does not power down, it goes to sleep because of the low battery (bad battery I assume). I also have a bad battery, but it can keep my Mac awake for around 5 minutes after a reboot.
Do you require a password immediately after it wakes up from sleep, or you have a delay (Require password after screen saver begins or display turns off) on System Settings -> Lock Screen?
no updated Metallib Package available here yet https://github.com/dortania/MetallibSupportPkg/releases I wonder if the 15.1.1. installations used it anyway...
Steve Gosselin
macrumors member
I haven't noticed this behavior with my mid-2014; When I unplug it, It does not power down. Same as macpro_mid2014, when the battery is low, it goes to sleep (with notification).
However, I did have the battery replaced about 3 years ago at Apple Store.
hvds
macrumors 6502a
Repeated the post-install patching. The directly matching metallib support package (24B91) is now present and used.
No difference noticed to 24B2083.
Attachments
Thing with mine is it can keep on battery for hours only if I boot it unplugged and log in it auto shuts down straight away. If I boot it plugged in log in wait a few minutes for everything to load then unplug it , it’s fine for hours. Disabling thunderbolt and firmware throttling still has the auto power down after log in . I’ll try changing the battery but wanted to ask on here first to see if it was a mid 2014 issue. Thanks everyone.
Sven G
macrumors 6502a
Everything OK with macOS 15.1.1 and OCLP 2.1.2, on my MBPs.
… BTW, talking about batteries, I, too, replaced the one in my MBP11,3 about two years ago (the built-in one was swollen); and the new one works perfectly (and is detected normally in System Information), even if of course from a third party (the Swiss LMP). Now, IIRC, someone said that, if you have a third party battery, it might be advisable to disable firmware throttling (probably required only for missing hardware), in the OCLP settings, for performance gains: but is this really true? Seems to be a little too extreme, maybe…
(See post below, by @samiqa: firmware version is ddae, so should be good. Thanks for the links.)
… BTW, talking about batteries, I, too, replaced the one in my MBP11,3 about two years ago (the built-in one was swollen); and the new one works perfectly (and is detected normally in System Information), even if of course from a third party (the Swiss LMP). Now, IIRC, someone said that, if you have a third party battery, it might be advisable to disable firmware throttling (probably required only for missing hardware), in the OCLP settings, for performance gains: but is this really true? Seems to be a little too extreme, maybe…
(See post below, by @samiqa: firmware version is ddae, so should be good. Thanks for the links.)
Last edited:
if your battery has Firmware Version: 2d31 you definitely should enable "Disable Firmware Throttling " .
you can refer to this post and dedicated thread for more info MacbookPro mid 2015 mds_stores or configd CPU high load .
Sven G
macrumors 6502a
Now it has been updated:
Release 15.1.1-24B91 · dortania/MetallibSupportPkg
Metal Library Patching Utilities. Contribute to dortania/MetallibSupportPkg development by creating an account on GitHub.
github.com
K two
macrumors 68020
RAMtheSSD
macrumors regular
You AREN’T being ignored, sometimes, the person that can help just hasn’t logged on in a couple of days and they are getting through their messages, etc…. The more unique the problem, the fewer people exist that can help. In that, the Mac community is blessed because there just aren’t that many differences relative to WinTel boxes. Hang in there, I don’t even know what is wrong with your machine yet —if anything.
RAMtheSSD
macrumors regular
Hello everyone 🙂 I am having what I hope is a simple problem that so many people have had that it was solved long ago. First, I need to confirm that a USB hub, regardless of the vintage, normally loads the AHCP? in Mac Pro 4 or 5,1; currently, mine stagnates even before there is an image on the monitor —the hub is 3.2 but the plug at the end of the cable is USB-A.
Second, the problem: Sequoia 15.1.1 —the security fix happened, the update prompt from OCLP happened as normal, but no actual reboot was needed.
A: It happens with every boot for an update on the Mac Pro since the first time I used OCLP; I do not get a choice of an update installer.
B: Choosing an option that was working fine —since the last update— either fails to boot and eventually goes to a reboot or, if it boots to the login screen, in a matter of seconds, the login screen goes away and some sort of error involving AHCP occurred and a few lines flash on the screen and there is a reboot, the chime, and the boot hangs until a PRAM reset wherein the cycle happens all over again.
C: On a MacBook Pro 6,2, I used the exact same install process and I get an update option and, for the life of me, I cannot figure out what’s different.
D: I used OCLP 2.2 for the installs
E:I am not on Discord because I feel that this has to be a problem with the Mac Pro in some way and that others have had this problem. In any case, while Discord adds to the knowledge of the moment, MacRumors adds to the knowledge base and people can look and find answers here that have gone into the aether long ago elsewhere.
I am starting to hate the whole update process, ContinuityCamera with all the whistles was working like a charm!
Second, the problem: Sequoia 15.1.1 —the security fix happened, the update prompt from OCLP happened as normal, but no actual reboot was needed.
A: It happens with every boot for an update on the Mac Pro since the first time I used OCLP; I do not get a choice of an update installer.
B: Choosing an option that was working fine —since the last update— either fails to boot and eventually goes to a reboot or, if it boots to the login screen, in a matter of seconds, the login screen goes away and some sort of error involving AHCP occurred and a few lines flash on the screen and there is a reboot, the chime, and the boot hangs until a PRAM reset wherein the cycle happens all over again.
C: On a MacBook Pro 6,2, I used the exact same install process and I get an update option and, for the life of me, I cannot figure out what’s different.
D: I used OCLP 2.2 for the installs
E:I am not on Discord because I feel that this has to be a problem with the Mac Pro in some way and that others have had this problem. In any case, while Discord adds to the knowledge of the moment, MacRumors adds to the knowledge base and people can look and find answers here that have gone into the aether long ago elsewhere.
I am starting to hate the whole update process, ContinuityCamera with all the whistles was working like a charm!