Problems with lircd 488

On 22 Feb 2006 11:47:59 -0800, Wescotte staggered into the Black Sun and said:

Hm. Which lirc* module are you using? If you have the wrong lirc* module modprobed, then you'll certainly see weird things happen. It looks like this thing connects to the serial port, so you'd use setserial to make sure the speed was right, then load lircserial . I think.

Bad serial port settings? See what "setserial -adev-ttyS0" gives you, I guess.

This is strange. So far, my experiments with lircd and an ATI Remote Wonder II remote have been pretty good--it just worked, as soon as I built the package with option "--with-driver=all" (sigh.) So I don't have a whole lot of lirc troubleshooting experience to fall back on.

All I really know is what I said above.

You typically do something like this:

(modprobe appropriate lirc* module)etc-init.d-lircd stop (just in case!) irrecord -ddev-lircX my-remote

irrecord now tries to read devicedev-lircX using the available lirc modules, and it will write a configuration file in the current dir called my-remote or "my-remote.conf" if my-remote exists already. You type in names for the buttons before pressing them, it asks "Enter the name of the next button:" and you type it in and press Enter, then you hold down that button. Repeat until all buttons are pressed. When done, hit Enter twice, or just wait for 10 seconds without pushing any buttons and it'll exit. At least that's how it works in lirc-0.8.0pre3. HTH anyway,

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL