no udev rules installed

Yes you are right. I'm using vdr and lircd dies when vdr connects to it, since lircd doesn't find /dev/lirc.

Would it be trivial to include the udev rules from the LIRC tarball? I had asked about hotplugging on the LIRC mailing list and attached is the response I got. Hopefully it won't be quite so involved to get it working.

Under feisty, I see the device nodes appearing in /dev. What isn't working, so that I can better understand how to recreate the problem?
Thanks!

Actually, I can't remember what the problem was :) I have an Antec case with a VFD which needs lirc_imon loaded, and a serial receiver which needs lirc_serial. The serial one needs to be loaded first, otherwise the client (VDR) tries to use imon and things fail. But, all this can be done with the /etc/lirc/hardware.conf, by changing MODULES="lirc_serial lirc_imon", then serial is loaded first and things work.

I can't see the need for udev rules anymore, maybe someone else can?

On 4/4/07, Kees Cook <email address hidden> wrote:
> Under feisty, I see the device nodes appearing in /dev. What isn't working, so that I can better understand how to recreate the problem?

The issue is with hotplugging. At least at the time, unplugging and plugging in my remote without rebooting didn't work. Since LIRC is so multi-leveled, I'd have to restart all the programs between lircd and my desktop media programs to get it working again.

I haven't tried on Feisty; are you saying hotplugging works?

Ah-ha! Thank you. No, hotplugging is clearly not working; I just tried this with a USB receiver. I will try the udev patch and see if that helps.

Okay. I see two bugs here:

1) device load order (serial vs imon). This is fixable with the hardware.conf load order, and the udev rules don't help this, afaict. This is the "original bug". As such, I'm closing this bug report. If some solution becomes known, please feel free to reopen it.

2) lirc totally does not handle hotplugging. when I unplug a USB receiver, the entire stack shuts down. :( So, this should be a new bug, and it would be a "Wishlist" feature request, since it doesn't seem that there is already a way for lircd to handle these situations.

Thanks to everyone who looked at this! I think I understand the lirc problems much better now. :)