<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 6/3/2015 10:22 AM, Alec Leamas
wrote:<br>
</div>
<blockquote cite="mid:556F37DA.6000800@gmail.com" type="cite">On
03/06/15 18:36, Kirk Bocek wrote:
<br>
<br>
<blockquote type="cite">Ah, discovered the CentOS Software
Collections Repository:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.centos.org/AdditionalResources/Repositories/SCL">http://wiki.centos.org/AdditionalResources/Repositories/SCL</a>
<br>
<br>
Which includes Python 3.3
<br>
<br>
Which is required according to LIRC:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.lirc.org/html/install.html">http://www.lirc.org/html/install.html</a>
<br>
<br>
*Maybe* doable.
<br>
</blockquote>
<br>
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.
<br>
<br>
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).
<br>
<br>
All this is arguably a mess :(
<br>
<br>
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.
<br>
<br>
</blockquote>
<br>
I tried the two kernel settings on the LIRC setup page:<br>
<br>
# echo -- 'lirc' > /sys/class/rc/rc0/protocols<br>
<br>
Yields a write error and creating <br>
<br>
<span style="color: rgb(0, 0, 0); font-family: Verdana, Arial,
Lucida, Helvetica; font-size: medium; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align: justify;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
display: inline !important; float: none; background-color:
rgb(255, 255, 255);">/etc/udev/rules.d/99-remote-control-lirc<br>
<br>
Doesn't help.<br>
<br>
My driver and lirc *are* loading:<br>
<br>
IR NEC protocol handler initialized<br>
IR RC5(x) protocol handler initialized<br>
IR RC6 protocol handler initialized<br>
Registered IR keymap rc-rc6-mce<br>
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<br>
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<br>
mceusb 5-1:1.0: Registered Philips eHome Infrared Transceiver on
usb5:2<br>
usbcore: registered new interface driver mceusb<br>
IR JVC protocol handler initialized<br>
IR Sony protocol handler initialized<br>
lirc_dev: IR Remote Control driver registered, major 247<br>
rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at
minor = 0<br>
IR LIRC bridge handler initialized<br>
alloc irq_desc for 32 on node -1<br>
alloc kstat_irqs on node -1<br>
<br>
But then when I run irw I see in /var/log/messages a bunch of:<br>
Jun 3 07:02:48 marble lircd-0.9.0[1501]: failed on bit 13<br>
Jun 3 07:02:48 marble lircd-0.9.0[1501]: failed on bit 9<br>
<br>
So *something* is getting through.<br>
<br>
<br>
<br>
</span>
</body>
</html>