Bug 398846

Summary: HP Pavilion dv6700: unmapped keys generate unknown scancodes
Product: [openSUSE] openSUSE 11.0 Reporter: andrea florio <andrea>
Component: KernelAssignee: Danny Al-Gaaf <dalgaaf>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P4 - Low CC: andrea.turrini, bidossessi.sodonon, clarkt, kev, sunscape1, werner.habel
Version: RC 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard: marked-ForNext11.0YOU:HAL
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 398774    
Attachments: lshal_output file
output of xev from multimedia keys - HP dv6645eg
fdi with section for dv6700
patch for 30-keymap-hp.fdi

Description andrea florio 2008-06-10 13:04:32 UTC
this bug is linked with bug #398774

keys are not mapped out of the box like happened on suse 10.3 and 2 keys are not detected bye xev...

from /var/log/messages i have this output  when i try to press the 2 keys not detected:

Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Unknown key pressed (translated set
2, code 0x88 on isa0060/serio0).
Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Use 'setkeycodes e008 <keycode>' to
make it known.
Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Unknown key released (translated
set 2, code 0x88 on isa0060/serio0).
Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Use 'setkeycodes e008 <keycode>' to
make it known.
Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Unknown key pressed (translated set
2, code 0x8e on isa0060/serio0).
Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Use 'setkeycodes e00e <keycode>' to
make it known.
Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Unknown key released (translated
set 2, code 0x8e on isa0060/serio0).
Jun 10 11:52:57 linux-16bn kernel: atkbd.c: Use 'setkeycodes e00e <keycode>' to
make it known.


that's my kernel:

anubis@linux-16bn:~> uname -a
Linux linux-16bn 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux
Comment 1 andrea florio 2008-06-11 06:26:21 UTC
i hope somebody to answer...
Comment 2 Danny Al-Gaaf 2008-06-11 06:58:06 UTC
Follow http://en.opensuse.org/HAL#Keymapping and provide a patch/the needed information.
Comment 3 andrea florio 2008-06-12 21:10:43 UTC
Created attachment 221889 [details]
lshal_output file

done.. sorry for late..but my jobs removed me lots of time
Comment 4 andrea florio 2008-06-12 21:13:54 UTC
i really don't understood well what i should do here: http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-index.html

no usefull "how to" found
Comment 5 andrea florio 2008-06-12 21:16:03 UTC
any way my laptop is the HP Pavlion dv6855el : http://en.opensuse.org/HP_Pavilion_dv6855el  (guide wrote by me)
Comment 6 andrea florio 2008-06-12 21:30:28 UTC
linux-16bn:/usr/share/hal/fdi/information/10freedesktop # lshal | grep system.hardware
  system.hardware.primary_video.product = 1063  (0x427)  (int)
  system.hardware.primary_video.vendor = 4318  (0x10de)  (int)
  system.hardware.product = 'HP Pavilion dv6700 Notebook PC'  (string)
  system.hardware.serial = 'XXXXXXXX'  (string)
  system.hardware.uuid = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'  (string)
  system.hardware.vendor = 'Hewlett-Packard'  (string)
  system.hardware.version = 'Rev 1'  (string)


i still not understanding how to activate 30-keymap-hp.fdi


if i go on yast-->system--runlevels editor 

i'm not able to find "hotkey-setup" service like on suse 10.3
Comment 7 andrea florio 2008-06-12 21:52:29 UTC
the problem looks to be the missing hotkeys-setup package..

i downloaded that one:

http://ftp5.gwdg.de/pub/opensuse/distribution/10.3/repo/src-oss/suse/src/hotkey-setup-0.1-72.src.rpm

and with rpmbuild --rebuild i had rebuild package and then installed..no more have the problem posted, and xev detect my keys.. but all multimedia keys are still not associated:

