Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Starting with macOS 12.4, Voice Control uses AVX. To avoid the crashes, make sure you’re using AVXpel.
Wow tried the patches but no joy still crashed on logging into the account that enabled voice control. On the bright side, another account nor OC showed bad signs with the patch. A thought is to try it on a guest account and maybe that would knock it out of the kink

Tried that and no go. looked at crash report and latest crash was /Library/Application Support/Motorola Mobility/MotoHelper.app/Contents/Resources/REUpdater

Maybe if I get rid of that?

Did see it crashes right after downloading some stuff to turn on voice control

no still crashed but do have:

Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[78E6D3DF-9A4D-3F46-B298-3C52A83F9108]@0xffffff801410c000->0xffffff801428afff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[5D7C7E5D-CA94-360D-9A05-384B539B1A7A]@0xffffff80123b2000->0xffffff80123bbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[B97B3370-F304-3E32-8356-E2CB9B0255A7]@0xffffff80123c8000->0xffffff80123cdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[3542B048-616C-33A7-A22B-532EDFC1A466]@0xffffff80128d4000->0xffffff80128dbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[EDB37126-8C1E-3BF1-B95A-07D7074F3AC6]@0xffffff8013b7c000->0xffffff8013b92fff
dependency: com.apple.kec.corecrypto(12.0)[08AB2CDD-6687-35EA-BA0B-2974BDB2FB9C]@0xffffff80142c4000->0xffffff8014344fff

dependency: com.apple.security.AppleImage4(4.2.0)[5DA3A952-D34E-3D9D-8C91-FD475E1DF6F0]@0xffffff801244f000->0xffffff8012467fff
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib(1.0)[BD10F82C-64B9-390D-94D1-70A0B5BE2044]@0xffffff80123e5000->0xffffff80123f6fff

Process name corresponding to current thread (0xffffff86b850b000): com.apple.SpeechRecognitionCore.

Edit: 5/28 Enabling voice control on this machine CMP 2009, will download files and then crash. I dont know about others but maybe using this setup with open core on these running 12.6.6. If you are going to try it, do it on a guest account because it will hose your regular until you find all the setting files in the account library prefs
 
Last edited:
@h9826790 Monterey is working on my MP5.1 now. Thank you for that very good guide in Post #1314.

Since I'm using OC 0.9.2, I didn't disable SIP as per the initial instructions. I read through the post several times as I found "Since 0.6.3, I allow OC to take over SIP control...". Since we're now using OC 0.9.2, I keep SIP enabled. I recommend that you remove the SIP statements and video since we're way beyond OC 0.6.3.
I had to disable SIP. Enabled SIP caused problems. I will test it again in the near future.

UPDATE: WiFi/Bluetooth are not working. However, I'm using Ethernet. I've updating the WiFi/Bluetooth several years ago, and they were working in Mojave.
 
Last edited:
@h9826790 Monterey is working on my MP5.1 now. Thank you for that very good guide in Post #1314.

Since I'm using OC 0.9.2, I didn't disable SIP as per the initial instructions. I read through the post several times as I found "Since 0.6.3, I allow OC to take over SIP control...". Since we're now using OC 0.9.2, I keep SIP enabled. I recommend that you remove the SIP statements and video since we're way beyond OC 0.6.3.
I had to disable SIP. Enabled SIP caused problems. I will test it again in the near future.

UPDATE: WiFi/Bluetooth are not working. However, I'm using Ethernet. I've updating the WiFi/Bluetooth several years ago, and they were working in Mojave.
That's a BT 4.0 card, should be natively supported in Monterey, but doesn't work?

Do you know if BT is working in the boot picker?

Did you try SMC reset yet?
 
Hi everybody
I’m new to opencore
I use 0.92 for Mac Pro 5.1
Vega 56
But I don’t have hevc working
Any help
Thank

0BB8D606-8E63-4EE5-86FD-105D5DD09A30.jpeg
 
