<div dir="ltr">On Tue, Sep 2, 2008 at 11:06 AM, James Crow <span dir="ltr"><<a href="mailto:james@ultratans.com">james@ultratans.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Sat, 2008-08-30 at 13:31 -0700, Allen Edwards wrote:<br>
><br>
><br>
</div><div><div></div><div class="Wj3C7c">> On Sat, Aug 30, 2008 at 12:23 PM, Michael T. Dean<br>
> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<br>
><br>
> On 08/30/2008 03:00 PM, Allen Edwards wrote:<br>
> > I have seen this many times and today my wife had an<br>
> example. She<br>
> > said the remote wasn't working any more. I came in from the<br>
> garage<br>
> > and it wasn't working. I put it down on the table. Then<br>
> myth suddenly<br>
> > responded to at least some, if not all, of my key presses.<br>
> I tell the<br>
> > story to give an idea of the time frames involved. She was<br>
> 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<br>
> either.<br>
> ><br>
> > I have a HDHR with the IR Rx on it and a very powerful (high<br>
> ir<br>
> > output) programmable remote. I am running LIRC on a<br>
> mythbuntu 8.04<br>
> > updated system. When it works, it works instantly with no<br>
> noticeable<br>
> > delay.<br>
> ><br>
> > Any logs I can look in? Anyone know what causes this? A<br>
> cure?<br>
><br>
><br>
> Got a working real-time clock? New kernels should be compiled<br>
> without<br>
> the rtc module and, instead, should use the rtc-core and an<br>
> appropriate<br>
> hardware-specific support (i.e. for PC's using rtc-cmos). So,<br>
> if you<br>
> had previously configured your system to load rtc and it<br>
> doesn't exist,<br>
> now, and you haven't updated the configuration, it could cause<br>
> problems<br>
> like this.<br>
><br>
> Run "hwclock --debug" and see if you get errors. If so, try<br>
> "modprobe<br>
> rtc-cmos" and see if all ("hwclock --debug" and LIRC) works<br>
> better.<br>
><br>
> Mike<br>
><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>
<br>
><br>
<br>
</div></div>To add one more data point, my Mythbuntu 8.04 system does (did?) this as<br>
well. Since school has started I have not had time to watch any TV so<br>
have not used the Myth box. I use a MS MCE remote with its included IR<br>
receiver. When it works (almost all the time) it works perfectly. Fast<br>
response and I never seem to have any interference.<br>
<br>
I did install all current updates on my Mythbuntu system this weekend. I<br>
do not yet know if that has fixed the problem.<br>
<br>
Thanks,<br>
<font color="#888888">James<br>
</font><div><br></div></blockquote></div><br>Same problem here. I start playing a recording, the remote works for
30 seconds or so, then there's a long delay where the commands get
buffered, maybe 2-4 minutes. Unfortunately, it's a sometimes issue and
I have not found a pattern as to when it happens, except that it's more
likely to happen with my wife is around :-/.<br>
<br>
I have a really slow machine (P4 1.3 GHz, 630MB), so I have a hunch
that after a recording starts playing, Myth might be doing something
that's blocking the remote. Is there a log I can check or anything to
troubleshoot the problem? I also use HDHR, and have verified with irw
that the remote keypresses are getting to my Mythbox nearly
instantaneously. It's a combination FE/BE.<br>
<br>
MythTV Version : 16838<br>
MythTV Branch : branches/release-0-21-fixes<br>
Library API : 0.21.20080304-1<br>
Network Protocol : 40<br>
Options compiled in:<br>
linux profile using_oss using_alsa using_arts using_jack using_backend
using_dbox2 using_dvb using_firewire using_frontend using_hdhomerun
using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc
using_opengl_vsync using_opengl_video using_v4l using_x11 using_xrandr
using_xv using_xvmc using_xvmcw using_xvmc_vld using_glx_proc_addr_arb
using_bindings_perl using_bindings_python using_opengl
using_ffmpeg_threads using_libavc_5_3 using_live<br>
</div>