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>