Well, I'm glad everything is working for you.

If that's still a problem... for the backlight you can use setpci to directly write the values because xbacklight also broke for me since I started using KMS. So this is rather a dirty workaround...voRia wrote:Kernel 2.6.30-10 enables KMS by default, breaking screen backlight support.slasher-fun wrote: Hi,
Screen Backlight support seems not working with 2.6.30-10. Works fine with -9.
You can disable KMS by creating a new .conf file in /etc/modprobe.d/ containing this line:or you can use the kernel 2.6.30-10 from my repository, in which I've disabled KMS by default.Code: Select all
options i915 modeset=0
Code: Select all
# setpci -s 00:02.1 F4.B=xx
Here you can find a kernel module which enables the backlight control when KMS is in use (more info in this bug report).crocomo wrote: If that's still a problem... for the backlight you can use setpci to directly write the values because xbacklight also broke for me since I started using KMS. So this is rather a dirty workaround...
Where xx ranges from 00 to ff. (00 being minimum, ff the maximum).Code: Select all
# setpci -s 00:02.1 F4.B=xx
I remember youcrocomo wrote: Btw, voRia should still know me as I wrote you an E-Mail some long time ago...![]()
Ok, didn't know about this bug report. Should have searched morevoRia wrote: Here you can find a kernel module which enables the backlight control when KMS is in use (more info in this bug report)....
Yep! That's mevoRia wrote: I remember you
If I'm not wrong your idea was to create a repository/wiki for using ArchLinux on the NC10, right?
If you did it, please give us some links!![]()
Ok, didn't know about this bug report. Should have searched more'voRia' pid='1761' dateline='1250586200' wrote: Here you can find a kernel module which enables the backlight control when KMS is in use (more info in this bug report)....
Yep! That's me'voRia' pid='1761' dateline='1250586200' wrote: I remember you
If I'm not wrong your idea was to create a repository/wiki for using ArchLinux on the NC10, right?
If you did it, please give us some links!![]()
Can you post your script? Maybe I can merge it with my current scripts in order to have different ways to control backlight?crocomo wrote: But the solution via setpci on KMS works like a charm for me. So I'll stick with that for now...
Good to know that everything works out of the box with Arch.crocomo wrote: Yep! That's me
But since everything is working just fine out of the box (as far as the hardware goes) there is no need for having extra packages in AUR... and there also was an wiki entry, which can be found here. Only describes some general stuff...
Sure. No problem.voRia wrote: Can you post your script? Maybe I can merge it with my current scripts in order to have different ways to control backlight?
Code: Select all
#!/bin/sh
# adjust backlight via setpci and dpms via vbetool
# Check if root called this script
USER=`whoami`
if [ $USER != "root" ]; then
echo "Need to be root to run this script."
exit 1
fi
# Get old value
OLD=$[16#`setpci -s 00:02.1 F4.B`]
case "$1" in
inc)
# Check if value given
if [ -z "$2" ]; then
echo "Usage: $0 $1 <value>"
exit 1
fi
# Take second argument as value to increment
NEW=$[$OLD+$2]
# Set new value
$0 set $NEW
;;
dec)
# Check if value given
if [ -z "$2" ]; then
echo "Usage: $0 $1 <value>"
exit 1
fi
# Take second argument as value to decrement
NEW=$[$OLD-$2]
# Set new value
$0 set $NEW
;;
set)
# Check if value given
if [ -z "$2" ]; then
echo "Usage: $0 $1 <value>"
exit 1
fi
# Take second argument as value to set
NEW=$2
# Check if value less than 0
if [ "$NEW" -lt "0" ]; then
NEW=0
fi
# Check if value greater than 255
if [ "$NEW" -gt "255" ]; then
NEW=255
fi
# Set new value
setpci -s 00:02.1 F4.B=`echo "obase=16; ibase=10; $NEW" | bc`
;;
toggle)
# Path to logfile
LOG=/tmp/backlight.log
# Check if logfile does not exist
if [ ! -f $LOG ]; then
vbetool dpms off
touch $LOG
else
vbetool dpms on
rm -rf $LOG
fi
;;
*)
echo "Usage: $0 (inc <value>|dec <value>|set <value>|toggle)"
exit 1
;;
esac
exit 0