Logitech Elite Keyboard HOWTO
 

OK this is gonna be a brief tutorial on setting up the Logitech Elite Keyboard for use under KDE and X. XFree86 already has a keyboard layout premade for the Logitech-Elite keyboard. It's actually slightly different (the Elite has 2 additional keys, Go and Back) but other than that the layout is the same.

Look in the file /etc/X11/xkb/symbols/inet

At approximately line #1118 you should have an entry like this:

partial alphanumeric_keys
xkb_symbols "logicdn" {
name[Group1]= "Logitech Cordless Desktop Navigator";
...
...
...
}



If your inet file doesn't have this entry then you probably have an older version. I got mine from XFree86 beta. But not to fear you can copy mine (copy everything between the code tags below into /etc/X11/xkb/symbols/inet) into your inet file and it will work just the same. Just choose an appropriate place to paste it, be careful not to paste between any { of these } only on the outside of them i.e. after } and before the next {.


I wanted to make the Go and Back keys work (the two little keys on the left side of the keyboard next to the scroll wheel) so what I did was I copied thew whole entry for the "Logitech Cordless Desktop Navigator" and modified it and renamed it like this:
NOTE: The two bold entries are what I added to enable the two side buttons Go and Back, also I renamed XF86Stanby to XF86User which matches the keyboard.

Now if you go to K Menu -> Configuration -> KDE -> Accessibility -> Keyboard Layout. Now check Enable Layouts and this should allow you to select a Keyboard from the Keyboard model pull-down menu. There are quite a few if you have the latest XFree86 installed. But unfortuneately Logitech Elite is not one of them... yet! Here's what you do to add it to the list.

Edit /etc/X11/xkb/rules/xfree86.lst

Scroll down to the Logitech entries and add a new entry like this.

Once again what is in bold is what I added to the file. NOTE: I put mine in alphabetical order like the rest, I don't think it matters.

So now you can go back to K Menu -> Configuration -> KDE -> Accessibility -> Keyboard Layout and when you use the Keyboard model pull-down menu the Logitech Elite should be listed along with the others.



So now your keyboard is ready to start assigning keys in KDE. But what if you don't use KDE and you want to be able to define the keyboard for say Blackbox or XFce? In that case you need to assign the keyboard from the /etc/X11/XF86Config-4 file. Everything is already setup to do that you only need to edit one more file.

Edit the file /etc/X11/xkb/rules/xfree86. Scroll down to the inet keyboards section
! $inetkbds =

Then I put the lable logielite in the same order I had placed it in the inet file (right after the freedom navigator), like this:
Thats it. Now just edit XF86Config-4 and change your keyboard section like this:

Of course you can verify the keys are working properly by running xev and pressing some keys. I verified the keys I added are working:
As you can see the XF86Go and XF86Back indicate that the keys are working.

Since each Windowmanager/Desktop environment has it's own unique way of assigning actions to these keys I'll not attempt to explain that here. I believe there is another thread similar to this one which deals with HOWTO assign events to Logitech keyboard.

So I think that is about it. I sure hope you found this useful.

<edit>Just a note about Xorg. Everything should be just about the same, if not a little easier. Xorg release 6.8.1 has a keyboard defined which is identical in layout to the Logitech Elite, its called Logitech iTouch Internet Navigator Keyboard SE The only difference I see is there are a couple keys with different names. If you are using KDE just select the keyboard from the Control Panel and everything should work.

It works fine using the 2.4.X kernel and of course some keys don't work with the 2.6.X kernel.


The xkb_symbols "logiinkse" is what you would use in your xorg.conf file. Remember when you switch to xorg the keyboard driver is xkb not keyboard, so you should have that in the xorg.conf file, something like this:
For those of you with USB problems Xorg also has this keyboard, Logitech iTouch Internet Navigator Keyboard SE (USB) that may solve some of your problems.

Re: Logitech Elite Keyboard HOWTO
 

hi "/bin/bash",

I read & follow ur email Logitech Elite Keyboard HOWTO, can u help me about:

How can i assign an event with my new configuration?

thnx in advance

fr33d0m

i forget to say, my Desktop in WindowMaker...

thnx again...

f

