[Bug 1202125] New: Unable to change display brightness thought brightness keys or applet slider.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 Bug ID: 1202125 Summary: Unable to change display brightness thought brightness keys or applet slider. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: info.djvar@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hello there. After installing openSUSE Tumbleweed on my partner's laptop (Lenovo IdeaPad Flex 15D with an AMD A6 APU (with ATI Radeon HD 8400 graphics processor)), I noticed that the display brightness is so low and I can't change it at all, not through the brightness keys on the keyboard, nor through the display brightness slider in the power management applet. I am on XFCE4 and with the latest kernel 5.18.12-1-default. The curious thing is that I noticed this exact same behaviour (brightness stuck at previous state) on my own Lenovo ThinkPad as well. But rolling back BTRFS snapshot to previous kernel version (5.18.11-1-default) fixed the issue and brightness keys and brightness slider were working as expected again, so I now know that this is a kernel bug of 5.18.12-1-default. Now, I managed to downgrade the kernel on the Lenovo IdeaPad Flex 15D by downloading it from an archive of recent Tumbleweed snapshots, but the problem was still there, nothing changed at all, so I thought I potentially missed on some other packages needed to solve the issue, that don't come bundled with the kernel (like some additional firmware or other similar stuff), but downgrading kernel version to the previous one on my Lenovo ThinkPad definitely solves this issue, as I said before, after the upgrade even the ThinkPad started behaving the same way, but downgrading to a previous snapshot helped. I am more than happy to give you logs or additional troubleshooting information that you might need. I just hope that you can help me get rid of this annoyance for my partner. I thank you all very much for your attention -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |info.djvar@gmail.com, | |tiwai@suse.com Flags| |needinfo?(info.djvar@gmail. | |com) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- First off, could you verify whether the problem persists with the latest OBS Kernel:stable kernel? Currently it's 5.18.15, and it should move to 5.19 in tomorrow, supposedly. Note that it's an unofficial build, hence you'd need to disable Secure Boot. If the problem is still there with the latest Kernel:stable, please upload the hwinfo output and the dmesg output to Bugzilla. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c2 Vittorio Basile <info.djvar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(info.djvar@gmail. | |com) | --- Comment #2 from Vittorio Basile <info.djvar@gmail.com> --- Ok. So with the OBS kernel (5.18.15) default the system wouldn't even boot at all. It said something about the touchpad not being recognised or something like that. So, here are pastebins for hwinfo and dmesg. hwinfo: https://paste.opensuse.org/40483401 dmesg: https://paste.opensuse.org/25075829 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Could you upload to Bugzilla (use attachments) instead? Also, check the 5.19 kernel in OBS Kernel:HEAD repo, too. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c4 --- Comment #4 from Vittorio Basile <info.djvar@gmail.com> --- Created attachment 860638 --> http://bugzilla.opensuse.org/attachment.cgi?id=860638&action=edit hwinfo -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c5 --- Comment #5 from Vittorio Basile <info.djvar@gmail.com> --- Created attachment 860639 --> http://bugzilla.opensuse.org/attachment.cgi?id=860639&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c6 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(info.djvar@gmail. | |com) --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- Thanks. The machine is with radeon driver, and it seems having a sysfs backlight control. Could you check the entries in /sys/class/backlight/*? If there is a directory (usually a symlink), go to there, and check the content of "brightness" and "max_brightness" there. i.e. % cat /sys/class/backlight/*/brightness % cat /sys/class/backlight/*/max_brightness Then try to change the value by writing to */brightness (as root): e.g. % su # echo 50 > /sys/class/backlight/*/brightness Does this change the backlight level? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c7 --- Comment #7 from Vittorio Basile <info.djvar@gmail.com> --- cat /sys/class/backlight/*/brightness ---> 12 cat /sys/class/backlight/*/max_brightness ---> 255 I remember changing the value of brightness as sudo once and it did change the brightness BUT, as soon as I would do a reboot it would just freeze at the Tumbleweed loading logo with no apparent errors or warnings in the bootstrap. Anyway, this time around changing the value to 50 in the brightness file did increase the display brightness indeed like last time and it also updates the brightness slider in the brightness (power management) applet. But still the brightness keys and slider didn't respond at all. Upon reboot this time, it gets to the XFCE4 desktop, and it stuck at the display brightness of '50' as set before reboot. Again, I cannot alter it unless I go through this manual method... -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202125 http://bugzilla.opensuse.org/show_bug.cgi?id=1202125#c8 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X.Org Assignee|kernel-bugs@opensuse.org |gfx-bugs@suse.de QA Contact|qa-bugs@suse.de |gfx-bugs@suse.de Flags|needinfo?(info.djvar@gmail. | |com) | --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- (In reply to Vittorio Basile from comment #7)
So, this doesn't look like a kernel problem. Writing your favorite level to the sysfs should change the current brightness, and this is the only interface the kernel provides. The rest is the user-space implementation, and that's likely the missing piece for radeon. Note that systemd remembers the last brightness at reboot/shutdown time, and tries to restore it at the next boot. That's why it sticks with 50. If you reboot after changing to a higher value, it'll be restored at the next reboot. I thought that is should be possible to specify the backlight device entry in X11 config. I'm not sure whether radeon also allows it, though. In anyway, as it's rather an issue of X, reassigned. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com