keycode 205 (keysym 0x0, NoSymbol) (i.e.)
Comment 8 andrea florio 2008-06-12 21:57:26 UTC
FIXED.. just need to install htokey-etup package that is missing on OSS repository.. please add it ( it exist on suse <= 10.3 OSS )
Comment 9 Danny Al-Gaaf 2008-06-12 22:42:58 UTC
(In reply to comment #8 from andrea florio)
> FIXED.. just need to install htokey-etup package that is missing on OSS
> repository.. please add it ( it exist on suse <= 10.3 OSS )

hotkey-setup was dropped. We don't add it again to openSUSE.

(In reply to comment #4 from andrea florio)
> i really don't understood well what i should do here:
> http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-index.html
> 
> no usefull "how to" found

What is the problem?
* http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-scancodes.html

collect all unknown scancode and then follow:

* http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-try.html
Comment 10 Danny Al-Gaaf 2008-06-12 22:45:21 UTC
And if this is to difficult: collect all unknow scancodes your machine generates, paste them together with the name/function of the related key into this bug. 
Comment 11 andrea florio 2008-06-13 06:19:24 UTC
1) why this package has been dropped? if it's usefull on laptops?

2) the only unknow scancode was the one pasted on comment #1 and they are

e008 end e00e 

3) i yet followed the guide, but not works

4) as i told, installing hotley-setup package, the error disappear and has been fixed (after an X reboot) also bug #398774
Comment 12 Danny Al-Gaaf 2008-06-13 08:07:09 UTC
(In reply to comment #11 from andrea florio)
> 1) why this package has been dropped? if it's usefull on laptops?

Because it's simply not needed anymore. HAL do the mapping now.

> 2) the only unknow scancode was the one pasted on comment #1 and they are
> 
> e008 end e00e 

What is that difficult to tell also the function/name of the keys which generate the scancodes? 

Are there other keys (Fn+Fx, special keys like (i) ...) which generate unknown scancodes?
Comment 13 andrea florio 2008-06-13 17:45:41 UTC
the only key that gave that error was 2, and both was fixed installing hotkey-setup.

hotkey-setup package fix also all unmapped key..infact all key that xev show like:

keycode 176 (keysym 0x0, NoSymbol)

are now mapped and showed like


keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume)

anyway the default "hp".fdi file is the same available here:

http://gitweb.freedesktop.org/?p=hal-info.git;a=blob;f=fdi/information/10freedesktop/30-keymap-hp.fdi
Comment 14 andrea florio 2008-06-14 07:43:35 UTC
bug, and the "fixing installing hotkey-setup package" confirmed on a treadh on www.suseitalia.org forum. i'll aks the user to report his experience here.

hi have the same problem, unmapped keys, after installing hotkey-setup package they are now mappend and are working well
Comment 16 Danny Al-Gaaf 2008-06-14 09:45:27 UTC
What is that difficult to understand that we droppend hotkey-setup for good reasons and that we don't add it again to the distribution?

Sorry, but atm it looks to me as if you are unwilling to answer my questions.

If you don't answer which *keys* (check all Fn-Fx combinations) produce the unknown scancodes in /var/log/messages and what the function of them is (do they have any function/blue icon?) I can't do anything. 
Comment 17 andrea florio 2008-06-14 15:00:33 UTC
i understood that hal SHOULD map keys but it DON't..

anyway as itold on comment #11 the only unknown scancodes was given bye 2 keys and the complete log from /var/log/messages is the one in comment #1
Comment 18 andrea florio 2008-06-14 15:30:38 UTC
ask sorry those are keys:

e008, e00e, e031, e00a
Comment 19 Danny Al-Gaaf 2008-06-14 18:01:57 UTC
Either you are unable to understand me or you are unwilling to report what I ask for.

WHAT ARE THE FUNCTION OF THESE KEYS? 

To map the scancodes to a keycode I need to know what the function of them is!!! Again: which keycombination generate which scancode and what is the function of this key, what should the key do?
Comment 20 Kevin Johnson 2008-06-14 18:05:49 UTC
Created attachment 222165 [details]
output of xev from multimedia keys - HP dv6645eg
Comment 21 Kevin Johnson 2008-06-14 18:08:19 UTC
Ooops, seems this doesn't work the same way as the Forum and I posted the attachment first!


