laptop brightness problem with Slackware current and kernel 4.1.6
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
laptop brightness problem with Slackware current and kernel 4.1.6
Hi, After upgrading my 64bit Slackware current the brightness buttons on my laptop are acting strange as if two programs are managing the brightness and one of them is doing it badly.
I have always used xfce-power-manager for brightness before, and that still seems to be working OK because if I use the brightness slider on the tray icon it works as expected.
Putting values into /sys/class/backlight/acpi_video0/brightness works OK too (which is what I think xfce-power-manager does)
Using the brightness keys on the laptop does update /sys/class/backlight/acpi_video0/brightness properly, but it also flickers the brightness between high and low at the same time and the end result seems random. It could end up extra bright or extra dim whatever the acpi_video0 brightness is set to. This happens even without X running, so I think it is something to do with the kernel but does anyone know what? I would like to stop the kernel changing brightness when I press the brightness buttons if possible and just have it managed by xfce-power-manager like before.
I also have /sys/class/backlight/radeon_bl0 with a brightness and actual_brightness. The actual_brightness seems to randomly go up and down when I use the brightness keys
edit:
I added the radeon.backlight=0 option to my lilo.conf so now the radeon_bl0 is gone from /sys but the brightness still flickers when using the brightness buttons even though the values in acpi_video0 are updating properly. When getting acpi_video0/brightness down to 0 using the buttons the brightness actually displays at about 50%. If using the xfce-power-manager slider or doing echo 0 > brightness the brightness is displayed properly.
Last edited by af7567; 08-23-2015 at 07:50 AM.
Reason: some more testing
First, is your BIOS up-to-date? Someone suggested that could help on a different thread.
Second, what if you try going in the BIOS as per the second thread and mapping the keys differently? Someone got it working with this, at least partially.
Third, was it working in an older release? The first thread suggests it has always been a problem, and may once have been fixed in the kernel, but some people reported the problem returning.
Fourth, try checking dmesg after an attempt to change the brightness with the buttons. Post any output near the end regarding ACPI or brightness or both.
Fifth, try combinations of the following in your kernel parameters:
Sixth, read the launchpad bug thread (first link) for anything I might have missed.
Maybe one of these will help. The only other thing I find odd is that on launchpad everyone says they have Intel integrated graphics, but you have a Radeon. I wonder why.
Thanks for your reply. Unfortunately none of these kernel options make a difference. I tried them all together and one at a time but nothing changes, I did reboot and re-run lilo each time I changed them.
I have had slackware on here for a few years and the brightness has always worked fine, it was just with the latest current update that it went wrong when the kernel was updated to 4.1.6.
The brightness control and buttons are still actually working OK using the ACPI interface as it always has done, but there is also another module or something catching the keypresses as well now and causing flickering. I want to disable this module.
There is nothing in dmesg that lets me see what this extra module might be, the only mention of brightness is:
Code:
[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
Which was mentioned in the links you posted, but the ACPI brightness interface is the one that is working fine. The BIOS is up to date.
I also have problem with brightness with radeon but only in KDE.
It works in xfce and from an terminal with "echo 100 > /sys/class/backlight/radeon_bl0/brightness".
I tried an older kernel i have installed but it was the same so i don't think it's the kernel in my case.
I haven't tried with catalyst but i might recompile KDE to see if it solves the problem, but right now i have to little time to play around.
Any tip on what KDE package to recompile?
I still have strange flickering brightness changes when using the brightness buttons, but I just noticed today it only happens when the laptop is plugged into AC power. When running on battery the brightness changes are smooth up and down steps as they should be. On AC it flickers dim then bright on every keypress.
Also, I found your other thread about your laptop crashing. Did you ever get that fixed?
I think I have fixed the laptop crashing problem now. It was caused by 2 things. The biggest problem was whenever my bluetooth mouse went to sleep and disconnected from the system it would result in X doing something that crashed the system and dmesg showed the kernel BUG message in my other post. I "fixed" that by not using my bluetooth USB dongle + mouse anymore.
The other thing sometimes causing the kernel BUG message was conky accessing the hwmon i8k module. This module was never used in previous kernel versions so I blacklisted it now and haven't had a crash since.
Sorry for not replying earlier, I haven't checked back here for a while.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.