I had experienced this bug with Gutsy and Hardy. It started working again with Intrepid. I currently use it all the time... I have kernel "2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux" My motherboard is an Asus P4P800-E Deluxe
I use the script below, called "MythWakeSet". Note that it clears the RTC before writing to it. #!/bin/bash echo 0 > /sys/class/rtc/rtc0/wakealarm echo $1 > /sys/class/rtc/rtc0/wakealarm readabledate=`perl -e '$date=localtime('$1'); print $date;'` echo "Next Wakeup will be at $readabledate" exit 0 Usage: MythWakeSet [time in epoch] Example: ./MythWakeSet 1232075790 Output: Next Wakeup will be at Thu Jan 15 19:16:30 2009 On Thu, Jan 15, 2009 at 5:51 PM, Leann Ogasawara < leann.ogasaw...@canonical.com> wrote: > Hi Karl, > > Could you test the more recent 2.6.27 kernel available in Intrepid? Or > even the 2.6.28 based kernel which will be available in the upcoming > Jaunty release - http://cdimage.ubuntu.com/releases/jaunty/ . I think > they provide a newer interface to use - /sys/class/rtc/rtc0/wakealarm . > Note that wakealarm uses absolute time in seconds (date + %s). Please > let us know your results. Thanks. > > -- > [GUTSY] RTC alarm does not retain setting from /proc/acpi/alarm > https://bugs.launchpad.net/bugs/139846 > You received this bug notification because you are a direct subscriber > of the bug. > -- [GUTSY] RTC alarm does not retain setting from /proc/acpi/alarm https://bugs.launchpad.net/bugs/139846 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs