[cable_guy]

I simply cannot get irw to run, it just says connection refused. Any idea please?

[Crazy_Land1]

Hi all

Ok bear with me on this, i just upgraded to V13 Gotham and all seems to work very well other then my remote.

I did a clean fresh install and setup my media just fine. After 2 hours of scraping my media i was set and ready to watch movies, i selected a movie and start to watch it using my remote and after 5 mins i went to pause the movie to find out my remote no longer did any thing.

It will not pause/stop/fast-forward/rewind or any thing at all. Only way i can get it to work while playing the video or even after the video ends is to plug a mouse in or reboot the htpc.

This update was done on my htpc that ran Frodo 12.3 with no problems at all. no hardware changes no bios changes.

Im not sure what is going on and i would like help for others before i go in messing around and totally messing it up lol

Also forgot to say its a MCE remote with a RC6 reciver

[HunterZ]

@Crazy_Land1: Could your problem be something like what happened to me a while back? Here's my thread on the issue: http://forum.xbmc.org/showthread.php?tid=131181

[Crazy_Land1]

@Crazy_Land1: Could your problem be something like what happened to me a while back? Here's my thread on the issue: http://forum.xbmc.org/showthread.php?tid=131181

Thanks for your reply HunterZ but it doesn't look like that is the problem.

Here's what i did to get that answer, Putty into xbmc, run irw and used the remote irw showed the commands.
Played with the remote moving around in xbmc adding some add-ons and going thru my movie list for about 10 mins and remote worked the hole time.

Left xbmc running and went for a walk to a coffee shop took about 20 mins to do that and when i got back picked up the remote hit ok on the movie list and remote work, played for 5 mins in xbmc with the remote and it worked and irw showed the commands. Started a movie and hit pause and info button every now and then and remote worked and irw showed the commands.

Waited about 20 mins into the movie and hit pause and the movie kept going, hit all kinds of buttons on the remote and nothing work and irw didn't show any cammands at all.

Its like the usb port stops working but i unplug the ir reciver and plug a mouse in and the mouse works right away.......

im at a loss lol

[retali8]

I've been trying all day to get my Zotac remote (that came with my Zbox ID80) working in Debian Wheezy (kernel 3.2.0.4) and keep running into the same issue no matter what I try. Basically I can get irw to receive commands from the remote fine but once I launch XBMC the directional buttons (up, down, left, right) get stuck in a temporary and/or infinite loop until I stop inputlirc. I don't know what is causing it but the other buttons (vol+, vol-, play, pause, etc.) seem to be fine. I currently have this in a config file in my xorg.conf.d directory..

Section "InputClass"
Identifier "PHILIPS MCE USB IR Receiver- Spinel plus"
MatchProduct "PHILIPS MCE USB IR Receiver- Spinel plus"
MatchIsKeyboard "true"
Option "Ignore" "true"
EndSection

[ 1677.851] (II) config/udev: Adding input device PHILIPS MCE USB IR Receiver- Spinel plus (/dev/input/event0)
[ 1677.851] (**) PHILIPS MCE USB IR Receiver- Spinel plus: Ignoring device from InputClass "PHILIPS MCE USB IR Receiver- Spinel plus"

root@zbox:/usr/share/X11/xorg.conf.d# irw
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
67 0 KEY_UP /dev/input/myremote
(on and on...)

