I posted this on [i]Usage/How To[/i], but had no reaction. So I'll try here:

I just installed R5D1, and everything looks great. The only thing I cannot get working is irblaster. I use a homebrew irblaster from iguana.net on the first com port, with a [i]one-for-all[/i] universal remote. I captured the codes for my satellite box and for an unused vcr funtion on the remote that I plan to use to control mythtv. [b]channel_change.sh[/b] and [b]irw[/b] works fine, but nothing happens in mythtv.
I truncated [b]/home/mythtv/.mythtv/lircrc[/b] to the following to make sure nothing in it is corrupt:[code]begin
prog = mythtv
remote = VCR
button = up
config = Up
end

begin
prog = mythtv
remote = VCR
button = down
config = Down
end

begin
prog = mythtv
remote = VCR
button = left
config = Left
end

begin
prog = mythtv
remote = VCR
button = right
config = Right
end[/code]all of which matches irblasterd.conf exactly.

When I try [code]ircat mythtv[/code]or [code]irexec -n mythtv[/code]I get:[code]mythtv: Connection refused
mythtv: Cannot connect to socket[/code]

I figured out that I can get either the remote control in myth working or the channel_change.sh, but not both at the same time.
I do this by either enabling or disabling the main lirc device in [b]/etc/lirc/hardware.conf[/b] with the following:[code]DRIVER="default"[/code]or[code]DRIVER="null"[/code]When it is set to [i]default[/i], the remote works in mythtv, when it is [i]null[/i], the irblaster works.

The irblaster works once upon startup and then promplty crashes when channel_change.sh is executed again. The only relevant error I can find in the logs is in daemon.log:[code]could not connect to device /dev/irblasterd [/code]
If I restart lirc and irblaster then they stay up, but mythtv doesn't catch the keypresses from the remote. mode2, irw, ircat etc. all works as expected from then on.

I tried to recompile lirc from the sources included and also from lirc-0.8.0, but that did not help. I'm not sure whether I did the recopile correctly as I can't see any different modules being used in daemon.log

Any help will be greatly appreciated.

I got it working by killing lirc in /etc/init.d and symlinking /dev/lircd to /dev/irblasterd. If anyone is interested in the details let me know I will post the whole thing.

Question: What command do you use to stop (temporarily) LIRC?

I have found the following command, but it doesn't seem to work. It gives me a message that it doesnt understand the "service" command. I'm a totally inexperienced user, so I apologize for the easy question.

/sbin/service lircd stop

Try: [code]/etc/init.d/lirc stop[/code]

[quote="tjc"]Try: [code]/etc/init.d/lirc stop[/code][/quote]

That works perfectly. Many thanks.

No, I removed it from the rc's completely with: [code]update-rc.d lirc remove[/code]only irblaster starts and loads lirc-serial.

After upgrading to R5E50, I had to redo the above procedure.

Here are the steps I followed:

1. Backup system, and copy irblaster.conf, channel_change.sh and lircrc to /myth/backup/.
2. Auto-upgrade to R5E50.
3. Choose 6-in-1 (no.34 on R5E50) as remote in lirc-reconfig.sh.
4. Choose my com port and select "I'll install my own" (no.13 in R5E50) in irblaster.sh
5. Restore system, and restore irblaster.conf, channel_change.sh and lircrc.
6. Kill lirc with:
   Code:
   update-rc.d -f lirc remove
7. Symlink /dev/lircd to /dev/irblasterd

For some reason I couldn't get the symlink to stick past a reboot, I'm no linux expert, so I just added: to the irblaster init script in /etc/init.d just after it creates the irblasterd device.

Please do comment on what you think of my procedure.

Douw.