From: Pavel Machek <pavel@suse.cz>
To: David Brownell <david-b@pacbell.net>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: waking system up using RTC (was Re: rtcwakeup.c)
Date: Sun, 27 Aug 2006 12:17:25 +0200 [thread overview]
Message-ID: <20060827101725.GB9953@elf.ucw.cz> (raw)
In-Reply-To: <200608261704.05017.david-b@pacbell.net>
Hi!
> > > > Your new RTC driver seems to work for me (thinkpad x60), but no, I
> > > > can't get wakeup using RTC to work:
> > >
> > > Does it work using /proc/acpi/alarm? In my experience, ACPI wakeup
> > > doesn't work on Linux ... hence my pleasant surprise to see it work
> >
> > No, I could not get it working using /proc/acpi/alarm.
>
> Then I suspect that's the root cause of your problem ... ACPI code,
> in either Linux or your BIOS, is not sufficiently cooperative. All
> that the rtc-acpi driver does is move the wakeup code, it doesn't
> actually change what the /proc/acpi/alarm stuff does.
I searched the bios; timer wakeup is enabled, but I can't set timer
wakeup from the bios.
> > rtc-acpi 00:07: AT compatible RTC (S4wake) (y3k), 1 month alarm
>
> Seems like Intel's chips won't do one year alarms ... so sad. :)
:-).
(BTW... if STR still does not work on your notebook, let me know, and
we can try to fix that...)
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2006-08-27 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060725124941.GD5034@ucw.cz>
2006-08-26 14:59 ` waking system up using RTC (was Re: rtcwakeup.c) Pavel Machek
2006-08-26 21:15 ` David Brownell
2006-08-26 21:43 ` Pavel Machek
2006-08-27 0:04 ` David Brownell
2006-08-27 10:17 ` Pavel Machek [this message]
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=20060827101725.GB9953@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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