# \[Solved\] - Screen goes very dim when reaching 100% Brightness

**URL:** <https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042>\
**Category:** Community Support\
**Tags:** display-issues, amd-7040\
**Created:** [August 10, 2026, 3:02pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042 "2026-08-10T15:02:01Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Augustin\_Trancart](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Augustin\_Trancart](https://community.frame.work/u/Augustin_Trancart)\
**Post date:** [August 10, 2026, 3:02pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/1 "2026-08-10T15:02:01Z")

</div>

When going to 100% brightness, my Framework 16 laptop screen becomes dim. It goes back to very bright at 95%.

I’m running:

- nixos 26.05
- Laptop 16 AMD 7040 series
- kde

I did make a firmware update at the same time (shouldn’t have, yes, I know), but I rebooted in an old nixos generation and couldn’t reproduce the problem, so I assume it is not a firmware issue, but a kernel one. Last working revision is `26.05.20260719.fd14620` (linux-6.18.39). It got broken in `26.05.20260807.ee48b14` (linux-6.18.43).

Thanks for the help

---

<div class="post-metadata">

**Author:** ![Charlie\_6](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/charlie_6/32/22087_2.png) [@Charlie\_6](https://community.frame.work/u/Charlie_6)\
**Post date:** [August 12, 2026, 7:33am UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/2 "2026-08-12T07:33:07Z")

</div>

I got this on my other (non-Framework) laptop as well, often after waking up from sleep. Likely a Linux or KDE version problem

---

<div class="post-metadata">

**Author:** ![Augustin\_Trancart](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Augustin\_Trancart](https://community.frame.work/u/Augustin_Trancart)\
**Post date:** [August 12, 2026, 8:34am UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/3 "2026-08-12T08:34:17Z")

</div>

Oh important info! Which OS/version are you using? Is it a recent problem? Do you experience it every time, or only from time to time? After a cold boot?

---

<div class="post-metadata">

**Author:** ![Charlie\_6](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/charlie_6/32/22087_2.png) [@Charlie\_6](https://community.frame.work/u/Charlie_6)\
**Post date:** [August 12, 2026, 11:22am UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/4 "2026-08-12T11:22:07Z")

</div>

Hardware: AMD 5900HX NVIDIA RTX 3070 Max-Q  
Software: EndeavourOS Linux 7.1.6, Plasma 6.7.4, Wayland.

It happens more often than I previously thought. I witnessed the problem a few days before it first happened on a Framework

---

<div class="post-metadata">

**Author:** ![Crystalyne](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/crystalyne/32/606_2.png) [@Crystalyne](https://community.frame.work/u/Crystalyne)\
**Post date:** [August 12, 2026, 11:47am UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/5 "2026-08-12T11:47:12Z")

</div>

Can confirm that I too have been seeing this on my FW16 running Fedora Silverblue 44.

Video of the brightness bug:

> **[New video · Wednesday, Aug 12 🎬](https://photos.google.com/share/AF1QipOxBotmd2uZWHy9LwEtE8bhFyT-QPDs1KIYJB4a5v7U_8JvcspT2ms1P6_sAjE1yw?key=NWN4ZnJlbnI5Ml91d0VZdndVVDVlRG41eWdzTDlR)**

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [August 12, 2026, 11:53am UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/6 "2026-08-12T11:53:25Z")

</div>

Update for me:  
FW16 AMD 7840HS. No dGPU.  
Brightness bug:  
Linux mainline kernel 7.1.5 OK.  
Linux mainline kernel 7.1.6, 7.1.7, 7.1.8 Bad.  
Linux firmware is latest from git, for all kernel version tests, so I don’t think it is amd gpu firmware related or mesa version related.  
I am using 7.1.8 because it fixes some other green noise artifacts.  
So, something in here is causing the brightness bug:  
[https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.6](https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.6)

Looking at:  
/sys/devices/pci0000:00/0000:00:08.1/0000:c1:00.0/drm/card0/card0-eDP-1/amdgpu\_bl0

brightness: 62291 is bright. 65535 is dim  
actual\_brightness: 63584 is bright. 0 is dim

So, it seems that “actual\_brightness” matches what the user sees happening.  
the “brightness” matches what the user sees, except at the 65535 setting.  
So, there is some sort of bug mapping brightness → actual\_brightness.

Linux kernel documentation:  
What: /sys/class/backlight/\<backlight\>/brightness  
Date: April 2005  
KernelVersion: 2.6.12  
Contact: Richard Purdie [rpurdie@rpsys.net](mailto:rpurdie@rpsys.net)  
Description:  
Control the brightness for this . Values  
are between 0 and max\_brightness. This file will also  
show the brightness level stored in the driver, which  
may not be the actual brightness (see actual\_brightness).  
Users: HAL

What: /sys/class/backlight/\<backlight\>/actual\_brightness  
Date: March 2006  
KernelVersion: 2.6.17  
Contact: Richard Purdie [rpurdie@rpsys.net](mailto:rpurdie@rpsys.net)  
Description:  
Show the actual brightness by querying the hardware. Due  
to implementation differences in hardware this may not  
match the value in ‘brightness’. For example some hardware  
may treat blanking differently or have custom power saving  
features. Userspace should generally use the values in  
‘brightness’ to make decisions.  
Users: HAL

---

<div class="post-metadata">

**Author:** ![Augustin\_Trancart](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Augustin\_Trancart](https://community.frame.work/u/Augustin_Trancart)\
**Post date:** [August 12, 2026, 3:19pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/7 "2026-08-12T15:19:34Z")

</div>

skimming the changelog, I have this strong candidate:

```auto
commit 490ceacd2162de919a142bcb4eff363bb493b1de
Author: Mario Limonciello <mario.limonciello@amd.com>
Date: Mon Jun 29 15:27:00 2026 -0500

    drm/amd/display: Fix backlight max_brightness to match exported range
    
    commit f1b5d8f9cc54ae8a2567ac126867ae488e1bf625 upstream.
    
    [Why]
    FWTS autobrightness fails on eDP panels because actual_brightness can
    read higher than the advertised max_brightness (e.g. 63576 vs 62451).
    
    The conversion helpers expose the firmware PWM range to userspace as
    [0..max]. But max_brightness is advertised as (max - min), which is
    smaller. So reading the level can return a value above max_brightness.
    
    This regressed in commit 4b61b8a39051 ("drm/amd/display: Add debugging
    message for brightness caps"), which changed max_brightness to
    (max - min) and undid commit 8dbd72cb7900 ("drm/amd/display: Export full
    brightness range to userspace").
    
    [How]
    Advertise max_brightness as max, and scale the initial AC/DC brightness
    against max too. Update the KUnit expectations to match.
    
    Fixes: 4b61b8a39051 ("drm/amd/display: Add debugging message for brightness caps")
    Reviewed-by: Alex Hung <alex.hung@amd.com>
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: George Zhang <george.zhang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    (cherry picked from commit bd9e2b5b0473c75abc0f4134dfe79ecbfb16610d)
    Cc: stable@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

```

I’m going to test with this commit reverted and we’ll see.

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [August 12, 2026, 4:19pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/8 "2026-08-12T16:19:43Z")

</div>

> [@Augustin\_Trancart](#):
>
> `commit f1b5d8f9cc54ae8a2567ac126867ae488e1bf625`

That may contribute to it, but at a guess I would expect the bug to be somewhere here:

in file: drivers/gpu/drm/amd/display/amdgpu\_dm/amdgpu\_dm.c

```auto
static void amdgpu_dm_backlight_set_level(struct amdgpu_display_manager *dm,
                                         int bl_idx,
                                         u32 user_brightness)

```

At a glance, it all looks a little too complex for something as simple as brightness control.  
I can see that is it easy to make mistakes where in some places in the code “brightness” means the hardware setting, and in other places “brightness” means the setting the users can set. Giving two very different things the same variable name is a recipe for confusion.

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [August 12, 2026, 8:55pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/9 "2026-08-12T20:55:24Z")

</div>

Temporary fix / work around found for the 100% brightness problem.

Add this to the grub kernel command line:  
`amdgpu.dcdebugmask=0x40000`

It essentially disables this function:

```auto
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c:
static void convert_custom_brightness(const struct amdgpu_dm_backlight_caps *caps,
                                      unsigned int min, unsigned int max,
                                      uint32_t *user_brightness)
{
        u32 brightness = scale_input_to_fw(min, max, *user_brightness);
        u8 lower_signal, upper_signal, upper_lum, lower_lum, lum;
        int left, right;

        if (amdgpu_dc_debug_mask & DC_DISABLE_CUSTOM_BRIGHTNESS_CURVE)
                return;

```

Note: DC\_DISABLE\_CUSTOM\_BRIGHTNESS\_CURVE == 0x40000

---

<div class="post-metadata">

**Author:** ![Augustin\_Trancart](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Augustin\_Trancart](https://community.frame.work/u/Augustin_Trancart)\
**Post date:** [August 13, 2026, 7:17am UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/10 "2026-08-13T07:17:04Z")

</div>

I confirm that reverting this commit fixes the issue for me.

---

<div class="post-metadata">

**Author:** ![herman45](https://avatars.discourse-cdn.com/v4/letter/h/a5b964/32.png) [@herman45](https://community.frame.work/u/herman45)\
**Post date:** [August 13, 2026, 11:49am UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/11 "2026-08-13T11:49:10Z")

</div>

I think it is a kernel regression rather than a hardware problem, especially since 6.18.39 works and 6.18.43 shows the issue. I would sugget boot the working NixOS generation for now and compare the display/brightness changes between those kernel versions.

---

<div class="post-metadata">

**Author:** ![David\_A\_Buser](https://avatars.discourse-cdn.com/v4/letter/d/bc79bd/32.png) [@David\_A\_Buser](https://community.frame.work/u/David_A_Buser)\
**Post date:** [August 13, 2026, 12:34pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/12 "2026-08-13T12:34:17Z")

</div>

Confirmed: adding amdgpu.dcdebugmask=0x40000 to the kernel command line fixes the issue for me. After rebuilding and rebooting, 100% brightness is bright again instead of  
making the panel go dark. I’m on a Framework 16 AMD 7040 running NixOS 26.11 with kernel 6.18.43 and the amdgpu\_bl1 backlight device. Before the workaround, the panel  
became very dim at 99%, 99.9%, and 100%; 95% remained bright. This appears consistent with the AMDGPU custom-brightness-curve regression. Thanks for identifying the  
workaround!

---

<div class="post-metadata">

**Author:** ![Augustin\_Trancart](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Augustin\_Trancart](https://community.frame.work/u/Augustin_Trancart)\
**Post date:** [August 13, 2026, 1:10pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/13 "2026-08-13T13:10:06Z")

</div>

I’ve opened a bug on the kernel bugtracker : [https://bugzilla.kernel.org/show\_bug.cgi?id=221879](https://bugzilla.kernel.org/show_bug.cgi?id=221879)

And I’ve marked the kernel grub argument as the solution, because it’s really easiest than recompiling the whole kernel 😆.

---

<div class="post-metadata">

**Author:** ![Augustin\_Trancart](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Augustin\_Trancart](https://community.frame.work/u/Augustin_Trancart)\
**Post date:** [August 13, 2026, 3:10pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/14 "2026-08-13T15:10:44Z")

</div>

Actually, the correct bugtracker is not [bugzilla.kernel.org](http://bugzilla.kernel.org). The correct issue is: [Making sure you're not a bot!](https://gitlab.freedesktop.org/drm/amd/-/work_items/5562). It’s already fixed, so we should get the fix soon!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\
**Post date:** [August 15, 2026, 3:11pm UTC](https://community.frame.work/t/solved-screen-goes-very-dim-when-reaching-100-brightness/84042/15 "2026-08-15T15:11:21Z")

</div>

Closed on August 15, 2026, 3:11pm UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
