## Fedora README ### Upstream release 0.9.1a The changes that broke the update for 0.9.0 are now in upstream. There are no functional fedora-specific patches in this release, just some bugfixes. #### Running another instance. Sometimes another lircd instance is required to handle some other input device. This could be done by creating a new service definition in /etc/systemd/system. In my case I have an extra instance handling ir output to the transciever. This is accomplished with a file /etc/systemd/system/lirc-tx: ---------------- [Unit] Description=LIRC Infrared Signal Decoder After=network.target [Service] Type=simple ExecStart=/usr/sbin/lircd --driver=iguanaIR \ --device=/var/run/iguanaIR/0 \ --output=/var/run/lirc/lircd-tx \ --pidfile=/run/lirc/dont-use-lircd-tx.pid \ --nodaemon \ --allow-simulate [Install] WantedBy=multi-user.target ----------------------- This defines a new service which can be started using 'systemctl start lirc-tx' etc. It's essential that each service has an unique output socket. You should probably also think twice before running two instances with the same input device. ## Troubleshooting Getting lircd logs from last boot cycle: ``` # journalctl -b /usr/sbin/lircd ``` If lircd fails to start or dies after restart, first check logs for errors: ``` # journalctl -f & # systemctl restart lircd.service ``` You could also run lircd in foreground after stopping service, using the driver and device defined in lirc_options.conf: ``` # systemctl stop lircd.service # /usr/sbin/lircd --nodaemon ``` Sometimes kernel complains about multiple clients trying to access the same device. In this case you need to blacklist some kernel module to make the kernel device available for lircd. One example is my RF remote using the atilibusb driver. This needs to blacklist the built_in ati_remote module. This is is done by creating the file /etc/modprobe.conf.d/blacklist-ati-remote.conf as: ``` ## Block built-in handling of ati-remote (use lircd instead). blacklist ati_remote ```