I get the boot menu too, but as far as I've heard from Martin, if the system firmware doesn't say his specific revision that he codes in, OC is not being recognized properly.
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.
MP 1,1-5,1 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
macOS 12.3 needs an extra kext for power management:
OpenCore on the Mac Pro
Managed to fix it thanks to @cdf . You need to add the ASPP-Override.kext to the EFI>OC>Kexts folder and add the definition to the config.plist (underneath Lilu, WhateverGreen, FeatureUnlock): Edit: Enabled has to be set to true for this to work Arch...
forums.macrumors.com
You don’t want to do that: those additions are necessary now, and the VMM flag is not intended for long term use.
macOS 12.3 needs an extra kext for power management:
OpenCore on the Mac Pro
Managed to fix it thanks to @cdf . You need to add the ASPP-Override.kext to the EFI>OC>Kexts folder and add the definition to the config.plist (underneath Lilu, WhateverGreen, FeatureUnlock): Edit: Enabled has to be set to true for this to work Arch...
You don’t want to do that: those additions are necessary now, and the VMM flag is not intended for long term use.
OK, I am using the config.plist from Martin's 0.78v2. I have now:
- Added (back) the entries you entries you provided in post 3334.
- Turned off the VMM flag (CPUID / UpdateSMBIOS) again.
- Added the kext and plist entries as detailed in post 10536 (!) of the OC thread.
I am happy to report that I have now booted into 12.3, and my Apple Bluetooth keyboard is working fine. The BT module is identified correctly in System Report (BCM_20703A1).
It did have a long pause during boot though. When I first started typing this post, it was to say it was still hanging - but it pulled through eventually. Perhaps future boots will be quicker (I'll need to shut down to remove my Mojave disk), but at least now I'm back in business!
Thanks @cdf, as ever, for being so responsive and helpful.
A report in the OC thread says SurPlus and MonteRand are no longer needed, and one person said SurPlus caused boot to hang. @h9826790 Should these therefore be removed (if still in the 0.78v2 config.plist, which I believe they are)?
Last edited:
OC must be doing something, or the 5,1 wouldn't be able to boot Monterey in the first place?
The answers are as follows:
1. You must enable the VMM flag or the system goes into a boot loop due to that extra kext that is needed for 12.3. While there have been people who are not experiencing this issue, most others are.
2. The reason the system firmware didn't read as Martin's spoofed value was because updateSMBIOS was set to false per the install Monterey instructions Martin provided. Setting this value to true clears that up.
3. Bluetooth (Broadcom specifically) works just fine in Monterey with OC but you have to enable two values within the config.plist file (BlueToolFixup.kext and BlueTooth-Spoof.kext). Search for these names and set their values to true.
Martin is working on a solution to the 12.3 kext problem and may end up putting out 0.7.9 a bit earlier than expected but is still testing as of right now.
If you followed Martin's instructions in the 0.7.8 v2 package and reverted your modifications back to his default values after installing Monterey, and are now stuck in a boot loop, pull the drive, put it in another machine and change the VMM flag back to the C modification. That's all you need to do at this time to get your system back and running.
1. You must enable the VMM flag or the system goes into a boot loop due to that extra kext that is needed for 12.3. While there have been people who are not experiencing this issue, most others are.
2. The reason the system firmware didn't read as Martin's spoofed value was because updateSMBIOS was set to false per the install Monterey instructions Martin provided. Setting this value to true clears that up.
3. Bluetooth (Broadcom specifically) works just fine in Monterey with OC but you have to enable two values within the config.plist file (BlueToolFixup.kext and BlueTooth-Spoof.kext). Search for these names and set their values to true.
Martin is working on a solution to the 12.3 kext problem and may end up putting out 0.7.9 a bit earlier than expected but is still testing as of right now.
If you followed Martin's instructions in the 0.7.8 v2 package and reverted your modifications back to his default values after installing Monterey, and are now stuck in a boot loop, pull the drive, put it in another machine and change the VMM flag back to the C modification. That's all you need to do at this time to get your system back and running.
Thanks for the info.
So it's not necessary to have updateSMBIOS set to 'false', in addition to setting VMM to 'C'? Is that only when doing OS updates?
Will setting the VMM flag to 'C' disable power management? Obviously, being able to boot is more important, but still. I'm currently booted with VMM off, so don't really want to enable it if it has side-effects. I guess I may have been lucky though (this time).
My BT is working fine. I haven't changed any related settings in Martin's Config - are the values you gave the defaults?
It wasn't my experience that the MP would boot with just the VMM flag, though my updateSMBIOS was set to false at the same time. It was only after I added the stuff that cdf suggested that the Mac booted. Though it did pause for a couple of minutes during boot.
So it's not necessary to have updateSMBIOS set to 'false', in addition to setting VMM to 'C'? Is that only when doing OS updates?
Will setting the VMM flag to 'C' disable power management? Obviously, being able to boot is more important, but still. I'm currently booted with VMM off, so don't really want to enable it if it has side-effects. I guess I may have been lucky though (this time).
My BT is working fine. I haven't changed any related settings in Martin's Config - are the values you gave the defaults?
It wasn't my experience that the MP would boot with just the VMM flag, though my updateSMBIOS was set to false at the same time. It was only after I added the stuff that cdf suggested that the Mac booted. Though it did pause for a couple of minutes during boot.
Last edited:
Hello and a big thank you to Martin for the great work!
I have a cmp 5,1 (Mid 2010) with an XFX RX580 GTS 8 GB and use OC 0.78. I have Apple Cinema HD displays connected to the RX580. On startup I see the selection for the startup volumes, but the colours are all way off and vary. I can barely make out the writing. When I set the retina display flag AQ== to Ag== in previous versions (e.g. OC0.74), the icons and font got bigger and everything is ok. In OC 0.78 I can't find AQ== anymore. Can I insert it in the old place or am I breaking something?
Many greetings and thanks for all suggestions!
Marcel
I have a cmp 5,1 (Mid 2010) with an XFX RX580 GTS 8 GB and use OC 0.78. I have Apple Cinema HD displays connected to the RX580. On startup I see the selection for the startup volumes, but the colours are all way off and vary. I can barely make out the writing. When I set the retina display flag AQ== to Ag== in previous versions (e.g. OC0.74), the icons and font got bigger and everything is ok. In OC 0.78 I can't find AQ== anymore. Can I insert it in the old place or am I breaking something?
Many greetings and thanks for all suggestions!
Marcel
If updateSMBIOS is set to true then Martin's spoofed value will not appear in system firmware. I'm not sure if there's any other ramifications for this.
Setting the VMM flag is not for long term use, but it is a workaround for the boot loop issue in 12.3. They are working on a resolution to this.
Can't speak to your Bluetooth as many others did not work and I posted the fix. Mine did not work at all until I enabled both of those kexts and no, they are not enabled by default.
Remember, this is specifically in relation to 0.7.8 v2 and Monterey 12.3. If that's not your setup (i.e. you're running Big Sur) then you won't need to worry about any of this.
Sorry, I was getting mixed up about SMBIOS. Rechecking Martin's video, it's usually set to True, and is just set to False for system updates. So should it be set to True?
I'm using an upgraded BT module, from a later iMac I believe. I was persistently running into an issue with BT not working (so no keyboard), even when my Mac managed to boot to the desktop. It's working now without changing those BT entries, but that's almost certainly due to adding the plist code / kext I mentioned in post 3353.
Yes, I'm running Martin's 0.78v2 and Monterey 12.3. I wouldn't normally be on the bleeding edge of updates; I mistakenly thought 12.3 had been out for a week and people had found it fine. I'd been getting the occasional Monterey 'boot disk hash error' and was hoping 12.3 would fix it (will have to wait to find out with that one).
I'm using an upgraded BT module, from a later iMac I believe. I was persistently running into an issue with BT not working (so no keyboard), even when my Mac managed to boot to the desktop. It's working now without changing those BT entries, but that's almost certainly due to adding the plist code / kext I mentioned in post 3353.
Yes, I'm running Martin's 0.78v2 and Monterey 12.3. I wouldn't normally be on the bleeding edge of updates; I mistakenly thought 12.3 had been out for a week and people had found it fine. I'd been getting the occasional Monterey 'boot disk hash error' and was hoping 12.3 would fix it (will have to wait to find out with that one).
Last edited:
Yes, sorry. Must have mixed that up when typing. It should only be set to false when installing, then set back to true so that you see Martin's spoofed value in system firmware.
May I have a copy of your config.plist file?
I have tried to set things up for 12.3 based on the
Edit:
Forget it – it works now! I had pasted some stuff in the wrong place in the config.plst.
Last edited:
I was updated to OC 0.7.9 (made by cdf) a few days ago
and in addition all day I tested Martin's Beta.
Before update to 12.3 I updated Xcode and then I made an update Monterey 12.3, using a modified version of 0.7.8 Martin's release (with Monterand and Sur Plus, with VMM flag "on" and with UpdateSMBIOS "false" and with thunderbolt3 "false").
The installation was successful without failures (though the installation process took several hours).
After installation, I returned to a standard Martin's 0.7.9 beta (with a flag turned off, but adding only aspp-override kext (but not try to use my 0.7.9 yet).
Passed stress tests and benchmark performance.
Also tested the work in the real tasks of UE-5 and Twinmotion.
The UE-5 scene was loaded for a very long time, according to my feelings about 5 times slower than this morning at mac os 12.2 before the update to 12.3
As to hardware acceleration I checked in video prog H264 and HEVC is ok, without VMM flag on, but only with an additional kext
UPDATED
CPU render time in corona benchmark dramatically increase (up to 30%).
CPU performance with Monterey 12.3 in real tasks significantly worsened:
the compilation of shaders in UE4.27 and UE5.0.0 now happens very slowly, several times longer
BUT
Blender 3.1 Cycles now has a Metal GPU backend, contributed by Apple. Metal GPU rendering is currently supported on:
Apple M1 computers running macOS 12.2 or newer
Apple computers with AMD graphics card running macOS 12.3 or newer
The implementation is in an early state. Performance optimizations and support for Intel GPUs are under development.
My RadeonPro W5700 is 7 times faster than dual cpu with bed performance (In this system with this configuration of OpenCore)
UPDATED
about compiling shaders UE4-UE5, probably the time was greatly increased, because the shaders were compiled for the first time in a new system, reloading scenes now takes normal time
UPDATED
I made changes in my own config
(config made with all instructions posted by cdf macrumors 68000 +added aspp-override kext)
performance now is as usual,
fps in UE4-27 and UE5.0 in my standard scene is better than yesterday (was approx 40, now about 50)
MacPro 4.1/5.1, 96Gb samsung RAM, 1Tb nvme 970EvoPlus, AlpineRidge thunderbolt card, RadeonPro W5700, OC 0.7.9, MacOS Monterey
and in addition all day I tested Martin's Beta.
Before update to 12.3 I updated Xcode and then I made an update Monterey 12.3, using a modified version of 0.7.8 Martin's release (with Monterand and Sur Plus, with VMM flag "on" and with UpdateSMBIOS "false" and with thunderbolt3 "false").
The installation was successful without failures (though the installation process took several hours).
After installation, I returned to a standard Martin's 0.7.9 beta (with a flag turned off, but adding only aspp-override kext (but not try to use my 0.7.9 yet).
Passed stress tests and benchmark performance.
Also tested the work in the real tasks of UE-5 and Twinmotion.
The UE-5 scene was loaded for a very long time, according to my feelings about 5 times slower than this morning at mac os 12.2 before the update to 12.3
As to hardware acceleration I checked in video prog H264 and HEVC is ok, without VMM flag on, but only with an additional kext
UPDATED
CPU render time in corona benchmark dramatically increase (up to 30%).
CPU performance with Monterey 12.3 in real tasks significantly worsened:
the compilation of shaders in UE4.27 and UE5.0.0 now happens very slowly, several times longer
BUT
Blender 3.1 Cycles now has a Metal GPU backend, contributed by Apple. Metal GPU rendering is currently supported on:
Apple M1 computers running macOS 12.2 or newer
Apple computers with AMD graphics card running macOS 12.3 or newer
The implementation is in an early state. Performance optimizations and support for Intel GPUs are under development.
My RadeonPro W5700 is 7 times faster than dual cpu with bed performance (In this system with this configuration of OpenCore)
UPDATED
about compiling shaders UE4-UE5, probably the time was greatly increased, because the shaders were compiled for the first time in a new system, reloading scenes now takes normal time
UPDATED
I made changes in my own config
(config made with all instructions posted by cdf macrumors 68000 +added aspp-override kext)
performance now is as usual,
fps in UE4-27 and UE5.0 in my standard scene is better than yesterday (was approx 40, now about 50)
MacPro 4.1/5.1, 96Gb samsung RAM, 1Tb nvme 970EvoPlus, AlpineRidge thunderbolt card, RadeonPro W5700, OC 0.7.9, MacOS Monterey
Last edited:
Martin is testing a new revision of 0.7.9 called beta 2 and though I haven't had a chance to test it yet, I have a copy and from what he has said, the boot loop issue has been resolved.
I have also asked him to update the Readme to include instructions on enabling Bluetooth properly for Broadcom.
I have also asked him to update the Readme to include instructions on enabling Bluetooth properly for Broadcom.
Would you mind posting a copy of cofig and also the 0.7.9 v2 package? Cant find it anywhere and Martin's link on facebook is dead. ThanksI have tried to set things up for 12.3 based on the 0.7.9v2 package, and the computer seems to start up into Monterey (can sleep, wake and eject optical disc tray), but I have no video signal.
Forget it – it works now! I had pasted some stuff in the wrong place in the config.plst.
0.7.8 v2 is on page 53 of this thread just like all the other versions of Martin's OC. However, I would not recommend using it and instead please wait until he releases 0.7.9 officially. I am now running 0.7.9 beta 2 and I can confirm it fixes the boot loop issue. Everything works nice and smoothly now, and Martin is assuming that if no other issues arise, 0.7.9 beta 2 will end up becoming the official 0.7.9 release. Hang tight!Sorry, typo.
Meant 0.7.8v2
OK Cool - I am still running 0.7.8 but unfortunately upgraded to 12.3 so I am having many weird problems, biggest of which is I cannot boot without the VMM set. I have added the ASPP-Override kext and config as per @cdf but that didnt solve the VMM requirement that. Also my bluetooth is no longer working so I am not sure whats what right now. The stock 0.7.8v2 doesnt boot my mac anymore so I was hoping for a Martin Lo 0.7.9 to solve it!
That's not a strange issue at all. That is the known-issue that 0.7.9 addresses. If you are using 0.7.8 with Monterey 12.3 you must set the VMM flag in order to boot. Otherwise, if this VMM flag is not set, a boot loop will occur. Martin should be releasing 0.7.9 soon, and that solves the issue.
Yes, thanks – I know.
I just mistyped 0.7.9v2 when I meant 0.7.8v2 in my post above and @kkinto was wondering if I could share the 0.7.9v2 package which I don't have.
Monterey 12.3 is working fine for me now using Martin's 0.7.8v2 after modifying the config.plist, but like you say it's probably a good idea to wait for Martin's 0.7.9 release of the OC package.
Maybe just wait for 0.7.9, but did you also enter the code in this post correctly?
It has to be added into the config.plist – not replace anything in it.
For Bluetooth to work with my USB dongle I have to enable Bluetooth-Spoof.kext and BlueToolFixup.kext
Easy to do with OpenCore Configurator after having opened the config.plist with it:
Thanks. Will try the bluetooth fixup and the spoof. Maybe that'll help. Yes I added that code for the new kext in that post, but as soon as I put the VMM cpuid1mask back to all A's it will not boot Monterey anymore (dies immediately the progress bar appears under the apple).
EDIT Nope, enabling bluetoothfixup and bluetooth-spoof didnt help. Bluetooth still dead in Monterey now. Not sure what I did to kill it.
EDIT Nope, enabling bluetoothfixup and bluetooth-spoof didnt help. Bluetooth still dead in Monterey now. Not sure what I did to kill it.
Last edited:
Does your USB dongle work with stuff like Continuity and Handoff? Not specifically with 12.3, but just in general with macOS. I've got an upgraded wireless card, but the BT signal can be a little weak sometimes, so interested in alternatives.Yes, thanks – I know.
I just mistyped 0.7.9v2 when I meant 0.7.8v2 in my post above and @kkinto was wondering if I could share the 0.7.9v2 package which I don't have.
Monterey 12.3 is working fine for me now using Martin's 0.7.8v2 after modifying the config.plist, but like you say it's probably a good idea to wait for Martin's 0.7.9 release of the OC package.
Maybe just wait for 0.7.9, but did you also enter the code in this post correctly?
It has to be added into the config.plist – not replace anything in it.
For Bluetooth to work with my USB dongle I have to enable Bluetooth-Spoof.kext and BlueToolFixup.kext
Easy to do with OpenCore Configurator after having opened the config.plist with it:
View attachment 1974460
It's just a Bluetooth 4.0 dongle and I don't have any working wifi, so no – it doesn't work with Continuity and Handoff.
Last edited:
I am trying to completely remove OpenCore from my Mac in an attempt to start again fresh. Since the upgrade to 12.3 there has been nothing but grief. Now I cannot even zap the NVRAM - tried four keyboards, 2 apple alumium wired and two older plastic apple wired. None of them will enable me to zap the NVRAM, all work perfectly when Mac is booted. Tried every single USB port back and front, even using two different dongle (bus powered) USB hubs, every time MP just boots to the OpenCore bootpicker. Have I screwed something fundamental up somehow?