On 10/9/07, <b class="gmail_sendername">Peter Carlsson</b> <<a href="mailto:maillist.peter@home.se">maillist.peter@home.se</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;">
Hello Craig!<br><br>> Peter,<br>><br><br>I'm running Debian. Even if it's aimed at Ubuntu I found the following<br>very informative and I have tried to follow it.<br><a href="https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake">
https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake</a><br><br>><br>> HTH.<br><br>Unfortunately not. WOL and wake-on-keyboard works for me. The problem<br>for me is that no matter what I set in the BIOS it will not wake up.
<br><br>If you are able to dig up anything else I would very much appreciate it.<br>Thanks for the advice so far.<br><br></blockquote></div>Peter,<br><br>Paul Harrison has jogged my memory about another "gotcha". IIRC, some
<br>motherboards tie the BIOS setting for the APM RTC alarm function to the<br>ACPI RTC alarm function so either they're both enabled or both disabled.<br>Just to confuse everyone (I think ;-) others have them diametrically opposed
<br>so that enabling the APM RTC alarm function effectively disables the ACPI<br>RTC alarm function and vice versa. In short, you need to try tests with both<br>states of the BIOS controlled APM RTC alarm function. If you have no luck
<br>with either state, then try them again with the reboot operation put into effect.<br><br>IIRC, Matthias Hensler's webpage for Suspend2 under Fedora Core had some<br>discussion of how to work with motherboards that require reboots to get the
<br>alarm to work. See <a href="http://mhensler.de/swsusp/">http://mhensler.de/swsusp/</a><br><br>Another place to research is the ACPI HOWTO created by Ariel Glenn at<br>Columbia University. See <a href="http://www.columbia.edu/%7Eariel/acpi/">
http://www.columbia.edu/~ariel/acpi/</a><br>At times, I found the text version to be better to work with and at others, the<br>html version worked better. I guess it depended on whether I was really reading<br>the text or chasing the cross-references.
<br><br>Perhaps some of these suggestions will help.<br><br>Craig.<br>