![]() ![]() So, change the entry in /etc/lirc/hardward. Lrwxrwxrwx 1 root root 19 08:57 /dev/lircd -> /var/run/lirc/lircdĬrw-rw- 1 root root 61, 0 08:57 0I saw that there was indeed a device created, just not where I had expected it to be. In this configuration, each button the remote uses the keyboard interface and each key is translated to a key press. ![]() Service lirc restartThis should have recreated the device /dev/lirc0. a) Use the default driver (eHome Infrared Receiver) If you only use MCE, and you do not want to change the functionality of any of the buttons, then you can use the default driver and no other setup is required. ,Next, rebuild modules using,ĭpkg-reconfigure lirc-modules-sourceRestart lirc: * Formosa Industrial Computing AIM IR605/A */ * Formosa Industrial Computing / Beanbag Emulation Device */ * Formosa aim / Trust MCE Infrared Receiver */ * Formosa21 / eHome Infrared Receiver */ Grep -i formosa /usr/src/lirc-0.8.6/drivers/lirc_mceusb/lirc_mceusb.c In Windows 10 it is starting only if the user, an application or another service starts it. So is the device known by the modules? To answer that question, I have to install lirc-modules-source:Īpt-get install lirc-modules-sourceNow look in /usr/src/lirc-0.8.6/drivers/lirc_mceusb/lirc_mceusb.c for your receiver, EHome Infrared Receiver (USBCIR) is a kernel device driver. So, why does lirc not recognise it? Are the modules being loaded? IdVendor 0x147a Formosa Industrial Computing, Inc. But no such device exists! However, checking with lsusb the receiver is being recognised:īus 004 Device 002: ID 147a : e03e Formosa Industrial Computing, Inc.īDeviceClass 0 (Defined at Interface level) ![]() The default remote device was /dev/lirc0, see /etc/lirc/nf. usbhid: v2.6:USB HID core driverTo configure lirc I used the command,ĭpkg-reconfigure lircSelecting Windows Media Center Transceivers/Remotes (all), and transmitter, none. usbcore: registered new interface driver usbhid Getting the remote to workEven though dmesg reported that I had a infrared receiver, lirc failed to recognise it when testing with irw. This device is already supported by the in-kernel mceusb driver.So hopefully you are much luckier than I was in setting this up! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |