I am a newbie at linux and I have installed Fedora 38 KDE on my laptop. It's turned out that backlight of my built-in keyboard is off although in Windows I can switch it on and off by Fn+F8. Of course I tried pressing Fn+F8). Also I opened Settings/Shortcuts and tried to assign Fn+F8 to something. And when I pressed the combination nothing happened as if Linux didn't hear this combination at all. When laptop starts the backlight is on and it switches off when GRUB menu appears. I tries to use OpenRGB but is says "One or more I2C/SMBus interfaces failed to initialize." Unfortunately, I don't know what I2C is and how it relates to keyboard backlight. lsusb shows:

Bus 003 Device 006: ID 1038:113a SteelSeries ApS SteelSeries KLC

**Update** I found the information that has helped me to solve the problem. But I don't understand how it works. I'll appreciate if you explain me)

My keyboard backlight function keys don't seem to work, so I've written a script to change the keyboard brightness, which must be run as root. It is invoked like so... sudo /usr/bin/local/backlight inc sudo /usr/bin/local/backlight dec This works fine from the terminal, but it doesn't work as the command of a custom keyboard shortcut I created via keyboard settings. Just guessing here, but might the issue be that the command, when invoked via the keyboard shortcut, is not actually running under my user, but as someone else, which wouldn't be in the sudoers file?

I’m a linux novice. I’ve recently install on a VM Fedora 39 Workstation. I have a CMStorm keyboard that lights up/off with the scroll lock key which doesn’t seem to work with the installation. My goal is to have the keyboard lights turn on, at least when I start the session. On Linux Mint it was relatively easy as I would simply add a startup command through the UI (“Session and Startup”) to run “xset led 3”. On Fedora I’ve been running the following command: sudo sh -c 'echo 1 > /sys/class/leds/input1::scrolllock/brightness' I’ve placed that command in a script in “/usr/bin”, which works when run in the terminal, and I’ve tried initially creating a systemd service to run at boot. When that didn’t work, I removed the service tried creating a user systemd service. My boot service was defined as: [Unit] Description=Service to activate keyboard lights. [Service] Type=oneshot ExecStart=/bin/bash /usr/bin/activate_keyboard_lights.sh [Install] WantedBy=multi-user.target My user service was defined as: [Unit] Description=Service to activate keyboard lights [Service] #Type=simple Type=oneshot RemainAfterExit=true ExecStart=/bin/bash /usr/bin/activate_keyboard_lights.sh [Install] WantedBy=default.target With the boot service nothing happened. On login with the user service, nothing happened and status logs show messages related to “bus not found” which detailed messages show that it’s probably related to permissions. I’m guessing because of the need to use sudo. I’ve also tried running both the script and the command as a keyboard short cut binded to F4, but nothing seems to happen. Any tips or ideas or should I try get used to manually running the script when I log in? Thanks.

I ever dislike the keyboards with lights, today after firmware update on my NS5x_NS7xPU the keyboard..become "with backlight". How to turn off? I have tried this command as root sh -c "echo 0 > /sys/class/leds/system76_acpi::kbd_backlight/max_brightness" sh: line 1: /sys/class/leds/system76_acpi::kbd_backlight/max_brightness: Permission denied When I press fn+f7 it appear a "monitor configuration" of Xfce4 When I run this command echo 0 > /sys/class/leds/system76_acpi\:\:kbd_backlight/brightness the keyboard backlight is still on,

I use arch linux and the reason I want this so bad is because my computer doesn't remember the backlight state and turns it on every boot and every time it wakes from deep sleep and I mostly don't need it. Referring to archwiki I tried both brightnessctl and xset but none of them seemed to detect it. my /sys/class/leds/ looks like

input3::capslock
input3::numlock
input3::scrolllock
phy0-led

there is neither a ::kbd_backlight nor a ::thinklight directory most solutions online are based on them

Is there a way to turn on the keyboard backlight from the multi-user.target environment? As X11 is not loaded, the command xset led on does not work and gives xset: unable to open display "". Currently, I am wanting the keyboard backlight to turn on each time the system starts (only if the keyboard is present). I would also like the keyboard backlight to turn on regardless the system loading in a graphical or non-graphical environment. Preferably, I would like this done through Cron.

