Re: PROBLEM: Acer D255E Backlight out for 10 seconds with ACPI
From: joeyli <jlee@suse.com>
Date: 2012-10-02 04:46:28
於 六,2012-09-29 於 22:42 -0400,Dan 提到:
On Fri, Sep 28, 2012 at 7:58 PM, joeyli [off-list ref] wrote:quoted
Hi Dan, 於 四,2012-09-27 於 14:09 -0400,Dan 提到:quoted
On Wed, Sep 26, 2012 at 7:19 PM, joeyli [off-list ref] wrote:quoted
於 三,2012-09-26 於 16:48 -0400,Dan 提到:quoted
Hello, Apologies if this was sent to the wrong place. With an Acer AOD255E netbook, the backlight goes out for exactly 10 seconds before returning while booting. This is a backlight issue and not KMS, as I can shine a flashlight at the screen and still see boot text scrolling. With "acpi=off" appended to the kernel line, this no longer occurs (Fn key backlight controls still work with this appended). With everyIt's a clue for that problem is happen in acpi, but sometimes the Fn key on notebook is changed by BIOS, need check DSDT.quoted
quoted
quoted
other acpi option I have tried, this still occurs though. This includes "acpi_backlight" and "acpi_display_output". With "acpi_backlight=vendor" the entry in /sys/class/backlight changes from acpi_video0 to acer_wmi, but backlight still goes out. Otherwise backlight works correctly.Could you please try this kernel parameter? video.use_bios_initial_backlight=0 Thanks Joey LeeSame results with that kernel parameter applied.This parameter works when _BQC used indexed value but not direct use brightness value. One possible thing is BIOS really set the initial index or brightness level to lowest level.quoted
Just to make it clear when this is happening: The BIOS screen and bootloader work fine. This occurs during the boot process while the systemd text is scrolling (or with the splash screen in the case of Ubuntu). I have not been able to pin down any event during the boot process that triggers it. It seems to be based on time after the kernel loads. I can tell by the difference booting from a HDD vs a SSD. With a HDD, it will occur earlier in the process (close to the time init is called) since booting takes longer. With an SSD, the backlight goes out close to the time the login screen appears. Once the backlight is out, it will stay out for exactly 10 seconds before returning no matter what is on the screen.What's your value of max brightness? Please run: # cat /sys/class/backlight/acpi_video0/max_brightness Please also manually change brightness level after your system boot finished, and look at does it changed or have problem like reversed? # echo 10 > /sys/class/backlight/acpi_video0/brightness And, Please attached your acpidump: # acpidump > acpidump.dat Thanks Joey Lee# cat /sys/class/backlight/acpi_video0/max_brightness 9 Echoing values into brightness works as expected. Higher values increase the brightness, lower values descrease it. Echoing 0 into it results in a dim screen, but not a blank one. I should also mention my findings are consistent with this person's: https://bbs.archlinux.org/viewtopic.php?pid=941871#p941871 He found that the brightness level in /sys/class/backlight/acpi_video0/brightness remains the same during the blackout by echoing it out at random times during the boot process (I had found this out awhile back but failed to remember and mention it in the original message. Sorry about that!). Acpidump is attached.
I traced your DSDT at this morning, didn't see problem in _BCL, _BCM and
_BQC.
Per DSDT, the _BQC on this machine used brightness value but not index,
so 'video.use_bios_initial_backlight=0' should works to you for set the
backlight to max_level when acpi/video driver loaded.
And, the value of max_level in package of _BCL is 100, there have no 0
value in level list:
Method (_BCL, 0, NotSerialized)
{
Return (Package (0x0C)
{
0x46, /* level on AC */
0x28, /* level on Battery */
0x0A, /* 10 */
0x14, /* 20 */
0x1E,
0x28,
0x32,
0x3C,
0x46,
0x50,
0x5A,
0x64 /* 100 */
That strange for 'video.use_bios_initial_backlight=0' doesn't work to
you for set the backlight level to maximum.
Could you please share the acpi debug log? Please add the following
kernel parameter when system boot. Please also check the kernel config
need CONFIG_ACPI_DEBUG=y:
acpi.debug_level=0x0000000F acpi.debug_layer=0xffffffff log_buf_len=5M
Please attached on your dmesg or boot message after system boot finished. Hope we
can find any hint from acpi debug log.
Thanks a lot!
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html