Created attachment 37756 [details] drm.debug=4 dmesg I have a machine with only DVI output, it is a mini pc made by Dell. When enabling the KMS intel driver i915 as soon as it starts the framebuffer the screen goes blank and nothing further is displayed, although the machine continues to function as normal.
I realise this isn't and xorg bug but no place looked appropriate so I hoped someone would move it to it's correct home.
[07:11] <airlied> r4tune: can you try booting with video=DVI-I-1:d [07:12] <r4tune> sure sorry was afk [07:13] <r4tune> that fixed it
Hmm, can you update to the latest Linus tree, or Dave Airlie's drm-core-next as that contains some useful information such as the names of the various connectors and encoders whilst setting up the mode. Also if you can grab the drm.debug=4 dmesg both with and without video=DVI-I-1:d, that would be useful. Am I correct in thinking that you only have a DVI-I conntected with a false detection on VGA?
The issue appears to be that we setup the DVO [DVI connector] and the CRT [VGA connector] on the same i2c bus and so end up hooking both connectors to the sil164 external chip + single connector. FAIL.
commit 7511af860b1232a8a0a0df23b5750cab727fba18 Author: David Müller <d.mueller@elsoft.ch> Date: Thu Jan 6 12:29:32 2011 +0000 drm/i915/crt: Check for a analog monitor in case of DVI-I Since Linux 2.6.36 the digital output on my system (855GME + DVI-I) is not working any longer. The analog output is always activated regardless of the type of monitor attached. The culprit seems to be intel_crt_detect_ddc(), which returns true as soon as an ACK from the EDID device is received. Obviously this approach does not work with DVI-I where the analog and digital outputs share a common DDC bus. In a similar manner to the shared DDC wire, ala the "Mac Mini Hack", we need an additional check to make sure that there really is an analog device attached to the DDC. Signed-off-by: David Müller <d.mueller@elsoft.ch> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
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.