OK I edited the thread and added a link to a thread which deals with assigning events to the keyboard. I don't know if windowmaker is covered but if not you'll have to post a thread because I can't help you with that.

Re: Logitech Elite Keyboard HOWTO -> WindowMaker handlers
 

Hi list,

The very useful How-to "Logitech Elite Keyboard HOWTO" have a liltle differences in practice with my Logitech Navigator Keyboard, this are the diff:

In /etc/X11/xkb/symbols/inet the code is:
Modification for XFree86V4 in /etc/X11/xkb/rules/xfree86 can be:

and a modification to ~/GNUstep/Defaults/WMRootMenu file for WMaker window manager:

Thanks for this wonderful tutorial. It works just fine for my keyboard except the four keys: messenger/sms, webcam, iTouch, and Shopping. I have a regular logitech elite keyboard (not wireless.) xev doesn't recognize these keys but a tail of /var/log/messages states (for the "Shopping" key):
What should I do? they keycodes i enter it says are out of bounds? Looking at the inet file in your example that code does match up. It bothers me that the four keys that don't work have consecutive numbering (0x11, 0x12, 0x13, 0x14) curious

I am using gentoo with gnome window manager (regular metacity)

I noticed that too on my keyboard. I knew the keys worked at one time because I had Messenger/SMS mapped to ymessenger and Webcam was mapped to Camorama. So of course at first I thought that I had broken my keyboard and I just ignored the keys. Then when I saw your post I knew we both didn't break the same keys. Some more searching and I discovered the keys worked when I booted my 2.4 kernel. So thats where it stand right now. Something in the new 2.6.x kernel keyboard driver seems to not like those keys. If I find out anything more I'll let you know.

I don't really know if this is a bug or if I'm doing something wrong? I might go ahead and submit a bug report just in case.

I use kernel 2.6 also (2.6.3-gentoo-r1) and it doesn't work. I guess I'll build a 2.4 kernel sometime and see if it works.

getting this to work on 2.6 kernels
 

First off, thanks so much for this information. Didn't think I'd be able to make my logitech elite keyboard use the extra buttons with nix. I had the same probs yall talked about with the 2.6.x kernels, currently I'm on 2.6.3, on gentoo. Anyway, this is how I got it working. First, as root I set the keycodes. You probably want to add this in to a startup script or something so it will do it with every boot.

#For the messenger key
setkeycodes e011 112
# For the webcam key
setkeycodes e012 116
# For the shopping key
setkeycodes e014 118
# For the itouch key
setkeycodes e013 120

Then I edited the xmodmap to use the new keycodes. Mine looks like this:

keycode 144 = logitech_rew
keycode 239 = logitech_sms
keycode 222 = logitech_webcam
keycode 139 = logitech_itouch
keycode 123 = logitech_shopping
keycode 153 = logitech_fwd
keycode 160 = logitech_mute
keycode 162 = logitech_playpause
keycode 164 = logitech_stop
keycode 174 = logitech_voldown
keycode 176 = logitech_volup
keycode 178 = logitech_myhome
keycode 223 = logitech_user
keycode 229 = logitech_search
keycode 230 = logitech_favorites
keycode 233 = logitech_go
keycode 234 = logitech_arrow
keycode 236 = logitech_email
keycode 237 = logitech_media


Now they should all be working. I changed the xmodmap simply because I couldn't find the right setkeycodes number to make them match what you already used. Like setkeycode e011 112 assigns it to key 239, *shrugs*, but this way works and I don't think it bothers any other keys that were defined already.

shryke
I was working with setkeycodes myself. I noticed I couldn't use a keycode above 127?

e.g.
setkeycode e011 127 #This works
setkeycode e011 128 #This tells me the keycode is out of range?


Also the keycodes don't seem to have any logical order, and they are not decimal like they are supposed to be but they are not hex either?

I then built my keyboard driver as a module (atkbd) so I could pass it parameters but had no luck there either. It supposedly has three different key sets you can choose with the set= parameter but I never got it to use anything other than the default set=2. I even modified atkbd.c and set it manually but it still used set 2? But I'm not a C programer so that doesn't prove anything.

Anyways, I still fiddle with it when I get some spare time. If any one figures out the mystery of the setkeycode numbering scheme please "clue me."

