• 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 16
How to get a seamless remote experience
#46
I wish this guide had been available when I installed XBMC 10 on Xubuntu 11.04. It wasn't, so I had to find my own solution. I did not write everything down, so just an abstract from memory. Maybe it gives somebody an idea or two.

Problem (well known):

- XBMC needs LIRC to play nicely
- 2.6.38 kernels handle IR internally and differently from LIRC

-> Generic LIRC setup didn't work (no IR codes recognized)

Solution:

- Use input-lirc to bridge between the kernel and LIRC. Basically, LIRC is set up without it's kernel modules and gets input from the inputlirc daemon.

Again, this is from memory.
Reply
#47
XBMC does not need LIRC. LIRC is optional and discouraged if not needed (e.g. for irexec)

@Jayphen: does /etc/rc_keymaps/test actually exist? What does `ls /etc/rc_keymaps/test` say?
Reply
#48
LB06 Wrote:XBMC does not need LIRC. LIRC is optional and discouraged if not needed (e.g. for irexec)

@Jayphen: does /etc/rc_keymaps/test actually exist? What does `ls /etc/rc_keymaps/test` say?

Nothing there.

Code:
/etc/rc_keymaps$ ls
imon_mce
Reply
#49
You have to specify a file that contains the keymappings. To test if your receiver and remote actually work just execute

Code:
ir-keytable -c -p NEC,RC-5,RC-6,JVC,SONY -t

as specified in the guide
Reply
#50
LB06 Wrote:You have to specify a file that contains the keymappings. To test if your receiver and remote actually work just execute

Code:
ir-keytable -c -p NEC,RC-5,RC-6,JVC,SONY -t

as specified in the guide

Code:
Couldn't find any node at /sys/class/rc/rc*.

There is no /sys/class/rc
Reply
#51
LB06 Wrote:XBMC does not need LIRC. LIRC is optional and discouraged if not needed (e.g. for irexec)

Tell that to my XBMC installation. Stare

It was not able to recognize my remote on Xubuntu 11.04 without LIRC and InputLIRC. Believe me, if it had worked out of the box, I wouldn't have bothered trying LIRC!
Reply
#52
Either you are running a kernel that doesn't support ir-keytable yet (i.e. <=2.6.35) or you don't have the drivers for your receiver installed and/or loaded and running. Or your receiver is not supported.
Reply
#53
recluce Wrote:Tell that to my XBMC installation. Stare

It was not able to recognize my remote on Xubuntu 11.04 without LIRC and InputLIRC. Believe me, if it had worked out of the box, I wouldn't have bothered trying LIRC!
Do you mean your receiver or the key presses on your remote? Because LIRC doesn't really support (or not support) remotes.
Reply
#54
LB06 Wrote:Either you are running a kernel that doesn't support ir-keytable yet (i.e. <=2.6.35) or you don't have the drivers for your receiver installed and/or loaded and running. Or your receiver is not supported.

Code:
$ uname -r
2.6.38-11-generic

& I'm using the Asus DH USB receiver. I'd say the drivers aren't installed/running, but I'm not sure how to install them.
Reply
#55
Is it detected at boot time (dmesg) or by lsusb?
Reply
#56
Code:
Bus 004 Device 004: ID 1130:cc00 Tenx Technology, Inc.
That's him, in lsusb.

Code:
$ dmesg | grep 1130
[    4.108377] generic-usb 0003:1130:CC00.0003: hiddev0,hidraw2: USB HID v1.10 Device [T-wins ASUS DH Remote] on usb-0000:00:12.0-4/input0
Reply
#57
I don't think it's supported. I can't find the vendor ID in the kernel source. Maybe you need proprietary drivers. My dmesg looks like this:

Code:
[    9.625302] IR NEC protocol handler initialized
...
[    9.628838] IR RC5(x) protocol handler initialized
[    9.631419] IR RC6 protocol handler initialized
[    9.635459] IR JVC protocol handler initialized
[    9.636835] IR Sony protocol handler initialized
[    9.639029] lirc_dev: IR Remote Control driver registered, major 251
[    9.639971] IR LIRC bridge handler initialized
[    9.660238] Registered IR keymap rc-rc6-mce
[    9.660329] input: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/rc/rc0/input2
[    9.660385] rc0: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/rc/rc0
[    9.669227] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[    9.669245] mceusb 4-2:1.0: Registered Philips eHome Infrared Transceiver on usb4:2
[    9.669263] usbcore: registered new interface driver mceusb
Reply
#58
LB06 Wrote:Do you mean your receiver or the key presses on your remote? Because LIRC doesn't really support (or not support) remotes.

Receiver was recognized (lsusb), but no key-presses got anywhere.
Reply
#59
LB06 Wrote:I don't think it's supported. I can't find the vendor ID in the kernel source. Maybe you need proprietary drivers. My dmesg looks like this:

Code:
[    9.625302] IR NEC protocol handler initialized
...
[    9.628838] IR RC5(x) protocol handler initialized
[    9.631419] IR RC6 protocol handler initialized
[    9.635459] IR JVC protocol handler initialized
[    9.636835] IR Sony protocol handler initialized
[    9.639029] lirc_dev: IR Remote Control driver registered, major 251
[    9.639971] IR LIRC bridge handler initialized
[    9.660238] Registered IR keymap rc-rc6-mce
[    9.660329] input: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/rc/rc0/input2
[    9.660385] rc0: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/rc/rc0
[    9.669227] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[    9.669245] mceusb 4-2:1.0: Registered Philips eHome Infrared Transceiver on usb4:2
[    9.669263] usbcore: registered new interface driver mceusb

Bummer, I might have to go and grab a different receiver. This one appears to be supported by LIRC, but I couldn't get it to work with that either.

Do you have any recommendations for receivers?
Reply
#60
HP MCE receiver with S/N 5188-1667. If your receiver is already supported by lirc, chances are it will be supported by ir-keytable in upcoming Linux versions. Also, you can continue to use LIRC and disable ir-keytable and the LIRC bridge by blacklisting all ir-* and rc-* modules. Modules like ir-*, rc-*, mceusb, imon and nuvoton are the 'new style' drivers, while lirc-* modules are the old ones. You can still just pick either.
Reply
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 16

Logout Mark Read Team Forum Stats Members Help
How to get a seamless remote experience9