View previous topic :: View next topic |
Author |
Message |
RayDude Advocate
Joined: 29 May 2004 Posts: 2051 Location: San Jose, CA
|
Posted: Sun Oct 09, 2016 3:31 pm Post subject: Can't control screen brightness on ASUS ROG laptop |
|
|
I had a lot of stuff misconfigured in the kernel, but I'm pretty sure I took care of all that.
The buttons to control the keyboard backlight work perfectly,
But I can't change the screen brightness with the keyboard FN keys and if I echo "5" > /sys/class/backlight/asus-nb-wmi/brightness the value changes but the screen brightness does not.
I used acpi_listen and can see the screen brightness keyboard event.
I think all the modules are installed and working:
Code: | lsmod | grep asus
asus_nb_wmi 11792 0
asus_wmi 14531 1 asus_nb_wmi
sparse_keymap 2706 1 asus_wmi
hwmon 2866 2 coretemp,asus_wmi
led_class 3655 3 iwlmvm,input_leds,asus_wmi
wmi 6882 1 asus_wmi
video 25740 1 asus_wmi
backlight 5552 2 video,asus_wmi
asus_wireless 1910 0
|
Can anyone think of something else I can check? Not being able to dim is blinding me at night.
Also, I would love to disable the touch pad. It keeps moving the pointer when I'm typing. _________________ Some day there will only be free software. |
|
Back to top |
|
|
mrbassie l33t
Joined: 31 May 2013 Posts: 771 Location: over here
|
Posted: Sun Oct 09, 2016 3:51 pm Post subject: Re: Can't control screen brightness on ASUS ROG laptop |
|
|
If you're using grub try adding Code: | acpi_backlight=vendor |
to GRUB_CMDLINE_LINUX="" in /etc/default/grub.
Code: | synclient TouchpadOff=1 |
should turn off your touchpad.
Code: | synclient TouchpadOff=0 |
to turn it back on.
add the command to .bashrc to make it permanent. |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Sun Oct 09, 2016 6:18 pm Post subject: |
|
|
Have you checked maxbacklight or what the value is called in that folder?
Code: | echo "5" > /sys/class/backlight/asus-nb-wmi/brightness |
Usually its 1 to 100.
It is heavily kernel related. So which notebook, which kernel, which kernel.config, which userspace ?
My 3 year old Asus g75vw works only with the latest kernel.org stable kernel. not with the antique ones. It also depends on many hidden kernel modules, which needs a bit of research. feel free to look up my posts, I documented it here. Sadly the search feature is not that well here.
You may use / adapt:
Code: | xrandr --output LVDS-0 --set Backlight 1 |
or
Code: | xrandr --output LVDS-0 --set Backlight 100 |
for the touchpad
Code: | if [ $(synclient -l | grep TouchpadOff | awk '{print $3}') == 1 ] ; then synclient touchpadoff=0; else synclient touchpadoff=1; fi |
Of course it implies that you have the related userspace tools, and kernel prepared and that your BIOS uses the same values as mine does.
You need to check xrandr extension which outputs are available for example ...
--
Quote: | The buttons to control the keyboard backlight work perfectly, |
Which desctop environment are you using?
It also depends on teh desctop environment in question |
|
Back to top |
|
|
RayDude Advocate
Joined: 29 May 2004 Posts: 2051 Location: San Jose, CA
|
Posted: Sun Oct 09, 2016 11:11 pm Post subject: |
|
|
Thanks!
I tried this in the kernel command line:
Code: |
acpi_osi= acpi_backlight=vendor
|
No dice.
max_backlight is "10" and setting backlight to "0" has no effect.
I couldn't get xrandr to work. Note: I had to do xrandr -q to find out which output was in use.
Code: | xrandr --output DP-2 --set brightness 5
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 139 (RANDR)
Minor opcode of failed request: 11 (RRQueryOutputProperty)
Serial number of failed request: 39
Current serial number in output stream: 39
|
I tried "backlight" as well but got a similar message.
I'm currently looking for the synclient tool. I figure it's part of the synaptiks package.
Thanks for trying. I'll keep plugging away. _________________ Some day there will only be free software. |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Mon Oct 10, 2016 9:22 am Post subject: |
|
|
Please provide the required informations.
also acpi_listen and other related outputs
Again: I have already posted several times for my notebook on how to resolve that issue.
Quote: | acpi_osi= acpi_backlight=vendor |
No idea why guys post that, that never works for endless bug reports on kernel.org
Did you read kernel.org bugzilla for your hardware ? Bios ?
--
As long as you do not provide the requested informations, I will ignore this topic.
Asus, MSI and others manufacture several gaming notebooks a year, so it is not a generic issue, its a hardware platform specific issue. And its UEFI - ACPI - Desctop - Kernel related issue |
|
Back to top |
|
|
mrbassie l33t
Joined: 31 May 2013 Posts: 771 Location: over here
|
Posted: Mon Oct 10, 2016 10:29 am Post subject: |
|
|
RayDude wrote: |
I'm currently looking for the synclient tool. I figure it's part of the synaptiks package.
Thanks for trying. I'll keep plugging away. |
I think you just need INPUT_DEVICES="synaptics" in make.conf. |
|
Back to top |
|
|
RayDude Advocate
Joined: 29 May 2004 Posts: 2051 Location: San Jose, CA
|
Posted: Tue Oct 11, 2016 4:37 pm Post subject: |
|
|
I'm using KDE, sorry forgot to say.
I found a related bug at bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=112531
I'm reading through it now.
Thanks for the help.
Roman_Gruber wrote: | Please provide the required informations.
also acpi_listen and other related outputs
Again: I have already posted several times for my notebook on how to resolve that issue.
Quote: | acpi_osi= acpi_backlight=vendor |
No idea why guys post that, that never works for endless bug reports on kernel.org
Did you read kernel.org bugzilla for your hardware ? Bios ?
--
As long as you do not provide the requested informations, I will ignore this topic.
Asus, MSI and others manufacture several gaming notebooks a year, so it is not a generic issue, its a hardware platform specific issue. And its UEFI - ACPI - Desctop - Kernel related issue |
_________________ Some day there will only be free software. |
|
Back to top |
|
|
Vrenn Guru
Joined: 15 Dec 2004 Posts: 313
|
Posted: Tue Oct 11, 2016 6:16 pm Post subject: |
|
|
If I might dare to give some points from my ROG G751-JY here.
Changing backlight works smooth "stepless" adjustable using the power manager in the KDE-systray (kde-plasma/powerdevil?) using kde5 and nvidia-drivers.
Buttons don't work either, but brightness-change (in systray) works easy. acpi_listen also tells me just the keys/acpi-signals are ignored/not happening. yout kernel-bug seems to be a good address.
For the annoying touchpad I use a script started by user-kde-autorun at the session-begin. It freezes the touchpad on typing. Code: | #!/bin/sh
#lock synaptic touchpad when typing
#syndaemon -i 1 -t -d
syndaemon -i 1 -R -t -k -d
#syndaemon -i 1 -R -k -d | I tested several options, the second fits most for me. Have a look at "man syndaemon" (x11-drivers/xf86-input-synaptics).
For KDE kde-misc/kcm-touchpad might also do the job, but never tested it. _________________ With nice greetings
Vrenn |
|
Back to top |
|
|
RayDude Advocate
Joined: 29 May 2004 Posts: 2051 Location: San Jose, CA
|
Posted: Tue Oct 11, 2016 6:57 pm Post subject: |
|
|
Thanks.
It's strange. My keyboard backlight controls fully work. And the "Battery and Brightness Widget" sees the keyboard controls, but do not see the screen brightness controls.
Although I'm back to using an external monitor. I wonder if it's smart enough to know that...
I'll have to open the notebook to find out. _________________ Some day there will only be free software. |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Wed Oct 12, 2016 5:21 am Post subject: |
|
|
You should search for my ASUS g75VW bug reports on kernel.org. there are at least two afaik. They reveal some kernel options ..
REgarding the screen brightness it depends on the gpu and uefi. xrandr is a way to go for my hardware
I hope you guys provide enough informations for the kernel devs, so the kernel gets fixed. |
|
Back to top |
|
|
|