<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 31, 2015 at 9:39 AM, Kirk Bocek <span dir="ltr"><<a href="mailto:t004@kbocek.com" target="_blank">t004@kbocek.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On 8/30/2015 11:31 PM, Alec Leamas wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">
On 31/08/15 02:36, Kirk Bocek wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
So we do have something here. I see note about installing the output of<br>
-r elsewhere so it can be used.<br>
</blockquote>
<br></span>
This basically means that you should be able to use the devinput driver and configuration file using this device as input (or, perhaps better, the corresponding link under /dev/input/by_id). This is with the devinput limitations, notably the lack of sending (blasting) support.<br>
<br>
Also, depending on what buttons you actually are pressing, the key mappings looks strange... If a plain 'left' button is decoded as LEFTSHIFT, LEFTALT and/or LEFTMETA ther moight be a problem. It should then be resolved at the kernel side (ir-keytable has many options, none of which I'm used to).<br>
<br>
</blockquote>
<br>
So, circling back, why can't I get any output out of this receiver (that I was *promised* would work)?<br>
<br>
/etc/lirc/lircd.conf:<br>
<br>
include "/etc/lirc/lircd.conf.devinput"<span class=""><br>
<br>
/etc/lirc/lirc_options.conf:<br>
<br>
driver = devinput<br>
device = /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir<br>
<br></span>
by-path and by-name are the same thing, they are both symlinks to /dev/input/eventX. Running IRW with a generic MCE remote working with another setup gives no output. But systemctl shows IRW connecting:<br>
<br>
$systemctl status lircd<span class=""><br>
â lircd.service - LIRC Infrared Signal Decoder<br>
Loaded: loaded (/usr/lib/systemd/system/lircd.service; enabled)<br></span>
Active: active (running) since Mon 2015-08-31 07:23:43 PDT; 5min ago<br>
Main PID: 2851 (lircd)<br>
CGroup: /system.slice/lircd.service<br>
ââ2851 /usr/sbin/lircd --nodaemon<br>
<br>
Aug 31 07:23:43 liva2 lircd[2851]: lircd-0.9.1a[2851]: lircd(devinput) ready, using /var/run/...ircd<br>
Aug 31 07:23:43 liva2 lircd-0.9.1a[2851]: lircd(devinput) ready, using /var/run/lirc/lircd<br>
Aug 31 07:23:56 liva2 lircd-0.9.1a[2851]: accepted new client on /var/run/lirc/lircd<br>
Aug 31 07:23:56 liva2 lircd-0.9.1a[2851]: initializing '/dev/input/by-path/pci-0000:00:14.0-us...ir'<br>
Aug 31 07:23:56 liva2 lircd[2851]: lircd-0.9.1a[2851]: accepted new client on /var/run/lirc/lircd<br>
Aug 31 07:23:56 liva2 lircd[2851]: lircd-0.9.1a[2851]: initializing '/dev/input/by-path/pci-0...-ir'<br>
Aug 31 07:24:07 liva2 lircd-0.9.1a[2851]: removed client<br>
Aug 31 07:24:07 liva2 lircd-0.9.1a[2851]: closing '/dev/input/by-path/pci-0000:00:14.0-usb-0:1...ir'<br>
<br>
ir-keytable --device /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir -t<br>
<br>
Yields nothing with this generic MCE remote.<br>
<br>
Now at the end of<br>
<br>
ir-keytable --device /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir -r<br>
<br>
I see:<br>
<br>
...<br>
scancode 0xff0000fe = KEY_RESERVED (0x00)<br>
scancode 0xff0000ff = KEY_RESERVED (0x00)<br>
Enabled protocols:<br>
<br>
So, knowing the MCE remote is RC-6 let's try adding that protocol to the testing:<br>
<br>
$ir-keytable --device /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir -t --protocol rc-6<br>
Invalid protocols selected<br>
Couldn't change the IR protocols<span class=""><br>
Testing events. Please, press CTRL-C to abort.<br>
<br></span>
So I'm stumped here. Can this receiver work with a generic remote? Does it only work with the funky little remote it came with needing two CR2032 batteries (which will render it useless for me.)<div class=""><div class="h5"><br>
<br></div></div></blockquote><div><br>I'm the one that has used a lot of these and do today but
never with fedora, I like rhel but never a fan of fedora.<br>
<br>
All of my frontends running with openelec and the remotes works out of
the box and the receiver works with any of the learning remotes that I
have. Not sure what is going on with fedora maybe try mythbuntu and see
if it does the same thing, heck load openelec on a usb maybe the
receiver is bad, never had it happen but I guess its possible.<br>
<br>
Its the same remote that came with my zotac box where I came across them and I use learning remotes with all of the recievers, why I liked it since I did not have to use the remote that came with it. I have seen plugging it into a usb3 port to cause some issues.<br></div></div></div></div>