New answers tagged

0

I fixed this by installing acpid (sudo apt-get install acpid). I then created 2 files: /etc/acpi/events/asus-brightness: event=hotkey ASUS010:00 0000002[0-9a-f] action=/etc/acpi/brightness.sh %e /etc/acpi/brightness.sh: #!/bin/bash test -f /usr/share/acpi-support/key-constants || exit 0 export DISPLAY=:0 PREV=$(cat /etc/acpi/prevbrightness) if [[ "0x$...


2

I use SUSE (SLES) linux and have encountered a similiar problem. In my case it has to do with /etc/X11/xorg.conf which is where the graphics drivers start... this file then points to the rest of what's needed for graphics whether it's an nvidia graphics card on a pcie slot or onboard graphics on the motherboard/cpu. I have found that when using a nvidia ...


2

1) Yes, it is completely safe. Echoing into /sys (or /proc) does not overwrite kernel configuration directly, it runs a kernel userspace function which do validate the input. xrandr/xbacklight actually performs pretty much that (as far as I know). 2) Since it worked before I bet that xbacklight is simply finding the wrong backlight directory in /sys/...


0

Your script doesn't set the DISPLAY environment variable. It should look like this: #!/bin/sh export DISPLAY=:0 xrandr --output LVDS-1 --auto --output DP-5.8 --off



Top 50 recent answers are included