From: Jesse Barnes Subject: Re: Screen not turned on in kernel 2.6.35 Date: Mon, 9 Aug 2010 11:19:43 -0700 Message-ID: <20100809111943.5491f546@virtuousgeek.org> References: <20100807180932.GA4233@CORE-T7200> <20100809093907.0b6f7bab@virtuousgeek.org> <1281377339.17843.1373.camel@atropine> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by gabe.freedesktop.org (Postfix) with SMTP id 1F95B9E8E2 for ; Mon, 9 Aug 2010 11:19:48 -0700 (PDT) In-Reply-To: <1281377339.17843.1373.camel@atropine> 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: Adam Jackson Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Mon, 09 Aug 2010 14:08:59 -0400 Adam Jackson wrote: > On Mon, 2010-08-09 at 09:39 -0700, Jesse Barnes wrote: > > On Sat, 7 Aug 2010 20:09:32 +0200 Paul Neumann wrote: > > > i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment) > > > [drm] failed to find VBIOS tables > > > [drm] initialized overlay support > > > No connectors reported connected with modes > > > [drm] Cannot find any crtc or sizes - going 1024x768 > > > Console: switching to colour frame buffer device 128x48 > > > > > > and xrandr shows > > > > > > Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 > > > VGA1 disconnected (normal left inverted right x axis y axis) > > > DVI1 disconnected (normal left inverted right x axis y axis) > > > > Can you file a bug for this at bugs.freedesktop.org so it doesn't get > > lost? > > > > Adam's commit looks ok in general, but maybe your VBIOS is lying to us > > in this case? > > It's not that it's lying, it's that we don't _have_ one. The "BAR 6" > message is the PCI layer telling us there's no space for the VBIOS. Oops missed that, yeah it would cause problems unless we could get at the shadow at 0xc0000. -- Jesse Barnes, Intel Open Source Technology Center