READNE.fedora: add Troubleshooting

README.fedora

@@ -32,15 +32,15 @@ activation. This should fix the problems at startup when clients can't
 connect to /var/run/lircd because the lircd service is yet not started.
 
 To start the lircd service using socket activation:
-
+```
     # systemctl enable lircd.socket
     # systemctl start lircd.socket
-
+```
 The lircmd is started the usual way:
-
+```
     # systemctl enable lircmd.service
     # systemctl start lircmd.service
-
+```
 #### Running another instance.
 
 Sometimes another lircd instance is required to handle some other input
@@ -73,9 +73,45 @@ This defines a new service which can be started using
 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:
+```
+    # systemctl stop lircd.service
+    # bash
+    # source /etc/systconfig/lirc
+    # /usr/sbin/lircd $LIRCD_OPTIONS --driver $LIRC_DRIVER \
+    > --device $LIRC_DEVICE  --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
+```
+
+
+
+
+
 
 
 
 
 
-http://stackoverflow.com/questions/11939255/writing-to-dev-uinput-on-ubuntu-12-04