public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanno Mueller <sockpuppet@hanno.de>
To: linux-acpi@vger.kernel.org
Subject: How to get /proc/acpi/alarm to work
Date: Wed, 18 Jan 2006 02:42:54 +0100	[thread overview]
Message-ID: <43CD9D1E.6010205@hanno.de> (raw)

Hello,


Linux: 2.6.15.1 vanilla
Mainboard: ASRock P4V88+, revision 1.00
BIOS: Updated to 1.6 (latest release from manufacturer's site)


My mainboard's BIOS allows to set an RTC wakeup time and day (not month
or year) in its ACPI settings.

This will wakeup the system from the S5 state.


Problem: It is not possible to set this value through /proc/acpi/alarm.


It's possible to write valid value to /proc/acpi/alarm and to retrieve
it [1]:

# echo "2006-01-18 03:00:00" > /proc/acpi/alarm
# cat /proc/acpi/alarm
2006-01-18 03:00:00

After a reboot the stored value is broken [2]:

# cat /proc/acpi/alarm
2006-00-00 03:00:00

The alarm time does not wake up the system. It doesn't wake up at
03:00:00 BIOS time, not today, not tomorrow, not on 2006-01-18.

Also, the alarm time does not show up in the BIOS's ACPI settings.
There, one can still find the old values that where entered several
boots ago.


Since the mainboard explicitely lists this function in its ACPI
settings, I guess that the Linux kernel somehow doesn't handle my
mainboard right.

I'm aware that there are many broken ACPI implementations on mainboards
out there. Is there any way I can find out how to fix this issue? Is
there a debugging guide for this? [3]


Thanks,

Hanno



[1] Yes, when I tried this, it was a date and time in the future. I read
somewhere that a past or invalid date will turn off the alarm time setting.

[2] I read in a forum that calling /sbin/hwclock can mess with the alarm
value. When I tried the things above, I removed the /sbin/hwclock calls
from my system's init.d-scripts, but that didn't help.

[3] The same mainboard does not work with nvram-wakeup, which is a
popular older program used by many Linux vdr/pvr setups. nvram-wakeup
uses /dev/nvram to store the wakeup time directly in the NVRAM section.
Ugly, but it works with two other (older) mainboards I tried. On my
current mainboard, however, the alarm timer bytes do not appear to be
accessible through NVRAM.

             reply	other threads:[~2006-01-18  1:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18  1:42 Hanno Mueller [this message]
2006-01-18  1:46 ` How to get /proc/acpi/alarm to work *?* Hanno Mueller
  -- strict thread matches above, loose matches on Subject: below --
2006-01-18  2:47 How to get /proc/acpi/alarm to work Li, Shaohua

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43CD9D1E.6010205@hanno.de \
    --to=sockpuppet@hanno.de \
    --cc=linux-acpi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox