From: Douglas P. <Dou...@pe...> - 2011-01-10 09:15:26
|
I have just upgraded the kernel on my mythbuntu box to 2.6.37 to solve a problem and while that is fixed, I now get two key presses for each arrow key I pressed. Anyone else struck this? Cheers Douglas. |
From: Jarod W. <ja...@wi...> - 2011-01-10 19:14:53
|
On Jan 10, 2011, at 4:15 AM, Douglas Pearless wrote: > I have just upgraded the kernel on my mythbuntu box to 2.6.37 to solve a > problem and while that is fixed, I now get two key presses for each > arrow key I pressed. > > Anyone else struck this? Check /sys/class/rc/rc0/protocols and I bet you'll see that both in-kernel and userspace (lirc) decode are enabled. The Ubuntu lirc initscript was disabling in-kernel decode previously via /sys/devices/virtual/rc/... but those bits got moved. Mario is aware of the problem and I believe was planning to push an updated package for Ubuntu. -- Jarod Wilson ja...@wi... |
From: Mario L. <su...@ub...> - 2011-01-10 19:16:42
|
Yeah, there's a fix already in the packaging. Planning on uploading it when I upload a 0.9 snapshot soon to natty. Here's the updated init script you'll need: http://bazaar.launchpad.net/~mythbuntu-dev/lirc/ubuntu/annotate/head:/debian/lirc.init.d On Mon, Jan 10, 2011 at 13:14, Jarod Wilson <ja...@wi...> wrote: > On Jan 10, 2011, at 4:15 AM, Douglas Pearless wrote: > > > I have just upgraded the kernel on my mythbuntu box to 2.6.37 to solve a > > problem and while that is fixed, I now get two key presses for each > > arrow key I pressed. > > > > Anyone else struck this? > > Check /sys/class/rc/rc0/protocols and I bet you'll see that both in-kernel > and userspace (lirc) decode are enabled. The Ubuntu lirc initscript was > disabling in-kernel decode previously via /sys/devices/virtual/rc/... but > those bits got moved. Mario is aware of the problem and I believe was > planning to push an updated package for Ubuntu. > > -- > Jarod Wilson > ja...@wi... > > > > -- Mario Limonciello su...@gm... |
From: Seth G. <set...@gm...> - 2011-01-10 19:42:32
|
I've been watching these threads on repeating key-presses. I just checked my machine and I don't have this file /sys/class/rc/rc0/protocols or /sys/devices/virtual/rc/. Still no joy for my repeated key-presses. My next step will be to downgrade lirc to 0.8.6, I just haven't had a chance to try it yet. Seth On 01/10/2011 01:14 PM, Jarod Wilson wrote: > On Jan 10, 2011, at 4:15 AM, Douglas Pearless wrote: > >> I have just upgraded the kernel on my mythbuntu box to 2.6.37 to solve a >> problem and while that is fixed, I now get two key presses for each >> arrow key I pressed. >> >> Anyone else struck this? > > Check /sys/class/rc/rc0/protocols and I bet you'll see that both in-kernel > and userspace (lirc) decode are enabled. The Ubuntu lirc initscript was > disabling in-kernel decode previously via /sys/devices/virtual/rc/... but > those bits got moved. Mario is aware of the problem and I believe was > planning to push an updated package for Ubuntu. > -- Seth Galitzer The beatings will continue until morale has improved. |
From: Jarod W. <ja...@wi...> - 2011-01-10 19:59:30
|
On Jan 10, 2011, at 2:22 PM, Seth Galitzer wrote: > I've been watching these threads on repeating key-presses. I just > checked my machine and I don't have this file > /sys/class/rc/rc0/protocols or /sys/devices/virtual/rc/. Still no joy > for my repeated key-presses. My next step will be to downgrade lirc to > 0.8.6, I just haven't had a chance to try it yet. Please don't assume that anyone here already knows what kernel, lirc version, and hardware you're talking about. This thread is about mceusb hardware, and from the list archive, it looks like you're talking about a hauppauge remote with a serial receiver. Its not expected that you'd have either of those /sys paths with lirc_serial, your issue is something else entirely. From your original posting though, it sounds like everything is actually behaving exactly as expected for a raw IR hardware receiver, you just need to do some repeat filtering, either via repeat = x lines in .lircrc, or with 'suppress_repeat y' in lircd.conf. > On 01/10/2011 01:14 PM, Jarod Wilson wrote: >> On Jan 10, 2011, at 4:15 AM, Douglas Pearless wrote: >> >>> I have just upgraded the kernel on my mythbuntu box to 2.6.37 to solve a >>> problem and while that is fixed, I now get two key presses for each >>> arrow key I pressed. >>> >>> Anyone else struck this? >> >> Check /sys/class/rc/rc0/protocols and I bet you'll see that both in-kernel >> and userspace (lirc) decode are enabled. The Ubuntu lirc initscript was >> disabling in-kernel decode previously via /sys/devices/virtual/rc/... but >> those bits got moved. Mario is aware of the problem and I believe was >> planning to push an updated package for Ubuntu. -- Jarod Wilson ja...@wi... |
From: Seth G. <set...@gm...> - 2011-01-10 20:06:51
|
Fair enough. I had no idea the implementation was so wildly different for every device. It seemed reasonable to me that if it was a core issue then it would be device-agnostic. Yes I have tried repeat filtering, as you said, still no luck. I'll stop hijacking this thread now. Seth On 01/10/2011 01:59 PM, Jarod Wilson wrote: > On Jan 10, 2011, at 2:22 PM, Seth Galitzer wrote: > >> I've been watching these threads on repeating key-presses. I just >> checked my machine and I don't have this file >> /sys/class/rc/rc0/protocols or /sys/devices/virtual/rc/. Still no joy >> for my repeated key-presses. My next step will be to downgrade lirc to >> 0.8.6, I just haven't had a chance to try it yet. > > Please don't assume that anyone here already knows what kernel, lirc > version, and hardware you're talking about. This thread is about > mceusb hardware, and from the list archive, it looks like you're > talking about a hauppauge remote with a serial receiver. Its not > expected that you'd have either of those /sys paths with lirc_serial, > your issue is something else entirely. > > From your original posting though, it sounds like everything is > actually behaving exactly as expected for a raw IR hardware receiver, > you just need to do some repeat filtering, either via repeat = x > lines in .lircrc, or with 'suppress_repeat y' in lircd.conf. > > > > >> On 01/10/2011 01:14 PM, Jarod Wilson wrote: >>> On Jan 10, 2011, at 4:15 AM, Douglas Pearless wrote: >>> >>>> I have just upgraded the kernel on my mythbuntu box to 2.6.37 to solve a >>>> problem and while that is fixed, I now get two key presses for each >>>> arrow key I pressed. >>>> >>>> Anyone else struck this? >>> >>> Check /sys/class/rc/rc0/protocols and I bet you'll see that both in-kernel >>> and userspace (lirc) decode are enabled. The Ubuntu lirc initscript was >>> disabling in-kernel decode previously via /sys/devices/virtual/rc/... but >>> those bits got moved. Mario is aware of the problem and I believe was >>> planning to push an updated package for Ubuntu. > > > -- Seth Galitzer The beatings will continue until morale has improved. |
From: Jarod W. <ja...@wi...> - 2011-01-10 20:33:20
|
On Jan 10, 2011, at 3:06 PM, Seth Galitzer wrote: > Fair enough. I had no idea the implementation was so wildly different for every device. It seemed reasonable to me that if it was a core issue then it would be device-agnostic. Yes I have tried repeat filtering, as you said, still no luck. I'll stop hijacking this thread now. Bottom-posting is also highly preferred on this list, though not (yet) officially mandated. :) Please provide irw output from a button press or two. Are you getting true repeats, or are your signals coming through as new presses every time? > On 01/10/2011 01:59 PM, Jarod Wilson wrote: >> On Jan 10, 2011, at 2:22 PM, Seth Galitzer wrote: >> >>> I've been watching these threads on repeating key-presses. I just >>> checked my machine and I don't have this file >>> /sys/class/rc/rc0/protocols or /sys/devices/virtual/rc/. Still no joy >>> for my repeated key-presses. My next step will be to downgrade lirc to >>> 0.8.6, I just haven't had a chance to try it yet. >> >> Please don't assume that anyone here already knows what kernel, lirc >> version, and hardware you're talking about. This thread is about >> mceusb hardware, and from the list archive, it looks like you're >> talking about a hauppauge remote with a serial receiver. Its not >> expected that you'd have either of those /sys paths with lirc_serial, >> your issue is something else entirely. >> >> From your original posting though, it sounds like everything is >> actually behaving exactly as expected for a raw IR hardware receiver, >> you just need to do some repeat filtering, either via repeat = x >> lines in .lircrc, or with 'suppress_repeat y' in lircd.conf. -- Jarod Wilson ja...@wi... |
From: Seth G. <set...@gm...> - 2011-01-10 21:14:06
|
On 01/10/2011 02:33 PM, Jarod Wilson wrote: > On Jan 10, 2011, at 3:06 PM, Seth Galitzer wrote: > >> Fair enough. I had no idea the implementation was so wildly different for every device. It seemed reasonable to me that if it was a core issue then it would be device-agnostic. Yes I have tried repeat filtering, as you said, still no luck. I'll stop hijacking this thread now. > > Bottom-posting is also highly preferred on this list, though not (yet) > officially mandated. :) > > Please provide irw output from a button press or two. Are you getting > true repeats, or are your signals coming through as new presses every > time? > > >> On 01/10/2011 01:59 PM, Jarod Wilson wrote: >>> On Jan 10, 2011, at 2:22 PM, Seth Galitzer wrote: >>> >>>> I've been watching these threads on repeating key-presses. I just >>>> checked my machine and I don't have this file >>>> /sys/class/rc/rc0/protocols or /sys/devices/virtual/rc/. Still no joy >>>> for my repeated key-presses. My next step will be to downgrade lirc to >>>> 0.8.6, I just haven't had a chance to try it yet. >>> >>> Please don't assume that anyone here already knows what kernel, lirc >>> version, and hardware you're talking about. This thread is about >>> mceusb hardware, and from the list archive, it looks like you're >>> talking about a hauppauge remote with a serial receiver. Its not >>> expected that you'd have either of those /sys paths with lirc_serial, >>> your issue is something else entirely. >>> >>> From your original posting though, it sounds like everything is >>> actually behaving exactly as expected for a raw IR hardware receiver, >>> you just need to do some repeat filtering, either via repeat = x >>> lines in .lircrc, or with 'suppress_repeat y' in lircd.conf. > > Bottom-post it is. :) I don't have a irw capture on file, but I remember when I was testing it that they were registering as unique presses, with a new index value each time. I can verify this later if you like. Thanks. Seth -- Seth Galitzer The beatings will continue until morale has improved. |
From: Jarod W. <ja...@wi...> - 2011-01-10 21:31:35
|
On Jan 10, 2011, at 4:13 PM, Seth Galitzer wrote: > On 01/10/2011 02:33 PM, Jarod Wilson wrote: >> On Jan 10, 2011, at 3:06 PM, Seth Galitzer wrote: ... >>>> ...This thread is about >>>> mceusb hardware, and from the list archive, it looks like you're >>>> talking about a hauppauge remote with a serial receiver. Its not >>>> expected that you'd have either of those /sys paths with lirc_serial, >>>> your issue is something else entirely. >>>> >>>> From your original posting though, it sounds like everything is >>>> actually behaving exactly as expected for a raw IR hardware receiver, >>>> you just need to do some repeat filtering, either via repeat = x >>>> lines in .lircrc, or with 'suppress_repeat y' in lircd.conf. ... >>> Fair enough. I had no idea the implementation was so wildly different for every device. It seemed reasonable to me that if it was a core issue then it would be device-agnostic. Yes I have tried repeat filtering, as you said, still no luck. I'll stop hijacking this thread now. >> >> Bottom-posting is also highly preferred on this list, though not (yet) >> officially mandated. :) >> >> Please provide irw output from a button press or two. Are you getting >> true repeats, or are your signals coming through as new presses every >> time? > Bottom-post it is. :) Thank you, much appreciated. > I don't have a irw capture on file, but I remember when I was testing it that they were registering as unique presses, with a new index value each time. I can verify this later if you like. Hm, need clarification... "new index value" each time... If they were registering as unique keypresses, the index value should always be 00. If they were incrementing, then they're repeats. -- Jarod Wilson ja...@wi... |
From: Seth G. <set...@gm...> - 2011-01-10 21:32:51
|
On 01/10/2011 03:31 PM, Jarod Wilson wrote: > On Jan 10, 2011, at 4:13 PM, Seth Galitzer wrote: > >> On 01/10/2011 02:33 PM, Jarod Wilson wrote: >>> On Jan 10, 2011, at 3:06 PM, Seth Galitzer wrote: > ... >>>>> ...This thread is about >>>>> mceusb hardware, and from the list archive, it looks like you're >>>>> talking about a hauppauge remote with a serial receiver. Its not >>>>> expected that you'd have either of those /sys paths with lirc_serial, >>>>> your issue is something else entirely. >>>>> >>>>> From your original posting though, it sounds like everything is >>>>> actually behaving exactly as expected for a raw IR hardware receiver, >>>>> you just need to do some repeat filtering, either via repeat = x >>>>> lines in .lircrc, or with 'suppress_repeat y' in lircd.conf. > ... >>>> Fair enough. I had no idea the implementation was so wildly different for every device. It seemed reasonable to me that if it was a core issue then it would be device-agnostic. Yes I have tried repeat filtering, as you said, still no luck. I'll stop hijacking this thread now. >>> >>> Bottom-posting is also highly preferred on this list, though not (yet) >>> officially mandated. :) >>> >>> Please provide irw output from a button press or two. Are you getting >>> true repeats, or are your signals coming through as new presses every >>> time? > >> Bottom-post it is. :) > > Thank you, much appreciated. > >> I don't have a irw capture on file, but I remember when I was testing it that they were registering as unique presses, with a new index value each time. I can verify this later if you like. > > Hm, need clarification... "new index value" each time... If they were > registering as unique keypresses, the index value should always be 00. > If they were incrementing, then they're repeats. > I could be misremembering, I'll check tonight and post results. Thanks. Seth -- Seth Galitzer The beatings will continue until morale has improved. |
From: Seth G. <set...@gm...> - 2011-01-11 00:14:09
|
On Mon, Jan 10, 2011 at 3:32 PM, Seth Galitzer <set...@gm...> wrote: > On 01/10/2011 03:31 PM, Jarod Wilson wrote: >> >> On Jan 10, 2011, at 4:13 PM, Seth Galitzer wrote: >> >>> On 01/10/2011 02:33 PM, Jarod Wilson wrote: >>>> >>>> On Jan 10, 2011, at 3:06 PM, Seth Galitzer wrote: >> >> ... >>>>>> >>>>>> ...This thread is about >>>>>> mceusb hardware, and from the list archive, it looks like you're >>>>>> talking about a hauppauge remote with a serial receiver. Its not >>>>>> expected that you'd have either of those /sys paths with lirc_serial, >>>>>> your issue is something else entirely. >>>>>> >>>>>> From your original posting though, it sounds like everything is >>>>>> actually behaving exactly as expected for a raw IR hardware receiver, >>>>>> you just need to do some repeat filtering, either via repeat = x >>>>>> lines in .lircrc, or with 'suppress_repeat y' in lircd.conf. >> >> ... >>>>> >>>>> Fair enough. I had no idea the implementation was so wildly different >>>>> for every device. It seemed reasonable to me that if it was a core issue >>>>> then it would be device-agnostic. Yes I have tried repeat filtering, as you >>>>> said, still no luck. I'll stop hijacking this thread now. >>>> >>>> Bottom-posting is also highly preferred on this list, though not (yet) >>>> officially mandated. :) >>>> >>>> Please provide irw output from a button press or two. Are you getting >>>> true repeats, or are your signals coming through as new presses every >>>> time? >> >>> Bottom-post it is. :) >> >> Thank you, much appreciated. >> >>> I don't have a irw capture on file, but I remember when I was testing it >>> that they were registering as unique presses, with a new index value each >>> time. I can verify this later if you like. >> >> Hm, need clarification... "new index value" each time... If they were >> registering as unique keypresses, the index value should always be 00. >> If they were incrementing, then they're repeats. >> > > I could be misremembering, I'll check tonight and post results. > > Thanks. > Seth Here's the output from irw. This is using what I would call "normal" finger pressure to push the buttons. 0000000000001794 00 Up Hauppauge_350 0000000000001794 00 Up_UP Hauppauge_350 0000000000001794 00 Up Hauppauge_350 0000000000001794 00 Up_UP Hauppauge_350 0000000000001795 00 Down Hauppauge_350 0000000000001795 00 Down_UP Hauppauge_350 0000000000001795 00 Down Hauppauge_350 0000000000001795 00 Down_UP Hauppauge_350 0000000000001796 00 Left Hauppauge_350 0000000000001796 00 Left_UP Hauppauge_350 0000000000001797 00 Right Hauppauge_350 0000000000001797 00 Right_UP Hauppauge_350 00000000000017a5 00 OK Hauppauge_350 00000000000017a5 00 OK_UP Hauppauge_350 00000000000017a5 00 OK Hauppauge_350 00000000000017a5 00 OK_UP Hauppauge_350 Left and Right only appeared to fire once in this run, which is most likely because I pushed them ever so much more briefly. If I use this very light touch, which is not easy to duplicate, then the signals are not repeated. Thanks. Seth -- The beatings will continue until morale has improved. |
From: Douglas P. <Dou...@pe...> - 2011-01-11 05:19:07
|
Hi Mario, Thanks, that fixed the issue. Cheers Douglas. On 11/01/2011 8:16 a.m., Mario Limonciello wrote: > Yeah, there's a fix already in the packaging. Planning on uploading > it when I upload a 0.9 snapshot soon to natty. Here's the updated > init script you'll need: > > http://bazaar.launchpad.net/~mythbuntu-dev/lirc/ubuntu/annotate/head:/debian/lirc.init.d > <http://bazaar.launchpad.net/%7Emythbuntu-dev/lirc/ubuntu/annotate/head:/debian/lirc.init.d> > > On Mon, Jan 10, 2011 at 13:14, Jarod Wilson <ja...@wi... > <mailto:ja...@wi...>> wrote: > > On Jan 10, 2011, at 4:15 AM, Douglas Pearless wrote: > > > I have just upgraded the kernel on my mythbuntu box to 2.6.37 to > solve a > > problem and while that is fixed, I now get two key presses for each > > arrow key I pressed. > > > > Anyone else struck this? > > Check /sys/class/rc/rc0/protocols and I bet you'll see that both > in-kernel > and userspace (lirc) decode are enabled. The Ubuntu lirc > initscript was > disabling in-kernel decode previously via > /sys/devices/virtual/rc/... but > those bits got moved. Mario is aware of the problem and I believe was > planning to push an updated package for Ubuntu. > > -- > Jarod Wilson > ja...@wi... <mailto:ja...@wi...> > > > > > > > -- > Mario Limonciello > su...@gm... <mailto:su...@gm...> > > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of any company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl |