Linux - OpenELEC IR setup? - Printable Version

Linux OpenELEC IR setup? - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: Linux OpenELEC IR setup? (/showthread.php?tid=189165)

Pages: 1 2 3

RE: OpenELEC IR setup? - Chris230291 - 2014-03-25

(2014-03-25, 01:11)FishOil Wrote:
(2014-03-23, 14:49)Chris230291 Wrote: If I run those I see...

Code:
OpenELEC (official) Version: 3.2.4 Chris-HTPC:~ # killall lircd killall: lircd: no process killed Chris-HTPC:~ # ls /dev SYSTEM nbd8 tty0 tty46 ati nbd9 tty1 tty47 autofs net tty10 tty48 block network_latency tty11 tty49 bsg network_throughput tty12 tty5 btrfs-control null tty13 tty50 bus port tty14 tty51 char ppp tty15 tty52 console ptmx tty16 tty53 core pts tty17 tty54 cpu ram0 tty18 tty55 cpu_dma_latency ram1 tty19 tty56 disk ram10 tty2 tty57 fb0 ram11 tty20 tty58 fd ram12 tty21 tty59 full ram13 tty22 tty6 fuse ram14 tty23 tty60 fw0 ram15 tty24 tty61 hidraw0 ram2 tty25 tty62 i2c-0 ram3 tty26 tty63 i2c-1 ram4 tty27 tty7 input ram5 tty28 tty8 kmsg ram6 tty29 tty9 log ram7 tty3 ttyS0 loop-control ram8 tty30 ttyS1 loop0 ram9 tty31 ttyS2 mem random tty32 ttyS3 nbd0 rfkill tty33 uinput nbd1 rtc tty34 urandom nbd10 rtc0 tty35 vcs nbd11 rules.d tty36 vcs1 nbd12 sda tty37 vcsa nbd13 sda1 tty38 vcsa1 nbd14 sda2 tty39 vga_arbiter nbd15 sg0 tty4 watchdog nbd2 shm tty40 watchdog0 nbd3 snd tty41 zero nbd4 stderr tty42 zram0 nbd5 stdin tty43 nbd6 stdout tty44 nbd7 tty tty45 Chris-HTPC:~ #

It appears It is undetected?

Cheers,
Chris.

Without further investigation it would seem that your USB IR Receiver is not detected.

With the correct receiver its pretty easy to get a remote going in OpenELEC.

What do you get from

Code:
cat /proc/bus/input/devices

When I run that I get

Code:
OpenELEC (official) Version: 3.2.4

Chris-HTPC:~ # cat /proc/bus/input/devices

I: Bus=0019 Vendor=0000 Product=0001 Version=0000

N: Name="Power Button"

P: Phys=PNP0C0C/button/input0

S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0

U: Uniq=

H: Handlers=kbd event0

B: PROP=0

B: EV=3

B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000

N: Name="Power Button"

P: Phys=LNXPWRBN/button/input0

S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1

U: Uniq=

H: Handlers=kbd event1

B: PROP=0

B: EV=3

B: KEY=10000000000000 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41

N: Name="AT Translated Set 2 keyboard"

P: Phys=isa0060/serio0/input0

S: Sysfs=/devices/platform/i8042/serio0/input/input2

U: Uniq=

H: Handlers=sysrq kbd event2

B: PROP=0

B: EV=120013

B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe

B: MSC=10

B: LED=7

I: Bus=0003 Vendor=073a Product=2330 Version=0110

N: Name="www.tigerfly.net www.tigerfly.net"

P: Phys=usb-0000:00:13.4-1/input0

S: Sysfs=/devices/pci0000:00/0000:00:13.4/usb6/6-1/6-1:1.0/input/input3

U: Uniq=www.tigerfly.net

H: Handlers=sysrq kbd mouse0 js0 event3

B: PROP=0

B: EV=10001f

B: KEY=4c37fff072ff32d bf54445600000000 ffffffffff 30c100b17c007 ffa67bfad951dfff febeffdfffefffff fffffffffffffffe

B: REL=343

B: ABS=100030000

B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Front Headphone"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input4

U: Uniq=

H: Handlers=event4

