2009-03-16, 23:59
lens Wrote:Any ideas?
yes, it's a matter of timing. At the time lirc is called during startup, either: one/more modules are not loaded yet or the scripts in etc/init.d are not in the correct (or best possible) order.
but don't ask me how exactly to solve it - other than dirty solutions like re-calling a modprobe or lirc-start script from rc.local...