lsmod output:
root@zbox:~# lsmod
Module Size Used by
nfsd 216170 13
nfs 308353 0
nfs_acl 12511 2 nfs,nfsd
auth_rpcgss 37143 2 nfs,nfsd
fscache 36739 1 nfs
lockd 67306 2 nfs,nfsd
sunrpc 173730 19 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
ext2 59231 1
loop 22641 0
snd_hda_codec_hdmi 30824 1
nvidia 11264793 43
arc4 12458 2
iwlwifi 166761 0
snd_hda_codec_realtek 188851 1
snd_hda_intel 26259 3
snd_hda_codec 78031 3 snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_hdmi
i2c_i801 16870 0
psmouse 69265 0
mac80211 192806 1 iwlwifi
btusb 17502 0
snd_hwdep 13186 1 snd_hda_codec
bluetooth 119455 1 btusb
snd_pcm 68083 4 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
i2c_core 23876 2 i2c_i801,nvidia
pcspkr 12579 0
cfg80211 137243 2 mac80211,iwlwifi
snd_page_alloc 13003 2 snd_pcm,snd_hda_intel
serio_raw 12931 0
evdev 17562 10
iTCO_wdt 17081 0
iTCO_vendor_support 12704 1 iTCO_wdt
rfkill 19012 2 cfg80211,bluetooth
snd_seq 45126 0
snd_seq_device 13176 1 snd_seq
snd_timer 22917 3 snd_seq,snd_pcm
coretemp 12898 0
video 17683 0
processor 28149 0
snd 52889 13 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_hdmi
soundcore 13065 1 snd
button 12937 0
ext4 350763 3
crc16 12343 2 ext4,bluetooth
jbd2 62115 1 ext4
ses 13106 0
mbcache 13114 2 ext4,ext2
enclosure 13306 1 ses
usbhid 36418 0
hid 81372 1 usbhid
dm_mod 63645 9
sg 25874 0
sd_mod 36136 5
usb_storage 43870 1
crc_t10dif 12348 1 sd_mod
ata_generic 12479 0
ata_piix 29535 2
libata 140630 2 ata_piix,ata_generic
scsi_mod 162269 5 libata,usb_storage,sd_mod,sg,ses
fan 12674 0
thermal 17383 0
thermal_sys 18040 4 thermal,fan,processor,video
xhci_hcd 73434 0
uhci_hcd 26865 0
r8169 47008 0
ehci_hcd 40249 0
mii 12675 1 r8169
usbcore 128741 7 ehci_hcd,uhci_hcd,xhci_hcd,usb_storage,usbhid,btusb
usb_common 12354 1 usbcore
root@zbox:~#

nobody 3364 0.0 0.0 12496 380 ? Ss May10 0:01 /usr/sbin/inputlircd -g -m 0 -c /dev/input/myremote

root@zbox:~# ll /dev/input/myremote
lrwxrwxrwx 1 root root 6 May 10 23:47 /dev/input/myremote -> event0

root@zbox:~# cat /etc/udev/rules.d/10-persistent-ir.rules
KERNEL=="event*",ATTRS{idVendor}=="0471",ATTRS{idProduct}=="20cc",SYMLINK="input/myremote"

Bus 003 Device 002: ID 0471:20cc Philips (or NXP)

If I hit another button it will breakout of the loop unless it's another directional button then it will loop the new button I pressed. Any ideas? The kernel isn't loading any IR modules and I couldn't get this IR receiver to work with any of the kernel modules. I even tried to upgrade to a 3.12.x kernel to see if it would make any difference and it didn't.. please help!

[kees667]

Thanks for this guide. My HP MCE receiver works out of the box on Kodi (Asrock 330), I just can't get it to wake from suspend any longer. Found some old guides to fix this on the web that don't seem to work, is a new fix required to wake with this newer kernel?

[teeedubb]

You need to enable wakeup on the USB port and the ir receiver. I'm not at home for a few days so I can't post a example, but hopefully that gets you started.

Edit tried what's in this post? I now use a udev rule to set the wakeup flag, but the info in this post should work http://forum.kodi.tv/showthread.php?tid=...#pid835642

[kees667]

Thanks, it looks as if it is enabled, mce remote is pluged into USB2

[teeedubb]

How about the actual ir receiver?

[kees667]

It is an HP MCE receiver. When I run lsusb I get:


I think this means it is connected to USB2. I have tried other ports and switching back to USB 1 (My asrock 330 only has 1 and 2, not USB 3.0)

[fbacher]

I have Ubuntu 14.10 and using the kernel IR support, not lirc. I have an mce remote working for a number of navigation keys (left, right, up, down, play, etc.) but I can not get it to work for simple things like KEY_BACKSPACE or KEY_C, which I remapped a few keys to in order to avoid the > 255 problem.

Using ir-keytable -t, I can see that it properly generates KEY_C, or KEY_BACKSPACE, yet kodi does not recognize them.

[kees667]

I have Ubuntu 14.10 and using the kernel IR support, not lirc.

Please excuse a noob for trying to learn...I heard that in newer Kodibuntu (basically newer Linux) the kernel now handles (or can handle) USB/IR. in my case ever since these changes my IR support has deteriorated. I could switch my machine on and off using IR in both XBMC and Openelec. Now in latest openelec (started prior to Kodi as newer kernel was included) remote starts to freeze randomly requiring me to replug the receiver. In Kodibuntu it does not freeze but I can't resume from suspend using the remote.

Does your post mean there is a choice to have the kernel not handle IR? I am using Kodibuntu now so not a seperate Ubuntu install.

[kees667]

Teeedubb, you are a hero! After my HP MCE remote started failing in latest openelec versions (before KODI) I moved to Kodibuntu and could not get resume via remote working. Thanks to this clear guide it works again! I am a complete noob, for other noobs I'd ust like to add two small things. In the end you have to edit a file. You do this with:

