[mythtv-users] Going Nuts.. LIRC IRW Comes up, pressing buttons gives no output
knowledgejunkie at gmail.com
Sat Sep 22 21:55:33 UTC 2007
On 22/09/2007, Ben Kevan <ben.kevan at gmail.com> wrote:
> Is this a hardware thing?
> lsmod | grep lirc
> lirc_i2c 11268 0
> lirc_pvr150 19636 2
> lirc_dev 15988 2 lirc_i2c,lirc_pvr150
> ivtv 134544 3 lirc_pvr150
> i2c_core 22656 12
> dmesg | grep -i lirc_i2c
> [ 171.721405] [<f8d105c2>] init_module+0x42/0x50 [lirc_i2c]
> dmesg | grep -i lirc_pvr150
> [ 34.679106] lirc_pvr150: no version for "lirc_unregister_plugin" found:
> kernel tainted.
> [ 34.711620] lirc_pvr150: chip found with RX and TX
> [ 34.746392] lirc_pvr150: firmware of size 258140 loaded
> [ 34.747020] lirc_pvr150: 654 codesets loaded
> [ 34.779096] lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version
> Should I try it without the blaster? And only the lirc_i2c?
As I understand things, you want to load lirc_pvr150 if you want to
use both the RX and TX functionality of the PVR-150. If you only want
to use a remote control, you should only have to load lirc_i2c.
Loading either of these modules will in turn pull in the lirc_dev
module and create the /dev/lirc and /dev/lirc0 devices. I don't think
you want both the lirc_pvr150 and lirc_i2c modules loaded at the same
Ensure you have a good /etc/lircd.conf for the remote and a ~/.lircrc
config for your LIRC-enabled programs.
MythTV Official wiki:
MythTV users list archive:
"An investment in knowledge always pays the best interest." - Benjamin Franklin
More information about the mythtv-users