MediumAbout 20 minutesBoth

Brightness keys stopped working on Linux

Why does my laptop's brightness keys not work after installing Linux?

CF

Written by The CommonFixes team · fact checked by CommonFixes review desk

Last updated

Short answer

Brightness on a laptop is not really a keyboard function. The key asks the firmware, the firmware answers through a standard called ACPI, and the graphics driver then changes the backlight. Windows ships with the maker's own driver that knows the quirks of your model. A fresh Linux install has to guess, and on many machines it picks the wrong one of several backlight interfaces, so the key press goes nowhere. The fix is to tell the kernel which interface to use, and it is a one line change that survives reboots. The quickest thing to try first: check whether the system can change brightness at all — Open a terminal and run ls /sys/class/backlight/. You will usually see something like intel_backlight, amdgpu_bl0 or acpi_video0. Then run cat /sys/class/backlight/*/brightness to see the current value. If the folder is empty, the kernel has found no way to control the panel yet, which is what the next steps repair. Most people are done in about 20 minutes.

Full walkthrough below: 7 steps for Windows and Mac, rated medium.

Sounds like this

  • The brightness keys do nothing at all, or the on screen slider moves but the panel stays the same
  • Brightness is stuck at full and drains the battery
  • It worked perfectly in Windows before the change

Why it happens

Brightness on a laptop is not really a keyboard function. The key asks the firmware, the firmware answers through a standard called ACPI, and the graphics driver then changes the backlight. Windows ships with the maker's own driver that knows the quirks of your model. A fresh Linux install has to guess, and on many machines it picks the wrong one of several backlight interfaces, so the key press goes nowhere. The fix is to tell the kernel which interface to use, and it is a one line change that survives reboots.

Work through these in order

0% done
  1. 1

    Check whether the system can change brightness at all

    Open a terminal and run ls /sys/class/backlight/. You will usually see something like intel_backlight, amdgpu_bl0 or acpi_video0. Then run cat /sys/class/backlight/*/brightness to see the current value. If the folder is empty, the kernel has found no way to control the panel yet, which is what the next steps repair.

  2. 2

    Test the control directly before blaming the keys

    Install the small tool brightnessctl with sudo apt install brightnessctl on Ubuntu or Debian, or sudo dnf install brightnessctl on Fedora, then run brightnessctl set 30%. If the screen dims, the hardware is fine and only the key mapping needs work. If nothing happens, the kernel is using the wrong backlight interface and the next step is the important one.

  3. 3

    Tell the kernel which backlight interface to use

    Edit the boot options with sudo nano /etc/default/grub and add acpi_backlight=native inside the quotes on the GRUB_CMDLINE_LINUX_DEFAULT line, so it reads something like quiet splash acpi_backlight=native. Save, run sudo update-grub (or sudo grub2-mkconfig -o /boot/grub2/grub.cfg on Fedora), and reboot. This one change fixes the majority of laptops. If it does not help, repeat with acpi_backlight=video, and after that acpi_backlight=vendor, testing after each reboot.

  4. 4

    Update the firmware, because it is often the real cause

    Run sudo fwupdmgr refresh followed by sudo fwupdmgr update. Most Dell, Lenovo, HP and Framework laptops publish their firmware to Linux through this service, and a firmware bug in how the machine reports its backlight is a well known reason for dead brightness keys.

  5. 5

    Make sure the desktop is listening to the keys

    In GNOME open Settings, Keyboard, View and Customise Shortcuts and check that the brightness up and down entries are still bound. Run xev or wev in a terminal and press the key: if nothing at all is printed, the key is not even reaching the desktop, and the model specific kernel module is missing. Search your model name together with the words Linux backlight on the Arch Wiki, which lists per model modules such as dell-laptop, thinkpad_acpi or asus-nb-wmi and how to load them.

  6. 6

    Fall back to a shortcut that always works

    If the physical keys refuse to co-operate, bind your own. In Settings, Keyboard, Custom Shortcuts add two shortcuts running brightnessctl set 10%+ and brightnessctl set 10%-, and attach them to any free key combination. It is not elegant, but it is reliable, and you can stop hunting.

  7. 7

    Try a newer kernel before giving up

    Backlight support for newer laptops arrives with new kernel versions. On Ubuntu install the hardware enablement kernel with sudo apt install linux-generic-hwe-22.04 (match the number to your release), or simply install the current version of Fedora, which ships a very recent kernel. Plenty of machines that had no brightness control a year ago work out of the box today.

If none of that worked

Note your exact model, then look it up on the Arch Wiki and in the Ubuntu certified hardware list. Both record the precise boot option other people needed for the same machine. If your laptop uses a switchable graphics setup with two chips, also check that you are running on the integrated chip, because the backlight is wired to that one and hybrid setups are the usual reason a working fix stops working.

Did this fix work for you?

A quick thumbs up helps other readers find the guides that actually work.

Share this fix

Related fixes worth reading

Chosen automatically from the 157 guides on CommonFixes, based on how closely they match this problem.

Still not it? Browse every fix or see more in screen troubles.

Who wrote this and how we checked it

CF

The CommonFixes team

Writer and researcher

We are a small group of people who spend our days repairing laptops and desktops for family, friends and small offices. Every guide here starts with a problem someone actually brought to us, and we only write down the steps that put the machine right.

  • Everyday repairs
  • Windows and Mac
  • Plain language
RD

CommonFixes review desk

Technical editor

Before a guide goes live, a second person walks through it on a real machine and checks each instruction against the maker's own support pages. Anything we cannot confirm is removed rather than guessed at.

  • Fact checking
  • Safety warnings
  • Source links

This guide was last updated on 11 August 2026. If a step no longer matches what you see on screen, tell us on the contact page and we will test it again.

A gentle reminder: back up anything you cannot afford to lose before major repairs. If a step ever feels risky, stop and ask a technician. There is no shame in that.