Am Dienstag, 8. Oktober 2002 16:37 schrieb Timothee Besset:
> Mh .. setting the default to r_smp 1 when SMP detected may have been an
> oversight. This has been tested to work on nvidia cards, it's likely to
> break on anything else. I'd be interested to hear about work/not work in
> various situations.
>
> Use +set developer 1 +set logfile 2 on the command line to get a log file
> from q3.
With my "startup script" I get log all the time...;-)
Card: R200 DRI CVS.
Kernel: 2.4.19-ck5 and 2.5.40-ac4
System: dual AMD Athlon MP 1900+, MSI K7D Master-L, AMD 760MPX
I get ups with both kernels when "demo four" should come up (after weapons
load).
But I think it is a r100/r200 driver issue not your fault.
Even though "r_smp" should default to "0".
Load is _definitely_ shortened 'cause "quake3.x86" and "X" rising on different
CPUs, now. GREAT! Can't wait to see it running.
----- finished R_Init -----
Loading vm file vm/ui.qvm.
VM file ui compiled to 594408 bytes of code
ui loaded in 1963008 bytes on the hunk
35 arenas parsed
32 bots parsed
Loading vm file vm/cgame.qvm.
VM file cgame compiled to 786818 bytes of code
cgame loaded in 5380768 bytes on the hunk
drmCommandWrite: -22
drmRadeonCmdBuffer: -22
Get the same crash with several other "threaded" (multiple context) apps.
Regards,
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel at hamburg.de (replace at with @)
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
