[Skylake] Flawless Sleep/Wake on Asus boards

[xelanaiznac]

Did you try the darkwake flag?
Was a helping part on "fixing" of my (->Stork) Hero Build...

I think I found out the issue: I had power nap enabled.
my hack infect woke from sleep and then back to sleep again automatically.
I think this was the problem.
let's see this night its behavior

 

[defunkt]

Update

For those it may help, enabling ErP (BIOS: Advanced -> APM) and using the FixShutdown Clover flag fixed my shutdown issue (random restarts).

Has anyone had sleep issues since 10.12.3 and/or Clover 3998?

The ErP and FixShutdown worked for me previously, but all of the sudden it has reverted back to sleeping but not waking.

 

[xelanaiznac]

Has anyone had sleep issues since 10.12.3 and/or Clover 3998?

The ErP and FixShutdown worked for me previously, but all of the sudden it has reverted back to sleeping but not waking.

what do you mean with no waking?
black screen after waking or not waking at all?

 

[defunkt]

what do you mean with no waking?
black screen after waking or not waking at all?

Black screen, have to hold power to hard reboot

Q-Code usually reads "55" or "5d"

Upon reboot, BIOS thinks my "overclocking" failed, have to enter setup to continue.

This is exactly how it was acting before I did the ErP and FixShutdown fixes but have double checked both!

 

[wildwillow]

Black screen, have to hold power to hard reboot

Q-Code usually reads "55" or "5d"

Upon reboot, BIOS thinks my "overclocking" failed, have to enter setup to continue.

This is exactly how it was acting before I did the ErP and FixShutdown fixes but have double checked both!

This is a caution the UEFI BIOS takes when the system has been hard reset rather than properly shut down. When I was testing wake from sleep using HD530 I saw this regularly after a hard reset.

 

[defunkt]

Further testing, system ended up on Q Code "FF" and had to hard reset

Consulting the manual on Q Codes:
FF = "Reserved for future AMI error codes"
5F = "Reserved for future AMI error codes"
55 = "Memory not installed"

Flawless sleep and wake WAS working for me! Trying to nail down what has changed!

 

[wildwillow]

Putting your system in a position where it is locked via a crash or non recoverable state is going to give you "Q codes". Before testing sleep try and make your system 100% functional.

 

[defunkt]

Putting your system in a position where it is locked via a crash or non recoverable state is going to give you "Q codes". Before testing sleep try and make your system 100% functional.

Right, I feel like my system is 100% functional, besides sleep/wake.

I used the fixes detailed on the first post and had great success with sleep/wake.

Suddenly something has changed and I can no longer sleep/wake but my system is very stable if I never enter sleep.

The reason why I mention q codes is that it could be a clue into what's going wrong. The code changes but it is consistent that they appear when sleep happens

 

[xelanaiznac]

hi guys.
has anyone a fix for me?
sierra 10.12.3 with obviously Nvidia web driver.
980 ti, 6700k, maximus VIII hero, imac14,2 system def
the issue is that I have black screen after wake.
post code is 30, so it seems that it is ok.
i have tried with darkwake=no and with darkwake=0

 

[wildwillow]

I used the fixes detailed on the first post and had great success with sleep/wake.

Yoga and myself went through a lot more than BIOS settings to fix sleep. One of the main reasons for sleep failing on 100 series is USB. You should create a USB_SSDT specific to the ports you have connected. These being the Intel USB ports that have a limit as posted in the guides. I can confirm that Sleep does work for me on my ASUS Z170 Deluxe motherboard, recently I added the ThunderboltEX 3 add-in card and I'm connected via a Thunderbolt 3/USB C cable to a 4K monitor and this wakes fine from sleep. The only thing that doesn't work is the USB hub gets ejected on wake from sleep but the picture wakes as normal.