Comment 81 for bug 333386

Ok, I can post the results, does it make the difference if I post results
from the 'normal' distribution and not from yours (modified)? That's so
weird, so previously it was working because no programmatic check was done
by DSDT? I agree, new bios should be tried, but since it's a critical step
and I have critical projects with upcoming deadlines and can't afford the
risk... next time I'll use warranty I will ask for an update...

2009/7/7 Stefan Bader <email address hidden>

>
> I believe the BIOS is buggy with that respect (not sure why the DSDT
> compiler
> freaks out but that might be a different issue). I manually looked up those
> values in the DSDT you provided, so based on that data the kernel takes the
> right steps. The question is whether the new BIOS fixes this or whether
> this
> needs a general exemption for being a special (known broken) machine.
> It seemed to have worked in the past. There certainly can be a solution to
> Jaunty (though it needs a kernel change), but that cannot be the sole
> solution
> as it will likely break with every newer kernel. I cannot exactly say how
> to
> proceed from here. But I try to ask around. Meanwhile to complete the data
> gathered here, could you add the output of "sudo lspci -vvvnn" to the bug
> report please?
>
> --
> Cannot change brightness with 2.6.27-11+ kernel
> https://bugs.launchpad.net/bugs/333386
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “linux” package in Ubuntu: Confirmed
> Status in linux in Ubuntu Intrepid: Fix Committed
> Status in linux in Ubuntu Jaunty: In Progress
>
> Bug description:
> Since the 2.6.27-11 generic kernel (also in 2.6.27-12) I cannot change the
> backlight brightness anymore. In the latest kernel, it seems there's no more
> file in /proc/acpi/video, but GFX0 still apears in 2.6.27-9 where I can
> still change brightness. I'm new to linux so if you need information give me
> the command to run. It's an acer 6920G laptop.
>