From: Alex D. <ale...@gm...> - 2005-09-28 14:26:43
|
On 9/28/05, John Shillinglaw <ia...@sc...> wrote: > Thanks, > > now for a dumb question... how far back do I need to go to get mesa > without those changes, and where? > > Thanks again for the help. could you actually try checking out HEAD again? Brian made some assertion changes that may fix this. If that doesn't work please try is other suggestion in this thread. I'd test it myself, but my savage box is not in a useable state at the moment. Alex > > > > I have a Thinkpad T20 with a Savage IX, that is running Gentoo Linux > > > with 2.6.14-rc2-mm1 kernel. > > > > > > In order to get direct rendering working, I have followed the build f= rom > > > cvs instructions on the dri wiki. Now everything seems to work, dmesg > > > shows no errors, and the xorg log tells me direct rendering is enable= d, > > > and I can run glxgears with fps from 150 up to 300. > > > > > > However, glxinfo bombs with a seg fault message, and tuxracer locks u= p > > > the computer before actually getting to the play screen. > > > > > > I've compiled with the latest xorg cvs, dri cvs, mesa cvs, etc. > > > > > > Any ideas? > > > > > > > > > > I think Brian's renderbuffer changes may be the cause. If you go to > > a version of mesa cvs prior to the changes it should work. I've lots > > of other reports of this problem on savage; cc'ing dri-devel. > > > |