Backlight: Difference between revisions

From NixOS Wiki
imported>BenSchaeffner
No edit summary
Klinger (talk | contribs)
m link to category instead of redirect page
 
(15 intermediate revisions by 11 users not shown)
Line 1: Line 1:
{{expansion}}
This page documents methods for controlling backlight (aka screen brightness) and tips to control it via hotkeys.
== Introduction ==
 
This page documents methods for enabling backlight (aka screen brightness) control via hotkeys.
== Kernel native ==
 
Some laptops, using a recent enough kernel, will automatically handle increasing and decreasing the backlight using the hot keys. The following tools will allow scripting or controlling the backlight using other means, if desired.
 
== Desktop Environment native ==
 
Some desktop environments will handle querying and setting the backlight, including configuring the backlight keys. These include at least: Plasma (KDE) and XFCE. It may be needed to configure or start some desktop environment-specific services.


== <code>xbacklight</code> ==
== <code>xbacklight</code> ==
Line 7: Line 13:
<code>xbacklight</code> uses X to change the light settings. This can be inconvenient in some situations, e.g. for use with the {{nixos:option|services.actkbd}} service, which doesn't know about the X session. It, though, has an history of being more compatible with different hardware, especially newer hardware<sup>[citation needed]</sup>
<code>xbacklight</code> uses X to change the light settings. This can be inconvenient in some situations, e.g. for use with the {{nixos:option|services.actkbd}} service, which doesn't know about the X session. It, though, has an history of being more compatible with different hardware, especially newer hardware<sup>[citation needed]</sup>


To enable xbacklight via configuration.nix add:<p>
To install <code>xbacklight</code> globally, add this to your <tt>configuration.nix</tt>.
<code>environment.systemPackages = with pkgs; [ xorg.xbacklight ];</code>
<syntaxhighlight lang=nix>
  environment.systemPackages = with pkgs; [ xorg.xbacklight ];
</syntaxhighlight>
 
Alternatively, use <code>nix-env -iA nixos.xorg.xbacklight</code> to install it to your user profile.


== <code>light</code> ==
== <code>light</code> ==


<code>light</code> does not use X to change the light settings. This can be used in situations where the X service isn't available.</code>
<code>light</code> does not use X to change the light settings. This can be used in situations where the X service isn't available. While it does not use X, it will need some privileges to work.
 
To enable the use of <code>light</code>, add this to your <tt>configuration.nix</tt> and make sure that your user is a member of the <code>video</code> group.
 
<syntaxhighlight lang=nix>
  programs.light.enable = true;
</syntaxhighlight>
 
The following commands will allow you to test <code>light</code>:
* <code>light -U 30</code> — the screen should become darker.
* <code>light -A 30</code> — the screen should become brighter.
 
Be careful using <code>light -U</code>, as you might turn your backlight completely off! You will not be able to see what you're typing anymore.
 
== <code>brightnessctl</code> ==
 
