Contribute
Register

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

Schermafbeelding 2019-09-13 om 08.48.20.png

This one?
 
UPDATE.
I think I nailed it. I turn GFX in BIOS to PCI instead of Auto and now sleep\wake up works just fine. In High sierra it didn't cause any issues, but in Mojave it does. Or maybe it was fine with Nvidia and not fine with Vega, who knows.

Anyway, thank you one more time, you are the best!
I'll keep you posted if something goes wrong.

pastrychef said:
So right now, when your system goes to sleep, it powers off?

Please enter the following in to Terminal and post the output:
Code: 
pmset -g log | grep -i failure
Click to expand...

It kinda turns off. Power LED doesn't blink so something happens before I wake it up I guess
2019-09-12 20:34:17 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:
2019-09-12 20:46:43 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:
2019-09-12 23:48:26 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:
2019-09-12 23:58:19 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:


Here is my pmset
System-wide power settings:
Currently in use:
standby 1
Sleep On Power Button 1
womp 0
autorestart 0
hibernatefile /var/vm/sleepimage
proximitywake 1
powernap 0
networkoversleep 0
disksleep 10
standbydelayhigh 86400
sleep 15 (sleep prevented by SubmitDiagInfo, sharingd, mds_stores)
autopoweroffdelay 28800
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 15
highstandbythreshold 50
standbydelaylow 0
 
Last edited:
Mech314 said:
UPDATE.
I think I nailed it. I turn GFX in BIOS to PCI instead of Auto and now sleep\wake up works just fine. In High sierra it didn't cause any issues, but in Mojave it does. Or maybe it was fine with Nvidia and not fine with Vega, who knows.

Anyway, thank you one more time, you are the best!
I'll keep you posted if something goes wrong.



It kinda turns off. Power LED doesn't blink so something happens before I wake it up I guess
2019-09-12 20:34:17 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:
2019-09-12 20:46:43 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:
2019-09-12 23:48:26 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:
2019-09-12 23:58:19 -0500 Failure Sleep Failure [code:0xFFFFFFFF0000001F]:


Here is my pmset
System-wide power settings:
Currently in use:
standby 1
Sleep On Power Button 1
womp 0
autorestart 0
hibernatefile /var/vm/sleepimage
proximitywake 1
powernap 0
networkoversleep 0
disksleep 10
standbydelayhigh 86400
sleep 15 (sleep prevented by SubmitDiagInfo, sharingd, mds_stores)
autopoweroffdelay 28800
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 15
highstandbythreshold 50
standbydelaylow 0
Click to expand...

I always had primary display set to my dGPU in BIOS.

Those failure messages don't give enough info.

peset looks fine.
 
pastrychef said:
I always had primary display set to my dGPU in BIOS.

Those failure messages don't give enough info.

peset looks fine.
Click to expand...
How is opencore btw? Worth trying it?
 
Hey I just wanted to ask for some clarification on the USB fix so I understand it properly. (also thanks for the awesome guide pastrychef).

So in the 1st post you said to lower the ports down to 15, and then also link another helpful post which includes a list of all the ports on the mobo (#3005).

However in the image you provided the labels for the ports don't match up to the list on that post? For instance you reference SS10 which is not on that list or in the aml as far as I can tell. Also many people seem to exclude HS08, but that isn't referenced either?

I think I set mine up ok, but what would happen if you disabled the port limit patches and then had more that 15 ports available? Just trying to understand it better, if anyone can help cheers.
 
dupligh0st said:
Hey I just wanted to ask for some clarification on the USB fix so I understand it properly. (also thanks for the awesome guide pastrychef).

So in the 1st post you said to lower the ports down to 15, and then also link another helpful post which includes a list of all the ports on the mobo (#3005).

However in the image you provided the labels for the ports don't match up to the list on that post? For instance you reference SS10 which is not on that list or in the aml as far as I can tell. Also many people seem to exclude HS08, but that isn't referenced either?

I think I set mine up ok, but what would happen if you disabled the port limit patches and then had more that 15 ports available? Just trying to understand it better, if anyone can help cheers.
Click to expand...

There are ports that are not used by the motherboard.

  • On all Z370, 26 ports are available from the chipset level.
  • Motherboard manufacturers can build motherboards with up to 26 ports. (I don't know of any that use all 26)
  • The ports you mentioned, SS10 does not exist and HS08 is not used.
  • Even if a port is not used, it should still be excluded because, if you don't exclude it, macOS will think your motherboard has that port.

  • macOS only expects to 15 ports to be available.
  • If more are available, you may see unexpected/werid behavior. Most common is broken sleep. Another common issue is ports may lose USB3 functionality. Or, devices, simply won't work right.

Yes, there are patches to raise the port limit. However, these patches are often broken with macOS updates leaving you to chase down the latest patch. These patches are considered as temporary workarounds and should only be used until a proper fix is applied.
 
ok so you said SS10 doesn't exist, but your example shows the flag as:
uia_exclude=HS08;HS11;HS12;HS13;HS14;SS07;SS08;SS09;SS10;USR1;USR2

So if a port doesn't exist can you just exclude it for 'free'? Like it still counts to lowering the ports to 15?

For reference my flag is:
uia_exclude=USR1;USR2;HS07;HS08;HS09;HS10;HS11;HS12;HS13;SS03;SS04

So could I swap some of these out for the SS07-SS10 or?
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top