[mythtv-users] Problem with LIRC after upgrade to Fedora 24

Alec Leamas leamas.alec at gmail.com
Sun Jul 17 09:06:39 UTC 2016



On 17/07/16 00:58, Greg Woods wrote:
>
>
> On Tue, Jul 5, 2016 at 7:07 PM, Jerry <mythtv at hambone.e4ward.com 
> <mailto:mythtv at hambone.e4ward.com>> wrote:
>
>     Changing the driver from devinput to default in lirc_options.conf
>     fixed the issue.
>
>
> I am also having trouble getting my remote to work well after 
> upgrading from F23 to F24. It's the same damned problem I had five 
> years ago that started a long thread on this list with F14, but it's 
> not the same fix. That one turned out to be an actual kernel driver 
> bug that got fixed. This time, most likely not.
>
> I've got a Streamzap remote. I applied Jerry's fix above which got it 
> to work, but now I'm getting key bouncing (one press results in two 
> actions). I am already turning off other protocols besides lirc:
>
> # cat /sys/class/rc/rc0/protocols
> other unknown rc-5 nec rc-6 jvc sony rc-5-sz sanyo sharp mce_kbd xmp 
> [lirc]
>
>
This doesn't really make sense. The "fix" is really about using the 
devinput driver instead of the default driver (BTW, the *default* driver 
has an unfortunate name, it's a specific driver with this name).  The 
fix also is about how the decoding from raw IR timings to keypress 
events is done.

Earlier, before the "fix" Jerry used the default driver. This means 
using a /dev/lirc? device and occasionally also configuring this to use 
the lirc protocol. Doing so also means that the kernel decoding is 
disabled and lircd decodes the raw timing info.

After the "fix" Jerry is using the devinput driver. This means that the 
kernel is doing the decoding, lirc is just used to distribute the 
keypress events to applications (adding some functionality).  In this 
case the protocol should *not* be set to lirc, it should be left 
untouched so the kernel can setup the internal decoding.

It also means that the debug tool to be used is ir-keytable. This 
reports the decoded keypress events which lircd consumes using the 
devinput driver. The key question is if the events as seen by 
ir-keytable is doubled. If so, it's a kernel issue.

If the kernel has problems, one possible route is to use the default 
driver as before. Editing lirc_options.conf to use driver=default, 
device=/dev/lirc0 and dropping the streamzap config file in 
/etc/lirc/lircd.conf.d should work.   Mixing up these approaches means 
troubles ahead...


Cheers!

--alec
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160717/70378b2f/attachment.html>


More information about the mythtv-users mailing list