macOS 12 Monterey on Unsupported Macs Thread

[pshufd]

I moved up my 2020 M1 mini to Monterey yesterday after I felt that 12.5 was stable enough for my production stuff. I have had two main issues with Monterey: a weird networking bug and several memory leaks and these were both fixed by 12.5. There were a number of memory leaks in Monterey that have been fixed since initial launch. I have been running Monterey on my laptop since launch so I was watching the progress on my two main bug areas.

I tried Monterey on my 2015 MacBook Pro and was unhappy with performance and various issues so I went back to Mojave after trying it out for a bit. I went back to it yesterday as well and did find that Monterey performance is much improved and it runs faster than Mojave.

So why am I in the OCLP Monterey thread? I wanted the 2015 MacBook Pro to act as an Airplay receiver which isn't supported in 2015 MacBook Pros and I got this functionality using OCLP even though the 2015 MacBook Pro runs Monterey without it. I would also run Monterey using OCLP on my 2014 MacBook Pro but it's currently loaned out since August 2021 and I wonder if I'll ever get it back. Fortunately that system only has Intel Integrated graphics. I saw the note on Monterey 12.5 and Kepler GPUs and maybe it wouldn't have worked if I had a dGPU model.

There's one other system that I'm considering and that's my 2014 iMac 27 and it fortunately has AMD graphics.

At this point I am very pleased with Monterey and OCLP.

 

[bmillz]

Is anyone having issues with video decoding on Monterey 12.5 and OCLP 0.4.9? I noticed the changelog for 0.4.8 states that it fixes AppleGVA regression introduced in 0.4.6, but that its "applicable for Ivy Bridge-only systems." I have a 2011 MacBook Air, so Sandy Bridge, and running VDADecoderChecker fails with error, "VDADecoderCreate failed. err: -12473."

 

[0134168]

Updated my Macbook Pro 8,3 17" from 12.4 to 12.5 without any problem. Just had to patch again with OCLP 0.4.9.

Thanks again to everyone involved. 1.000.000 thanks is not enough.

 

[plugsnpixels]

Question about pending Software Update:

I've got a Kepler iMac freshly updated from Catalina and purposely holding at 12.4 with the OCLP 0.4.9 post updates, no problem.

