Contribute
Register

[GUIDE] OC Monterey Z590I Gigabyte VISION D + i9 11900K + AMD RX6600

I see, good for you! It is a great little system... :thumbup:

Well about the stability improvements, I had found using the following settings may help somewhat:

View attachment 554381

View attachment 554382

View attachment 554383

Under Monterey 12.4 I found removing the device-id actually helped but adding the CFG,CFG_USE_AGDC value above helped a lot. For the IGPU I use 03009BC5 for the i9 but for i5 it should be 03009BC8. Then for the GPU I also added the two kexts for the card - RadeonSensor.kext and SMCRadeonGPU.kext, with the CPUID spoofed to Comet Lake.

FYI if it helps for my boot-args I currently use -v alcid=1 keepsyms=1 agdpmod=pikera -lilubetaall -no_compat_check amfi_get_out_of_my_way=1 swd_panic=1
Thanks for the suggestion. I made a number of the changes but the Device Properties eludes me a bit. Below is my current. Do you think I should go with just your highlighted device properties. Most of the other changes I have made re quirks etc.

Current performance is normal for about 1 hour then the machine just hangs and eventually I get the beach ball, it must be something really simple that I'm missing.

1663540856916.png
 
Thanks for the suggestion. I made a number of the changes but the Device Properties eludes me a bit. Below is my current. Do you think I should go with just your highlighted device properties. Most of the other changes I have made re quirks etc.

Current performance is normal for about 1 hour then the machine just hangs and eventually I get the beach ball, it must be something really simple that I'm missing.

View attachment 554921
Yes you should do (use my recommended settings especially the CFG one and agdpmod=pikera). And btw you should delete shikigva as that is no longer used under Opencore or Monterey.
 
@Middleman - I have activated the device properties changes as you suggested. I'm still going through the motions of testing to see how it holds out. It did hang a few times but I just want to keep working to see if there is anything that trips it. Appreciate your help.
Looking at your OC 0.7.8 EFI, there are approx. 21 SSDTs, do you still use all of those?
 
@Middleman - I have activated the device properties changes as you suggested. I'm still going through the motions of testing to see how it holds out. It did hang a few times but I just want to keep working to see if there is anything that trips it. Appreciate your help.
Looking at your OC 0.7.8 EFI, there are approx. 21 SSDTs, do you still use all of those?
Right. And to answer your question no I don't. I only use about 14 so far. This is how I've set them.

Screen Shot 2022-09-20 at 8.17.11 AM.png
 
Right. And to answer your question no I don't. I only use about 14 so far. This is how I've set them.

View attachment 555041
Great, I'm holding off making major SSDT changes at the moment. So far about four hours this morning without any reliability problems. Touch wood.

21.09.2022 - update (edit)
System has performed optimally since instigating the changes under device properties, SSDTs and a number of Kexts.
Thanks again @Middleman

BTW - Geekbench CPU score are about the same before and after, GPU is about 10k points down on CL and Metal. While many argue about the virtue of Geekbench benchmarks, they are effective to measure before and after making changes.
1663708269345.png
 
Last edited:
Okay,

So I've been doing some reading online lately, and it seems some folks are having trouble with this particular motherboard in enablng Thunderbolt, WiFi and Bluetooth. So I thought to put down a few pointers which may help solve issues.

In my build I have a SSDT-TB4HP.aml enabled for the Thunderbolt 4, but in reality I don't think it works so well (because there is yet to be a proper solution for the Maple Ridge chipset). So for anybody listening I would advise you to disable TB4HP and enable (only) the other SSDT-TB3HP instead along with SSDT-DTPG as these two should work to enable Thunderbolt functionality (along with enabled BIOS TB settings). As I recently checked that the SSDT-TB3HP also works with a Z690 Asus Prime P D4 board (it has a TB4 Maple Ridge chipset) so I believe it shouldn't cause any issues.

As to the WiFi and Bluetooth, as the board comes standard with the Intel AX200, I would advise to try to enable BluetoolFixup.kext and IntelBluetoothFirmware.kext for the Bluetooth, and use the OpenIntelWireless Airportitlwm.kext (stable version for Monterey) for the WiFi. If you are using Big Sur then you may need to use the Big Sur stable version or itlwm.kext.

If you are planning to change it to a Broadcom/Fenvi BT/WiFi card, then you would need the following kexts: AirportBrcmFixup.kext, BluetoolFixup.kext, BrcmFirmwareData.kext and BrcmPatchRAM3.kext. If you are using any macOS version before Monterey 12 ie. Big Sur 11 or older such as Catalina 10.15 then discard Bluetoolfixup.kext from the above kexts listing and replace it with BrcmBluetoothInjector.kext (but you will still need the others listed).
 
@nikko20040,

Just informing you and others I have made some changes to the EFI for this board. In addition to the update to OC 0.8.4, Bluetooth for the Intel AX200 has finally been fixed (with IntelBTPatcher) and there is no more lag on login for the RX6600 display.

It may also be worth your time to try this new EFI because of the roughly 10% IPC performance uplift thanks to vit9696's findings on Z590 frequency vector injections using CPUFriend. I am now achieving average score of 9879 vs around 8200 before. FYI I am also using iMac20,2 on the build which I found works better than iMacPro1,1.
 
Hi @Middleman — your system is very similar to mine — the main difference being that I have an RX580 which I think should make things a little simpler. I'm on Big Sur and everything's stable, but am thinking about trying Ventura.

Are you thinking of trying it out?
 
Back
Top