2020-01-17, 21:11
I think you should go and read our piracy policy (wiki) and also our VPN policy (wiki) before going any further...
(2020-01-17, 21:09)DarrenHill Wrote: Those sources of media violate our piracy policy (wiki) and access to them is against our forum rules (wiki) and unsupported here.
(2020-01-17, 21:09)black_eagle Wrote: I've got 18.04 and it handles my remotes perfectly with LIRC. In fact, I have an option of 3 different remotes that I can pick up and use to control Kodi. Finding in dmesg where your ir receiver is identified would be a good starting point.Thanks, I'll have a have a play tomorrow. I did look at a log but did not see anything referring to infrared rx where the USB port info appeared. I will look closer tomorrow.
Look for something similar tooxml:[43197.321984] usb 6-2: Product: eHome Infrared Transceiver
[43197.321989] usb 6-2: Manufacturer: Formosa21 [43197.321993] usb 6-2: SerialNumber: FM000623
[43197.334953] Registered IR keymap rc-rc6-mce [43197.335183] input: Media Center Ed. eHome Infrared Remote Transceiver (147a:e016) as /devices/pci0000:00/0000:00:12.0/usb6/6-2/6-2:1.0/rc/rc1/input13
[43197.335462] rc1: Media Center Ed. eHome Infrared Remote Transceiver (147a:e016) as /devices/pci0000:00/0000:00:12.0/usb6/6-2/6-2:1.0/rc/rc1
[43197.335906] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input14
[43197.336550] rc rc1: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[43197.509161] mceusb 6-2:1.0: Registered Formosa21 eHome Infrared Transceiver with mce emulator interface version 1
[43197.509175] mceusb 6-2:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)
Reboot PC /unplug - plug in receiver and then either go through dmesg by handdmesg|less
or try and find it with grepdmesg|grep -C5 "IR"
(2020-01-17, 21:37)hjgtiger Wrote:Ubuntu can 'see' the IR Rx - Extract:-(2020-01-17, 21:09)black_eagle Wrote: I've got 18.04 and it handles my remotes perfectly with LIRC. In fact, I have an option of 3 different remotes that I can pick up and use to control Kodi. Finding in dmesg where your ir receiver is identified would be a good starting point.Thanks, I'll have a have a play tomorrow. I did look at a log but did not see anything referring to infrared rx where the USB port info appeared. I will look closer tomorrow.
Look for something similar tooxml:[43197.321984] usb 6-2: Product: eHome Infrared Transceiver
[43197.321989] usb 6-2: Manufacturer: Formosa21 [43197.321993] usb 6-2: SerialNumber: FM000623
[43197.334953] Registered IR keymap rc-rc6-mce [43197.335183] input: Media Center Ed. eHome Infrared Remote Transceiver (147a:e016) as /devices/pci0000:00/0000:00:12.0/usb6/6-2/6-2:1.0/rc/rc1/input13
[43197.335462] rc1: Media Center Ed. eHome Infrared Remote Transceiver (147a:e016) as /devices/pci0000:00/0000:00:12.0/usb6/6-2/6-2:1.0/rc/rc1
[43197.335906] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input14
[43197.336550] rc rc1: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[43197.509161] mceusb 6-2:1.0: Registered Formosa21 eHome Infrared Transceiver with mce emulator interface version 1
[43197.509175] mceusb 6-2:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)
Reboot PC /unplug - plug in receiver and then either go through dmesg by handdmesg|less
or try and find it with grepdmesg|grep -C5 "IR"
(2020-01-18, 09:10)black_eagle Wrote: LibreElec uses its own version of LIRC I think plus it may well use ir-keytable. Can you post the whole bit of the log where it detects the IR device, so I can see which inputs get assigned to it and which driver it's using ?This seems to be the part pertaining to the IR Rx
(2020-01-18, 12:22)hjgtiger Wrote:Still fiddling. Now I've tried Linux Mint 19 as the OS, but still getting same result. Also I perpetually get an error '/sys/class/rc/ cannot find directory or file' error when I try to run ir-keytable (to see if Mint sees my ir Rx . I can install ir-keytable ok.(2020-01-18, 09:10)black_eagle Wrote: LibreElec uses its own version of LIRC I think plus it may well use ir-keytable. Can you post the whole bit of the log where it detects the IR device, so I can see which inputs get assigned to it and which driver it's using ?This seems to be the part pertaining to the IR Rx
[ 193.796073] usb 7-1: new low-speed USB device number 2 using uhci_hcd
[ 193.998098] usb 7-1: New USB device found, idVendor=0766, idProduct=0204
[ 193.998102] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 193.998104] usb 7-1: Product: USB IR Combo Device
[ 193.998106] usb 7-1: Manufacturer: TopSeed Tech Corp.
[ 194.139249] hidraw: raw HID events driver © Jiri Kosina
[ 194.217557] usbcore: registered new interface driver usbhid
[ 194.217560] usbhid: USB HID core driver
[ 194.241516] input: TopSeed Tech Corp. USB IR Combo Device as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/0003:0766:0204.0001/input/input18
[ 194.300621] topseed 0003:0766:0204.0001: input,hidraw0: USB HID v1.00 Keyboard [TopSeed Tech Corp. USB IR Combo Device ] on usb-0000:00:1d.1-1/input0
[ 194.301318] input: TopSeed Tech Corp. USB IR Combo Device as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.1/0003:0766:0204.0002/input/input19
[ 194.360533] topseed 0003:0766:0204.0002: input,hiddev0,hidraw1: USB HID v1.00 Mouse [TopSeed Tech Corp. USB IR Combo Device ] on usb-0000:00:1d.1-1/input1
[ 221.365856] perf: interrupt took too long (3991 > 3983), lowering kernel.perf_event_max_sample_rate to 50000 --- This was the last line of log.