-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 29 April 2003 21:56 pm, Bryce Hardy wrote:
On Wednesday 30 April 2003 07:42 pm, Curtis Rey wrote:
Possibly a silly question - so forgive me. But, did you, as root, run the command in the console "switch2xf86_glx"?
Yes, you didn't see the end of my original post, I did do that just as a hunch, but still it's not working correctly.
OK, my experience with this sometimes boils down more to the way X, the card, and sax work with the monitor. I presume your getting a screen. You may want to look at the monitor settings. I often manually set the monitor params myself or run the x prog that tells you your monitor res timings and cut and past these into the XF86Config file. Also, look at the symlinks for /usr/lib/libGL*. I am used to dealing with nvidia cards and am unsure about what card your using since I haven't seen the 1st post you made. I would make sure the the libGL.so is point to LibGL.so.1 and that to the propers GL driver. Furthermore, you may want to look at /usr/lib/GL so see what other drivers are in there. If you find the mesasoft_glx drivers this may also be a problem because the symlinks may point to that. I have had confilcts with this before. The symlinks and the drivers are often the issue. If you try to "rpm -e mesa" or the mesasoft (can't remember exactly but I think it "rpm -e mesasoft") and it complains about the dependencies with the mesa libs (keeping the mesa libs isn't a prob in my experience) then you can just manually rm the mesasoft drivers in the /usr/lib/GL dir and reestablish/make the syms manually if need be. If unsure how this goes repost. Let us know what you find. HTH, Curtis. :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+sJ+f7WVLiDrqeksRAjX9AJ992OyoRRE+NPkyWGXRaw+Ywwg0GQCfb830 dW40ZpAqgb14MiTYfqmTVrc= =rNVA -----END PGP SIGNATURE-----