Contribute
Register

pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

Anybody else found that sleep isn't working anymore as it should be? If my system enters sleep (from a fresh reboot) I looks ok. System is entering sleep but after a 15 min or so it wakes again. When I don't touch my system it enters sleep again and then it stays a little shorter in sleep let say 10 min. After a while it toggles between sleep and wake (because nobody is logging in). Any ideas? I think something is changed in Ventura causing this. I tried different EFI backups from recent but nog change to them. Powernap is disabled.

After a while this issue came back. I thought it was an USB device as suggested by Pastrychef. The solution was quite simple. It was one of my monitors (the one with an active USB hub) which caused this issue. The input source had "Auto Select" active. Disable this option, enforcing only to use Display Port solved the issue.
 
On the Asus Z370-G, is it normal that one of the Red USB Ports in the back is not full speed? @pastrychef was there something done in port mapping that can cause that? Is it expected?

Using a NVMe in a external USB-C enclosure (USB 3.1 Gen 2 I think), I get an abysmal difference between the two ports.
Screenshot 2022-12-12 at 18.12.30.png

Screenshot 2022-12-12 at 16.59.14.png


Different cables also give different results, so I am just trying to understand... Thanks.
 
On the Asus Z370-G, is it normal that one of the Red USB Ports in the back is not full speed? @pastrychef was there something done in port mapping that can cause that? Is it expected?

Using a NVME in a external USB-C enclosure (USB 3.1 Gen 2 I think) I get an abysmal difference between the two ports.
View attachment 559798
View attachment 559799

Different cables also give different results, so I am just trying to understand... Thanks.

No. Both ports should work in full speed.
 
On the Asus Z370-G, is it normal that one of the Red USB Ports in the back is not full speed? @pastrychef was there something done in port mapping that can cause that? Is it expected?

Using a NVMe in a external USB-C enclosure (USB 3.1 Gen 2 I think), I get an abysmal difference between the two ports.
View attachment 559798
View attachment 559799

Different cables also give different results, so I am just trying to understand... Thanks.
Cabling could be bad.

Or mapping could be off.

If you focus on one port (the bad one) what's the max speed you get, using a known good cable? 40MB/s? If so, it's only doing USB2. Check your port mapping and confirm that physical port has both a USB2 and a USB3 resource assigned to it.

Post your Hackintool USB tab, with something plugged into it using USB3.
 
Cabling could be bad.

Or mapping could be off.

If you focus on one port (the bad one) what's the max speed you get, using a known good cable? 40MB/s? If so, it's only doing USB2. Check your port mapping and confirm that physical port has both a USB2 and a USB3 resource assigned to it.

Post your Hackintool USB tab, with something plugged into it using USB3.
The mapping is from Pastrychef.
I have 2 cables, both work on my MacBook air M1, and thru a hub, I get around 300 mb/s in both.
On my hack 1 of the cables gives me 40 mb/s on both the red ports and another gives me 700-900mb/s on the good port and 40mb/s on the bad one. -- No idea what to make of these results, seem all over the place. I'm new to using nvme's on external enclosures.

Hackintool:
hackintool.png


Not a big deal since at least one port works, but I'm having other issues and was wondering if it could be related.
 
The mapping is from Pastrychef.
I have 2 cables, both work on my MacBook air M1, and thru a hub, I get around 300 mb/s in both.
On my hack 1 of the cables gives me 40 mb/s on both the red ports and another gives me 700-900mb/s on the good port and 40mb/s on the bad one. -- No idea what to make of these results, seem all over the place. I'm new to using nvme's on external enclosures.

Hackintool:
View attachment 559869

Not a big deal since at least one port works, but I'm having other issues and was wondering if it could be related.

Those two USB ports are not part of the Z370 chipset and have their own controller which means they do not need to be "mapped" in the USB config.
 
Hello everybody, it's been a while. I was last active in 2019, when I first completed this build with Clover, running Mojave on the Z370-G. Worked quite well, it's actually been my primary work machine.

Over the course of the past few days I transitioned to OpenCore 0.8.7 and macOS Ventura. Here’s my process:

Preparations:
I bought a new WD Black SN850X drive for my new, clean install, because I read that the Samsung Evo 870 was not working properly with Ventura.

First Try: Dortania DIY EFI
Went through the entire process of Dortanias OC Guide. Spent three hours or more on it. Finally got a bootable USB drive. And then I had a kernel panic and couldn't figure out what caused it, so I was stuck. Then I remembered …

Second Try: Pastrychef's EFI
Tried the supplied 8.7.0 EFI folder on page #1, added Serial Numbers and set to iMacPro 1,1 – and it immediately booted from the drive with no issues. Then I got stuck on a grey screen because I must have plugged my Display on the wrong mDP port, but with some trickery I found my mouse cursor got to see the Installer.

After the installation, the system was up and running, almost OOTB. Only Bluetooth was not working, but I added three kexts: BlueToolFixup.kext, BrcmFirmwareData.kext and BrcmPatchRAM3.kext. And now everything is up and running.

Not Working:
– Wake from Keyboard press (On my previous install, I could only wake from keyboard. Now i can only wake from mouse. Anybody with an idea?)
– Keyboard Display Brightness controls/Hotkeys. (I assume that just doesn't work with external displays. Is there any other solution?)
– On shutdown, my desktop background and dock freezes, and then shuts down completely. (Anybody else have this behaviour? Strange.)

Conclusion
If you're on a Z370G, just go with Pastrychefs EFI. It was a great experience. Thank you @pastrychef.
 
Hello everybody, it's been a while. I was last active in 2019, when I first completed this build with Clover, running Mojave on the Z370-G. Worked quite well, it's actually been my primary work machine.

Over the course of the past few days I transitioned to OpenCore 0.8.7 and macOS Ventura. Here’s my process:

Preparations:
I bought a new WD Black SN850X drive for my new, clean install, because I read that the Samsung Evo 870 was not working properly with Ventura.

First Try: Dortania DIY EFI
Went through the entire process of Dortanias OC Guide. Spent three hours or more on it. Finally got a bootable USB drive. And then I had a kernel panic and couldn't figure out what caused it, so I was stuck. Then I remembered …

Second Try: Pastrychef's EFI
Tried the supplied 8.7.0 EFI folder on page #1, added Serial Numbers and set to iMacPro 1,1 – and it immediately booted from the drive with no issues. Then I got stuck on a grey screen because I must have plugged my Display on the wrong mDP port, but with some trickery I found my mouse cursor got to see the Installer.

After the installation, the system was up and running, almost OOTB. Only Bluetooth was not working, but I added three kexts: BlueToolFixup.kext, BrcmFirmwareData.kext and BrcmPatchRAM3.kext. And now everything is up and running.

Not Working:
– Wake from Keyboard press (On my previous install, I could only wake from keyboard. Now i can only wake from mouse. Anybody with an idea?)
– Keyboard Display Brightness controls/Hotkeys. (I assume that just doesn't work with external displays. Is there any other solution?)
– On shutdown, my desktop background and dock freezes, and then shuts down completely. (Anybody else have this behaviour? Strange.)

Conclusion
If you're on a Z370G, just go with Pastrychefs EFI. It was a great experience. Thank you @pastrychef.

I have never used the BrcmPatchRAM kexts on this build. Not sure if that might be the cause with your wake from keyboard issue... With the BCM94360CS2 card connected to the motherboard M.2, sleep/wake works perfectly.

Try setting the USB port where you have Bluetooth adaptor connect to type 255 in your USB config.

I don't recall anything freezing before shutdown...
 
Last edited:
Back
Top