Red Hat Bugzilla – Bug 989103
Add proper keymap for Samsung Series 5 and Series 5 Ultra
Last modified: 2013-10-21 17:38:54 EDT
Description of problem: The keymap table for Samsung i5 Ultra models are wrong. Version-Release number of selected component (if applicable): systemd-204-9.fc19.x86_64 How reproducible: Try to press the function keys, like Fn + F12 (Wlan) and check that several of them don't produce any scancode at all. Steps to Reproduce: 1. Boot 2. Press Fn keys Actual results: Several keys don't produce the expected results (Fn+F1, Fn+F11, Fn+F12, Fn Lock) Expected results: All keys should produce a scancode. Additional info:
Created attachment 779104 [details] keymap file for Samsung i5 ultra In order to trigger this keymap table, the following udev rule is needed: ENV{DMI_VENDOR}=="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}=="*530U3C*", RUN+="keymap $name samsung-i5-ultra"
Created attachment 779105 [details] dmidecode info of the notebook
*** Bug 989101 has been marked as a duplicate of this bug. ***
Created attachment 779596 [details] /lib/udev/keymaps/samsung-series-5
Created attachment 779598 [details] /lib/udev/keymaps/force-release/samsung-series-5
Created attachment 779608 [details] /lib/udev/rules.d/95-keymap.rules New 95-keymap.rules with Samsung series 5 DMI data
Those notebooks have an extra Fn Lock key, and don't sent KEY UP events for some keys. Patches addressing those were sent to linux-input ML: http://www.mail-archive.com/linux-input@vger.kernel.org/msg05491.html http://www.mail-archive.com/linux-input@vger.kernel.org/msg05492.html http://www.mail-archive.com/linux-input@vger.kernel.org/msg05490.html http://www.mail-archive.com/linux-input@vger.kernel.org/msg05489.html http://www.mail-archive.com/linux-input@vger.kernel.org/msg05493.html
Created attachment 779708 [details] /lib/udev/keymaps/force-release/samsung-series-5 Not all Fn keys need software keyup. Update the force-release
Created attachment 779709 [details] /lib/udev/rules.d/95-keyboard-force-release.rules
Looks like something where Martin Pitt might be able to help. Adding to CC. Martin?
Thanks for those! I translated those to the new-style hwdb format and pushed to http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e1452d6 Note that I left out the key codes of these two, as they already appear to be covered in your kernel patches; I just kept the "force release" bit: 0xA8 0x225 # Fn Lock - Function lock on 0xA9 0x226 # Fn Lock - Function lock off
systemd-204-14.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/systemd-204-14.fc19
(In reply to Lennart Poettering from comment #10) > Looks like something where Martin Pitt might be able to help. Adding to CC. > Martin? Lennart, thanks for forwarding it to Martin! (In reply to Martin Pitt from comment #11) > Thanks for those! > > I translated those to the new-style hwdb format and pushed to > http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e1452d6 Thanks, Martin! > Note that I left out the key codes of these two, as they already appear to > be covered in your kernel patches; I just kept the "force release" bit: > > 0xA8 0x225 # Fn Lock - Function lock on > 0xA9 0x226 # Fn Lock - Function lock off Agreed, better to keep only the force release there, at least for now.
Package systemd-204-14.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-204-14.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16988/systemd-204-14.fc19 then log in and leave karma (feedback).
Hm, this has been in stable as part for a while. I guess it hasn't been marked as closed because the update was obsoleted.