On Fri, 18 Jul 2008, [EMAIL PROTECTED] wrote:
> OK, some results:
> Before shutdown -h I checked with Fn End that I was already in the
> dimmest state.
>
> However, at the next power-up, sitting at the Lilo prompt, I could use
> several Fn Ends to make the screen dimmer.
Is the BIOS backlight con
OK, some results:
Before shutdown -h I checked with Fn End that I was already in the
dimmest state.
However, at the next power-up, sitting at the Lilo prompt, I could use
several Fn Ends to make the screen dimmer.
Well even though it seems brightness is not remembered through cold
power ups, at l
On Tue, 15 Jul 2008, [EMAIL PROTECTED] wrote:
> H> Do I understand correctly, and now that you're using brightness_mode=2, you
> H> see no weird brightness changes when you lauch xdm, and your brightness
> keys
> H> work just fine?
> Yes, and yes.
>
> (I am still observing how well brightness set
H> Do I understand correctly, and now that you're using brightness_mode=2, you
H> see no weird brightness changes when you lauch xdm, and your brightness keys
H> work just fine?
Yes, and yes.
(I am still observing how well brightness settings last through boots.
I will mail back if they don't.)
reassign 485465 linux-2.6
retitle 485465 thinkpad-acpi: races on brightness change on a R50e
found 2.6.14-1
tag 485465 upstream
forwarded 485465 [EMAIL PROTECTED]
owner [EMAIL PROTECTED]
thanks
Synopsis: recently, brightness started acting up on R50e. Something is
racing with the firmware. Users
On Thu, 26 Jun 2008, [EMAIL PROTECTED] wrote:
> Ah, this workaround finally worked:
> # rmmod thinkpad-acpi; modprobe thinkpad-acpi brightness_mode=2
>
> Fn End typed after this apparently last even thru reboots!
Send me the output of the following commands, BY PRIVATE EMAIL
(don't cc bugs.debian
OK, I will do
echo options thinkpad-acpi brightness_mode=2 > /etc/modprobe.d/jidanni
But do tell me a way to check what the current parameters of
thinkpad-acpi are.
# find /proc /sys -name parameters|grep acpi|xargs ls
acpica_version
is all I found.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On Thu, Jun 26, 2008 at 08:20:19 +0800, [EMAIL PROTECTED] wrote:
> JC> 'options thinkpad-acpi brightness_mode=2' in /etc/modutils/something
> JC> should work.
>
> $ ls /etc/modutils/
> $
> Are you saying I should do
> # echo options thinkpad-acpi brightness_mode=2 > /etc/modutils/jidanni
>
oops,
JC> 'options thinkpad-acpi brightness_mode=2' in /etc/modutils/something
JC> should work.
$ ls /etc/modutils/
$
Are you saying I should do
# echo options thinkpad-acpi brightness_mode=2 > /etc/modutils/jidanni
>> Apparently there is no way to check what parameters a running module uses.)
JC> Shou
On Thu, Jun 26, 2008 at 06:13:36 +0800, [EMAIL PROTECTED] wrote:
> 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
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.
(Won
On Thu, 26 Jun 2008, [EMAIL PROTECTED] wrote:
> HMH: be sure to add your warning to
> linux-doc-2.6.25/Documentation/laptops/thinkpad-acpi.txt.gz
There are warnings in there already, yes.
> And it seems the severity of this bug should be elevated: something on
> Debian is hijacking the brightness
HMH: be sure to add your warning to
linux-doc-2.6.25/Documentation/laptops/thinkpad-acpi.txt.gz
And it seems the severity of this bug should be elevated: something on
Debian is hijacking the brightness, causing the user to need to hit Fn
End, or else go blind. But then we thus enter the realm of t
13 matches
Mail list logo
