So I've encountered this problem every time I installed linux on my laptop. I've asked it before here , but that didn't go well. Now I'v installed Pop OS (22.04) and I'm fully committed to it, it's not dual boot anymore and it's the only OS I currently run. I did try gaming on it and works just fine, I actually have no problem right now with it, except the brightness of course xd The situation: Brightness of the screen is stuck at maximum (I think, it's really bright), the actual_brightness file has 100 in it, the brightness slider changes the brightness file (both files on /sys/class/backlight/nvidia_0).
I CAN change the brightness using xrandr --output DP-2 --brightness 0.5 for example, but it won't stay that way and none of the files I mentioned change when I use xrandr.
Also, the keyboard backlight works just fine, I didn't install any RGB related software and it has the default red color but the brightness level is working perfect. Changing the brightness of the keyboard backlight will return the display brightness to maximum, if I've used xrandr before and changed it. What I have done: I did dual boot Pop OS before wiping windows from the laptop, and in dual boot mode, I've changed the permissions of brightness and actual_brightness files (chmod 777), and also tried to manually write numbers in them but it didn't work (Used nano and vim for it, in sudo mode). I've searched for solutions but couldn't find working ones. There were somethings about older versions of nvidia drivers solving these problems, but: 1. I need up to date drivers, because I game on it and can't keep an outdated driver for gaming. Basically everything I need to install (steam, wine, lutris) will update the drivers or need up to date drivers. 2. This problem is not new, I had it every single time I've installed linux on this laptop (multiple times Ubuntu, I think I did manjaro one time and probably Pop OS before), and I think it's something related to how my hardware interacts with linux or something. My specs: ASUS ROG GL503VS, Intel Corei7-7700HQ, Nvidia Geforce GTX 1070 (The only GPU on my laptop, and it is dedicated of course), 1920x1080 144hz GeSync capable display (I don't know if it helps at all).
Software: Pop OS 22.04, nvidia-smi output:

$ nvidia-smi
Mon Nov 20 16:50:39 2023       
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.02              Driver Version: 545.29.02    CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1070        Off | 00000000:01:00.0  On |                  N/A |
| N/A   60C    P0              35W / 115W |    380MiB /  8192MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
                                                                                         
+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      2130      G   /usr/lib/xorg/Xorg                          139MiB |
|    0   N/A  N/A      2234      G   /usr/bin/gnome-shell                         57MiB |
|    0   N/A  N/A      5027      G   ...RunOnOsLogin,WebAssemblyTrapHandler       88MiB |
|    0   N/A  N/A      5593      G   ...,WinRetrieveSuggestionsOnlyOnDemand       90MiB |
+---------------------------------------------------------------------------------------+

And uname -r output:

$ uname -r
6.5.6-76060506-generic

If any other information is needed, I can happily give it to you. I'm quite new to linux (despite many tries) and know a thing or two but not much at all. I really want to use it as my main OS, but I think I'm gonna lose my eyes in the process if I can't solve this problem XD. Many thanks in advance.

