<quote who="Andy Walls">
> On Fri, 2008-07-11 at 20:56 -0400, Josh Becigneul wrote:
>>
>> Not sure why this happens, any ideas?
>>
>
> lirc_i2c is the receive only module.  lirc_pvr150 is a module that
> handles both Tx and Rx.  I suspect they are mutually exclusive: you
> probably can't load lirc_i2c and lirc_pvr150 together.  Try to inhibit
> the load of the  lirc_i2c module.
>
> Regards,
> Andy

Andy,

I moved the lirc_i2c driver so it can never be loaded. Running modprobe
lirc_pvr150 results in the following:

otherbox misc # modprobe lirc_pvr150
FATAL: Could not open '/lib/modules/2.6.24-gentoo-r4/misc/lirc_i2c.ko': No
such file or directory

And this is from my syslog:

Jul 12 00:29:16 otherbox ivtv:  Start initialization, version 1.3.0
Jul 12 00:29:16 otherbox ivtv:  End initialization
Jul 12 00:29:16 otherbox lirc_dev: IR Remote Control driver registered,
major 61
Jul 12 00:29:17 otherbox lirc_pvr150: chip found with RX and TX
Jul 12 00:29:17 otherbox lirc_dev: lirc_register_plugin: sample_rate: 0
Jul 12 00:29:17 otherbox lirc_pvr150: firmware of size 302355 loaded
Jul 12 00:29:17 otherbox lirc_pvr150: 743 codesets loaded
Jul 12 00:29:17 otherbox i2c-adapter i2c-1: Used 4 tries to write to
client at 0x70: success
Jul 12 00:29:17 otherbox lirc_pvr150: Hauppauge PVR-150 IR blaster:
firmware version 2.1.0
Jul 12 00:29:17 otherbox i2c-adapter i2c-2: NAK from device addr 0x70 msg #0
Jul 12 00:29:17 otherbox i2c-adapter i2c-2: NAK from device addr 0x71 msg #0
Jul 12 00:29:17 otherbox lirc_pvr150: cx18 i2c driver #0-1: no devices found

So far so good...

Running irsend results in the following:

otherbox bin # ./irsend SEND_ONCE blaster POWER
buffer: -BEGIN-
buffer: -SEND_ONCE blaster POWER-
buffer: -ERROR-
irsend: command failed: SEND_ONCE blaster POWER
buffer: -DATA-
buffer: -1-
buffer: -transmission failed-
irsend: transmission failed
buffer: -END-

lircd -n says:

lircd: accepted new client on /dev/lircd
lircd: write failed
lircd: Remote I/O error
lircd: error processing command: SEND_ONCE blaster POWER
lircd: transmission failed
lircd: removed client

Syslog says:

Jul 12 00:47:49 otherbox i2c-adapter i2c-1: NAK from device addr 0x70 msg #0
Jul 12 00:47:49 otherbox lirc_pvr150: i2c_master_send failed with -121
Jul 12 00:47:49 otherbox lirc_pvr150: sending to the IR transmitter chip
failed, trying reset
Jul 12 00:47:49 otherbox i2c-adapter i2c-1: Used 4 tries to write to
client at 0x70: success
Jul 12 00:47:49 otherbox lirc_pvr150: unexpected IR TX response: a0
Jul 12 00:47:49 otherbox i2c-adapter i2c-1: NAK from device addr 0x70 msg #0
Jul 12 00:47:49 otherbox lirc_pvr150: i2c_master_send failed with -121
Jul 12 00:47:49 otherbox lirc_pvr150: sending to the IR transmitter chip
failed, trying reset
Jul 12 00:47:50 otherbox i2c-adapter i2c-1: Used 4 tries to write to
client at 0x70: success
Jul 12 00:47:50 otherbox lirc_pvr150: unexpected IR TX response: a0
Jul 12 00:47:50 otherbox i2c-adapter i2c-1: NAK from device addr 0x70 msg #0
Jul 12 00:47:50 otherbox lirc_pvr150: i2c_master_send failed with -121
Jul 12 00:47:50 otherbox lirc_pvr150: sending to the IR transmitter chip
failed, trying reset
Jul 12 00:47:50 otherbox i2c-adapter i2c-1: Used 4 tries to write to
client at 0x70: success
Jul 12 00:47:50 otherbox lirc_pvr150: unexpected IR TX response: a0
Jul 12 00:47:50 otherbox i2c-adapter i2c-1: NAK from device addr 0x70 msg #0
Jul 12 00:47:50 otherbox lirc_pvr150: i2c_master_send failed with -121
Jul 12 00:47:50 otherbox lirc_pvr150: sending to the IR transmitter chip
failed, trying reset
Jul 12 00:47:50 otherbox lirc_pvr150: unable to send to the IR chip after
3 resets, giving up

Hope this helps... I'm going to run downstairs and see if the light on the
blaster blinks at all.

I also found this thread which is a little more complete:
http://mysettopbox.tv/phpBB2/viewtopic.php?t=6206&postdays=0&postorder=asc&start=0&sid=88e71f09b17342208fcaca9e220bdd4d

-Josh Becigneul



_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to