From: Steve F. <sf...@ih...> - 2009-02-23 05:55:09
|
Hi all. Hope somebody here can help! I've had trouble getting the remote working using the Ubuntu (kernel 2.6.27, 32-bit i686) lirc package, so I installed lirc from the latest source, and the symptoms are unchanged. irw shows nothing at all when I press buttons. The light on the receiver is blinking normally. Doing 'cat /dev/lirc0' while pressing buttons on the remote yields good output. I installed with: ./configure --enable-debug --with-driver=streamzap && make && sudo make install Output from lircd -D255 -n -d /dev/lirc0: lircd: http://pastebin.com/f477b30b9 Output from modes with an initial press of the 'OK' button, then repeating 'OK': http://pastebin.com/f175fc794 My unchanged /etc/lircd.conf: http://pastebin.com/f6eb4a398 I'm happy to provide any more information anyone needs, and I appreciate any suggestions you could offer. I've looked around and tried others' Streamzap configs, but none have worked. Thanks! Steve |
From: <li...@ba...> - 2009-02-23 20:00:13
|
Hi! Steve Freitas "sf...@ih..." wrote: [...] > I've had trouble getting the remote working using the Ubuntu (kernel > 2.6.27, 32-bit i686) lirc package, so I installed lirc from the latest [...] > Output from lircd -D255 -n -d /dev/lirc0: lircd: > http://pastebin.com/f477b30b9 The timeout in line 173 is the problem. But currently I don't have any idea what causes it. Can you try again if it still happens with todays CVS version? Christoph |
From: Steve F. <sf...@ih...> - 2009-02-23 22:48:05
|
Hi Christoph, thanks for your reply! Just grabbed today's CVS and it only slightly works. The first 'OK' came through irw, but nothing after that. Output from lircd -D255 -n -d /dev/lirc0: http://pastebin.com/f40af106e ('OK', then a bunch of random presses) Output from mode2 with a single 'OK', then a pause, then auto-repeated 'OK' presses: http://pastebin.com/f6f49db1d After these runs, I started lircd and irw again, but pressing 'OK' once yielded nothing at all. That output, if you're interested, is here: http://pastebin.com/f333e2294 To my untrained eyes, it looks pretty much like my first attempt from yesterday. Note that I didn't reboot between lirc builds. After building and installing from CVS, I just did "rmmod lirc_streamzap lirc_dev" and modprobed them again. (By the way, let me know if you need to continue seeing mode2 dumps.) Thanks for your help, I'm ready to try anything you suggest. Steve On Mon, 2009-02-23 at 20:59 +0100, Christoph Bartelmus wrote: > Hi! > > Steve Freitas "sf...@ih..." wrote: > [...] > > I've had trouble getting the remote working using the Ubuntu (kernel > > 2.6.27, 32-bit i686) lirc package, so I installed lirc from the latest > [...] > > Output from lircd -D255 -n -d /dev/lirc0: lircd: > > http://pastebin.com/f477b30b9 > > The timeout in line 173 is the problem. But currently I don't have any > idea what causes it. Can you try again if it still happens with todays CVS > version? > > Christoph > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H |
From: Steve F. <sf...@ih...> - 2009-02-23 23:11:34
|
On Mon, 2009-02-23 at 14:48 -0800, Steve Freitas wrote: > Note that I didn't reboot between lirc builds. After building and installing from CVS, > I just did "rmmod lirc_streamzap lirc_dev" and modprobed them again. By the way, I rebooted and no change. Looks like that initial 'OK' reading was a fluke, I can't get it to recognize anything at all now. Steve |
From: <li...@ba...> - 2009-02-24 07:36:00
|
Hi! Steve Freitas "sf...@ih..." wrote: > On Mon, 2009-02-23 at 14:48 -0800, Steve Freitas wrote: >> Note that I didn't reboot between lirc builds. After building and >> installing from CVS, I just did "rmmod lirc_streamzap lirc_dev" and >> modprobed them again. > By the way, I rebooted and no change. Looks like that initial 'OK' > reading was a fluke, I can't get it to recognize anything at all now. No idea. The input signal is corrupt. It's simply too short. Try again with fresh batteries. Christoph |
From: Steve F. <sf...@ih...> - 2009-03-02 01:06:12
|
On Tue, 2009-02-24 at 08:35 +0100, Christoph Bartelmus wrote: > No idea. The input signal is corrupt. It's simply too short. > Try again with fresh batteries. That did the trick! Thanks again for your help. Steve |