Public bug reported:
In Hardy, the cpu wakeup on alarm is working by writing the date/time to
/proc/alarm/rtc. In Intrepid, I write the date/time to
/sys/class/rtc/rtc0/wakealarm during system startup and shutdown.
I also reset the wakealarm before writing the date/time:
echo 0 > /sys/class/rtc/rtc0/wakealarm
I verified that the alarm date/time is also set properly:
cat /proc/driver/rtc:
rtc_time : 17:51:46
rtc_date : 2008-08-18
alrm_time : 16:30:00
alrm_date : 2008-08-19
alarm_IRQ : yes
alrm_pending : no
24hr : yes
periodic_IRQ : no
update_IRQ : no
HPET_emulated : yes
DST_enable : no
periodic_freq : 1024
batt_status : okay
However, after halt/shutdown, the computer does not wakeup (in Hardy
this works).
If I don't write the date/time during startup/shutdown once the alam is
setup properly, during next boot, the alarm date from /proc/driver/rtc
shows something like:
alrm_date : ****-08-19
Some modules are over-writing the setup alarm? Please confirm.
Some mythtv users are using this feature (wakeup from bios) based on
google.
** Affects: ubuntu
Importance: Undecided
Status: New
--
[INTREPID] /sys/class/rtc/rtc0/wakealarm is not working
https://bugs.launchpad.net/bugs/259149
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
