Keymapping

[napsilan]

I have a gyration MCE remote. Out of the box, the arrows, numbers, mouse, and enter/esc buttons worked. In xev, the basic multimedia functions were recognized (play, pause, volume, skip, previous, stop), and even the volume keys worked in kde. However, there are other keys on the remote that don't even generate anything in xev when I hit them. Some of these are the input key, channel up/down keys, and menu key. Is there a way to map these keys if xev doesn't catch them? I assume right now the remote is just using the build-in USB keyboard and mouse drivers (usb_hid). Do I need to set up LIRC, even though the remote is RF and not IR?

[napsilan]

starting to answer my own question. http://gentoo-wiki.com/HOWTO_Use_Multimedia_Keys says that I need to check dmesg and edit /etc/conf.d/local.start

Originally Posted by gentoo wiki If pressing a key doesn't do anything at all (ie, xev produeces no output), run the following command in an X terminal: dmesg You will probably see some lines like these: Output of dmesg atkbd.c: Unknown key released (translated set 2, code 0x96 on isa0060/serio0). atkbd.c: Use 'setkeycodes e016 <keycode>' to make it known. This means that the kernel doesn't have keycodes mapped to your keyboard's scancodes. You will have to add one line in /etc/conf.d/local.start for each missing key as follows: /etc/conf.d/local.start setkeycodes e008 136 setkeycodes e016 150 ... And so on ... Where the first number (e008) is what you see in dmesg, and the second number (136) is an unused keycode in your kernel. In general you can find a good keycode by taking the last 2 digits of this first number, converting it from hex (base-16) to decimal (base-10) and adding 128.

/etc/conf.d/local.start isn't used in ubuntu, I think it's /etc/rc.local instead

[napsilan]

looks like evrouter does the trick for most keys

http://www.bedroomlan.org/~alexios/coding_evrouter.html

I attached the evrouter dump codes for the remote. I still can't get any output from the "TV home", "setup menu", "Last" and "Input" keys.

[napsilan]

it looks like evrouter doesn't work with openbox for some reason.

xlib: connection to ":0.0" refused by server
xlib: no protocol specified

evrouter: could not open display ":0.0"

Anyone know how to get xlibs or whatnot working with openbox?

[napsilan]

needed to run

xhost +local:root

to fix that issue. Still not getting it to correctly autostart though. My /home/mythtv/.config/openbox/autostart.sh looks like

xhost +local:root &
sudo evrouter --config=...... /dev/input/......

I have the mythtv user set to sudo both autostart.sh and evrouter w/o a password.

[napsilan]

Got it working, although this is probably NOT the "proper" way to do it.

I left /home/mythtv/.config/openbox/autostart.sh as it was

xhost +local:root
killall evrouter
sudo rm /tmp/.evrouter*   #removes a previous lock file
sudo evrouter --config=/home/mythtv/Evrouter_gyration.txt /dev/input/by-id/usb-Gyration_Gyration_RF_Technology_Receiver-event-mouse /dev/input/by-id/usb-Gyration_Gyration_RF_Technology_Receiver-event-kbd &

Then I set it so that the mythtv user could sudo both evrouter and rm without a password. This was done with visudo. Having a password-less rm is the thing that made me save this idea for last. If anyone has a better way to allow the mythtv user to delete the evrouter lock file, please say so.

mythtv ALL=NOPASSWD: /usr/bin/evrouter
mythtv ALL=NOPASSWD: /bin/rm

Finally I added the autostart file to the end of the /usr/share/mythtv/startmythtv.sh file, right before "exec mythfrontend." This is the script called by the mythtv-xsession.desktop file. For some reason, the autostart script wasn't being run normally, so this was needed.

sh /home/mythtv/.config/openbox/autostart.sh &
#start mythtv frontend software
exec mythfrontend

This finally automatically starts up evrouter correctly on login and lets it map the remote keys (except those 4 that it didn't recognize).

I attached the evrouter deb and my current config file if anyone wants them.

[napsilan]

everytime mythtv updates, I have to re-edit the startmythtv file again.

[modulok]

wow, a whole thread talking to yourself...good stuff though!

I found the remote/keyboard combo on buy.com for cheap ($65) and was thinking about getting both. Right now I use the Logitech Dinovo Edge and trying to get the ATI Remote Wonder to work (without much success in mythtv).

Wondering how the remote works with mythtv (0.20.2)...and do you have the universal one? does it connect nicely to other components?

[napsilan]

wow, a whole thread talking to yourself...good stuff though

Yah basically. Started out as a request for help but I figured that others might find the info useful

I think my remote is slightly unique in that it registers as a keyboard and mouse, not as an actual remote. Have you tried looking at the LIRC info? That is the program/module that takes care of IR remotes, which I believe the ATI remote is.

Can you get any input from your remote at all? For example, if you are in a terminal and hit the numbers on your remote, will it enter those numbers into the terminal? Or does it not work at all? Mine was able to do that right when I plugged it in, so I just had to keymap the wierd keys, not get the whole thing working.

LIRC page
http://mythtv.org/wiki/index.php/LIRC

ATI remote wonder pages, depending on which model you have
http://mythtv.org/wiki/index.php/ATI_Remote_Wonder
http://mythtv.org/wiki/index.php/ATI_Remote_Wonder_II
http://mythtv.org/wiki/index.php/ATI_Remote_Wonder_Plus

[modulok]

yup, that first link is the remote I have....but I just ordered the gyration kb/universal remote combo.

IS that the remote you have, the gyration universal media center remote?
http://www.gyration.com/c-3-remotes.aspx - I got the combo coming, but remote is the same in both I think.