<div dir="ltr">When I had the driver set to devinput, the remote didn't work at all. Now that I set it to "default", I get the key bounces. I hadn't thought to go back and look at ir-keytable after making this change; prior to that, I saw nothing with ir-keytable or irw. Now, with irw (which I did check), I can see the bounces, so at least I know it's not anything in Myth that's doing it.<div><br></div><div>If I run ir-keytable, it does not see the keypresses. I can see the light flashing on the USB receiver, but ir-keytable doesn't report anything:<br><br><div>[root@mongoliad mythtv]# ir-keytable</div><div>Found /sys/class/rc/rc0/ (/dev/input/event4) with:</div><div> Driver streamzap, table rc-streamzap</div><div> Supported protocols: unknown other lirc rc-5 jvc sony nec sanyo mce-kbd rc-6 sharp xmp </div><div> Enabled protocols: lirc </div><div> Name: Streamzap PC Remote Infrared Rec</div><div> bus: 3, vendor/product: 0e9c:0000, version: 0x0100</div><div> Repeat delay = 500 ms, repeat period = 125 ms</div><div>[root@mongoliad mythtv]# ir-keytable -t -d /dev/input/event4</div><div>Testing events. Please, press CTRL-C to abort.</div><div>^C</div><div>[root@mongoliad mythtv]# </div><div><br></div><div>I confess that I do not understand how the various components of this relate to each other. For me at least, life was simpler before the kernel acquired the ability to handle remote controls directly.</div><div><br></div><div>--Greg</div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jul 17, 2016 at 3:06 AM, Alec Leamas <span dir="ltr"><<a href="mailto:leamas.alec@gmail.com" target="_blank">leamas.alec@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<p><br>
</p>
<br>
<div>On 17/07/16 00:58, Greg Woods wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jul 5, 2016 at 7:07 PM, Jerry
<span dir="ltr"><<a href="mailto:mythtv@hambone.e4ward.com" target="_blank">mythtv@hambone.e4ward.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">Changing the driver from
devinput to default in lirc_options.conf fixed the
issue.<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">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.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">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:</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"># cat /sys/class/rc/rc0/protocols</div>
<div class="gmail_extra">other unknown rc-5 nec rc-6 jvc sony
rc-5-sz sanyo sharp mce_kbd xmp [lirc]</div>
<div class="gmail_extra"><br>
</div>
<br>
</div>
</blockquote></span>
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.<br>
<br>
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.<br>
<br>
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. <br>
<br>
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.<br>
<br>
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...<br>
<br>
<br>
Cheers!<span class="HOEnZb"><font color="#888888"><br>
<br>
--alec<br>
</font></span></div>
<br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a><br>
<br></blockquote></div><br></div>