Comment 3 for bug 314119

Hi Leann,

On Tue, Jan 06, 2009 at 06:41:23PM -0000, Leann Ogasawara wrote:
> I don't suppose you'd be willing to do a git bisect to help narrow down
> the patch? 2.6.27-11.21 pulled in the upstream 2.6.27.8 and 2.6.27.9
> stable patch sets - bug 308761 . 2.6.27-11.22 pulled in the 2.6.27.10
> stable patch set - bug 309731 . You might even want to just quickly
> test the 2.6.27-11.21 build to try to quickly narrow down which patch
> set to focus on - https://edge.launchpad.net/ubuntu/intrepid/i386/linux-
> image-2.6.27-11-generic/2.6.27-11.21 . I'll post comments to bug 308761
> and 309731 about this regression. Thanks.

I tested 2.6.27-11.21 and brightness adjustments were broken there
as well. It seems quite likely to be a regression introduced by the
fixes for bug 257827; per the discussion with apw in that bug, adding
"options thinkpad_acpi brightness_enable=1" to /etc/modprobe.d/options
as a workaround causes the brightness settings to work again.

apw did ask that I test with a Jaunty kernel to see if the problem exists
there as well; is there any tips or tricks to installing a jaunty kernel
on intrepid? Otherwise I suppose I could boot one of the jaunty livecds.

Thanks.