<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW mobile Acer notebook] eDP can't light up in boot to text mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=65995#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW mobile Acer notebook] eDP can't light up in boot to text mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=65995">bug 65995</a> from <a class="email" href="mailto:enabfluw@gmail.com" title="tb <enabfluw@gmail.com>"> tb</a> <pre>This all sounds remarkably similar to my issue on the new Acer Aspire S7-392 with the Haswell HD 4400 and a 1920x1080 touchscreen--I assume it's IPS, it's really nice-looking. I've been able to get it to run every resolution but its native one when X starts. It will display on boot on these kernels: 1. <a href="http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/">http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/</a> (but doesn't work on rc2) 2. <a href="http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2013-08-08-saucy/">http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2013-08-08-saucy/</a> (but doesn't work on the 2013-08-09 kernel) So something in those time periods regressed. I'm not sure what kernel that "drm-next" one is, because the Ubuntu site also has a "drm-intel-next" folder. No idea what they're doing. I partially lied. It will display fine on its native resolution in a particular case: if you boot up into the black screen on any "non-working" kernel, like 3.11-rc5 or -rc6, you can log in and xrandr to a different resolution and it turns on just fine--but you must switch to tty, then back to X for the backlight to turn on. I can open a new bug if this seems different to you guys. I'm happy to provide whatever logs are required here.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>