On Mon, Oct 25, 2010 at 11:55 PM, Dale <rdalek1...@gmail.com> wrote: > Dale wrote: >> >> Well, at least we know there is a problem and it isn't just us. If you >> find something, let us know. I would hate to know I had to try to watch a >> DVD right now. I doubt it would even start up. o_O >> >> BTW, hal is disabled on xorg here. It's enabled on other things but not >> xorg. >> >> Dale >> >> :-) :-) >> > > I have a update. Check this out: > > r...@smoker / # glxgears > Running synchronized to the vertical refresh. The framerate should be > approximately the same as the monitor refresh rate. > 1380 frames in 5.0 seconds = 275.147 FPS > 242 frames in 5.0 seconds = 48.345 FPS > 241 frames in 5.0 seconds = 48.191 FPS > 246 frames in 5.0 seconds = 49.056 FPS > 240 frames in 5.0 seconds = 47.902 FPS > 238 frames in 5.0 seconds = 47.453 FPS > 238 frames in 5.0 seconds = 47.566 FPS > 240 frames in 5.0 seconds = 47.839 FPS > 244 frames in 5.0 seconds = 48.577 FPS > 242 frames in 5.0 seconds = 48.257 FPS > 241 frames in 5.0 seconds = 48.196 FPS > 242 frames in 5.0 seconds = 48.380 FPS > 238 frames in 5.0 seconds = 47.573 FPS > 238 frames in 5.0 seconds = 47.596 FPS > 241 frames in 5.0 seconds = 48.168 FPS > XIO: fatal IO error 22 (Invalid argument) on X server ":0.0" > after 900 requests (900 known processed) with 0 events remaining. > r...@smoker / # > > > What did I do you ask? Well, I did this: > > r...@smoker / # eselect opengl list > Available OpenGL implementations: > [1] nvidia * > [2] xorg-x11 > r...@smoker / # eselect opengl set 1 > Switching to nvidia OpenGL interface... done > r...@smoker / # > > Yea, it SAID it was already set but I told it to set it again anyway. Now I > get some good frame rates again. Excuse me while I go watch some videos I > been wanting to watch but got tired of the spit and sputter. lol > > YEPPIE ! ! ! It breathes again. > > Dale > > :-) :-) > > P. S. Bonus points if someone can explain why that worked. o_O
It's been a while since I last had X + accelerated 3D on any of my systems here (my gaming box's running W7), but it would be my guess that, while Nvidia's libraries *were* configured as the GL implementation to be used, in the process of the last driver upgrade they got overwritten with upgraded versions, running things that should have referenced them failed and defaulted to mesa's libraries, and you got stuck with CPU based 3D rendering. Upon using eselect to set it to Nvidia's again, however, you refreshed the links to the proper, updated, libraries and things started using the GPU again. This is, of course, entirely a guess, and is at least moderately broken by this from glxinfo: server glx vendor string: NVIDIA Corporation Still... it's the best guess I have at 1:17 AM here, my time. -- Poison [BLX] Joshua M. Murphy
