2014-04-08, 00:38
So I've been working to get a fresh install of 13.0 Beta2 XBMCBuntu working for my main machine. I know it's a beta and not necessarily ready for primetime, but my problems likely stem from Linux itself rather than XBMC.
I tried to follow a number of different (older) tutorials on getting remote controls to work properly in Ubuntu/XBMCBuntu with no luck. Most of them say to use to display keypress information but I could never get this to work after configuring Lirc numerous ways. I know now this is the old method of seeing input and am unsure if it is even meant to work now.
I started using ir-keytable to display keypresses (after removing Lirc and with Lirc installed, it never worked with Lirc as the only enabled protocol) and am getting some weird output. If I hold down the same key or press it repeatedly, I get different codes for the press that don't make any sense.
The event types on these keypresses are coming back as EV_MSC so that's not a good sign either (I looked up EV_MSC as a miscellaneous event).
So, the info on my equipment and what I've done.
I own a mediagate GP-IR02BK that I've used successfully as a primary means of control on a Windows 7 XBMC install since 2009 using EventGhost.
when i list usb devices:
I've seen during my search that this appears to be the correct driver name for the IR receiver.
When I run ir-keytable to see my config:
I have all protocols enabled right now, but the remote is RC-6 and gives results for RC-6 when it's the only protocol enabled. Apparently I have Lirc installed again now, I've been removing it and installing it as I try to follow different guides to get the remote working.
Now for (to me, at least) the really weird part: What follows is what happens when I run ir-keytable -t to test keypresses and press only the up arrow on the remote.
I just don't see any rhyme or reason to why these scancodes are being generated. I must be missing something, it may be really obvious. But I've been running in circles for days now and want to get some other eyeballs on this thing to see if any linux gurus have a solution.
Other notes:
I've tried to be as thorough as possible to document pertinent information, but I've probably missed some things. I'm hopefully obviously to get my setup working smoothly but I also want others who may experience this to be able to find a solution if one exists.
I tried to follow a number of different (older) tutorials on getting remote controls to work properly in Ubuntu/XBMCBuntu with no luck. Most of them say to use
Code:
irw
I started using ir-keytable to display keypresses (after removing Lirc and with Lirc installed, it never worked with Lirc as the only enabled protocol) and am getting some weird output. If I hold down the same key or press it repeatedly, I get different codes for the press that don't make any sense.
The event types on these keypresses are coming back as EV_MSC so that's not a good sign either (I looked up EV_MSC as a miscellaneous event).
So, the info on my equipment and what I've done.
I own a mediagate GP-IR02BK that I've used successfully as a primary means of control on a Windows 7 XBMC install since 2009 using EventGhost.
when i list usb devices:
Code:
root@Emerald:~# lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 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 003 Device 003: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code:
Bus 003 Device 003: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver
I've seen during my search that this appears to be the correct driver name for the IR receiver.
When I run ir-keytable to see my config:
Code:
root@Emerald:~# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event3) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Name: Media Center Ed. eHome Infrared
bus: 3, vendor/product: 1784:0008, version: 0x0101
Repeat delay = 500 ms, repeat period = 125 ms
I have all protocols enabled right now, but the remote is RC-6 and gives results for RC-6 when it's the only protocol enabled. Apparently I have Lirc installed again now, I've been removing it and installing it as I try to follow different guides to get the remote working.
Now for (to me, at least) the really weird part: What follows is what happens when I run ir-keytable -t to test keypresses and press only the up arrow on the remote.
Code:
root@Emerald:~# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1396909789.381192: event type EV_MSC(0x04): scancode = 0x2003c1
1396909789.381192: event type EV_SYN(0x00).
1396909789.701198: event type EV_MSC(0x04): scancode = 0x800f0
1396909789.701198: event type EV_SYN(0x00).
1396909790.021201: event type EV_MSC(0x04): scancode = 0x40078
1396909790.021201: event type EV_SYN(0x00).
1396909790.341193: event type EV_MSC(0x04): scancode = 0x2003c
1396909790.341193: event type EV_SYN(0x00).
1396909790.661170: event type EV_MSC(0x04): scancode = 0x1001e
1396909790.661170: event type EV_SYN(0x00).
1396909790.981203: event type EV_MSC(0x04): scancode = 0x1001e
1396909790.981203: event type EV_SYN(0x00).
1396909791.109225: event type EV_MSC(0x04): scancode = 0x100
1396909791.109225: event type EV_SYN(0x00).
1396909791.333217: event type EV_MSC(0x04): scancode = 0x200
1396909791.333217: event type EV_SYN(0x00).
1396909791.621200: event type EV_MSC(0x04): scancode = 0x800f
1396909791.621200: event type EV_SYN(0x00).
1396909791.973220: event type EV_MSC(0x04): scancode = 0x200
1396909791.973220: event type EV_SYN(0x00).
1396909792.133199: event type EV_MSC(0x04): scancode = 0x2003c10
1396909792.133199: event type EV_SYN(0x00).
1396909792.261217: event type EV_MSC(0x04): scancode = 0x4007
1396909792.261217: event type EV_SYN(0x00).
1396909792.453202: event type EV_MSC(0x04): scancode = 0x1001e08
1396909792.453202: event type EV_SYN(0x00).
1396909792.613186: event type EV_MSC(0x04): scancode = 0x2003
1396909792.613186: event type EV_SYN(0x00).
1396909793.509208: event type EV_MSC(0x04): scancode = 0x1001f
1396909793.509208: event type EV_SYN(0x00).
1396909794.277190: event type EV_MSC(0x04): scancode = 0x200
1396909794.277190: event type EV_SYN(0x00).
1396909794.693206: event type EV_MSC(0x04): scancode = 0x400
1396909794.693206: event type EV_SYN(0x00).
1396909794.917183: event type EV_MSC(0x04): scancode = 0x2003e
1396909794.917183: event type EV_SYN(0x00).
I just don't see any rhyme or reason to why these scancodes are being generated. I must be missing something, it may be really obvious. But I've been running in circles for days now and want to get some other eyeballs on this thing to see if any linux gurus have a solution.
Other notes:
Code:
root@Emerald:~# uname -r
3.13.0-21-generic
I've tried to be as thorough as possible to document pertinent information, but I've probably missed some things. I'm hopefully obviously to get my setup working smoothly but I also want others who may experience this to be able to find a solution if one exists.