Bug 70282 - No display device detected on a Baytrail all-in-one machine.
Summary: No display device detected on a Baytrail all-in-one machine.
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-08 14:04 UTC by roberth
Modified: 2017-07-24 22:57 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg with drm.debug=0xe on 20131004 drm-intel-nightly (80.14 KB, text/plain)
2013-10-08 14:04 UTC, roberth 		no flags Details
Xorg.0.log (8.59 KB, text/plain)
2013-10-08 14:04 UTC, roberth 		no flags Details
lspci -vvnn (23.87 KB, text/plain)
2013-10-08 14:05 UTC, roberth 		no flags Details
View All

Description roberth 2013-10-08 14:04:31 UTC 
Created attachment 87282 [details]
dmesg with drm.debug=0xe on 20131004 drm-intel-nightly

After booting the internal display device is not detected by i915, the screen goes black after bios. drm.debug=0xe dmesg attached with more info.

-- chipset: Intel Corporation ValleyView Gen7 [8086:0f31]
-- system architecture: x86_64
-- Linux distribution: Ubuntu 12.04.2 and 13.10
-- libdrm 2.4.43
-- Kernel versions affected: 3.11-rc3, 3.11.2, 3.12-rc3, drm-intel-nightly from 20131004
-- xf86-video-intel: 2.21.15, 2.99.903 git snapshot from 20131001
Comment 1 roberth 2013-10-08 14:04:55 UTC 
Created attachment 87283 [details]
Xorg.0.log
Comment 2 roberth 2013-10-08 14:05:59 UTC 
Created attachment 87284 [details]
lspci -vvnn
Comment 3 Chris Wilson 2013-10-08 14:43:42 UTC 
For starters, your xserver is broken - it is not selecting a CompatOutput() for the headless case. The BIOS sets up a 1600x900 mode on DP1, but there is not EDID for that panel so we treat it as disconnected. We have no means for determining the native timings for that panel. So either the NAK we get for the EDID probe is wrong, or the manufacturer skimped by hiding all the information in the BIOS rather than the panel firmware. If that is so, all you can do is hope for fastboot.
Comment 4 Chris Wilson 2013-11-01 11:41:06 UTC 
This is probably related to #71051
Comment 5 Jesse Barnes 2013-11-17 21:54:29 UTC 
Still an issue now that #71051 is fixed?
Comment 6 roberth 2014-01-10 14:47:02 UTC 
I don't have access to the machine to test anymore so closing this one.

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.