<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 2, 2013 at 7:41 PM, Roger Siddons <span dir="ltr"><<a href="mailto:dizygotheca@ntlworld.com" target="_blank">dizygotheca@ntlworld.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div><div class="im">On Mon, 02 Sep 2013 00:23:19 +0100, Daryl McDonald <<a href="mailto:darylangela@gmail.com" target="_blank">darylangela@gmail.com</a>> wrote:<br><br><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"><div>Well I mirrored your settings and scripts and scheduled a recording for 7p.m. gave the system two minutes to shutdown the backend and set the alarm then powered off, and waited until 7:05p.m. and it did not come on. Does the last line of the following output indicate UTC time?:</div>
<div> daryl@daryl-A780L3C:~$ sudo grep -i rtc /var/log/dmesg</div><div>[sudo] password for daryl: </div><div>[ 0.199663] RTC time: 19:04:25, date: 09/01/13</div><div>[ 1.222545] rtc_cmos 00:03: RTC can wake from S4</div>
<div>[ 1.222673] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0</div><div>[ 1.222692] rtc0: alarms up to one month, y3k, 114 bytes nvram</div><div>[ 1.229942] rtc_cmos 00:03: setting system clock to 2013-09-01 19:04:26 UTC (1378062266)</div>
</div></div></div></blockquote><div><br></div></div><div>Yes. On startup the system reads the RTC clock to get the current time/date. I suspect it's interpreting the time as UTC (rather than localtime) because your file "/etc/default/rcS" contains "UTC=yes". You should change that. Type "man /etc/default/rcS" to read more about it.</div>
<div class="im"><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"><div><br></div><div>This is what my disable hwclock script looks like:</div>
<div><div>daryl@daryl-A780L3C:~$ cat /etc/init/hwclock-save.conf</div><div># hwclock-save - save system clock to hardware clock</div><div># hwclock-save - save system clock to hardware clock</div>
<div>#</div><div># This task saves the time from the system clock back to the hardware</div><div># clock on shutdown.</div><div><br></div><div>description<span style="white-space:pre-wrap"> </span>"save system clock to hardware clock"</div>
<div><br></div><div>start on runlevel [06]</div><div><br></div><div>task</div><div><br></div><div>script</div><div> . /etc/default/rcS</div><div> [ "$UTC" = "yes" ] && tz="--utc" || tz="--localtime"</div>
<div> [ "$BADYEAR" = "yes" ] && badyear="--badyear"</div><div> ACPITIME=`cat /proc/acpi/alarm`</div><div> exec hwclock --rtc=/dev/rtc0 --systohc $tz --noadjfile $badyear</div>
<div> echo "$ACPITIME" > /proc/acpi/alarm</div><div>end script</div><div>daryl@daryl-A780L3C:~$ </div></div><div><br></div></div></div></div></blockquote><div><br></div></div><div>That doesn't look right to me. Up until last year the solution was to simply not write the clock. In January someone changed the wiki to re-write the alarm after setting the clock but /proc/acpi/alarm is only applicable to (old) 2.6 kernels, so it won't have any effect on recent kernels (like yours); i.e. hwclock updates aren't being disabled.<br>
</div><div>However, following Stefan comments, I can confirm that Mythbuntu 12.04 doesn't need its hwclock disabled so, for you, changing this file is an unnecessary distraction and I suggest you put it back to default (delete the 2 lines containing ACPITIME) & forget this step.</div>
<div><br></div></div><br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">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-users</a></blockquote><div><br></div><div>Thanks, I arrived at the same conclusion and restored the default script already, and have a successful first test :-) More tests tomorrow.</div>
<div><br></div><div>Daryl</div></div><br></div></div>