Am Dienstag, 30. Mai 2006 03:00 schrieb Roland Scheidegger: > Dieter Nützel wrote: > > Am Dienstag, 30. Mai 2006 00:33 schrieben Sie: > >> Dieter Nützel wrote: > >>> Latest Mesa and DRM CVS:
> >>> r200_sanity.c: In function ‘r200SanityCmdBuffer’: > >>> r200_sanity.c:1422: error: ‘RADEON_CMD_VECLINEAR’ undeclared (first use > >>> in this function) > >>> r200_sanity.c:1422: error: (Each undeclared identifier is reported only > >>> once r200_sanity.c:1422: error: for each function it appears in.) > >>> make[6]: *** [r200_sanity.o] Fehler 1 > >>> make[6]: Leaving directory `/opt/Mesa/src/mesa/drivers/dri/r200' > >> > >> Yes, this is caused by preparation for hw vertex programs on r200. You > >> need a new libdrm (actually, all you need is a new radeon_drm.h) from > >> drm cvs. > > > > Oh, shit. > > I had latest DRM code but haven't compiled it for some time...;-) > > Works. > > What should I test? > > Nothing yet as the code in cvs does pretty much nothing for now. The > rest is not yet in cvs mostly due to really ugly hacks I needed but > don't have an explanation for. If you're interested you could try the > attached patch and try doom3 with the r200 render path Now, after 'all' is in CVS: Which term? r200 didn't work arb (default) works arb2 didn't tried > (I actually just > hope it works the same with r200 as with rv250), you still need to > enable arb_vertex_program manually with driconf. If I do this doom3 hangs. Celestia 1.3.2 and 1.4.1 hangs system when I switch to wireframe mode but works _accelerated_ otherwise. - GREAT! > The attached patch is > basically the same as the earlier one, but without the changes already > commited to cvs. > > > BTW Doom3 do not work any longer on my wife's machine. > > It hangs in 'starting sequence'. > > Log available. > > Duron 1800 (3DNow!, SSE1), 512 MB, r200 (my 'old' one), SuSE 10.0 + > > latest Mesa/DRM. > > What pre-load should I try. > > Worked some months ago. > > Not sure what could be wrong - if that's just the game which hangs (i.e. > you can still kill it) and you've redirected the output make sure you > don't forget to specify +set in_tty 0 at the commandline when starting > doom3, otherwise the game will always stop at "initializing menus". Helped. Cheers, Dieter PS Hello list, I've back, again;-) -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
