R. G. Newbury wrote:
> Hal wrote:
>> What alternatives have people used? I'm about ready to stop beating
>> my head against the wall with lirc.
>> Wireless keyboard, of course, but that's pretty bulky and may not
>> have enough range.
>> Buy a capture card that comes with it's own remote. Then I have yet
>> another remote kicking around, plus I still probalby have problems
>> making it work with linux.
>> Any better solutions?
> Well the lirc documentation sucks, but it you have a reasonable remote
> that is supported then the error is at your side of the keyboard. Not
> that you are necessarily doing something BAD, you are just not doing
> something RIGHT.
> What is your reciever and what is your remote?
> Have you downloaded the lirc tarball and run the little configurator
> program to select your hardware?
> Have you tried just doing a ./configure --all instead?
> Does it then make, and make install?
> At this point you have the back end stuff prepared ready for
> If you got to here, then it is a matter of modprobing the bits into
> place. modprobe lirc_i2c, modprobe lirc_dev and modprobe
> Or put 'alias char_major_61 lirc_your_driver_here' in your
> modprobe.conf and reboot.
> The back end hardware should now work if lircd is started
> YOu should have a /dev/lirc....if not fix your udev rules.
> You may need to do a symlink from /dev/lirc0
> At this point, you need to run lircd from a console..(It should be put
> into a script in init.d to start automatically, later).
> Run mode2 and your remote's kepresses should be visible.
> THERE the hardware layer works.
> Now, build/ borrow an lircd.conf file, or use irw to capture the
> keypresses (or is it irrrecord...going from memor). The key codes are
> matched up with the key names in this file. The key nameds are used to
> select actions to perform in the lircrc file. The key names must match
> in both....ie PageUp in one cannot be Page+ in the other.
> Build your lircrc file..Lots around for things like mythtv.
> That's it.
Oh, I don't doubt that the problem is correctable. I wish I could at
least get an error message to chase down.
The receiver is home-brew, TSOP-1738 based. The lirc software was
installed using Synaptec apt-get on PCLinuxOS. Software startup looks like
ln -s /dev/lirc/0 /dev/lirc0
setserial /dev/ttyS0 uart none
modprobe lirc_serial irq=4 io=0x3f8
lircd -d /dev/lirc0 /etc/lircd.conf --nodaemon
No errors or warnings in the console or /var/log/messages.
mode2 -d /dev/lirc0
in a different window. Nothing happens.
Everything is being done as root at this point.
I can see that the hardware is getting power, and when I point a remote
at it and press buttons, I can see the voltage dip at the DCD input.
Using statserial instead of the lirc software, I can see that the DCD
bit changes state. It's almost certainly some configuration issue in the
software. I've been over and over the docs, but I can't see anything
wrong. In the absence of error messages, I've hit a wall.