I have a very simple generic gaming keyboard with a backlight. The, typically, universal way to engage the backlight is with xset led 3. I can confirm that this does in-fact work. Because I have two computers that I switch back and forth from with a peripheral switch, however, this becomes problematic because when I switch from one context to the other I'm unplugging and plugging the USB back in. I wrote a file /etc/udev/rules.d/keyboard.rules with the following rule: ATTRS{idVendor}=="258a", ATTRS{idProduct}=="0001", RUN+="/bin/bash -c \"DISPLAY=:1;xset led 3;\"" If I run /bin/bash -c \"DISPLAY=:1;xset led 3;\" by itself it works just fine, however, it doesn't seem to work as just a rule. It only sometimes turns on, and when it does it flashes on and then immediately turns back off. I have checked multiple times over and I know that my idVender and idProduct are correct: Bus 003 Device 079: ID 258a:0001 What else could I be missing?

I got a Logitech G413 SE keyboard. Its keys are lit when I plug it in; I want to turn that light off; but - there is no "lights off" switch on it! Damn them. Logitech has all sorts of software to do this on Windows. But - how can I turn off the lights on a Linux system? I'd prefer something that can work even from the command-line, but even a closed-source GUI utility is better than nothing... My distribution: Devuan GNU/Linux Daedalus.

I have on my hands an old 2011 Toshiba Qosmio X770 laptop, with CentOS Stream 8 and Windows 7 installed on it. The backlit keyboard works fine under Windows, but it remains dark under Linux. How can I turn on the keyboard backlight on Linux? Both CapsLock and NumLock leds work ok. The Fn+Z key (which commands the keyboard backlight) does nothing. The commands xset led on or xset led off doesn't seem to have any effect. Output of find /sys/devices -iname '*keyboard*' -or -iname '*kbd*' -or -iname '*backlight*': /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-eDP-1/nv_backlight1 /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-2/nv_backlight /sys/devices/pci0000:00/0000:00:02.0/backlight /sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight Content of /sys/class/leds/: lrwxrwxrwx 1 root root 0 Sep 1 21:39 ath9k-phy0 -> ../../devices/pci0000:00/0000:00:1c.1/0000:03:00.0/leds/ath9k-phy0 lrwxrwxrwx 1 root root 0 Sep 1 2022 input3::capslock -> ../../devices/platform/i8042/serio0/input/input3/input3::capslock lrwxrwxrwx 1 root root 0 Sep 1 2022 input3::numlock -> ../../devices/platform/i8042/serio0/input/input3/input3::numlock lrwxrwxrwx 1 root root 0 Sep 1 2022 input3::scrolllock -> ../../devices/platform/i8042/serio0/input/input3/input3::scrolllock lrwxrwxrwx 1 root root 0 Sep 1 21:39 mmc0:: -> ../../devices/pci0000:00/0000:00:1c.3/0000:05:00.0/leds/mmc0:: EDIT: Output of lsmod | grep acpi: snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg

