Wake by rtc alarm not working Gigabyte H110M-S2H-CF

[Meindert66]

Hello,

On my both Linux (debian) systems it is not possible for me get the wake up on alarm working. I tried a lot of settings in the Bios and followed the instructions on this page: http://www.mythtv.org/wiki/ACPI_Wakeup

MoBo: Gigabyte H110M-S2H-CF
Software: Linux (debian)

According to Gigabyte I should bring the machine in state S5. What I tried but not helped:
- shutdown -h now
- shutdown -P now

EXTRA info: I find out that if I select a time in the bios and shutdown (shutdown -h now) the system started just fine from the alarm time. The problem seems to be that it is not possible to write the bios alarm with a new time.

Simple test to wake the machine 5 minutes from now should be like (but is not working for me):

sudo bash -c "echo 0 > /sys/class/rtc/rtc0/wakealarm"
sudo bash -c "echo `date '+%s' -d '+ 5 minutes'` > /sys/class/rtc/rtc0/wakealarm"
cat /sys/class/rtc/rtc0/wakealarm
sudo shutdown -h now

 

[Calvin7]

use shutdown -p now to turn the power off immediately
shutdown -h now requests that the system be halted after it has been brought down

With each successive sleep state, from S1 to S4, more of the computer is shut down. S5 is the classic complete shutdown power state. Your not going to wake up the PC from a shutdown state.

System Sleep States

System Power State S0 – This is the Working State, where your Windows PC is awake. This is not a Sleep state.

System Power State S1 – In this sleep state, the CPU is stopped and your computer is in standby mode. If the next S3 state is note supported, this S2 is the default state on most hardware. The Processor clock is off and bus clocks are stopped. In this state, the power consumption could be between 5 – 30 Watts.

System Power State S2 – This state is similar to S1 except that the CPU context and contents of the system cache are lost because the processor loses power.

System Power State S3 – In this state, data or context is saved to RAM and hard drives, fans, etc. are shut down. The power consumption is usually less than 5 Watts. Wake-On-LAN is supported from S3 (Sleep) or S4 (Hibernate) state in Windows 10/8.

System Power State S4 – In this state, data or context is saved to Disk. It is also known as the Hibernate state and is useful for laptops. Your PC saves the contents of RAM to the hard disk. The hardware powers off all devices. Operating system context, however, is maintained in a hibernate file that the system writes to disk before entering the S4 state. Upon restart, the loader reads this file and jumps to the system’s previous, pre-hibernation location. Power consumption is again less than 5 Watts.

 

[Meindert66]

use shutdown -p now to turn the power off immediately
shutdown -h now requests that the system be halted after it has been brought down

With each successive sleep state, from S1 to S4, more of the computer is shut down. S5 is the classic complete shutdown power state. Your not going to wake up the PC from a shutdown state.

System Sleep States

System Power State S0 – This is the Working State, where your Windows PC is awake. This is not a Sleep state.

System Power State S1 – In this sleep state, the CPU is stopped and your computer is in standby mode. If the next S3 state is note supported, this S2 is the default state on most hardware. The Processor clock is off and bus clocks are stopped. In this state, the power consumption could be between 5 – 30 Watts.

System Power State S2 – This state is similar to S1 except that the CPU context and contents of the system cache are lost because the processor loses power.

System Power State S3 – In this state, data or context is saved to RAM and hard drives, fans, etc. are shut down. The power consumption is usually less than 5 Watts. Wake-On-LAN is supported from S3 (Sleep) or S4 (Hibernate) state in Windows 10/8.

System Power State S4 – In this state, data or context is saved to Disk. It is also known as the Hibernate state and is useful for laptops. Your PC saves the contents of RAM to the hard disk. The hardware powers off all devices. Operating system context, however, is maintained in a hibernate file that the system writes to disk before entering the S4 state. Upon restart, the loader reads this file and jumps to the system’s previous, pre-hibernation location. Power consumption is again less than 5 Watts.

Thanks but the problem is different than I wrote as Initial issue. I find out that if I select a time in the bios and shutdown (shutdown -h now) the system started just fine from the alarm time.
The problem seems to be that it is not possible to write the bios alarm with a new time.

Simple test to wake the machine 5 minutes from now should be like (but is not working for me):

sudo bash -c "echo 0 > /sys/class/rtc/rtc0/wakealarm"
sudo bash -c "echo `date '+%s' -d '+ 5 minutes'` > /sys/class/rtc/rtc0/wakealarm"
cat /sys/class/rtc/rtc0/wakealarm
sudo shutdown -h now