I can't give a definitive answer because I don't have access to my Mac Pro at the moment to verify any of this myself: The config settings for the kext in post #1 include a minimum kernel version, so unless you're booting macOS 12.3, the kext won't load. Perhaps an OC debug log would still indicate it's presence, confirming that the kext would load in macOS 12.3. You could also try removing the minimum kernel version (I don't think that the kext would cause an issue in macOS <12.3, but make sure to have a natively bootable version of macOS just in case you need to reapply the setting). However, you might still have to generate an OC debug log (ASPP-Override is a codeless kext, so I'm not sure that it would appear in the list provided by the kextstat command).
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 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Roobarb, I had a similar problem and found the following on YouTube that worked form me. Hope it solves yours.
Last edited:
Look in the Info.plist of the ASPP.Override.kext to see how it is to be loaded.
It is a codeless kext. Instead of having its own code, it points to the kext with bundle identifier com.apple.driver.ACPI_SMC_PlatformPlugin .
kextfind -b com.apple.driver.ACPI_SMC_PlatformPlugin->
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kextThe purpose of a codeless kext's Info.plist is to override the original kext's Info.plist. But the only difference I see is the IOProbeScore so I don't know what it's supposed to be doing.
Anyway, I can see that the one from OpenCore has loaded because the ACPI_SMC_PlatformPlugin IOService that is attached to AppleACPICPU of CPU0 has a IOProbeScore of 0x1388 = 5000.
Danged if you aren't right about this pickiness... I was using BBEdit instead of TextEdit, and I was using Terminal commands to copy things around. I switched back to TextEdit and using Cmd-C in the Finder, and then it worked. Crazy. It's just so weird to me that hdiutil should care about the files involved in creating an ISO, like it looks at the line endings?!? Thanks for the tip.
How can I check my IOProbeScore in order to see if OC is loading ASPP-Override correctly?
I have re-flashed my BootROM numerous times this evening, tried clearing NVRAM, etc...and 12.2 seems to run fine on OC79+ASPP, and Mojave continues to run fine without OC. But the 12.3 updated Monterey simply will not boot for me. I think, consistently, when I attempt to boot to 12.3, the black page progress bar goes about halfway and then just reboots in the middle of it. When I allow it to boot again, then the OC boot picker comes up the instant I choose Monterey from the OC Boot Picker, I get the "problem booting" screen that I showed earlier and it might continue after a pause or hitting a key, but then same thing, halfway through progress bar, it just restarts again.
If I try to select my 12.2 volume from the OC boot picker, the first time, it will show me that "problem booting" page immediately after I select that Monterey 12.2 volume, but then after the pause it will do the progress bar and boot up fine and after that will boot up fine without the problem page.
I'm out of ideas. My OC config seems to be working fine for 12.2.
Here is the Kernel extension section of config.plist:
XML:
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>ASPP-Override.kext</string>
<key>Comment</key>
<string>Power management override</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string></string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>21.4.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>My config.plist is not that complicated, I am following the guide pretty strictly, I think... I don't know what else to try...
Get the IORegistryExplorer.app (Xcode tools or something).
Or use this command:
ioreg -w0 -rc ACPI_SMC_PlatformPluginHave you tried a clean install of 12.3? I had problems with an install over 12.2.1 but it seems to have worked in the end so I don't need to try a clean install.
That's a question for the bootrom thread.
https://forums.macrumors.com/thread...-bootrom-upgrade-instructions-thread.2142418/
I get | "IOProbeScore" = 1000
what does that mean?
oh actually never mind... I'm running 12.2 in order to run that..which means the Min Kernel attribute has blocked ASPP-Override.kext from loading in any case. the irony is that there is no way to know if its loading unless I can actually boot up 12.3...which I can't.
So no idea whether that is the problem or not...
I don't have a place I can install 12.3 from scratch for one thing, not to mention it would be quite a few hours of work to reinstall all my apps, etc..so probably if it turns out my Mac cannot go past 12.2, then so be it that will be end of the line for this Mac I guess. Maybe in the future I can try that...but I'd rather try to figure out why its broken and not working.
Last edited:
It’s increasing the probe score of ACPI_SMC_PlatformPlugin to ensure that it gets used instead of X86PlatformPlugin.
Just remove the minimum kernel version setting and check the probe score in 12.2.
Thanks, @Chrisl33 - I've pulled the card for now but will try this next time around. Funny thing is v12.1 is fine, it's anything later which appears broken. But perhaps v12.1 was the version which put BlackmagicIO.kext and DeckLink_Driver.kext in place originally, I don't remember if I've upgraded from another version since Monterey and the DriverKit changes are major enough to jump to the top of my suspect list.
Well.... Kernel Panic every time... Looks to be related to Graphics...according to panic report:
On the advice of someone, I tried out OCLP and guess what, it boots into 12.3 completely fine, using it right now. That being said, I am still kind of committed to the cleaner/leaner CDF approach, and OCLP has all kinds of extra kexts installed that I don't have any idea what they are all doing and don't really want them if I don't need them...and numerous settings in config.plist that I don't really like either...
But....It would be good if we could figure out what exactly about the OCLP configuration enables 12.3 to boot on my machine without KP...while the cleaner/leaner/CDF version KP's every time.
I'd rather use clean/lean CDF guide honestly. But...for now...doesn't work for 12.3 on my system.
Code:
panic(cpu 12 caller 0xffffff8004dd38e3): Kernel trap at 0xffffff7f860462bf, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000003000000, CR3: 0x00000018229de018, CR4: 0x00000000000226e0
RAX: 0xffffff7f86046280, RBX: 0xffffff9588086014, RCX: 0x0000000002000000, RDX: 0x0000000003000000
RSP: 0xffffffd133b639b0, RBP: 0xffffffd133b639c0, RSI: 0x0000000000008200, RDI: 0xffffff9588086014
R8: 0xffffff8bec3289d0, R9: 0x00000000ffffffff, R10: 0x000000000000001d, R11: 0xffffffa0ba1ea4b0
R12: 0xffffff7f9dd6bf21, R13: 0xffffff90ba93ae80, R14: 0x0000000003000000, R15: 0x0000000000000006
RFL: 0x0000000000010206, RIP: 0xffffff7f860462bf, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000003000000, Error code: 0x0000000000000002, Fault CPU: 0xc, PL: 0, VF: 1
Panicked task 0xffffff95871586a0: 9 threads: pid 165: WindowServer
Backtrace (CPU 12), panicked thread: 0xffffff8beca1d000, Frame : Return Address
0xffffffd133b63360 : 0xffffff8004c83e1d
0xffffffd133b633b0 : 0xffffff8004de3ca6
0xffffffd133b633f0 : 0xffffff8004dd34fd
0xffffffd133b63440 : 0xffffff8004c23a60
0xffffffd133b63460 : 0xffffff8004c841ed
0xffffffd133b63580 : 0xffffff8004c839a6
0xffffffd133b635e0 : 0xffffff80055164af
0xffffffd133b636d0 : 0xffffff8004dd38e3
0xffffffd133b63850 : 0xffffff8004dd35d2
0xffffffd133b638a0 : 0xffffff8004c23a60
0xffffffd133b638c0 : 0xffffff7f860462bf
0xffffffd133b639c0 : 0xffffff7f86100c60
0xffffffd133b639d0 : 0xffffff7f860ffa80
0xffffffd133b63a00 : 0xffffff7f859c8d58
0xffffffd133b63a40 : 0xffffff7f859c8583
0xffffffd133b63a70 : 0xffffff7f859b7cdb
0xffffffd133b63aa0 : 0xffffff7f85a0b81a
0xffffffd133b63b00 : 0xffffff7f859fcc20
0xffffffd133b63b50 : 0xffffff7f9dd5bcc1
0xffffffd133b63be0 : 0xffffff7f859fbda0
0xffffffd133b63c10 : 0xffffff7f9dd51f0e
0xffffffd133b63ca0 : 0xffffff8005414aac
0xffffffd133b63d00 : 0xffffff80054830cb
0xffffffd133b63d60 : 0xffffff8004d89b87
0xffffffd133b63db0 : 0xffffff8004c8a6cb
0xffffffd133b63e10 : 0xffffff8004c5ecf3
0xffffffd133b63e60 : 0xffffff8004c75249
0xffffffd133b63ef0 : 0xffffff8004db6198
0xffffffd133b63fa0 : 0xffffff8004c24246
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(594.0)[3ECB2385-311A-374E-9C0F-65639BA26A05]@0xffffff7f9dd41000->0xffffff7f9dd6ffff
dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff8007803000->0xffffff800782efff
com.apple.kext.AMD9500Controller(4.0.8)[73F58F88-8BFB-39FD-ADD4-B8D9169D4369]@0xffffff7f8597f000->0xffffff7f859e3fff
dependency: com.apple.AppleGraphicsDeviceControl(6.5.4)[3BBDC2AD-9889-3863-82EA-864DCE9D0DEF]@0xffffff7f9c52c000->0xffffff7f9c52ffff
dependency: com.apple.iokit.IOACPIFamily(1.4)[CF250EA9-AE5C-3215-BCF5-763DB70A0228]@0xffffff8007360000->0xffffff8007361fff
dependency: com.apple.iokit.IOGraphicsFamily(594)[3ECB2385-311A-374E-9C0F-65639BA26A05]@0xffffff7f9dd41000->0xffffff7f9dd6ffff
dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff8007803000->0xffffff800782efff
dependency: com.apple.kext.AMDSupport(4.0.8)[C9BA70CD-D5CA-32B9-B28F-45EE36A83E3F]@0xffffff7f9c228000->0xffffff7f9c2edfff
com.apple.kext.AMDRadeonX4000HWLibs(1.0)[731EE448-F9F2-34F7-B05A-A986391D762D]@0xffffff7f85ee0000->0xffffff7f861ddfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff8007803000->0xffffff800782efff
com.apple.kext.AMDFramebuffer(4.0.8)[CCC9B796-5C11-38B9-807E-CAC9CE502386]@0xffffff7f859fb000->0xffffff7f85a1ffff
dependency: com.apple.iokit.IOACPIFamily(1.4)[CF250EA9-AE5C-3215-BCF5-763DB70A0228]@0xffffff8007360000->0xffffff8007361fff
dependency: com.apple.iokit.IOGraphicsFamily(594)[3ECB2385-311A-374E-9C0F-65639BA26A05]@0xffffff7f9dd41000->0xffffff7f9dd6ffff
dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff8007803000->0xffffff800782efff
dependency: com.apple.kext.AMDSupport(4.0.8)[C9BA70CD-D5CA-32B9-B28F-45EE36A83E3F]@0xffffff7f9c228000->0xffffff7f9c2edfff
Process name corresponding to current thread (0xffffff8beca1d000): WindowServer
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-devOn the advice of someone, I tried out OCLP and guess what, it boots into 12.3 completely fine, using it right now. That being said, I am still kind of committed to the cleaner/leaner CDF approach, and OCLP has all kinds of extra kexts installed that I don't have any idea what they are all doing and don't really want them if I don't need them...and numerous settings in config.plist that I don't really like either...
But....It would be good if we could figure out what exactly about the OCLP configuration enables 12.3 to boot on my machine without KP...while the cleaner/leaner/CDF version KP's every time.
I'd rather use clean/lean CDF guide honestly. But...for now...doesn't work for 12.3 on my system.
Add
keepsyms=1 to boot-args to get more detail from the stack trace.According to your original config posted earlier, you've included RadeonBoost. That may be the issue, especially if you haven't also included it in your OCLP setup...
You need to add the attached ASPP-Override companion power management kext.
Duplicate the ASPP-Override block, add it above your ASPP-Override entry and change all instances of
ASPP to AGPM.The issue appears to affect Big Sur as well, so you might want to change the min kernel to
20.0.0. You could use something like 20.4.0 or greater to only catch recent Big Sur but I think the issue has been latent in Big Sur all along and will go with 20.0.0 in MyBootMgr v079b.EDIT:
The attached kext is incomplete and only covers two old Nvidia GPUs
The actual issue was down to running RadeonBoost. See #10,705
Last edited:
That is interesting. I will try removing RadeonBoost to see what happens.
OCLP has a lot of stuff it includes by default, I'll have to check to see if RadeonBoost is part of that, but in general I don't like having all the stuff that is automatically included by default in OCLP...I would much rather use cleaner and leaner simple CDF config. RadeonBoost is about the only thing I was using beyond the guide.
You can read about AGPM-Override here:
github.com
The kext appears to set up parameters for the original Nvidia card (GT 120). I'm not sure it is actually needed.
[Bug]: Wrong AGPM Enabler kext generated for my AMD RX 580 GPU · Issue #525 · dortania/OpenCore-Legacy-Patcher
Machine Model MacPro5,1 Application Version Latest Release Application Variant TUI (Text User Interface) What versions of macOS are you seeing the problem on? macOS 10.15, Catalina Where does this ...
github.com
The kext appears to set up parameters for the original Nvidia card (GT 120). I'm not sure it is actually needed.
Odd that it includes stuff for MP41 and MP51 in that case
I suppose the key will be the "Vendor10deDevice05e2" interpretation which might well be Nvidia
I suppose the key will be the "Vendor10deDevice05e2" interpretation which might well be Nvidia
You can read about AGPM-Override here:
[Bug]: Wrong AGPM Enabler kext generated for my AMD RX 580 GPU · Issue #525 · dortania/OpenCore-Legacy-Patcher
Machine Model MacPro5,1 Application Version Latest Release Application Variant TUI (Text User Interface) What versions of macOS are you seeing the problem on? macOS 10.15, Catalina Where does this ...
The kext appears to set up parameters for the original Nvidia card (GT 120). I'm not sure it is actually needed.
especially since I am using RX580.
Well when I get home tonight I will try it, as well as try removing RadeonBoost and with increased KP logging mentioned above and see what I come up with.
You can read about AGPM-Override here:
[Bug]: Wrong AGPM Enabler kext generated for my AMD RX 580 GPU · Issue #525 · dortania/OpenCore-Legacy-Patcher
Machine Model MacPro5,1 Application Version Latest Release Application Variant TUI (Text User Interface) What versions of macOS are you seeing the problem on? macOS 10.15, Catalina Where does this ...
The kext appears to set up parameters for the original Nvidia card (GT 120). I'm not sure it is actually needed.
In that linked thread, this reply indicates the AGPM override kext isn't useful, at least wasn't back in September 2021:
But if one was to add it to their OC config, then should the board ID in the kext's plist file be the "native" one for your Mac Pro (i.e., MacPro5,1) or for the board being spoofed in the OC config ("Mac-27AD2F918AE68F61" if this guide has been followed).