B: PROP=0

B: EV=21

B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Line Out Side"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input5

U: Uniq=

H: Handlers=event5

B: PROP=0

B: EV=21

B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Line Out CLFE"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input6

U: Uniq=

H: Handlers=event6

B: PROP=0

B: EV=21

B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Line Out Surround"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input7

U: Uniq=

H: Handlers=event7

B: PROP=0

B: EV=21

B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Line Out Front"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input8

U: Uniq=

H: Handlers=event8

B: PROP=0

B: EV=21

B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Line"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input9

U: Uniq=

H: Handlers=event9

B: PROP=0

B: EV=21

B: SW=2000

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Front Mic"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input10

U: Uniq=

H: Handlers=event10

B: PROP=0

B: EV=21

B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA ATI SB Rear Mic"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input11

U: Uniq=

H: Handlers=event11

B: PROP=0

B: EV=21

B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HD-Audio Generic HDMI/DP,pcm=3"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input12

U: Uniq=

H: Handlers=event12

B: PROP=0

B: EV=21

B: SW=140

It looks to be a "tigerfly" reciever. Googleing it came up with this http://wiki.xbmc.org/index.php?title=Unbranded_MCE_remote
I'm just looking to use the receiver part though, I already have a decent remote.

Chris.

RE: OpenELEC IR setup? - nickr - 2014-03-25

What does lsusb tell you about the receiver?

RE: OpenELEC IR setup? - FishOil - 2014-03-26

(2014-03-25, 13:45)Chris230291 Wrote: [quote='FishOil' pid='1662534' dateline='1395702693']
[quote='Chris230291' pid='1660987' dateline='1395578957']

When I run that I get

[code]OpenELEC (official) Version: 3.2.4
Chris-HTPC:~ # cat /proc/bus/input/devices
I
I: Bus=0003 Vendor=073a Product=2330 Version=0110
N: Name="www.tigerfly.net www.tigerfly.net"
P: Phys=usb-0000:00:13.4-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:13.4/usb6/6-1/6-1:1.0/input/input3
U: Uniq=www.tigerfly.net
H: Handlers=sysrq kbd mouse0 js0 event3
B: PROP=0
B: EV=10001f
B: KEY=4c37fff072ff32d bf54445600000000 ffffffffff 30c100b17c007 ffa67bfad951dfff febeffdfffefffff fffffffffffffffe
B: REL=343
B: ABS=100030000
B: MSC=10

Its not being seen as an "Infrared Remote Transceiver". It appears to be a keyboard mouse receiver only.

IMO you should get a standard "Infrared Remote Transceiver"

BTW if I run the command I ask you to run with my "Infrared Remote Transceiver" unplugged. I get the same message you did.

Quote:Chris-HTPC:/ # ir-keytable -p lirc
/sys/class/rc/: No such file or directory

So, it would seem to indicate that you dont have an "Infrared Remote Transceiver"

RE: OpenELEC IR setup? - Chris230291 - 2014-03-26

(2014-03-25, 21:07)nickr Wrote: What does lsusb tell you about the receiver?

Hello. If I run that I get

Code:
OpenELEC (official) Version: 3.2.4

Chris-HTPC:~ # lsusb

Bus 006 Device 004: ID 073a:2330 Chaplet Systems, Inc.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

(2014-03-26, 00:36)FishOil Wrote:
(2014-03-25, 13:45)Chris230291 Wrote: [quote='FishOil' pid='1662534' dateline='1395702693']
[quote='Chris230291' pid='1660987' dateline='1395578957']

When I run that I get

[code]OpenELEC (official) Version: 3.2.4
Chris-HTPC:~ # cat /proc/bus/input/devices
I
I: Bus=0003 Vendor=073a Product=2330 Version=0110
N: Name="www.tigerfly.net www.tigerfly.net"
P: Phys=usb-0000:00:13.4-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:13.4/usb6/6-1/6-1:1.0/input/input3
U: Uniq=www.tigerfly.net
H: Handlers=sysrq kbd mouse0 js0 event3
B: PROP=0
B: EV=10001f
B: KEY=4c37fff072ff32d bf54445600000000 ffffffffff 30c100b17c007 ffa67bfad951dfff febeffdfffefffff fffffffffffffffe
B: REL=343
B: ABS=100030000
B: MSC=10

