[mythtv-users] Anyone Using LIRC on CentOS 6.6?
Hika van den Hoven
hikavdh at gmail.com
Wed Jun 3 22:36:44 UTC 2015
Hoi Kirk,
Wednesday, June 3, 2015, 11:10:18 PM, you wrote:
> On 6/3/2015 10:22 AM, Alec Leamas wrote:
>
>
> On 03/06/15 18:36, Kirk Bocek wrote:
>
>
> Ah, discovered the CentOS Software Collections Repository:
>
> http://wiki.centos.org/AdditionalResources/Repositories/SCL
>
> Which includes Python 3.3
>
> Which is required according to LIRC:
>
> http://www.lirc.org/html/install.html
>
> *Maybe* doable.
>
>
> Probably :) But the main problem is if you really need lirc.
> The link in my last message tries to sort out how the kernel works together w lirc.
>
> It might be that the error message comes from a (failed)
> attempt from the kernel to decode the data. You should be able
> to get rid of this by disabling the kernel decoding (same
> link...) and use lirc instead (which then reads the raw data from the kernel driver).
>
> All this is arguably a mess :(
>
> First debugging step (if you decide to use lirc's decoding)
> is to use mode2 to check the data from the driver. This makes
> no sense as long as the kernel still tries to decode the data,
> which is the default setup.
>
>
>
> I tried the two kernel settings on the LIRC setup page:
>
> # echo -- 'lirc' > /sys/class/rc/rc0/protocols
>
> Yields a write error and creating
>
> /etc/udev/rules.d/99-remote-control-lirc
>
> Doesn't help.
>
> My driver and lirc *are* loading:
>
> IR NEC protocol handler initialized
> IR RC5(x) protocol handler initialized
> IR RC6 protocol handler initialized
> Registered IR keymap rc-rc6-mce
> input: Media Center Ed. eHome Infrared Remote Transceiver
> (0471:0815) as
> /devices/pci0000:00/0000:00:1d.3/usb5/5-1/5-1:1.0/rc/rc0/input14
> rc0: Media Center Ed. eHome Infrared Remote Transceiver
> (0471:0815) as
> /devices/pci0000:00/0000:00:1d.3/usb5/5-1/5-1:1.0/rc/rc0
> mceusb 5-1:1.0: Registered Philips eHome Infrared Transceiver on usb5:2
> usbcore: registered new interface driver mceusb
> IR JVC protocol handler initialized
> IR Sony protocol handler initialized
> lirc_dev: IR Remote Control driver registered, major 247
> rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
> IR LIRC bridge handler initialized
> alloc irq_desc for 32 on node -1
> alloc kstat_irqs on node -1
>
> But then when I run irw I see in /var/log/messages a bunch of:
> Jun 3 07:02:48 marble lircd-0.9.0[1501]: failed on bit 13
> Jun 3 07:02:48 marble lircd-0.9.0[1501]: failed on bit 9
>
> So *something* is getting through.
>
>
>
>
What is dmesg/your log saying about the initialization?
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
More information about the mythtv-users
mailing list