actually, i had an rpm version of ati's driver and please tell me how to install the shell scripts

Install the RPM as root in a console, using:

rpm -i --force <ati package name>.rpm

It then should do what you want it to do. Scroll through the output and it should tell yo where the shell scripts are installed

and is it under the condition of mesa had already been uninstalled?

this is the output after i did
[root@localhost X4.3.0-3.2.5]# rpm -i --force fglrx-glc22-4.3.0-3.2.5.i586.rpm
*** Trying to install a precompiled kernel module.
*** WARNING ***
Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated
OpenGL will not work and 2D graphics will lack performance.

failed.
*** Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
probing for VMA API version...
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
patching 'drm_os_linux.h'...
doing script based build for kernel 2.4.x and similar
compiling 'agpgart_be.c'...
compiling 'agp3.c'...
compiling 'i7505-agp.c'...
compiling 'nvidia-agp.c'...
compiling 'firegl_public.c'...
linking of fglrx kernel module...
duplicating results into driver repository...
done.
==============================
- creating symlink
- recreating module dependency list
depmod: *** Unresolved symbols in /lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o
- trying a sample load of the kernel module
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol remap_page_range
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol __wake_up
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol unlock_page
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol register_chrdev
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol create_proc_entry
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol remove_wait_queue
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol highmem_start_page
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol kmap_prot
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol remove_proc_entry
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol add_wait_queue
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol _alloc_pages
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol mem_map
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol init_mm
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol __free_pages
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol kmap_pte
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. The module may be trying to access
GPLONLY symbols but the problem is more likely to be a coding or
user error. Contact the module supplier for assistance, only they
can help you.

/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: insmod /lib/modules/2.4.20-8/kernel/drivers/char/drm/
fglrx.o failed
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: insmod fglrx failed
failed.
depmod: *** Unresolved symbols in /lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o
Installed: qt3 (gcc 3.2) based control panel application
===
ATI display drivers successfully installed
please run 'fglrxconfig' now
===

[root@localhost X4.3.0-3.2.5]# cd /lib/modules/fglrx/build_mod/
[root@localhost build_mod]# ls
2.6.x agpgart_be.c agp.h firegl_public.o libfglrx_ip.a.GCC2 nvidia-agp.c
agp3.c agpgart_be.c~ fglrx.o i7505-agp.c libfglrx_ip.a.GCC3 nvidia-agp.o
agp3.o agpgart_be.o firegl_public.c i7505-agp.o make.log patch
agp_backend.h agpgart.h firegl_public.h libfglrx_ip.a make.sh
[root@localhost build_mod]# ./make.sh
ATI module generator V 2.0
==========================
probing for VMA API version...
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
patching 'drm_os_linux.h'...
doing script based build for kernel 2.4.x and similar
compiling 'agpgart_be.c'...
compiling 'agp3.c'...
compiling 'i7505-agp.c'...
compiling 'nvidia-agp.c'...
compiling 'firegl_public.c'...
linking of fglrx kernel module...
duplicating results into driver repository...
done.
==============================
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
==============================
[root@localhost build_mod]# cd ..
[root@localhost fglrx]# ls
build_mod fglrx.2.4.20-8.o fglrx.o
fglrx.2.4.18-17.7.x.o fglrx.2.4.21-1.1931.2.349.2.2.entbigmem-SMP.o make.2.4.20-8.log
fglrx.2.4.18-17.8.0.o fglrx.2.4.21-1.1931.2.349.2.2.ent.o make_install.sh
fglrx.2.4.20-6.o fglrx.2.4.21-1.1931.2.349.2.2.ent-SMP.o
fglrx.2.4.20-6-SMP.o fglrx_info.txt
[root@localhost fglrx]# ./make_install.sh
- creating symlink
- recreating module dependency list
depmod: *** Unresolved symbols in /lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o
- trying a sample load of the kernel module
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol remap_page_range
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol __wake_up
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol unlock_page
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol register_chrdev
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol create_proc_entry
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol remove_wait_queue
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol highmem_start_page
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol kmap_prot
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol remove_proc_entry
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol add_wait_queue
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol _alloc_pages
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol mem_map
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol init_mm
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol __free_pages
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: unresolved symbol kmap_pte
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. The module may be trying to access
GPLONLY symbols but the problem is more likely to be a coding or
user error. Contact the module supplier for assistance, only they
can help you.

