Re: Upgrade from lirc0.7.1. to lirc0.8.1 has caused breakage (USB-UIRT)

[Graeme M. <gra...@gm...>]

So you say the lircd.conf generated for 0.7.1 should work for 0.8.1? If
that's the case, something else must have gone wrong, cos my lircd.conf was
perfect.

I may have overlooked something in the setup, because it was last June when
I setup 0.7.1 and I never wrote anything down. It took me a long time to set
it up, and it was hair-pullingly frustrating.

The unit tends to go to sleep overnight when it's not getting used for a few
hours. I thought it may have been a problem with the motherboard, but it
can't be that as I've swapped motherboards and the problem persists. I was
thinking maybe 0.8.1 would fix this, and if not, if sending worked I could
set up a cron job to send dummy codes to keep the device alive.

Anyway, if you're saying the old lircd.conf should work, then I don't need
irrecord to work. However when I start up lircd, nothing happens.
IIRC I should be able to run lircd, then irw, then send codes and see them
pop up on the terminal. Nothing happens when I send codes. The unit blinks,
but nothing appears on the screen.

Do I need to tell lircd where lircd.conf is? Currently, it is in /etc, where
it always worked before.

You asked me to elaborate on my situation, but I'm not really sure what you
want.

Do you know of any detailed guides on setting lirc up? The info on
lirc.orgisn't that good imo.


-- 
No, no, you see the rules of language are purely arbitrary stodgy
ivory-tower crap we doesn't have to worried aboard because everytime history
on you rebendible sausage mountain.