I think you are saying that REMOTE_DEVICE should be set to one of these: $ ls /dev/input/by-id/usb-Logitech_USB_Receiver-* /dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd@ /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse@ /dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse@ /dev/input/by-id/usb-Logitech_USB_Receiver-if01-mouse@ /dev/input/by-id/usb-Logitech_USB_Receiver-mouse@
The only one that made sense to me was the kbd one. Here is my hardware.conf file (skipping empty entries): $ grep '="[A-Za-z0-9]' hardware.conf REMOTE="ATI/NVidia/X10 RF Remote (ati_remote)" REMOTE_MODULES="ati_remote" REMOTE_DRIVER="devinput" REMOTE_LIRCD_CONF="atiusb/lircd.conf.atiusb" TRANSMITTER="None" START_LIRCD="true" FORCE_NONINTERACTIVE_RECONFIGURATION="false" cp /usr/share/lirc/remotes/devinput/lircd.conf.devinput /etc/lirc/lircd.conf service lirc restart I still get nothing through irw. Here is how lircd is getting run: $ ps ax | grep -i lirc 7360 ? Ss 0:00 /usr/sbin/lircd --output=/var/run/lirc/lircd --driver=devinput --device=/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd This is made harder because there is no documentation about what the possible --driver values are! I'm running out of patience for this. lirc had bad gaps in documentation and is very hard to debug. Not fun. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
