Dear HMH, I have continued my observations. It seems the only time I
have to still hit Fn End to bring the brightness back down is after a
reboot: using reboot(8) brings one to a super bright Lilo screen.
And 'shutdown -h now' also will give a bright Lilo screen upon next
power up. (It is what I usually use, and each time the next day I have
to hit Fn End a few times there at the Lilo prompt before hitting RET
to enter GNU/Linux.)
OK, as an experiment at the above Lilo screens, I did my usual Fn Ends
to bring the brightness down to the minimum, but then instead of
hitting RET to enter GNU/Linux (image=/boot/vmlinuz-2.6.25-2-686), I
hit ALT-CTRL-DEL to reboot without the "help" of the reboot(8)
command. I was back sitting at the Lilo prompt with no brightness
problems this time. At this point I hit the power off button. The next
day powering back on also saw no brightness problem sitting there at
the Lilo prompt.
I conclude that my workaround,
# cat .bash_profile
case [EMAIL PROTECTED](hostname) in
[EMAIL PROTECTED])
j=/tmp/.jidanni_thinkpad_brightness #/tmp gone at boot
! test -f $j && ! pidof xdm > /dev/null &&
/sbin/rmmod thinkpad-acpi &&
/sbin/modprobe thinkpad-acpi brightness_mode=2 &&
touch $j;; [EMAIL PROTECTED]
esac
works great except that it does not cover the effects of reboot(8) and
shutdown(8). Therefore I would hope HMH would "neuter" them to not
mess with the brightness seen on the next boot! Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