[Here's the driver (it is called a "driver", isn't it?) for keyboard backlight](https://github.com/duncanthrax/roccat-vulcan) . I'm mostly interested in playing with the source code to understand something more about drivers, if possible. However, before diving into the code, I'd like to install it and see it working. That way I could really loop on "edit-reinstall-try" to see what effect my changes have. Well, I'm blocked at square 1, as I haven't been able to install the driver. To be honest, I haven't tried running sudo make install, and before doing so, I'd like to understand whether I truly need it and, if I do need it, understand why. I see that the [Makefile](https://github.com/duncanthrax/roccat-vulcan/blob/master/src/Makefile) has this install target:

install:
	mkdir -p ${DESTDIR}${BINDIR}
	cp $(NAME) ${DESTDIR}${BINDIR}/
	mkdir -p ${DESTDIR}${UDEVDIR}
	cp *.rules ${DESTDIR}${UDEVDIR}/

and a few lines above there's

BINDIR  := /usr/bin

so it's clear to me that sudo privileges are required because DESTDIR is not set, so ${DESTDIR}${BINDIR} resolves to /usr/bin, which needs sudo to be written to. However, if there's a ${DESTDIR} prefix in the first place, I wonder why I shouldn't run make install DESTDIR=$HOME or something. Indeed, I tried, but the executable, roccat-vulcan, when run, errors with Unable to find keyboard. Maybe it does need to be installed in /usr/bin? --- [A related question.](https://unix.stackexchange.com/questions/25715/why-do-some-packages-use-make-install-while-other-use-sudo-make-install) --- **Update** As suggested in the answer, I've tried installing with sudo make install BINDIR='/usr/local/bin', which succeed with the following **_output_**:

mkdir -p /usr/local/bin
cp roccat-vulcan /usr/local/bin/
mkdir -p /etc/udev/rules.d
cp *.rules /etc/udev/rules.d/

However, trying to run the software gives error. Below the output of roccat-vulcan -v:

ROCCAT Vulcan for Linux [github.com/duncanthrax/roccat-vulcan]
Effect Color Table (change these with -c option)
colorIdx    R      G      B  Desc
------------------------------------------------
0           0      0    119  Base keyboard color (dark blue)
1        2303      0   -255  Typing color, initial key (over-red, under-blue)
2        2303      0   -143  Typing color, first neighbor key
3        2303      0      0  Typing color, second neighbor key
4         187      0    204  Ghost typing color, initial key
5         153      0    187  Ghost typing color, first neighbor key
6          85      0    170  Ghost typing color, second neighbor key
7           0      0      0  (null)
8           0      0      0  (null)
9           0      0      0  (null)
open_device(1e7d, 3098): No LED device found
open_device(1e7d, 307a): ignoring non-LED interface #0
open_device(1e7d, 307a): ignoring non-LED interface #1
open_device(1e7d, 307a): ignoring non-LED interface #2
open_device(1e7d, 307a): LED interface at USB path 1-3:1.3
open_device(1e7d, 307a): Unable to open LED interface 1-3:1.3
Error: Unable to find keyboard

After installing Awesome (with no other GUI environments), the function keys on my laptop (for brightness especially), don't work like they do when I install KDE or GNOME. So far, the only method I've found to control brightness is commands like this: echo "10" > /sys/class/backlight/nv_backlight/brightness echo "20" > /sys/class/backlight/nv_backlight/brightness echo "30" > /sys/class/backlight/nv_backlight/brightness echo "40" > /sys/class/backlight/nv_backlight/brightness echo "50" > /sys/class/backlight/nv_backlight/brightness echo "60" > /sys/class/backlight/nv_backlight/brightness echo "70" > /sys/class/backlight/nv_backlight/brightness echo "80" > /sys/class/backlight/nv_backlight/brightness echo "90" > /sys/class/backlight/nv_backlight/brightness echo "100" > /sys/class/backlight/nv_backlight/brightness However, I cannot easily automate these commands to hot-keys because they only work as root. Surprisingly, sudo doesn't even work when using my regular user account. For example, this doesn't work: sudo echo "60" > /sys/class/backlight/nv_backlight/brightness The above command outputs: Permission denied. So, as is, to change brightness I have to su first. Perhaps someone can explain how I can permit my regular user account to modify that path without escalation. Then, I'd be able to tie hotkeys to these brightness adjustments. Ideally, though, I suspect that there is a package I can install that would map my laptop's existing keys for brightness adjustment. Here's the model (if that helps you know the package): Machine: Type: Laptop System: System76 product: Bonobo WS v: bonw13 Mobo: System76 model: Bonobo WS v: bonw13

I developed and maintain a keyboard backlight CLI/GUI for Linux-running Clevo laptops (https://github.com/webketje/tuxedo-backlight-control) . Some of the files this CLI/GUI needs to alter are under /sys/devices/platform/tuxedo_keyboard/. At the moment I am using polkit/pkexec to prompt for temporary admin permissions. However, someone created a fork of my repo and added a commit which activates a Linux service that makes the files under the /sys/devices/platform/tuxedo_keyboard/ directory writable for all (https://github.com/encarsia/tuxedo-backlight-control/commit/34da8989613c29c0faab67220a4391c460d2aa6a) . Obviously I would love to not have to prompt for the admin password every 5min just to change the keyboard backlight color, but I am wondering **security-wise, is this ok**? If so, how can I make sure after a new tuxedo_keyboard driver install, that the files remain writable?

I'm having an annoying issue with my PC, the keyboard and mouse stay on after shutdown and this is odd because does not happen when I use Windows or put the computer to hibernate. It's completely annoying because every time I have to unplug both devices, since the keyboard have a bright backlight and the computer desk is in my bedroom. To be more detailed: I'm also using a KVM switch to use the same keyboard and mouse on two computers and even when I remove the second's computer USB from the KVM switch, in which power is provided, the issue persists. My OS is Xubuntu 20.04 by the way.

Question ------------ How to ensure keyboard backlight is on (at max) at boot time on a Dell laptop? Rationale ---------- I sometimes hit the combination of keys which turns off the keyboard backlight at day time not noticing it, and then when I wake up, in the middle of the night usually, I don't want to wake up my wife by turning the lights on. Hence, I seek a solution, which would read the maximum possible value of the backlight and setting it no matter what when I boot my computer up. I always turn it off at night so the solution does not have to account for the sleep or hibernate modes. Research --------- The maximum value of keyboard backlight is stored in: /sys/class/leds/dell\:\:kbd_backlight/max_brightness And the actual value of currently set value is stored in: /sys/class/leds/dell\:\:kbd_backlight/brightness

How can I turn increase and decrease the keyboard backlight in notebook on Linux using the same hotkeys used on Windows? In Windows I can control the keyboard backlight by pressing hotkeys (FnF9 to decrease and FnF10 to increase), but in Linux it doesn't seems to have these hotkeys implemented as the keyboard backlight is a new and not most spread feature for the notebooks/ultrabooks. Note: The Fn is working for normal features like display brightness and sound, just for controlling the keyboard backlight it is not configured correctly... But it works in the Linux, as I can turn it on in the Grub2 boot device selector, but not in the running Linux OS. Just some extra-specs: OS : Linux (Mint Cinnamon 17). Notebook: Samsung Ativ Book 6.

I am using a new laptop, Asus ROG Strix, G531GT-AL041T, G Core i7 9th Gen, and running Linux Mint 19.2 Tina on it. I am unable to find any option that could disable the keyboard lights and in particular the underglow lights which make the laptop look unaesthetic in day light. Moreover, I do not wish to waste the battery power in something that is totally unnecessary. Is there a way to fix this issue?

I just bought Redgear Grimm backlight external keyboard to work with linux mint 18.3. The backlight didn't work initially and after some poking around I found /sys/class/leds/ and I am able to turn on the backlight with the following command echo 1 | sudo tee /sys/class/leds/input25::scrolllock/brightness Now here's the problems 1. Pressing Caps Lock key and Num Lock key disables the backlight which should not happen 2. After that the backlight doesn't work even when pressing the Num Lock, Caps Lock and Scroll Lock key(which btw should be the actual key for this function.) The keyboard is fine. Proved by testing it on a Windows laptop.

I am new to this forum and Kali as well. I have a Macbook 13 inch 2015 model, and recently I installed Kali in it. I was able to configure broadcom drivers but even after googling a lot, I don't see any progress with my touchpad. I tried using the inbuilt utility but that dosent seem to work as well. Here is a screen shot. I've also tired using synclient -i. But it shows bash: synclient: Command not found

For my [i3 window-manager](https://i3wm.org/) settings, I am looking for a command line tool, similar to xbacklight, but to control the brightness of the leds which are in the keyboard. Basically, I can set up the leds through a command line, but it requires to be root: # Light off the leds echo 0 > /sys/class/leds/smc::kbd_backlight/brightness # Light on the leds (full power) echo 100 > /sys/class/leds/smc::kbd_backlight/brightness I know that it is possible because Gnome3 has support for that, but I do not know exactly how they proceed... For now, my ~/.config/i3/config looks like this: # screen brightness controls bindsym XF86MonBrightnessUp exec xbacklight -inc 10 bindsym XF86MonBrightnessDown exec xbacklight -dec 10 # keyboard backlight controls #TODO # XF86KbdBrightnessUp # XF86KbdBrightnessDown So, is there a tool, similar to xbacklight to do the same than screen brightness with keyboard backlight? It would be even better if this tool would have the control on both (screen and keyboard).

I have an Asus VivoBook S510U running Debian buster/sid with GNOME 3.28.2 and still using XORG. A couple of months ago I was able to use the function keys to change keyboard backlight and I was also able to change that setting with a slider on the power screen. Now I don't see the slider anymore and the function keys show the OSD of the keyboard backlight but they don't change anything. Can't remember the exact update that caused this. I'm able to change the brightness using this command: echo 2 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness Echoing from 0 to 3 to get different brightness. I understand that I can make this into a script and set a hotkey to it, but I'd like to get the previous behaviour working that also showed the slider. Any hint on how to do that?