Originally posted by DaOne
Also, you need support for your chipset (this is what gives you yourchipset-agp)...you can see in Hooper's post that he has...
? ? <*> Intel 440LX/BX/GX, I8xx and E7x05 chipset support ? ?
in Character devices. So he most likely also has intel-agp loading with agpgart. I really don't know if DRM has any real effect on installing the drivers, but I did not include it in my kernel just as a precaution.
This is one that I believe gets over looked quite a bit. Yes there are two actual drivers (modules) responsible for this as DaOne mentions. You have a chipset to contend with as well as agpgart. The selection above supports this motherboards chipset. Without that selection, you cannot load fglrx due to no chipset drivers being loaded. That or, (depending upon the hardware) you just won't have the performance. The DRM had no effect on this installation for me. A few posts back you will notice that I posted to not load DRM due to the issues. I didn't have the same issues this time thus I loaded it directly into the kernel.
It's important for all to keep your motherboard manuals handy. I've kept mine handy and open if needed since my first computer. The XT 8080. It gives out all the secrets you'll need when compiling custom kernels. This motherboard is the asus P4C800-E Deluxe. The chipsets used in this configuration is the Intel 875P MCH/Intel ICH5R. When working with a new Linus release, be sure to use the help function in make menuconfig. When trying to match support for hardware try to choose the closest support for each function. Most of the time if you use the help function it will tell you what is supported. In this case my chipset is supported by my chipset selection and even if it weren't, it's the "best known and closest support". Not all will match up perfectly until linux support catches up to the hardware. There is more than sufficiant support even for this new motherboard.
Before compiling, be armed with the knowledge of your motherboards configuration. Check your bios settings to ensure your support for each module is turned on. It's there and you'll be able to match up mentally what the bios offers to the kernel config options. This doesn't require you to be a tech geek, but it's near impossible to tweak a kernel not being informed of your hardware's capabilities and limits. This is a must. Don't be in a big hurry to make install on your kernel. Unless of course you want to do this about a hundred times until you get it right.
Note though that you can load agpart directly into the kernel if you so choose instead of a module. Either way worked fine for me using this new driver and you can control how your card functions (use internal/external) via the /etc/X11/XF86Config-4.
Most of the issues can be resolved by correctly configuring the kernel. Another recommendation I have would be to mv /lib/modules/fglrx /lib/modules/fglrx-old before attempting to install your new drivers. I learned the hard way with modules and FreeBSD. I use the same practice when installing anything for both linux or freebsd since.
I took a look at the above manual. It's alright although a bit dated and using an rpm based distro. If you are using Slackware, it would be advised to skip over using rpm's at all. That is one of the main reasons I choose slackware over other distro's. Get rpm2tgz and rpm2tgz your ATI driver. Then move it to / and unarchive it or use pkgtool and install it from there. Rpm is the ruination of linux disto's IMO. Don't like rpm at all. 100% better successes from compiling from source. No flames please. It's just my opinion.
The above is the real reason when someone asks "Which Linux disto is right for me?" No one can really answer the vague question. It depends upon their knowledge of hardware/software basics/fundamentals. If they don't know what a bios is, it's obvious they need a generic distro kernel loaded to the gills with every possible hardware configuration and a book. If they are tech savy and give examples of what they know, then it will make for a better answer to the question. You'll find most don't care anything about a bios or how anything runs. Thus winblows. I never recommend that anymore no matter their knowledge. Send them to a book store.
Another thing to watch out for is Mesa Libs. Make sure Mesa doesn't get in your way and mess up your graphics driver work. I had that issue before as well.
I usually have no less than 3 or 4 machines running at any given time. All either linux or freebsd / desktops or servers. One thing I've noticed between Athlon and Intel machines is it always seems better to run Linux on Intel X86 for desktop optimizations. The Athlon machines do alright, but when getting down to business tweaking, the Intel always seems to give the advantage both in feel and throughput. I could be quite wrong in this area, but for the desktop I've found Intel to be the better choice with linux. With non desktop server boxes either do fine on the right platform, but I still prefer Intel.