On Mon, 2009-04-27 at 08:26 +0100, Richard Hughes wrote:
> On Sun, 2009-04-26 at 20:35 +0300, Maxim Levitsky wrote:
> > I am owner of an notebook which has hardware brightness keys, and this
> > is what happens when I press brightness up/down key:
> > 1 - hardware changes the brightness
> > 2 - in kernel acpi driver changes the brightness - can be disabled
> > (brightness_switch_enabled=0)
> > 3 - acpi driver sends a brightness/up down event using its own event
> > device - gpm sees this and again changes the brightness
> > 4 - keyboard also generates brightness up/down events - gpm again
> > changes brightness.
>
> You can either add brightness_switch_enabled=0 to modprobe.conf, or add
> the brightness_in_hardware hal key to the fdi file for your machine.
>
> I would be interested to the make and model of your laptop -- it sounds
> pretty pathological.
>
> Richard.
>
I did add 'brightness_in_hardware', and brightness_switch_enabled=0.
Now finally gpm doesn't mess with brightness, but still there is an
issue, which is kernel one. The issue is that if I use
brightness_switch_enabled=0, kernel doesn't update
/sys/class/backlight/acpi_video0/brightness - I understand perfect why
it does so, and thus I ask at LKML what to do next to make ACPI
brightness support suck less.
I don't yet know if it worth the effor to patch hal fdi files for my
system, since maybe its better to make kernel always handle the
brightness change, and thus always assume brightness_in_hardware=true
for acpi video.
Best regards,
Maxim Levitsky
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list