It looks like a pinpoint of light shining through any opened window, always at the same place (it doesn't move if I move the window). It looks like a screen-related hardware problem, only I don't think it's a hardware problem because if no window is opened it doesn't show. I can change the background picture, it doesn't show. Any opened window covering this place, whatever the program, it shows. An opened window not covering this place, it doesn't show. It doesn't appear on screenshots. The only fix I can think off would be to reinstall Lubuntu, but this seems like overkill for a small problem like that. Plus, I don't just want it to simply go away, I'm curious about what could possibly cause this?

I installed ArchLinux on my Lenovo Legion Y720 laptop and I can't turn on Keyboard lights and Extreme Cooling as I could in Windows 10 using Lenovo NerveSense app. How can I access these on Linux? Is it even possible? I've searched everywhere and I couldn't find anything. Should I try coding a driver? Any literature on that? Thank you! Output of ls /sys/class/leds/*/brightness: /sys/class/leds/input0::capslock/brightness /sys/class/leds/input0::numlock/brightness /sys/class/leds/input0::scrolllock/brightness /sys/class/leds/input17::capslock/brightness /sys/class/leds/input17::compose/brightness /sys/class/leds/input17::kana/brightness /sys/class/leds/input17::numlock/brightness /sys/class/leds/input17::scrolllock/brightness /sys/class/leds/input2::capslock/brightness /sys/class/leds/input2::compose/brightness /sys/class/leds/input2::kana/brightness /sys/class/leds/input2::numlock/brightness /sys/class/leds/input2::scrolllock/brightness /sys/class/leds/input5::capslock/brightness /sys/class/leds/input5::numlock/brightness /sys/class/leds/input5::scrolllock/brightness /sys/class/leds/phy0-led/brightness`

I would like to make a Debian 12 Live system for a laptop, from another computer that has an external display without backlight settings in the operating system. I need to know the file where is stored the backlight brightness settings, to copy it in the Live system, so that the backlight will be already adjusted when I will boot the live system. The live system will use MATE desktop environment, a fork of GNOME. I wonder if the backlight configuration is part of gsettings ? And so, which file I will have to copy, once the backlight brightness adjusted ?

How can a user change the scale attribute of a backlight that is exposed in sysfs? On my machine it's located at /sys/class/backlight/amdgpu_bl1/scale. I tried using udev to add write permissions to the file and write to it, but that doesn't change it from unknown. Running udevadm test /sys/class/backlight/amdgpu_bl1 returns:

amdgpu_bl1: /etc/udev/rules.d/90-backlight-scale.rules:5 RUN '/bin/chmod a+w /sys/class/backlight/amdgpu_bl1/scale'
amdgpu_bl1: /etc/udev/rules.d/91-backlight-scale.rules:5 RUN '/bin/echo non-linear > /sys/class/backlight/amdgpu_bl1/scale'
amdgpu_bl1: /usr/lib/udev/rules.d/99-systemd.rules:74 Skipping builtin 'path_id' in IMPORT key
amdgpu_bl1: Failed to update tags under /run/udev/tag/: Permission denied

After running the udev scripts, the file properties are

-rw-rw-rw-. 1 root root 4096 Mar 21 08:08 scale

Trying to write to it with echo non-linear | sudo tee /sys/class/backlight/amdgpu_bl1/scale yields

tee: /sys/class/backlight/amdgpu_bl1/scale: Input/output error

Is modifying /sys/class/backlight/amdgpu_bl1/scale at all possible?

Being aware of that this is partially a known issue, since each is individual and different, the problem is as following: On my Lenovo Laptop with Linux Mint the backlight cannot be set using Fn+F6/F7. These keys are not detected at all, neither by xev nor by acpi_listen. However other key combinations like Fn+F3 for volume up is detected by both commands. So it is a more low-level issue, I am afraid. On the other hand, this works well: - echo 10000 | sudo tee /sys/class/backlight/intel_backlight/brightness and as well - with the GUI slider in mate-power-preferences works perfectly. - xdotool key 232 or xdotool key XF86MonBrightnessDown More detailed: - I tried many boot combinations (yes I updated GRUB and did reboot, as described in this troubleshooting wiki.ubuntu.com Debugging/Backlight ) - I tried adding files in /usr/share/X11/xorg.conf.d/ as recommended (80-backlight.conf using both "Backlight" "ideapad" and "intel_backlight", or 20-intel.conf) uname -a yields: Linux Lenovo-V14-G2-ITL 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux These are the available backlights (which can be written using cat) $ ls /sys/class/backlight/ ideapad intel_backlight This is my current configuration $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=/dev/mapper/vgmint-root ro pcie_aspm=force acpi_osi=Linux acpi_backlight=vendor quiet splash I tried these (as well individually and with many combinations, only visible effect is that the output of ls /sys/class/backlight/ is changing) GRUB_CMDLINE_LINUX="pcie_aspm=force acpi_osi=linux acpi_backlight=vendor video.use_native_backlight=1"

I'm trying to enable some multimedia keys, and the ones for volume do work. F5 and F6, the ones for increasing/decreasing do not work, I do not know why. When I run in the terminal: xbacklight +10 I can see the working effect. When I try my binded special keys (which are set to ~/.config/i3/config): # Sreen brightness controls bindsym XF86MonBrightnessUp exec xbacklight -inc 20 # increase screen brightness bindsym XF86MonBrightnessDown exec xbacklight -dec 20 # decrease screen brightness Obviously, the media keys must be combined with the fn key. However, I don't see the effect. Any solutions?

I am running Qubes OS based on Fedora 36, and using i3wm. I am working on creating an i3 block similar to this contributed blocklet , but without using xbacklight. Why not xbacklight? My laptop has brightness increase and decrease fn keys (i.e., XF86MonBrightnessUp and XF86MonBrightnessDown) which work! I do not have xbacklight installed, and I do not want to install additional packages, because clearly my brightness controls work. 1) What I want to do is determine what command my XF86MonBrightnessUp and XF86MonBrightnessDown keys are sending (such that I could run it from terminal)? Using that, I will update my i3blocks script. I've tried using xev, but it does not seem to give me very useful info. 2) Would also be great if there is a way to determine current brightness level (again, without additional packages). Ideally, I want to control the brightness in a way that is most battery efficient, and I assume that's what XF86MonBrightnessUp and XF86MonBrightnessDown do already by default, and while not necessarily so with other packages.

