Yes, exactly the same crash in a newly created admin test account: so, it looks like it’s something system-wide…
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
Long story short:
We are running on a 2012/13 Intel with OCLP:
- MetalOld.dylib, CoreImageOld.dylib, CoreWLANOld.dylib, plus AppleIntelHD4000GraphicsMTLDriver.
- We are using OCLP’s compatibility layers to expose modern Metal on HD4000 (officially unsupported).
Motion 5.11 + Helium 3.1.0 use compute pipelines; the shim/driver combo borks the encoder lifecycle and the debug layer calls abort(). - Earlier trace also showed: CoreFoundation: doesNotRecognizeSelector:
Helium: HGMetalFunctionCache::_createFunctionWithSource(...)
Suggestion: Upgrade your hardware or wait for OCLP to fix it.
Last edited:
^^^ And, as I mostly use my old MBP11,3 in clamshell mode with an external display, this evidently happens also with its Nvidia Kepler dGPU, which was in use in this case. Anyway, not an urgent issue (which, BTW, I discovered only because I reinstalled the software): if it is easily fixable by the OCLP devs, good; if not, it can definitely wait…
(Edit: I tried in all GPU modes (integrated-only, discrete-only and with automatic switching): but Motion crashes every time, in any configuration.)
(Edit: I tried in all GPU modes (integrated-only, discrete-only and with automatic switching): but Motion crashes every time, in any configuration.)
Last edited:
… BTW, when reinstalling everything, I also tried different forms of Boot Camp installs, to see if my old MBP11,3 still is compatible with natively booting Windows 11 (of course after bypassing the TPM, etc. checks, if necessary)… Well, installing on an external Kingston Windows To Go USB drive more or less succeeded, with different methods (via VirtualBox mapped to raw disk, via Rufus in a VM and via WinClone directly from macOS), but strangely an ordinary Boot Camp installation after partitioning the internal drive failed at the end of the Windows install (the same also when installing directly to an external Thunderbolt drive); and now, with Windows 11 25H2, Windows also refuses to boot on this machine with Hyper-V enabled: which had never happened before. So, it looks like also Boot Canp is becoming less and less viable, with time; while fortunately a Windows 11 VM in Parallels still works perfectly, albeit rather slowly. Just to share some experiences: nothing to do with OCLP…
(Curiously, too, after removing the Boot Camp partition after the failed Windows 11 install and restoring a fully dedicated to macOS internal disk, FileVault now began to ask for the login password two times, instead of only at the beginning as before and as should be: another strange glitch, but not OCLP-related; had also happened before, but it was “fixed by itself”.)
(Edit: I already have two Parallels subscriptions, one for the MBA and one for the MBP: more than enough. Now, if only they allowed at least two installs with one subscription, as others do…)
(Curiously, too, after removing the Boot Camp partition after the failed Windows 11 install and restoring a fully dedicated to macOS internal disk, FileVault now began to ask for the login password two times, instead of only at the beginning as before and as should be: another strange glitch, but not OCLP-related; had also happened before, but it was “fixed by itself”.)
(Edit: I already have two Parallels subscriptions, one for the MBA and one for the MBP: more than enough. Now, if only they allowed at least two installs with one subscription, as others do…)
Last edited:
Parallels has a decent promotion going on at the moment. Care to use the code? I wont.
BTW, if your EFI partition suddenly has problems which Disk Utility cannot repair (error -69766), this command from the Terminal might help:
sudo fsck_msdos disk0s1
(of course, if it is on disk0).
For example, this saved me from a full reformat (reinstalling macOS over itself didn’t change anything), after a failed Boot Camp install…
sudo fsck_msdos disk0s1
(of course, if it is on disk0).
For example, this saved me from a full reformat (reinstalling macOS over itself didn’t change anything), after a failed Boot Camp install…
My trusty 2015 MBA died so I bought my wife an M4 MBA and took over her 2019 MBA. Is the T2 issue still a work in progress or am I stuck on macOS 14 until I by myself something newer?
T2 Macs are not supported with OCLP, especially 2018/2019 MBA models.
macOS Sequoia and OpenCore Legacy Patcher Support · Issue #1136 · dortania/OpenCore-Legacy-Patcher
Another year, another WWDC and macOS version. This time with macOS 15, Sequoia, and a surprising lack of dropped hardware compared to previous years 🎉. As the OS has been in developer beta for a fe...
github.com
OTA update to 24G325 using 2.4.1 was as buttery smooth as a soap bubble landing on water.
I've seen 15.7.2 (24G325) described as "RC4". Updated a supported m/c ok, working on updating an unsupported one at present.
This Mac has an Nvidia Kepler GPU (3802-based), it can get unstable when idling. It will freeze or show glitched graphics.
The solution is to select "Disable mediaanalysisd service" on OCLP settings. Re-build and install OpenCore.
Thanks, but not necessary on the rMBP10,1. The nVidea card is working perfectly now after a somewhat glitchy start immediately post update. I've tested that it activates- and deactivates the card automatically when using- and not using 3D apps. I've also been running the m/c for the past hour with zero issues. So I'm not sure your advice is correct or advisable.
Last edited:
I have the MBP9,1, same GPU, connected to external Thunderbolt Display, so it runs exclusively on the Nvidia dGPU. My Photos Libray is huge, so it will try to use the GPU when the Mac is idle to scan the photos. It runs fine until I forget about it and it sleeps, then when I came back it was either frozen or the graphics were very messed up.
After selecting "Disable mediaanalysisd service" option it's very stable now. But I lost Photos person/objects recognition, which I don't care about.
Now when using in portable mode I agree that it's not necessary, graphics switch work as expected.
Last edited:
All these NVIDIA graphics issue(s) posts make me thankful that my iMac has AMD graphics, and a Metal supported one, as well. Seems like all the NVIDIA users still have a bunch of issues. If I remember correctly, even with a supported install, weren't NVIDIA graphics with Macs more trouble over integrated Intel, or dedicated AMD cards?
It was more of a business problem than performance.
The last Macs with Nvidia GPU were the mid-2014 15" MacBook Pros using Nvidia 750M and the late 2013 27" iMacs using Nvidia 755M to 780M.
Faulty Nvidia chips in 2008+ Macs and Nvidia's refusal to support Apple Metal doomed their relationship (some background here):
The last Macs with Nvidia GPU were the mid-2014 15" MacBook Pros using Nvidia 750M and the late 2013 27" iMacs using Nvidia 755M to 780M.
Faulty Nvidia chips in 2008+ Macs and Nvidia's refusal to support Apple Metal doomed their relationship (some background here):
Last edited:
Au contraire! I seem to remember endless complaints re AMD GPUs, vs nVidia, which has always worked great on this rMBP10,1
I remember older AMD chips having heat issues in 2011 and older Macs, but in this case, I'm also referring to OCLP, it seems like in comparison, the only limitation I have compared to some is, Apple DRM doesn't work, which is minor compared to some issues with NVIDIA. The other limitation is 3D Acceleration in VMs doesn't work, but also in my situation, minor, because I have set up Linux on an external drive, and running directly as the host, is going to run better anyway than a VM when it comes to graphics performance.
One of the strangest glitches with having Nvidia Kepler as a dGPU in the MBP11,3 is that it won’t display the license agreement for some apps, typically for macOS full installers and also macOS updates in Software Update; while the MBP11,1 with only an Intel GPU doesn’t have this problem: it is not a serious issue, but rather strange (Metal-related?)…
Last edited:
… And then there’s also a more important bug (maybe related?), in peculiar apps such as Acronis: some configuration windows aren’t displayed at all. An already known issue…
I believe after thinking about things a bit, I'm more thinking about the NVIDIA non metal related issues on recent macOS. I guess I just automatically associated NVIDIA with issues regarding macs because of the partnership. I know AMD GPUs have had issues as well, but as mentioned, those were mainly heat issues, and in older macs. I'm not aware of recent macs with an AMD GPU having problems.
In terms of OCLP related stuff, the license agreement, and other glitches mentioned above came to mind as well.
So when all is said and done, it just has the appearance that at least with OCLP NVIDIA GPUs have more issues than AMD, or Intel.
Edit: heat related issues include mainly laptops PPC, and Intel, with non leaded solder, and the joints breaking when the board got hot.
I don't have the wide exposure to other Mac users like I used to. So, now, I'm mainly focused on my own setup, and not aware of what's going on outside my space. I only get on here to ask questions I can't solve, or answer, respond to posts.