[mythtv-users] Issues with ir-kbd-i2c PVR250 on Fedora15

Gabe Rubin gaberubin at gmail.com
Tue Aug 23 23:47:14 UTC 2011

On Tue, Aug 23, 2011 at 4:41 PM, Billy Macdonald
<toastyfries at hotmail.com> wrote:
> Hi List,
>    Sorry if this has been posted multiple times;  It kept getting flagged for size.
>    I recently did a clean install of Fedora 15 (previously 13) and I am running into issues with the new ir-kbd-i2c that I'm supposed to use for lirc.  I feel like I'm really close, just missing a step.  Can someone review my current status and let me know where I've gone wrong. I've uploaded my /etc/sysconfig/lirc to http://pastebin.com/UnjnLpTY and /etc/lirc/lircd.conf to http://pastebin.com/Wz2UTkVe.  Also, I'm not using the grey remote that came with the card, but a remote code on my Verizon remote that's RC5 and worked with F13.  I'm not sure if that's the problem but dmesg sees the key presses so I think it's okay.
> After I "modprobe ir_kbd_i2c debug=1" the output below is in dmesg after I press some buttons. So that piece appears to be working.   However, when I start LIRC and run irw, there is no output.
> Thanks in advance!Billy
> [ 1422.806589] IR NEC protocol handler initialized[ 1422.824364] IR RC5(x) protocol handler initialized[ 1422.827347] IR RC6 protocol handler initialized[ 1422.835361] IR JVC protocol handler initialized[ 1422.838393] IR Sony protocol handler initialized[ 1422.839214] Registered IR keymap rc-hauppauge[ 1422.839489] input: i2c IR (Hauppauge) as /devices/virtual/rc/rc0/input8[ 1422.839630] rc0: i2c IR (Hauppauge) as /devices/virtual/rc/rc0[ 1422.839639] ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-1/1-0018/ir0 [ivtv i2c driver #0][ 1422.840931] ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=5 code=5[ 1422.840939] ir-kbd-i2c: ir_key_poll: keycode = 0x0505[ 1422.897082] lirc_dev: IR Remote Control driver registered, major 249[ 1422.906668] IR LIRC bridge handler initialized[ 1426.140896] ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=5 code=33[ 1426.140902] ir-kbd-i2c: ir_key_poll: keycode = 0x0521[ 1426.240895] ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=5 code=33[ 1426.240901] ir-kbd-i2c: ir_key_poll: keycode = 0x0521[ 1426.440895] ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=5 code=33[ 1426.440901] ir-kbd-i2c: ir_key_poll: keycode = 0x0521[ 1426.540893] ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=5 code=33[ 1426.540898] ir-kbd-i2c: ir_key_poll: keycode = 0x0521[ 1426.740888] ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=5 code=33[ 1426.740893] ir-kbd-i2c: ir_key_poll: keycode = 0x0521[ 1426.840893] ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=5 code=33[ 1426.840898] ir-kbd-i2c: ir_key_poll: keycode = 0x0521
> Aug 20 21:03:34 myth4 lircd-0.9.0[2264]: lircd(devinput) ready, using /var/run/lirc/lircdAug 20 21:03:39 myth4 lircd-0.9.0[2264]: accepted new client on /var/run/lirc/lircdAug 20 21:03:39 myth4 lircd-0.9.0[2264]: initializing '/dev/input/event8'Aug 20 21:03:40 myth4 lircd-0.9.0[2264]: you are using an obsolete devinput config file: SuccessAug 20 21:03:40 myth4 lircd-0.9.0[2264]: get the new version at http://lirc.sourceforge.net/remotes/devinput/lircd.conf.devinput: SuccessAug 20 21:03:46 myth4 lircd-0.9.0[2264]: removed clientAug 20 21:03:46 myth4 lircd-0.9.0[2264]: closing '/dev/input/event8'Aug 20 21:17:00 myth4 lircd-0.9.0[2264]: accepted new client on /var/run/lirc/lircdAug 20 21:17:00 myth4 lircd-0.9.0[2264]: initializing '/dev/input/event8'Aug 20 21:17:07 myth4 lircd-0.9.0[2264]: removed clientAug 20 21:17:07 myth4 lircd-0.9.0[2264]: closing '/dev/input/event8'
> [root at myth4 ~]# ir-keytableFound /sys/class/rc/rc0/ (/dev/input/event8) with:        Driver ir-kbd-i2c, table rc-hauppauge        Supported protocols: RC-5        Enabled protocols: RC-5        Repeat delay = 500 ms, repeat period = 125 ms[root at myth4 ~]# ps ax | grep [l]ircd 2264 ?        Ss     0:00 /usr/sbin/lircd --driver=devinput --device=/dev/input/event8[root at myth4 ~]#

Read this thread.  It may contain helpful information.

More information about the mythtv-users mailing list