In the current version of Photoshop 24.5, a new functionality requiring macOS Monterey was added, so I finally decided to update from BigSur (using Martin's Package). It was successful, a few notes:

- I downloaded the Monterey 12.6.6 installer from
(installer extracted to /Applications)
- I edited the OC config.plist according to Martin's instructions (and restarted)
- after starting the installation, both my displays were black, no signal, for about 20 minutes (my system is on a SATA SSD), you have to be patient and not interrupt the process (even if it may seem dead)
- after the first reboot, you have to continue the installation from the macOS installer (for me, it launched itself from the system disk back to BigSur, so I repeated the installation and supervised the launch from the installer). The second restart during installation already goes correctly from the system disk.
- the further progress of the installation (approx. 20 minutes) could already be watched on the display
- I reverted the original config.plist from Martin's data 0.9.2 and rebooted

- Monterey works great, seems snappier than BigSur (after about half a day work), also the new Remove tool in Photoshop.

Question: can I update Monterey in the future from System Preferences as with BigSur (now always with those modifications in OC config.plist)? It already offers me the Safari 16.5 update, and in the future I assume that there will be updates to 12.6.7... Or is it better not to touch it anymore? Automatic system updates are turned off.
 

Attachments

  • Screenshot1.png
    Screenshot1.png
    13.4 KB · Views: 48
  • Screenshot2.png
    Screenshot2.png
    72.5 KB · Views: 52
"factory flashing" ???
You do not need to flash standard RX580 to run it on the Mac.

If it's a second hand GPU, it's very possible that the firmware was user flashed to a gaming or cryptocurrency mining firmware, so, the signature of the GOP UEFI module is now invalid and the GPU needs to be flashed to the original factory installed firmware again to have EnableGop or the OC boot picker working.

For dual firmware GPUs, first test both switch positions before trying to flash back the factory firmware.
 
If it's a second hand GPU, it's very possible that the firmware was user flashed to a gaming or cryptocurrency mining firmware, so, the signature of the GOP UEFI module is now invalid and the GPU needs to be flashed to the original factory installed firmware again to have EnableGop or the OC boot picker working.

For dual firmware GPUs, first test both switch positions before trying to flash back the factory firmware.
 

Attachments

  • DD6DCBE4-10FC-4579-B26E-A4DC9651FA70.jpeg
    DD6DCBE4-10FC-4579-B26E-A4DC9651FA70.jpeg
    369.8 KB · Views: 91
  • 1EB77A73-82CF-4D8B-94C8-4391BC06277E.jpeg
    1EB77A73-82CF-4D8B-94C8-4391BC06277E.jpeg
    271.5 KB · Views: 87
  • 7064055D-FA48-465F-8715-2E5978F0B81D.jpeg
    7064055D-FA48-465F-8715-2E5978F0B81D.jpeg
    359.9 KB · Views: 74
I install bigsur the problem gone
When go back to Mojave the problem still there
But now I’m happy with Big Sur
By the way anything I can do to bring back WiFi and Bluetooth without upgrade the new one
Thanks Martin Lo and the team for 0.92 packages
 
I install bigsur the problem gone
When go back to Mojave the problem still there
But now I’m happy with Big Sur
By the way anything I can do to bring back WiFi and Bluetooth without upgrade the new one
Thanks Martin Lo and the team for 0.92 packages
Good to hear. No you would have to upgrade them. Yes thanks for doing all or at least most of the work! Im on 12.6.6 but OC still using whatever it was when I set it up. There have been a ton of updates since. Im on like 7 or 8 works fine. On another note, I should really sanely get rid of it and use something newer but really attached to the case and design was so top notch
 
Last edited:
Today I just install Monterey although the installation is successful I still get trouble
I get Apple.com/startup help 3 times . I turn off pc and turn on it back pc continue installing
When I boot to Monterey I still get Apple.com/startup
Turn off and on it boot to Monterey . Do I made any mistake?
Monterey run so smoothly
 

Attachments

  • 84A3D08D-764D-4248-BE7A-27AB592661FB.jpeg
    84A3D08D-764D-4248-BE7A-27AB592661FB.jpeg
    320.2 KB · Views: 58
  • FBF5B875-F6E0-4FBF-B933-4C7A07CB113B.jpeg
    FBF5B875-F6E0-4FBF-B933-4C7A07CB113B.jpeg
    734.1 KB · Views: 66
Today I just install Monterey although the installation is successful I still get trouble
I get Apple.com/startup help 3 times . I turn off pc and turn on it back pc continue installing
When I boot to Monterey I still get Apple.com/startup
Turn off and on it boot to Monterey . Do I made any mistake?
Monterey run so smoothly
Is that with my latest OC 0.9.2 package?
 
In the current version of Photoshop 24.5, a new functionality requiring macOS Monterey was added, so I finally decided to update from BigSur (using Martin's Package). It was successful, a few notes:

- I downloaded the Monterey 12.6.6 installer from
(installer extracted to /Applications)
- I edited the OC config.plist according to Martin's instructions (and restarted)
- after starting the installation, both my displays were black, no signal, for about 20 minutes (my system is on a SATA SSD), you have to be patient and not interrupt the process (even if it may seem dead)
- after the first reboot, you have to continue the installation from the macOS installer (for me, it launched itself from the system disk back to BigSur, so I repeated the installation and supervised the launch from the installer). The second restart during installation already goes correctly from the system disk.
- the further progress of the installation (approx. 20 minutes) could already be watched on the display
- I reverted the original config.plist from Martin's data 0.9.2 and rebooted

- Monterey works great, seems snappier than BigSur (after about half a day work), also the new Remove tool in Photoshop.

Question: can I update Monterey in the future from System Preferences as with BigSur (now always with those modifications in OC config.plist)? It already offers me the Safari 16.5 update, and in the future I assume that there will be updates to 12.6.7... Or is it better not to touch it anymore? Automatic system updates are turned off.
May be you have multiple monitors setup. For single monitor setup, you should able to see the installation progress, but not just black screen.

Anyway, as you said, just don't touch it, then the cMP will sort out itself.

Unfortunately, for Monterey, my package required users to turn on VMM and disable SMBIOS spoofing for every macOS update. However, that's for "Monterey update" only. e.g. from 12.6.6 to 12.6.7. If just something like Safari update, RAW support update, or other misc update. You can simply accept the update without changing the VMM flag.

If you want to make it as seamless as Big Sur, then you can study the cdf's OpenCore post #1. I've put the required FirmwareFeatureMask in the config already (credit to cdf). I have't enable that mainly because once we turn on SecureBootModel, most likely you won't able to boot your existing Mojave (if any) via OC. And I personally recommend people has a Mojave drive for emergency use. Therefore, I am a bit reluctant to let cMP has seamless Monterey support, but can't boot Mojave (when via my OC package).

But TBH, the situation is changing now. When most of the users have their cMP flashed with EnableGop, then I think we can safely turn on SecureBootModel. On the day that really need to boot existing Mojave, the user can simply hold Option key to boot. But that will be at least a few months away.
 
SSD drives
Opencore 0.92 on Ssd Mojave disk 1
Monterey on Ssd disk 2
High Sierra on nvme pci slot 3
 
It was exactly the same way I do install Big Sur with the same drives in pc. The different is I take out bigsur Ssd and put new ssd into it
Now the pc boot into Monterey without any issues
I think the problem still there
 
Last edited:
Unfortunately, for Monterey, my package required users to turn on VMM and disable SMBIOS spoofing for every macOS update. However, that's for "Monterey update" only. e.g. from 12.6.6 to 12.6.7. If just something like Safari update, RAW support update, or other misc update. You can simply accept the update without changing the VMM flag.
OK, thanks for info, Safari now up to date without this config.plist changes.
 
  • Like
Reactions: h9826790
It was exactly the same way I do install Big Sur with the same drives in pc. The different is I take out bigsur Ssd and put new ssd into it
Now the pc boot into Monterey without any issues
I think the problem still there
Your setup looks OK to me.

But may be you can move OpenCore to the Monterey drive's EFI partition (and bless it).

Both Mojave and High Sierra can boot natively anyway. Put OpenCore onto the Monterey drive make more sense in general.
 
Ok thank for your advice
Do I need remove the opencore in Mojave before I bless the the new one in efi of Monterey
 
Ok thank for your advice
Do I need remove the opencore in Mojave before I bless the the new one in efi of Monterey
Up to you.

But if you want to remove it, better install and bless the new one, and after testing to make sure it works, then remove the old one.
 
Monterey 12.6.5 update successfully (as usual, with VMM on, SMBIOS spoofing off). HWAccel still works as expected. It seems a very normal security update this time. Safe to apply.
View attachment 2187191
Greetings h9826790, I've burned myself out trying to resolve this, but it looks like you have success with the HW Acceleration on your macOS 12.6.5 install. I have a fully upgraded 4,1 to 5,1, 2010 cMP with dual processors (upgraded) max Ram and a AMD 6900XT (Pixlas mod) but cannot get HW Acceleration for H264 with his AMD card, but I do have it for HEVC. I've followed Syncretics patcher (much praise) and the 6900XT works, but of course, no boot picker, and much to my surprise, no H264 HWA. I'm okay with no boot picker for now, but would love to solve this H264 HWA problem. Doing basic video tasks like video screen records are impossible, or exports from Davinci Resolve can only be done via software rendering and not hardware rendering. My guess is that the problem is that my installation of 12.6.6 is born from the OCLP and not via your MLOC to install my macOS 12.6.6, and the two just can't cross pollinate. I've tried to use the HW Acceleration tools from #594 and from #1314, but no luck. To be frank, using the OCLP has been great, but even from earlier versions, I've never had the use of DRM, but did have H246 and HEVC HWA. I thought a new card would solve all of this. For workflow and a stronger workhorse, I was anxious to leave my old Nvidia Quadros behind, so yes, new card is great, but the one thing I need, I don't have, H264 HWA. Any history behind this problem or am I just doing this all wrong? I appreciate your guidance on this one, please. I'm at a loss and may have to reluctantly go back to the Quadros, just to get work done. Much thanks for the wisdom share! I'm a slow learner but I've learned a lot. Best ~ EMJAYWLZ
 

Attachments

  • MJ_cMP_12.6.6_no_H264_HWA_230531.png
    MJ_cMP_12.6.6_no_H264_HWA_230531.png
    559.8 KB · Views: 50
  • Attemtped Screen Record.png
    Attemtped Screen Record.png
    110 KB · Views: 47
  • Scree Recording Error.png
    Scree Recording Error.png
    38.6 KB · Views: 56
Greetings h9826790, I've burned myself out trying to resolve this, but it looks like you have success with the HW Acceleration on your macOS 12.6.5 install. I have a fully upgraded 4,1 to 5,1, 2010 cMP with dual processors (upgraded) max Ram and a AMD 6900XT (Pixlas mod) but cannot get HW Acceleration for H264 with his AMD card, but I do have it for HEVC. I've followed Syncretics patcher (much praise) and the 6900XT works, but of course, no boot picker, and much to my surprise, no H264 HWA. I'm okay with no boot picker for now, but would love to solve this H264 HWA problem. Doing basic video tasks like video screen records are impossible, or exports from Davinci Resolve can only be done via software rendering and not hardware rendering. My guess is that the problem is that my installation of 12.6.6 is born from the OCLP and not via your MLOC to install my macOS 12.6.6, and the two just can't cross pollinate. I've tried to use the HW Acceleration tools from #594 and from #1314, but no luck. To be frank, using the OCLP has been great, but even from earlier versions, I've never had the use of DRM, but did have H246 and HEVC HWA. I thought a new card would solve all of this. For workflow and a stronger workhorse, I was anxious to leave my old Nvidia Quadros behind, so yes, new card is great, but the one thing I need, I don't have, H264 HWA. Any history behind this problem or am I just doing this all wrong? I appreciate your guidance on this one, please. I'm at a loss and may have to reluctantly go back to the Quadros, just to get work done. Much thanks for the wisdom share! I'm a slow learner but I've learned a lot. Best ~ EMJAYWLZ
If your OS is patched, I suggest you unpatch it first.

Or you can simply enable VMM and disable SMBIOS spoofing (assume you are using my package now). Boot to recovery partition (via OpenCore, not natively. Your card should able to show GOP boot screen. If not, something is wrong), and re-install Monterey from there (just cover on top of the existing one, no need to format or delete anything). This will essentially unpatch Monterey.

If you really can't boot to recovery via OpenCore due to lack of boot screen. Simply boot to your existing Monterey desktop and run the 12.6.6 full installer also work.

Assuming the Monterey is unpatched, no extra unnecessary kext installed, and you are using my package. Then both H264 and HEVC HWAccel should work.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.