[mythtv-users] USB IR Receivers

[Kirk Bocek]

On 8/31/2015 12:24 PM, Alec Leamas wrote:
> On 31/08/15 17:59, Kirk Bocek wrote:
>>
>>
>
>> But to use lirc, you need to load a kernel driver.
>
> Indeed.
>
>> Hunting around, this was suggested in /etc/udev/rules.d:
>>
>> SUBSYSTEM=="usb" , ATTRS{idVendor}=="0471", ATTRS{idProduct}=="20cc",
>> SYMLINK+="remote", ACTION=="add"
>
> That rule would just add a symlink if/when the device was created. I'm 
> no udev guru, but in a situation like this I don't think udev adds 
> anything useful (except if used to unbind the active driver, see my 
> previous postings).
>
> Check the dmesg output when physically reconnecting the device. I 
> cannot read the whole thread, but as I understand the problem is not 
> that there is no kernel driver loaded, but that the wrong (from our 
> perspective) hidusb driver is loaded by the kernel.
>
> Whatever driver the kernel loads for your device it should be obvious 
> from the dmesg output.
>
>

[    2.803036] usb 1-2: New USB device found, idVendor=0471, idProduct=20cc
[    2.803044] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[    2.803048] usb 1-2: Product: MCE USB IR Receiver- Spinel plus
[    2.803051] usb 1-2: Manufacturer: PHILIPS
[    2.952817] usb 1-2: ep 0x81 - rounding interval to 64 microframes, 
ep desc says 80 microframes
[    2.956975] ACPI: Video Device [GFX0] (multi-head: yes  rom: no post: no)
[    2.957886] acpi device:09: registered as cooling_device2
[    2.958053] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
[    2.970165] input: PHILIPS MCE USB IR Receiver- Spinel plus as 
/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:0471:20CC.0001/input/input4
[    2.972169] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on 
minor 0
[    2.977346] fbcon: inteldrmfb (fb0) is primary device
[    3.024090] hid-generic 0003:0471:20CC.0001: input,hiddev0,hidraw0: 
USB HID v1.00 Keyboard [PHILIPS MCE USB IR Receiver- Spinel plus] on 
usb-0000:00:14.0-2/input0

Looks like we have a video thing mixed in here. But we keep talking 
about this only getting recognized as a keyboard: that looks like 
input0. The by-id and by-path links are to input4 here.