"Stephen C. Tweedie" wrote:
>
> Well, in composing the previous email I did several reboots with what
> I thought was the "good" configuration and some of them failed. So
> I've just spent half an hour rebooting into full DRI, and finally got
> the X server to start properly. Now that it has got past the
> initialisation, it is running fine --- quake3 shows a good performance
> improvement over the old voodoo3 (especially on some of the large
> terra levels which rapidly went into texture swap on the old 16MB
> card), and tribes 2 is running albeit a little slowly.
>
> So, I've established that there is no apparent pattern at all to the X
> server starting up or not in this configuration. Once it does start,
> it seems 100% solid: I've had it running for an hour now with
> absolutely no problems except for absense of the team3arena startup
> logo (I just get a blank screen during the intro), lack of bilinear
> filtering on mip levels beyond the closest (which I've seen reported
> elsewhere), and some odd sky texture effects in tribes2.
>
> So the bottom line is that, for reasons unknown, X simply fails to
> initialise properly on this box. Beyond that, everything works as
> expected, but having to reboot half a dozen times or more to run
> startx is sub-optimal. :-)
Thanks for the detailed info, Stephen.
I'm currently working on some kernel-related tasks, but I can take a
look into the problems you (and others) have mentioned regarding the
Radeon driver early next week. Are you running it from the DRI CVS? If
you're game, you might want to try the in-development mesa-3-5-branch.
This is where all our focus is at the moment, and many of the GL-related
problems may be fixed there already.
-- Gareth
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
