Microsoft remote.

**Lisiano** · October 31st, 2011

Ahhh thanks. I'm not home atm but I will try this once I get home. Sounds promising. Except I didn't understand what exactly were you referencing here

Originally Posted by s13_mills

I don't know if this is complicated by the fact that this is a USB remote only (ie not an IR input on a TV card or what not), but you might try setting the ir-keytable to the exact one for your remote, and eliminating the two that are incorrect. If it transpires that you have a mix of the three, you can configure that too.

I'm assuming you are talking about the "mceusb", "mceusb_haupauge" and "vista_mce" that LIRC decided to give me when I told it I have a MCE.
Note: I'm not afraid to mess up my LIRC conf since there is nothing (I think) beside what dpkg put there.

**s13_mills** · November 4th, 2011

Hi again,

How did you go? Did you get it figured out?

Sorry if I was a bit unclear below:

I don't know if this is complicated by the fact that this is a USB remote only (ie not an IR input on a TV card or what not)

I was referring to the fact that this is a remote with it's own USB receiver, as opposed to a remote that came with a TV card or similar, which has the receiver built into the TV card.

I'm assuming you are talking about the "mceusb", "mceusb_haupauge" and "vista_mce" that LIRC decided to give me when I told it I have a MCE.

With regard to the different configurations, they are keymaps for within ir-keytable, rather than inside LIRC - it is a similar thing though, and will likely have similar names. They are all found in /lib/udev/rc_keymaps/ (from memory).

Cheers,

Andrew

**Lisiano** · November 30th, 2011

Hi, I haven't been able to do anything yet till this moment, work, health, life. Anyway.
ir-keytables wasn't installed so after installing it.

Code:

sudo ir-keytable -t
/sys/class/rc/: No such file or directory
lisiano@Lisiano-Ubuntu:~$ cd /sys/class/rc
bash: cd: /sys/class/rc: No such file or directory

I don't know if this is good news or bad news... Assuming bad.

**mutant_matt** · December 2nd, 2011

What Kernel version are you on? (uname -a). What Distro and version?

Sounds to me like you might have a kernel of 2.6.35 or newer? (where the MCE stuff changed and the driver moved out of LIRC and into the main-line kernel). This is sounds very similar to the MCE USB remote setup I just went through on Mythbuntu 11.10 where I ended up setting LIRC to Linux Devinput (from the Myth Control Centre), plugging in the eventX into hardware.conf, and ran two lircd's to link the two events together, that the "Windows Vista/Windows 7" MCE remote presents itself as (an HID Keyboard and an HID Mouse).

What is the result of: modprobe -l | grep mce

Some of the steps here are useful: http://parker1.co.uk/mythtv_ubuntu2.php (Kerel Drivers/LIRC section)

If you identify the event it's using, as per the above page, you can start at the bottom and work your way up:

