Sidebar Sidebar
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

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 updated my MBP Mid 2012 (9,1) to Sequoia 15.2. So far things seem to work OK, however I have noticed a regression with Safari. On wunderground.com I can no longer see the weather radar. It's just blank. It still works on other browsers, but Safari doesn't seem to like it any more. This is the first time I've seen this issue.
 
  • Like
Reactions: OKonnel
The mbp9,1 got OTA'd to 15.2 successfully. Will keep an eye out for any unknown issues.

OTA to 15.2.png
 
  • Like
Reactions: deeveedee
Has anyone had trouble with bluetooth with the new 15.2 and OCLP 2.2.0? I am on a MBP 9,1 and bluetooth will not turn on or work. I've reset PRAM, reverted root patches and re-patched, all without success. Everything else is working great. Thanks for any help.
 
@tennismac In my limited testing (Bluetooth to speaker) Bluetooth works for me. But I don't have the same system, so the only thing I can say is that Bluetooth does / can work on an OCLP-patched Mac running Sequoia 15.2 patched with OCLP 2.2.0.

EDIT: @tennismac Did you "Build and Install Open Core" with OCLP 2.2.0 (different from applying post-install patches)?
 
Last edited:
deeveedee said:
@tennismac In my limited testing (Bluetooth to speaker) Bluetooth works for me. But I don't have the same system, so the only thing I can say is that Bluetooth does / can work on an OCLP-patched Mac running Sequoia 15.2 patched with OCLP 2.2.0.

EDIT: @tennismac Did you "Build and Install Open Core" with OCLP 2.2.0 (different from applying post-install patches)?
Click to expand...
yes. Thanks for your help, though. Under the 15.2 betas, all was well. It just stopped working with the final updates. Not sure what happened.
 
tennismac said:
Has anyone had trouble with bluetooth with the new 15.2 and OCLP 2.2.0? I am on a MBP 9,1 and bluetooth will not turn on or work. I've reset PRAM, reverted root patches and re-patched, all without success. Everything else is working great. Thanks for any help.
Click to expand...
I am using a bluetooth keyboard and airpods on my 9,1 with no issues. Have you tried resetting the SMC yet?

I also recall in an earlier thread, maybe the Sonoma one, someone mentioning some manual intervention with Hackintool and some bluetooth parameters that helped with some kind of bluetooth issue. I've never needed anything more than the usual PRAM and SMC resets on my machine for weird issues that came up.
 
  • Like
Reactions: K two, OKonnel and deeveedee
Kevo said:
I am using a bluetooth keyboard and airpods on my 9,1 with no issues. Have you tried resetting the SMC yet?

I also recall in an earlier thread, maybe the Sonoma one, someone mentioning some manual intervention with Hackintool and some bluetooth parameters that helped with some kind of bluetooth issue. I've never needed anything more than the usual PRAM and SMC resets on my machine for weird issues that came up.
Click to expand...
Thanks so much. That worked!
 
  • Like
Reactions: K two, luckyduke23, OKonnel and 1 other person
So you all installed MacOS 15.2 (24C101) with OCLP 2.2? Did OCLP download the matching metallib 24C101 somewhere even if it is not yet available for manual download on GitHub?
 
  • Like
Reactions: macpro_mid2014
PropClear said:
OCLP uses the closest match so metallib 24C100 will also be used for 24C101 without problemes - same behavior with the KDK if needed.
Click to expand...
Yes, I was just curious (and impatient). I have now installed 15.2 (24C101) with OCLP 2.2, and indeed, OCLP says it can't find the 24C100 metallib and has downloaded 24C100. As usual, I have the "gray screen phenomenon" during startup, but as I know by now, this disappears later when the background activities with the updates are finished. I'm happy to see that the Find My app is finally working again on my Mac, and with it the desktop widgets. So all other iCloud issues are probably fixed as well, as expected from the changelog info.

IMG_3617.jpeg
 
