Skip to content

Brightness above 64267 results in brightness lower than 0 #244

Description

@non-bin

Device Information

Framework Laptop 16 (AMD Ryzen™ 7040 Series)
BIOS 04.05

Describe the bug

Since the latest BIOS update, when a brightness above 64267 is requested, it seems to overflow.
I generated this table:

brightnessactual_brightnessComment
03341I think this is normal
40003341
50003829
60004073
6000061633
6400065291Oh dear...
6426765535Uh oh...
642680Ah. The backlight is still on though
653000There is a perceptable brightness change
655000And again
655350This is still darker than asking for 0 brightness
Using this script
b() {
echo$1>/sys/class/backlight/amdgpu_bl1/brightness
cat /sys/class/backlight/amdgpu_bl1/brightness | tr -d '\n'printf" | "
cat /sys/class/backlight/amdgpu_bl1/actual_brightness
}
echo"brightness | actual_brightness"echo"-|-"
b 0 # 3341
b 4000 # 3341
b 5000 # 3829
b 6000 # 4073
b 60000 # 61633
b 64000 # 65291
b 64267 # 65535
b 64268 # 0
b 65000 # 0
b 65300 # 0
b 65500 # 0
b 65535 # 0

Ideally I would like to keep the new low minimum brightness, just without having to script around the overflow. Could we please just have direct controll over the brightness? Maybe even be able to turn the backlight off?

Example workaround script
if [ "$1"=="" ] ||(($1>65535))||(($1<0));thenecho ERROR: Value is out of range
exit 1
fi
x=$(($1-1268))if((x <0));thenecho$((64268+$1))>/sys/class/backlight/amdgpu_bl1/brightness
elseecho$x>/sys/class/backlight/amdgpu_bl1/brightness
fi

Operating System (please complete the following information):

  • OS/Distribution: NixOS
  • Version: updated yesterday
  • Linux Kernel Version: Linux skellybones 7.1.7 #1-NixOS SMP PREEMPT_DYNAMIC Thu Aug 6 17:28:04 UTC 2026 x86_64 GNU/Linux

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions