I have installed version R5A22 and have a Non-MCE PVR-150. Both times were 100% successful. However the remote does not work.

I have searched all over the Myth mailing lists and forums for an answer to this and all I find are ways to solve versions EARLIER that R5A22. I am new to Linux but learn new OS's very fast. I have also seen the same people with this question that report that it worked for them without manually configuring anything.

I have brought back up the IR config options, and set it for all 3 remote options under Hauppauge with no luck. I would appreciate any steps on both troubleshooting and solving this issue.

Thanks

Make sure you have fresh batteries in the remote in the correct orientation, that the receiver cable is plugged firmly into the correct connector (it's the smaller black at the "bottom" of the card), and that the "eye" is oriented towards the remote.
http://images10.newegg.com/NeweggImage/productimage/15-116-625-06.JPG
http://images10.newegg.com/NeweggImage/productimage/15-116-625-07.JPG

- Run the lirc-reconfig.sh script.

- Select "Hauppauge" and then "silver remote" (thicker on the ends than in the middle as shown in the picture right?)

- Reboot

- Check the log file /var/log/dmesg if you still have a problem, and make sure you don't have any errors in the IVTV sections about not being able to load firmware.

Yep, same one, I actually ordered it from Newegg!

Ran the script and selected silver, rebooted. Nothing.

I checked the connection a thousand times yesterday so i know its good. I will go out and buy some new AAA batteries tomorrow to check that. I installed the card in Windows a month ago and the remote worked then so I know the unit is not defective. Perhaps the batteries died.

Log file showed no errors in the IVTV section and had a line that firmware was loaded so it appears that it was successful.

Thanks

Also try this:

Ok after running the above command it seems that there is something wrong. Got Webmin running last night late, pretty cool...now I can POST this info.

/var/log/daemon.log:Nov 8 00:47:18 mythtv lircd-0.7.2pvr150[5018]: lircd(any) ready
/var/log/daemon.log:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: accepted new client on /dev/lircd
/var/log/daemon.log:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: could not open /dev/lirc
/var/log/daemon.log:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: default_init(): No such device
/var/log/daemon.log:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: caught signal
/var/log/daemon.log:Nov 7 22:06:21 mythtv lircd-0.7.2pvr150[3169]: lircd(any) ready
/var/log/daemon.log:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: accepted new client on /dev/lircd
/var/log/daemon.log:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: could not open /dev/lirc
/var/log/daemon.log:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: default_init(): No such device
/var/log/daemon.log:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: caught signal
/var/log/kern.log:Nov 8 00:47:18 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
/var/log/kern.log:Nov 8 00:47:18 mythtv kernel: lirc_pvr150: ivtv i2c driver #0: no devices found
/var/log/kern.log:Nov 7 22:06:21 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
/var/log/kern.log:Nov 7 22:06:21 mythtv kernel: lirc_pvr150: ivtv i2c driver #0: no devices found
/var/log/messages:Nov 8 00:47:18 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
/var/log/messages:Nov 7 22:06:21 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
/var/log/syslog.0:Nov 8 00:47:18 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
/var/log/syslog.0:Nov 8 00:47:18 mythtv kernel: lirc_pvr150: ivtv i2c driver #0: no devices found
/var/log/syslog.0:Nov 8 00:47:18 mythtv lircd-0.7.2pvr150[5018]: lircd(any) ready
/var/log/syslog.0:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: accepted new client on /dev/lircd
/var/log/syslog.0:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: could not open /dev/lirc
/var/log/syslog.0:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: default_init(): No such device
/var/log/syslog.0:Nov 8 00:48:57 mythtv lircd-0.7.2pvr150[5018]: caught signal
/var/log/syslog.0:Nov 7 22:06:21 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
/var/log/syslog.0:Nov 7 22:06:21 mythtv kernel: lirc_pvr150: ivtv i2c driver #0: no devices found
/var/log/syslog.0:Nov 7 22:06:21 mythtv lircd-0.7.2pvr150[3169]: lircd(any) ready
/var/log/syslog.0:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: accepted new client on /dev/lircd
/var/log/syslog.0:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: could not open /dev/lirc
/var/log/syslog.0:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: default_init(): No such device
/var/log/syslog.0:Nov 7 22:06:37 mythtv lircd-0.7.2pvr150[3169]: caught signal

what is even more frustrating for me is that everything was working great... for about ten minutes. remote and everything! this is after i configured my ATI TV out, and onboard audio digital coax out! now the remote just isn't working. i'm going to keep digging, though.

changed the batteries, and i've repluged the IR catcher quite a few times.

i've installed windows previously, and the remote works perfectly.

this may be no help, but I know on the pvr250 I've done this and heard of other people doing it too the plug where the ir reciever plugs in is very easy to not have it pluged all the way in, but think you do.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

I know that's true for my PVR-350 as well. It's not a very secure and strong "click" that keeps the plug in.

Plus - I don't think the socket is very strong and secure on the PVR card, either, as my plug/socket rocks around a bit - you can wiggle it side-to-side enough that it seems the solder connections may be broken on the board itself.

something even more strange.

i reinstalled because i had imported teh SQL data with the wrong time set. the first boot, the remote worked fine. second boot, erratically, now not at all. this is very strange.

and i keep getting



in my log files

I was having the same problem. I did a re-install with out changing anything. I had been changing /cache and /myth to xfs and jfs. The plain vanilla install worked great.

If you are changing the file systmes I would try it once with out.

good luck

yeah, that's the thing. it worked right out of the box, but after a few reboots... poof! stopped working.

Well it has never worked for me and I have reinstalled 3 times.

Since then I have added every icon of every channel to the database, installed Webmin, Samba, and countless other hard things that have went smooth EXCEPT for the remote.

tjc did you see the post of my log I posted above yet?

Yeah, but nothing obvious is jumping out at me, other than that you've definitely got a problem.

Did we check in the /var/log/dmesg log file yet to see if all of your firmware is getting loaded? What does this show for you?

Actually make that:

I got:

> ls -al /dev/lirc*
crw-r--r-- 1 root root 61, 0 Sep 25 03:01 /dev/lirc
crw-r--r-- 1 root root 61, 1 Oct 1 04:02 /dev/lirc1
srw-rw-rw- 1 root root 0 Nov 8 19:57 /dev/lircd
prw-r--r-- 1 root root 0 Jul 30 2004 /dev/lircm