On Wednesday 30 April 2003 09:16 pm, Curtis Rey wrote:
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.
I set the monitor more or less manually during installation. All the sync ranges are from the monitor CDROM manual. Which program is that that you refer to?
Also, look at the symlinks for /usr/lib/libGL*.
I don't have a directory by that name on my system.
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.
It's an Intel 82810 CGC.
I would make sure the the libGL.so is point to LibGL.so.1 and that to the propers GL driver.
This part I don't understand.
Furthermore, you may want to look at /usr/lib/GL so see what other drivers are in there.
In /usr/lib/GL I have two: libGL.so.1.2.xf86 (the one I'm assuming I need) and also libGL.so.1.4.mesasoft.
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)
It complains that mesasoft is needed by 3Ddiag.
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.
I appreciate your response, but about 40% of the above is ancient Greek to this home-user Schlub. I'll have to take another look at the monitor settings in YaST and see if I entered the wrong values somewhere. The wierd thing is when I Alt-F2 and try to run a 3D game, the system comes up with a warning that 3D hasn't even been configured yet, even though 3Ddiag and YaST and sax2 all seem to think it has been. I don't know but my two days off are over and I have to work today. Thanks for your attempts to help. -- Bryce Hardy (Santa Rosa, CA) brycehdy@sonic.net