{{nixos:package|brightnessctl}} ([https://github.com/Hummer12007/brightnessctl homepage]) is another option, which, like <code>light</code>, would work even without X or on Wayland.
 
You can use it by simply installing the package. Since <code>brightnessctl</code> supports the systemd-logind API it should work out of the box (i.e. without installing any udev rules or using a setuid wrapper).
 
The following commands will allow you to test <code>brightnessctl</code>:
* <code> brightnessctl set 5%-</code> - the screen should become darker.
* <code> brightnessctl set 5%+</code> - the screen should become brighter.
 
If you get an error like <code>Failed to set brightness: Protocol error</code>, check that you are using the right device. You can get a list of the devices with running <code>brightnessctl -l</code> and then specify the device with <code>-d deviceName</code>.
 
Example: <code>brightnessctl set 5%- -d intel_backlight</code>


To enable light via configuration.nix add:<p>
== <code>/sys/class/backlight/...</code> ==
<code>programs.light.enable = true;</code>


A reboot may be required.
The <code>/sys/class/backlight/*/brightness</code> files are a built-in way to set brightness. Use them e.g. with:


To test:<p>
<syntaxhighlight lang=bash>
<code> light -U 30</code> - the screen should become darker<p>
  sudo tee /sys/class/backlight/intel_backlight/brightness <<< 300
<code> light -A 30</code> - the screen should become brighter<p>
</syntaxhighlight>
Be careful using <code>light -U</code>, as you might turn your backlight completely off, and not see what you're typing any more.


== Key mapping ==
to set the brightness to <code>300</code>, where the maximum is stored in <code>brightness_max</code>. You can set file permissions e.g. with a udev rule, if you don't want to use sudo. Here is an example udev rule, where you will likely have to replace intel_backlight, with the name in your /sys/class/backlight/:


Once the backend functionality of controlling the backlight is verified, you can assign that to an actual key. Different laptops and keyboards may map the hotkeys to different key codes.
<syntaxhighlight lang=nix>
  services.udev.extraRules = ''
    ACTION=="add", SUBSYSTEM=="backlight", KERNEL=="intel_backlight", MODE="0666", RUN+="${pkgs.coreutils}/bin/chmod a+w /sys/class/backlight/%k/brightness"
  '';
</syntaxhighlight>


== Key mapping - obtain key codes via xev ==
== Tips ==
While logged into an X session:<p>
<code>nix-shell -p xorg.xev</code><p>
<code>xev</code><p>
Xev reports key codes, but they did not seem to be the right codes for use with actkbd.


== Key mapping - obtain key codes via actkbd ==
=== Key mapping ===
First enable the actkbd service (see below).<p>
To read key codes via actkbd, you need to select the right input event provider from /dev/input/. Each input device generating input events has it's own entry there, enumerated with an number. To find out which one generates the events from the hotkeys, it is viable (if tedious) to run the below command with each available entry, and see which one generates event notifications when pressing the brightness hotkeys:<p>
<code>actkbd -v9 -n -s -d /dev/input/event<number></code><p>
Once you discover the right one, it will report key presses like so:<p>
<code>Event: <number>:key</code><p>
<code>Event: <number>:rel</code><p>
Those represent the key-press and key-release actions. The number is the key code to use for mapping.


== Key mapping - map via actkbd service ==
While controlling the backlight via the command line is useful, it would be preferable to control it using key bindings. This is especially true considering most laptops have backlight control keys.
To map keys using actkbd service and the <code>light</code> program, add the following to your configuration.nix file:<p>
<code>services.actkbd = {
  enable = true;
  bindings = [
    {keys = [ <brightnessDown> ]; events = [ "key" ]; command = "run/wrappers/bin/light -U 10";}
    {keys = [ <brightnessUp> ]; events = [ "key" ]; command = "run/wrappers/bin/light -A 10";}
  ];
};</code>
Where <brightnessUp> and <brightnessDown> are the key codes obtained before.


== Working configuration on Lenovo T440 ==
There are two main choices to add key bindings, using a system-level service like [[actkbd]] or using an X session tool, either provided by your [[:Category:Desktop environment|Desktop environment]], [[Window manager]] or a tool like [[xbindkeys]].
To enable backlight control on a Lenovo T440, add to configuration.nix:


<code>programs.light.enable = true;
Depending on the tools that work for controlling the backlight you will be able to choose one of those options.
 
{| class="wikitable"
|-
!  
| <code>light</code>
| <code>xbacklight</code>
|-
! System service
| Yes
| With hacks
|-
! X session
| Yes
| Yes
|}
 
Follows, an example mapping for use with actkbd:
 
{{note|This was verified to work with
 
* NixOS 18.03 on a Lenovo T440 and
* NixOS 19.09pre173166.373488e6f4c on a Lenovo X240
 
it may work on other models, but is unconfirmed. See [[actkbd]] for details on finding out the proper key bindings. Also check if the path to the light binary is correct.}}
 
<syntaxhighlight lang=nix>
  programs.light.enable = true;
   services.actkbd = {
   services.actkbd = {
     enable = true;
     enable = true;
     bindings = [
     bindings = [
    { keys = [ 224 ]; events = [ "key" ]; command = "/run/wrappers/bin/light -A 10"; }
      { keys = [ 224 ]; events = [ "key" ]; command = "/run/current-system/sw/bin/light -A 10"; }
    { keys = [ 225 ]; events = [ "key" ]; command = "/run/wrappers/bin/light -U 10"; }
      { keys = [ 225 ]; events = [ "key" ]; command = "/run/current-system/sw/bin/light -U 10"; }
  ];
    ];
};</code>
  };
</syntaxhighlight>


== Enabling actkbd service ==
== OLED Screens ==


== Using <tt>/proc/</tt> ==
OLED screens do not have a backlight, but their perceived brightness can be changed via xrandr:


<tt>...</tt>
* <code>xrandr --output <output> --brightness .5</code> - dim to 50%
* <code>xrandr --output <output> --brightness 1</code> - no dimming


== See also ==
== See also ==


* [https://wiki.archlinux.org/index.php/backlight Arch Linux wiki page about the backlight]
* [https://wiki.archlinux.org/index.php/backlight Arch Linux wiki page about the backlight]
[[category:hardware]]

Latest revision as of 21:07, 1 July 2024

This page documents methods for controlling backlight (aka screen brightness) and tips to control it via hotkeys.

Kernel native

Some laptops, using a recent enough kernel, will automatically handle increasing and decreasing the backlight using the hot keys. The following tools will allow scripting or controlling the backlight using other means, if desired.

Desktop Environment native

Some desktop environments will handle querying and setting the backlight, including configuring the backlight keys. These include at least: Plasma (KDE) and XFCE. It may be needed to configure or start some desktop environment-specific services.

xbacklight

xbacklight uses X to change the light settings. This can be inconvenient in some situations, e.g. for use with the services.actkbd service, which doesn't know about the X session. It, though, has an history of being more compatible with different hardware, especially newer hardware[citation needed]

To install xbacklight globally, add this to your configuration.nix.

  environment.systemPackages = with pkgs; [ xorg.xbacklight ];

Alternatively, use nix-env -iA nixos.xorg.xbacklight to install it to your user profile.

light

light does not use X to change the light settings. This can be used in situations where the X service isn't available. While it does not use X, it will need some privileges to work.

To enable the use of light, add this to your configuration.nix and make sure that your user is a member of the video group.

  programs.light.enable = true;

The following commands will allow you to test light:

  • light -U 30 — the screen should become darker.
  • light -A 30 — the screen should become brighter.

Be careful using light -U, as you might turn your backlight completely off! You will not be able to see what you're typing anymore.

brightnessctl

brightnessctl (homepage) is another option, which, like light, would work even without X or on Wayland.

You can use it by simply installing the package. Since brightnessctl supports the systemd-logind API it should work out of the box (i.e. without installing any udev rules or using a setuid wrapper).

The following commands will allow you to test brightnessctl:

  • brightnessctl set 5%- - the screen should become darker.
  • brightnessctl set 5%+ - the screen should become brighter.

If you get an error like Failed to set brightness: Protocol error, check that you are using the right device. You can get a list of the devices with running brightnessctl -l and then specify the device with -d deviceName.

Example: brightnessctl set 5%- -d intel_backlight

/sys/class/backlight/...

The /sys/class/backlight/*/brightness files are a built-in way to set brightness. Use them e.g. with:

  sudo tee /sys/class/backlight/intel_backlight/brightness <<< 300

to set the brightness to 300, where the maximum is stored in brightness_max. You can set file permissions e.g. with a udev rule, if you don't want to use sudo. Here is an example udev rule, where you will likely have to replace intel_backlight, with the name in your /sys/class/backlight/:

  services.udev.extraRules = ''
    ACTION=="add", SUBSYSTEM=="backlight", KERNEL=="intel_backlight", MODE="0666", RUN+="${pkgs.coreutils}/bin/chmod a+w /sys/class/backlight/%k/brightness"
  '';

Tips

Key mapping

While controlling the backlight via the command line is useful, it would be preferable to control it using key bindings. This is especially true considering most laptops have backlight control keys.

There are two main choices to add key bindings, using a system-level service like actkbd or using an X session tool, either provided by your Desktop environment, Window manager or a tool like xbindkeys.

Depending on the tools that work for controlling the backlight you will be able to choose one of those options.

  light xbacklight
System service Yes With hacks
X session Yes Yes

Follows, an example mapping for use with actkbd:

Note: This was verified to work with
  • NixOS 18.03 on a Lenovo T440 and
  • NixOS 19.09pre173166.373488e6f4c on a Lenovo X240
it may work on other models, but is unconfirmed. See actkbd for details on finding out the proper key bindings. Also check if the path to the light binary is correct.
  programs.light.enable = true;
  services.actkbd = {
    enable = true;
    bindings = [
      { keys = [ 224 ]; events = [ "key" ]; command = "/run/current-system/sw/bin/light -A 10"; }
      { keys = [ 225 ]; events = [ "key" ]; command = "/run/current-system/sw/bin/light -U 10"; }
    ];
  };

OLED Screens

OLED screens do not have a backlight, but their perceived brightness can be changed via xrandr:

  • xrandr --output <output> --brightness .5 - dim to 50%
  • xrandr --output <output> --brightness 1 - no dimming

See also