[mythtv-users] WakeOnAlarm: Searching for the cause of failure

[victor rajewski]

On 10/30/07, Peter Carlsson <maillist.peter at home.se> wrote:
> Hello!
>
> I have once again been in contact with Gigabyte supprt, which have been
> very supportive.
>
> They have tested with a setup similar to mine with only a minimum of
> components and I have done the same. I also followed the exact same
> steps as they did and it worked immediately! I then put one component
> back at a time and tested the Wake-On-Alarm and it still worked after
> all components were back in the computer!?!
>
> The steps suggested by Gigabyte support:
> - Load Optimized Defaults in BIOS
> - Set correct BIOS time
> - Save BIOS settings and exit
> - Computer will reboot
> - Enter BIOS setup
> - Set Power-On by Alarm [Enabled]
> - Set Day of Month Alarm [Everyday]
> - Set wakeup time 5-10 minutes in the future
> - Save BIOS settings and exit
> - Computer will reboot
> - After reboot turn power off (press power button for 4 seconds)
>
> The only differences from these steps I can recall are that I didn't
> load the Optimized Defaults and also instead of holding down the power
> button for 4 seconds I issued the poweroff command from the root account.
>
> Is there something I have to do for this to work with the poweroff
> command? Suggestions about what I should do next?
>
> I also noticed that the wakeup time was found after a successful startup:
>
> htpc:~# cat /proc/acpi/alarm
> 2007-00-00 17:55:00
>
> For background information, please see my previous mails.

Here's my experience, fwiw, on a gigabyte ga-m61p-s3. Under feisty (I
think kernel 2.6.18), acpi wakeup worked fine. After upgrading to
gutsy it stopped working. But as I subsequently discovered, it only
stopped on a 'proper' shutdown. If I put the computer to sleep or
hibernate, it wakes up at the correct time. Try that and see if it
helps. I'm guessing that's to do with the shutdown scripts writing
back the time (as previously mentioned), but curiously, why did it
work under feisty?

vik