On Wed, Dec 17, 2008 at 10:44 AM, Khashayar Naderehvandi <khashayar.lists@xxxxxxxxx> wrote: > On Wed, Dec 17, 2008 at 1:57 AM, Zhang Rui <rui.zhang@xxxxxxxxx> wrote: >> On Wed, 2008-12-17 at 04:55 +0800, Matthew Garrett wrote: >>> On Tue, Dec 16, 2008 at 10:00:23AM -0800, Andrew Morton wrote: >>> >>> > OK, that's weird. I have a suspicion that we're about to find out that >>> > this is intentional, but I don't know what the fix is.. >>> >>> My recollection is that some BIOSes provide the list of brightness >>> values in reverse order - someone posted a patch to sort them in-kernel, >>> but I can't remember what happened to it. xbacklight will work because >>> it triggers a direct write to the hardware if the acpi driver isn't >>> loaded. >>> >> right, this seems to be a duplicate of >> http://bugzilla.kernel.org/show_bug.cgi?id=12037 >> >> khashayar, >> please attach the result of "grep . /proc/acpi/video/*/*/*". >> please try the patch in >> http://bugzilla.kernel.org/show_bug.cgi?id=12037#c5 >> and see if it helps. >> > Here's the output of "grep . /proc/acpi/video/*/*/*". The video module > wasn't loaded at boot time, but just before greping. I don't know if > that has any relevance. Also, there's an external display attached at > this point. > > /proc/acpi/video/VGA/CRTD/brightness:<not supported> > /proc/acpi/video/VGA/CRTD/EDID:<not supported> > /proc/acpi/video/VGA/CRTD/info:device_id: 0x0100 > /proc/acpi/video/VGA/CRTD/info:type: CRT > /proc/acpi/video/VGA/CRTD/info:known by bios: yes > /proc/acpi/video/VGA/CRTD/state:state: 0x1d > /proc/acpi/video/VGA/CRTD/state:query: 0x00 > /proc/acpi/video/VGA/DVID/brightness:<not supported> > /proc/acpi/video/VGA/DVID/EDID:<not supported> > /proc/acpi/video/VGA/DVID/info:device_id: 0x0321 > /proc/acpi/video/VGA/DVID/info:type: DVI > /proc/acpi/video/VGA/DVID/info:known by bios: yes > /proc/acpi/video/VGA/DVID/state:state: 0x1d > /proc/acpi/video/VGA/DVID/state:query: 0x00 > /proc/acpi/video/VGA/HDMI/brightness:<not supported> > /proc/acpi/video/VGA/HDMI/EDID:<not supported> > /proc/acpi/video/VGA/HDMI/info:device_id: 0x7320 > /proc/acpi/video/VGA/HDMI/info:type: DVI > /proc/acpi/video/VGA/HDMI/info:known by bios: yes > /proc/acpi/video/VGA/HDMI/state:state: 0x1d > /proc/acpi/video/VGA/HDMI/state:query: 0x00 > /proc/acpi/video/VGA/LCDD/brightness:levels: 100 91 86 81 76 70 65 60 > 55 50 45 40 35 30 25 20 > /proc/acpi/video/VGA/LCDD/brightness:current: 86 > /proc/acpi/video/VGA/LCDD/EDID:<not supported> > /proc/acpi/video/VGA/LCDD/info:device_id: 0x0410 > /proc/acpi/video/VGA/LCDD/info:type: LCD > /proc/acpi/video/VGA/LCDD/info:known by bios: yes > /proc/acpi/video/VGA/LCDD/state:state: 0x1d > /proc/acpi/video/VGA/LCDD/state:query: 0x00 > > > I will try the patch as soon as I can, and get back to you. > I've now tried the patch and can confirm that it fixes the problem. Well, almost; I'm now having the same issue reported in comment 8, http://bugzilla.kernel.org/show_bug.cgi?id=12037#c8. But that, I guess, is a whole other thing. Thanks for this one, though! Will the patch be part of the 2.6.28 final release? Regards, Khash. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
