Are you sure you installed the fglrx? What happens when you "modprobe -v fglrx"?

If this fails then you haven't really follwed the installation guid because fglrx is not present in your system. Also your cardtype would be helpfull.

Sorry to see that you gave up.

Well, I haven't succeed so far. I hoped to solve it with gentoo but my kde still exhibits the same problem as before "DCOP ...".

I can use the normal Desktop and so I have to wait until a new driver is out and hope that this will be fixed then. It's annoying because now I have to boot into Windows to play.

Ok finaly got it .. it works
it looks like there went something wrong with online update of kernel
i made a new install and all updates and then all what is written here and
tadaaa 3500+ FPS
thx for all your help..

Which card do you have?

I have now managed to understand how to load either the ATI supplied RPM or the SuSe fglrx.rpm and km_fglrx.rpm. Either way I can get the XFree86.0.log to indicate
(II) fglrx(0): Direct rendering enabled

I run glxinfo and things are looking up:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
GLX_ATI_render_texture
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: (null)
OpenGL renderer string: (null)
OpenGL version string: (null)
OpenGL extensions:
glu version: 1.3
glu extensions:
Of course the (null) makes me think something is wrong.
Sure enough, glxgears gives no output.

I have come to realize all of this comes from the
643191 Sep 21 22:43 libGL.so.1.2 that comes from the ATI RPM.
So since the SuSe RPM's don't have this, I uninstall ATI fglrx and perform the steps listed previously. (Did I say the I really don't want to have to make a fresh install)
Still no problem with X and lsmod etc...
Now I get the error
fglrx: Failed to initialize QS connection!
And of course everything says and acts like MESA GL.

I would like to understand a bit more of what the heck is going on here.

Maybe this is a stupid question, but how do I "uninstall" all the steps described in sirra's instructions?? I'd like to go back and start again but I have no idea how to reverse the steps once they've been done, short of reinstalling SuSE and I'm not about to do that at the moment -- I'd rather do without 3D support entirely...

I also have a KT400 board (Asus K7V8X-X) and I also can't get it to work with my 9600Pro card. With me it fails with the attempt to load the agpgart module on bootup. I get a message saying that loading it failed, possibly because of "wrong parameters". However, the agpgart module worked fine with my FX5200 and the Nvidia driver, so I suspect that it has something to do with the combination of mainboard chipset, the Radeon hardware and the Radeon driver.

PS on the KT400: I now have the following statement from SuSE on the KT400. It's in the context of the NVidia driver but it may well apply to all graphics drivers because it's a basic problem with agpgart: "You have a mainboard with the VIA KT400 chipset. This chipset has problems with the AGP controller when the kernel's agpgart module is used. The reasons for this are not yet entirely clear. However, there is already a lot of information available in forums like kernel.org, nvnews and viaarena." (translated from German)

Another possibility is that there's a problem with the recent SuSE update of the Athlon kernel. However, I think I solved those problems because I also managed to recompile the DVB drivers for VDR (the Linux hard disk video recorder), for which it was necessary to reconfigure the new kernel source that came with the new Athlon kernel.

I kind of figured this might happen when I chose an ATI card instead of Nvida, but I decided to risk it because the 3D on the card is primarily for gaming under XP, so 3D in Linux would be a nice addition but wouldn't actually be essential. It would be nice if ATI could get their act together with Linux drivers as well as Nvidia has...sigh...

sirra462,
Just wanted to drop a line and say thanks to you and all those who have given helpful tips with this problem. I'm an absolute newb, but solving this problem has given me quite a bit of confidence. Thanks again!

For Uninstall I am using the rpm -e {package-name} Maybe this doesn't really work
and that is why I am getting messed up. I can verify at least that this is working for
swapping between MESA's and ATI's libGL simply by looking at the file sizes and dates.

There seems to be a new driver out on ATI' s website. Yesterday it was 3.2.8 and today it is 3.7, so to all who still have problems (like owners of a Radeon 9800XT) you might check out if it works now.

I haven' t tested it yet, but I try to install it right now and then I can provide some feedback.

I finally found a solution to get the Radeon 9800 XT also working with that driver.

I posted the additional explanation here

http://www.linuxquestions.org/questi...hreadid=131203

and I added a link to this thread, because the initial steps are the same.

I hope that this will help other users and prevent them to hunt for a solution as long as I did.

Happy Gaming!

Using the new driver (I don't actually believe it made a difference)
I got it to work. My 4 year old loves Tuxracer and I love FlightGear.

I believe the most significant discovery was that support for dual-head with different screens (two framebuffers) is NOT supported. At least not
with any of the instructions I have found. Dual head with Xinerama does not work either.
So I am stuck with one screen, two monitors.

Funny thing is that the fglrx driver does not play happy with my 19" Gateway monitor at 1600x1200. I could modeline tweek it to work but I decided to leave the two monitors at the same 1280x1024. I tried removing the comment on noDDC and that used to work with the older fglrx but the new one really seems to need it.

I am not sure if it helped, but I noticed a conflict with overlapping mtrr registers and I was able to remove that by adding a line to boot.local
echo "delete=2" > /proc/mtrr

(I am typing from memory so check you documentation from mtrr.txt for the real scoop)

Sorry, I haven' t taken into account the context of the thread. I didn' t mean that this works only with the new driver, it works also with 3.2.8 and most probably with other older drviers as well. Matter of fact I'm running it right now with 3.2.8 because 3.7.0 is not in my distri yet and I haven' t seen any advantages to try it.

I wonder why the high version jump. From the readme they added only some small stuff so I wondered why they went from 3.2.8 to 3.7.0.

I'm running suse 9.0 with the radeon 9700 pro. I followed the instructions with a fresh install but the fglrx module didn't load and agpgart is unused. I then used modprobe -v fglrx to discover what happened and I got the following output.

/sbin/insmod /lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o
Using /lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o
Symbol version prefix ''
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol irq_stat_R62a76ef0
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol remove_proc_entry_R448cb66c
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol __alloc_pages_R0808c439
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol remove_wait_queue_R17c614fa
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol register_chrdev_R3af595d9
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol create_proc_entry_R11ebb079
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol mem_map_Ra2dbbaa3
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol contig_page_data_R41e32c13
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol init_mm_Rf0e844ad
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol unlock_page_Rbc6adb81
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol highmem_start_page_R259972b3
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol add_wait_queue_R794cb9c3
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: unresolved symbol __free_pages_Rd705b629
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. Contact the module supplier for
assistance, only they can help you.

/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o failed
/lib/modules/2.4.21-99-default/kernel/drivers/char/drm/fglrx.o: insmod fglrx failed


Am i missing a license? any help would be appreciated.

Boot into linux in runlevel three by typing "linux 3" at the bootloader instead of just selecting linux... or by using other methods described in the instructions.

Then, just run sax and let it recreate the original configuration. That should at least get X running again.

Thank you so much Sirra462 for this excellent tutorial!!!

I had problems with my radeon 9700 in mandrake and for this reason switched to SuSE 9 and I almost freaked out when I got the same type of problem here.

Everything works fine now, exept sound. Thank you so much again!