Code:

sudo nano /etc/rc.local

Then insert the lines from the guide before the last line (which is exit 0 or exit 1)
Exit the text editor with CTRL-X and chose save, then execute the last step from the guide,

One thing worth mentioning is that to resume from the remote with newer kernels you need to enable wake up on the actual receiver device aswell as the usb port.

lsusb will list your attached usb devices:

Code:

$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[b]Bus 004 Device 002: ID 1934:[u]5168[/u] Feature Integration Technology Inc. (Fintek) F71610A or F71612A Consumer Infrared Receiver/Transceiver[/b]
Bus 004 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 002 Device 006: ID 0b38:0010 Gear Head 107-Key Keyboard
Bus 002 Device 005: ID 046d:c049 Logitech, Inc. G5 Laser Mouse
Bus 002 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The bold line of text is my usb mce ir receiver. Use the device id (5168 in my case) with the following command to find your device in /sys/bus/usb/devices

Code:

$ grep 5168 /sys/bus/usb/devices/*/idProduct
/sys/bus/usb/devices/4-2/idProduct:5168

Now use that location to check if wakeup from the device is enabled with:

Code:

$ cat /sys/bus/usb/devices/4-2/power/wakeup
disabled

The following command will change this setting to enabled:

Code:

$ sudo sh -c 'echo "enabled" > /sys/bus/usb/devices/4-2/power/wakeup'

This setting will be reset on boot so to enable it on every boot I added the following line to my /etc/rc.local file (the first line is to enable wake up on the usb port, as per this wiki article.)

Code:

echo USB1 > /proc/acpi/wakeup
echo enabled > /sys/bus/usb/devices/4-2/power/wakeup

Make sure /etc/rc.local is executable with the command

Code:

sudo chmod +x /etc/rc.local

This got wake from the remote working for me, and after some testing it seems to work more reliably than on lucid...

[lonjemoco]

Hi,

Hope anyone can help. I'm trying to setup my remote with lirc. ir-keytable works, ir-keytable -t works, evtest works. irw does not work. Lirc log says this:

Feb 09 01:55:15 htpc lircd[266]: lircd-0.9.2[266]: Notice: accepted new client on /var/run/lirc/lircd
Feb 09 01:55:15 htpc lircd[266]: lircd-0.9.2[266]: Info: initializing '/dev/lirc'
Feb 09 01:55:15 htpc lircd[266]: lircd-0.9.2[266]: Debug: No device found: /sys/class/rc/rc0/lirc
Feb 09 01:55:15 htpc lircd[266]: lircd-0.9.2[266]: Info: Cannot configure the rc device for /dev/lirc
Feb 09 02:07:38 htpc lircd[266]: lircd-0.9.2[266]: Notice: accepted new client on /var/run/lirc/lircd

For some reason it's looking for a file called lirc (or whatever the name of my dev is, as I have tried renaming and making symlinks to it) in /sys/class/rc/rc0.
Any idea?

[teeedubb]

kees667 Glad you found that 3+ year old post useful

There is a better way to enable wakeup on a device - using udev. It will enable/disable wakeup even if you change the usb port the device is connect to (something the guide you used will not do).

/etc/udev/rules.d/99-disable-wakeup.rules

Code:

#disable devices
#ipazz keyboard
#SUBSYSTEM=="usb", ATTRS{idVendor}=="0c45", ATTRS{idProduct}=="7000", RUN+="/bin/sh -c 'echo disabled > /sys$env{DEVPATH}/../power/wakeup'"
#logitect k400r
SUBSYSTEM=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", RUN+="/bin/sh -c 'echo disabled > /sys$env{DEVPATH}/../power/wakeup'"
#usb bt
SUBSYSTEM=="usb", ATTRS{idVendor}=="0cf3", ATTRS{idProduct}=="3005", RUN+="/bin/sh -c 'echo disabled > /sys$env{DEVPATH}/../power/wakeup'"
#xbox360
SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="0291", RUN+="/bin/sh -c 'echo disabled > /sys$env{DEVPATH}/../power/wakeup'"


#enable
#cec adapter
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d6b", ATTRS{idProduct}=="0003", RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup'"
#harmony/phillips ir
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", ATTRS{idProduct}=="2093", RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup'"

You'll need to configure it for your system/devices, change the idvendor and idproduct string to match the output of lsusb, eg the output for my phillips ir receiver:

Code:

Bus 001 Device 005: ID 0471:2093 Philips (or NXP)