Extra keys not working on Logitech Cordless Desktop LX710
 

Some do, some don't.

I am running Debian unstable, kernel 2.6.32-trunk-amd64.

The box says it's a Logitech Cordless Desktop Wave.
lsusb says it's a "Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser".

The zoom keys and the other key on the left don't work.
The configuration and camera key don't work.
The music and media centre keys both think they're the configuation key.

However, the Previous, Next, Stop, Play, Mute, Volume Up/Down, Calculator, and Sleep keys work.

Following is heaps of spam. I hope somebody can make some sense of it. :P

A while ago when I first got my Logitech MX 3000 keyboard I spent a good while trying to get all of the additional function keys to work. In the end I gave up -- I couldn't find a fully reliable solution. You may find keytouch [http://keytouch.sourceforge.net/keyboards_logitech.php] of use, but I didn't use it myself. You should also be able to reconfigure the function of some of the media keys by using xmodmap. However, there does seem to be an issue with this in that Logitech USB keyboards will sometimes change some of the key codes on reboot.

Overall, although it's annoying not to be able to use all of the additional keys, the effort trying to get them to work just didn't seem worth it.

I've tried keytouch. It doesn't actually pick up the key events.
xev doesn't pick up the key events either.
getkeycodes shows almost all zeroes.
setkeycodes fails with some warning along the lines of KDSETKEYCODE blah blah.
(I'm not actually at mycomputer right now, so sorry about the vagueness of this message.)

And I know, I've lived with it for one or two years now; I was just hoping there was an answer somewhere.

*bump*

*bump again*

Same problem here with the same Logitech desktop.

Hoping that pinging this question will spur any new viewers to answer.

The main issue is that these missing keys do not seem to produce scancodes. Both xev and showkeys do not register any key presses for these keys. There are no messages in dmesg from atkbd.c indicating an unresolved scancode.

I found a reference to an IBM keyboard that will not send scancodes without being first initialized. See section 6.2 here. Perhaps this logitech keyboard does the same thing?

Is there some deeper layer of logic filtering out these events or is there some driver-hardware protocol that needs to be invoked to get this desktop to send the scancodes?