From: David G. <dg...@ir...> - 2000-04-28 02:47:52
|
On Thu, 27 Apr 2000, Erik wrote: > On Thu, Apr 27, 2000 at 05:55:20PM -0500, Jay Thomas wrote: > > Hi, > > > > I noticed a couple things when testing the latest utah-glx on a dual 600 PIII > > w/ 512 MB RAM & a Matrox G400 MAX dual head. > > > > a) When I open up a second GLX context the X server invariably crashes. > > > > b) When I run w/ two X-servers on the same screen (ctrl-alt-f7/f8) via GDM the > > G400 card seems to become corrupt easily. i.e: garbage is displayed onto the > > screen & the screen cannot be reset w/o rebooting. > > > > Any ideas? > Thats interesting. I only have a G400, on a K7-550, but i have two screens open > all the time. I play unreal on :1, although i never have 3d going on both screens. > > Also i have had multiple glx contexts open ... never was a problem(just tried now, > it works fine for me) ... > > interesting :0 > > > -Jay > > Erik Bernhardson > jo...@jp... I often use multiple glx contexts within the same application, and I find that when I quit the application (i.e. causing multiple glx contexts to be deallocated at nearly the same time) X crashes about 50% of the time. Both on the G200 and the G400. Also, the G400 hard-locks during general use reasonably often, the G200 hard-locks only when I use a large (i.e. 1280x1024) context. Neither of these cards ever gives me trouble when I'm playing Quake III, so pretty much all the serious quake-related bugs must have been squashed. As a general-purpose OpenGL driver, though, the utah-glx mga driver is definitely no better than alpha-quality. Many kudos to the developers, though, having X crash every so often is far better than having no drivers at all! - David P.S. Your ":0" emoticon, obviously meant to convey either surprise or disbelief that the G400 driver has any major bugs, is quite insulting to all of us people who do experience problems with it. -- David Gobbi, MSc dg...@ir... Advanced Imaging Research Group Robarts Research Institute, University of Western Ontario |