I also have it working, though I don't really know what the error was. Hooper, your kernel config helped out a lot. Thanks a whole lot to all you guys.

Your welcome. I'm happy when everybody's ATI cards work... Hard earned money I say.. and well... we all know what this hardware does on a nicely tweaked out linux box!!

Yippee Yay... Congratulations... !!!

Great score!

I thank all as well and DaOne for getting this SMP fixes for the AGP/ATI. That
was a real big help and he spent some hours on this. Much appreciated DaOne. Tuxracer is flying like a bat out of he.. well you know.

Hooper

Glad to hear about the successes. Now...I wonder how it will all fit together once ATI releases the new drivers? Could be today yet from what I hear. Could be fun huh?

Does the new driver requires patching?
BTW, I got an error:

dmesg
[fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)
[fglrx:firegl_unlock] *ERROR* Process 605 using kernel context 0 (605 was X)
mtrr:0xe0000000,0x80000000 overlaps existing 0xe0000000,0x10000000

any help?

New drivers huh... I guess my email to ATI helped. :P

I downloaded them, should be able to give them a shot within the next day or so.

To the above.... Hmm. Don't know. If we have to patch the new drivers, that doesn't sound like ATI is putting the needed effort into them.

Hmmm...try not using the Memory Lock function...here is a snip from my config...

=== ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"

I disabled the function during fglrxconfig.

I couldn't wait a couple days to try out the
new drivers. Installed with no issues. Gained
a speed increase it so appears. Very nice.
==================================
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 PRO x86/SSE2
OpenGL version string: 1.3 (X4.3.0-3.7.0)

rjs@machine:~$ glxgears
16514 frames in 5.0 seconds = 3302.800 FPS
21137 frames in 5.0 seconds = 4227.400 FPS
21651 frames in 5.0 seconds = 4330.200 FPS
21649 frames in 5.0 seconds = 4329.800 FPS
21650 frames in 5.0 seconds = 4330.000 FPS
21649 frames in 5.0 seconds = 4329.800 FPS
21645 frames in 5.0 seconds = 4329.000 FPS
21651 frames in 5.0 seconds = 4330.200 FPS
21650 frames in 5.0 seconds = 4330.000 FPS
21644 frames in 5.0 seconds = 4328.800 FPS
====================================
I shut off the new user page locking as requested.
*methinks: wonders what it does?*

Thank you,
Hooper

I already turned off the page locking and mtrr, but I still get the same error, still mtrr error
what is the "kernel context 0" anyways...
thx for your help ^^

I don't know if the new driver requires patching or not. Do you have MTRR (Memory Type Range Register) support enabled in your kernel under # Processor type and features # ?

Hmmm. That is strange. The only thing I did was do as DaOne mentioned and turned off the user page lock setting in the x config. I've been tinkering with kernel options so I did also set DRM up in the kernel this time around.

=========================
CPU settings
========================

? ? Subarchitecture Type (PC-compatible) ---> ? ?
? ? Processor family (Pentium-4/Celeron(P4-based)/Xeon) ---> ? ?
? ? [ ] Generic x86 support ? ?
? ?[*] HPET Timer Support ? ?
? ?[*] Symmetric multi-processing support ? ?
? ? (2) Maximum number of CPUs (2-255) ? ?
? ?[*] Preemptible Kernel ? ?
? ?[*] Machine Check Exception ? ?
? ?[*] Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4 ? ?
? ?[*] check for P4 thermal throttling interrupt. ? ?
? ? < > Toshiba Laptop support ? ?
? ? < > Dell laptop support ? ?
? ? < > /dev/cpu/microcode - Intel IA32 CPU microcode support ? ?
? ? < > /dev/cpu/*/msr - Model-specific register support ? ?
? ? < > /dev/cpu/*/cpuid - CPU information support ? ?
? ? <M> BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL) ? ?
? ? High Memory Support (4GB) ---> ? ?
? ?[*] Allocate 3rd-level pagetables from highmem ? ?
? ? [ ] Math emulation ? ?
? ?[*] MTRR (Memory Type Range Register) support

==========================================
Graphics Support
==========================================
[*] Support for frame buffer devices ? ?
? ? < > Cirrus Logic support ? ?
? ? < > Permedia2 support ? ?
? ? < > CyberPro 2000/2010/5000 support ? ?
? ? [ ] IMS Twin Turbo display support ? ?
? ? < > VGA 16-color graphics support ? ?
? ?[*] VESA VGA graphics support ? ?
? ? < > Hercules mono graphics support ? ?
? ? < > nVidia Riva support ? ?
? ? < > Intel 810/815 support (EXPERIMENTAL) ? ?
? ? < > Matrox acceleration ? ?
? ? <M> ATI Radeon display support ? ?
? ? < > ATI Rage128 display support ? ?
? ? < > ATI Mach64 display support ? ?
? ? < > SIS acceleration ? ?
? ? < > NeoMagic display support ? ?
? ? < > 3Dfx Banshee/Voodoo3 display support ? ?
? ? < > 3Dfx Voodoo Graphics (sst1) support ? ?
? ? < > Trident support ? ?
? ? < > Permedia3 support ? ?
? ? < > Virtual Frame Buffer support (ONLY FOR TESTING!) ? ?
? ? Console display driver support ---> ? ?
? ? Logo configuration --->

==========================
Character Devices
==========================

<*> /dev/agpgart (AGP Support) ? ?
? ? < > ALI chipset support ? ?
? ? <M> ATI chipset support ? ?
? ? < > AMD Irongate, 761, and 762 chipset support ? ?
? ? < > AMD Opteron/Athlon64 on-CPU GART support ? ?
? ? <*> Intel 440LX/BX/GX, I8xx and E7x05 chipset support ? ?
? ? < > NVIDIA nForce/nForce2 chipset support ? ?
? ? < > SiS chipset support ? ?
? ? < > Serverworks LE/HE chipset support ? ?
? ? < > VIA chipset support ? ?
? ?[*] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ? ?
? ? < > 3dfx Banshee/Voodoo3+ ? ?
? ? < > 3dlabs GMX 2000 ? ?
? ? < > ATI Rage 128 ? ?
? ? <M> ATI Radeon ? ?
? ? < > Intel I810 ? ?
? ? < > Intel 830M, 845G, 852GM, 855GM, 865G ? ?
? ? < > Matrox g200/g400 ? ?
? ? < > SiS video cards ? ?
? ? < > ACP Modem (Mwave) support ? ?
? ? < > RAW driver (/dev/raw/rawN) ? ?
? ? < > Hangcheck timer
=================

I also loaded up the modprobe fglrx in the /etc/rc.d/rc.modules.
MTRR should be enabled if all possible.

Hope this helps some.
Hooper

Ps. I loaded QuakeIII linux last evening and ran a few time demo's. Pretty impressive.

I just noticed the following howto:

http://www.rage3d.com/content/articles/atilinuxhowto/

If anybody tries it, let us know.

I think the problem comes from the AGP driver... thx for the help and link..
I have MTRR compiled.
Im not sure which agpgart driver to use ... The fglrx driver seems to have its own AGP driver, the 2.6 kernel has a module fo it, and nVidia made one for 2.4

There will be 2 agp modules for 2.6.0. agpgart, and yourchipset-agp. In my case, it's intel-agp. As far as the kernel config goes, you want MTRR compiled into the kernel, and agpgart as a module. 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.

Also as a note, in the last set of drivers, I added agpgart and intel-agp to rc.modules so that they loaded at startup. With this release, I removed them because they now load with fglrx. I believe that is because I do NOT use ATI's internal agpgart during fglrxconfig...never have.

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.