From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 32864] New: wayland "libEGL warning: failed to create DRM screen"
Date: Wed, 5 Jan 2011 17:25:59 -0800 (PST) [thread overview]
Message-ID: <bug-32864-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=32864
Summary: wayland "libEGL warning: failed to create DRM screen"
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: darxus-gf8W+JFHfRr/2OF+hy8yCA@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Running the wayland compositor used to give output including:
libEGL debug: searching for pipe module nouveau
libEGL debug: loaded /home/darxus/install/lib/egl/pipe_nouveau.so
But now instead of saying it loaded pipe_nouveau.so, it says:
libEGL warning: failed to create DRM screen
Git commit 6a102074bb30e44273e999ee8cdd2afbfbc4e333 works (last before
problem).
Git commit 997f84ff4efb62779a19f6bd0441cbae1b7bad70 has this problem.
I tried adding a bunch of prints to nouveau_drm_screen_create() in
src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c, none of them printed.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-01-06 1:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 1:25 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-32864-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-01-06 1:30 ` [Bug 32864] wayland "libEGL warning: failed to create DRM screen" bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-06 1:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-06 4:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-06 8:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-06 8:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07 4:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07 4:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07 4:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-08 19:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-08 20:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-08 20:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-08 21:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-08 22:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-08 23:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-08 23:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-09 0:06 ` 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-32864-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.