Created attachment 89178 [details] Hardware information In the last three weeks I've narrowed down the bug described in the subject through Ubuntu launchpad. My new Laptop (Acer Aspire V5-573G) with new Haswell CPU shows a black screen on reboot because the brightness is on zero level. I verified this behaviour with the latest mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ I have done the bisect process and tracked the bug down to the following commit. For explanation: good commit means: The laptop starts with display brightness on full power, but low(er) resolution and the Fn+ keys are not working bad commit 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 <paulo.r.zanoni@intel.com> 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 <paulo.r.zanoni@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> :040000 040000 f93a7761de2157a8be61f20ca9a5499264bb5c55 1fed098470278830f06b0bca1706f61ba231d38d M drivers For the full bug report and the additional hardware information please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239183 I've also searched the LKML and maybe this bug could be in conjunction with http://marc.info/?t=137837786100005&r=1&w=2
Link to mailing list thread: http://lists.freedesktop.org/archives/intel-gfx/2013-November/035949.html Next step: I will try the kernel from http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git as mentioned by Aaron and Jani on the mailing list.
Created attachment 89193 [details] dmesg output with 0xe grub flag
I've tested kernel branch http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git This works without a problem. The screen starts at full brightness and correct native resolution. Also fn+ keys are working. I submit the dmesg output as attachment. Hopefully I did it right because last time I did there was Grub 0.x ;) Should I test the second branch too? Anything else I can help with?
Nice, so indeed fixed with all the recent acpi hacks.
(In reply to comment #3) > I've tested kernel branch > http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git > > This works without a problem. The screen starts at full brightness and > correct native resolution. Also fn+ keys are working. > > I submit the dmesg output as attachment. Hopefully I did it right because > last time I did there was Grub 0.x ;) > > Should I test the second branch too? Anything else I can help with? This is sufficient, thank you! Aaron, what are the chances of getting the initial brightness BIOS bug workaround backported to stable kernels? The above is headed for 3.13 right?
No problem, I'am glad that I could help. I could stay on the branch kernel until it gets backported or until 3.13 :) Thanks for information!
(In reply to comment #5) > (In reply to comment #3) > > I've tested kernel branch > > http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git > > > > This works without a problem. The screen starts at full brightness and > > correct native resolution. Also fn+ keys are working. > > > > I submit the dmesg output as attachment. Hopefully I did it right because > > last time I did there was Grub 0.x ;) > > > > Should I test the second branch too? Anything else I can help with? > > This is sufficient, thank you! > > Aaron, what are the chances of getting the initial brightness BIOS bug > workaround backported to stable kernels? The above is headed for 3.13 right? Yes, and I've marked that commit with stable tag, manually backport may be necessary since there are a lot of other commits for ACPI video in between.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.