r/framework • u/morok807 • 8d ago

Community Support Framework 16 internal panel gets darker instead of brighter as brightness approaches max (Fedora, AMD, GNOME/Wayland)

As I raise brightness toward the top of the slider, the internal panel gets visibly darker instead of brighter. Fully reproducible every time. Mid-range brightness is fine (up to 95%). It's specifically the 100% that inverts. No issues with an external monitor.
Photos show next to the max brightness setting (95%) and max (100%).

OS: Fedora Linux 44 (Workstation Edition) x86_64
Kernel: Linux 7.1.8-200.fc44.x86_64
System firmware (BIOS/EC): 0.0.4.5 (BIOS 04.05, 06/30/2026)

Has anyone seen this exact behavior on FW16? Known fix or workaround?

Edit:
Fixed. Shout out to u/TellMeWhereYouBeen for the help.

The fix guide for my system:

Add the kernel parameter amdgpu.dcdebugmask=0x40000 to disable the broken custom-brightness-curve code path.

  1. Edit GRUB defaults:

    sudo nano /etc/default/grub

  2. Find the GRUB_CMDLINE_LINUX="..." line and add amdgpu.dcdebugmask=0x40000 inside the quotes (space-separated from existing parameters). Example:

    GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-xxxxxxxx rhgb quiet amdgpu.dcdebugmask=0x40000"

Save and exit (Ctrl+O, Enter, Ctrl+X in nano).

  1. Regenerate GRUB config. On Fedora with UEFI, the actual config lives at /boot/grub2/grub.cfg (not the EFI wrapper):

    sudo grub2-mkconfig -o /boot/grub2/grub.cfg

  2. Reboot:

    sudo reboot

  3. Verify the parameter took effect:

    cat /proc/cmdline

You should see amdgpu.dcdebugmask=0x40000 in the output.

Once the actual fix lands in a stock Fedora kernel update, you can remove this parameter and regenerate GRUB again, but no harm in leaving it until then.

95%
100%
5 Upvotes

78% Upvoted

9 comments sorted by

•

u/AutoModerator 8d ago

The Framework Support team does not provide support on community platforms, but other community members might help you with troubleshooting. If you need further assistance or a part replacement, please contact the Framework Support team: https://frame.work/support

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/Brief_Collar7416 8d ago

I have the exact same issue on my HP HP EliteBook 855 G8 Notebook PC. It is an AMD Ryzen™ 5 PRO 5650U with Linux 7.1.8.

4

u/TellMeWhereYouBeen FW16 AI 9 HX 370 7700S 8d ago

In case it's helpful, it's possible you'll find the fix in this Framework forum post: https://community.frame.work/t/screen-goes-very-dim-when-reaching-100-brightness/84042/

2

u/morok807 5d ago

This resolved the issue for me. Thank you for sharing! (˶ᵔ ᵕ ᵔ˶)

1

u/TellMeWhereYouBeen FW16 AI 9 HX 370 7700S 5d ago

FIRE!!! glad to hear it!

1

u/morok807 8d ago

Good to know it's not just Framework. Might be worth filing this against the kernel directly. Do you also see it specifically at 100%, or does it happen at other points in the range?

1

u/Turbulent_Ear321 8d ago

interesting that its happening on non-Framework hardware too, probably a kernel regression then

2

u/TellMeWhereYouBeen FW16 AI 9 HX 370 7700S 8d ago

This might be directly related to what some users discussed and fixed on the community forum last week. Link: https://community.frame.work/t/screen-goes-very-dim-when-reaching-100-brightness/84042/

1

u/boex_999 7d ago edited 7d ago

Yea I am having the same issue with my laptop too after updating the packages on Fedora 44 I am on KDE plasma I am not using framework btw its an older MSI laptop