From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 65576] New: [NV11] no EGL with nouveau_vieux_dri - no DRI_IMAGE
Date: Sun, 09 Jun 2013 16:56:05 +0000 [thread overview]
Message-ID: <bug-65576-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2173 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65576
Priority: medium
Bug ID: 65576
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [NV11] no EGL with nouveau_vieux_dri - no DRI_IMAGE
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: chris-Tc38MJj1weLQT0dZR+AlfA@public.gmane.org
Hardware: x86 (IA32)
Status: NEW
Version: git
Component: Drivers/DRI/nouveau
Product: Mesa
If I try and run any EGL program using the egl_dri2 driver, I get errors about
EGL_IMAGE. eg:
$ EGL_LOG_LEVEL=debug src/egl/opengl/eglinfo
libEGL debug: Native platform type: x11 (build-time configuration)
libEGL debug: EGL search path is /usr/lib/egl
libEGL debug: added egl_dri2 to module array
libEGL debug: added egl_glx to module array
libEGL debug: DRI2: dlopen(/usr/lib/dri/nouveau_vieux_dri.so)
libEGL debug: DRI2: found extension `DRI_Core'
libEGL info: DRI2: found extension DRI_Core version 1
libEGL debug: DRI2: found extension `DRI_DRI2'
libEGL info: DRI2: found extension DRI_DRI2 version 3
libEGL debug: DRI2: found extension `DRI2_Flush'
libEGL info: DRI2: found extension DRI2_Flush version 3
libEGL debug: DRI2: found extension `DRI_TexBuffer'
libEGL info: DRI2: found extension DRI_TexBuffer version 2
libEGL debug: DRI2: found extension `DRI_CONFIG_QUERY'
libEGL fatal: DRI2: did not find extension DRI_IMAGE version 1
I'm running latest git kernel, drm, mesa, xf86-video-nouveau & mesa/demos.
Everything else from Fedora 18. My card is an NV11 [GeForce2 Go].
Desktop GL works at least a little (glxgears works). I do have problems with
slow rendering in some programs with the nouveau X driver which don't occur
with the modesetting X driver (eg: rectangle selection animation in GIMP causes
a big slow down), but the desktop is basically functional.
Ultimately, I'm trying to get wayland/weston working on my ancient hardware to
see if it's a feasible proposition. Functioning EGL is the current hurdle.
Chris.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3427 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2013-06-09 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 16:56 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-65576-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-06-09 17:44 ` [Bug 65576] [NV11] no EGL with nouveau_vieux_dri - no DRI_IMAGE bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-13 5:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-13 5:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:38 ` 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-65576-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.