<br><br><div class="gmail_quote">On Fri, Dec 17, 2010 at 2:13 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Dec 16, 2010, at 7:09 PM, Rodd Clarkson wrote:<br>
<br>
> On Thu, Dec 16, 2010 at 5:34 PM, Grant McChesney <<a href="mailto:grantmc@gmail.com">grantmc@gmail.com</a>> wrote:<br>
> On Wed, Dec 15, 2010 at 9:37 PM, Michael Rice <<a href="mailto:mikerice1969@gmail.com">mikerice1969@gmail.com</a>> wrote:<br>
> On Wed, Dec 15, 2010 at 7:08 PM, Newbury <<a href="mailto:newbury@mandamus.org">newbury@mandamus.org</a>> wrote:<br>
> ><br>
> >> Seems to have the same problem for me.<br>
> >><br>
> >> [root@mythfrontend2 ~]# uname -a<br>
> >> Linux mythfrontend2 2.6.35.10-67.fc14.i686.PAE #1 SMP Wed Dec 15<br>
> >> 22:45:07 UTC 2010 i686 i686 i386 GNU/Linux<br>
> >><br>
> >> Again the irw output from pressing a single Up after several Downs:<br>
> >><br>
> >> [root@mythfrontend2 ~]# irw<br>
> >> 0001006c00000001 00 Down devinput<br>
> >> 0001006700000001 00 Up devinput<br>
> ><br>
> > And that is what you are looking for, unless I Missed something.<br>
><br>
> Nope. When I press Up I don't want it to register Down/Up. Just Up. :)<br>
><br>
> It is still doing something strange. One key press usually (or always?)<br>
> generates two presses one of which is held until the next key is pressed<br>
> at which time they both come out.<br>
><br>
> In the output above I had hit a bunch of down keys. Waited a few seconds<br>
> then ran irw and hit a single Up. At that point the buffered Down is emitted<br>
> along with an Up.<br>
><br>
> Glad I'm not the only one experiencing this behavior. I've been hacking away at my lircd.conf trying to fix it. I've resorted to my wireless keyboard until this gets sorted.<br>
><br>
> Jarod, I look forward to the fix. Thanks!<br>
><br>
><br>
> Jarrod,<br>
><br>
> I've just tried kernel-2.6.35.10-68 and it's better in terms of response time, and ironically it's worse because of this. HUH?<br>
><br>
> I think I'm getting double inputs from my remote because both lirc and evdev at using it as an input device. When I press some keys on my remote, they seem to be doing things twice. For example, press the up or down I sometimes skip an item in the menu. However, I think this is related to evdev and lirc running at the same time.<br>
><br>
> if I run `xev` and `irw` in two seperate terminal windows and then press the up and down keys on the remove I get in 'xev':<br>
><br>
> KeyPress event, serial 30, synthetic NO, window 0x4800001,<br>
> root 0xbf, subw 0x0, time 654082, (630,511), root:(634,560),<br>
> state 0x10, keycode 111 (keysym 0xff52, Up), same_screen YES,<br>
> XLookupString gives 0 bytes:<br>
> XmbLookupString gives 0 bytes:<br>
> XFilterEvent returns: False<br>
><br>
> KeyRelease event, serial 33, synthetic NO, window 0x4800001,<br>
> root 0xbf, subw 0x0, time 654331, (630,511), root:(634,560),<br>
> state 0x10, keycode 111 (keysym 0xff52, Up), same_screen YES,<br>
> XLookupString gives 0 bytes:<br>
> XFilterEvent returns: False<br>
><br>
> KeyPress event, serial 33, synthetic NO, window 0x4800001,<br>
> root 0xbf, subw 0x0, time 655246, (630,511), root:(634,560),<br>
> state 0x10, keycode 116 (keysym 0xff54, Down), same_screen YES,<br>
> XLookupString gives 0 bytes:<br>
> XmbLookupString gives 0 bytes:<br>
> XFilterEvent returns: False<br>
><br>
> KeyRelease event, serial 33, synthetic NO, window 0x4800001,<br>
> root 0xbf, subw 0x0, time 655614, (630,511), root:(634,560),<br>
> state 0x10, keycode 116 (keysym 0xff54, Down), same_screen YES,<br>
> XLookupString gives 0 bytes:<br>
> XFilterEvent returns: False<br>
><br>
> and in 'irw' i get:<br>
><br>
> 000000037ff07be1 00 Up mceusb<br>
> 000000037ff07be0 00 Down mceusb<br>
> 000000037ff07be0 01 Down mceusb<br>
><br>
> As a result, my remote now skips every second menu item.<br>
><br>
> Why is this worse? We, because (and I'm taking an educated quess here) there were keypress delay issues in older kernels than the one above, if I pressed the buttons on the remote quickly, I saw only the output in the irw window. However, if I held the button a little longer, i got output in both windows. In the example above, I wouldn't have seen the KeyPress/Release event for the 'Up' action, but I would have got both Down events.<br>
><br>
> Is it fair to assume that both evdev and lirc are giving mythtv a command each and that's why I'm going up and down two menu items at a time?<br>
><br>
> How can I fix this?<br>
<br>
</div></div>echo lirc > /sys/class/rc/rc0/protocols<br>
<br>
That effectively disables in-kernel decoding, setting only userspace<br>
lirc decoding to be active. I'm going to push an updated lirc package<br>
Real Soon Now that does this automatically (needs to be done every time<br>
you reboot).<br></blockquote><div><br>Thanks Jarod for your quick response.<br><br>I got this from another thread:<br><br>echo none > /sys/class/rc/rc0/protocols<br>echo +lirc > /sys/class/rc/rc0/protocols<br><br>which I think is similar and it's worked a treat.<br>
<br>I've stuck this into /etc/rc.local for the moment (is this the right place) and will remove when you get around to that new version of lirc RSN.<br><br>With the combination of this above and the new kernel from koji my remote now works stupendously. Thank you very much for all your hard work.<br>
<br><br>Rodd<br></div></div>