[Bug 1441849] [NEW] Update force_release for Dell Latitudes

Pali pali.rohar at gmail.com
Wed Apr 8 20:51:11 UTC 2015


Public bug reported:

Wireless HW switch on Dell Latitude notebooks generate key press event
via AT Translated Set 2 keyboard, but does *not* generate release key
event. This means that operating systems and applications see key still
pressed.

Scan code of that problematic key is 136 (0x88).

Fixing this problem can be done via force_release option of atkbd kernel
driver (by adding 136 scan code to list)

Kernel developers told me that now only userspace (udev package)
maintains list of those problematic scan codes and so udev needs to be
extended/patched to add new values to atkbd kernel driver at runtime.
See: https://lkml.org/lkml/2015/4/5/157

Currenly there is file /lib/udev/keymaps/force-release/dell-touchpad
which contains some force_release scan code for all dell latitude
notebooks handled by file /lib/udev/rules.d/95-keyboard-force-
release.rules by rule:

ENV{DMI_VENDOR}=="Dell Inc.",
ATTR{[dmi/id]product_name}=="*Latitude*|*Precision*", RUN+="keyboard-
force-release.sh $devpath dell-touchpad"

Can you extend either /lib/udev/keymaps/force-release/dell-touchpad or
/lib/udev/rules.d/95-keyboard-force-release.rules to include also scan
code 136 (0x88)? Because without is there are problems with HW wireless
switch!

This problem was tested on Ubuntu 12.04.5 LTS Precise release.

** Affects: udev (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/1441849

Title:
  Update force_release for Dell Latitudes

Status in udev package in Ubuntu:
  New

Bug description:
  Wireless HW switch on Dell Latitude notebooks generate key press event
  via AT Translated Set 2 keyboard, but does *not* generate release key
  event. This means that operating systems and applications see key
  still pressed.

  Scan code of that problematic key is 136 (0x88).

  Fixing this problem can be done via force_release option of atkbd
  kernel driver (by adding 136 scan code to list)

  Kernel developers told me that now only userspace (udev package)
  maintains list of those problematic scan codes and so udev needs to be
  extended/patched to add new values to atkbd kernel driver at runtime.
  See: https://lkml.org/lkml/2015/4/5/157

  Currenly there is file /lib/udev/keymaps/force-release/dell-touchpad
  which contains some force_release scan code for all dell latitude
  notebooks handled by file /lib/udev/rules.d/95-keyboard-force-
  release.rules by rule:

  ENV{DMI_VENDOR}=="Dell Inc.",
  ATTR{[dmi/id]product_name}=="*Latitude*|*Precision*", RUN+="keyboard-
  force-release.sh $devpath dell-touchpad"

  Can you extend either /lib/udev/keymaps/force-release/dell-touchpad or
  /lib/udev/rules.d/95-keyboard-force-release.rules to include also scan
  code 136 (0x88)? Because without is there are problems with HW
  wireless switch!

  This problem was tested on Ubuntu 12.04.5 LTS Precise release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1441849/+subscriptions



More information about the foundations-bugs mailing list