<!DOCTYPE html><html><head>
<style type="text/css">body { font-family:'DejaVu Sans'; font-size:13px}</style>
</head>
<body>On Wed, 28 Aug 2013 22:44:03 +0100, Daryl McDonald <darylangela@gmail.com> wrote:<br><br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 28, 2013 at 4:56 PM, Karl Dietz <span dir="ltr"><<a href="mailto:dekarl@spaetfruehstuecken.org" target="_blank">dekarl@spaetfruehstuecken.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 28.08.2013 22:33, Daryl McDonald wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
If I understand it correctly using UTC or not is a decision that is<br>
mostly made depending on presence of other (Windows) operating systems<br>
dual-booting on the same hardware.<br></div><div class="im">
I do have dual boot, so I should opt for RTC?</div></blockquote></blockquote></div></div></div></blockquote><div><br></div><div>To repeat Chris/Karl: RTC is the BIOS clock - it can be set to use either UTC (Linux default) or localtime (Windows default). As previously, stated you can hack Windows to use UTC but it's probably simpler to keep it as localtime (which it seems to be at the moment). The important point is </div><div>to make Linux aware of this - your /etc/default/rcS should have:</div><div><br></div><div># assume that the BIOS clock is set to UTC time (recommended)<br>UTC=no<br></div><div><br></div><div>The hwclock-save.conf script uses this to set the clock using localtime.</div><div><br></div><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
</div></blockquote>
<br>
according to the other mail you can choose to set your hardware clock<br>
chip to:<br>
* local wall clock time and add the conversion between UTC and local<br>
time to your MythTV shutdown script<br>
* UTC without any calculations on the linux side, but needs a registry<br>
hack for windows (see Chris' mail, this option is new to me)<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't get the option for S5, just 1,2,3, or auto, and terminal output<br>
says I can wake from S4...more confusion<br>
</blockquote>
<br></div>
S5 is what happens when you tell the computer to power off instead of<br>
some kind of sleeping.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* your tuners support whichever power saving state you decide on (do<br>
they need special fiddling to come back to working state?)<br>
<br>
Don't know how to do that<br>
</blockquote>
<br></div>
look for known issues with your selected hardware. Maybe on linuxtv or<br>
search the internet for problems reported by others.</blockquote><div><br></div><div>Would my experience with powering off during nights when I know I'll be up before the next recording indicate that my hardware is OK with S5? </div>
</div></div></div></blockquote><div><br></div><div><div>Yes. Regarding your S1/S2/S3/Auto: I suspect you're looking at the BIOS option for what to do when the system is suspended, ie. you briefly press the power switch. This is irrelevant. When these scripts shut Myth down it will turn itself off in the same way as you do manually (S5). The important point is that you set the BIOS to power up automatically at your alarm time via the RTC Alarm/Wakeup/whatever option.</div><div><br></div><div>The terminal S4 comment is also irrelevant. I'm guessing it's an informational message to distinguish your system from very old systems that didn't support S4. Also note that the link you're following (on a cursory reading) appears very similar to <a href="http://www.mythtv.org/wiki/ACPI_Wakeup#BIOS_setup">http://www.mythtv.org/wiki/ACPI_Wakeup</a>, which has been around for years.</div><div><br></div></div><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* MythTV likes whatever state you decide on. hint: full shutdown is<br>
known to work well :-)<br>
<br>
Don't know how to do this either<br>
</blockquote>
<br></div>
follow bug reports and user discussion wrt hibernate etc. but plain old<br>
turn off and on is known to work. I have no idea how the backend likes<br>
it if the system time suddenly jumps ahead some hours/days.<br>
<br>
<br>
I'd just try if the system comes back up when you set an alarm in<br>
5 minutes and shut down. If that doesn't work disable the update of the<br>
hwclock on shutdown, see the howto you referred to. And only if that<br>
does not work start looking into the other options.<div class="HOEnZb"><div class="h5"><br>
<br>
Regards,<br>
Karl<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-user</a></div></div></blockquote><div><br></div><div>I'm thinking I'll toggle to auto, rather than S1,2,or3; should give me the best shot for the first test anyway.</div>
<div><br></div><div>Thanks, Daryl </div></div><br></div></div>
</blockquote><div><br></div><div>Also, be aware that auto-wake will only work if Myth shut down the system. If you use your Windows OS (or a Linux desktop) then they will clear any RTC alarm when they shut down. You will have to re-boot into Myth afterwards and then shut it down to re-set the alarm and auto-wake for the next recording. It's easy to forget this and miss recordings...</div><br></body></html>