Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2797
Summary: DRI with r300 doesn't work with Crystal Space
Product: DRI
Version: XOrg CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: libGL
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: [EMAIL PROTECTED]
DRI works great with some programs but not with others. Here's the log from
running tuxracer.
[EMAIL PROTECTED]:/opt/Xorg-6.8$ LIBGL_DEBUG=verbose tuxracer
Tux Racer 0.61 -- a Sunspire Studios Production (http://www.sunspirestudios.com)
(c) 1999-2000 Jasmin F. Patry <[EMAIL PROTECTED]>
"Tux Racer" is a trademark of Jasmin F. Patry
Tux Racer comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions.
See http://www.gnu.org/copyleft/gpl.html for details.
libGL: XF86DRIGetClientDriverName: 4.0.1 r300 (screen 0)
libGL: OpenDriver: trying /opt/Xorg-6.8/lib/modules/dri/r300_dri.so
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
The log continues on from there.. it works great, in other words, and I can play
hardware-accelerated tuxracer.
Here's what happens if I try to run Crystal Space:
[EMAIL PROTECTED]:~/software/CS$ LIBGL_DEBUG=verbose ./walktest
NOTIFY: Could not get sound driver
libGL: XF86DRIGetClientDriverName: 4.0.1 r300 (screen 0)
libGL: OpenDriver: trying /opt/Xorg-6.8/lib/modules/dri/r300_dri.so
libGL error: dlopen /opt/Xorg-6.8/lib/modules/dri/r300_dri.so failed
(/opt/Xorg-6.8/lib/modules/dri/r300_dri.so: undefined symbol: glXGetProcAddress)
libGL error: unable to find driver: r300_dri.so
Indirect rendering may indicate a flawed OpenGL setup if you run on a local
X server.
At first I thought this was an error from compiling against the wrong headers or
libraries, but recompiling doesn't make it go away. My next thought was that
this happened because walktest wasn't directly linked with libGL, but rather
uses some kind of dlopen magic to talk to a plugin that is linked against libGL.
So I linked walktest manually against libGL, which made this error went away but
then it wouldn't render anything, only draw a totally back window.
The CS people suggest this might be due to the experimentalness of the r300
driver. Any ideas?
Ethan
--
Configure bugmail: https://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.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
