Contribute
Register

ASUS prime Z370-A Big Sur 11.2 sleep problem

Uhm, I guess, it means you left out the front dual header, since those ports are the only ones I'm missing, since that's the only single USB header I can't plug elsewhere..

I mistyped above. I left off 1 internal header, not 1 internal port. See below for why.

I started to read the beginner's guide, but I'm too beginner yet, it's pretty difficult for me yet :D if maybe you could help me, and when you have a bit of free time, and sending me the location ID and port number (I guess that's what I need to patch), because I started my investigation with hackintool, but I didn't manage to figure out which one is the one :D

Well, the concept is that each USB 2.0 port counts as 1 port but each USB 3.0 port counts as 2 ports since you can connect either a USB 2.0 or 3.0 device to it. Ignoring the USB 3.1 Gen 2 ports, which are on a separate controller, the Prime Z370-A motherboard has 6 USB 2.0 (HS) and 6 USB 3.0 (SS) ports. Since each USB 3.0 port counts as 2 ports, that's a total of 18 ports, which is 3 more than the 15 port limit for each USB controller allowed by macOS. So I mapped a total of 14 ports: HS01/SS01, HS02/SS02, HS05/SS05, HS06/SS06, HS09, HS10, HS11, HS12, HS13, and HS14.

What I left off was one of the two internal headers for USB 3.0: HS03/SS03 and HS04/SS04. I believe that corresponds to U31G1_34 in the motherboard user manual, which is the one right next to the USB 2.0 headers at edge of the motherboard. You should try connecting your front panel USB 3.0 cable to the USB 3.0 header right next to your SATA connectors, which is U31G1_12, as shown in the attached screenshot.

Lastly, your screenshot shows ports that I didn't map. Are you still using USBInjectAll.kext or someone else's USB port map? If so, I would remove them and try my USBMap.kext again.
 

Attachments

  • USB 3 Headers.png
    USB 3 Headers.png
    95.3 KB · Views: 167
Last edited:
For Lkevin30 and anyone else interested, I have updated my EFI folder to OpenCore 0.7.6. In addition to updating config.plist and the standard suite of kexts, I added FeatureUnlock.kext to support macOS Monterey features. I also updated ScanPolicy to recognize HFS+ file systems so macOS USB installers should now be recognized by OpenCore during boot.
 

Attachments

  • OpenCore 0.7.6 EFI for ASUS Prime Z370A (UHD630 Graphics).zip
    10.5 MB · Views: 112
Hello, here I am once again :D
I managed to configure the USB map, all my ports are working fine, but there's one quite annoying thing.
I'm using a logitech mx518, which has quite useful extra buttons, but they are not functioning until the G Hub can't see the mouse as an active device, and mostly it is being inactive, even tho I can use the mouse basic functions.
And very weird, because it happens frequently that when I mount my EFI partition with OC configurator, my G Hub starts to see asap the mouse connected properly... I had problems with RODE app seeing my wireless GO 2-s earlier, but recently it's working properly, only the Logitech mouse is acting weird. What is going on? thanks again :))
 
I'm using a logitech mx518, which has quite useful extra buttons, but they are not functioning until the G Hub can't see the mouse as an active device, and mostly it is being inactive, even tho I can use the mouse basic functions.

If the basic mouse functions work, then I suspect it's a software driver issue with G Hub. Try removing and reinstalling the driver according to these instructions:


 
I encourage you to give it a try and report back with your findings.

Full disclosure - for the Z370-A board your OC 0.6.8 EFI folder with layout-id=1 under PciRoot(0x0)/Pci(0x1b,0x0) seems to work pretty well, and supports HDMI sound and a discrete RX 580 Pulse just fine, as you might expect.

Ditto on your more recent OC 0.7.6, which also worked just fine on the ASUS Z370-G board.

You have done some great work. Thanks!
 
In addition to updating config.plist and the standard suite of kexts, I added FeatureUnlock.kext to support macOS Monterey features

Do you foresee any need to update OC 0.7.6 for the new Monterey 12.3 update?
 
Do you foresee any need to update OC 0.7.6 for the new Monterey 12.3 update?
Not really. The updates in 0.7.7 and 0.7.8 incorporated fixes that aren't relevant for our motherboard. However, I was planning to update to OC 0.7.9 when I have some time and will post the updated EFI folder here.

Update: I completed the upgrade to OC 0.7.9 and updated my machine to macOS 12.3 without issue. My EFI is attached. As before, you'll need to input your own PlatformInfo values for ROM, MLB, SystemSerialNumber, and your onboard ethernet MAC address to ensure that the various iServices work properly.
 

Attachments

  • EFI.zip
    10.6 MB · Views: 100
Last edited:
What do you find to be the best method for updating OC?

Currently, I start with the latest version of OpenCore, download and install all of the updated kexts and resources, prune the various EFI folders to remove unneeded tools and drivers, and transfer over my old config.plist and SSDT files. I then use a combination of ocvalidate, Propertree, and an app called Meld to update my config.plist. However, I've read that OCAuxiliaryTools (OCAT) offers an automated solution so I might give that a go next time.
 
Back
Top