I have a script which corrects my screen brightness based on an ambient light sensor. I want it to stop changing my screen brightness when my screen dims as a result of user inactivity. How can I subscribe to a screen dim event?

I get my new-but-old Razer keyboard (Blackwidow Ultimate 2016) out of the box. (old Kubuntu, can't update or install stuff) And keyboard works, but the back-light annoyingly goes on and off every few seconds. I have no windows box to try and set it up. Any suggestions? And even if I do, will the setup hold or needs to be done on every reboot? Thanks, Joseph

My problem is as follows: I use a Steelseries Apex M800 keyboard, which means it has proprietary RGB software for the keyboard backlight (I chose my keyboard before I switched to Linux, so I am aware of the quality of this choice :( ). Now about 50% of the time the backlight doesn't work on boot and the only way to fix it is to manually pull out the USB plug and reconnect it again. I am looking for a way to virtually accomplish the same thing so I wouldn't have to crawl under my desk every morning just so I could see my keys. I'm trying to find a sort of "hard reseating the USB cable" script. I tried several scripts I found across the web, including [this](https://github.com/netinvent/usb_resetter/blob/main/usb_reset.py) , [this](https://github.com/mcarans/resetusb/blob/master/reset_usb.py) and [this](https://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line) . I'm pretty sure they are all trying to do very similar things and it doesn't seem to work. Anybody got an idea what command and/or script I could still try out to completely disconnect and reconnect my keyboard, similar to pulling the plug out and putting it back in again? I use Manjaro with a 5.15 kernel in case that is relevant.

I have a Lenovo IdeaPad 3 17ABA7 with a fresh Debian Bullseye installation. Unfortunately the screen brightness control doesn't work out of the box. lspci lists the following video device:

04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c2) (prog-if 00 [VGA controller])

I've already found various suggestions on the Internet, including boot options like acpi_backlight=vendor acpi_osi=Linux or amdgpu.backlight=0. None of those worked. How do I get the brightness control keys to work?

How does one flip a monitor's backlight on/off from the normal Linux console (tty1)? I'm looking for a way to do this without dependencies on Xorg or specific Wayland-Compositors. Let's say, that I want to toggle the backlight of the monitor connected to

/sys/class/drm/card0-HDMI-A-1

. EDIT: Putting a specific monitor into standby mode from tty1 would suffice as an answer.

seems to work, but there doesn't seem to be a way that affects just one specific monitor instead of all of them.

setvcp D6 x05

let me turn off one of my monitors. Again, how does one select which one with these tools?

I have Manjaro installed in dual boot on a Dell XPS 9360 with FHD screen non touchscreen. The key combo to increase/decrease the screen brightness are Fn+F11 and Fn+F12. This works perfectly on Windows 11 and Ubuntu but not on Manjaro So far I can adjust the brightness from the slider in the notification area of the top bar (I'm using Gnome with Wayland, same as ubuntu where Fn key combo it works perfectly also for brightness; on X I have the same problem so it's not some wayland related issue) and adjust it through /sys/class/backlight/intel_backlight/brightness I can also change the brightness through xbacklight, but still not with Fn key combo Looks like that the Fn+F key combo is not detected at all, like it's not registered anywhere - in xev the pushing of Fn+F11 or F12 isn't even detected - acpi_listen reports 9 DBB5994-A997- 000000d0 00000000 for both Fn+F11 and Fn+F12; at least it detects something but I know it's not the right thing as if I push Fn+F3 (to increase the spearkers volume) it gives button/volumeup VOLUP 00000080 00000000 K meaning that it somehow associates that key combo to a specific event/action. 9 DBB5994-A997- 000000d0 00000000 is the same result if I push Fn+F10 which is the combo to adjust keyboard brightness, but this works flawlessly I've also tried the following, without any success - add acpi_backlight=none, acpi_backlight=vendor, acpi_backlight=video and acpi_backlight=native to /etc/default/grub in the section GRUB_CMDLINE_LINUX_DEFAULT - add acpi_osi= and acpi_osi=Linux alone and in combination with one of the previous keys to GRUB_CMDLINE_LINUX_DEFAULT; to be honest I've not tried all the combinations (as suggested [here](https://askubuntu.com/questions/142017/brightness-keys-f4-and-f5-not-working-on-dell-xps-15-6-laptop) for example), so you tell me if it's the case - configure /usr/share/X11/xorg.conf.d/20-intel.conf as auggested [here](https://www.reddit.com/r/archlinux/comments/clj91c/brightness_buttons_stopped_working_dell_xps_15/) but nothing Thank you for your help

The brightness (LCD backlight) controls on a Lenovo IdeaPad Gaming 3 (15ARH05, LCD display, AMD Renoir CPU Ryzen 5 4600H, discrete NVIDIA GeForce 1650 Ti Mobile) are not working: - Fn keys show the brightness slider on the display moving. - /sys/class/backlight/amdgpu_bl0/brightness changes accordingly from 0 to 255. - The display does not show any brightness change. - Manually writing to brightness does not change the display's brightness either. - /sys/class/backlight/amdgpu_bl0/actual_brightness stays at **311**. *I figure **this** indicates a problem with the amdgpu driver.* - The display seems to stay at full brightness always. Adjustments work fine on Windows 10. The laptop is running: - Kali Linux Rolling - linux-image-5.8.0-kali-amd64 (based on 5.8.14) and custom-built kernels 5.9, 5.9.1 and 5.10-rc1, mostly based off the Kali config - X with amdgpu drivers, discrete graphics unused (proprietary NVIDIA drivers loaded and unloaded for testing). I have tried booting with various acpi_backlight kernel options, which lead to various backlights being available in /sys/class/backlight/*/brightness: - acpi_backlight=video: acpi_video0 acpi_video1 amdgpu_bl0 - acpi_backlight=vendor: amdgpu_bl0 ideapad - acpi_backlight=native: amdgpu_bl0 - acpi_backlight=none: amdgpu_bl0 Other things that did not work: - acpi_osi=Linux (no change) - acpi_osi= (hangs at boot) - BIOS update (no other version available) - moving /lib/firmware/amdgpu/renoir_dmcu.bin away - patching [amdgpu_dm.c](https://github.com/Aonnghus/renoir-brightness/blob/master/brightness.patch) I am aware that there has been a number of updates related to backlights for AMDGPUs, like general support and fixes in kernel 5.7.x and updates to the scaling of brightness values >255 in 5.9, but so far this seems not to have helped my case (or possibly, broke more things). I am not looking for: - software alternatives - adjusting the gamma values - using discrete graphics (if it can be avoided) **What else can I do or look into to gain control of the backlight?** I came across [this comment](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861925/comments/27) and [this bug report](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899626) , which seem to suggest that some kernel fixes may have broken other things. **What would be the best place to report that?**

After installing AlmaLinux on a Toshiba Portege laptop and choosing the workstation setup, the brightness control keys do not work. The hardware is capable and Linux compatible, as evidenced by the fact that a dual boot of Linux Mint has no issue with this.

I am running FreeBSD 11RC2 with The current Nvidia-driver version 367.44 and using the nvidia-modeset kernel module that's loaded at startup in my /etc/rc.conf file by adding kld_list="nvidia-modeset" Here's the info on my GPU vgapci0@pci0:1:0:0: class=0x030000 card=0x0130106b chip=0x0fe910de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GK107M [GeForce GT 750M Mac Edition]' class = display subclass = VGA cap 01 = powerspec 3 supports D0 D3 current D0 cap 05 = MSI supports 1 message, 64 bit enabled with 1 message cap 10 = PCI-Express 2 endpoint max data 256(256) RO NS link x8(x16) speed 8.0(8.0) ASPM L0s/L1(L0s/L1) cap 09[b4] = vendor (length 20) ecap 0002 = VC 1 max VC0 ecap 0004 = Power Budgeting 1 ecap 0001 = AER 2 0 fatal 0 non-fatal 0 corrected ecap 000b = Vendor 1 ID 1 ecap 0019 = PCIe Sec 1 lane errors 0 Here is the acpi information for this machine : http://paste2.org/LUcIwtzn device acpi debug.acpi.resume_beep: 0 debug.acpi.batt.batt_sleep_ms: 0 debug.acpi.ec.timeout: 750 debug.acpi.ec.polled: 0 debug.acpi.ec.burst: 0 debug.acpi.cpu_unordered: 0 debug.acpi.suspend_bounce: 0 debug.acpi.reset_clock: 1 debug.acpi.default_register_width: 1 debug.acpi.interpreter_slack: 1 debug.acpi.enable_debug_objects: 0 debug.acpi.acpi_ca_version: 20160527 debug.acpi.max_threads: 3 debug.acpi.tasks_hiwater: 40 debug.acpi.max_tasks: 1024 hw.acpi.acline: 1 hw.acpi.battery.info_expire: 5 hw.acpi.battery.units: 1 hw.acpi.battery.state: 0 hw.acpi.battery.time: -1 hw.acpi.battery.life: 97 hw.acpi.cpu.cx_lowest: C2 hw.acpi.reset_video: 0 hw.acpi.handle_reboot: 1 hw.acpi.disable_on_reboot: 0 hw.acpi.verbose: 0 hw.acpi.s4bios: 0 hw.acpi.sleep_delay: 1 hw.acpi.suspend_state: S3 hw.acpi.standby_state: NONE hw.acpi.lid_switch_state: NONE hw.acpi.sleep_button_state: S3 hw.acpi.power_button_state: S5 hw.acpi.supported_sleep_state: S3 S4 S5 machdep.idle: acpi machdep.idle_available: spin, mwait, hlt, acpi machdep.acpi_root: 2061033492 machdep.acpi_timer_freq: 3579545 dev.acpi_perf.7.%parent: cpu7 dev.acpi_perf.7.%pnpinfo: dev.acpi_perf.7.%location: dev.acpi_perf.7.%driver: acpi_perf dev.acpi_perf.7.%desc: dev.acpi_perf.6.%parent: cpu6 dev.acpi_perf.6.%pnpinfo: dev.acpi_perf.6.%location: dev.acpi_perf.6.%driver: acpi_perf dev.acpi_perf.6.%desc: dev.acpi_perf.5.%parent: cpu5 dev.acpi_perf.5.%pnpinfo: dev.acpi_perf.5.%location: dev.acpi_perf.5.%driver: acpi_perf dev.acpi_perf.5.%desc: dev.acpi_perf.4.%parent: cpu4 dev.acpi_perf.4.%pnpinfo: dev.acpi_perf.4.%location: dev.acpi_perf.4.%driver: acpi_perf dev.acpi_perf.4.%desc: dev.acpi_perf.3.%parent: cpu3 dev.acpi_perf.3.%pnpinfo: dev.acpi_perf.3.%location: dev.acpi_perf.3.%driver: acpi_perf dev.acpi_perf.3.%desc: dev.acpi_perf.2.%parent: cpu2 dev.acpi_perf.2.%pnpinfo: dev.acpi_perf.2.%location: dev.acpi_perf.2.%driver: acpi_perf dev.acpi_perf.2.%desc: dev.acpi_perf.1.%parent: cpu1 dev.acpi_perf.1.%pnpinfo: dev.acpi_perf.1.%location: dev.acpi_perf.1.%driver: acpi_perf dev.acpi_perf.1.%desc: dev.acpi_perf.0.%parent: cpu0 dev.acpi_perf.0.%pnpinfo: dev.acpi_perf.0.%location: dev.acpi_perf.0.%driver: acpi_perf dev.acpi_perf.0.%desc: dev.acpi_perf.%parent: dev.fpupnp.0.%parent: acpi0 dev.atdma.0.%parent: acpi0 dev.acpi_button.1.%parent: acpi0 dev.acpi_button.1.%pnpinfo: _HID=PNP0C0E _UID=0 dev.acpi_button.1.%location: handle=\_SB_.SLPB dev.acpi_button.1.%driver: acpi_button dev.acpi_button.1.%desc: Sleep Button dev.acpi_button.0.%parent: acpi0 dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=0 dev.acpi_button.0.%location: handle=\_SB_.PWRB dev.acpi_button.0.%driver: acpi_button dev.acpi_button.0.%desc: Power Button dev.acpi_button.%parent: dev.acpi_lid.0.wake: 1 dev.acpi_lid.0.%parent: acpi0 dev.acpi_lid.0.%pnpinfo: _HID=PNP0C0D _UID=0 dev.acpi_lid.0.%location: handle=\_SB_.LID0 dev.acpi_lid.0.%driver: acpi_lid dev.acpi_lid.0.%desc: Control Method Lid Switch dev.acpi_lid.%parent: dev.acpi_acad.0.wake: 0 dev.acpi_acad.0.%parent: acpi0 dev.acpi_acad.0.%pnpinfo: _HID=ACPI0003 _UID=0 dev.acpi_acad.0.%location: handle=\_SB_.ADP1 dev.acpi_acad.0.%driver: acpi_acad dev.acpi_acad.0.%desc: AC Adapter dev.acpi_acad.%parent: dev.battery.0.%parent: acpi0 dev.pcib.0.%parent: acpi0 dev.pci_link.7.%parent: acpi0 dev.pci_link.6.%parent: acpi0 dev.pci_link.5.%parent: acpi0 dev.pci_link.4.%parent: acpi0 dev.pci_link.3.%parent: acpi0 dev.pci_link.2.%parent: acpi0 dev.pci_link.1.%parent: acpi0 dev.pci_link.0.%parent: acpi0 dev.acpi_timer.0.%parent: acpi0 dev.acpi_timer.0.%pnpinfo: unknown dev.acpi_timer.0.%location: unknown dev.acpi_timer.0.%driver: acpi_timer dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz dev.acpi_timer.%parent: dev.attimer.0.%parent: acpi0 dev.atrtc.0.%parent: acpi0 dev.cpu.7.%parent: acpi0 dev.cpu.6.%parent: acpi0 dev.cpu.5.%parent: acpi0 dev.cpu.4.%parent: acpi0 dev.cpu.3.%parent: acpi0 dev.cpu.2.%parent: acpi0 dev.cpu.1.%parent: acpi0 dev.cpu.0.%parent: acpi0 dev.acpi_sysresource.2.%parent: acpi0 dev.acpi_sysresource.2.%pnpinfo: _HID=PNP0C01 _UID=2 dev.acpi_sysresource.2.%location: handle=\_SB_.MEM2 dev.acpi_sysresource.2.%driver: acpi_sysresource dev.acpi_sysresource.2.%desc: System Resource dev.acpi_sysresource.1.%parent: acpi0 dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=1 dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.PDRC dev.acpi_sysresource.1.%driver: acpi_sysresource dev.acpi_sysresource.1.%desc: System Resource dev.acpi_sysresource.0.%parent: acpi0 dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C02 _UID=2 dev.acpi_sysresource.0.%location: handle=\_SB_.PCI0.LPCB.LDRC dev.acpi_sysresource.0.%driver: acpi_sysresource dev.acpi_sysresource.0.%desc: System Resource dev.acpi_sysresource.%parent: dev.hpet.0.%parent: acpi0 dev.acpi_ec.0.wake: 0 dev.acpi_ec.0.%parent: acpi0 dev.acpi_ec.0.%pnpinfo: _HID=PNP0C09 _UID=0 dev.acpi_ec.0.%location: handle=\_SB_.PCI0.LPCB.EC__ dev.acpi_ec.0.%driver: acpi_ec dev.acpi_ec.0.%desc: Embedded Controller: GPE 0x17, ECDT dev.acpi_ec.%parent: dev.acpi.0.%parent: nexus0 dev.acpi.0.%pnpinfo: dev.acpi.0.%location: dev.acpi.0.%driver: acpi dev.acpi.0.%desc: APPLE Apple00 dev.acpi.%parent: I came from running linux and typically there's a video or some acpi settings that will control the brightness of the screen but on FreeBSD, there doesn't seem to be anything like this so my monitor is constantly at 100% brightness. Shouldn't there be some way to dim the brightness through the acpi interface? Can I get some support to be able to dim the screen brightness? [edit] Here is the output of my xorg.conf # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 367.35 Wed Sep 7 17:03:49 CST 2016 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "keyboard" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection

I don't see any events when I run xev and press either the brightness up or down keys. I have configured i3wm to handle the XF86MonBrightnessDown and XF86MonBrightnessUp, but they won't get triggered because they are never published. Using the brillo command to change the brightness from the command-line works great as a workaround, but it is really nice to be able to use the keys instead. I'm running Arch Linux with kernel version 5.14.12-arch1-1.

My PC is running Manjaro. Unfortunately since recently my PC is restarted by itself and is then displayed to me that.

[FAILED] Failed to start load/save screen backlight brightness of backlight:acpi_video0

Can someone please explain to me what this is and how I can fix it?

I would like for example when editing in VI, that my RGB keyboard would highlight shortcut keys in different colors, or when I press CTRL in gnome then pgup, pgdown, up, down, would be highlighted in red color, alt and shift green color, etc. The color of keys would depend on the current context. Is there any such project going on? Is it even possible to accomplish? Thanks.