← Back to team overview

kernel-packages team mailing list archive

[Bug 1205791] Re: Dell Vostro V131: special keys not working


@Darek: Thanks for reporting, this proves there are more Dell laptop
models than just the Vostro V131 that need a specially crafted SMI in
order to receive events via WMI. BTW, hotkey #2 reports WMI event 0xe06e
on Vostro V131 (the same one as on your Inspiron), not sure why you
mentioned 0xe026.

Could you perhaps create a list for your laptop similar to the one


The more the merrier: the situation right now is that we know the
solution, but it cannot be merged into mainline just yet because we need
a method to determine which laptop models need this special SMI and
which ones don't. There is also another issue with keycode generation
happening on some models and not happening on others:


To solve both these problems The Right Way™, we could really use some
help from Dell, but unfortunately it doesn't seem to be coming.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Dell Vostro V131: special keys not working

Status in udev:
Status in linux package in Ubuntu:

Bug description:
  Bug filed, following conversation on IRC at:


  I own a Dell Vostro V131. This model has 3 special hotkeys (quick
  launch keys:


  There are documented in page 1 of the manual:


  as being:

    1. "Windows mobility center" (this hotkey generates [Mod]+[x])
    2. "Dell support center"
    3. "Dell instant launch manager"

  This was previous raised at:


  The "Dell support center" key generates keycode 0xEE, but misses
  release event. I got it working with an udev "keyboard force release"
  quirk, see attached patch in the '4444' email.

  However, the "Dell instant launch manager" key doesn't generate
  anything, neither through dell-wmi nor i8042. It's the rightmost
  button in the right upper corner of the keyboard.  The ACPI interrupt-
  count appears to increment, as seen with:

    watch -n 0,1 cat /proc/interrupts

To manage notifications about this bug go to: