On 9/7/07, <b class="gmail_sendername">Craig Huff</b> <<a href="mailto:huffcslists@gmail.com">huffcslists@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<snip><br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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><snip><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></blockquote></div><br>
I reported this as bug # 8995 to the Kernel Bug Tracker <a href="http://bugzilla.kernel.org">(http://bugzilla.kernel.org).</a> We'll see if any help comes from that quarter.<br><br>Craig.<br>