[SOLVED] Suspend Skylake Fatal1ty z170 gaming-itx

Jessie wrote: Hello, I'm using the Fatal1ty z170 gaming-itx/ac (BIOS 2.1) with an Intel Skylake i3-6320 and I am unable to wake up the computer after putting it in standby. Strangely the first time I suspend the computer, it wakes up correctly. But the second time it is suspended, instead or waking up, it reboot automatically. I am using : - the latest available BIOS : 2.1 - Debian Stable (Jessie) with linux kernel 4.6 and latest intel driver (2.99.917+git20160522-1) However I don't think this is related to the operating system, as it seems that all power is cut immediately as soon as I push the power button to wake up the computer. I also tested the RAM with Memtest86 without any issues. Deactivating the ACPI option "Suspend to RAM" (S3) in BIOS, get the computer to wake up every single time. Can somebody help me ? Thanks

First I must say that Linux of any flavor is not officially supported by your board.

An example of why is what you experience when you "deactivate" (Disable?) Suspend to RAM (S3 Sleep) in the UEFI. The UEFI implementation of Suspend to RAM is tailored to work with Windows. But that implementation does not work with the version/configuration of Linux that you use.

There are likely many examples of this type of difference that creates varying levels of incompatibility. We could debate which are correct, and Windows could be wrong (IMO, more likely) most of the time. But the bottom line is a choice had to be made, and Windows/Microsoft was chosen in this instance.

ACPI is a well defined specification. Entering and exiting the ACPI S3 Sleep state should be a well defined sequence of events. I don't know whom has that done correctly (Windows or the version of Linux you use), or if your Linux configuration has a bug, or Windows does, but it seems clear the implementation ASRock chose to use is not compatible with both OS versions I am discussing here. That choice was made for ASRock by the OS they chose to primarily support.

If waking from Sleep works with your Linux configuration with Suspend to RAM set to Disabled, why does that bother you? For all we know there is a "flag" variable setting in the code (on or off, true or false) that is interpreted in precisely the opposite way in each OS I've mentioned here.

Who cares if "Disabling" something causes it to work correctly for you? The main thing is you can CONFIGURE Suspend to RAM to work correctly with your OS of choice. IMO, to worry or be bothered by setting Suspend to RAM to Disabled to get it working with your OS, IF that is all that is bothering you, does not make sense and is a non-issue.

Computer code can be programmed to interpret Enabled or Disabled as 1 and 0 respectively, or 0 and 1. "True" and "False" are normally 1 and 0 respectively, but those values are arbitrary, they could just as easily be 0 and 1 respectively.

For example, the Enabled setting could be renamed "Enabled for Windows Only", and the Disabled setting renamed to "Enabled for Debian Linux Only", and both settings will disable it for the other OS.

Waking from Sleep problems are very common and sometimes cannot be diagnosed and fixed by ourselves, or anyone. My Intel P67 chipset mother board would not wake from Sleep if left in the Sleep state for more than about 15 minutes. Other owners of this board had the same problem. We discussed this issue in a forum thread (not an ASRock forum) for months and tried to find the cause and a fix. We had all kinds of theories, and a few users apparently got it working, but others including myself, never did.

Honestly, if Sleep and Wake works for me on a PC with all the different hardware and software components I am using, I am pleased and relieved. I have certain mouse models that are unable to wake the PC from Sleep, while others can. I can press the power button and wake the PC when using the mouse that fails to wake the PC.

Sleep and waking from Sleep works fine with my ASRock Z170 Extreme7+ board, using Windows 10. I use Sleep all the time, the PC is configured to enter Sleep automatically after 1/2 hour of inactivity. I trust its operation that much. It sounds like you can configure yours to do the same thing. If setting Suspend to RAM to Disabled does not negatively affect anything else, IMO just do it and move on.

I have been having suspend issues ever since I bought this same motherboard.