/bin/bash
I did read someplace that the keycodes wont go over 127, which is why I used the codes that I did. Also I couldn't figure out the numbering scheme either. I just credited it to the differences in how X and the kernel handle the keycodes. Doesn't X have its own unique keycodes separate from the kernel? Could be wrong *shrugs*

Yes X does have its own way of doing things. Most likely (depending on how your XF86Config file looks) you are probably using the keycodes file in /etc/X11/xkb/keycodes/xfree86. This file basically gives each keycode a unique identifier .
e.g.
<END> = 103;

Also note in the file these lines:
And the keycodes do go up to 255, so I do think there is something wrong with the setkeycodes program.

What you actually did by using the setkeycodes program is you changed the identifier for the keys. If you look in the file /etc/X11/xkb/keycodes/xfree86 you'll see that the keycodes you set the keys to are actually already identified like this:

So actually you could skip the xmodmap file and just edit the /etc/X11/xkb/symbols/inet file if you setup your rc.local file to run the setkeycodes commands every time you boot.

You would just change the four keys in the inet:
I never checked to see if these keys are being used for something else, so don't blame me if there are problems. Also like I said this only applies to you if you use the keycodes file /etc/X11/xkb/keycodes/xfree86.

A question to /bin/bash or anyone:

Kernel 2.6.4 (customized, not stock), SuSE 9.0, Logitech Elite Keyboard, PS/2 (So it's not a USB issue)

How did you come up with the scancodes for setkeycodes? (The e011, etc.) I tried using showkey -s before running the setkeycodes lines you mentioned, and nothing appeared when I hit any of the keys that stopped working (shop, itouch, sms, webcam). After I ran the setkeycodes lines, showkey -s would list keycodes for those buttons, but they aren't like the keycodes that are generated for other buttons (ex: E-Mail, Media, etc). Also, when I run xev to try and see what's going on, the keys that are "patched" back in - SMS, Webcam, etc - generate ButtonPush and ButtonRelease events... ?

The reason I ask how you found the scancodes is that I have another complete set of function keys located on my F-keys row, which used to work under 2.4, but doesn't work under 2.6 anymore.

Finally, did you submit that bug report? I think it might need to be sent in, I don't know why these keys stopped working, but i'm concerned whether there will be enough keycodes in 1-127 to program unique functions for all these buttons.

I just looked at the system logger while pressing the keys to see the first code (e011) you can do this by hitting ctrl+alt+F12 or typing 'tail /var/log/messages' (depending on your system logger.) You should see something like this:
Which also explains why xev wont show them

So is it possible to get all the keys working under 2.6? (F keys too?) I just bought a Logitech MX Duo a few days ago, and i've tried a few things but maybe i don't quite understand what to do. Can it be done at all, or will it take a fix in the kernel?

There's a mention of a logitech-keyboard-fix in the 2.6.5-rc3-mm4 patch, but it says it's a fix for something that broke in 2.6.5-rc2 I think. Does anyone know anything more about it?

The F-keys should work out of the box. Just hit the F-Lock key. Other than that read the previous posts to get the other keys working.

Sorry i don't think i said that correcctly, by F-keys I'm mean the special keys (New, Reply, etc.) with F-Lock off. Do they work? I don't get anything in xev or with #tail /var/log/messages (though i may not be doing it properly).

And the 4 multimedia keys, I've tried a few things from the thread. Strange thing is, xev shows them as mouse buttons. Messenger is button 1, Itouch is button 2, and Webcam is button 3, and Shopping is 6 (i think). Does this happen for anyone else?

I have a Logitech Cordless Desktop Navigator keyboard/mouse combo. When plugged into the usb port, the Messenger, Webcam, iTouch and Shopping buttons all seem to think they're mouse buttons. This happens under 2.4 and 2.6. Everything works fine using the ps/2 port under 2.4, and the apparently usual problems occur using ps/2 under 2.6

Anybody else had this problem?

Look at the post before yours :)

Well at least we're not alone. I'm getting along fine without the buttons.

he he - d'oh! sorry bout that. Will try and be a little more attentative when reading before replying next time.

NON-WORKING Keys
 

The Keys That do not work are:
New
Reply
Forward
Send
Save
My Documents
My Pictures
My Music

