FS#30577 - [linux] 3.4.x - 3.6.x brightness controls doesn't work on Toshiba NB505
Attached to Project:
Arch Linux
Opened by Max Pray (synthead) - Friday, 06 July 2012, 23:35 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 January 2013, 14:58 GMT
Opened by Max Pray (synthead) - Friday, 06 July 2012, 23:35 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 January 2013, 14:58 GMT
|
Details
The Fn + (F6|F7) keys used to work in earlier versions of
the v3 kernel, now they don't respond after the system
boots. They function just fine with the laptop's firmware
(before the OS boots).
linux 3.4.4-2 (x86_64) Will provide more information as needed :) |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 23 January 2013, 14:58 GMT
Reason for closing: Fixed
Additional comments about closing: 3.6.10
Wednesday, 23 January 2013, 14:58 GMT
Reason for closing: Fixed
Additional comments about closing: 3.6.10
libxfce4ui 4.10.0-1
libxfce4util 4.10.0-1
xfce4-session 4.10.0-3
xfce4-settings 4.10.0-2
xfconf 4.10.0-2
xfdesktop 4.10.0-3
xfwm4 4.10.0-1
https://bugs.archlinux.org/task/31269
I've done some serious historical digging, this issue doesn't exist on any 2.6 kernel I had available. I'll see if I can pinpoint the 3.4.x kernel change that breaks this.
$ showkey
kb mode was UNICODE
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]
press any key (program terminates 10s after last keypress)...
keycode 28 release
keycode 224 press
keycode 224 release # this is for Fn+F6 (decrease brightness)
keycode 225 press
keycode 225 release # this is for Fn+F7 (increase brightness)
Tested with 3.5.3-1-ARCH and showkey version 1.15.3
I'm unsure if i'm affected by this bug or if https://bugs.archlinux.org/task/31269 is applicable. Still investigating.
*edit*
It's fine up till 3.3.8-1-ARCH, things break on the first 3.4-1-ARCH. This matches the sheer masses of ACPI related backlight / brightness control reports that are already available on the kernel's bugtracker. Next step will be to revert all the ACPI-related commits in the 3.4-rc1 kernel.
Either way, I'm fairly confident this is an upstream regression. Will be compiling vanilla to confirm.
Given that this is a fairly old commit, I can't simply revert it or create a patch against the current stable... Too much has changed to the affected block of code since that commit and I'm certainly no ACPI wiz. Hopefully more to come.
https://bugzilla.kernel.org/show_bug.cgi?id=47861
Sadly this issue is very hardware dependent and causes may vary between models, people are generally advised to open their own model specific bug-reports on the kernel's bug-tracker.
In general: I would suggest you all to do as I did, track down the kernel commit that causes the bug and submit it to the kernel bugtracker + cc-ing the author of the commit. Issues like these are very likely to be caused by upstream development, this is the proper place to report these bugs and get them fixed in stable. I would suggest to report under ACPI Power-Video component.
If anything, finding the commit that causes the issue for you will help you track down the possible cause as searching on the commit hash might provide better results than other arbitrary search terms.
for HP 6720s laptop owners, the fix (workaround) was recently submitted for discussion:
http://thread.gmane.org/gmane.linux.acpi.devel/56345
Let's hope for fast turnover!
I control brightness in such way:
# echo 13 > /sys/class/backlight/acpi_video0/brightness
This is temporary solution, i hope this will be fixed..
@others with similar issues: You really should post DMESG output or attempt to bisect the kernel yourself, there are piles upon piles of laptop model specific patches in the kernel tree and the kernel devs are now of the opinion that expecting hardware to be perfect is silly.
This means they want you to report these hardware irks.