Hi Folks, I've recompiled the stock Ubuntu "fiesty" kernel (2.6.22-9-generic) after patching with this week's thinkpad_acpi patch, and behavior of /proc/acpi/ibm/brightness is much better but still not perfect. At this point, thinkpad_acpi tracks changes made using the keyboard brightness buttons and/or gnome-power-manager-preferences --- but it is still fooled when I close the laptop's lid or run "xset dpms force off". In these cases, the screen brightness (once restored from the off state) shoots up to 100%, but the thinkpad_acpi continues to report the previous value. I should mention that I'm running BIOS 2.12 and the "video" module is loaded on my system. (Is loading this module a mistake?) If this behavior sounds like a bug, I'd be glad to report any useful information about my system. -Josh One other point: when thinkpad_acpi gets out of sync, issuing a "level n" command has no effect if thinkpad_acpi incorrectly believes the display to already be at level n. For example, if thinkpad_acpi thinks the display's at level 0 but it's really at level 7, then I can't just issue "level 0" to dim the screen. I have to issue "level x" and then "level 0", where x !=0. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