I followed your walkthrough to the LETTER and it doesn't work for those keys :( :confused: :scratch: :newbie:

Same problem
 

I've got Logitech Elite keyboard, running Slackware 9.1 on kernel 2.6.5 with Dropline Gnome 2.6.0. I got my keyboard working, thanks to this thread, but have the same problems that other people with 2.6.x kernel have (i.e. keys: iTouch, Shopping, Messenger/SMS, Webcam and F-Keys do not work)

Has anybody find solution to this problem since the last post?

ZiGiE
I contacted the author of the atkbd module. That was back in early April and I have received no reply as of this date. It seems to me the problem would be with the kernel module since everything works with the 2.4. I check every new kernel to see if the atkbd module has any changes but as of 2.6.5 it still doesn't work.

hi. same problem here.

I checked dmesg some times when I was compiling/starting to run kernel 2.6.5 and I found out that at boot time, not only a keyboard was found on the usb port but also a logitech mouse was found. (same usb channel number)
maybe the confusion comes from that?

also my media key isn't mapped correctly after /bin/bash 's walkthrough. didn't think it could be that easy setting up the keyboard extrabuttons, thanks for the tips.

My personal fix
 

I always come back to this post when I'm setting up my logitech elite ps2 keyboard on any linux distro, and it always gets me close but not all the way. I have a super fast fix that I'm putting here because my keycodes argue with all of the others on the internet, so this is for all those of y'all who want a super fast fix and have my keycodes.

There's no need to create new keyboards or anything like that, as far as I can see. All I do is create a file in my home directory called .xmodmaprc, (and some people have default xmodmap files that are executed, you might be able to use those.) Then I have xmodmap execute the file on startup, and there are different ways to do this - in KDE I put a shortcut in my ~/.kde/Autostart folder that runs the command "xmodmap ~/.xmodmaprc" - obviously without the quotes. In gnome I used to do this differently, there was a menu item called something like session options or something ["start menu", preferences, more preferences, sessions], anyway it allowed you to put in startup commands. I put the same thing in there, along with other programs, like xscreensaver -nosplash and imwheel, etc.

After you create the xmodmaprc file and have executed it, you are ready to start using the keys. It's that easy. I don't get the whole creating a new keyboard model or anything. In kde 3.2+ you can easily map them with khotkeys (have fun in kde 3.1- (come out from under your rock)) and in gnome you should use the metacity config editor. The command for that is, I think, gnome-config-editor ["start menu", system tools, more system tools, configuration editor] or something like that, it should come up if you start typing it correctly in the run dialog, and the icon is the red vw bug with the trunk up. Here's the xmodmaprc file for MY Logitech Eliete ps2 keyboard.

This is if you don't want kmix to do your audio for you, and you'd rather use aumix or other, you have to map your keycodes to something other than the easy-to-read codes XF86AudioMute, etc. I use eject, poweroff, and wakeup because the elite doesn't have these keys. There are a slew of mapable names, you can call these any of them - just don't try making your own.
keycode 144 = XF86AudioPrev
keycode 145 = XF86Messenger
keycode 146 = XF86WebCam
keycode 147 = XF86iTouch
keycode 148 = XF86Shop
keycode 153 = XF86AudioNext
keycode 160 = XF86Eject
keycode 162 = XF86AudioPlay
keycode 164 = XF86AudioStop
keycode 174 = XF86PowerOff
keycode 176 = XF86WakeUp
keycode 178 = XF86HomePage
keycode 223 = XF86Standby
keycode 229 = XF86Search
keycode 230 = XF86Favorites
keycode 236 = XF86Mail
keycode 237 = XF86AudioMedia
keycode 233 = XF86Go
keycode 234 = XF86Back

This is if you DO want kmix to do your audio for you (kde only, i think)
keycode 144 = XF86AudioPrev
keycode 145 = XF86Messenger
keycode 146 = XF86WebCam
keycode 147 = XF86iTouch
keycode 148 = XF86Shop
keycode 153 = XF86AudioNext
keycode 160 = XF86AudioMute
keycode 162 = XF86AudioPlay
keycode 164 = XF86AudioStop
keycode 174 = XF86AudioLowerVolume
keycode 176 = XF86AudioRaiseVolume
keycode 178 = XF86HomePage
keycode 223 = XF86Standby
keycode 229 = XF86Search
keycode 230 = XF86Favorites
keycode 236 = XF86Mail
keycode 237 = XF86AudioMedia
keycode 233 = XF86Go
keycode 234 = XF86Back

