Something in the last week or two broke the r200 driver. After I cvs
update'ed and recompiled yesterday, I get this error:
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020
(EE)
Ronny V. Vindenes wrote:
Something in the last week or two broke the r200 driver. After I cvs
update'ed and recompiled yesterday, I get this error:
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP
On Thu, 2003-10-30 at 12:03, Keith Whitwell wrote:
Ronny V. Vindenes wrote:
Something in the last week or two broke the r200 driver. After I cvs
update'ed and recompiled yesterday, I get this error:
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed
Ronny V. Vindenes wrote:
Something in the last week or two broke the r200 driver. After I cvs
update'ed and recompiled yesterday, I get this error:
[...]
Card is 9000/128mb under linux 2.6.0-test9 (athlon64 running in pure
32bit mode) with an lcd connected to dvi.
just wanted to let you know that
Hopefully I'll have some time this weekend to look into this, what
files in the r200 client driver should I be looking at? Having looked
at the code I'm guessing r200_state. Scissor and cliprect stuff.
Although thinking about it more, there are probably more changes
required since I guess
On Thu, 2003-10-30 at 20:43, Ronny V. Vindenes wrote:
Card is 9000/128mb under linux 2.6.0-test9 (athlon64 running in pure
32bit mode) with an lcd connected to dvi.
Just checked latest DRI CVS with my radeon 9000 PCI, no errors. I know
it doesn't help but it might give you a better idea of
ok, should of mentioned, its with the r200 driver, and confirmed again
with the the cvs as of 30 mins ago.
glXSwapBuffers segs GL applications if DRI is NOT enabled.
Confirmed by recompiling glxgears with debugging and ran through gdb
(see previous emails)
On Fri, 31 Oct 2003 17:42:34 +1000
Chris Ison [EMAIL PROTECTED] wrote:
ok, should of mentioned, its with the r200 driver, and confirmed again
with the the cvs as of 30 mins ago.
glXSwapBuffers segs GL applications if DRI is NOT enabled.
Confirmed by recompiling glxgears with debugging and
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=704
--- Additional Comments From [EMAIL PROTECTED] 2003-30-10 18:08 ---
No. Sorry, I don't
Hmm, I can't reproduce this with my Radeon7500 and DRI disabled by not
loading module dri in XF86Config-4. Seeing a backtrace after the
segfault would be extremely helpful in locating the exact problem. Just
type bt at the gdb prompt after the segfault.
Regards,
Felix
bt just returns
Ronny V. Vindenes wrote:
Something in the last week or two broke the r200 driver. After I cvs
update'ed and recompiled yesterday, I get this error:
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP
Chris Ison wrote:
On Thu, 2003-10-30 at 17:08, Chris Ison wrote:
I'm wondering what happened to the full sw mode for 3d you could use
before when DRI wasn't enabled. Now GL apps just seg (including
glxgears) where a few months ago you could still run them without DRI
although very slow.
Further
On Fri, 2003-10-31 at 00:43, Roland Scheidegger wrote:
Ronny V. Vindenes wrote:
Something in the last week or two broke the r200 driver. After I cvs
update'ed and recompiled yesterday, I get this error:
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer
I'll take a look at fixing this in the radeon driver. What needs to be
done to play nice with the DRI?
Alex
--- Alan Hourihane [EMAIL PROTECTED] wrote:
On Thu, Oct 30, 2003 at 07:47:06AM -0600, Billy Biggs wrote:
Alan Hourihane ([EMAIL PROTECTED]):
Well, if someone else has a chip, or
I've actually already done it, but I'll probably leave it till after
XFree86 4.4.0.
Once 4.4.0 is out, I'll merge that into the DRI CVS and create a branch
for this work I've been doing on the radeon with regard to dynamic
allocation the DRI.
Alan.
On Thu, Oct 30, 2003 at 07:36:42AM -0800,
On Thu, Oct 30, 2003 at 10:59:41AM -0600, Billy Biggs wrote:
Alan Hourihane ([EMAIL PROTECTED]):
I've actually already done it, but I'll probably leave it till after
XFree86 4.4.0.
Regarding bug 830, does this mean my users can expect to sometimes hit
these situations where XVIDEO
manu wrote:
Hi all,
before I open a bug for that I would like to sort out things a bit.
Here is the story : I installed a MDK 9.2, the agpgart module seems to
be OK with my mobo (which has a nForce2 Ultra chipset), so I went on
and try to make 3D accel work for my Radeon 9200. Whereas all
manu wrote:
Le 30.10.2003 17:07:54, manu a écrit :
So I ran glxinfo see below which told me that Direct Rendering is not
enabled! This is crazy as you can check in the XFree log (file
attached).
Hope someone can tell me more about this, be it to file this directly
as a bug on bugzilla ;-)
Alan Hourihane ([EMAIL PROTECTED]):
I've actually already done it, but I'll probably leave it till after
XFree86 4.4.0.
Regarding bug 830, does this mean my users can expect to sometimes hit
these situations where XVIDEO apps can't run until they shut down a
large application like their web
19 matches
Mail list logo
