No matter what lircd.conf I use, irw does not spit out anything.


On Fri, Dec 31, 2010 at 6:19 PM, Jarod Wilson <jarod@wilsonet.com> wrote:
On Thu, Dec 30, 2010 at 2:41 PM, Lorne Kligerman <lorne@kligerman.com> wrote:
> Some good news.  For reasons I can't explain, after another reboot the
> /dev/lirc0 device exists, and I can get signal info through mode2.
> The problem now is when using irrecord, the initial step to press a bunch of
> buttons produces dots, but then when asked to press individual buttons, I
> continously get:
> Sorry, something went wrong.
> Try again.
> Any idea?  I'm use a Logitech Harmony 880 remote.

None. irrecord is still largely a mystery to me. :) I rarely use it,
there's almost always a remote config already in existence for remotes
I've got, and certainly for a Harmony remote. Just program it as the
appropriate windows media center remote and use the stock mceusb
config if you don't want to hassle with irrecord. (I'll get familiar
with it some day, but not likely anytime soon, too many other things
going on right now).


> On Wed, Dec 22, 2010 at 11:46 AM, Jarod Wilson <jarod@wilsonet.com> wrote:
>>
>> On Dec 22, 2010, at 11:04 AM, Lorne Kligerman wrote:
>>
>> > Yes to both.
>>
>> Please keep replies on the list.
>>
>> > lorne@tv:~$ lsusb
>> > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> > Bus 006 Device 003: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote
>> > Controller
>> > Bus 006 Device 002: ID 045e:006d Microsoft Corp. eHome Remote Control
>> > Keyboard k
>> >            eys
>> > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> > Bus 005 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop
>> > Laser
>> > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> ...
>> > lorne@tv:~$ lsmod |grep mce
>> > mceusb                 12846  0
>> > rc_rc6_mce              1438  0
>> > edac_mce_amd            9387  0
>> > ir_core                16906  11
>> > mceusb,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,rc_rc6_mce,rc_imon_pad,ir_rc5_decoder,imon,ir_nec_decoder
>> > lorne@tv:~$
>>
>>
>> And /dev/lirc0 really is there, correct?
>>
>> What sort of dmesg output do you have? (Please pastebin all output
>> from dmesg following a fresh boot).
>>
>>
>> > On Wed, Dec 22, 2010 at 10:52 AM, Jarod Wilson <jarod@wilsonet.com>
>> > wrote:
>> > On Dec 20, 2010, at 7:13 PM, Lorne Kligerman wrote:
>> >
>> > > This is what I get:
>> > >
>> > > lorne@tv:/dev$ sudo mode2 -d /dev/lirc0
>> > > mode2: could not get hardware features
>> > > mode2: this device driver does not support the LIRC ioctl interface
>> > > mode2: major number of /dev/lirc0 is 250
>> > > mode2: LIRC major number is 61
>> > > mode2: check if /dev/lirc0 is a LIRC device
>> > > lorne@tv:/dev$
>> >
>> > That's... Not so good. Is the hardware still showing up in lsusb
>> > output? And is this lirc_mceusb or the mceusb driver from your
>> > distro's kernel?
>> >
>> >
>> > > On Mon, Dec 20, 2010 at 5:34 PM, Jarod Wilson <jarod@wilsonet.com>
>> > > wrote:
>> > > On Dec 20, 2010, at 4:54 PM, Lorne Kligerman wrote:
>> > >
>> > > > Ah ok, makes sense.  Can you elaborate a bit on what you mean and
>> > > > how to use just the mceusb config?
>> > >
>> > > Use remotes/mceusb/lircd.conf.mceusb for lircd.conf, and don't use the
>> > > devinput driver, use the 'default' driver (or specify none, since its
>> > > the default), with device /dev/lirc0.
>> > >
>> > >
>> > > > On Mon, Dec 20, 2010 at 4:52 PM, Jarod Wilson <jarod@wilsonet.com>
>> > > > wrote:
>> > > > On Dec 20, 2010, at 4:48 PM, Lorne Kligerman wrote:
>> > > >
>> > > > > I killed inputlirc, but am unable to have mode2 open any of the
>> > > > > inputs.
>> > > > >
>> > > > > lorne@tv:~$ sudo mode2 -H devinput -d /dev/input/event4
>> > > > > mode2: initializing '/dev/input/event4'
>> > > > > This program does not work for this hardware yet
>> > > > > lorne@tv:~$
>> > > > >
>> > > > > lorne@tv:~$ mode2 -H devinput -d /dev/input/event4
>> > > > > mode2: initializing '/dev/input/event4'
>> > > > > mode2: unable to open '/dev/input/event4'
>> > > > > lorne@tv:~$
>> > > > >
>> > > > > How do I get mode2, and likely the other commands, to work with
>> > > > > the devinput driver?
>> > > >
>> > > > You don't. You use mode2 against /dev/lirc0.
>> > > >
>> > > > I think I see now why you're not getting any data though. You're
>> > > > trying
>> > > > to use the devinput config rather than the mceusb config, but the
>> > > > ubuntu initscripts disable in-kernel decoding, which means you'll
>> > > > never
>> > > > get any input layer keycodes passed along. I'd advise just using the
>> > > > normal mceusb config.
>> > > >
>> > > >
>> > > > > On Mon, Dec 20, 2010 at 3:47 PM, Jarod Wilson <jarod@wilsonet.com>
>> > > > > wrote:
>> > > > > On Dec 15, 2010, at 9:35 AM, lklig wrote:
>> > > > >
>> > > > > >
>> > > > > > Installed lirc, selected Windows Media Centre
>> > > > > > Transceivers/Remotes
>> > > > > >
>> > > > > > lorne@tv:~$ uname -a
>> > > > > > Linux tv 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36
>> > > > > > UTC 2010
>> > > > > > x86_64 GNU/Linux
>> > > > > > lorne@tv:~$
>> > > > > >
>> > > > > > IR receiver is an HP Media Center
>> > > > > > lorne@tv:/dev$ lsusb
>> > > > > > Bus 006 Device 003: ID 045e:006d Microsoft Corp. eHome Remote
>> > > > > > Control
>> > > > > > Keyboard keys
>> > > > > >
>> > > > > > Remote is a Logitech Harmony 880
>> > > > > >
>> > > > > > lorne@tv:/etc/lirc$ ps -ef |grep lirc
>> > > > > > nobody 1223 1 0 19:58 ? 00:00:00 /usr/sbin/inputlircd -m0 -g -c
>> > > > > > -d/var/run/lirc/lircd /dev/input/event0 /dev/input/event1
>> > > > > > /dev/input/event2
>> > > > > > root 2552 1 0 20:11 ? 00:00:00 /usr/sbin/lircd
>> > > > > > --output=/var/run/lirc/lircd
>> > > > > > --device=/dev/lirc0
>> > > > > ...
>> > > > > > When I run irw, the red light on the receiver flash, but no
>> > > > > > commands appear
>> > > > > > on the screen.
>> > > > >
>> > > > > Why do you have both inputlircd and lircd running?
>> > > > >
>> > > > > Try running mode2, see if it reports anything. But first, please
>> > > > > get
>> > > > > inputlircd out of the way, just to be sure its not interfering.
>> > > > >
>> > > > > --
>> > > > > Jarod Wilson
>> > > > > jarod@wilsonet.com
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > Jarod Wilson
>> > > > jarod@wilsonet.com
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > > --
>> > > Jarod Wilson
>> > > jarod@wilsonet.com
>> > >
>> > >
>> > >
>> > >
>> >
>> > --
>> > Jarod Wilson
>> > jarod@wilsonet.com
>> >
>> >
>> >
>> >
>>
>> --
>> Jarod Wilson
>> jarod@wilsonet.com
>>
>>
>>
>
>



--
Jarod Wilson
jarod@wilsonet.com