Has anyone tried Pixelmator Pro 3.6.13 on Sequoia 15.1.1 or 15.2 + OCLP 2.1.2 or 2.2.0?

Since this build; When launching the application, it has a popup warning that you need a Mac that supports Metal.
Works fine with Pixelmator Pro 3.6.12 / Sequoia 15.1.1 or 15.2 + OCLP 2.1.2 or 2.2.0.
 
Last edited:
  • Like
Reactions: Ready-for-Apple and OKonnel
Updated my MBP 11,3 without problems. The only thing that is bothering me is the inability to edit RAW files in Photos. I always get the "Cannot Start Editing - Photos cannot load edits. Please try again later" message. JPG files can be edited fine.
 
Hello to all,

A preamble: both of my computers are connected to Ethernet while updating system software, hence, loss of WiFi during installation is not relevant to the process.

iMac 13,2 (late 2012). Metal-capable

On the iMac I have to revert patches before the OTA update panel actually works properly (panel seems inactive or stalls mid process). Once rebooted without patches, OTA update offers delta update. The delta update process fails with an error message, but once error message is dismissed, and update button is clicked again, full installer is downloaded.

Installation proceeded without issues. Patching was also smooth; there was no request attempt by OCLP to download new Metalib package. However, I previously transplanted Metaliib folder, from an external drive running15.2RC to the iMac internal drive; the latter run Sequoia 15.2 - 24C100, so there was a Metalib resident when 15.2 - 24C101 was installed. See post #2072 or, for alternate method, Tom1211’s posts (above) regarding MetaLib package "fix".
Patching via OCLP 2.2 completed without issues; WiFi and Bluetooth were fully enabled.
Airdrop, Handoff, continuity and iPhone camera (e.g. FaceTime), all work as expected.


MacBook Pro 5,2. (2009). Non-metal (probably applicable to some other non-metal machines)

Requires external keyboard and mouse connected via external USB hub in order to complete installation and login; keyboard and track pad are fully functional once system is patched.

Process:
Downloaded 24C101 OTA, and patched with OCLP 2.2 (public release)
Installation went without problems and machine booted to desktop.

OCLP did “try” to download KDK for 24C101while patching, but process stalled. I quit the installer and downloaded KDK 24C101 from apple website. Installed it manually, then relaunched OCLP to complete patching. On reboot graphics acceleration worked, as did WiFi and Bluetooth. Keyboard backlight required SMC reset to work.

Again, superb work by developers and tester teams.

Hope this post may be of help.

MacBook Pro.png
iMac 13,2.png
 
Last edited:
  • Like
Reactions: K two, macpro_mid2014, roronl and 5 others
Neon Ball said:
Since it works on your other Macs, which are all on Haswell based CPUs, it may indicate a possiblity that the newer version is using AVX/AVX2. If that is the case, it is unfixable. Oldest CPUs with AVX are Sandy Bridge, Haswell for AVX2. I can't tell for sure but many old Macs (and PCs) are starting to age now with more and more applications moving to AVX2.

The GPU drivers for Polaris in fact require AVX2 since Ventura and that is the reason why downgraded drivers are needed for them to work on the Mac Pros, otherwise the GPUs would be fully native and wouldn't need root patching. Now it could of course also be an issue with these downgraded drivers, e.g. some incompatibility or a lacking feature.
Click to expand...
Thank you for this insightful explanation! This really hits the nail on the head and explains exactly what I'm experiencing.

The AVX2 dependency makes perfect sense because:
- The older version (5.521.0) works perfectly fine
- The new version crashes immediately at startup
- It works on my MacBook Pro (Haswell CPU with AVX2)
- It's a 3D modeling software that would benefit greatly from AVX2 instructions

This discovery might actually mark a significant turning point for Mac Pro 5,1 users. While OCLP has done an amazing job keeping our machines running modern macOS versions, the lack of AVX/AVX2 support represents a hardware limitation that no software patch can overcome. As both Apple and third-party developers increasingly rely on these CPU instructions in their frameworks and applications, we might be facing a gradual but inevitable decline in software compatibility.

