http://bugzilla.novell.com/show_bug.cgi?id=498018 Summary: MSI PR200: brightness keys go haywire when defined as a hal quirk Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jmatejek@novell.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.3 Firefox/3.0.8 so. there is no hal quirk configuration for my notebook - but all keys do what they're supposed to do, except that they also spam syslog with "unknown keycode" messages. i tried to fix that, using the guide from http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-try.html i added the following to the default 30-keymap-misc.fdi file : <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" contains="MSI Notebook PR200"> <append key="input.keymap.data" type="strlist">e064:f22</append> <!-- Fn-F3 Touchpad disable --> <append key="input.keymap.data" type="strlist">e077:brightnessdown</append> <!-- Fn-F4 Brightness down --> <append key="input.keymap.data" type="strlist">e078:brightnessup</append> <!-- Fn-F5 Brightness up --> <!-- there are volume buttons, but they're mapped somewhere else, apparently. also the display toggle key --> <append key="input.keymap.data" type="strlist">e079:prog1</append> <!-- P1 - no defined purpose, custom button --> <append key="input.keymap.data" type="strlist">e06e:camera</append> <!-- P2 - webcam toggle --> <append key="input.keymap.data" type="strlist">e076:wlan</append> <!-- satellite dish 1 --> <append key="input.keymap.data" type="strlist">e062:bluetooth</append> <!-- satellite dish 2 --> </match> when the changes took effect, everything still worked and syslog was no longer spammed. however, after playing a bit with brightness keys, the backlight started blinking randomly, X's cpu usage went through the roof and X was no longer usable. also, a whole new keycode appeared in syslog, many times over: atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. i didn't press any keys and i don't know what this might be. when i restarted X via double-ctrl-alt-bksp, another keycode appeared, but only once: atkbd.c: Unknown key released (translated set 2, code 0x5b on isa0060/serio0). atkbd.c: Use 'setkeycodes 5b <keycode>' to make it known. (i'm not sure i can reproduce this one, though) after some restarting hal and X processes from a remote session, the system was usable again. Reproducible: Always if you close this as invalid with "don't modify quirk confs", i'm just going to submit a new bug called "quirk conf missing for PR200", provide info and let somebody else hit the same bug again :P also, it would be nice, once this is resolved, to merge the quirk conf and send it upstream then again ... the system is usable without a quirk conf, all keys do what they're supposed to. it just makes reporting other bugs that much harder, because one has to filter out the keycode spam from syslogs first -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.