Compaq 6510b HAL keymap quirk does nothing

Vladislav IV · 2008-06-25 13:35:10

Hi all !

I wanted to drop keytouch and try out hal for my laptop's bonus keys. I added all the infos needed in the right fdi file :

<match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" contains="6510b">
          <append key="input.keymap.data" type="strlist">e001:fn_esc</append>    <!-- FnEsc -->
          <append key="input.keymap.data" type="strlist">e008:presentation</append>    <!-- presentation -->
          <append key="input.keymap.data" type="strlist">e009:battery</append>    <!-- FnF8 (battery) -->
          <append key="input.keymap.data" type="strlist">e00a:screenlock</append>    <!-- FnF6 Lock -->
          <append key="input.keymap.data" type="strlist">e059:info</append>    <!-- I key -->
          <append key="info.capabilities" type="strlist">input.keymap</append>
</match>

In fact, it was a copy/paste of another section, with only a removed key binding. The codes was OK.

After restarting hal, I checked the keymap in use :

$ lshal | grep keymap
  info.callouts.add = {'hal-setup-keymap'} (string list)
  info.capabilities = {'input', 'input.keyboard', 'input.keypad', 'input.keys', 'input.keymap', 'button'} (string list)
  input.keymap.data = {'e001:fn_esc', 'e008:presentation', 'e009:battery', 'e00a:screenlock', 'e059:info'} (string list)

It seemed OK. But when I launched xev and pressed any key, for example the info key, no events were triggered and the following was immediately added to /var/log/everything.log :

Jun 25 14:45:54 portable atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
Jun 25 14:45:54 portable atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
Jun 25 14:45:54 portable atkbd.c: Unknown key released (translated set 2, code 0xd9 on isa0060/serio0).
Jun 25 14:45:54 portable atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.

After that I found a patch for my laptop on the hal quirks site (http://www.nabble.com/Keymap-patch-for- … 55220.html), but it did not worked. The extra keys are always unknown.

I searched the Web but don't found anything on this problem. Any idea on what can cause it ?

Kernel 2.6.25, hal 0.5.11-1, Arch up-to-date.
DAEMONS=(syslog-ng acpid @cpufreqd @sensors network openntpd netfs crond @alsa @hal !keytouch slim)

.:B:. · 2008-06-25 14:09:34

[offtopic] Afaik you can delete your own topics unless somebody already replied . [/offtopic]

Vladislav IV · 2008-06-25 14:49:28

B wrote:

[offtopic] Afaik you can delete your own topics unless somebody already replied . [/offtopic]

Ahhhh I don't see how to delete the other one... He he he....
Hem... God ? Could You... ?

Vladislav IV · 2008-06-26 14:25:13

After looking on the web, it seems that hal can cause some problems with the keymap under xorg 1.4 (some keys don't work, the keymap quirks are ignored, etc.)

Anybody with xorg 1.4 and hal quirks working ?

ibendiben · 2008-06-26 16:32:50

On compaq 6710b those keys aren't recognised either...

Vladislav IV · 2008-06-26 18:25:54

I found this howto in the wiki : http://wiki.archlinux.org/index.php/Xor … otplugging . So I compiled xorg-server with hal enabled, and I restarted X. My mouse and my keyboard didn't worked anymore I managed to get on vc/1, and installed xf86-input-evdev. After rebooting, the input devices worked normally, so I presume that hal is correctly configured. I even saw the mouse plug/unplug events in /var/log/Xorg.0.log.

I looked at lshal :

vlad ~  $  lshal | grep keymap
  info.callouts.add = {'hal-setup-keymap'} (string list)
  info.capabilities = {'input', 'input.keyboard', 'input.keypad', 'input.keys', 'input.keymap', 'button'} (string list)
  input.keymap.data = {'e001:fn_esc', 'e008:presentation', 'e009:battery', 'e00a:screenlock', 'e033:f22', 'e059:info'} (string list)

The keycodes are OK for the extra keys.

BUT... They're still unknown... So I'm at the same point as at the begining.

Edit : not exactly the same point... If there's an update of xorg-server package, I suppose the X hal support of my laptop will be lost ? So, I must blacklist this package in pacman and compile every update, right ?

Last edited by Vladislav IV (2008-06-26 18:30:54)

Vladislav IV · 2008-06-27 11:13:36

OK, after looking at several forums / mailing lists, it seems that hal is not very stable yet for input handling... Lots of people have the same problem under several distros (Gentoo, Ubuntu, Fedora... Arch ). But the major issues should be fixed, somme day (I hope), and then everything should work out of the box.

Until then... I think I'll reinstall keytouch. It's so easy

problemkenner · 2009-03-31 18:03:52

First sorry that I reanimate this thread but I have the same laptop trying to make the media keys usable.

So you might help me - what do I have to do to get them working?

Big thanks

.:B:. · 2009-03-31 19:44:29

By now Xorg has input device handling done by HAL. So a lot of those keys should 'work' - that is: be recognised correctly. You can check by using xev.

As for configuration, depending on your DE/WM you'll have some default pre-set stuff, or nothing at all . All depends on how much you love tinkering .

problemkenner · 2009-03-31 20:03:03

Hello B,

I checked the output of xev and the keys for increasing/decreasing volume and muting sound seem to be detected. But as I'm using Musca I have no pre-set stuff and have just no idea how to deal with.

Do you have the same laptop and are the keys working?

Greets

.:B:. · 2009-03-31 20:08:23

I had the 6510b - witness my previous post in this topic. I sold it though, but the procedure is always the same. I don't know if Musca offers you the possibility to set up keybiindings, but I guess it does. That's what you should look into.

Vladislav IV · 2009-04-18 13:13:45

Hello.

I talked with the guys from the HAL mailing list. The keys controlling the volume have a keycode under 255, while the media keys have a greater one, if my memory is good.

You can get the media keys recognized by running "setkeycodes e008 148 e059 138" at each boot, which will bring those keys under 255, so X can see them. I choosed 148 and 138 arbitrarily. I read in the wiki that you can put this command in /etc/rc.local ; for me it just doesn't work, I would have to do this in a terminal after my session start, but I don't use those keys anymore.

Arch Linux

#1 2008-06-25 13:35:10

Compaq 6510b HAL keymap quirk does nothing

#2 2008-06-25 14:09:34

Re: Compaq 6510b HAL keymap quirk does nothing

#3 2008-06-25 14:49:28

Re: Compaq 6510b HAL keymap quirk does nothing

#4 2008-06-26 14:25:13

Re: Compaq 6510b HAL keymap quirk does nothing

#5 2008-06-26 16:32:50

Re: Compaq 6510b HAL keymap quirk does nothing

#6 2008-06-26 18:25:54

Re: Compaq 6510b HAL keymap quirk does nothing

#7 2008-06-27 11:13:36

Re: Compaq 6510b HAL keymap quirk does nothing

#8 2009-03-31 18:03:52

Re: Compaq 6510b HAL keymap quirk does nothing

#9 2009-03-31 19:44:29

Re: Compaq 6510b HAL keymap quirk does nothing

#10 2009-03-31 20:03:03

Re: Compaq 6510b HAL keymap quirk does nothing

#11 2009-03-31 20:08:23

Re: Compaq 6510b HAL keymap quirk does nothing

#12 2009-04-18 13:13:45

Re: Compaq 6510b HAL keymap quirk does nothing

Board footer