From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: Sandy Bridge (i7/H67) and connected screens Date: Fri, 04 Mar 2011 17:47:43 +0000 Message-ID: <1bdc18$jp5hb6@fmsmga002.fm.intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTP id 5C3439E79C for ; Fri, 4 Mar 2011 09:47:46 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Robert Kaiser , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Fri, 04 Mar 2011 18:20:16 +0100, Robert Kaiser wrote: > Is this a driver, configuration or even hardware problem? How can I find > out? Can I force the kernel or X to assume that screens are connected? Let's start by looking at the dmesg and Xorg.log and then determine what's wrong. If you add drm.debug=0xe to your grub kernel parameters, so much the better. Thanks, -Chris -- Chris Wilson, Intel Open Source Technology Centre