On Friday 06 December 2002 18:08, you wrote:
Thanks for the advice Karol. I have already done all of these and more. I have repeatedly used both the rpm and tar.gz - completely removing all between each install and config attempts. checking symlinks and dependencies, etc... I did do some things described by grimmer's modules/kernel page on the suse sdb. It's seems that there was a difference between the /usr/src/ and the /boot files. I did some shifting around of the /boot/vmlinuz.... files and did SuSEconfig, mk_initrd, and a depmod -a. Then a reinstalled some of the updates via yast2-you and ran the sax2 from the CC (sax2 would crash previously in either the gui or ncurses - probably because no NVdriver and couldn't initialize correctly).
Well, the NVdriver module is loaded automatically. Just for the record, what I do/did to install the latest NVidia incarnation is: - install binary GLX from NVidia.com - rebuild kernel module SRPM (I use my own kernel) On one machine with a clean SuSE 8.1 install, all I had to do to get the latest NVidia stuff was to select "Current NVidia driver" in YOU. The machine had a GeForce3 Ti200 video card.
Anyway, it asked if I wanted to setup 3d config for xf86 (before nvidia drivers shouldn't have the "enable 3d acceleration" turned on). What I find interesting is no matter what I did (short of loading the module via boot.local with "modprobe NVdriver" and the same for the agpgart) the modules were not loaded. After enabling the 3d accel option in sax the drivers were loaded (which include videodev, agpgart, and NVdriver) and voila - gears works and 3d/glx is on.
This sounds like the 'Load "glx"' was added to the /etc/X11/XF86config .
I am at a loss as to some of the new ways 8.1 seems to handle the video (and apparently it's associated modules/drivers) configs. I play a fair amount of 3d games and before if i changed the res (e.g. 800x600 to 1024x768 or 1280x1024) the screen would resize no problems. But after 8.1 doing this would result in either a smaller screen with a black border around it (like 1024x768 inset in the screen) while up'ing the res or the opposite (800x600 inset with a black border around it), this seemed dependent on certain monitor options such as iterate precisely or calc'ing the desktop geometry.
Hmm. This seems like a XFree86 bug more than anything else. That's truly bizarre.
I have it working know but, the part Sax2 plays related to why a kernal module is or is not load has me a bit baffled - since these never seemed to influence one anothers functions related to modules being loaded during boot before.
As far as I understand the internals, the kernel module is auto-loaded
through the kernel module loader when called upon by the GLX XFree86
module. The 'Load "glx"' line is commented out (i.e., non-functioning)
if 3D acceleration is turned off via SaX2, uncommented otherwise.
At least you "have it working now"...
--
Karol Pietrzak