I get no default response from any of the "extra" keys on my HP dv6645eg laptop
either.

I managed to get the mute/vol up/vol down working by assigning them in the
mixer.  But I get no onscreen feedback apart from the mixer icon showing mute.

Ie no vol up/down animation.

I don't get any problems with unknown keys though.

Keyboard is German, layout is German no dead keys.
Comment 22 andrea florio 2008-06-14 19:34:54 UTC
ok sorry.. anyway..keys shoud do exactly what is written here:

http://gitweb.freedesktop.org/?p=hal-info.git;a=blob;f=fdi/information/10freedesktop/30-keymap-hp.fdi

and infact

e008

<append key="input.keymap.data" type="strlist">e008:pc</append>       <!-- Media Player: Media Mode (PVR or PC?) -->

e00e

<append key="input.keymap.data" type="strlist">e00e:dvd</append>      <!-- Media Player: DVD mode -->

e031

<append key="input.keymap.data" type="strlist">e031:help</append>      <!-- Fn+F1 (help) -->

e00a

<append key="input.keymap.data" type="strlist">e00a:screenlock</append><!-- Fn+lock -->

the problem look to be hal not able to load fdi file.

infact

lshal | grep keymap

show nothing
Comment 23 Timo Hoenig 2008-06-16 08:13:10 UTC
Created attachment 222210 [details]
fdi with section for dv6700

Andrea, please copy the attached file (30-keymap-hp.fdi) to

/usr/share/hal/fdi/information/10freedesktop/

reboot and report back if this helps.
Comment 24 Timo Hoenig 2008-06-16 08:15:53 UTC
Created attachment 222212 [details]
patch for 30-keymap-hp.fdi

Danny: This is a patch against 30-keymap-hp.fdi which adds a section for the dv6700.  In case Andrea confirms that this helps, you may want to pick this up for hal-info.
Comment 25 andrea florio 2008-06-16 21:31:43 UTC
Timo...well

your patch fix only 2 keys, they are:

e031

<append key="input.keymap.data" type="strlist">e031:help</append>      <!--
Fn+F1 (help) -->

e00a

<append key="input.keymap.data" type="strlist">e00a:screenlock</append><!--
Fn+lock -->


the others two instead still give me "unknown scancodes"

the strange thing is that WITHOUT hotkey-setup package ALL keys give me:

keycode "key-number" (keysym 0x0, NoSymbol)

installing the package instead they are ALL mapped 

i.e.

keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume)

and NO ONE give me "unknown scancodes"
Comment 26 andrea florio 2008-06-16 21:39:57 UTC
same thing happen on my DESKTOP pc..

without hotkey-setup i have all multimedia key like:

keycode "key-number" (keysym 0x0, NoSymbol)

once i install hotkey-setup package they are mapped and works..

i understood that hal should now do what hotkey-setup does but you should say the true..something wrong in hal...

if you have any keyboard with multimedia keys it should be easy to reproduce..i have the same problem on 4 differents pc.. 2 laptops and 2 desktops
Comment 27 andrea florio 2008-06-18 12:08:58 UTC
news?
Comment 28 Timo Hoenig 2008-06-18 12:13:17 UTC
no :-)
Comment 29 Timo Hoenig 2008-06-18 12:57:45 UTC
Andrea, as you're the one who has the machine on which the hotkeys don't work reliably:  Would you mind having a look at /usr/share/hal/fdi/information/10freedesktop/30-keymap-hp.fdi and play with it a little more until all your hotkeys are working?

That would be great.

Thanks!
Comment 30 andrea florio 2008-06-18 13:26:04 UTC
of course, i'm yet working on it, your patch "fix" 2 keys, e031 and e00a, infact they give no more the "unknown scancodes" but they are still no working because they are still not mappend.

on my desktop pc, with an olidata keyboard i have the same problem, no keys give unknown scancodes but all multimedia keys are unmapped, i ever receive

(keysym 0x0, NoSymbol)

from xev..

and only after installing hotkey-setup package become mapped and then works...

