Talk:ACPI Wakeup

From MythTV Official Wiki
Revision as of 04:29, 7 September 2007 by Vossman (talk | contribs) (strage stript for the wakealarm feature in new kernels: correction?)

Jump to: navigation, search

Does this only work on x86_64?

Works fine on X86_32 for me --Benjsc 12:56, 3 October 2006 (UTC)

It works on 32 bit as well. If you miss /proc/acpi/alarm then it seems that this dissapears if you run smp.

Does anyone have experience with the Via EPIA boards? I'm not able to get it working and thus still use nvram-wakeup...

How do I use ACPI wakeups with MythWelcome? The instructions for it are all for using it with nvram-wakeup. --Turpie 11:09, 29 December 2006 (UTC) Looks like capability for ACPI with MythWelcome is coming. Hopefully we'll see an update to the WIKI once 0.21 comes out or sooner if someone with svn version gets ambitious.

2.6.22 Kernels

I just updated my fedora 7 kernel and apparently the 2.6.22 linux kernel removes the /proc/acpi/alarm feature, see does anyone know the new method for these new kernels? --Vossman 06:18, 23 July 2007 (UTC)

There is no documentation, only some hidden description in the git commit that introduced this feature. So I wrote some short documentation, but it isn't included in the source tree yet, AFAIK.

It can be found here:

strage stript for the wakealarm feature in new kernels

The script is somewhat strange in some parts.

# $1 is the --settime switch that nvram-wakeup normally expects
# $2 is the date/time in seconds since 1970

DATE=`date -d "1970-01-01 $2 sec" "+%F %H:%M:%S" -u`
SECS=`date -d "1970-01-01 $2 sec" "+%s" -u`

Why is the argument $2, which is seconds since epoch, converted into seconds since epoch? I think that part can be scratched. Just echo $2 > /sys/class/rtc/rtc0/wakealarm should do fine (at least it does for me)

# Save the wakeup time
echo "$*"  > /myth.wakeup.args
echo $DATE > /myth.wakeup.time
echo $SECS > /myth.wakeup.secs

Why are files written into the root directory? Just scratching the "> /myth.wakeup.args" should be fine, as the echo output can be seen in the backend log then.

Good work guys. Correct me if I am wrong, but can't you just write:

and skip the whole date command? Or does it need to be converted. --Vossman 04:29, 7 September 2007 (UTC)