And the cream of the cream, my setup and my commands (this one is just for my own convenience)

keycode 145 = XF86Messenger //gaim
keycode 236 = XF86Mail //thunderbird
keycode 146 = XF86WebCam //sudo /usr/sbin/synaptic (debian apt-get gui)
keycode 147 = XF86iTouch //firefox http://aaronsmiley.deviantart.com
keycode 148 = XF86Shop //firefox http://www.newegg.com
keycode 229 = XF86Search //firefox http://www.google.com
keycode 230 = XF86Favorites //firefox http://www.aaronsmiley.com
keycode 160 = XF86Eject //aumix -v -25 (aka mute - rather than mute I go down by increments of 25 for faster volume lowering)
keycode 237 = XF86AudioMedia //aumix -v -25 (aka media - rather than unmute I go up by increments of 25 for faster volume raising)
keycode 174 = XF86PowerOff //aumix -v -2 (aka volume down - aumix lowers system volume by increments of 2)
keycode 176 = XF86WakeUp //aumix -v +2 (aka volume up - aumix raises system volume by increments of 2)
keycode 162 = XF86AudioPlay //xmms -t (this is the same as play/pause, if you want play, just use -p or pause -u)
keycode 144 = XF86AudioPrev //xmms -r
keycode 153 = XF86AudioNext //xmms -f
keycode 164 = XF86AudioStop //xmms -s
keycode 178 = XF86HomePage //~
keycode 223 = XF86Standby //xscreensaver-command -lock
keycode 233 = XF86Go //konsole
keycode 234 = XF86Back //sudo konsole

I hope this was of some help. Took me a couple hours to put together, but I know it'll save me a hundred hours down the road, and hopefully help a few others, too.

Edit: I went back to gnome and looked where things were. I have added them in square brackets.

Hi there.

Thanks to this thread I was able to make some of the keys of my Cordless Elite Keyboard work, but all mentioned special keys (Shoppinh, iTouch, ...) still don't work. Has anybody found a solution? I'm using Kernel 2.6.3-15mdk.

Activate the last 5 Keys of Elite Keyboard
 

For your convience all the steps described all above.... (thx to thouse guys above...)
... inclusive the last 5 Keys... Messenger / WebCam / Sleep / Shopping / iTouch...

1.Step make all Keys Known to kernel
- open a vim: tail -f /var/log/messages
now push all keys you belive not known to kernel it will show:
kernel: atkbd.c: Use 'setkeycodes e011 <keycode>' to make it known.
kernel: atkbd.c: Use 'setkeycodes e012 <keycode>' to make it known.
kernel: atkbd.c: Use 'setkeycodes e014 <keycode>' to make it known.
.
.
.
write thouse codes down yuo will need them...
- vi /etc/rc.local (or any place that is startet on boot)
#logitech elite keyboard solve 4 dead key problem
#For the messenger key
setkeycodes e011 112
# For the webcam key
setkeycodes e012 116
# For the shopping key
setkeycodes e014 118
# For the itouch key
setkeycodes e013 120
# For pushLeftWheel
setkeycodes e016 127

2.Step make Keyboard known as described on many places like here (thx to thouse guys)
vi inet
vi xfree86.lst
vi xfree86
(just read thread what to do)

3. Step
vi /usr/X11R6/lib/X11/XKeysymDB
look here what names are around you may add a name f.ex.
XF86Shopping and you use any free number here (does not matter as long it is not double)
4. Step
xmodmap -pke > .Xmodmap
edit .Xmodmap with names out of step 3
xmodmap .Xmodmap <-- to make it work

4a.Step following commands have to be activated after your KDE started!!
I put them in autostart
# activate xmodmap settings
xmodmap ~/.Xmodmap
# make pushLeftWheel be equal to Rerturn <--- just in case you like that
xmodmap -e "keysym Menu = Return"

