8086:0a16 [Acer Aspire V5-573G] Black screen on boot due to low brightness setting

[bp0]

On boot, following the bios screen and grub screen to choose ubuntu, the screen goes completely black.

WORKAROUND: The fn-arrow keys can be used to turn the backlight up.

Commit bisect revealed:
70b12bb415463c1bd146b67c5fbf6784fd046ad9 is the first bad commit
commit 70b12bb415463c1bd146b67c5fbf6784fd046ad9
Author: Paulo Zanoni <email address hidden>
Date: Tue Nov 20 13:32:30 2012 -0200

    drm/i915: promote Haswell to full support

    Since it should be working a little bit better now.

    Signed-off-by: Paulo Zanoni <email address hidden>
    Signed-off-by: Daniel Vetter <email address hidden>

:040000 040000 f93a7761de2157a8be61f20ca9a5499264bb5c55 1fed098470278830f06b0bca1706f61ba231d38d M drivers

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: seker 1893 F.... pulseaudio
 /dev/snd/controlC1: seker 1893 F.... pulseaudio
Date: Sat Oct 12 19:08:14 2013
HibernationDevice: RESUME=UUID=cf48b287-c5f6-4b61-a5bd-3eac732c2f58
InstallationDate: Installed on 2013-08-31 (41 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130830)
MachineType: Acer Aspire V5-573G
MarkForUpload: True
ProcFB: 0 inteldrmfb1239183
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=9ec81638-697e-4b52-b175-0ab53a2518d6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Dazzle_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.20:bd08/29/2013:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-573G
dmi.product.version: TBD by OEM
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc5-saucy/

[bp0 (bullet-proof-0)]

I've tested 3.12.0-999-generic using the instructions at the link and the bug is still there, so added the exists-upstream tag.

[penalvch (penalvch)]

bp0, could you please test exactly http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc5-saucy/ (not the daily folder or some other kernel) and advise if this is reproducible?

[bp0 (bullet-proof-0)]

I've now tested the rc5-saucy kernel, and the problem is still there.

[penalvch (penalvch)]

bp0, the latest kernel is now http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/ could you please test this and advise to the results?

[bp0 (bullet-proof-0)]

Same problem with rc6-saucy kernel downloaded from the link in post #7 above.

[penalvch (penalvch)]

bp0, did this problem not occur in a release prior to Saucy?

[bp0 (bullet-proof-0)]

My computer is new and I had some difficulty installing 13.04 so went straight to 13.10 alpha - afraid I don't know if the bug occurred beforehand.

[penalvch (penalvch)]

bp0, for regression testing purposes, could you please test Precise via http://releases.ubuntu.com/precise/ and advised to the results?

[bp0 (bullet-proof-0)]

Same problem under 12.04.3, run under LiveUSB

[penalvch (penalvch)]

bp0, for regression testing purposes, could you please test for this in Lucid via http://old-releases.ubuntu.com/releases/lucid/ ?

[bp0 (bullet-proof-0)]

The backlight works under Lucid!

[penalvch (penalvch)]

bp0, the next step is to bisect from Lucid to Precise, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Mario Kleinsasser (m4r10k)]

I've tested it by booting the live images (desktop edtion) .

13.10 -> not working (just to test, if I can reproduce the failure with live boot)
11.04 -> working

I'am currently downloading 10.10 (Maverick Meerkat).

[Mario Kleinsasser (m4r10k)]

Sorry, I meant 11.10 (Oneiric Ocelot) :)
11.10 -> not working, no graphic display is shown up in general. (under LiveUSB) I'am not shure if this is the same issue.

Therefore, bp0 can you please verify that 11.10 is not working on your hardware too?

[bp0 (bullet-proof-0)]

For me, 11.10 doesn't boot to x, but to a terminal. Using the 'startx' command brings up a normal ubuntu session. The backlight works in this version, but the brightness buttons don't and I couldn't immediately see where to change brightness so couldn't test if the screen just had one brightness setting or if it is controllable.

