Fedora 44 (GNOME) on iMac Mid-2015 (AMD): screen brightness resets to maximum on every reboot

Hi everyone,

I’m running Fedora 44 with GNOME on an iMac (Mid-2015) with an AMD GPU. Every time I reboot, the screen brightness goes back to 100%, no matter what level I had set before shutting down.

What I’ve checked so far:

•	ls /sys/class/backlight/ returns a single interface: radeon_bl0.
•	/var/lib/systemd/backlight/ does not exist, so it looks like systemd-backlight has never saved a value on this machine.
•	I disabled automatic brightness in GNOME settings, and also the related options under Power (dim screen, etc.). It makes no difference: brightness is always at maximum after boot.

My questions:

  1. Is the right fix to install brightnessctl and run a startup script (e.g. a GNOME autostart entry running brightnessctl set 70% after a short delay)? Or is there a cleaner way to make systemd-backlight save and restore the value properly?
  2. Is this a known issue with radeon on this hardware or with Fedora/GNOME? If so, is there a kernel parameter or a udev rule that would fix it?
  3. Is there anything else I should check (service status, journal logs, GNOME settings daemon) to find out why the value isn’t being saved or restored?

I can provide the output of systemctl status ‘systemd-backlight@backlight:radeon_bl0.service’, journalctl -b, or anything else that helps.

Thanks in advance!

Your issue looks really like

The only difference could be your device uses radeon_bl0 not amdgpu_bl0?

What does

cat /sys/class/backlight/radeon_bl0/brightness
cat /sys/class/backlight/radeon_bl0/actual_brightness
cat /sys/class/backlight/radeon_bl0/max_brightnes

each return WHILE YOU SCREEN IS NOT AT MAX BRIGHTNESS.

Which kernel are you using?

uname -r

Hi Shivank,

Kernel is 7.2.11-200.fc44.x86_64

If I setting the brightness in gnome around the middle I obtain the next :
brightness: 117
actual_brightness:117
max_brightness: 255

If I reboot all the values are in 255

A brightnessctl autostart entry would work, but I’d find out why systemd-backlight isn’t saving the level first.

The missing /var/lib/systemd/backlight/ directory means the save step at shutdown has never written a value. Check whether the unit ran this boot with

systemctl show -p ActiveState,SubState,Result 'systemd-backlight@backlight:radeon_bl0.service'

Then check what it logged during the previous boot and shutdown with

journalctl -b -1 -o cat -u 'systemd-backlight@backlight:radeon_bl0.service'

If the unit shows as inactive with nothing in the journal, udev isn’t starting it for radeon_bl0, and that is the part to fix.

Drafted with AI, reviewed by me.

Thank you Christopher,

return me:

  1. ActiveState: inactive
  2. SubState: dead
  3. Result: success

and
'journalctl -b -1 -o cat -u ‘systemd-backlight@backlight:radeon_bl0.service’

do not return any text

then I tested:
'systemctl status ‘systemd-backlight@backlight:radeon_bl0.service’
to check if the service exist
systemd-backlight@backlight:radeon_bl0.service - Load/Save Screen Backlight Brightness of backlight:radeon_bl0
Loaded: loaded (/usr/lib/systemd/system/systemd-backlight@.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
Docs: man:systemd-backlight@.service(8)

What does this print?

udevadm info /sys/class/backlight/radeon_bl0 | grep -E 'TAGS|SYSTEMD_WANTS'

Drafted with AI, reviewed by me.

Hi Christopher,

E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

What do these two print?

grep -n backlight /usr/lib/udev/rules.d/99-systemd.rules
ls /etc/udev/rules.d/

Drafted with AI, reviewed by me.