Thanks for the help, it helped me with some of my problems. I couldn't really find the debian script you were referring to. I found one here
http://packages.debian.org/en/lenny/acpi-support,
but I couldn't figure out how it works. This is video_brightnessup.sh for example
Code:
#!/bin/sh
[ -f /usr/share/acpi-support/key-constants ] || exit 0
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_BRIGHTNESSUP
Well googling FOR video_brightnessup.sh I found this
http://www.ubuntugeek.com/fix-your-l...-in-hardy.html
and the scripts provided there lead me to a solution that sort of works.
I post my modified bash script here if someone has a similar issue, this is eg video_brightnessup.sh
Code:
#!/bin/bash
CURRENT=$(grep "current:" /proc/acpi/video/GFX0/LCD/brightness |awk '{print $2}')
LEVELS=$(grep "levels:" /proc/acpi/video/GFX0/LCD/brightness | sed 's/levels://')
for level in $LEVELS
do
if [ "$level" -gt "$CURRENT" ]
then
echo -n $level > /proc/acpi/video/GFX0/LCD/brightness
exit 0
fi
done
exit -1
This works fine and I'm able to adjust brightness from the command line. The thing is once I've changed the brightness from being 100 the Fn-[FX] combinations work again, but they don't really step the brightness but just either put it to 100 or to 0 without any intermediate steps. Once the brightness is back to 100 I can't control it anymore with these buttons. Adding the scripts as acpi events does help me from being stuck at 100 but it still steps through from 100 to 0 without intermediate steps. It is as though something else is also listening to the Fn-[FX] events apart from acpi?
I know these got kind of confusing, and I'm sort of ready to give up and see if this is fixed when the new kernel comes out. But if you have anymore ideas let me know!