Its not being seen as an "Infrared Remote Transceiver". It appears to be a keyboard mouse receiver only.

IMO you should get a standard "Infrared Remote Transceiver"

BTW if I run the command I ask you to run with my "Infrared Remote Transceiver" unplugged. I get the same message you did.

Quote:Chris-HTPC:/ # ir-keytable -p lirc
/sys/class/rc/: No such file or directory

So, it would seem to indicate that you dont have an "Infrared Remote Transceiver"

Hmm. So I should just buy a different one? The Wiki I posted seems to suggest that it should work. Perhaps that's just the remote part?

Chris.

RE: OpenELEC IR setup? - nickr - 2014-03-26

google 073a:2330 there are plenty of pages about this remote.

RE: OpenELEC IR setup? - fritz222 - 2014-05-18

Do you guys have any new insights on this?

I have exactly the same error on this with my moneual moncaso 312 remote.

It worked with lirc in xbmcbuntu now i have updatet to openelec and this doesn't work.

Any help?

Thank you.
fritz222

RE: OpenELEC IR setup? - mebby - 2014-05-19

(2014-03-15, 12:34)trsqr Wrote: I wrote small article about mapping of the buttons: http://intelnuc.blogspot.fi/2014/01/mapping-buttons-on-remote-control.html

You did not specify what kind of problems you have with the remote, but maybe that will help you a bit.

Man - THANK YOU! I've been banging my head against the wall all weekend trying to get my i5 NUC setup. Everything worked fantastically except for some of the more customized things I was looking to do (key press taking my straight to a file location or playlist). The wiki doesn't appear to explain the interaction of the hidden lircmap.xml and the remote.xml files at all.

I'm coming from a Windows XBMC background and I very well knew about the keymap.xml file but that just wasn't getting it done here because I couldn't tell how the IR codes were mapped to the XBMC codes. Got it now thanks to you!

So thanks a ton!

RE: OpenELEC IR setup? - fritz222 - 2014-05-23

Nobody any idea??

I need help concerning the issue with no such file or directory after entering ir-keytable -p lirc

RE: OpenELEC IR setup? - FishOil - 2014-05-23

(2014-05-19, 05:20)mebby Wrote: The wiki doesn't appear to explain the interaction of the hidden lircmap.xml and the remote.xml files at all.

http://wiki.xbmc.org/index.php?title=Lirc

Re: RE: OpenELEC IR setup? - nickr - 2014-05-24

(2014-05-23, 17:35)fritz222 Wrote: Nobody any idea??

I need help concerning the issue with no such file or directory after entering ir-keytable -p lirc

Have a look at the article referred to in post #4. No ir-keytable needed.

RE: OpenELEC IR setup? - FishOil - 2014-05-24

(2014-05-23, 17:35)fritz222 Wrote: Nobody any idea??

I need help concerning the issue with no such file or directory after entering ir-keytable -p lirc

The issue is likely due to your IR receiver not being detected by default or incompatible.

You may have success by specifying the device to ir-keytable with the -d switch.

RE: OpenELEC IR setup? - fritz222 - 2014-05-24

the format of ir-keytable is this right: ir-keytable -d /dev/input/eventX

I don't know which event it is.

"cat /proc/bus/input/devices" gives me this, but I think the ir receiver is not listed:

Code:
I: Bus=0019 Vendor=0000 Product=0001 Version=0000

N: Name="Power Button"

P: Phys=PNP0C0C/button/input0

S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0

U: Uniq=

H: Handlers=kbd event0

B: PROP=0

B: EV=3

B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000

N: Name="Power Button"

P: Phys=LNXPWRBN/button/input0

S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1

U: Uniq=

H: Handlers=kbd event1

B: PROP=0

B: EV=3

B: KEY=10000000000000 0

I: Bus=0001 Vendor=10ec Product=0889 Version=0001

N: Name="HDA Digital PCBeep"

P: Phys=card0/codec#2/beep0

S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input4

U: Uniq=