5.Step
xev <--- see here how all your keys get a meaning...
KeyRelease event, serial 29, synthetic NO, window 0x2a00001,
root 0xb3, subw 0x0, time 3704650, (83,119), root:(1367,932),
state 0x10, keycode 123 (keysym 0x1008ff93, XF86Shopping), same_screen YES,
XLookupString gives 0 bytes:
6.Step
assign now actions to your keys f.ex with
kcontrol (KHotKeys)
7.Step
enjoy it having such a incredible confortable thing like a working keyboard
Poor, damned Windows users that never will get that good feeling having a
working keyboard... tztztz

Greetings LoboCobra RHCE :p :p

I tried once more and I finally got all the keys working :)
except one. the User key, although xev tells me its keycode is 223 and /usr/X11R6/lib/X11/keycodes/xfree86 tells me keycode 223 in the 'basic' setup should be named <I5F>, I wrote it down in /etc/X11/xkb/symbols/inet to make it work like I did with the other keys but it doesn't work: xev doesn't tell me it received the X special signal given in .../inet file.

I managed to get some extra keys working but then put the Logitech Bluetooth in hci-mode in order to let it work as an actual hub which connects to other devices as well and now *no* extra key does work anymore. In this post I describe what exactly I did, my Kernel is 2.6.8.1-7. xev doesn't respond to the extra keys as well as there aren't any messages in the syslog.

Any ideas? :/

Is there any way to get keyboard scan codes then from dmesg? I've tried showkeys w/ the different ways and it doesn't work. The reason is I would like to remap the scroll wheel if possible and use it to switch desktops, and not to go up and down. Or being able to unbind keys would be good. My webcam key and mute key are bound to the same keycode.

Hi /bin/bash
 

Hi I followed your instructions for adding the logitech elite keyboard to the layout and as well as the inet addition, I even went as far as changing the x86config-4 layout but nothing seems to work for me on both USB, and PS/2. When I press the iTouch key i only the "unclutter windows dialog" and the menu when I press the Webcam key. Do you have any idea why this wouldn't work for me?

Mandrake Linux 10 Official
Logitech Elite

I had two problems--first, the f-lock and mute buttons were switched when I opened my Logitech Cordless Elite Duo. After emailing Tech support, they suggested that I pull out the batteries and discharge the capacitors. This solved that problem. But another previously existing problem persisted--that is, four buttons, Messenger/SMS, iTouch, Shopping, and My Home still did not work. They didn't even return a keycode in xev.

Tech support offered to have me return my keyboard for replacement. But I need my keyboard to do work, so it'd be an inconvenience to return it. Especially if this problem will occur anyways, which I do suspect because my keyboard was 100% functional in Windows.

Can anyone with this keyboard confirm that there are no codes for Messenger/SMS, Webcam, iTouch, Shopping? Just to confirm that we have the same keyboard, my model is Y-RJ20.

I have solved the functions
 

I solved the functions using gnome and assigning the keys. I tried the kde version of doing things but nothing changed.

Mandrake10.1
Xorg6.8.2
Kernel2.6.8-1Custom
DELL

apachedude: this was mentioned in the previous posts I think. those buttons are generally the ones not functionning by default in Linux. what you need to do first is to tell the kernel that these buttons correspond to a keycode. then xev will tell you what keycode is catched when pressing the button. you can then configure X to match these keycodes to some command names that can be used by any window manager to do whatever you want.

for myself, I tried plugging my keyboard in USB after getting it to fully work in PS/2 and some buttons like SMS, webcam and My Home changed to button presses instead of key presses in xev. any clues? (plugging the keyboard in USB was supposed to fix the problem of having too many keycodes at the same time)

I thought so too
 

I had the keyboard under KDE plugged in as usb but the whole addition of adding the keyboard to the xkb didn't work for me either even after changing the layouts and creating my own. I just plugged it back in as ps/2 and use gnome, I was able to assign some keys to it, not all work though. This might help you out:

http://www.linuxquestions.org/questi...hreadid=125333

This is what I followed but I didn't get any results, nothing changed for me. I haven't really persude it so I could have made a mistake.

Logitech Media keyboard with 2.6.10-gentoo-r4
 

Okay, instructions look simple enough to follow, but I have a small problem in following the instructions previously posted as this is what is in kernel logs of my system when I press the non functioning keys:

