On 12/20/07, <b class="gmail_sendername">Jonathan Rogers</b> <<a href="mailto:jonner@teegra.net">jonner@teegra.net</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;">
There already is some documentation at<br><URL:<a href="http://mythtv.org/wiki/index.php/ACPI_Wakeup">http://mythtv.org/wiki/index.php/ACPI_Wakeup</a>>.<br><br>Since I use Ubuntu, I found this slightly more useful:<br>
<URL:<a href="https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake?highlight=%28wakeup%29%7C%28acpi%29">https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake?highlight=%28wakeup%29%7C%28acpi%29
</a>></blockquote><div><br>Yup, I've been through both of those documents. Waking up is not a problem. Shutting down is. I don't know how to make Myth take the settings I give it (I've restarted Mythbackend after making changes) but it simply won't sleep. Is it because I have nothing scheduled to record so it doesn't have a wake-up time?
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am using SVN trunk, so some mythwelcome/mythshutdown settings have changed.</blockquote>
<div><br>I'm using Mythbuntu 7.10 and whatever version of Myth comes with that -- probably the latest in Ubuntu's Gutsy repos.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
For my Abit motherboard, I found two things in those docs essential:<br>* I disabled the wakeup feature in the BIOS setup.<br>* I modified my hwclock.sh script so that the wakeup time is written<br>to /proc/acpi/alarm twice after the hardware clock is set.
</blockquote><div><br>I haven't disabled wakeup in BIOS (quite frankly don't know if it's set) but since it wakes up without a problem, I never bothered to change it. Do you think the BIOS wakeup could possibly prevent Myth from shutting down? I doubt it.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yeah, I've been testing my setup and saw the same thing. I set a short<br>
idle timeout in mythtv-setup of 30s. My mythtvbackend log contains<br>lines like "I'm idle now... shutdown will occur in 30 seconds." and<br>"Waited more than 60 seconds for shutdown to complete - resetting idle
<br>time". I don't know if there's a bug in mythbackend or mythshutdown or<br>what. However, it does eventually shut down, though it takes longer<br>than it seems it should.</blockquote><div><br>How did you get it to output that? I see nothing like it in my logs. Just for fun I ran the following:
<br><br>myth@libra:~$ sudo sh -c 'echo "+00-00-00 00:05:00" > /proc/acpi/alarm'<br>myth@libra:~$ mythshutdown -v all --shutdown<br>2007-12-20 09:59:47.203 Mythshutdown: --shutdown<br>2007-12-20 09:59:
47.204 MSqlQuery: SELECT data FROM settings WHERE value = 'DailyWakeupStartPeriod1' AND hostname IS NULL;<br>2007-12-20 09:59:47.204 MSqlQuery: SELECT data FROM settings WHERE value = 'DailyWakeupEndPeriod1' AND hostname IS NULL;
<br>2007-12-20 09:59:47.204 MSqlQuery: SELECT data FROM settings WHERE value = 'DailyWakeupStartPeriod2' AND hostname IS NULL;<br>2007-12-20 09:59:47.205 MSqlQuery: SELECT data FROM settings WHERE value = 'DailyWakeupEndPeriod2' AND hostname IS NULL;
<br>2007-12-20 09:59:47.205 no daily wakeup times are set<br>2007-12-20 09:59:47.205 MSqlQuery: SELECT data FROM settings WHERE value = 'MythShutdownNextScheduled' AND hostname IS NULL;<br>2007-12-20 09:59:47.205 no recording time is set
<br>2007-12-20 09:59:47.205 no wake up time set and no scheduled program<br>2007-12-20 09:59:47.206 MSqlQuery: DELETE FROM settings WHERE value = 'MythShutdownWakeupTime';<br>2007-12-20 09:59:47.207 MSqlQuery: INSERT INTO settings ( value, data ) VALUES ( 'MythShutdownWakeupTime', NULL );
<br>2007-12-20 09:59:47.207 MSqlQuery: SELECT data FROM settings WHERE value = 'MythShutdownNvramRestartCmd' AND hostname = 'libra' ;<br>2007-12-20 09:59:47.207 everything looks fine, shutting down ...<br>
2007-12-20 09:59:47.208 MSqlQuery: SELECT data FROM settings WHERE value = 'MythShutdownPoweroff' AND hostname = 'libra' ;<br>2007-12-20 09:59:47.208 ..<br>2007-12-20 09:59:47.208 .<br>2007-12-20 09:59:47.208
shutting down ...<br>2007-12-20 09:59:47.274 SSDPCache - Destructor<br>2007-12-20 09:59:47.274 UPnpDeviceDesc - Destructor<br>myth@libra:~$<br>Broadcast message from myth@libra<br> (/dev/pts/1) at 9:59 ...<br><br>
The system is going down for maintenance NOW!<br>Connection to libra closed by remote host.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've been using the hibernate command as the mythwelcome/mythshutdown<br>shutdown command. It can use several different suspend methods<br>including suspend to RAM and suspend2. Right now I'm wondering if<br>mythbackend isn't expected to still exist after running a shutdown
<br>command. Maybe everything would be smoother if I shut down mythbackend<br>before suspending and restarted it after resuming.</blockquote><div><br>I'd like to get regular shutdowns working before I start playing with suspend, though at some point that is a goal as well.
</div></div><br>I think the gap that I'm missing is how to get Myth to consider itself idle and then shutdown (even if it doesn't have a wake up time). After that I'll look into WOL to force it to wake if it's asleep.
<br><br>Thanks for your help,<br>Brion<br>