[mythtv-users] Anyone Using LIRC on CentOS 6.6?

Kirk Bocek t004 at kbocek.com
Thu Jun 4 16:25:33 UTC 2015



On 6/4/2015 9:17 AM, Hika van den Hoven wrote:
> Hoi Kirk,
>
> Thursday, June 4, 2015, 6:02:37 PM, you wrote:
>
>
>
>> On 6/4/2015 8:05 AM, Hika van den Hoven wrote:
>>> Try: SUBSYSTEM=="input", \ KERNEL=="event*", \
>>> ATTRS{idVendor}=="0471", \ ATTRS{idProduct}=="0815", \
>>> SYMLINK+="input/ir-mceusb"
>>> or: SUBSYSTEM=="input", \ KERNEL=="event*", \ DRIVERS=="mceusb", \
>>> SYMLINK+="input/ir-mceusb"
>> Nope, neither worked.
>> $vi /etc/udev/rules.d/99-remote-control-lirc
>> $udevadm control --reload-rules
>> $modprobe -rv mceusb
>> $modprobe -v mceusb
>> $ls /dev/input/
>> by-id    event0  event10  event12  event14  event3  event5  event7
>> event9  mouse0
>> by-path  event1  event11  event13  event2   event4  event6  event8 mice
>> _______________________________________________
> The backslashes are to escape the linebreaks. Spaces more then one
> behind each other are ignored.
> So either put it on one line without backslashes or order it neatly
> with an backslash at the end of every in between linebreak (except of
> cause the last one)
>
>
>

Yes, I get that. My rules file looks like:

#Create stable name for IR Receiver
#SUBSYSTEM=="input", KERNEL=="event*", DRIVERS=="mceusb", 
SYMLINK+="input/ir-mceusb"
SUBSYSTEM=="input", KERNEL=="event*", ATTRS{idVendor}=="0471", 
ATTRS{idProduct}=="0815", SYMLINK+="input/ir-mceusb"

Ah hah! Figured it out. I had named my file 99-remote-control-lirc. 
Renamed it to 99-remote-control-lirc.rules and it now works. Error was 
between keyboard and chair.

$ls /dev/input
by-id    event0  event10  event12  event14  event3  event5  event7 
event9     mice
by-path  event1  event11  event13  event2   event4  event6  event8 
ir-mceusb  mouse0




More information about the mythtv-users mailing list