brightness keys incorrectly mapped for ProBook 455 G5

Bug #1784008 reported by James Buren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Hello. For unknown reasons, the brightness up and brightness down keys on my ProBook 455 G5 are being mapped to F20, which is the microphone mute key. Because of this, the screen brightness cannot be adjusted by pressing the brightness keys. However, the screen brightness can still be adjusted by software such as panel applets.

I did a fair amount of testing to arrive at this conclusion. acpi_listen reports the brightness keys as F20, same with my microphone mute key. showkey reveals that the scan codes are identical for both the brightness keys and the microphone mute key. On the off-chance it was some kind of userspace issue, I also performed these tests from other distributions, both systemd and non-systemd variants. The same issue is present there as well.

The only conclusion I am left with is that the kernel is not reporting the keys correctly. I haven't been able to find any other reports of a similar situation, so I am unsure how to proceed from here. Please advise me on how I can help you find a solution to my issue. Thank you.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ryuo 3305 F.... pulseaudio
 /dev/snd/controlC0: ryuo 3305 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
MachineType: HP HP ProBook 455 G5
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-29-generic N/A
 linux-backports-modules-4.15.0-29-generic N/A
 linux-firmware 1.173.1
StagingDrivers: r8822be
Tags: bionic staging
Uname: Linux 4.15.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: kvm sudo
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 03/30/2018
dmi.bios.vendor: HP
dmi.bios.version: Q84 Ver. 01.01.01
dmi.board.name: 836E
dmi.board.vendor: HP
dmi.board.version: KBC Version 03.16.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 455 G5
dmi.sys.vendor: HP

Revision history for this message
James Buren (braewoods) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic staging
description: updated
Revision history for this message
James Buren (braewoods) wrote : CRDA.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : CurrentDmesg.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : IwConfig.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : Lspci.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : Lsusb.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : ProcEnviron.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : ProcInterrupts.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : ProcModules.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : PulseList.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : RfKill.txt

apport information

Revision history for this message
James Buren (braewoods) wrote : UdevDb.txt

apport information

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
James Buren (braewoods) wrote :

acpidump output

Revision history for this message
James Buren (braewoods) wrote :

acpidump binary output

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
James Buren (braewoods) wrote :

Did this issue start happening after an update/upgrade? No.

Was there a prior kernel version where you were not having this particular problem? No.

Also, I finished testing the mainline kernel build, version 4.18-rc6. The issue is still present. I have marked the bug as requested.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
James Buren (braewoods) wrote :

I did some further testing with ATKBD's softraw parameter to see how it changed showkey's output. Here are my findings.

When ATKBD's softraw parameter is set to 1, showkey -s says that all 3 keys map to this scancode sequence: 0x5a 0xda

When ATKBD's softraw parameter is set to 0, showkey -s shows that the brightness keys map to this scancode sequence: 0xe0 0x01 0xe0 0x81, while the microphone mute key maps to this scancode sequence: 0xe0 0x01 0xe0 0x81 0xc2

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Platform_x86

Revision history for this message
James Buren (braewoods) wrote :
Revision history for this message
James Buren (braewoods) wrote :

Issue resolved by BIOS update.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.