From: "Jan Dittmer" <jdi@l4x.org>
To: "Jesse Barnes" <jbarnes@virtuousgeek.org>
Cc: "Dave Airlie" <airlied@gmail.com>,
"Diego Calleja" <diegocg@gmail.com>,
linux-kernel@vger.kernel.org, eric.anholt@intel.com,
airlied@linux.ie
Subject: Re: intel kms "Failed to allocate space for kernel memory manager"
Date: Mon, 12 Jan 2009 23:08:03 +0100 [thread overview]
Message-ID: <621d098f0901121408y2cf8c2c9y2a6a5cc77ea8e8f5@mail.gmail.com> (raw)
In-Reply-To: <200901121353.40270.jbarnes@virtuousgeek.org>
On Mon, Jan 12, 2009 at 10:53 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>> 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. :)
With the patches againg 29-rc1 from here
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=3a03ac1a0223f779a3de313523408ddb099e5679;hp=dc1336ff4fe08ae7cfe8301bfd7f0b2cfd31d20a
and here
http://groups.google.com/group/linux.kernel/msg/26aa0471cfb54b06?dmode=source&output=gplain
at least glxinfo works.
Anyways thanks for your help, time to get some sleep,
Jan
next prev parent reply other threads:[~2009-01-12 22:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <621d098f0901110546p2b99a525k5de54e37fa181197@mail.gmail.com>
2009-01-11 13:51 ` Jan Dittmer
2009-01-11 21:21 ` Diego Calleja
2009-01-11 21:39 ` Dave Airlie
2009-01-11 22:04 ` Diego Calleja
2009-01-12 7:42 ` Jan Dittmer
2009-01-12 8:04 ` Dave Airlie
2009-01-12 8:37 ` Jan Dittmer
2009-01-12 17:56 ` Jesse Barnes
2009-01-12 18:30 ` Diego Calleja
2009-01-12 21:19 ` Jan Dittmer
2009-01-12 21:33 ` Jan Dittmer
2009-01-12 21:53 ` Jesse Barnes
2009-01-12 22:08 ` Jan Dittmer [this message]
2009-01-12 22:29 ` Jan Dittmer
2009-01-12 23:19 ` Jesse Barnes
2009-01-12 13:03 ` Olivier Galibert
2009-01-12 17:53 ` Jesse Barnes
2009-01-12 21:32 ` Olivier Galibert
2009-01-12 21:59 ` Jesse Barnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=621d098f0901121408y2cf8c2c9y2a6a5cc77ea8e8f5@mail.gmail.com \
--to=jdi@l4x.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=diegocg@gmail.com \
--cc=eric.anholt@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®