I guess kernel bisecting would need to start from 11.10 then, but I have to admit that I don't know how to do this, especially from a liveUSB.

[Mario Kleinsasser (m4r10k)]

I've already filed a report at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245424, therefore my hardware is tracked.
I'am participating on this bug number, because it seems like to be the one with the most activity.

I've build Oneiric and Precise Kernels on my Laptop the last days. For test purpose I took on of the oldest and the newest Ubuntu-* commit of the branches. All of them (expect the oldest Precise commit, that causes no root device found) are booting my laptop with full brightness.

Therefore I'am not shure where the behavior resides. I'am downloading Quantal Ubuntu kernel git now to test ahead. But this takes a lot of time.

Tested kernels so far:
3.0.0-13.22 (no root device found)
3.0.0-20.34 (full brigthness, wrong resolution)
3.0.0-32.51 (full brigthness, wrong resolution)
3.1.0-2.3 (full brigthness, wrong resolution)
3.2.0-56.86 (full brigthness, wrong resolution)

[penalvch (penalvch)]

bp0, one would not do a bisection from a live environment. Instead, one would follow https://wiki.ubuntu.com/Kernel/KernelBisection .

[Mario Kleinsasser (m4r10k)]

@Christopher M. Penalver: Thanks for closing duplicate bug. I already did the BIOS Update https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1224415

After additional tests (bisecting main versions), I have more information now. I tested all the kernels I build with Kubuntu 13.10.
Current status is:

Kernel Quantal Quetzal 3.5.0_43.66: Working perfect, full brightness at startup and Fn+ function keys working (commit 7772e0d UBUNTU: Ubuntu-3.5.0-43.66)

Kernel Raring Ringtail 3.8.0.33: NOT Working, zero brightness at startup, backlight working, Fn+ function keys working to raise brightness. (commit dd8a621 UBUNTU: Ubuntu-3.8.0-33.48)

I'am going to bisect between those to now, but again, my laptop isn't that fast ... :), this might take some days. Or anyone with better ideas?

[Mario Kleinsasser (m4r10k)]

I've tried Kernel Raring Ringtail commit 1161744, 3.8.0-0.1. This kernel shows the same behaviour as the latest in Raring Ringtail. As mentioned before Quantal Quetzal 3.5.0_43.66 ist working. Therefore I need somethin in between to test.

How should I proceed? Is there a Ubuntu git for kernel between 3.5.* and 3.7.* or should I continue to test with mainstream? Any information would be appreciated!

[penalvch (penalvch)]

Mario Kleinsasser, one may find 3.7.x kernels from https://launchpad.net/ubuntu/raring/+source/linux . If this doesn't narrow it down, you may want to switch to git bisecting and building Ubuntu kernel commits, or bisecting the mainline kernel. Instructions on both are in https://wiki.ubuntu.com/Kernel/KernelBisection .

[Mario Kleinsasser (m4r10k)]

Thank you for your information. I've tried the kernels up to 3.7.0-7.15 which I guess is the latest kernel before 3.8.0-0.1 as of this list -> https://launchpad.net/ubuntu/raring/+source/linux

The problem is, that the lates 3.7 is not showing the problem. The resolution isn't correct and the fn+ is not working, but the brightness is at full power.

The 3.8.0-0.1 kernel show the black startup screen. How should I proceed? Any suggestions. Maybe it is time to post at LKML?

[penalvch (penalvch)]

Mario Kleinsasser, now that it is known 3.7.0-7.15 is the latest kernel tested not to show the problem, and 3.8.0-0.1 is, the next step is to commit bisect between these two kernel versions (not test different kernel version but different commit versions) following https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernel_versions .

Posting to LKML would be largely a waste of time at this point because the commit causing the regression is not known.

[Mario Kleinsasser (m4r10k)]

