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
Not that I've seen, and I typically use Alfred instead of spotlight. I got Alfred years ago, when spotlight wasn't so great as a launcher, and finding certain things, and just stuck with it. With that said, neither one give me issues.
Does it quit permanently?. I know after any update, it's indexing the whole machine.. also photos is redoing things too. On older machines that really can bog it down for quite a while. I've also not noticed any issue after that's all done, but I'm also on Sonoma not Sequoia.. Sequoia doesn't work well enough for me on the 2012 or 2015 Air. I've stuck with Sonoma on those.
reverted patches updated to latest 15.7.2 (24G322) beta 950 mb (ish) went without issue on both my Mac mini and MacBook Pro 2014 .
While I haven’t watched the video (yet) one comparison video I would enjoy is apples claims of improved battery life e.g 10 more video hours vs a OCLP Mac battery life lol
Don’t know if anyone has tried VMware fusion 25 ?
getting just a black screen on windows VMware fusion 13.6.4 still works fine luckily there’s no auto update there.
getting just a black screen on windows VMware fusion 13.6.4 still works fine luckily there’s no auto update there.
I have the latest version of Fusion compatible with Monterey (13.5.2), and 13.6.4 for Sequoia. I pretty much gave up on Fusion after Broadcom bought it, as it just doesn't seem like the same program anymore, and things like the machine menu was removed on newer versions. Plus, since I have a stable install of Linux on an external drive, no real need for VMs anymore, but I keep it around for "just in case"
This is a known problem discussed in the Broadcom Fusion forum. As a temporary workaround you may go to the VM Advanced settings and set Troubleshooting to Hang/Crash.
Last edited:
If you used a USB made with OCLP it should be fine, otherwise a post install doesn't take long and should be done, if you do 15.7.2 OTA, OCLP will ask to post install at the end.
I have 3 macPros running Monterey OCLP 2.4.1 and all 3 of them suffer from this root patching issue. I've gone through this procedure on all three of them and got nowhere. Repeating it is probably pointless but nonetheless I've done so over a period of several months and it never, ever works. if I don't fix this soon I may be in danger of "failing sanity checks" myself. Any suggestions anyone?
Have you switched off automatic OS and security updates? That pretty much eliminates the issue AFAIK.
So you always make clear and aware decisions when you want to update. FWIW.
Was wondering if anyone seen any ill effect from the limitations of four core.
I strictly use my 5,1 running Sequoia, and Pro Tools.
I strictly use my 5,1 running Sequoia, and Pro Tools.
- Sequoia.
- CPU Limitation: If your Mac Pro has dual CPUs, only four cores will be usable due to compatibility issues. OpenCore automatically disables additional cores to prevent system panic.
My iMac 17,1 runs Monterey natively, if I'm understanding you right, you're having issues with updates. From what I've seen on my supported install, once you install 12.7.6, there haven't been any more OS updates for Monterey, the other updates are Safari, and Pro video formats, if you have the pro apps installed. Neither of the non OS updates should interfere with root patches. One thing you might want to do is, install Monterey, update to 12.7.6 then root patch after it's updated. Then you should be good to go. You could also disable auto updates, but in my experience there hasn't been anymore for Monterey.
Apple’s Motion app now crashes on MBP11,3 and OCLP’d macOS Sequoia 15.7.1: not immediately, but after clicking on Open in the Project Browser. Something similar to what described here:
Another infamous Nvidia Kepler issue, or something else maybe…? BTW, I don’t use Motion: just curious about the reasons for this unexpected behaviour…
Another infamous Nvidia Kepler issue, or something else maybe…? BTW, I don’t use Motion: just curious about the reasons for this unexpected behaviour…
I just posted to the thread linked above. Tested FCP 11.2 on my iMac 17,1 Sequoia 15.7.1, no crash upon import.
^^^ And your iMac doesn’t have an Nvidia card: sadly, there have often been problems with those graphics cards (especially with the Kepler one)…
I had posted on the Reddit thread, that I thought some of the older iMacs could have their graphics card changed by the user, or even use an eGPU, but wasn't sure if the ones in question here could do either.
