View previous topic :: View next topic |
Author |
Message |
alexcorn n00b
Joined: 06 Aug 2006 Posts: 11 Location: Muncie, Indiana, USA
|
Posted: Sat Aug 12, 2006 10:51 pm Post subject: Disable AGPGART and use NVAGP |
|
|
I am running Gentoo AMD64 on a Tyan S2885 with a Quadro FX 500 AGP card. I want to use NVAGP in place of AGPGART. Using NVAGP in SuSE made a huge difference in performance. However, in Suse AGPGART was modularized; in Gentoo, it is compiled in statically. In menuconfig, there is no option to change the way AGPGART is included. It is compiled in statically no matter what I do. I tried running Gentoo x86, and was able to disable AGPGART. That didn't work either, though. When AGPGART was disabled entirely, the nVidia driver refused to load. How do I enable AGPGART to load as a module in 64 bit Gentoo and use NVAGP in its place? |
|
Back to top |
|
|
troymc Guru
Joined: 22 Mar 2006 Posts: 553
|
Posted: Sun Aug 13, 2006 6:35 am Post subject: |
|
|
In your xorg.conf, take a look at the NvAGP option in your Device section.
troymc |
|
Back to top |
|
|
alexcorn n00b
Joined: 06 Aug 2006 Posts: 11 Location: Muncie, Indiana, USA
|
Posted: Sun Aug 13, 2006 2:44 pm Post subject: |
|
|
I've got "NvAGP" set to 1 in xorg.conf, which tries to force nvagp instead of agpgart. I don't think that's the problem though. Agpgart is statically compiled into the kernel and I think it is keeping nvagp from loading. I want to modularize agpgart in the kernel config, but there doesn't appear to be a way for me to do so... |
|
Back to top |
|
|
cnistra Tux's lil' helper
Joined: 01 Apr 2006 Posts: 78 Location: Göteborg, Sweden
|
Posted: Sun Aug 13, 2006 11:17 pm Post subject: |
|
|
If you put agp=off at the end of the kernel commandline in grub.conf agpgart will not be loaded. |
|
Back to top |
|
|
alexcorn n00b
Joined: 06 Aug 2006 Posts: 11 Location: Muncie, Indiana, USA
|
Posted: Mon Aug 14, 2006 1:10 am Post subject: |
|
|
cnistra wrote: | If you put agp=off at the end of the kernel commandline in grub.conf agpgart will not be loaded. |
Will this work even if agpgart is statically compiled into the kernel? If so, great. If not, I still need to be able to tell agpgart to compile as a module. |
|
Back to top |
|
|
cnistra Tux's lil' helper
Joined: 01 Apr 2006 Posts: 78 Location: Göteborg, Sweden
|
Posted: Mon Aug 14, 2006 10:09 am Post subject: |
|
|
I think I should have said "agpgart will be disabled" instead of "agpgart will not be loaded", sorry for the confusion.
zless /usr/share/doc/nvidia-drivers-1.0.8762-r1/README.gz wrote: | To use the Linux AGPGART driver, it will need to be compiled with your kernel,
either statically linked in, or built as a module. NVIDIA AGP support cannot
be used if AGPGART is loaded in the kernel. It is recommended that you compile
AGPGART as a module and make sure that it is not loaded when trying to use
NVIDIA AGP. Please also note that changing AGP drivers generally requires a
reboot before the changes actually take effect.
If you are using a recent Linux 2.6 kernel that has the Linux AGPGART driver
statically linked in (some distribution kernels do), you can pass the
agp=off
paramater to the kernel (via LILO or GRUB, for example) to disable AGPGART
support. As of Linux 2.6.11, most AGPGART backend drivers should respect this
parameter.
|
Just try it, if it works go on with your life. |
|
Back to top |
|
|
alexcorn n00b
Joined: 06 Aug 2006 Posts: 11 Location: Muncie, Indiana, USA
|
Posted: Thu Aug 17, 2006 2:35 pm Post subject: |
|
|
I tried using "agp=off" but it didn't work. Now when nvagp tries to load, it fails and says it is because the kernel was compiled with iommu support. I've tried disabling iommu in the kernel config, and I've tried passing "iommu=off" to the kernel at boot. I also tried "iommu=noagp". Nothing so far works. |
|
Back to top |
|
|
Drunkula Apprentice
Joined: 28 Jul 2003 Posts: 257 Location: Denton, TX - USA
|
Posted: Thu Aug 17, 2006 4:47 pm Post subject: |
|
|
Well if you're recompiling the kernel why not just compile without agpgart - or modularize it. _________________ Go away or I will replace you with a very small shell script. |
|
Back to top |
|
|
cnistra Tux's lil' helper
Joined: 01 Apr 2006 Posts: 78 Location: Göteborg, Sweden
|
Posted: Thu Aug 17, 2006 5:33 pm Post subject: |
|
|
Hello alexcorn, we are making some progress at least. A dmesg would be interesting to see.
Anyway I saw on another message board that one could try to boot with iommu=memaper=2 and set agp aperture size to 64MB or 128 in bios. So maybe you could try to boot with agp=off iommu=memaper=2. If it does not work post the output of dmesg here. Here is another thread of the same messageboard that deals with your problem.
Also, it could be benificial to use a recent bios. Check your mobo maker web page. |
|
Back to top |
|
|
cnistra Tux's lil' helper
Joined: 01 Apr 2006 Posts: 78 Location: Göteborg, Sweden
|
|
Back to top |
|
|
alexcorn n00b
Joined: 06 Aug 2006 Posts: 11 Location: Muncie, Indiana, USA
|
Posted: Fri Aug 18, 2006 1:22 am Post subject: |
|
|
I finally got it to work. What did it was a combination of adding iommu=memaper=2 and installing nvidia-drivers instead of nvidia-glx and nvidia-kernel. nvidia-drivers is one version newer. I compiled agpgart as a module, but did not configure it to load. Thus, I am not using agp=off. I also didn't end up taking the K8 IOMMU GART out of the kernel. It is still statically compiled in. Unfortuneatly, Quake 3 is still sorta choppy and xine DVD playback gets audio and video out of sync. mplayer plays DVDs fine though, so no big deal there. I have SBA and FW both enabled, so I don't know what to do about Quake 3 just yet. I may try a different nvidia card. Thanks for all the help! |
|
Back to top |
|
|
cnistra Tux's lil' helper
Joined: 01 Apr 2006 Posts: 78 Location: Göteborg, Sweden
|
Posted: Fri Aug 18, 2006 2:12 am Post subject: |
|
|
Cool that it works, strange that q3 is choppy though. I remember q3 had fluent framerate with a gforce 1 card in 800x600. Does glxinfo look ok? Check out Appendix M in nvidia documentation (/usr/share/doc/nvidia-drivers-1.0.8762-r1/README.gz) about the proc interface, maybe the driver itself can give some clues. |
|
Back to top |
|
|
|