Multimedia keys missing

onearm · 2006-09-08 10:15:48

Hi all,
I have a Samsung 4500DP keyboard which has the aforementioned multimedia keys. I'm using keytouch to bind them to some command and this has worked very well till 3 days ago. The strange thing is that they work partially, in the sense that the keys are 20 in total but now only 11 of them work.
I use both kde and openbox 3.3, Xorg 7.0, kernel 2.6.17-beyond. I thought it could be a problem in initialiazing the driver from xorg because xev doesn't see the key pressing anymore, but the relevant part of xorg.conf:

Section "InputDevice"     
          Identifier  "Keyboard1"
          Driver      "kbd"
          Option      "AutoRepeat" "500 30"
  # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
          Option      "XkbRules" "xorg"
          Option      "XkbModel" "samsung4500"
          Option      "XkbLayout" "it"
  EndSection

has not been modified at all and the only relevant package upgrade in the last days has been keytouch itself.

I don't know where else to look :?

patroclo7 · 2006-09-08 11:18:47

Go in a console and press those same keys, then look in the system log. Do you see some messages from atkbd, complaining about "unknown key released"? This could explain why xev does not see them, and it is very easy to solve (the solution is in one of those messages from atkbd).

onearm · 2006-09-08 12:52:24

You were right, the keys were unknown to atkbd.
I tried, has suggested in the log, to put this in rc.local (sorry, I didn't know where to look for choosing the right scancodes, I tried this ones)

setkeycodes e002 200
setkeycodes e003 201
setkeycodes e004 202
setkeycodes e005 203
setkeycodes e006 204
setkeycodes e026 205
setkeycodes e059 206
setkeycodes e009 207
setkeycodes e00a 208

and this in .Xmodmap

keycode 200=XF86ScreenSaver
keycode 201=XF86Launch2
keycode 202=XF86Launch3
keycode 203=XF86Launch4
keycode 204=XF86Launch5
keycode 205=XF86LaunchA
keycode 206=XF86LaunchB
keycode 207=XF86LaunchC
keycode 208=XF86LaunchD

now the system "see" the keys but some doesn't do what supposed to do with my keytouch configuration. I guess I have misconfigured the keycodes/scancodes, anyone knows where to look for more information about how to configure correctly this? thx

patroclo7 · 2006-09-08 13:11:57

I admit that I have no experience with xmodmap and keytouch. But once I have assigned the scancodes in rc.local (they are not right wrong, it is enough to choose quite high number so to not interphere with default scancodes of your console keymap), xev is immediately able to see them and to give you the information needed to bind them to execute a specific command. I do this last part with xbindkeys (if you run it with the -mk option you get the same codes you can obtain through xev). So i do not think you really need to pass through xmodmap.

onearm · 2006-09-08 13:30:57

I understand better now. Ok, dumped xmodmap completely, I've modified the setkeycodes command in rc.local with the number that xev gave me. The keys still don't work.
The strangest thing is that the keycodes that xev give me are different from those with xbindkeys -mk
I think I'm off to reading the manpages of these commands and see what I can grok from them.
Thx again

patroclo7 · 2006-09-08 14:03:59

No... I made a mistake and you misunderstood something else. First, the misunderstanding: you do not have to use the codes xev gives with setkeycodes. In setkeycodes you map the codes you found from atkbd in system log to arbitrary numbers (let us say 250, 251 and so on). These arbitrary numbers will be then useful only if you want to use those keys when in console.
Otherwise, if you want to use them only in X, you can do two things:
1) use xev and xmodmap;
2) use xbindkeys, mapping the code given by xbindkeys -mk to a certain command. (in ~/.xbindkeysrc).

The code given by xbindkeys -mk is that of the format c:<foonumber>

I was wrong in thinking that xev codes and xbindkey codes are the same. I apologize.

onearm · 2006-09-09 08:37:06

Don't worry, you have nothing to apologize.
Pratically xev+xmodmap and xbindkeys are two way of doing the same thing but they can't, obviously, be used together.
After having done some more researches today I'll try to make it all work.

Snowman · 2006-09-09 18:57:39

Update to keytouch 2.2.1-2 and put back the keytouch daemon in the DAEMONS array of rc.conf
For some reason, I tought it was no longer needed so I removed it. My keys were working fine but it is still needed for some people. Sorry about that.

onearm · 2006-09-10 08:34:34

yeah, I noticed that. No problem now with keytouch as daemon (I wonder why it's not always necessary running it at start, maybe different keyboards...)

Snowman · 2006-09-10 22:28:38

The keytouch damon runs keytouch-init. It's mainly used for USB keyboards. If you want to know more: http://dl.sourceforge.net/sourceforge/k … manual.pdf

onearm · 2006-09-11 09:22:10

thx /me reading

Arch Linux

#1 2006-09-08 10:15:48

Multimedia keys missing

#2 2006-09-08 11:18:47

Re: Multimedia keys missing

#3 2006-09-08 12:52:24

Re: Multimedia keys missing

#4 2006-09-08 13:11:57

Re: Multimedia keys missing

#5 2006-09-08 13:30:57

Re: Multimedia keys missing

#6 2006-09-08 14:03:59

Re: Multimedia keys missing

#7 2006-09-09 08:37:06

Re: Multimedia keys missing

#8 2006-09-09 18:57:39

Re: Multimedia keys missing

#9 2006-09-10 08:34:34

Re: Multimedia keys missing

#10 2006-09-10 22:28:38

Re: Multimedia keys missing

#11 2006-09-11 09:22:10

Re: Multimedia keys missing

Board footer