Some examples where this might become relevant:
- Modern development frameworks (like newer versions of SwiftUI)
- 3D modeling and video editing software
- Future versions of creative applications
- Machine learning and AI tools
- Modern games and graphics applications

This doesn't mean our Mac Pros will stop working overnight, but it suggests that even with OCLP's excellent work, we're approaching a natural end-of-life situation - not because of macOS compatibility, but because of fundamental CPU architecture requirements in modern software.

I'll stick to using Shapr3D on my MacBook Pro or keep using the older version that still works, but this experience has helped me understand the longer-term implications for Mac Pro 5,1 usage.

Thanks again for helping me understand the root cause - this information will surely be valuable for other Mac Pro 5,1 users in planning their future upgrade paths.
 
Last edited:
  • Like
Reactions: F1Mac, deeveedee, TOM1211 and 5 others
Marfan-58 said:
iMac 14,2 updated to MacOS 15.2 with OCLP 2.2.0. All seems ok, but still can't render the Sequoia dynamic wallpaper.
Click to expand...
Ho @Marfan-58! We meet from time to time! :)
Sequoia's original / final dynamic background doesn't work, and if you're really interested you might be able to find the version distributed with the early betas around, since it's created in .HEIC format, like the earlier dynamic versions. (Or I can send it to you privately). But both the final version and the beta are very ugly, and maybe that's why our "Sir iMacs" refuse to start them ;):p:D
Instead, if you haven't noticed, the standard background with the Sequoia forest works just fine! It comes alive when you freeze the screen or wake it up from sleep and changes position in the Desktop.

That said, the only thing that worries me as I work is the Histogram malfunction in Preview and the bug that causes the image to disappear if you press "Auto Levels" or touch the two sliders at the ends.
Preview is an original and important part of macOS and I hope the OCLP’s Developers will fix this Metal issue (which the powerful Kepler video cards in our 14,2 iMacs can overcome), as they did with Chess, Music and FreeForm.

1734084391437.png
 
Last edited:
  • Like
Reactions: Marfan-58 and deeveedee
just installed my mbp early 2015 13" to sequoia 15.2 + oclp 2.2.0 and reminders and calendars widgets are not displaying infos. Am i the only one who's experiencing this? how can i fix this issue?
1734087287786.png
 
Alright so far everything has been running smooth on my 13,3 macbook pro touchbar late 2016. All except some issues with the photos app so far. opening the recently deleted items album it doesn't accept the password but if i use touch id it works. Not sure if it's an issue caused by OCLP or a general bug.
 
xlw108 said:
This discovery might actually mark a significant turning point for Mac Pro 5,1 users. While OCLP has done an amazing job keeping our machines running modern macOS versions, the lack of AVX/AVX2 support represents a hardware limitation that no software patch can overcome. As both Apple and third-party developers increasingly rely on these CPU instructions in their frameworks and applications, we might be facing a gradual but inevitable decline in software compatibility.
Click to expand...
It's indeed true not only for 5,1 Mac Pros but obviously 6,1 as well. Latest Photoshop cannot run on my 6,1, same with Premiere, they both require AVX2... The end of the road on this machine is Photoshop 2024 and Premiere 2023. When we think about it that is not surprising either, after all we have to expect compromises on 10+ years old computers. I am still amazed that it is actually possible to run Sequoia on this trusty trash can. I work mainly with audio software such as Pro Tools and Cubase, and this machine is still more than capable when it comes to making music. I don't blame Apple nor Adobe or any other company for "abandoning" compatibility with older machines, it is how it is.

OCLP developers are doing an amazing job for keeping our machines alive and current. Yet, keeping in mind that at some point it will be time to upgrade, Apple "intelligence" or not;)

On another note I installed 15.2 with the latest OCLP and it's running flawlessly. Thank you OCLP team!
 
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
Back