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://freedesktop.org/bugzilla/show_bug.cgi?id=1786
--- Additional Comments From [EMAIL PROTECTED] 2004-11-04 18:23 ---
Possible
Hello,
The PCI ID is already added in the DRM branch of r300_driver.
As for the AGP issues, I have no idea. Maybe they're related to the lockup,
maybe not.
cu,
Nicolai
I think the AGP issues *are* related to the lockup. I've just switched
sysloggers, and switched to CVS XServer (was using
http://bugme.osdl.org/show_bug.cgi?id=3708
Summary: build failure in drivers/char/drm/gamma_drv.c:42
(missing structure member in included headers)
Kernel Version: 2.6.9
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
http://bugme.osdl.org/show_bug.cgi?id=3708
--- Additional Comments From [EMAIL PROTECTED] 2004-11-06 02:27 ---
Created an attachment (id=3969)
-- (http://bugme.osdl.org/attachment.cgi?id=3969action=view)
.config file for kernel report (gzipped)
Sorry, didnt realize I could attach
Hi,
On Saturday 06 November 2004 10:09, Ben Skeggs wrote:
I think the AGP issues *are* related to the lockup. I've just switched
sysloggers, and switched to CVS XServer (was using release 6.8 before).
My previous problems still occurred, but I now seem to have a lot more
debugging
As long as the X server works and uses the ring buffer, that would point
towards a simple configuration problem. Perhaps you could post a log of
glxinfo with LIBGL_DEBUG=all and RADEON_DEBUG=all?
cu,
Nicolai
Hmm, I believe you may be right about the config problem, I'm not
sure why I
r300_dri.so needs to get linked against expat.
- ajax
Yup, that did the trick. Thankyou. Any thoughts as to why it wasn't
linked against expat when I built it the first time around?
Ben.
from glxinfo:
disabling 3D acceleration
name of display: :0.0
display: :0 screen: 0
direct rendering:
Am So, den 07.11.2004 schrieb Ben Skeggs um 2:01:
As long as the X server works and uses the ring buffer, that would point
towards a simple configuration problem. Perhaps you could post a log of
glxinfo with LIBGL_DEBUG=all and RADEON_DEBUG=all?
cu,
Nicolai
Hmm, I believe you may
On Saturday 06 November 2004 20:01, Ben Skeggs wrote:
As long as the X server works and uses the ring buffer, that would point
towards a simple configuration problem. Perhaps you could post a log of
glxinfo with LIBGL_DEBUG=all and RADEON_DEBUG=all?
cu,
Nicolai
Hmm, I believe you may be
So I'm trying to get the DRI working on DragonFlyBSD. Someone has
created a series of patches for Xorg 6.8.1 which get it to compile and
run on DragonFly. Direct Rendering gets enabled:
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(II)
On Sat, 06 Nov 2004 20:09:45 +1100, Ben Skeggs [EMAIL PROTECTED] wrote:
Hello,
The PCI ID is already added in the DRM branch of r300_driver.
As for the AGP issues, I have no idea. Maybe they're related to the lockup,
maybe not.
cu,
Nicolai
I think the AGP issues *are* related to
On Sat, 2004-11-06 at 12:25 +0100, Nicolai Haehnle wrote:
Okay, the new syslog has all the debug info. I notice the following line:
Nov 7 07:37:58 disoft-dc [drm:radeon_cp_init_ring_buffer] writeback test
failed
The Radeon DRM source code has a comment indicating that writeback doesn't
Owen Taylor wrote:
Over a last few days, I've been working on a tool to allow watching
a live view of the texture usage of a DRI application. I'm not going to
go into a lot of detail here - there is a more complete description at:
http://fishsoup.net/software/texturetop/
And an even more
http://bugme.osdl.org/show_bug.cgi?id=3708
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
|bugs.osdl.org
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://freedesktop.org/bugzilla/show_bug.cgi?id=1773
--- Additional Comments From [EMAIL PROTECTED] 2004-11-06 11:51 ---
(In reply
On Sat, 2004-11-06 at 18:11 +, Keith Whitwell wrote:
My questions would be:
- Is this interesting to anybody but me? It's been quite useful to me
so far in just the couple of hours I've had it working...
It's definitely interesting. Have you been using it to tune an
2 days ago, after CVS update, I realized I can't get accelerated rendering.
(II) RADEON(0): Direct rendering enabled
but:
OpenGL renderer string: Mesa GLX Indirect
I have correct radeon.ko loaded, everything setup correctly (when I recompile
older Mesa and copy r200_dri.so I have direct
Hi,
It's perhaps related to the problems I had a while ago while testing
Xorg CVS Mesa CVS together. r200_dri.so had unresolved symbols and I
fixed that with the patch from
http://marc.theaimsgroup.com/?l=dri-develm=109812433626328w=2
(replaced $(MESAX86BUILDDIR)unshared with
One of our developers who is working with a non-gcc compiler has asked
if we could convert __FUNCTION__ usage in the drm to __func__. __func__
has the benefits of being shorter, being c99, and still being just fine
for gcc 2.95. Any opposition?
--
Eric Anholt
On Sat, 2004-11-06 at 19:07 +0100, Jacek Popawski wrote:
2 days ago, after CVS update,
Which tree of which CVS repository?
I realized I can't get accelerated rendering.
(II) RADEON(0): Direct rendering enabled
but:
OpenGL renderer string: Mesa GLX Indirect
This means the problem is
Eric Anholt wrote:
One of our developers who is working with a non-gcc compiler has asked
if we could convert __FUNCTION__ usage in the drm to __func__. __func__
has the benefits of being shorter, being c99, and still being just fine
for gcc 2.95. Any opposition?
Most of linux-kernel still uses
On Sat, 2004-11-06 at 16:27, Randy.Dunlap wrote:
Eric Anholt wrote:
One of our developers who is working with a non-gcc compiler has asked
if we could convert __FUNCTION__ usage in the drm to __func__. __func__
has the benefits of being shorter, being c99, and still being just fine
for
On Sat, Nov 06, 2004 at 06:36:08PM -0500, Michel Dnzer wrote:
LIBGL_DEBUG=verbose glxinfo
give any hints?
Yes:
libGL: XF86DRIGetClientDriverName: 4.0.1 r200 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r200_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/r200_dri.so
23 matches
Mail list logo
