<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Multimedia Keys not recognized" href="https://bugs.freedesktop.org/show_bug.cgi?id=98400#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Multimedia Keys not recognized" href="https://bugs.freedesktop.org/show_bug.cgi?id=98400">bug 98400</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>sorry about the delay, this fell through. short summary: this would need to go into systemd's hwdb (60-keyboard.hwdb) but I fail to see any identifying information for that keyboard, so I'm not sure we can make a generic match here. Is this a laptop? The dmi only includes the gigabyte motherboard's information and the keyboard claims it's connected via serial bus. either way, the solution to this would be a blurb simliar to others in the 60-keyboard.hwdb file. A match string, together with the scancode to event code mappings. example here: evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*Presario*CQ*:pvr* KEYBOARD_KEY_d8=f21 KEYBOARD_KEY_d9=f21 You'll need to convert the scancodes into hex (e.g. 159 -> 0x9f) and then add the entries. the key names are in /usr/linux/input-event-codes.h, just lowercase it and remove the KEY_ prefix. If we can't find any identifying information, you'll have to keep this as a local override in /etc/udev/hwdb.d/</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>