Otherwise my keyboard works currently rather nicely.

My customizations to /etc/X11/xkb/symbols/inet:
The extended function keys are just waiting there for proper settings, but I included them in one format there for completeness. I based my configuration on the logiinkse settings.

/etc/X11/xkb/rules/xorg
/etc/X11/xkb/rules/xorg.lst
/etc/X11/xkb/rules/xorg.xml
/etc/X11/xkb/symbols.dir

Well If You...
 

Well if you read the tutorial you will see that he/she or they seem to be using XFree86, now you and I are using Xorg, and I tried this on Xorg, and didn't have any luck at all, so it could be because of that, I will give it a try again and post what I did, that last time I did try it some keys worked, the volume kept crashing but it got working, so give me a day and I will post up what I have done if it works.

Web.

Just a note about Xorg. Everything should be just about the same, if not a little easier. Xorg release 6.8.1 has a keyboard defined which is identical in layout to the Logitech Elite, its called Logitech iTouch Internet Navigator Keyboard SE The only difference I see is there are a couple keys with different names. If you are using KDE just select the keyboard from the Control Panel and everything should work.

It works fine using the 2.4.X kernel and of course some keys don't work with the 2.6.X kernel.


The xkb_symbols "logiinkse" is what you would use in your xorg.conf file. Remember when you switch to xorg the keyboard driver is xkb not keyboard, so you should have that in the xorg.conf file, something like this:
<edit> For those of you with USB problems Xorg also has this keyboard, Logitech iTouch Internet Navigator Keyboard SE (USB) that may solve some of your problems.

Pity there isn't directly a config yet for the Logitech Media Keyboard, but then again I was personally at least going to share my experiences in getting this working with xorg project. Perhaps they would add it to future versions. :)

Hoary HOWTO
 

I've just uploaded a quick mini-HOWTO for making these things work in Hoary. It's actually aimed at the Duo MX and Cordless Desktop MX bundles (an Elite Keyboard and an MX700 sharing a receiver), but each section is applicable to the standalone models.
Let me know if it's any use.

HOWTO link

Just to add to this thread, here's the way I get my Logitech Elite working by following this guide.

Unfortunately, I too do not have the Messenger/SMS, Webcam, iTouch, and Shopping keys working. I tried messing with a few things in this thread but didn't get it to work.

In my experimenting I did notice that xev gave a different keycode for the above keys with every new session.

how do you pick what keys to assign using setkeycodes? I want to assign numbers to the un-F-locked keys (new, reply, forward,...,My Music). I looked at /var/log/syslog to get the codes i need but not what to assign.

so syslog says this:
so i sort of randomly started counting up from 128:
i'm pretty sure this isn't going to work because i have no idea what the real keycodes should be. Any ideas?

I am having some trouble with sorting out my logitech cordless keyboard.

The system recognises the keyboard and the keypresses. I have been trying to assign actions to the keys using khotkeys.

For example I can get mute to work by getting the key to make a DCOP call to kmix.Mixer0.mute(1).

The problem is that I can get this to bind to a key combination like Win-Mute. However I cannot get this to bind to the mute button alone. If I press mute I get a box coming up saying mute on or mute off but it doesn't actually have an effect.

