From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Ronald Wielink
<ronald.mythtv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: unable to set alam using echo to /proc/acpi/alarm
Date: Thu, 15 Dec 2005 17:23:46 +0100 [thread overview]
Message-ID: <20051215162346.GI2904@elf.ucw.cz> (raw)
In-Reply-To: <59D45D057E9702469E5775CBB56411F1011BD8A4@pdsmsx406>
Hi!
> >> when I try setting the alarm to wake up my pc I get the following
> >> result:
> >> [root@mithrandir acpi]# pwd
> >> /proc/acpi
> >> [root@mithrandir acpi]# cat alarm
> >> 2005-12-00 00:00:00
> >> [root@mithrandir acpi]# echo 2005-12-15 17:18:19 > alarm
> >> [root@mithrandir acpi]# cat alarm
> >> 2005-12-00 17:18:19
> >> [root@mithrandir acpi]#
> >> BTW, nothing happens at the echo'd date/time. Could someone please
> >> give me a clue where to start looking? I'm running fedora core 4,
> my
> >> mobo is an ASUS P5S800-VM, the documentation on the motherboard
> states
> >> that ACPI is supported. There is an option to turn acpi 2.0 on,
> but no
> >> difference...
> >
> >alarm never worked properly, IIRC.
> It works well on different systems here :).
Okay, so the problem is in me. Could we get some documentation? It
would be useful to know what to expect, and it should probably end up
in Documentation/ somewhere.
Pavel
--
Thanks, Sharp!
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-15 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 17:05 unable to set alam using echo to /proc/acpi/alarm Li, Shaohua
2005-12-14 17:22 ` Kevin Fenzi
2005-12-15 16:23 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-16 1:58 Li, Shaohua
2005-12-12 8:40 Starikovskiy, Alexey Y
2005-12-11 21:29 Ronald Wielink
[not found] ` <302c0a190512111329i76e9e214v4aff822d99ae5de5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-12-12 15:20 ` Pavel Machek
[not found] ` <20051212152008.GA8748-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-12-16 19:40 ` Stefan Seyfried
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=20051215162346.GI2904@elf.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ronald.mythtv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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