Aapo Tahkola wrote:
Missed these:
*********************************WARN_ONCE*********************************
File radeon_mm.c function radeon_mm_alloc line 182
Ran out of GART memory!
Please consider adjusting GARTSize option.
***************************************************************************
*********************************WARN_ONCE*********************************
File r300_ioctl.c function r300RefillCurrentDmaRegion line 629
Whops! Dont know how to evict VBOs yet.
***************************************************************************
Put:
Option "GARTSize" "64"
into "Device" section of xorg.conf and it should run just fine.
I admit that r300 driver shouldnt quit like that and I'm working on it.
That doesn't change the fact that not adjusting GARTSize will make r300 driver
run at lowered performance.
You are right, I saw the backtrace and looked no further.
ut2004(demo):
Texture corruption and eventual lockup.
The only hope on tracking down problem with your card is to be able to isolate
it somehow.
Apps like ut2k4 & q3 are pretty complicated beasts to debug...
Good start would be to determine if the textures really get corrupted or if its
a symptom of something else.
Mesa demos/tests would be good for this sort of thing but anything with less
than 1k of code should do.
I have been using Mesa demos/tests, NeHe, and some Humus demos. Do you
know of any more demos/tests?
Also would you be interested in a PASS/FAILED log of these?
Rune Petersen
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
