Ya, I know about the nvagp options and have implemented them in several versions of SuSE. However, something about the way the kernel driver interacts with the OS and X seems to have changed. I have never had a situation where a module that's listed in the modules.conf file and is compiled into the kernal is not loaded. I most likely didn't do something I should have but can't figure out what. I did things as I normally used to do and this time it didn't work. I really suspect it was the k_athlon kernel update I did via apt-get/synaptic. As far as agpgart is concerned I used to forego it because it wasn't necessary. But since v-8.0 it seems to be the default config done during the OS install and this is true for v-8.1. I just never had a situation where the NVdriver wouldn't load after the boot up unless it was configured with Sax2. Before I used to not even used sax and just hand config my X server. But it seems to be especially cranky of late, and as this has been since 8.0. Like I said, in v-8.1 it seems that sax2 has a larger play into the modules loaded pertaining to the X config. Cheers, Curtis.
That depends on your config. the XF86Config option NvAGP determines which implementation will be used.
agpgart is the Linux kernel's AGP implementation; NVdriver is NVidia's. Honestly, I don't know if NVidia's kernel module works with agpgart.
NVdriver is much more than AGP. It can use agpgart if you tell it to do so. However, in my experience it's not necessary.
Anders
-- Billboard Writer vs. Literature = Micorsoft vs. Computing,