All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221933] New: Screen brightness dimmer since kernel 7.2 (amdgpu)
Date: Sat, 29 Aug 2026 06:11:27 +0000	[thread overview]
Message-ID: <bug-221933-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221933

            Bug ID: 221933
           Summary: Screen brightness dimmer since kernel 7.2 (amdgpu)
           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: 3lefji@gmail.com
        Regression: No

Hi everyone,

Follow-up on a brightness issue I've been having since the kernel 7.2 update
(still present in 7.2.2). Sharing what I found in case it helps others or
points to the root cause.

System info:
- Laptop: Lenovo IdeaPad Gaming 3
- CPU: AMD Ryzen 5 5500H (iGPU handles the internal display backlight)
- GPU: Nvidia RTX 2050 (hybrid AMD/Nvidia, PRIME render offload setup)
- OS: Fedora 44, GNOME 50, Wayland
- Kernel: 7.2.2-cachyos
- Backlight device: amdgpu_bl1

Issue: since kernel 7.2, the same brightness percentage looks much dimmer than
before. I used to sit around 30% in dim rooms, now I need about 60% for the
same visual result. Raw values:
```
cat /sys/class/backlight/amdgpu_bl1/brightness -> 45755
cat /sys/class/backlight/amdgpu_bl1/max_brightness -> 65535
```
So roughly 70% reported but visually much closer to what used to be ~30-35%.
Looks like a mapping/curve change in the amdgpu backlight handling, similar to
reports I found for other kernel versions affecting amdgpu_bl on AMD laptops
(both integrated and hybrid setups).

I tried the common workaround of adding amdgpu.backlight=vendor to
GRUB_CMDLINE_LINUX. Brightness mapping did go back to normal after that change,
BUT it caused severe system instability right after the password screen:
extreme lag, barely able to move the mouse, a strange fade/scanline artifact on
the lock screen, GPU idle at 32°C while CPU sat at 13% doing nothing. Had to
revert the kernel parameter to get a usable system again.

So amdgpu.backlight=vendor is not a safe workaround at least on this hybrid
AMD/Nvidia + Wayland + GNOME 50 combination.

Has anyone found a fix that doesn't cause this kind of freeze, or is this a
case where we just need to wait for an upstream amdgpu fix? Happy to test
patches or provide more logs if useful.

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.

             reply	other threads:[~2026-08-29  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29  6:11 bugzilla-daemon [this message]
2026-08-31  7:07 ` [Bug 221933] Screen brightness dimmer since kernel 7.2 (amdgpu) 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-221933-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.