Backlight slider no longer works in Linux Mint
up vote
1
down vote
favorite
I'm running Linux Mint 18 Cinnamon on my Asus X555LA, which also has Windows 10 installed on another partition (the backlight works perfectly in Windows).
However in Linux Mint: there's already an issue with Fn+F5/F6 not changing the backlight intensity. The various fixes I've tried (but haven't worked) include:
- adding a
20-intel.conffile into the/usr/share/X11folder. - added
acpi_osi=to the/etc/default/grub
- Running
acpi_listenand pressing Fn+F5/F6 shows no output. - Installing
xbacklightand runningxbacklight -set $percentage
Until about two days ago I could skirt this issue by using the brightness slider in the UI, however even this no longer works and the screen brightness is stuck at 100%.
I am at a loss and no longer know what to do.
linux-mint acpi asus backlight
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
add a comment |
up vote
1
down vote
favorite
I'm running Linux Mint 18 Cinnamon on my Asus X555LA, which also has Windows 10 installed on another partition (the backlight works perfectly in Windows).
However in Linux Mint: there's already an issue with Fn+F5/F6 not changing the backlight intensity. The various fixes I've tried (but haven't worked) include:
- adding a
20-intel.conffile into the/usr/share/X11folder. - added
acpi_osi=to the/etc/default/grub
- Running
acpi_listenand pressing Fn+F5/F6 shows no output. - Installing
xbacklightand runningxbacklight -set $percentage
Until about two days ago I could skirt this issue by using the brightness slider in the UI, however even this no longer works and the screen brightness is stuck at 100%.
I am at a loss and no longer know what to do.
linux-mint acpi asus backlight
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
useful info would be dmeg output, dsdt dump, also what dirs exist in "/sys/class/backlight/" currently?
– mikejonesey
Nov 23 '16 at 18:47
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm running Linux Mint 18 Cinnamon on my Asus X555LA, which also has Windows 10 installed on another partition (the backlight works perfectly in Windows).
However in Linux Mint: there's already an issue with Fn+F5/F6 not changing the backlight intensity. The various fixes I've tried (but haven't worked) include:
- adding a
20-intel.conffile into the/usr/share/X11folder. - added
acpi_osi=to the/etc/default/grub
- Running
acpi_listenand pressing Fn+F5/F6 shows no output. - Installing
xbacklightand runningxbacklight -set $percentage
Until about two days ago I could skirt this issue by using the brightness slider in the UI, however even this no longer works and the screen brightness is stuck at 100%.
I am at a loss and no longer know what to do.
linux-mint acpi asus backlight
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
I'm running Linux Mint 18 Cinnamon on my Asus X555LA, which also has Windows 10 installed on another partition (the backlight works perfectly in Windows).
However in Linux Mint: there's already an issue with Fn+F5/F6 not changing the backlight intensity. The various fixes I've tried (but haven't worked) include:
- adding a
20-intel.conffile into the/usr/share/X11folder. - added
acpi_osi=to the/etc/default/grub
- Running
acpi_listenand pressing Fn+F5/F6 shows no output. - Installing
xbacklightand runningxbacklight -set $percentage
Until about two days ago I could skirt this issue by using the brightness slider in the UI, however even this no longer works and the screen brightness is stuck at 100%.
I am at a loss and no longer know what to do.
linux-mint acpi asus backlight
linux-mint acpi asus backlight
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
asked Nov 16 '16 at 8:44
Virtual Anomaly
1063
1063
useful info would be dmeg output, dsdt dump, also what dirs exist in "/sys/class/backlight/" currently?
– mikejonesey
Nov 23 '16 at 18:47
add a comment |
useful info would be dmeg output, dsdt dump, also what dirs exist in "/sys/class/backlight/" currently?
– mikejonesey
Nov 23 '16 at 18:47
useful info would be dmeg output, dsdt dump, also what dirs exist in "/sys/class/backlight/" currently?
– mikejonesey
Nov 23 '16 at 18:47
useful info would be dmeg output, dsdt dump, also what dirs exist in "/sys/class/backlight/" currently?
– mikejonesey
Nov 23 '16 at 18:47
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
lsmod | grep video
(video is the kernel driver that handles acpi calls for brightness)
You can check if "/sys/class/backlight/acpi_video0" exists, and you can use;
acpi_listen
...to check for the acpi event.
Essentially the firmware triggers one of the Q functions which triggers a notify to the monitor with either 0x87 or 0x86, when this is received the brightness can be changed.
If for whatever reason the DSDT tables doesn't have certain methods like _DOD then kernel acpi wont recognize the definition of a monitor.
Regardless, you can boot your kernel with acpi_backlight=video to force video.ko to control the backlight (this will use acpi based values defined in BCL).
When you use vendor it'll use vendor specific acpi or rely simply on the pci device.
Regardless of acpi you can always change your brightness via pci bypassing acpi.
To do this check out /sys/class/backlight/ for a dir with the name amd or intel.
You can echo to the brightness file, this won't use the brightness levels defined in the DSDT tables so you actually get a larger variety of brightness levels.
PS... the only forced detections for Asus laptops are to force vendor.
These laptops are;
- Asus UL30VT
- Asus UL30A
There is no reference for "X555LA", so I'd try acpi_backlight=video before acpi_backlight=vendor.
edited Nov 30 at 16:38
Community♦
1
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
1
No offence, but this answer just reads like a ramble. Any chance of clarifying what you mean, please?
– Virtual Anomaly
Nov 23 '16 at 14:49
If you try adding "acpi_backlight=video", in grub or whatever boot loader you have, then test the buttons and also acpi_listen again. if this does not solve your problem, i'll update the post.
– mikejonesey
Nov 23 '16 at 18:45
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
lsmod | grep video
(video is the kernel driver that handles acpi calls for brightness)
You can check if "/sys/class/backlight/acpi_video0" exists, and you can use;
acpi_listen
...to check for the acpi event.
Essentially the firmware triggers one of the Q functions which triggers a notify to the monitor with either 0x87 or 0x86, when this is received the brightness can be changed.
If for whatever reason the DSDT tables doesn't have certain methods like _DOD then kernel acpi wont recognize the definition of a monitor.
Regardless, you can boot your kernel with acpi_backlight=video to force video.ko to control the backlight (this will use acpi based values defined in BCL).
When you use vendor it'll use vendor specific acpi or rely simply on the pci device.
Regardless of acpi you can always change your brightness via pci bypassing acpi.
To do this check out /sys/class/backlight/ for a dir with the name amd or intel.
You can echo to the brightness file, this won't use the brightness levels defined in the DSDT tables so you actually get a larger variety of brightness levels.
PS... the only forced detections for Asus laptops are to force vendor.
These laptops are;
- Asus UL30VT
- Asus UL30A
There is no reference for "X555LA", so I'd try acpi_backlight=video before acpi_backlight=vendor.
edited Nov 30 at 16:38
Community♦
1
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
1
No offence, but this answer just reads like a ramble. Any chance of clarifying what you mean, please?
– Virtual Anomaly
Nov 23 '16 at 14:49
If you try adding "acpi_backlight=video", in grub or whatever boot loader you have, then test the buttons and also acpi_listen again. if this does not solve your problem, i'll update the post.
– mikejonesey
Nov 23 '16 at 18:45
add a comment |
up vote
0
down vote
lsmod | grep video
(video is the kernel driver that handles acpi calls for brightness)
You can check if "/sys/class/backlight/acpi_video0" exists, and you can use;
acpi_listen
...to check for the acpi event.
Essentially the firmware triggers one of the Q functions which triggers a notify to the monitor with either 0x87 or 0x86, when this is received the brightness can be changed.
If for whatever reason the DSDT tables doesn't have certain methods like _DOD then kernel acpi wont recognize the definition of a monitor.
Regardless, you can boot your kernel with acpi_backlight=video to force video.ko to control the backlight (this will use acpi based values defined in BCL).
When you use vendor it'll use vendor specific acpi or rely simply on the pci device.
Regardless of acpi you can always change your brightness via pci bypassing acpi.
To do this check out /sys/class/backlight/ for a dir with the name amd or intel.
You can echo to the brightness file, this won't use the brightness levels defined in the DSDT tables so you actually get a larger variety of brightness levels.
PS... the only forced detections for Asus laptops are to force vendor.
These laptops are;
- Asus UL30VT
- Asus UL30A
There is no reference for "X555LA", so I'd try acpi_backlight=video before acpi_backlight=vendor.
edited Nov 30 at 16:38
Community♦
1
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
1
No offence, but this answer just reads like a ramble. Any chance of clarifying what you mean, please?
– Virtual Anomaly
Nov 23 '16 at 14:49
If you try adding "acpi_backlight=video", in grub or whatever boot loader you have, then test the buttons and also acpi_listen again. if this does not solve your problem, i'll update the post.
– mikejonesey
Nov 23 '16 at 18:45
add a comment |
up vote
0
down vote
up vote
0
down vote
lsmod | grep video
(video is the kernel driver that handles acpi calls for brightness)
You can check if "/sys/class/backlight/acpi_video0" exists, and you can use;
acpi_listen
...to check for the acpi event.
Essentially the firmware triggers one of the Q functions which triggers a notify to the monitor with either 0x87 or 0x86, when this is received the brightness can be changed.
If for whatever reason the DSDT tables doesn't have certain methods like _DOD then kernel acpi wont recognize the definition of a monitor.
Regardless, you can boot your kernel with acpi_backlight=video to force video.ko to control the backlight (this will use acpi based values defined in BCL).
When you use vendor it'll use vendor specific acpi or rely simply on the pci device.
Regardless of acpi you can always change your brightness via pci bypassing acpi.
To do this check out /sys/class/backlight/ for a dir with the name amd or intel.
You can echo to the brightness file, this won't use the brightness levels defined in the DSDT tables so you actually get a larger variety of brightness levels.
PS... the only forced detections for Asus laptops are to force vendor.
These laptops are;
- Asus UL30VT
- Asus UL30A
There is no reference for "X555LA", so I'd try acpi_backlight=video before acpi_backlight=vendor.
edited Nov 30 at 16:38
Community♦
1
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
lsmod | grep video
(video is the kernel driver that handles acpi calls for brightness)
You can check if "/sys/class/backlight/acpi_video0" exists, and you can use;
acpi_listen
...to check for the acpi event.
Essentially the firmware triggers one of the Q functions which triggers a notify to the monitor with either 0x87 or 0x86, when this is received the brightness can be changed.
If for whatever reason the DSDT tables doesn't have certain methods like _DOD then kernel acpi wont recognize the definition of a monitor.
Regardless, you can boot your kernel with acpi_backlight=video to force video.ko to control the backlight (this will use acpi based values defined in BCL).
When you use vendor it'll use vendor specific acpi or rely simply on the pci device.
Regardless of acpi you can always change your brightness via pci bypassing acpi.
To do this check out /sys/class/backlight/ for a dir with the name amd or intel.
You can echo to the brightness file, this won't use the brightness levels defined in the DSDT tables so you actually get a larger variety of brightness levels.
PS... the only forced detections for Asus laptops are to force vendor.
These laptops are;
- Asus UL30VT
- Asus UL30A
There is no reference for "X555LA", so I'd try acpi_backlight=video before acpi_backlight=vendor.
edited Nov 30 at 16:38
Community♦
1
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
edited Nov 30 at 16:38
Community♦
1
edited Nov 30 at 16:38
Community♦
1
edited Nov 30 at 16:38
Community♦
1
1
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
answered Nov 19 '16 at 15:31
mikejonesey
1,362415
1,362415
1
No offence, but this answer just reads like a ramble. Any chance of clarifying what you mean, please?
– Virtual Anomaly
Nov 23 '16 at 14:49
If you try adding "acpi_backlight=video", in grub or whatever boot loader you have, then test the buttons and also acpi_listen again. if this does not solve your problem, i'll update the post.
– mikejonesey
Nov 23 '16 at 18:45
add a comment |
1
No offence, but this answer just reads like a ramble. Any chance of clarifying what you mean, please?
– Virtual Anomaly
Nov 23 '16 at 14:49
If you try adding "acpi_backlight=video", in grub or whatever boot loader you have, then test the buttons and also acpi_listen again. if this does not solve your problem, i'll update the post.
– mikejonesey
Nov 23 '16 at 18:45
1
1
No offence, but this answer just reads like a ramble. Any chance of clarifying what you mean, please?
– Virtual Anomaly
Nov 23 '16 at 14:49
No offence, but this answer just reads like a ramble. Any chance of clarifying what you mean, please?
– Virtual Anomaly
Nov 23 '16 at 14:49
If you try adding "acpi_backlight=video", in grub or whatever boot loader you have, then test the buttons and also acpi_listen again. if this does not solve your problem, i'll update the post.
– mikejonesey
Nov 23 '16 at 18:45
If you try adding "acpi_backlight=video", in grub or whatever boot loader you have, then test the buttons and also acpi_listen again. if this does not solve your problem, i'll update the post.
– mikejonesey
Nov 23 '16 at 18:45
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f323638%2fbacklight-slider-no-longer-works-in-linux-mint%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
useful info would be dmeg output, dsdt dump, also what dirs exist in "/sys/class/backlight/" currently?
– mikejonesey
Nov 23 '16 at 18:47