The 03.05.12 at 20:02, Curtis Rey wrote:
DANGER, DANGER WILL ROBINSON (lost in space phrase)! 2022753 Sep 10 2002 /usr/lib/GL/libGL.so.1.3.mesasoft
What's that? (The lost in space part, I mean - movie titles get translated, so I don't know which one is that, or I don't remember)
Loose this now. Mesasoft drivers have caused me nothing but grief with nvidia drivers and many howto sites (and I believe nvidia) state that this is a conflict. This is most like the cause of the problems. if you try and rpm -e mesasoft rpm will complain that the other dependent packages need this
Ok, done. run: switch2nvidia switch2nvidia_glx cp /etc/X11/XF86Config.nvidia.20030511 /etc/X11/XF86Config /sbin/depmod /sbin/ldconfig and finally, reboot, init 3, startx (from a console). It takes something like three or four minutes till I get kde running - I'm not kidding, when I think it has hanged, I boot up my old pentium 120 w 32 Mb, and I have time to ssh into this one before kde is finished and accepting input. By the way, response to ssh is fast, but inside kde even the mouse gets lost now and then.
driver - not true! just rm it for the /usr/lib/GL dir directly. I am willing to bet this is the source of your problems and if you think about it the slow video response is most likely on the order of the mesasoft GL performance!
It wasn't, I'm afraid. :-( Remember that this machine had nvidia working last december with the same software - except upgrades. Mesasoft was there from the very begining.
The other option is to point the games / 3D apps to look for the nvidia drivers. Many state that this is the case, like the original Quake 3 with
I want nvidia working to play games, but I can't even use kde or gnome. It works perfect now with the open driver (nv), but horrible with the closed "nvidia".
Like I said. I always loose the mesasoft drivers first think - they're antiques, they're slow, and almost always in the way and a conflict. Try this and get back to us to let us know - well kick this in the butt yet :) !
Good try, but didn't work out. I'm going to try to downgrade the kernel, and see what happens - it's faster for me than updating to a mantel kernel, because 35 Mb on a modem is a lot. If it works, then I'll think about upgrading. Afterthought: This is the report of 3Ddiag: 3Ddiag version 0.496 Verifying 3D configuration: Using 3dinfo ************************************************************ Verifying 3D configuration based on XFree86 4 for 3D board "nVidia Corporation GeForce2 MX/MX 400 (10de@0110)": Tests for package "NVIDIA_GLX": package ... done. package files ... done. Tests for package "NVIDIA_kernel": package ... done. package files ... done. Tests for correct OpenGL libraries/GLX extensions: Symbolic Links ... done. /etc/sysconfig/3ddiag (SCRIPT_3D=switch2nvidia_glx) ... done. Test for correct XFree86 version ... done. Tests for XFree86 configuration: Config File /etc/X11/XF86Config ... done. Driver ... done. Color Depth ... done. Extensions ... done. Options ... done. ----------------------- NOTE ----------------------------------- If 3D hardware OpenGL configuration is not stable enough, you should switch back to 'Mesa Software Rendering'. You can verify this configuration with the command "3Ddiag --mesasoft". ----------------------- NOTE ----------------------------------- Checking GLU/glut runtime configuration: GLU ... done (package mesaglu) glut ... done (package mesaglut) nimrodel:~ # 3dinfo nVidia Corporation GeForce2 MX/MX 400 (10de@0110):4:nvidia:16:glx:::NVIDIA_GLX,NVIDIA_kernel:switch2nvidia_glx -- Cheers, Carlos Robinson