[mythtv-users] Continuing the lirc Fedora14 issue with PVR350

The Walters sbwalters0731 at gmail.com
Mon Feb 7 17:23:53 UTC 2011

>>/  >>
/>>/  /  This past week had to replace a dead motherboard on a system that has been running solid for 4 years with myth 0.21 and fedora 8.  Did a clean install of Fedora 14 and mythtv 0.24.  All is working well except for PVR350 remote (I have a 150 in the system as well no remote input).  I have seen where ivtv has move to the kernel and lirc_zilog is now going to be the standard.  Don't have an IR Blaster just a receiver.
/>>/  /
/>>/  >  lirc_zilog is for devices with a zilog z8 chip on them, which all support both
/>>/  >  send and receive. You still use lirc_i2c or ir-kbd-i2c for devices that do
/>>/  >  receive only (lirc_i2c is going away, ir-kbd-i2c is the way forward, can still
/>>/  >  be used with lirc using its devinput driver).
/>>/  Thanks, didn't realise that.
/>>/  I set LIRC_DRIVER="devinput" but it still comes up with lirc_zilog.
>"it" still comes up? lsmod shows you have lirc_zilog loaded. Doesn't
>matter though, its not bound to anything.

Sorry about that bad language.

>>/  If I modprobe ir-kbd-i2c then lsmod|grep -i lirc i get
/>>/>  ir_lirc_codec           3417  0
/>>/>  rc_core                14291  9 ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,rc_rc5_tv,ir_nec_decoder,ir_kbd_i2c
/>>/>  lirc_zilog             11784  0
/>>/>  lirc_dev               12896  2 ir_lirc_codec,lirc_zilog
/>>>/  i2c_core               21328  18 ir_kbd_i2c,lirc_zilog,msp3400,saa7127,saa7115,tuner_simple,wm8775,tda9887,tda8290,tuner,cx25840,nvidia,ivtv,v4l2_common,videodev,i2c_algo_bit,i2c_nforce2,tveeprom
>Looks sane.

>>/  dmesg
/>>/  [ 3376.918767] IR NEC protocol handler initialized
/>>/  [ 3376.932119] IR RC5(x) protocol handler initialized
/>>/  [ 3376.937260] IR RC6 protocol handler initialized
/>>/  [ 3376.942858] IR JVC protocol handler initialized
/>>/  [ 3376.947887] IR Sony protocol handler initialized
/>>/  [ 3376.952063] Registered IR keymap rc-rc5-tv
/>>/  [ 3376.952326] input: i2c IR (Hauppauge WinTV PVR-350 as /devices/virtual/rc/rc0/input7
/>>/  [ 3376.953534] rc0: i2c IR (Hauppauge WinTV PVR-350 as /devices/virtual/rc/rc0
/>>/  [ 3376.953542] ir-kbd-i2c: i2c IR (Hauppauge WinTV PVR-350 detected at i2c-2/2-0018/ir0 [ivtv i2c driver #1]
/>>/  [ 3376.955127] IR LIRC bridge handler initialized
>Also looks sane.

>>/  I restart lirc and then check irw but still no luck.  I have lircd.conf in /etc/lirc/ and my .lircrc file in the .mythtv folder.
/>>/  Do i also need to set the LIRC_DEVICE? (I think the virtual device is what I need.  I saw in my searching that this is probably /dev/input/event7?)
>Yes, you need to set LIRC_DEVICE to /dev/input/eventX that matches the
>device created by ir-kbd-i2c (cat /proc/bus/input/devices to see which
>one it has -- look at the H: Handlers= line).

>And you also need the devinput lircd.conf, not the Hauppauge one. You'll
>be mapping input layer scancodes now, not rc5 IR signals.

I was just reading a post you made back on 3-31-2010 about that and have done so.

I added LIRC_MODULE="ir-kbd-i2c" to /etc/sysconfig/lirc but the ir-kbd-i2c doesn't get loaded so i end up with
lircd-0.9.0-pre1[1569]: unable to open '/dev/input/event7'

Is this the right place to load the module?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20110207/0de391b2/attachment.htm>

More information about the mythtv-users mailing list