So, really, I do not think a fix in userspace will help me much for years down the road. I may want to switch to Hans' proposed solution once that has trickeled through to Debian stable userspace (I am limited to that or SLES at work), but wether this machine will live to that day and age is anybody's guess. That's fine for me unless that's supposed to go away too, or be allowed to break. So, _if_ I understand you correctly, I will just go ahead and keep the e_native_backlight=0 in the command line. Relying on the DE to handle the brightness keys falls short as it doesn't work on consoles (I have fluxbox handle brightness events on my XO laptop, and find this annoying). The acpid needs to poll the nvram for the brightness keys anyway. If it is supposed to be userspace's job to control brightness, Hans' proposal sounds good to me. I really think the kernel should just continue handle the brightness events by itself, as it "always" did. Perhaps that definition is too broad?Īnyway, in regard to Hans' proposition of fixing this in acpid, I cannot really offer much beside bikeshedding. So I am somewhat surprised that this box is categorized just like the "real" Win8 machines. So this is _not_ a proper "Windows 8" machine, as in Microsoft would not allow shipping this box with Windows 8, AFAIK. Let me get up to speed here: The native backlight interface is not even _supposed_ to handle brightness control events from ACPI? ACPI just signals the events to userspace and is done with it?Īlso, to avoid any confusion with "Ẃindows 8 compatibility": Note that the T420 predates Windows 8, and while it can run Win8 in compat mode, the bios is not secure boot capable, among other things. Set of patches fixes the regression this bug is aboutĭisable native backlight for ThinkPad X201sĪcpidump for Thinkpad x201s (with bios 6QET70WW (1.40 )) Acpid script to change intel_backlight using the brightness keys
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |