Bug 216933 - brightness keys not working on Lenovo ideapad 3
Summary: brightness keys not working on Lenovo ideapad 3
Status: RESOLVED DUPLICATE of bug 214899
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-15 14:19 UTC by tuxuser
Modified: 2023-01-24 08:20 UTC (History)
1 user (show)

See Also:
Kernel Version: 6.1.5
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg-kernel-5.14.21-150400.322.g49b518d-default (78.07 KB, text/plain)
2023-01-15 14:20 UTC, tuxuser
Details
hwinfo-kernel-5.14.21-150400.322.g49b518d-default (2.28 MB, text/plain)
2023-01-15 14:20 UTC, tuxuser
Details

Description tuxuser 2023-01-15 14:19:19 UTC
System: Lenovo ideapad 3
OS: openSUSE Leap 15.4, all updates installed
Kernel: 6.1.5, 5.14.21-150400.38-default

Brightness keys are not working. When pressing these in kde plasma no brightness increase / decrease indicator is shown.
The brightness system itself is working: When changing the brightness using the plasma battery applet, the brightness changes as expected.

Changing to runlevel 3 showkey and evtest don't respond to pressing these keys. They only respond to other keys.
evtest displays
/dev/input/event1 is Video Bus
Here it displays Event code 224 for KEY_BRIGHTNESSDOWN and Event code 225 for KEY_BRIGHTNESSUP. But pressing the buttons leads to no response.
Comment 1 tuxuser 2023-01-15 14:20:01 UTC
Created attachment 303606 [details]
dmesg-kernel-5.14.21-150400.322.g49b518d-default
Comment 2 tuxuser 2023-01-15 14:20:42 UTC
Created attachment 303607 [details]
hwinfo-kernel-5.14.21-150400.322.g49b518d-default
Comment 3 tuxuser 2023-01-15 14:54:40 UTC
I've also reported this at openSUSE: https://bugzilla.opensuse.org/show_bug.cgi?id=1207149
Comment 4 Takashi Iwai 2023-01-24 08:20:57 UTC
This turned out to be the same issue as bug 214899.  6.2-rc kernel works fine.

*** This bug has been marked as a duplicate of bug 214899 ***

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