Mine _seem_ to work OK, but they are not stable.
They crash on UT2003,UT,SOF and other games at the same point
I have SMP athlon?
Any ideas here?
Or how to debug this?

You may want to check Rage3D's linux forum I don't think ATi drivers support SMP on Linux just yet.

Hi all

Last ATI Raden drivers for XFree 4.1, 4.2, 4.3 you can download form
http://www.schneider-digital.de/html...nload_ati.html

I've got a 9800 Pro in my new box...and It's taken me three days to get all the issues sorted.
This is for a raedon on an nforce motherboard.
If your running a 2.4.20 kernel you need to patch it with the nvidia agp patch that can be found in the latest nforce driver package, if your running 2.4.21 (as I am) you need to apply this patch,
http://penna.dyn.dhs.org/~penna/linu...-agpgart.diff.

Then you need to rebuild your kernel - pay attention to the instructions in the readme.txt that comes in the nvagp directory (part of the nforce package), then you need to build the fglrx kernel module against your new kernel (instructions and scripts are in the package from schneider-digital).
I'm getting 207 fps in quake3 at 1280x1024 with all the eye candy on and glxgears is giving me the following,
Details of my new system,
AthlonXP 3000+
Asus A7N8X Deluxe
Saphire 9800 Pro
512MB Corsair XMS3200 (2x256)
Saegate Barracuda V 80gb SATA
Samsung SyncMaster 172t LCD panel

Installing slackware to the SATA drive took a bit of work, as did getting it working at a decent speed without lockups.

Hi, I have exactly the same system specs as you Aussie but seeing this is my first day using Linux I am finding it slightly difficult to comprehend. Could you please enlighten me?

Woops! I installed those drivers from schneider-digital and i now dont have a desktop! If anyone can help me out of that as well it would be very much appreciated.

First make sure you boot into console and not to X, re run the fglrxconfig script to replace your current XF86Config file with ATi's settings. Then just try first launching X, if it does not work, then re run script... usually that helps, if you keep having problems, post back.

How do you boot to console? Via safe mode?

<edit> I reinstalled linux by the way to get back to KDE.

You enter into console by changing the runlevel of your distro, there should be a file called inittab under /etc, there should be a number coded set of runlevels, check which corresponds to pure console (or pure multiuser) Usually (as it is a convention in Red Hat) runlevel 0 and 6 mean halt (and poweroff) and reboot respectively, 1 is not used (or used by the safemode console) 2 is multiuser without networking capabilities, 3 full multiuser with network (no X), 4 is not used (to be a custom mode) and 5 is full Multiuser under X. You must edit the file to reflect the desired runlevel in the line
Alternatively you can switch the runlevel by exiting to a system console (by pressing ctrl+alt+F1-F6), log in as root, and then just issue the command init followed by the desired runlevel, eg. init 3 (in my case). Once in the console, go to the directory where the driver rpm lies, install it and switch back to X runlevel, in my case init 5.

Ok, got it. I have got to the console and set up fglxrconfig (or whatever it is called) and i issue the command startx afterwards but X refuese to start because it still cant find any displays.

Thanks for putting up with me, i know Windows inside out but when it comes to Linux, i'm not so sure at the moment!

You'll get the feel of it, it is not that different, but of course there are fundamental differences, but not when it comes to the interface... Anyway, usually reconfiguring with the script fglrxconfig solves most of the problems, although you may have some garbage when it comes to the configuration file X looks up (the one the script creates) and my got confused. To look into this first posibility (the most likely) go the location of this configuration file, i.e /etc/X11. If you ls the contents of that directory, you'll probably find many intances of a file called XF86Config*, in order to have a clean configuration file, I'd suggest to delete any instance of it by rm XF86Config* (as root) then re-run the script, and then (it is my personal recomendation) rename the resulting file (XF86Config-4) to plain XF86config.

Prior releases of XFree86 4 (4.0, 4.1 & 4.2) looked to the file XF86Config-4 to apply the cofiguration to the version 4 of the X Free Window system, and the XF86Config to the versions 3.x, this in systems whith both X systems. But as of version 4.3 the configuration file is plain XF86Config (as in version 3.x), so if you have XFree86 version 4.3 (you may know about the version by looking at the log file in /var/log/XFree86.0.log, it should be in the one of the top lines in that file), my suggestion would be to rename the XF86Config-4 file to XF86Config by:
In the event that doesn't work, make sure your monitor is connected to the VGA output of the card, if you configured the driver to use only one monitor (the DVI corresponds to the [b[second[/b] head!) otherwise if you have a DVI connected monitor choose dualhead mode in clone mode.

That should be the easiest to trouble shoot the No screen found error message.

It turned out to be a garbled file, so now it does attempt to work. I say attempt becasue all it does is give me a blank screen. I can here disk activity so the X window system is doing its stuff, its just that I can't see it! I have tried the most possible configurations within the scope of my hardware but to no avail.

Almost there (i think!).

In my experience, some times (rarely) the driver intialises not accordingly to your XF86Config specs, when this happens to me, I simply go off to a console (ctrl+alt+F1) log in as root and type
What this does is that it will kill the X server, but since I am under graphical mode, the deamon GDM (the gnome display manager) restarts, forcing X to restart and hence to re-read the config file. Try that... or may be you misconfigured your Hsync/VSync values? (I always check anyhow, you never know when you specified an out of range value).

I did CTRL + ALT + F1 and found that X was actually hiding an error from me (here goes!):

fglrx: No matching device section for instance (busID PCI:3:0:1) found

fglrx.o: init module: no such device

it then says 2 lines about 'insmod failed fglrx.o'

fglrx(0): DRIScreenInit Failed!


Something wrong with the drivers i guess?!

Ok, try uninstalling the drivers (rpm -e fglrx-blah-blah) and then reinstall it. Alternatively you may simply erase fglrx.o from /lib/modules/<kernel version>/kernel/drivers/char/drm (or simply change to /lib/modules and make a find . -iname fglrx.o and change to the directory find tells you it is on). Then just recompile the module:
Go to /lib/modules/fglrx/build_mod/ and execute the script make.sh, then change to upper directory and execute the script make_install.sh, pay close attention to the messages displayed by make_install.sh, may be the same insmod message would appear.

Remember that all these steps should be made OUTSIDE X, i. e in pure console.

Possible causes for which the module is not loading:
The first that comes to mind is to check your kenrel configuration, if you run a custom kenrel, make sure NO other DRM modules are compiled INTO the kernel (specially the Radeon module, which recognizes the Radeon, or any other like the tdfx module for 3dfx cards), otherwise the kernel will complaint about an already loaded module, and will not be able to load the fglrx module.

So check your kernel (if you configured it yourslf) or install an upgraded kernel version from your distribution's web services, and try again recompiling the module with the script make.sh under /lib/modules/fglrx/build_mod