Created attachment 95530 [details] log files After booting the screen on my Samsung ATIV 940x3g Ultrabook with qhd+ display remains most of the time off. Usually two or three reboots solve this for one session and once the desktop is up there are usually no Problems. However having to reboot several times to get there is not convenient. The OS is standard Ubuntu 13.10 up-to-date (10.3.2014) The graphic package versions are: ii intel-gpu-tools 1.5-0intel2 amd64 tools for debugging the Intel graphics driver ii intel-linux-graphics-installer 1.0.4-0intel1 amd64 Intel graphics drivers update utility ii libdrm-intel1:amd64 2.4.49-2 amd64 Userspace interface to intel-specific kernel DRM services -- runtime ii libdrm-intel1:i386 2.4.49-2 i386 Userspace interface to intel-specific kernel DRM services -- runtime ii libva-intel-vaapi-driver 1.2.2-1 all VAAPI driver for Intel G45 & HD Graphics family (transitional package) ii xserver-xorg-video-intel 2:2.99.907-0ubuntu1 amd64 X.Org X server -- Intel i8xx, i9xx display driver Linux version 3.11.0-18-generic (buildd@toyol) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ) #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 The CPU is: model name : Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz In the attachement are the follwoing logs: xrandr dmesg intel_reg_dumper Xorg.0.log The logs were generated when Ubuntu booted up nicely If required I can make a Video on the bootup problem and upload it.
Can you provide the log files for a bad boot? I presume the attached is for a working boot since there are no errors/warnings and everything appears happy even if using 1920x1080 rather than 3200x1800.
Created attachment 95572 [details] log file dmesg
Created attachment 95573 [details] intel reg dumper failing boot (display off)
Created attachment 95574 [details] Xorg log from failing boot
Hello Chris, thanks for looking into this so quickly. I logged in via ssh from an other machine and created the log files while the screen remains blank. Sometimes pressing CTRL+ALT+F1 works to get into the console and if lucky pressing CTRL+ALT+F7 afterwards might work to get a desktop. I am not using QHD+ resolution as the performance is not good. On the previous installed OS (Windows 8) it seems more reactive but thats another thing.
Hmm, nothing obvious. A silent training issue? FDI link error?
Hello developers, can I help somehow? I could also give you a temorary ssh access to the labtop.
I do experience the same problem as far as I can tell. xrandr -d :0.0 --output DP1 --off; xrandr -d :0.0 --output DP1 --rotate left --auto reproduce the problem 50% of the time. I am using Ubuntu 12.04.4 uname -r 3.11.0-15-generic tested with Ubuntu 13.04 and 13.10 same problem There is no trace of error in dmesg, xorg.log For xrandr the display appear to be working. This is not a backlight error as the backlight is not handle by the motherboard. I should add that the eDP is converted to LVDS. intel_reg_dumper is not working for some reason "Couldn't map MMIO region: Resource temporarily unavailable" and can not manage to compile it due to depandancy error. However I can attached some log file is desired and/or test with a more recent Ubuntu version where intel_reg_dumper is working
Forgot to add that the problem is also visible at boot time (plymooth) and when I switch to a text console (can be blank too) and coming back to X
@Xavier: Do you also have a Ultrabook from Samsung's ATIV 940 seriea? I am wondering why there are not more people having this issue.
No, I am using a com express board ESMQM77 http://www.avalue.com.tw/en/product/detail.aspx?ccid=2&cid=8&id=15&zid=653 But I experience exactly the same problem, seems to work but the dislay remain off, no error in the log, same type of output than you.
In my case, the hardware is probably to blame as I just discovered the same behaviour on Windows 7
Please re-test running current drm-intel-nightly branch from http://cgit.freedesktop.org/drm-intel
Time out after Jani last enquiry. Please do re-open if the bug still happens.
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.