@baskerville That's precisely why I mistakenly thought the H2O couldn't schedule a wake up. To illustrate using your lines:
Code:
[root@(none) ~]# cd /sys/class/rtc/rtc0/
[root@(none) rtc0]# ls
date hctosys power time
dev max_user_freq since_epoch uevent
device name subsystem
Code:
[root@(none) rtc0]# WAKE_ALARM=/sys/class/rtc/rtc0/wakealarm
[root@(none) rtc0]# echo 0 > "$WAKE_ALARM"
-sh: can't create /sys/class/rtc/rtc0/wakealarm: nonexistent directory
Nevertheless, the H2O can wake up if you ioctl RTC_WKALM_SET in spite of not having a /sys/class/rtc/rtc0/wakealarm sysfs file.
You can still query the state through /proc/driver/rtc.
Code:
# ./rtcwake -m on -s 300
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup using /dev/rtc0 at Tue Feb 1 12:26:53 2011
^C
[root@(none) sbin]# cat /proc/driver/rtc
rtc_time : 12:22:10
rtc_date : 2011-02-01
alrm_time : 12:26:53
alrm_date : 2011-02-01
alarm_IRQ : yes
alrm_pending : no
24hr : yes