<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16525" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=063220413-07092007><FONT face=Arial
color=#0000ff size=2>Craig,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=063220413-07092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=063220413-07092007><FONT face=Arial
color=#0000ff size=2>I wrote an nvram-wakeup replacement call acpi-wakeup.
It is a bash script that is command line compatible with nvram-wakeup, but uses
the proc acpi interface and handles epoch data etc. The acpi path is just
a constant you can change.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=063220413-07092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=063220413-07092007><FONT face=Arial
color=#0000ff size=2>It would need a tweak to work for you situation, but your
welcome to play with it. I can put it on <A
href="http://www.generationd.com">www.generationd.com</A> if you want
it.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=063220413-07092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=063220413-07092007><FONT face=Arial
color=#0000ff size=2>MD</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mythtv-users-bounces@mythtv.org
[mailto:mythtv-users-bounces@mythtv.org] <B>On Behalf Of </B>Craig
Huff<BR><B>Sent:</B> Friday, September 07, 2007 8:56 AM<BR><B>To:</B>
mythtv-users@mythtv.org<BR><B>Subject:</B> [mythtv-users] Real Time Clock
Alarm Broken with 2.6.22+ kernel<BR></FONT><BR></DIV>
<DIV></DIV>Hi, all<BR><BR>For your information:<BR><BR>I had done a lot of
work to figure out how to get the RTC alarm to work in FC6 on my system
so<BR>MythTV can wake from Suspend-to-disk/Power Off to do mythfilldatabase
jobs and to wake <BR>in time to record scheduled programs. <BR><BR>I upgraded
everything last week when I needed to move MythTV up to the latest version to
switch<BR>over to SchedulesDirect for collecting TV schedule data.<BR><BR>I
posted a message on the atrpms list when I discovered that my system wasn't
waking up anymore <BR>and found that /proc/acpi/alarm didn't exist. A
kind soul (apparently a kindred MythTV user) replied<BR>with a pointer to the
updated wiki page: <A
href="http://www.mythtv.org/wiki/index.php/ACPI_Wakeup">http://www.mythtv.org/wiki/index.php/ACPI_Wakeup
</A>which <BR>has had an update about the change the kernel gurus did,
changing the path to the alarm to be<BR>/sys/class/rtc/rtc0/wakealarm.
While they were at it, they changed the format of the value from
the<BR>former, human-readable string to the seconds since the "epoch" (see
man-page regarding "date +%s"). <BR>Oh, and they changed the code behind it so
that to change the alarm you have to first reset it, which<BR>can be done
(amongst other ways) by "echo 0 > /sys/class/rtc/rtc0/wakealarm".
Finally, don't expect <BR>the value you get back to equal the value you put in
to the alarm unless your mobo is (in my experience)<BR>the rare bird that
REALLY takes the WHOLE alarm setting, including month and year. You're
more<BR>likely to see "echo 12345 > /sys/class/rtc/rtc0/wakealarm; cat
/sys/class/rtc/rtc0/wakealarm" return <BR>a value like 87654399899 (made up
number on my part). From googling, it appears that this will be <BR>the
original value plus a TBD constant that depends on your mobo.
YMMV.<BR><BR>However...<BR><BR>On my system, the code changes behind the new
design have broken the alarm function completely. <BR>I have tried disabling
the hwclock update in /etc/init.d/halt, turned on all the elements in
/proc/acpi/wakeup,<BR>and enabled on the (old technology) APM alarm in the
BIOS, all to no avail.<BR><BR>If some kind soul has gotten further with this
"improvement" and can give me any ideas how to fix this, <BR>short of
regressing to a kernel < 2.6.22, I would appreciate it.
AAAAUUUUGGGHHHH!!!!!<BR><BR>Craig.<BR><BR>P.S. If I forgot to mention some
detail of relevance, please remind me to reply with the appropriate data.
<BR></BLOCKQUOTE></BODY></HTML>