From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 11918] New: drmMap of framebuffer failed
Date: Thu, 9 Aug 2007 10:17:52 -0700 (PDT) [thread overview]
Message-ID: <bug-11918-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=11918
Summary: drmMap of framebuffer failed
Product: Mesa
Version: CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: pmandin-/BqsFWbVIFRWk0Htik3J/w@public.gmane.org
With latest drm changes (0.0.10 revision), glxgears (and maybe other GL apps)
fails to initialize nouveau dri:
libGL error: drmMap of framebuffer failed (Invalid argument)
libGL error: reverting to (slow) indirect rendering
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-08-09 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 17:17 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-11918-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2007-08-09 18:45 ` [Bug 11918] drmMap of framebuffer failed bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-08-09 19:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-08-09 20:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-08-09 22:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-08-11 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-07-05 17:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-07-07 13:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-08-24 19:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-11918-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.