https://bugzilla.novell.com/show_bug.cgi?id=719076 https://bugzilla.novell.com/show_bug.cgi?id=719076#c20 --- Comment #20 from Drew Adams <Druonysus@gmail.com> 2011-11-19 22:52:05 UTC --- (In reply to comment #18)
(In reply to comment #17)
I thought this issue related to i915's combination mode. Michael Chang have experience on it.
This issue is much like i915 kms regression from 2.6.38-rc8 (bko#31522). No good fix to it so far as it is firmware(bios) related (As I know this regression only reported on ACER laptops, not seen on any other model so far).
Well .. to workaround it is possible by accessing the LPBC register directly instead of through ACPI (it also access LPBC but somewhat in a complicated path..).
Let me know how the commands work on your side ?
$ su $ setpci -s $(lspci | grep -i vga | cut -d" " -f1) F4.B=22 $ setpci -s $(lspci | grep -i vga | cut -d" " -f1) F4.B=66 $ setpci -s $(lspci | grep -i vga | cut -d" " -f1) F4.B=AA $ setpci -s $(lspci | grep -i vga | cut -d" " -f1) F4.B=FF
Your back-light should should be at max level when set F4.B=FF
Thanks.
Hey Michael, sorry I didn't get back with the responses to this sooner. I have been busy with job interviews and such... real life just got in the way and I didn't have a lot of time to sit down and try the solutiona and respond properly. When I did finally try these commands: each one changed the brightness of my screen to different levels and the last command turned the backlight all the way OFF. Once the last command was entered, the backlight was off but I could still turn it back up with the Fn+left key (labeled as brightness down). The fist command (setpci -s $(lspci | grep -i vga | cut -d" " -f1) F4.B=22) didn't change the brightness of my screen at all. It stayed at max brightness... Or near as I could tell. Maybe the bios is interpreting these values backwards? Is that possible? Thanks for the help. Sorry again for the late response. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.