Oh, yes, yes, but the Ubuntu-3.7.0-7.15 commit istn't in the Raring git and the Ubuntu-3.8.0-0.1 commit is not in the Quantal git. Thats my problem or maybe I don't understand something. To bisect commits, I need those commits inside one git, right?

The benefit of git bisect is to simplify the process of the binary search inside the commits and that is what comes handy in such situations - but how to do this with different releases?

[penalvch (penalvch)]

Mario Kleinsasser :
>"...Ubuntu-3.7.0-7.15 commit istn't in the Raring git..."

This is incorrect. The Raring git would include mostly everything in the Quantal git, plus the commits that make Raring, Raring:
http://kernel.ubuntu.com/git?p=ubuntu%2Fubuntu-raring.git&a=search&h=HEAD&st=grep&s=3.7.0-7.15

[Mario Kleinsasser (m4r10k)]

Ah, I'am sorry, I've greped for Ubuntu-xyz -> my fault, but that was my missing link :) (and I only used --oneline)
Now I know how to search the diff log and how to find the commit I need. I'am going to try bisect.Thanks!

[Mario Kleinsasser (m4r10k)]

Bisect done. For explanation:

good means: The laptop starts with display brightness on full power, but low(er) resolution and the Fn+ keys are not working

bad means: The laptop starts with black display (0 brightness), Fn+ keys are working and you can level up the brightness trough the Fn+ keys. The resolution is the native LCD hardware display resolution

Bisect output:

70b12bb415463c1bd146b67c5fbf6784fd046ad9 is the first bad commit
commit 70b12bb415463c1bd146b67c5fbf6784fd046ad9
Author: Paulo Zanoni <email address hidden>
Date: Tue Nov 20 13:32:30 2012 -0200

    drm/i915: promote Haswell to full support

    Since it should be working a little bit better now.

    Signed-off-by: Paulo Zanoni <email address hidden>
    Signed-off-by: Daniel Vetter <email address hidden>

:040000 040000 f93a7761de2157a8be61f20ca9a5499264bb5c55 1fed098470278830f06b0bca1706f61ba231d38d M drivers

Anything I could/should to beyond this point?

[penalvch (penalvch)]

bp0 / Mario Kleinsasser, the issue you are reporting is an upstream one. Could one of you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Please provide a direct URL to your post once you have made it so that it may be tracked.

Thank you for your understanding.

[Mario Kleinsasser (m4r10k)]

Information from freedesktop.org mailing list is, that this seems to be a firmware bug.

Bug filed as https://bugs.freedesktop.org/show_bug.cgi?id=71596

Mailinglist thread is http://lists.freedesktop.org/archives/intel-gfx/2013-November/035949.html

[Mario Kleinsasser (m4r10k)]

This "initial brightness zero bug" is an ACPI problem and a work around fix patch is headed for kernel 3.13. Chances are good that it gets backported to kernel 3.12. Details at: https://bugs.freedesktop.org/show_bug.cgi?id=71596

I think Bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1224415 is a duplicate of this one too.

[Mario Kleinsasser (m4r10k)]

For your information. The bugs for the Acer Aspire V5-573g are fixed. Brightness works correct, shutdown works and even suspend to ram is functional now. Tested with mainline Ubuntu 3.13.(trusty) kernel through Kubuntu 13.10. (https://wiki.ubuntu.com/Kernel/MainlineBuilds).

I guess this bug could be cloused now.

[AceLan Kao (acelankao)]

Hi Mario,
I'm just curious, with the 3.13 kernel, does the lowest brightness level turns off the screen?

[Mario Kleinsasser (m4r10k)]

Hi Kao,

I apologize but I have not installed *ubuntu anymore. But I can confirm, that with the distribution I have currently running on this laptop, the display goes off if I switch down to the lowest level with the fn-keys. Currently running Kernel 3.13.5.

Hope this helps.

[AceLan Kao (acelankao)]

Hi Mario,
Thanks for your response, that's very useful for me as we're encountering another backlight issue.
BTW, I'm closing this issue as it's been fix in 3.13 kernel.