[mythtv-users] Trying To Get Two IR Receivers Working

[Hika van den Hoven]

Hoi Kirk,

Thursday, October 15, 2015, 2:39:30 AM, you wrote:



> On 10/14/2015 9:55 AM, Kirk Bocek wrote:
>>
>>
>> On 10/14/2015 9:32 AM, Alec Leamas wrote:
>>> The devinput LIRC driver does exactly this - acts as a bridge between
>>> the kernel decoding and the LIRC application interface. You feed the
>>> event device as the --device option to devinput, starts lircd and then
>>> uses irw. This is what's described in [2]
>>
>> Ah, I did not change the "device=" setting in lirc_options.conf. I 
>> think I thought it was saying what the device line the driver 
>> *created* at startup. My bad.
>>
>>>
>>> You can use udev rules to handle that the event device is not fixed as
>>> Karl described. However, it's not really necessary, see [1]
>>>
>>>
>>
>> That's right. You told me about that before. I got sidetracked onto 
>> other things. This device has a nice unique name so that:
>>
>> device = name='*Spinel*'

> I installed driver=devinput and installed the devinput conf file. I then
> tried several variations of the device= line. With and without double 
> quotes, with NAME= and name=. Although the doc page shows no double 
> quotes and lower case, I am firing this off from a config file.

> lircd is starting:
> Oct 14 17:38:19 liva2.pvt systemd[1]: Started LIRC Infrared Signal Decoder.
> Oct 14 17:38:19 liva2.pvt systemd[1]: Starting LIRC Infrared Signal 
> Decoder...
> Oct 14 17:38:19 liva2.pvt lircd-0.9.2a[11203]: Illegal effective uid: 
> lirc: Success
> Oct 14 17:38:19 liva2.pvt lircd-0.9.2a[11203]: Info: Using remote: devinput.
> Oct 14 17:38:19 liva2.pvt lircd-0.9.2a[11203]: Info: Using remote: devinput.
> Oct 14 17:38:19 liva2.pvt lircd-0.9.2a[11203]: Notice: lircd(devinput)
> ready, using /var/run/lirc/lircd
> Oct 14 17:38:19 liva2.pvt lircd[11203]: lircd-0.9.2a[11203]: Illegal 
> effective uid: lirc: Success
> Oct 14 17:38:19 liva2.pvt lircd[11203]: lircd-0.9.2a[11203]: Info: Using
> remote: devinput.
> Oct 14 17:38:19 liva2.pvt lircd[11203]: lircd-0.9.2a[11203]: Info: Using
> remote: devinput.
> Oct 14 17:38:19 liva2.pvt lircd[11203]: lircd-0.9.2a[11203]: Notice: 
> lircd(devinput) ready, using /var/run/lirc/lircd

> Still *nothing* from irw and ir-keytable still whines:

> $ir-keytable -t
> Couldn't find any node at /sys/class/rc/rc*.

> Tried a couple of manual -d versions:

> ir-keytable -t -d 
> /dev/input/by-id/usb-PHILIPS_MCE_USB_IR_Receiver-_Spinel_plus-event-ir

> ir-keytable -t -d 
> /dev/input/by-path/pci-0000\:00\:14.0-usb-0\:2\:1.0-event-ir

> Still nothing.
> _______________________________________________

Already earlier earlier in your struggle I was thinking about rights.
Earlier in similar discussions it was mentioned that in the newer
distributions lircd is run as a user and not as root any longer. But
then I saw that your /var/run/lirc/lircd was owned by root and rw for
all so I dismissed it. But now I notice in your log
> Oct 14 17:38:19 liva2.pvt lircd-0.9.2a[11203]: Illegal effective uid:
> lirc: Success
So I think it's worth looking into the user used for running lircd and
the rights on the devinput node. It might be at the root of the problem.
If I remember correctly it then was solved by changing the rights on
the node through an udev rule.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens