[mythtv-users] Long delays with remote occasionally

[Andrew Allison]

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

Well, your not alone, my myth system does the same thing. Myth stops /
buffers the remote control commands. I've run irw and the remote is
working. It seems to stop responding until a commercial skip occurs the
all the buffered key press get processed.

I don't see any pattern when myth decides to buffer the remote key
presses, If I remember it started right after I upgraded to Fedora 9 and
just figured I messed up the install by trying to minimize the amount of
software I installed.

Hauppauge
2 PVR-150
1 PVR-500
Fedora 9
x86_64
myth 0.21-192.fc9
kernel 2.6.25.10-86.fc9.x86_64
lirc.x86_64  0.8.4-80_cvs20080528.f
lirc-devel.x86_64  0.8.4-80_cvs20080528.f
lirc-devices.noarch  0.8-4.fc9
lirc-kmdl-2.6.25.10-86.fc9.x86_64.x86_64 0.8.4-80_cvs20080528.f