beta 3 working ok on a supported 2018 intel Mac mini8,1
Not installing 15.4 betas on any unsupported Macs at this point.
Not installing 15.4 betas on any unsupported Macs at this point.
Last edited:
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
I and others have run the same rMBP 2012 for some time now with Sequoia and after some time of settling down
(and unless I try to run anything with HVEC/H265, like the moving screensavers)
it runs very similar to Catalina IMHO.
Installed latest 15.4 beta, removed OCLP post-install root patch and reinstalled post-install root patch to apply the latest KDK (I could have just reinstalled post-install root patch but didn't want to risk something getting missed). So far so good on my specific machine.
Released 15.3.2 this is a minor update, has anyone tried it yet?
Not until I know the dual screens bug (see Apple Support Community) has been fixed.View attachment 2491117Runs as intended.👏
The point release to 15.3.2-24D81 on a rMBP 10,1 seems fine and no different so far to 15.3.1.
15.3.2-24D81 metal libs installed
The mandatory Silent Knight run downloaded some updates and activating the updates gave this in terminal after xprotect update:
Update succeeded: Activated update CloudKitUpdate[v5290 - current @ 2025-03-11 18:27:10 +0000]
FWIW.
15.3.2-24D81 metal libs installed
The mandatory Silent Knight run downloaded some updates and activating the updates gave this in terminal after xprotect update:
Update succeeded: Activated update CloudKitUpdate[v5290 - current @ 2025-03-11 18:27:10 +0000]
FWIW.
Last edited:
Thank you for reminding me to run Silent Knight. It's an invaluable tool.
Your are welcome
.. and to be clear for others, also afterwards type in the terminal: sudo XProtect update
to enable the updates that Silent Knight downloads. This seems mandatory for an optimised OCLP install
as I understand it, as the XProtect updates are typically not done automatically in this scenario.
Have a look at this: https://eclecticlight.co/2024/12/19/xprotect-has-changed-again-in-macos-sequoia-15-2/ Howard Oakly:
"Macs running 15.2 and later now get XProtect updates differently. Neither you nor SilentKnight can alter that, unless you want to try obtaining prerelease updates through the xprotect command in Terminal. While SilentKnight and Skint will warn you when an XProtect update is expected, you should rely on macOS to handle those updates for you."
I did the XProtect update on 15.3.1 after a week running stable. The MacBook Pro (see signature) has been slightly unstable since. Nothing a reboot does not fix, but before that I did not reboot often.
Last edited:
rMBP10,1 2012 updated from 15.3.1 to Sequoia 15.3.2 (24D81) + OCLP 2.2.0
OCLP auto-downloaded the Metallib new version when reapplying the post install root patches.
All is running well this morning for my current use cases.
OCLP auto-downloaded the Metallib new version when reapplying the post install root patches.
All is running well this morning for my current use cases.
I did this on my iMac and everything is fine now after battling the gray background issue again. I still have a black background for the login screen, but it does not affect performance.
Smooth sailing with 15.3.2... Update went without any issue and works great.
Good article, thanks! Not sure the part quoted above applies to OCLP-based Macs, as I remember the last time I read about this, you need to download in SN and then apply via terminal.
I guess that info could be out of date, but it appears to still work.
If someone knows more about best practice for XProtect on OCLP and Sequoia, a comment would certainly be appreciated.
Last edited:
Just updated my Sequoia USB installer this morning to 15.3.2 and booted from it to update my Sequoia APFS volume. Install went flawless, and everything works as it should. Also booted from my Sonoma APFS Volume, and applied the Safari update, and also that works as it should as well. So, my multi boot setup is still functioning as it should.
I'm using an iMac 17,1. Also wanted to mention that I went to the webgl site in both Sonoma, and Sequoia with the latest version of Safari, and all seems to be functioning as it should. I saw the rotating cube as expected both times.
I'm using an iMac 17,1. Also wanted to mention that I went to the webgl site in both Sonoma, and Sequoia with the latest version of Safari, and all seems to be functioning as it should. I saw the rotating cube as expected both times.
I use Lockrattler instead on my OCLP´d machines and do the Xprotect and other updates manually from time to time (or directly upon updating the OS). I guess it is a similar approach with SilentKnight, but I prefer the LR´s user interface (or got used to it earlier ;-)
MBP11,1: similarly positive experience.
With OCLP 2.2.0, metallib installation first failed, while it worked well with 2.3.0n.
Then removed the latest metallib from /Library/Application Support/Dortania, and 2.2.0 loaded it again and its installation worked as well. Maybe a temporary glitch.
(Didn't look any deeper, just that the error message is produced in gui_sys_patch_start.py after the metallib installation thread finishes. For this see install_metallib at end of metallib_handler.py)
Attachments
Last edited:
Thanks! How long did it take to settle down, can you remember? The moving screensavers definitely seem to be a resource hog. I've found temperatures so far to be 10-15 degrees higher than on Catalina, when doing regular tasks like web browsing and YouTube playback. I changed the thermal paste a few weeks back (and think I did a decent job) so it seems to be the extra pressure on the two cores of the i5 that's causing the extra heat.
Depends on the size of things like the photolibrary and how much you use spotlight. That might take a while to get done. Day or two. Media analysis (faces in photos and live text) can be switch off in settings/extras if fans bug you.
Spotlight can be tweaked to work less if that is ok with you in System settings/Spotlight.
Other than that, the main thing IMHO is that this rMBP, albeit great does not have hardware support for any video beyond H264 so if you don't like fans you need to stay away from H265/HVEC, including in sites like youtube.
That is a biggie IMHO.
Other than these tweaks and if they are ok with you, you should be good.
MBP11,1: 15.4b3 installed OTA over b2 to external SSD. Using OCLP 2.2.0 for patching, 2.3.0n gives same result. Running OK so far, including Photos.
Kernel Debug Kit 15.3.2 build 24D81 online right now - FYI
I'm trying to repurpose my daughters mid-2010 Macbook Pro (MBP 7.1) which now has 8Gb and new 500GB SSD and runs the last 'recommended/supported' High Sierra os but it's now getting clunky and several websites not loading properly, like the OCLP Assets can't be seen using native browser so having had to resort to some Firefox 115 version, made me realise i need to take the next steps and update the MacOS.....
So far so good, but I'm not an Apple/Mac man and whilst I'm happy to use OCLP 2.2 having done some research, I'm still unsure about the limitation warning that I get when deciding to download Sequoia and what the warning message about 'Legacy trackpad and keyboard' means in practice as I don't want to brick the laptop......OCLP installer suggesting only Monterey.......yet i see notes about patches which may resolve/mitigate ??......I've also seen reference to plugging in a USB2 hub (which I have) to get around the inbuilt USB1.1??
Appreciate some guidance please.......Thanks in advance
So far so good, but I'm not an Apple/Mac man and whilst I'm happy to use OCLP 2.2 having done some research, I'm still unsure about the limitation warning that I get when deciding to download Sequoia and what the warning message about 'Legacy trackpad and keyboard' means in practice as I don't want to brick the laptop......OCLP installer suggesting only Monterey.......yet i see notes about patches which may resolve/mitigate ??......I've also seen reference to plugging in a USB2 hub (which I have) to get around the inbuilt USB1.1??
Appreciate some guidance please.......Thanks in advance