From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221879] New: Max brightness broken since 6.18.42 / 7.1.6
Date: Thu, 13 Aug 2026 13:00:50 +0000 [thread overview]
Message-ID: <bug-221879-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221879
Bug ID: 221879
Summary: Max brightness broken since 6.18.42 / 7.1.6
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: augustin@trancart.eu
Regression: No
# Description
When setting my brightness to 100%, the display becomes very dim. It goes back
to bright when going back to 95%.
According to some users [1], this affects framework 16 laptops (at least AMD
5900HX NVIDIA RTX 3070 Max-Q and FW16 AMD 7840HS without dGPU). One user also
reported this with another non-framework laptop.
Seemingly all linux distros are affected (at least Fedora Silverblue, NixOS
26.05, EndeavourOS Linux 7.1.6) and various DEs.
I've identified 490ceacd2162de919a142bcb4eff363bb493b1de as a potential culprit
(in the 6.18.43 branch) because I don't reproduce any more if I build my kernel
with this commit reverted (The commit is
1191285ecb4233e5bf907da7e9394d7999055566 for the 7.1.6 branch).
[1]:
https://community.frame.work/t/screen-goes-very-dim-when-reaching-100-brightness/84042
Thanks!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2026-08-13 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 13:00 bugzilla-daemon [this message]
2026-08-13 13:05 ` [Bug 221879] Max brightness broken since 6.18.42 / 7.1.6 bugzilla-daemon
2026-08-13 13:05 ` bugzilla-daemon
2026-08-13 13:26 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221879-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.