I have a PVR 150 with a new silver remote. Now in R26 it did not work out of the box, but I did find a little help in the forum that did seem to help.

I did the install telling it I had a gray remote. Rebooted and then did the lirc-reconfig.sh and told it I have a pvr 150 remote.

What this did for me: Well now when I go into a shell and put in irw I get codes out. I get the correct code for every button I press. They all appear is a 350 remote, but they are the correct button.

The problem,. Mythtv does nothing when I press them. I am new to Mythtv and linux in general. Knoppmyth is great and everything else is working correctly and I love it, but I really do want to get the remote working. Please help.

_________________
R5F1 : AMD 64 2800 : Nvidia 5200 : 2x PVR- 150

You're a little lean on the details.

- Presumbaly you've rebooted after making the changes? The lircd is finicky about this.

- Have you checked the connections? It's really easy for that little tiny plug to not be well seated, and we've probably had a dozen different cases where reseating it solved the problem.

- Have you check the log files? Primarily /var/log/daemon.log and /var/log/syslog

After the last change I did not reboot. I will do that tommarow.

I am pretty sure that the cable is connected correctly, because irw did see all the commands that I was giving it from the remote control, but I will re check again tomarrow.

I will look at the log files. Thanks for telling me where to look, but exactly what am I looking for? just general errors I would expect?

Thanks for the help...

_________________
R5F1 : AMD 64 2800 : Nvidia 5200 : 2x PVR- 150

Here is something intersting I found in the daemon.log file:

Nov 30 12:31:10 mythtv lircd-0.7.2pvr150[4646]: caught signal
Nov 30 12:31:28 mythtv lircd-0.7.2pvr150[4660]: lircd(any) ready
Nov 30 12:31:31 mythtv lircd-0.7.2pvr150[4660]: accepted new client on /dev/lircd
Nov 30 12:32:11 mythtv lircd-0.7.2pvr150[4660]: accepted new client on /dev/lircd
Nov 30 12:32:15 mythtv lircd-0.7.2pvr150[4660]: removed client
Nov 30 12:32:31 mythtv lircd-0.7.2pvr150[4660]: removed client
Nov 30 12:32:31 mythtv lircd-0.7.2pvr150[4660]: caught signal
Nov 30 12:32:31 mythtv lircd-0.7.2pvr150[4732]: lircd(any) ready
Nov 30 12:32:34 mythtv lircd-0.7.2pvr150[4732]: caught signal
Nov 30 12:32:34 mythtv lircd-0.7.2pvr150[4762]: lircd(any) ready
Nov 30 12:32:37 mythtv lircd-0.7.2pvr150[4762]: accepted new client on /dev/lircd
Nov 30 12:32:39 mythtv lircd-0.7.2pvr150[4762]: removed client
Nov 30 12:32:43 mythtv lircd-0.7.2pvr150[4762]: caught signal
Nov 30 12:32:43 mythtv lircd-0.7.2pvr150[4797]: lircd(any) ready
Nov 30 12:32:50 mythtv lircd-0.7.2pvr150[4797]: accepted new client on /dev/lircd
Nov 30 12:32:52 mythtv lircd-0.7.2pvr150[4797]: accepted new client on /dev/lircd
Nov 30 12:32:57 mythtv lircd-0.7.2pvr150[4797]: removed client
Nov 30 12:32:59 mythtv init: Switching to runlevel: 6
Nov 30 12:33:06 mythtv lircd-0.7.2pvr150[4797]: removed client
Nov 30 12:33:06 mythtv lircd-0.7.2pvr150[4797]: caught signal

I found this in the syslog file

Nov 30 06:33:41 mythtv kernel: lirc_pvr150: i2c_master_send failed with -121
Nov 30 06:33:41 mythtv kernel: lirc_pvr150: polling the IR receiver chip failed, trying reset
Nov 30 06:35:37 mythtv kernel: i2c_adapter i2c-2: sendbytes: error - bailout.
Nov 30 06:35:37 mythtv kernel: lirc_pvr150: i2c_master_send failed with -14
Nov 30 06:35:37 mythtv kernel: lirc_pvr150: polling the IR receiver chip failed, trying reset
Nov 30 06:35:45 mythtv kernel: i2c_adapter i2c-2: sendbytes: error - bailout.
Nov 30 06:35:45 mythtv kernel: lirc_pvr150: i2c_master_send failed with -14
Nov 30 06:35:45 mythtv kernel: lirc_pvr150: polling the IR receiver chip failed, trying reset

and this also.

lirc_dev: IR Remote Control driver registered, at major 61
Nov 30 12:35:17 mythtv kernel: lirc_pvr150: chip found with RX and TX
Nov 30 12:35:17 mythtv kernel: ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR RX, addr=71]
Nov 30 12:35:17 mythtv kernel: ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR TX, addr=70]
Nov 30 12:35:17 mythtv kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
Nov 30 12:35:17 mythtv kernel: lirc_pvr150: firmware of size 209327 loaded
Nov 30 12:35:17 mythtv kernel: lirc_pvr150: 575 codesets loaded
Nov 30 12:35:17 mythtv kernel: lirc_pvr150: unexpected IR TX response: 00
Nov 30 12:35:17 mythtv lircd-0.7.2pvr150[2759]: lircd(any) ready
Nov 30 12:35:37 mythtv lircd-0.7.2pvr150[2759]: accepted new client on /dev/lircd
Nov 30 12:35:39 mythtv lircd-0.7.2pvr150[2759]: accepted new client on /dev/lircd
Nov 30 12:40:34 mythtv lircd-0.7.2pvr150[2759]: accepted new client on /dev/lircd
Nov 30 12:40:37 mythtv lircd-0.7.2pvr150[2759]: removed client
Nov 30 12:42:42 mythtv lircd-0.7.2pvr150[2759]: removed client

Any Ideas now? I am grabbing at straws here...

_________________
R5F1 : AMD 64 2800 : Nvidia 5200 : 2x PVR- 150

Any Ideas? Anyone?

_________________
R5F1 : AMD 64 2800 : Nvidia 5200 : 2x PVR- 150

I have the same problem, but unfortunately, no solution. Which version of LIRC are you using?

I am using the defalt ver that comes with R5A26. Sometimes it works and then just stops working. Its just wierd.

_________________
R5F1 : AMD 64 2800 : Nvidia 5200 : 2x PVR- 150

Try Mark's instructions.
http://www.blushingpenguin.com/mark/blog/?p=23

I tried those instruction several times, but unfortunately they caused my remote to stop functioning all together.

I have band-aided the problem by adding the following code to my crontab.

* * * * * root ivtvctl --reset-ir


This runs the ivtvctl --reset-ir command every minute, which will reset the IR and make the remote work after it stops working. The problem is...if the remote drops out, you have to wait out the clock until the next minute hits so that this gets run. I've also heard there are issues with using this method along with the IR blaster, but I don't use the IR blaster, so I wouldn't know.

What I did to stop it happening on mine is listed at the bottom of this thread

http://mysettopbox.tv/phpBB2/viewtopic.php?t=7458

Apparently there is a known hardware issue with some PVR cards related to the remote losing it's marbles. The most recent IVTV drivers apparently take care of the reseting internally...