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
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
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
The original posting is below. Since then, I have disabled the driver,
since it always locks within 5 minutes of starting X.org 6.8.0.
Also, to answer a previous question, the r300 GL demo looks great, but
the triangle demo does not. It comes out shifted and with some garbage.
However, the
Hi,
On Friday 05 November 2004 23:12, Pat Suwalski wrote:
[snip]
I am running the following system:
- AMD 64 fx-51
I'm afraid that this is a very likely culprit, assuming you're running in 64
bit mode. The trouble is that parts of the DRM interface and also some of
the code interfacing the
10 matches
Mail list logo