H: Handlers=kbd event2

B: PROP=0

B: EV=40001

B: SND=6

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA Intel PCH Line Out"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input8

U: Uniq=

H: Handlers=event3

B: PROP=0

B: EV=21

B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA Intel PCH Line"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input7

U: Uniq=

H: Handlers=event4

B: PROP=0

B: EV=21

B: SW=2000

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA Intel PCH Front Mic"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input6

U: Uniq=

H: Handlers=event5

B: PROP=0

B: EV=21

B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA Intel PCH Rear Mic"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input5

U: Uniq=

H: Handlers=event6

B: PROP=0

B: EV=21

B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA NVidia HDMI/DP,pcm=7"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input10

U: Uniq=

H: Handlers=event7

B: PROP=0

B: EV=21

B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="HDA NVidia HDMI/DP,pcm=3"

P: Phys=ALSA

S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input9

U: Uniq=

H: Handlers=event8

B: PROP=0

B: EV=21

B: SW=140

But it is listed in lsusb (the last entry):

Code:
HTPC:/etc/lirc # lsusb

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

Quote: Have a look at the article referred to in post #4. No ir-keytable needed.

irw does not give anything back and I dont have this nuvoton-cir module.

dmesg gives me this:

Code:
[    5.097081] usbcore: registered new interface driver usbserial

[    5.098206] usbcore: registered new interface driver ftdi_sio

[    5.098219] usbserial: USB Serial support registered for FTDI USB Serial Device

[    5.098250] ftdi_sio 2-1.3:1.0: FTDI USB Serial Device converter detected

[    5.098274] usb 2-1.3: Detected FT232RL

[    5.098275] usb 2-1.3: Number of endpoints 2

[    5.098277] usb 2-1.3: Endpoint 1 MaxPacketSize 64

[    5.098278] usb 2-1.3: Endpoint 2 MaxPacketSize 64

[    5.098280] usb 2-1.3: Setting MaxPacketSize 64

[    5.098626] usb 2-1.3: FTDI USB Serial Device converter now attached to ttyUSB0

I also got support in the openelec forum but without succes:
http://openelec.tv/forum/103-infared-remotes/71129-ir-keytable-no-such-file-or-directory

Thank you guys for helping me! Love

Regards,
fritz222

RE: OpenELEC IR setup? - FishOil - 2014-05-24

If you dont see lirc* when you issue the command "ls /dev" then lirc is not being activated / used.

The next step (assuming your IR device is of the correct kind) is to see what modules are loaded.

Type
lsmod

some sort of lirc / IR module should be loaded.

If not, you can try to manually load one and see how it goes from there.

RE: OpenELEC IR setup? - fritz222 - 2014-05-25

There is no lirc* in /dev. Sad

When I type lsmod I get the following:

Code:
HTPC:~ # lsmod

Module                  Size  Used by

nvidia              10628714  39

snd_hda_codec_hdmi     30179  1

intel_powerclamp        7890  0

intel_rapl              7883  0

snd_hda_codec_realtek    40820  1

snd_hda_codec_generic    39966  1 snd_hda_codec_realtek

ftdi_sio               32872  0

usbserial              17922  1 ftdi_sio

snd_oxygen             14183  2

snd_oxygen_lib         25429  1 snd_oxygen

snd_mpu401_uart         4747  1 snd_oxygen_lib

snd_rawmidi            13979  1 snd_mpu401_uart

snd_hda_intel          29715  0

snd_hda_codec          70871  4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel

snd_hwdep               4757  1 snd_hda_codec

snd_pcm                59081  5 snd_hda_codec_hdmi,snd_oxygen_lib,snd_hda_codec,snd_hda_intel

uvesafb                18838  1

xhci_hcd               80853  0

How to load the module and which?

EDIT: Is ther mplay2 suport in OE anyway?

EDIT 2: I found this guide. Didn't work...

Thanks.
Regards,
fritz222

RE: OpenELEC IR setup? - leetwanker - 2015-04-27

Sorry to resurrect an old thread but I'm having the same issue. Raspberry Pi 2 w/ OpenOLEC 5.08.

Kodi:~ # ls /dev/

Code:
autofs

