Hi there,

I've FINALLY got my mythtv box up and running (huzzah!), although one (albeit small) thorn in my side with my box is that my PVR-350 remote isn't quite as responsive as i'd like. What i mean by this is that when navigating through the frontend menus it takes usually a contant press of a key for a couple of seconds to get to to respond, rather than the usual quick tap you associate with other remote control devices (like your regular tv remote for example). Now I've read other people have had problems like this from googling, but no replies of advice).

Interestingly in /var/log/messages i also see loads of these:

ug 8 14:24:24 mythtv kernel: i2c IR (Hauppauge): unknown key: key=0x25 raw=0x37a5 down=1
Aug 8 14:24:25 mythtv kernel: i2c IR (Hauppauge): unknown key: key=0x25 raw=0x37a5 down=0
Aug 8 14:24:30 mythtv kernel: i2c IR (Hauppauge): unknown key: key=0x15 raw=0x3f95 down=1


Which i guess might be related to the slow IR response, (or is this expected output for some reason?).


Machine Stats:
Knopmyth R5C7
256 Ram
PVR-350
Duron 1600mhz (ish!)
300Gb Maxtor DMax 10
gfx card generic 2meg vga card!


Thanks in advance to anyone with any helpful advice!

_________________
lau

Well, this effect occures from the "unknown key". I described the "unknown key" problem http://mysettopbox.tv/phpBB2/viewtopic.php?t=11102.

"Slowing down" the remote is the effect which occures at my Mythbox.
I would be very happy if there is a solution out there.

Thanks i'll take a look at that.


Anyone got any ideas about speeding up the remote?

_________________
lau

This won't help, but maybe you will feel better knowing you're not alone. I'm having the exact same problem with my 350. Anyone

Heck, I could deal with a slower than normal remote if I had button sounds, so I knew a press was seen my myth. Unfortunately, when I tried the script to add sound, I lost the sound during playback!

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb

I believe this is the same problem covered in the R5F27 hints and tips, under Known Issues #5

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

_________________
Retired KM user (R4 - R6.04); friend to LH users.

Apparently my problem was along the lines of the conflict between lirc_i2c and ir-kbd-i2c. What got the remote working for me was to remove the ir-kbd-i2c kernel module like this:

dmesg | grep saa7134

It wasn't in use, so I ran:

mv /lib/modules/2.6.18-chw-13/kernel/drivers/media/video/ir-kbd-i2c.ko /lib/modules/2.6.18-chw-13/kernel/drivers/media/video/ir-kbd-i2c.ko.bak

Rebooted, and it works much better now.

Notably, now when I run

dmesg | grep saa7134

I get:
saa7134: Unknown symbol get_key_pinnacle_color
saa7134: Unknown symbol get_key_pinnacle_grey
saa7134_dvb: Unknown symbol saa7134_ts_register
saa7134_dvb: Unknown symbol saa7134_set_gpio
saa7134_dvb: Unknown symbol saa7134_ts_qops
saa7134_dvb: Unknown symbol saa7134_i2c_call_clients
saa7134_dvb: Unknown symbol saa7134_ts_unregister

This is why the R5F27 hints tell you to comment out the dvb module loading and provide an example sed command to do it...