i think that the real problem is in hal not able to load key mapping files
Comment 31 Benjamin Sabatini 2008-07-02 22:48:27 UTC
Confirmed, some of my laptop keys (brightness controls) do nothing and do not register in xev. Laptop is fujitsu p8010, and I think HAL is fubar. Hotkey-setup does not fix the problem either.
Comment 32 Andrea Turrini 2008-07-10 12:47:42 UTC
I've a similar problem.

My laptop is an Acer Aspire 1691 wlmi and after the upgrade from openSUSE 10.3 to opensuse 11.0, I've lost two keys: dollar and euro signs near arrows.

When I press such keys, xev does not generate feedback, while in /var/log/messages following lines appear (for dollar and euro key, respectively):
Jul 10 14:43:51 orodruin kernel: atkbd.c: Unknown key pressed (translated set 2, code 0xb4 on isa0060/serio0).
Jul 10 14:43:51 orodruin kernel: atkbd.c: Use 'setkeycodes e034 <keycode>' to make it known.
Jul 10 14:43:51 orodruin kernel: atkbd.c: Unknown key released (translated set 2, code 0xb4 on isa0060/serio0).
Jul 10 14:43:51 orodruin kernel: atkbd.c: Use 'setkeycodes e034 <keycode>' to make it known.
Jul 10 14:43:53 orodruin kernel: atkbd.c: Unknown key pressed (translated set 2, code 0xb3 on isa0060/serio0).
Jul 10 14:43:53 orodruin kernel: atkbd.c: Use 'setkeycodes e033 <keycode>' to make it known.
Jul 10 14:43:53 orodruin kernel: atkbd.c: Unknown key released (translated set 2, code 0xb3 on isa0060/serio0).
Jul 10 14:43:53 orodruin kernel: atkbd.c: Use 'setkeycodes e033 <keycode>' to make it known.

This is the result of "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 = {'e025:help', 'e026:setup', 'e027:battery', 'e029:switchvideomode', 'e033:euro', 'e034:dollar', 'e055:wlan', 'e056:wlan', 'e057:bluetooth', 'e058:bluetooth', 'e06e:brightnessup', 'e06f:brightnessdown', 'e071:f22', 'e072:f23', 'e073:prog2', 'e074:prog1'} (string list)

and this the result of "lshal|grep system.hardware":
  system.hardware.primary_video.product = 22099  (0x5653)  (int)
  system.hardware.primary_video.vendor = 4098  (0x1002)  (int)
  system.hardware.product = 'Aspire 1690'  (string)
  system.hardware.serial = 'XXXXXXXXXXXXXXXXXXXXXX'  (string)
  system.hardware.uuid = 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX'  (string)
  system.hardware.vendor = 'Acer, inc.'  (string)
  system.hardware.version = 'Not Applicable'  (string)
