From: Hanno Mueller <sockpuppet@hanno.de>
To: linux-acpi@vger.kernel.org
Subject: Re: How to get /proc/acpi/alarm to work?
Date: Wed, 18 Jan 2006 11:02:06 +0100 [thread overview]
Message-ID: <43CE121E.8000806@hanno.de> (raw)
In-Reply-To: <59D45D057E9702469E5775CBB56411F101682685@pdsmsx406>
Li, Shaohua schrieb:
> Is it possible you could try the patch at
> http://bugzilla.kernel.org/show_bug.cgi?id=5833?
> Christian Lupien's patch made a lot of improvements on alarm.
Thanks, but no, that didn't solve the problem.
Let me rephrase the description. My BIOS has a different ACPI alarm
value than the value stored in /proc/acpi/alarm.
I can set the RTC alarm wakeup in the BIOS's ACPI settings to:
enabled: yes
day: 18
hour: 15
minute: 10
second: 30
If I look at /proc/acpi/alarm, it doesn't show me "****-**-18 15:10:30"
as one would expect, but a different value.
When doing
echo "2006-01-18 15:20:45" > /proc/acpi/alarm
I get (with Christian's patch):
cat /proc/acpi/alarm
"****-**-** 15:20:45 +int (2006-01-18 10:50:12)"
Now, after rebooting, the BIOS _still_ shows 15:10:30 on day 18 in its
ACPI settings.
So on my system, the BIOS's RTC alarm wakeup ACPI setting appears to be
something different than what /proc/acpi/alarm has access to.
Also, the /proc/acpi/alarm setting does not wake the system from S5,
while the BIOS setting can. And the BIOS can handle the day's number as
a wakeup setting, while /proc/acpi/alarm cannot.
Any idea how to read and change the BIOS's RTC alarm wakeup from Linux?
I have read from users of other mainboards that it works for them
(including the day's number).
As I wrote before, the nvram-wakeup method does not work on this
mainboard, either.
Regards,
Hanno
--
epublica GmbH
http://www.epublica.de
Open Business Club - join: http://www.openbc.com/go/invanon/2
next prev parent reply other threads:[~2006-01-18 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 2:47 How to get /proc/acpi/alarm to work Li, Shaohua
2006-01-18 10:02 ` Hanno Mueller [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 1:44 How to get /proc/acpi/alarm to work? Li, Shaohua
2006-01-19 1:13 Li, Shaohua
2006-01-20 0:52 ` Hanno Mueller
2006-01-18 1:42 How to get /proc/acpi/alarm to work Hanno Mueller
2006-01-18 1:46 ` How to get /proc/acpi/alarm to work *?* Hanno Mueller
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=43CE121E.8000806@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