This might be usefull tips for the Troubleshooting section of the Hardware 3D Acceleration Guide. (Taken from this reality soap: http://forums.gentoo.org/viewtopic-p-2785398.html#2785398 ) ;-) --- Direct rendering is slow, and in /var/log/Xorg.0.log I have an error about falling back to PCI-mode. If you are using a 2.6 kernel, the hardware specific part of agpgart is a separate module. Check lsmod if this module loads automatically. If not, add it to /etc/modules.autoload.d/kernel-2.6 and reboot. --- X is crashing at restart or logout; mouse and keyboard not working anymore! Setting APG in /etc/X11/xorg.conf to a high value, may cause instability. Lower it to 4, 2 or 1. It may not even have an effect on your acceleration speed (FPS). --- Regards. Reproducible: Always Steps to Reproduce:
Created attachment 75397 [details, diff] dri-howto.xml.patch Okay, this implements the agpgart autoload reference--this is indeed very important, otherwise the whole thing is screwed up!! :) But, what do you mean by "APG"? Do you mean AGP? "less /etc/X11/xorg.conf.example | grep -i AGP" doesn't have much, and "man xorg.conf" doesn't talk about any such values for any AGP option. What are you talking about?
(In reply to comment #1) > But, what do you mean by "APG"? Do you mean AGP? > > "less /etc/X11/xorg.conf.example | grep -i AGP" doesn't have much, and "man > xorg.conf" doesn't talk about any such values for any AGP option. What are you > talking about? Never mind, I figured it out. Re-read the doc. :) So you know, the "4" setting reflects the mode that the card and motherboard are capable of running at. All modern AGP cards and AGP-capable motherboards ship with 8x AGP interfaces, so that's why one might set 8. If you only have a 4x or 2x card/motherboard, then obviously 8 (8x) will not work.
Created attachment 75467 [details, diff] dri-howto.xml.diff
(In reply to comment #3) > Created an attachment (id=75467) [edit] > dri-howto.xml.diff > Hi, My two tips above where meant for the Troubleshooting section, using question-answer style. But a small change to section 3 would be a good idea too. However, the patch is not correct. For 2.4 kernels, there's only one module to load: "agpgart". Since 2.6, two modules should load: "agpgart" plus one for the hardware ("intel-agp" in the example). Loading "intel-agp", pulls in "agpgart" as dependency automatically. So the current example in the doc is correct for 2.6. Only a separate example for 2.4 should be added, to load "agpgart". B.t.w.: using /etc/modules.autoload.d/kernel-2.x may not be necessary on all systems, but it won't hurt either. Setting "AGPMode" in /etc/X11/xorg.conf to the max. value that is supported by the hardware, may cause instability. Not setting a value in /etc/X11/xorg.conf may cause a lower default value to be used. In case of instability, it's a good idea to find out the current value used in /var/log/Xorg.0.log, and try specifying a lower value in /etc/X11/xorg.conf. How about this patch... Changed to only one troubleshooting tip.
(In reply to comment #4) > Setting "AGPMode" in /etc/X11/xorg.conf to the max. value that is supported by > the hardware, may cause instability. Not setting a value in /etc/X11/xorg.conf > may cause a lower default value to be used. In case of instability, it's a good > idea to find out the current value used in /var/log/Xorg.0.log, and try > specifying a lower value in /etc/X11/xorg.conf. > > How about this patch... Changed to only one troubleshooting tip. Actually, if you build agpgart as a module, it *must* be listed in the proper modules.autoload.d. Otherwise it will not be loaded at boot, which of course will cause problems. Regarding the AGP settings, well, I've already implemented that in a patch elsewhere. Take a look at bug #116506 ; I've made quite a few changes. Still waiting to hear back from spyderous on that one. I did suggest that the modules.autoload.d mention could (and should) be integrated with my numerous changes to other parts of the existing doc.
(In reply to comment #5) > Actually, if you build agpgart as a module, it *must* be listed in the proper > modules.autoload.d. Otherwise it will not be loaded at boot, which of course > will cause problems. What about coldplug?
(In reply to comment #6) > (In reply to comment #5) > > Actually, if you build agpgart as a module, it *must* be listed in the proper > > modules.autoload.d. Otherwise it will not be loaded at boot, which of course > > will cause problems. > > What about coldplug? Doesn't handle agpgart, AFAIK. Probably because that would totally screw around with binary drivers.
Already fixed in bug #116506. Also, if you specify an AGP setting not supported by your hardware (for example, you attempt to rice your system with 8x AGP though your motherboard only supports 4x), it defaults to 1x, so you'll be safe.
