From: Richi Plana <richip@ri...> - 2012-05-30 07:08:39
I'm at my wit's end trying to setup my MythTV (0.25) system on CentOS
6.2. I'm using lirc-0.9 from the ATRMS repository but can't get it to
work. I also have a WinTV PVR-350 card with the grey remote control that
came with it.
1) Copied /usr/share/doc/lirc-0.9/remotes/devinput/lircd.conf.devinput
2) Created a /etc/rc_keymaps/haupp350 file based on the
/etc/rc_keymaps/haupp file but with "0x1e" --> "0x00". I also made sure
to modify /etc/rc_maps.cfg and added a "* * haupp350" line there
3) Started lircd:
# modprobe ir-kbd-i2c debug=1
# lircd -n --device=/dev/input/event5 --driver=devinput
4) Started irw and tried pressing buttons. No output
Looking at dmesg, I see output for each RC event and the keycodes match
the ones in the /etc/rc_keymaps/haupp350 file. 'lsof /dev/input/event5'
shows me that lircd has the dev file open. Stopping lircd and just
cat'ting /dev/input/event5 shows output whenever I press buttons on the
remote control. The only thing that isn't happening is lircd sending out
data on /var/run/lirc/lircd that gets picked up by irw. Looking at
/var/log/messages, I see log output from lircd whenever I start irw and
when I initially press a button on the RC.
I'm not seeing much in the documentation that would describe how lircd
uses /etc/lirc/lircd.conf nor what it does with the files in
/etc/rc_maps.cfg and /etc/rc_keympas/*. I just don't know how the raw
data from /dev/input/event? gets translated to the codes that are output
Any help would be appreciated. I still need to get MythTV working as a
lirc client after irw is successful at returning any data.
Btw, I tried mode2 but it complained about an incompatible driver. As
for evtest, I don't know where I can get a package for CentOS 6 from.