However, Software Update is offering the 12.5 update with the "Restart" option (which usually implies it's locked and loaded). After seeing that, I immediately turned off all of the auto-update options.

I was unable to determine if the 12.5 installer had actually already downloaded (I checked temp folder, etc.) or if it still needed to download.

I'm curious what will happen when the computer needs a restart for some other reason... I would hope the installer would not now run on its own with the preferences set to No.

 

[Tockman]

I would hope the installer would not now run on its own with the preferences set to No.

It would not if you left 12.5 update and "Install updates automatically" checkboxes empty.

 

[ChrisOSX]

Unenroll from the Beta Software Program. Only way I could remove it.

I would, but I'm on 12.5 second release candidate (build 21G72). If I unenroll, yes I won't get the Ventura update notification, but I also won't get another 12.5 build if they decide to do another RC. It's just a visual annoyance of the badge.

Looking through Ventura compatible machines, my mid 2010 (daily driver), no matter the dev work, might not ever be compatible. Which is ok, I'm due in for a new machine eventually.

 

[TOM1211]

I would, but I'm on 12.5 second release candidate (build 21G72). If I unenroll, yes I won't get the Ventura update notification, but I also won't get another 12.5 build if they decide to do another RC. It's just a visual annoyance of the badge.

Looking through Ventura compatible machines, my mid 2010 (daily driver), no matter the dev work, might not ever be compatible. Which is ok, I'm due in for a new machine eventually.

You mean system red notification badge?
In terminal run

defaults write com.apple.systempreferences AttentionPrefBundleIDs 0

Then

killall Dock

 

[sergiodadi]

Hello,

I have upgraded (OTA upgrade) my test iMac 27 mi 2011 (WX4130 + BCM94360CD) from Monterey 12.4 to Monterey 12.5 without problem.

Thank you to the various people on this forum who advised, a few years ago, the right graphics card (AMD ) .

 

[K two]

Question about pending Software Update:

I've got a Kepler iMac freshly updated from Catalina and purposely holding at 12.4 with the OCLP 0.4.9 post updates, no problem.

However, Software Update is offering the 12.5 update with the "Restart" option (which usually implies it's locked and loaded). After seeing that, I immediately turned off all of the auto-update options.

I was unable to determine if the 12.5 installer had actually already downloaded (I checked temp folder, etc.) or if it still needed to download.

I'm curious what will happen when the computer needs a restart for some other reason... I would hope the installer would not now run on its own with the preferences set to No.

Now that you have made the CP settings per Tockman go to Monterey/Library/Updates ƒ and trash everything in there and 12.5 will be gone for good.

 

[plugsnpixels]

Now that you have made the CP settings per Tockman go to Monterey/Library/Updates ƒ and trash everything in there and 12.5 will be gone for good.

Thanks, just a couple of .plist files in there, please advise. I'm not sure if that's where the update preferences I made are stored and don't want to mess up my settings.

I don't see any actual installation files in there, even with invisible files revealed (shift-command-.)

 

[kinwin]

Is anyone having issues with video decoding on Monterey 12.5 and OCLP 0.4.9? I noticed the changelog for 0.4.8 states that it fixes AppleGVA regression introduced in 0.4.6, but that its "applicable for Ivy Bridge-only systems." I have a 2011 MacBook Air, so Sandy Bridge, and running VDADecoderChecker fails with error, "VDADecoderCreate failed. err: -12473."

I can confirm DRM streaming is broken for the following configurations after upgrading to 12.5 and OCLP 0.4.9:
2010 iMac 27", 2.93 GHz Core i7 (I7-870 Lynnfield), AMD M5100 M6100
VDADecoderChecker fails. AppleTV app won't play DRM encrypted content, but can still play non-encrypted content.

It seems to be affecting specific CPU's. I also have tested 2011 iMac 21", 2.5 GHz Core i5, I5-2400S (Sandy Bridge), AMD M5100. This one works just fine. VDADecoderChecker report full compatibility. AppleTV can play anything.

 

[K two]

Thanks, just a couple of .plist files in there, please advise. I'm not sure if that's where the update preferences I made are stored and don't want to mess up my settings.

I don't see any actual installation files in there, even with invisible files revealed (shift-command-.)

Trash them and remake the settings in the CP.

 

[plugsnpixels]

Trash them and remake the settings in the CP.

Done... It's the wife's computer so it better work, ha!

I have a similar model iMac in the office to experiment with further (not a critical machine). It's currently at 12.5 without the post-install and laggy due to graphics, of course. So I will bring it back to 12.4 from that thumb drive and adjust the update prefs, restart after a bit and see!

 

[webg3]

Is anyone having issues with video decoding on Monterey 12.5 and OCLP 0.4.9? I noticed the changelog for 0.4.8 states that it fixes AppleGVA regression introduced in 0.4.6, but that its "applicable for Ivy Bridge-only systems." I have a 2011 MacBook Air, so Sandy Bridge, and running VDADecoderChecker fails with error, "VDADecoderCreate failed. err: -12473."

I can confirm DRM streaming is broken for the following configurations after upgrading to 12.5 and OCLP 0.4.9:
2010 iMac 27", 2.93 GHz Core i7 (I7-870 Lynnfield), AMD M5100 M6100
VDADecoderChecker fails. AppleTV app won't play DRM encrypted content, but can still play non-encrypted content.

It seems to be affecting specific CPU's. I also have tested 2011 iMac 21", 2.5 GHz Core i5, I5-2400S (Sandy Bridge), AMD M5100. This one works just fine. VDADecoderChecker report full compatibility. AppleTV can play anything.

I had informed some previous posts about using OCLP 0.4.5 Patch-Root as it fixes these VDADecoder issues

 

[Pedro Manoel]

so im onto opencore ( running monterey )patcher on a 2014 mbp with dedicated graphics ( NVIDIA GeForce GT 750M 2 GB) but i think monterey doesnt know how to use the dgpu ? I disabled it on photoshop and it runs smoother this way, anyone can tell me why ? also when i render videos, its faster with the igpu. Should i go back to bigsur ?

 

[Ausdauersportler]

so im onto opencore ( running monterey )patcher on a 2014 mbp with dedicated graphics ( NVIDIA GeForce GT 750M 2 GB) but i think monterey doesnt know how to use the dgpu ? I disabled it on photoshop and it runs smoother this way, anyone can tell me why ? also when i render videos, its faster with the igpu. Should i go back to bigsur ? View attachment 2037512
View attachment 2037511

Take some time and read the release notes of the current OCLP version or scan through the last few pages of this thread. Everybody is writing about this particular topic for days now.

 

[DragenFi]

Just about to update my MBP 9.2 to Monterey 12.5, I think I have the VDA Decoder issue as FaceTime and Photo Booth crash on my system, I have updated my Monterey OCLP installer to 0.4.9, will updating via OTA and then reapplying the patches and updating the OpenCore install on my startup disk fix the issue, or should I just use the OCLP installer to update everything?

 

[sinbad21]

Which version of OCLP are you using? You may want to report it to the developers, so they can figure out what's going on.

The last one, OCLP 0.4.9.

 

[kinwin]

I had informed some previous posts about using OCLP 0.4.5 Patch-Root as it fixes these VDADecoder issues

Thanks for your suggestions, indeed rolling back to OCLP 0.4.5 seems to fixe the VDADecoder issue for several users with the Intel HD4000 GPU ( #6,820 ). However, my case is different as I have upgraded my iMac with an AMD GCN. In my case I see no difference using OCLP 0.4.5 vs 0.4.9, both fail VDADecoder. The only root patching available is the legacy wifi, it makes no difference whether I apply it or not with respect to the DRM streaming issue. At least for this specific system 2010 iMac 27", 2.93 GHz Core i7 (I7-870 Lynnfield), AMD M6100, I have to roll back to Monterey 12.4 if I want to keep full DRM streaming functionality.

 

[Ausdauersportler]

Thanks for your suggestions, indeed rolling back to OCLP 0.4.5 seems to fixe the VDADecoder issue for several users with the Intel HD4000 GPU ( #6,820 ). However, my case is different as I have upgraded my iMac with an AMD GCN. In my case I see no difference using OCLP 0.4.5 vs 0.4.9, both fail VDADecoder. The only root patching available is the legacy wifi, it makes no difference whether I apply it or not with respect to the DRM streaming issue. At least for this specific system 2010 iMac 27", 2.93 GHz Core i7 (I7-870 Lynnfield), AMD M6100, I have to roll back to Monterey 12.4 if I want to keep full DRM streaming functionality.

Okay, we were not aware of this problem. Since AMD GCN did not need any patches so far you will not find any provided by OCLP right now - and possibly no solution in near future. Metal dGPU patching is a mess…

Until now I assumed one would need a metal iGPU (2012 Intel CPU or later) or a 2016+ dGPU (GCN4 and newer) to have DRM working. At least this is true from now on?

 

[kinwin]

Okay, we were not aware of this problem. Since AMD GCN did not need any patches so far you will not find any provided by OCLP right now - and possibly no solution in near future. Metal dGPU patching is a mess…

Until now I assumed one would need a metal iGPU (2012 Intel CPU or later) or a 2016+ dGPU (GCN4 and newer) to have DRM working. At least this is true from now on?

Yes, with the exception that the AMD M5100 (both red and green PCB) seems to still work fine. The following systems have full DRM support even in Monterey 12.5 and OCLP 0.4.9
2010 iMac, 27”, 3.2 GHz, Core i3, I3-550 (Clarkdale), AMD W5170M
2011 iMac, 21”, 2.5 GHz, Core i5, I5-2400S (Sandy Bridge), AMD M5100

 

[webg3]

Thanks for your suggestions, indeed rolling back to OCLP 0.4.5 seems to fixe the VDADecoder issue for several users with the Intel HD4000 GPU ( #6,820 ). However, my case is different as I have upgraded my iMac with an AMD GCN. In my case I see no difference using OCLP 0.4.5 vs 0.4.9, both fail VDADecoder. The only root patching available is the legacy wifi, it makes no difference whether I apply it or not with respect to the DRM streaming issue. At least for this specific system 2010 iMac 27", 2.93 GHz Core i7 (I7-870 Lynnfield), AMD M6100, I have to roll back to Monterey 12.4 if I want to keep full DRM streaming functionality.

hey, it's a real shame, check the way of capturing logs and, if possible, call the developers on Discord.

 

[Ausdauersportler]

Yes, with the exception that the AMD M5100 (both red and green PCB) seems to still work fine. The following systems have full DRM support even in Monterey 12.5 and OCLP 0.4.9
2010 iMac, 27”, 3.2 GHz, Core i3, I3-550 (Clarkdale), AMD W5170M
2011 iMac, 21”, 2.5 GHz, Core i5, I5-2400S (Sandy Bridge), AMD M5100

The Venus family (M5100 and W5170M and M6000 and M4000) is used in the 2015 MacBookPro - which has still Monterey support, unlike the 2014 iMacs...

 

[Pedro Manoel]

Take some time and read the release notes of the current OCLP version or scan through the last few pages of this thread. Everybody is writing about this particular topic for days now.

thanks for the reply. i forgot to mention that i didnt update the patch ( im using 0.43), i have also applied the patches, but hadn't change nothing

 

[Ausdauersportler]

thanks for the reply. i forgot to mention that i didnt update the patch ( im using 0.43), i have also applied the patches, but hadn't change nothing

Sorry!

Yes, you should go back to Big Sur. Kepler patches on Monterey with OCLP do not work 100%, in particular OpenCL is still broken and so apps like PhotoShop do not work (properly or 100%). A fix is very, very unlikely.

Additionally Monterey 12.5 broke Kepler support completely. This looks like the end of the Kepler road, so far.