Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

[CaseySJ]

After upgrading to Ventura 13.4 from Monterey 13.4, I start getting strange kernel panic, when Hack is idle for long. It happens from time to time — hack is idle (screen is locked, and turned off), and it wont turn on until hard reboot. Monterey was rock solid.

In system log there are a lot of

"
Jun 15 15:11:43 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:_AMMuxedDeviceDisconnected, mux-device:3130
Jun 15 15:11:43 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:3130
Jun 15 15:11:56 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:_AMMuxedDeviceDisconnected, mux-device:3131
Jun 15 15:11:56 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:3131"

Here is my EFI (OC 0.9.1) and panic report text. I have never any such problem before (4 years of happy hackintoshing)

Perhaps there's a third-party application that's not fully compatible with Ventura?

One option is to perform a clean installation of Ventura and test it for stability without installing third-party applications.

 

[statusquo]

Building now but made a rookie mistake. After installing my second m.2 SSD card and put back the heatsink, I accidentally stripped the screw hole. Not sure why they put the hole too close to the edge and also on the grooves.

A better design choice would have been the female thread hex coupling nut.

Did anyone have this problem before?

Other than that, it's been fun so far

 

[beelzebozo]

Building now but made a rookie mistake. After installing my second m.2 SSD card and put back the heatsink, I accidentally stripped the screw hole. Not sure why they put the hole too close to the edge and also on the grooves.

A better design choice would have been the female thread hex coupling nut.

Did anyone have this problem before?

Other than that, it's been fun so far

View attachment 567937

View attachment 567938

Nope. Ouch.

 

[CaseySJ]

Building now but made a rookie mistake. After installing my second m.2 SSD card and put back the heatsink, I accidentally stripped the screw hole. Not sure why they put the hole too close to the edge and also on the grooves.

A better design choice would have been the female thread hex coupling nut.

Did anyone have this problem before?

...

I had this problem on my Asus X670E Gene. Can't understand why they over-tighten these screws.

 

[Feartech]

Building now but made a rookie mistake. After installing my second m.2 SSD card and put back the heatsink, I accidentally stripped the screw hole. Not sure why they put the hole too close to the edge and also on the grooves.

A better design choice would have been the female thread hex coupling nut.

Did anyone have this problem before?

Other than that, it's been fun so far

View attachment 567937

View attachment 567938

You need to have your hardware profile filled out as per rules (the ones you agreed to when signing up here)

https://www.tonymacx86.com/account/account-details

 

[Sn0wMan]

@CaseySJ Today, I added a 4TB SN850X to my Aero G Build and did a fresh installation on the new drive. Currently, two macOS 13.4 in this build (4TB SN850X and 1TB SN850). I used the same copy of OC config in both systems.

The fresh installation fixed the issue that I225-V was not working problem (The driver can be detected, but shows the cable is not connected even though it is connected).

But I met another issue when I boot into the system on SN850X, there is a panic issue and boot loop. Changing UIScale from 02 to 01 could fix the issue, but the OC Picker is too small.

At the same time, keep UIScale=02, there is no panic issue when booting into the system on SN850.

Any suggestions to fix this issue?

 

[CaseySJ]

@Sn0wMan,

I simply set UIScale to 0 so that it picks the best scale automatically. If UIScale is present in NVRAM section of config.plist, it should be removed from there (then do Reset NVRAM one time).

 

[statusquo]

So I have my build ready, and it appears nothing fried after turning on the power supply. Was a bit nervous LOL. Some stuff was easy and some wasn't too obvious especially when the docs was lacking so had to do a ton of research.

I got Windows 10 installed. Haven't had a chance to install all the drivers yet. Should I leave Windows installed like this? Or is there a better way to do it so it can be dual boot with macOS?

I'm still on BIOS version F6. Surprisingly, it's able to detect i5 13600K chipset. I thought it needed an update.

I have a ton to read especially the first page of this thread. What's the recommended BIOS version I should upgrade to? I'm using the DDR5 version. It seems like version F23 has been tested in this thread so will be going with that one.

Also when upgrading the BIOS, can I use @BIOS windows utility to upgrade the BIOS instead of flashing it using a USB stick? What should I watch out for? I wouldn't suggest using @BIOS to upgrade your BIOS. There were 2 options, one was to update from server and another from file. I tried the server but the US server wasn't even responding. I didn't want to try other servers oversea. The update from file is probably similar to downloading the BIOS from Gigabyte website and then extract it to your USB stick, but I wasn't too sure about this method, so I ended up sticking with the traditional method of using USB stick.

All beginners talk

 

[statusquo]

Replying to this 0.8.3 mini guide

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

In my case the boot argument is necessary, otherwise the 1GbE driver gets attached instead of the 2.5GbE driver. I put the above changes on test USB installer stick; I booted into Monterey. No problems > Ethernet working fine. BTW, USB stick has OC 0.8.3 developer version which I'm going to...

www.tonymacx86.com

@CaseySJ
When modifying the Kernel, I noticed the EFI file doesn't have the "ForceAquantiaEthernet" enabled but the image shows that it's enabled. So should this be enabled?

 

[CaseySJ]

Replying to this 0.8.3 mini guide

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

In my case the boot argument is necessary, otherwise the 1GbE driver gets attached instead of the 2.5GbE driver. I put the above changes on test USB installer stick; I booted into Monterey. No problems > Ethernet working fine. BTW, USB stick has OC 0.8.3 developer version which I'm going to...

www.tonymacx86.com

@CaseySJ
When modifying the Kernel, I noticed the EFI file doesn't have the "ForceAquantiaEthernet" enabled but the image shows that it's enabled. So should this be enabled?

If you are using a 10GbE Ethernet adapter then this kernel quirk is required. Otherwise it is optional. There’s no harm keeping it enabled all the time. And if there’s no 10GbE Ethernet adapter installed then it’s okay to disable it.