/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: insmod /lib/modules/2.4.20-8/kernel/drivers/char/drm/
fglrx.o failed
/lib/modules/2.4.20-8/kernel/drivers/char/drm/fglrx.o: insmod fglrx failed
failed.

what's all the unsolved symbol problem?

K forget the insmod. I'm not sure what the unresolved symbol is, perhaps you got the driver for the wrong version of X?? Do you have glibc23? What distro do you have??

You shouldn't have needed to run insmod. The scripts do that for you.

Type these two commands:

/lib/modules/fglrx/build_mod/make.sh
/lib/modules/fglrx/make_install.sh

Then try again ~ All of the toying around MIGHT have screwed things up though. I did it my first few tries (and my solution to massively horrible screw ups is to reinstall Linux )

i believe i did post what i got after i run make.sh & make_install.sh
I don't know why!
But i did download the 3.2.0 version from ati's website.
But the case was i had installed everything from my cd & i am sure it's everything because when i was reinstalling my system i had chose everything during the process of chosing packages!
Why?
did ya got ya own radeon work already?

Mine's installed and runs fine ~ Have you read through ATI's documentation that is provided with the RPM?

What version of the kernel are you using?

my kernel was the one who had shipped with redhatlinux9
and i should be 2.4.22 i believe
Could u tell me something about your sucessful story?
What kind graphics card do you have?

ATI makes $hit Linux drivers.
You usually end up using generic drivers, and that's why you can't get accelerated graphics.

Do yourself a favor: get an nVidia card. They provide GOOD drivers so you can kick some 3D ass with Linux.

Heh heh, me too!!

Heehee ~ Speaking of which, I'm just setting up my newest installation of Redhat just now...I gotta stop screwin around so much with my system...

I'm using a Radeon 9800 Pro, and I completely agree with electron_lemon. My roommate is using an nVidia card and had a slight bit of trouble selecting the right driver, and the installation wasn't exactly easy...but once you get the correct driver selected and running you install painlessly and without issues thereafter.

ATI on the other hand isn't the same story...it's easy to pick the driver, simple to get the install running, but if it fails you have no idea what you did wrong. If you're really die hard at getting 3D acceleration then reinstall Slackware. But I will tell you that I had an incredible amount of difficulty installing my drivers onto Gentoo (which is my only experience with power distros) and so much that I just gave up (and also ended up going back to Redhat. I need to have a life.) So your problem could be, and probably is, stemming from a kernel that just doesn't like the driver. It could happen. The mesa drivers found their way back into your system, and that'll play a role in it.

Anyhew ~ My solution to serious messes like this is to whip out a few zip disks, back everything up, and completely clean out the harddrive like nobody's business and start over clean. When you're reinstalled, install the ATI driver first. If it still doesn't work, reinstall. Fortunately for me, on Redhat this is a simple process of leaving my computer on to install for 30 mins or so at a time if I need one or two extra tries, and I go and occupy myself. But I'll tell you, it works. I've never used Slackware though so I'm not too keen on how the install process goes.

My only advice to you is to read the documentation provided. It may as well be written in Japanese, because I didn't understand half of it, but you may find your problem in there. Just be careful that you don't misdiagnose the problem and go about solving it the wrong way....I did that....then I felt like an a$$ when I realized how easy the problem was to fix...

You might want to try not uninstalling mesa maybe??

(I didn't)

tricky_linux, what distro are you using??

how do u not install mesa? it was there without my say so