Not having a Westmere Xeon is not a real show stopper - but besides the audio issues, there are several apps that require resources only present with Westmere Xeons - like Extended Page Tables, Unrestricted mode and the NI instructions.
Hmm. Does UIScale=2 produce even bigger icons at the OpenCore boot picker? If so, then you may be limited by the available resolution modes of your display at pre-boot. You can investigate this by generating an OC debug log. See Maintenance > Debugging in the guide.
Enter
sudo powermetrics in Terminal. You'll be able to compare the average frequencies of the CPUs at idle vs under stress (for example, spanning 50%–105%). You'll also see the C-state residencies (notably C6). To see what happens when power management is disabled (partially?), you can enable the VMM flag. You'll see a reduction of the boost frequency (something like 99% vs 105%) and no C-state residency.
Did you review the first post and update your config.plist for Monterey - AVXPel? Read the "Complete your configuration" section and make sure your config.plist is updated for Monterey
I see the image in Disk Utility. It's an HFS volume but erasing it will still leave roughly 12GB of unused partition space. Not quite sure where that partition is located, or how best to fold that back into Big Sur's APFS volume. I'm a bit hesitant to mess around with the main drive's partition mapping...
Thanks. OK so essentially I realised I couldn't boot any of my existing Monterey drives, only the Mojave, until I added more stuff to the kexts and configs. So I skipped all the booting parts and built a new EFI mainly from post 1 but with reference to what Martin Lo's config had. I kept some of his settings like the spoofing code etc since I don't understand the implications yet. I used the verify function to check the confiq was ok and downloaded new versions of WG and Lilu etc and eventually got it to boot back to Monterey, but now OC 085.
Yes, and if you spoof the 2019 Mac Pro board ID (as recommended for modern versions of macOS, namely Catalina and later), you'll also need to keep the "-no_compat_check" boot argument (or press Command-C-Minus) before selecting Mojave on the OpenCore boot menu.
You'll have to switch it back to Disabled unless you spoof the iMac Pro board ID, which allows for booting Mojave even without "-no_compat_check" (or the corresponding key combination). Alternatively, you can always boot Mojave natively (see Maintenance > Disabling OpenCore in the guide).
No.
No need for this patch if you've made your NVMe drives internal as described in the guide.
These apply to patches (like AVXpel) that may become problematic (though unlikely) in future versions of macOS. The guide includes the latest values (look for AVXpel and SurPlus).
If you've moved your card, make sure to update the path. With device properties, you'll be able to clean up the corresponding boot arguments ("wegtree=1" and "unfairgva=1" and others depending on your spoofing strategy).
The caveat with the iMac Pro board ID (Mac-7BA5B2D9E42DDD94) is that you have to apply the "agdpmod=pikera" device property (or the corresponding boot argument) to avoid a black screen after booting. Moreover, some ports of some graphics cards may not work. This is the reason the 2019 Mac Pro board ID (Mac-27AD2F918AE68F61) is recommended for modern versions of macOS.
It most certainly does. Thank you for a detailed and considered reply 👍
You can remove these if you’ve added the corresponding device properties ("rebuild-device-tree" and "unfairgva") as described in the guide (device properties should work with your RX 580). With Mac-27AD2F918AE68F61, these are the only two properties that you need for hardware acceleration and DRM in Monterey.
Yes. Ordinarily, there is no need for boot arguments. This is also true for "DefaultBackgroundColor". More important: "csr-active-config" shouldn't be overridden like this (unless you are doing hard patching and bootability depends on it) because you can always adjust it (if needed) in Recovery as intended by Apple. Try with a clean NVRAM section as described in the guide. If something breaks, then we can address it.
It seems that your config is not up to date. Both "AllowNvramReset" and "AllowToggleSip" were removed in version 0.8.1, "LegacyEnable" was removed in 0.8.3, and "LoadEarly" was added in 0.8.3. You can track down these changes by clicking on the "WikiPost History" button at the bottom of the guide, then view "Update to OC 0.8.2" and "Update to OC 0.8.4". There, you'll find the pertinent update notes in the section Maintenance.
Try with "PickerAttributes=16" (0x10). You can also try clicking your mouse a few times (that seems to be required for the boot picker to become responsive to a Bluetooth mouse).
I have read this post and the updated Open Core Setup post #1. It doesn’t mention any firmware requirements. Do you need any particular firmware version patched or otherwise? Which one do you use btw? Thanks! PS. If you decide to create packages with your USB hub with the GPIO port(s) and cables. I would definitely be interested in purchasing a kit from you. 👍🏻
So the guide is for a “flashed-for-Mac” GC-Titan Ridge card. As long as the firmware enables Thunderbolt bus (device present under System Information > Thunderbolt), you should be good to go.
I use my own modified NVM23. I’ll provide the file and full documentation shortly.
I’ll also provide more information about this.
You can go to your Fireface Settings app and try setting the 'Bandwidth Limit' to e.g. Analog+AES, something lower than 'All Channels'. Does it help? If you don't have a Westmere Xeon CPU that could be a problem.
Hello, thanks for the answer, I will try what you say, although in Mojave and with the same equipment there is no problem, everything works fine.
