From: Alec L. <lea...@gm...> - 2016-01-15 16:30:08
|
On 15/01/16 15:47, mai...@wo... wrote: > And ps -ef shows is still a running lircd process. As they say: I cannot parse this... there is no lircd process, right? > No, even after stoping both lircd.socket and lircd.service after having entered the "failed" state, unloading results in FATAL: Module lirc_rpi is in use. And ps -ef shows is still a running lircd process. There is no running process before I start it with "lircd". In that case I'd say that this is about the lirc_rpi module. If no process is accessing /dev/lirc0 this shouldn't happen. If there was a clue, it should be in dmesg. But since it's not, perhaps you should report this against lirc_rpi. In short,the module doesn't seem to work correctly but I have no clue as to why. Cheers! --alec |