cat /dev/input/eventX - push buttons and see if you get garbage on the screen for each press (and if some buttons work, and some others don't)

sudo evtest /dev/input/eventX - to see what mappings are taking place

sudo /usr/sbin/lircd -H dev/input -d /dev/input/eventX -n plus irw in another window

Matt

**Lisiano** · December 2nd, 2011

Code:

uname-a
Linux Lisiano-Ubuntu 3.0.0-13-generic #22-Ubuntu SMP Wed Nov 2 13:27:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

It started from the very purchase of this PC, I think I installed Ubuntu 10.04 or 9.10 on it. Somewhere there. Currently using Ubuntu 11.10.

Code:

modprobe -l | grep mce
kernel/arch/x86/kernel/cpu/mcheck/mce-xeon75xx.ko
kernel/arch/x86/kernel/cpu/mcheck/mce-inject.ko
kernel/drivers/media/rc/keymaps/rc-fusionhdtv-mce.ko
kernel/drivers/media/rc/keymaps/rc-genius-tvgo-a11mce.ko
kernel/drivers/media/rc/keymaps/rc-imon-mce.ko
kernel/drivers/media/rc/keymaps/rc-rc6-mce.ko
kernel/drivers/media/rc/mceusb.ko
kernel/drivers/edac/mce_amd_inj.ko
kernel/drivers/edac/edac_mce_amd.ko

Code:

cat /proc/bus/input/devices

I: Bus=0003 Vendor=0471 Product=0613 Version=0100
N: Name="PHILIPS MCE USB IR Receiver- Spinel plus"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 
B: PROP=0
B: EV=120013
B: KEY=c0000 40000000000 0 58000 8001e84000c004 e0beffdf01cfffff fffffffffffffffe
B: MSC=10
B: LED=1f

Cating /dev/input/event3 gives random garbage only on those buttons that work.
sudo evtest /dev/input/event3 didn't show anything when I pressed these buttons:

Multimedia Apps(?)
Windows Media Center
Teletext
Red/Green/Yellow/Blue buttons

Those buttons are exactly the ones I wish to bind to do other functions, WMC - start XBMC, Teletext - Context Menu, R/G/Y/B - Prev Page/Prev tab/Next tab/Next page (For web browsing)
And per my original question, is there any way to make these buttons work?

EDIT:

Originally Posted by mutant_matt

sudo /usr/sbin/lircd -H dev/input -d /dev/input/eventX -n plus irw in another window

The remote stops working (No events are printed in evtest and nothing shows up in lircd and irw). The only thing that happens is that lircd say that a client connected. Once I stop irw, it says a client disconnected.

**mutant_matt** · December 2nd, 2011

As suspected, you're on a current Kernel where the device is using mceusb from the main-line kernel automatically (11.10 comes with 3.0.x kernel and Lirc 0.9.0).

From the cat /proc/bus/input/devices command, are you sure you don't have something like, in addition to event3:

I: Bus=0003 Vendor=0471 Product=0613 Version=0100
N: Name="PHILIPS MCE USB IR Receiver- Spinel plus"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/input/input4
U: Uniq=
H: Handlers=kbd mouse1 event4

For me, some buttons work on the keyboard event (up/down/left/right/OK), some others on the mouse event (Play, Pause, green/red/blue/yellow etc), so to get them all working, a later step is to run two lircd daemons, to link the two together, to provide one set of working button events to the next layer up.

I can't remember the order you have to do everything, but it sounds like you need to setup LIRC to point at the Linux Event Layer (I did this from the Mythbuntu Control Centre which is a graphical UI), and then edit the hardware config file something like this:

/etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Linux input layer (/dev/input/eventX)"
REMOTE_MODULES=""
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="/dev/input/event3"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput"
REMOTE_LIRCD_ARGS=""

Hopefully, this will then allow the test lircd/irw to work? Once that's working, you can worry about remapping/key bindings in an lircrc file for your specific app, and if required, linking two lircds together.

HTH!

Matt

**Lisiano** · December 3rd, 2011

Code:

lisiano@Lisiano-Ubuntu:~$ 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=10000 c020000000000 0 0 700f02000003 3803078f830f401 febfffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=0471 Product=0613 Version=0100
N: Name="PHILIPS MCE USB IR Receiver- Spinel plus"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 
B: PROP=0
B: EV=120013
B: KEY=c0000 40000000000 0 58000 8001e84000c004 e0beffdf01cfffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=04f3 Product=0216 Version=0111
N: Name="USB Mouse"
P: Phys=usb-0000:00:02.0-4/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb3/3-4/3-4:1.0/input/input4
U: Uniq=
H: Handlers=mouse0 event4 
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:07.0/sound/card0/input5
U: Uniq=
H: Handlers=event5 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:10.0/0000:02:00.1/sound/card1/input6
U: Uniq=
H: Handlers=event6 
B: PROP=0
B: EV=21
B: SW=100

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:10.0/0000:02:00.1/sound/card1/input7
U: Uniq=
H: Handlers=event7 
B: PROP=0
B: EV=21
B: SW=100

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:10.0/0000:02:00.1/sound/card1/input8
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=100

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:10.0/0000:02:00.1/sound/card1/input9
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=100

lisiano@Lisiano-Ubuntu:~$

Judging by this line

Code:

H: Handlers=sysrq kbd event3

It's a keyboard only device so guessing no need for multiple Lircd daemons
Here is the original lirc hardware config

Code:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Windows Media Center Transceivers/Remotes (all)"
REMOTE_MODULES="lirc_dev mceusb"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""

Edited that to this

Code:

..snip..

#Chosen Remote Control
REMOTE="Windows Media Center Transceivers/Remotes (all)"
REMOTE_MODULES=""
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="/dev/input/event3"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput"
REMOTE_LIRCD_ARGS=""

..snip..

After a

Code:

sudo service lirc restart

The remote still works and as before, irw stops the remote from working.

EDIT: After a while (Just noticed) the remote stopped working, regardless of irw. Reverting to the old hardware.conf to see if it'll be fixed.

EDIT 2: Reverting hardware.conf fixed it.

**mutant_matt** · December 5th, 2011

Hmm. Sorry, sounds like either driver doesn't fully support your particular device!? Presumably, you'll need help from someone smarter than I, or someone who has already got this exact device fully working, who can give you some pointers.

I tried! Sorry.

Good luck,

Matt

**toto70** · July 30th, 2012

Hello,

I've the same remote and i had the same problem. I spent three days looking for the solution, and i've found the solution here :
http://ben.periton.co.uk/2012/06/con...emote-control/

The only difference is 6. Instead of using :

SUBSYSTEM=="usb" , ATTRS{idVendor}=="0471", ATTRS{idProduct}=="20cc", SYMLINK+="remote", ACTION=="add", RUN+="/sbin/initctl --quiet emit --no-wait ir-ready"

Replace the idProduct 20cc by 0613.