Against sys-kernel/gentoo-sources-2.6.12-r6, ati-drivers builds fine, & works with Direct Rendering enabled, but is forced to use the kernel agpgart, regardless of the 'UseInternalAGPGart' setting in /etc/X11/xorg.conf. This is illustrated by the following extract from dmesg:- [fglrx] Internal AGP support requested, but kernel AGP support active. [fglrx] Have to use kernel AGP support to avoid conflicts. [fglrx] Kernel AGP support doesn't provide agplock functionality. A fix for earlier kernel & driver versions was found at http://ati.cchtml.com/show_bug.cgi?id=131 - this doesn't work for my current versions. Furthermore, /lib/modules/<kernel>/modules.dep lists fglrx as depending on agpgart, & since this file is created at boot-time from information contained in the modules, there doesn't seem to be any way to stop 'UseInternalAGPGart' from being overridden. Reproducible: Always Steps to Reproduce: 1.configure & build kernel to support ati-drivers. 2.emerge ati-drivers 3.configure fglrxconfig to 'UseInternalAGPGart'. 4.reboot Actual Results: See detailed comment, particularly the extract from dmesg Expected Results: Used the driver's internal-agpgart, thus enabling agplock, blocking the loading of the kernel's agpgart & <chipset>-agp modules, & driven the graphics-card to it's fullest available potential. As this is my first bug-submission, i'll refrain from including any more info, until it is asked for...
Before submitting this bug, a search for "ati agp" (without the quotes) produced 'zarro' results. A subsequent search didn't find _this_ bug, but did find bug#89877, so apologies for what may be perceived as a duplicate. I would like to argue that the (somewhat abrupt) response on that bug won't work for the packages i listed, & that the other details i gave before lead me to believe this to be a genuine bug in ati-drivers (or it's ebuild), & not a configuration-error.
The answer was abrupt because this *is* a configuration issue. The very fact that it's loading the external AGP tells me that you haven't followed the instructions in 89877, comment #3. You *must not* have AGP support enabled *at all* within the kernel. Make sure you completely recompile the kernel and update its image on /boot. *** This bug has been marked as a duplicate of 89877 ***
Sorry Joshua, but I told you when I opened bug 89877 that ati-drivers don't install if I don't mark AGP as module or built-in.
(In reply to comment #3) > Sorry Joshua, but I told you when I opened bug 89877 that ati-drivers don't > install if I don't mark AGP as module or built-in. But you say in comment #2 of that bug you have the AGP modules built. The ATI documentation states that if you have *any* AGP support built, module or internal, the ATI drivers will pick the kernel support over its own internal AGP support. It detects the presence of the modules, not whether or not they are loaded. You must completely remove any trace of kernel AGP support for ATI to use its own implementation.
As a follow-up to comment 4, i tried building the drivers against a kernel with *NO* agp support included *prior* to filing this bug (i've posted the process at http://forums.gentoo.org/viewtopic-p-2654813.html#2654813) - the drivers *do* build okay, only producing the warning from the ebuild :- "You don't have AGP support enabled, the direct rendering will not work." When X was started, sure enough, Direct Rendering was *disabled*. Because i use udev/coldplug for device-management, & have *no* entries in /etc/modules.autoload.d/kernel-2.6, the only hypothetical solution i can think of is to build *with* agp kernel-support as modules, revert to using devfsd, & manually load *only* the required modules - & i'd rather not have to resort to that... I think i'm going to ask (on the forum-thread linked above) if anyone *has* InternalAGPGart working, if it's better than external, & how they did it.
(In reply to comment #5) > When X was started, sure enough, Direct Rendering was *disabled*. I forgot to mention that dmesg contained the well-known list of error-messages about agp not being found - i didn't keep a copy, sorry, but they were the same ones listed at all the usual sites; one example is at http://rage3d.com/board/showpost.php?p=1333602371&postcount=1 I've also just realised that the devfsd idea won't work either, because of the /lib/modules/<kernel>/modules.dep entry i mentioned in my opening comments.
Please use the external agpgart. The internal one is a extreme measure just in case the external isn't working and usually has lesser performance.
