Ah, this workaround finally worked: # rmmod thinkpad-acpi; modprobe thinkpad-acpi brightness_mode=2
Fn End typed after this apparently last even thru reboots! OK, until bug is fixed I'm sticking that line in ~root/.bash_profile as apparently no way to put parameters into /etc/default/acpid. (Wonder what the original parameter was. Apparently there is no way to check what parameters a running module uses.) P.S., now mostly irrelevant, but: >> linux-doc-2.6.25/Documentation/laptops/thinkpad-acpi.txt.gz H> There are warnings in there already, yes. OK, got to read the whole document probably. Most folks just grep to a section. H> Well, stop HAL. If the mess stops, at least we know it is something H> dangling from HAL or DBUS. Stopped hal, /etc/init.d/xdm start still cranked up brightness. H> rmmod video Didn't help H> rmmod thinkpad-acpi; modprobe thinkpad-acpi debug=0xffff Some boring output attached.
th.gz
Description: boring
