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

[Hika van den Hoven]

Hoi Kirk,

Thursday, June 4, 2015, 4:17:08 AM, you wrote:



> On 6/3/2015 6:55 PM, Hika van den Hoven wrote:
>>
>> My error. Should be: udevadm info --attribute-walk path --name=/dev/lirc0
>>
>>
>>

> I'm putting this in a separate message for clarity. As a test, I 
> downloaded, compiled and installed LIRC .0.9.2a. A bit harder to figure
> out without init scripts but I got it done. Same errors when running irw
> and firing some  commands at the receiver:

> Jun  3 19:01:37 marble lircd-0.9.2a[26577]: Error: failed on bit 1
> Jun  3 19:01:37 marble lircd-0.9.2a[26577]: Error: failed on bit 21
> Jun  3 19:01:37 marble lircd-0.9.2a[26577]: Error: failed on bit 17
> Jun  3 19:01:37 marble lircd-0.9.2a[26577]: Error: failed on bit 13

> Now the lircd.conf I am using is from 0.8.7. I've tried a couple of 
> different remotes just to get output. But has the format changed with 
> the 9 series? Should I download and install a newer configuration file?
> Is an old config file the problem?
> _______________________________________________

I'm a little bit at a loss. The two devices point to the same hardware
and it seems to the same driver. Maybe something new, that they now
offer both the old lirc interface and the kernel input layer
interface?

Anyhow the commands for loading lircd are different. With /dev/lirc0
you have something like: -d /dev/lirc0. With the new interface it is:
-H devinput -d /dev/input/event14. The trouble is that the number can
easily change. They say -H devinput -d name="DVB" should work or if
you have by-path sim-links in /dev/input, you could use them. I use
udev to get a stable named sim-link.

Also lircd needs to be compiled with the right device support and
against the right kernel. Most versions you install with a
distribution are compiled with all support.

If you use in-kernel support lircd.conf doesn't do much anymore. It's
all supplied by the kernel. Standard support will work without lircd
loaded. Only if you want to differentiate from the default or if your
device is not supported (like with blasters or my homebrew serial
device I have on one machine) you need lircd. In the new input layer
it's like with keyboards and mice, it just should works. 


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