From: Henrik G. <li...@ge...> - 2006-07-13 15:50:38
|
Henrik Gammelmark wrote: > I am having difficulties using the PVR-350 remote control with lirc. > I have after a lot of trouble succeeded in making the remote work and > get the buttons mapped right. > > However, often I must press the same key a bunch of times, or keep it > pressed for a second or two before lirc responds to it. > The "missed" button presses show up in dmesg like this: > > i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=1 > i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=0 > > If only the 3's would be 1's, the keys match the ones in lircd.conf. > However, adding them to lircd.conf also, has no effect. Why can't I use > them as well? > > I tried one more thing - I found out that irrecord can autodetect the > keys by reading from the remote. The provided values are the > "1xxx"-range values matching the ones already in my config as opposed to > the "3xxx" that are "unknown". > It also provides a header which is the following: > > bits 13 > flags RC5|CONST_LENGTH > eps 30 > aeps 100 > > one 889 889 > zero 889 889 > plead 889 > gap 500011 > toggle_bit 2 > > frequency 36000 > duty_cycle 50 > > It took forever to detect this (a few minutes just for the "gap" > detect), and afterwards it still don't work any > better than before. > > Using Debian testing on Linux 2.6.16.20 with i2c support. I tried it on my desktop system, and the remote worked perfectly, by installing the same versions of everything as on the mythbox. I noticed that on the desktop the device is called /dev/lirc, while on the actual mythbox it is named /dev/lirc0 - why is that? Perhaps something is left-over from my previous binary Debian packages? There are no other lircd processes running, the packages are uninstalled, and lsmod shows only the modules I compiled myself... Please help - I'm desperate here!! |