block

btrfs-control

bus

char

console

cpu_dma_latency

disk

fb0

fd

full

fuse

hidraw0

hidraw1

hwrng

initctl

input

kmsg

log

loop-control

loop0

mem

memory_bandwidth

mmcblk0

mmcblk0p1

mmcblk0p2

mqueue

nbd0

nbd1

nbd10

nbd11

nbd12

nbd13

nbd14

nbd15

nbd2

nbd3

nbd4

nbd5

nbd6

nbd7

nbd8

nbd9

net

network_latency

network_throughput

null

ppp

ptmx

pts

ram0

ram1

ram10

ram11

ram12

ram13

ram14

ram15

ram2

ram3

ram4

ram5

ram6

ram7

ram8

ram9

random

shm

snd

stderr

stdin

stdout

tty

tty0

tty1

tty10

tty11

tty12

tty13

tty14

tty15

tty16

tty17

tty18

tty19

tty2

tty20

tty21

tty22

tty23

tty24

tty25

tty26

tty27

tty28

tty29

tty3

tty30

tty31

tty32

tty33

tty34

tty35

tty36

tty37

tty38

tty39

tty4

tty40

tty41

tty42

tty43

tty44

tty45

tty46

tty47

tty48

tty49

tty5

tty50

tty51

tty52

tty53

tty54

tty55

tty56

tty57

tty58

tty59

tty6

tty60

tty61

tty62

tty63

tty7

tty8

tty9

ttyAMA0

uinput

urandom

usb

vc-cma

vc-mem

vchiq

vcio

vcs

vcs1

vcs2

vcs3

vcs4

vcs5

vcs6

vcsa

vcsa1

vcsa2

vcsa3

vcsa4

vcsa5

vcsa6

zero

Kodi:~ # cat /proc/bus/input/devices

Code:
I: Bus=0003 Vendor=0c16 Product=0002 Version=0110

N: Name="Gyration Gyration RF Technology Receiver"

P: Phys=usb-bcm2708_usb-1.5/input0

S: Sysfs=/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:0C16:0002.0001/input/input0

U: Uniq=

H: Handlers=sysrq kbd event0 

B: PROP=0

B: EV=10001f

B: KEY=3007f 0 0 0 0 483ffff 17aff32d bf544446 0 0 1 120c13 b17c000 267bfa d941dfed e09effdf 1cfffff ffffffff fffffffe

B: REL=40

B: ABS=1 0

B: MSC=10

I: Bus=0003 Vendor=0c16 Product=0002 Version=0120

N: Name="Gyration Gyration RF Technology Receiver"

P: Phys=usb-bcm2708_usb-1.5/input1

S: Sysfs=/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.1/0003:0C16:0002.0002/input/input1

U: Uniq=

H: Handlers=sysrq kbd mouse0 event1 

B: PROP=0

B: EV=10001f

B: KEY=3007f 0 0 0 0 483ffff 17aff3bd bf544446 0 0 1f0001 120c17 b17c007 ffa67bfa d941dfff 80beffcd 1cfffff febffbff dffffffe

B: REL=143

B: ABS=1 0

B: MSC=10

Kodi:~ # lsusb

Code:
Bus 001 Device 005: ID 0c16:0002 Gyration, Inc. RF Technology Receiver

Bus 001 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Kodi:~ # lsmod

Code:
Module                  Size  Used by

btusb                  18075  0 

bluetooth             255606  18 btusb

bcm2708_rng              801  0

Kodi:~ # ir-keytable -t

Code:
/sys/class/rc/: No such file or directory

I know my remote can be used with lirc, I gather that for whatever reason I'm getting this error because lirc isn't recognizing my USB receiver. Has anyone found a way to get it working? My remote is a Gyration GYR3101US. Most of my remote is currently working but I'd like to get more of it's buttons functional.

Edit: Instead of being in /sys/class/rc/ this is where I found my remote
Kodi:~ # ls /sys/class/input/input0/device/driver/

Code:
0003:0C16:0002.0001  0003:0C16:0002.0002  bind                 new_id               uevent               unbind

So if lirc would look in /sys/class/input/ instead? Just a thought.