Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757565AbZALVxx (ORCPT ); Mon, 12 Jan 2009 16:53:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752488AbZALVxm (ORCPT ); Mon, 12 Jan 2009 16:53:42 -0500 Received: from outbound-mail-26.bluehost.com ([69.89.17.191]:35928 "HELO outbound-mail-26.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752247AbZALVxm (ORCPT ); Mon, 12 Jan 2009 16:53:42 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org; h=Received:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id:X-Identified-User; b=hb4oMys0Ac9lB8yRRcj+DcYHcK2d8Nilr78HLwGMsdULIFRqkfFnedJ36kWaJny2Fs88iqpPGoceVvGsjy2cNmtu35ppqADoL9od20eDB3sP4Z4meUcU02bpECMaJrt+; From: Jesse Barnes To: "Jan Dittmer" Subject: Re: intel kms "Failed to allocate space for kernel memory manager" Date: Mon, 12 Jan 2009 13:53:39 -0800 User-Agent: KMail/1.9.10 Cc: "Dave Airlie" , "Diego Calleja" , linux-kernel@vger.kernel.org, eric.anholt@iintel.com, airlied@linux.ie References: <621d098f0901110546p2b99a525k5de54e37fa181197@mail.gmail.com> <200901120956.31728.jbarnes@virtuousgeek.org> <621d098f0901121319j1be02f82j368250314664b997@mail.gmail.com> In-Reply-To: <621d098f0901121319j1be02f82j368250314664b997@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901121353.40270.jbarnes@virtuousgeek.org> X-Identified-User: {642:box128.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 75.111.27.49 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2296 Lines: 54 On Monday, January 12, 2009 1:19 pm Jan Dittmer wrote: > On Mon, Jan 12, 2009 at 6:56 PM, Jesse Barnes wrote: > > On Monday, January 12, 2009 12:37 am Jan Dittmer wrote: > >> On Mon, Jan 12, 2009 at 9:04 AM, Dave Airlie wrote: > >> > the latest git should work with kms on most chipsets, we are still > >> > chasing down some issues on some chipsets, > >> > >> So is there anything I can test to help you get it going on 'my' chipset > >> (GM965, Lenovo X300)? > > > > I do much of my testing on GM965, so you should be able to get it to work > > with the latest bits: > > - libdrm from git master of mesa/drm > > - mesa from git master of mesa/mesa > > - xf86-video-intel from git master > > - drm-intel-next from anholt's kernel tree > > (git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel) > > > > You'll need to use UXA as your AccelMethod. If you run into issues with > > the above, please file bugs (if you don't already see your issue filed) > > at bugs.freedesktop.org. > > Thanks, at least X starts now, though dri is still broken. Is there > any quick fix to: > > name of display: :0.0 > libGL: XF86DRIGetClientDriverName: 1.9.0 i965 (screen 0) > libGL: OpenDriver: trying /usr/local/lib/dri/i965_dri.so > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 4, (OK) > drmOpenByBusid: Searching for BusID pci:0000:00:02.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 4, (OK) > drmOpenByBusid: drmOpenMinor returns 4 > drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 > libGL error: drmMap of framebuffer failed (Resource temporarily > unavailable) libGL error: reverting to software direct rendering > > ? > This is with latest mesa git libGL. Any special compilation options for > mesa? Nope, not afaik. Are you sure UXA is enabled? And that Mesa was built against the same libdrm bits as your 2D driver? If so, then I guess it's time to file a bug. :) -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/