On Fri, 20 Jun 2008, [EMAIL PROTECTED] wrote: > H> 1. If it is *spamming* your logs with *lots* of EC/NVRAM out of sync > No, that message only happens when I tried > echo 0 > /sys/class/backlight/thinkpad_screen/brightness > to counteract xdm or whatever it is that turns my thinkpad to full > brightness, as mentioned in this bug report. > > But now that I use the better workaround of > echo level 0 > /proc/acpi/ibm/brightness > in /etc/X11/xdm/Xsetup I don't see that message anymore.
They are supposed to do *exactly* the same thing in thinkpad-acpi... but hey, it *is* two code paths, one of which doesn't go through the horrible backlight sysfs class, but rather the even worse proc fs :-) Please tell me the exact version of the kernel and thinkpad-acpi in your box, I will look into it. Might be a timing issue, but it might be some real bug. I do remember I added better locking to that area of the code a while back. cat /proc/acpi/ibm/version would help, as well as uname -a output. > I hope I'm not doing anything bad. At least my workaround saves me > having to adjust the brightness back down each time I start xdm. No, you're not doing anything bad. It should be safe, as long as you don't press any brightness keys, and you do it BEFORE running xdm, or AFTER it has settled down. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