Similary I can assign volume changes to win-volume+ but volume+ by itself brings up a volume display and actually changes the volume in the headphones (The call being kmix.Mixer0.increaseVolume(1) when I want kmix.Mixer0.increaseVolume(0).

Clearly something somewhere is overriding the actions taht I am trying to assign to my keys. But what?

anyone have an update for modular xorg 7.0? maybe it's just me, but all the files are either missing or moved, and I can't find them.

sweetbrett

It depends on how the X11R7 packages were built. The config files are not necessarily in /etc/X11 any more but would be in $PREFIX/etc/X11, by default this would be /usr/local/etc/X11. Also it is possible to specify --sysconfdir when building the modular xorg and place the config directory anywhere you want. I would suggest you look for the xserver Xorg and the config directory will probably be located relative to that directory ../etc/X11. So if the Xorg file is in /usr/local/bin then the config files will be at /usr/local/etc/X11.

<edit> Sorry the above isn't correct. The new modular xorg has the config files in:
$PREFIX/lib/X11
and
$PREFIX/share/X11

The xkb files are in the latter.

I've been ripping my hair out trying to figure this crap out.

Someone help... I have a Compaq Easy Access Keyboard (8 key), running under PCLinuxOS.

I have xorg-x11 6.8.

uname -a prints:
2.6.16.27.tex1.lve #1 Mon Jul 31 15:59:12 WST 2006 i686 Pentium III (Coppermine) unknown GNU/Linux

in KDE, I set the keyboard option to my keyboard.

In xorg.conf, I have the proper keyboard layout (compaqeak8).

I can't get khotkeys working. I type it in and nothing happens.

I did, however, set up lineakd (Linux Easy Access Keys Daemon) with the proper options. However, the keycodes are all over 127 in the defs file.

I have the same setkeycodes issue that everyone else had (out of range, it only goes up to 127, etc)

I've been doing this forever and I can't get it. I have every other piece of hardware working nearly perfectly (DRI included). Once this is done, I can get this PC shipped out to my pastor. In other words, the sooner the better!

Howdy,
Bit of a noob at linux but am really enjoying it. With the help of this forum ive been able to get all my media buttons working except the usual 5 buttons (SMS,Itouch...etc). I did manage to get those buttons working (sort of) by following "lobocobra" guide on pg 2. By sort of i mean that i went into konsole became a super user and typed in "setkeycodes e011 112" ...etc for all 5 of them.
I then went into xev to get the keycodes for each button and then modified .Xmodmap to correspond the keycodes given with the "XF86messenger"
eg.
keycode 239 = XF86Messenger
keycode 222 = XF86WebCam
keycode 139 = XF86iTouch
keycode 123 = XF86Shop

Once i changed the keycodes to the right ones(as above) and then logged out and logged back in again thse keys could now be binded with khotkeys. It all worked great until...i rebooted. Now those buttons dont have keycodes when i chek with xev. It works fine (again) if i go into konsole->become a su-> type in that
"setkeycodes e011 127"...etc AGAIN! I dont have to do anything else after doin the setkeycode thing, which tells me that it has to be done every time i reboot (not log in) Which is fine as ill just setup a shortcut(or several) in ~.kde/autostart like i did with .Xmodmap. Problem is that u have to be super user to do that "setkeycodes...thing. Can any1 tell me if theres a place where i can put the shortcuts so that they are already in Super User mode, and so that i dont have to envoke them every time i restart. Or what i can do to make it automated.
I am running opensuse 10.1 with kde and Logitech Elite Keyboard (corded PS/2)
thanks in advance (suks to be a noob)

There should be a file called "rc.local" or "local.start" or something along those lines in your /etc directory somewhere... I don't recall what it's called in SuSE, but that's where you would add the setkeycodes lines. and you can add other stuff in there too. Also I skipped the .Xmodmap step, I figured I was forgetting something <_<

I have to go see if I can get the keys working if I add the Xmodmap stuff.

sonnicbhoc,
yeah i sort of figured that out myself its not in the guide, but if you have a logitech elite PS/2 those "setkeycode"...things should work for you just type them all in (as su) run xev and the keycodes should be the same as the ones i have above then change .Xmodmap accordingly (make sure you have
"xmodmap ~/.Xmodmap" (as a shortcut) in your ~.kde/autostart) and log out and log in, then go xev to chek then do khotkeys. But just beware that if you reboot it wipes thos "setkeycode...thingy, but .Xmodmap and khotkeys will stay. Ill have a look at what you sed with etc/

HHHHHHEEEEEEEEEEELLLLLLLLLLLLLLLL YEAH!!!!!!!!!!!
5 other buttons work now.
For suse users read previous posts then go to
/etc/init.d/boot.local
Open with kwrite or kedit or whateva

add this to end
#For the messenger key
setkeycodes e011 112
# For the webcam key
setkeycodes e012 116
# For the shopping key
setkeycodes e014 118
# For the itouch key
setkeycodes e013 120
# For pushLeftWheel
setkeycodes e016 127

and save (will have to get permission)
Reboot=>Check with xev(to c if yor gettin keycodes)=>bind with khotkeys( or keyboard shortcuts)

HAve fun :-p