<div dir="ltr"><br><br><div class="gmail_quote">On Sat, Aug 30, 2008 at 12:23 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On 08/30/2008 03:00 PM, Allen Edwards wrote:<br>
> I have seen this many times and today my wife had an example. She<br>
> said the remote wasn't working any more. I came in from the garage<br>
> and it wasn't working. I put it down on the table. Then myth suddenly<br>
> responded to at least some, if not all, of my key presses. I tell the<br>
> story to give an idea of the time frames involved. She was just<br>
> watching a recorded show and wanted to pause it.<br>
><br>
> This happens now and then, not every day, but it is not rate either.<br>
><br>
> I have a HDHR with the IR Rx on it and a very powerful (high ir<br>
> output) programmable remote. I am running LIRC on a mythbuntu 8.04<br>
> updated system. When it works, it works instantly with no noticeable<br>
> delay.<br>
><br>
> Any logs I can look in? Anyone know what causes this? A cure?<br>
<br>
</div></div>Got a working real-time clock? New kernels should be compiled without<br>
the rtc module and, instead, should use the rtc-core and an appropriate<br>
hardware-specific support (i.e. for PC's using rtc-cmos). So, if you<br>
had previously configured your system to load rtc and it doesn't exist,<br>
now, and you haven't updated the configuration, it could cause problems<br>
like this.<br>
<br>
Run "hwclock --debug" and see if you get errors. If so, try "modprobe<br>
rtc-cmos" and see if all ("hwclock --debug" and LIRC) works better.<br>
<br>
Mike</blockquote></div><br><br>dad@myth_desktop:~$ hwclock --debug<br>hwclock from util-linux-ng 2.13.1<br>Using /dev interface to clock.<br>Last drift adjustment done at 1220111053 seconds after 1969<br>Last calibration done at 1220111053 seconds after 1969<br>
Hardware clock is on UTC time<br>Assuming hardware clock is kept in UTC time.<br>Waiting for clock tick...<br>...got clock tick<br>Time read from Hardware Clock: 2008/08/30 20:30:20<br>Hw clock time : 2008/08/30 20:30:20 = 1220128220 seconds since 1969<br>
Sat 30 Aug 2008 01:30:20 PM PDT -0.045784 seconds<br><br><br>Looks OK to me. Anything else I should try?<br><br>Allen<br><br><br><br><br></div>