Comment 33 Danny Al-Gaaf 2008-07-10 13:54:41 UTC
Please stop mixing up different machines! This report is about the HP Pavlilion and not about Acer or FSC machines. Open a new bug if you have a new problem!°
Comment 34 Andrea Turrini 2008-07-10 14:11:07 UTC
Done (for the Acer). New bug report: https://bugzilla.novell.com/show_bug.cgi?id=407974
Comment 35 andrea florio 2008-07-10 15:06:41 UTC
(In reply to comment #33 from Danny Kukawka)
> Please stop mixing up different machines! This report is about the HP Pavlilion
> and not about Acer or FSC machines. Open a new bug if you have a new problem!°
> 

as you can easy understand is not related to machine used, but on HAL, same problem exist on HP, ACER, FSC, OLIDATA, ecc... is easy to understand that exist something wrong on HAL that is not able to do his work
Comment 36 Danny Al-Gaaf 2008-07-10 15:51:53 UTC
(In reply to comment #35 from andrea florio)
> as you can easy understand is not related to machine used, but on HAL, same
> problem exist on HP, ACER, FSC, OLIDATA, ecc... is easy to understand that
> exist something wrong on HAL that is not able to do his work

Sorry, but that doesn't matter. You can't mix up all these problems, it makes bugzilla unusable. Different machines have differen problems (missing machine specific keymapping information) and need different bug reports. We also don't mix up all machines with suspend problems or kernel bugs in one bug.
Comment 37 Danny Al-Gaaf 2008-07-10 15:57:41 UTC
Btw. The only job of HAL is to map unknown scancode to keycodes. Nothing more. All the othere problems are not related to HAL but maybe to a special kernel module, X or your desktop environment.
Comment 38 Werner Habel 2008-07-11 12:39:13 UTC
Hello,

volume control keys not working after upgrade to 11.0
installed hotkey-setup from http://packman.links2linux.de/package/hotkey-setup
Problem solved.

Only the OSD feedback to the actions is still missing.

Thanks Andrea!

Werner
Comment 39 Danny Al-Gaaf 2008-07-17 21:57:17 UTC
(In reply to comment #25 from andrea florio)
> Timo...well
> 
> your patch fix only 2 keys, they are:
[...]
> the others two instead still give me "unknown scancodes"

Only to clarify: Are there with the new fdi-file keys which still produce unknown scancodes in /var/log/messages ? 

Please check in lshal for which input device hal do the mapping (check for keymap and linux.device_file). Then start evtest on this device and paste the output to this bug.
Comment 40 Bidossessi SODONON 2008-07-30 09:33:21 UTC
hi all,
i have an hp dv6700 and the only two keys that give unknown scancode are the quickplay keys (DVD, and... well, that circular thing that's supposed to call hp media center in vista).

it would be nice to be able to map them to something like mplayer for the first and elisa for the second...
Comment 41 Bidossessi SODONON 2008-07-30 09:53:47 UTC
i applied the patch submitted by Timo;

extract from hp.fdi on my system:
<append key="input.keymap.data" type="strlist">e00e:dvd</append>	<!-- Media Player: DVD mode -->
<append key="input.keymap.data" type="strlist">e008:pc</append>	<!-- Media Player: Media Mode (PVR or PC?) -->

but i still get:

Jul 30 10:53:14 laptop-2 kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0).
Jul 30 10:53:14 laptop-2 kernel: atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
Jul 30 10:53:14 laptop-2 kernel: atkbd.c: Unknown key released (translated set 2, code 0x88 on isa0060/serio0).
Jul 30 10:53:14 laptop-2 kernel: atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
Jul 30 10:53:16 laptop-2 kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x8e on isa0060/serio0).
Jul 30 10:53:16 laptop-2 kernel: atkbd.c: Use 'setkeycodes e00e <keycode>' to make it known.
Jul 30 10:53:16 laptop-2 kernel: atkbd.c: Unknown key released (translated set 2, code 0x8e on isa0060/serio0).
Jul 30 10:53:16 laptop-2 kernel: atkbd.c: Use 'setkeycodes e00e <keycode>' to make it known.

did i miss something
Comment 42 Danny Al-Gaaf 2008-10-14 13:04:08 UTC
That's because there was a bug in the openSUSE 11.0 kernel AFAIK that didn't allow set keycodes over 255 (0xFF) which affects these keys. It's fixed for openSUSE 11.1
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f6d65610df3bd4e7138da03aec391224219df135)
--> feel free to open another bug to request a fix for the kernel


The HAL mapping is fixed in this package:
http://download.opensuse.org/repositories/home:/dkukawka/openSUSE_11.0/
Comment 43 andrea florio 2008-10-14 13:16:38 UTC
perfetct, does it means that with suse 11. 1 i need to install no more hotkey-setup package? doest keys gives no more unknown scancodes or also "(keysym 0x0, NoSymbol)" issue is fixed?

btw, you linked a repository not a package.. witch package fix the issue? 

thanks
Comment 44 Danny Al-Gaaf 2008-10-14 13:19:06 UTC
About which package are we speaking all the time? HAL.
Comment 45 Danny Al-Gaaf 2008-10-31 17:44:48 UTC
Submitted package and SWAMP-file for YOU update, bnc#394390 stays open until released.