Bug 202581 - Mute key LED does not work on HP Pavilion x360
Summary: Mute key LED does not work on HP Pavilion x360
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jaroslav Kysela
Depends on:
Reported: 2019-02-14 19:24 UTC by El jinete sin cabeza
Modified: 2019-04-01 11:48 UTC (History)
1 user (show)

See Also:
Kernel Version: Ubuntu 4.19.0-12.13-generic 4.19.18
Tree: Mainline
Regression: No


Description El jinete sin cabeza 2019-02-14 19:24:52 UTC
Open bug in launchpad.net:


Description of problem:
The F6/mute key on the keyboard of HP notebooks often has a built in LED indicator to show if the sound is muted. The LED state is never toggled. It will just retain its state, even though the audio is succesfully muted/unmuted.

Tested with HP Pavilion x360 from 2018.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Press mute key on HP laptop

Actual results:
Mute state in software toggles, LED in mute key does not.

Expected results:
Mute state in software and LED in mute key toggle.

Additional info:
This happens on kernel 4.20.8

Other similar errors:
* https://bugs.launchpad.net/bugs/1683277
* https://bugs.launchpad.net/bugs/1705586
Comment 1 El jinete sin cabeza 2019-02-14 20:55:58 UTC

My first patch for the linux kernel:

I would like to have credits for this patch (:
Comment 2 El jinete sin cabeza 2019-02-14 23:59:58 UTC

My first patch v2 for the Linux kernel:

Attentive to comments...

El jinete sin cabeza
Comment 3 El jinete sin cabeza 2019-02-15 00:18:47 UTC
Now YES!

El jinete sin cabeza
Comment 4 El jinete sin cabeza 2019-02-15 15:24:19 UTC
I'm asking for help to have a server where I can compile. Please give me a few days to generate a patched kernel and confirm that this actually works.
Comment 5 Fabio 2019-04-01 11:48:32 UTC
I also have the same problem in my HP Pavilion 15-bc202na. Is there any chance to add it to the list of quircks?


Note You need to log in before you can comment on or make changes to this bug.