Hallo,
I was able to install according to the instructions:
https://wiki.ubuntu.com/Testing/EnableProposed the kernel 4.15.0-60.67 and test
successfully. The kernel now offers the desired LED hotkey support without
option: options snd-hda-intel mode = mute-led-gpio in:
/etc/modprobe.d/alsa-base.conf.
inxi -S
System: Host: HP470 Kernel: 4.15.0-60-generic x86_64 bits: 64 Desktop:
Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina
dpkg -l | grep linux-image
ii linux-image-4.15.0-58-generic 4.15.0-58.64
amd64 Signed kernel image generic
ii linux-image-4.15.0-60-generic 4.15.0-60.67
amd64 Signed kernel image generic
ii linux-image-generic 4.15.0.60.62
amd64 Generic Linux kernel image
Great work, all good, Many Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811254
Title:
HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
Notebook: HP ProBook 470 G5 (3KZ03EA)
Distro: Linux Mint 19.1 Tessa
Desktop: Cinnamon 4.0.8
Kernel: 4.15.0-43-generic x86_64 bits: 64
The functions of all hotkeys are given, but the LED's in the [f5]
Speaker-mute, [f8] Micro-mute and [f11] Wireless on/off Buttons do not
show the status. Disturbing is also the LED in [f11] permanently lit.
This is my first bug report to launchpad and I ask for leniency and
troubleshooting support.
I created 12 logs, unfortunately the upload did not work at once:
acpi_listen.txt
apt-cache-policy
dmesg.log
lsb_release
lsinput.log
lspci-vnvn.log
rfkill_list.txt
udev-db.txt
version.log
xev keypress test.txt
xkbcomp.txt
xkbmap.txt
Previous attempts:
My on-board search for other HP ProBook Hotkey LED-issues led me to this bug
report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586
but the solution to the file: /etc/modprobe.d/alsa-base.conf
to supplement the entry: options snd-hda-intel mode = mute-led-gpio
did not lead to the solution here. Presumably, the failure results
from a different ubuntu-version and/or a another kernel.
Information: This problem was previously discussed on
linuxmintusers.de:
https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
