I guess i did something wrong or something maybe i was suppose type ./before the sh file or something to run it i donno. But anyways i rebooted and tried it all again and it has the same problem when trying to run 3d stuff the screen turns black and locks up and only plays the music to the game

after reading what you just posted...
I remembered there was one other thing I did...(sorry I missed that)
I added nomodeset to lilo.

try rebooting again and when you get to the
lilo boot screen press the tab key and add
nomodeset to the line.

for example if "linux" is the one you pick...
then when you press the tab key (before you press enter)...
the line should be something like:

linux nomodeset

then press enter...and let us know how it went

I did everything you said but unfortunately its still doing the same thing. I tried it with supertux and the supertuxcart game. Supertux crashes the screen and only plays sound. And the cart game shows up on the screen in window mode but it displays everything ran together like it doesnt know how to display the graphics properly.

could you post your /var/log/Xorg0.log and /var/log/dmesg files?
it sounds like when the game crashes...
the whole system does not go down correct?
then try posting the results of the following commands
(as root) right after you run the game so we can see if
any error messages show up in the log files.

The output of
might be useful as well.

here is pastebin links to what you asked for

http://pastebin.com/Apgc6CZw
http://pastebin.com/sg4p9KRy
http://pastebin.com/4a1CM3JZ

And this is what T3slider said might be useful .

http://pastebin.com/tGaTwVEM

looking through the logs it looks like the driver is not
getting loaded with kernel modesetting turned on.

for example, I see this in my logs once everything was in place

Then what do i do to get it to load or whatever ?

it would probably(hopefully) help to maybe go over
everything again and double check that everything is in place.

1. make sure you are starting with the nomodeset option
(which can be added to lilo.conf so that you don't have to keep typing
it in each time you start your machine).
2. make sure the drivers are correctly blacklisted -
show us the contents of the file you created in /etc/modprobe.d/.
3. make sure the drivers are loaded with kms enabled before
starting X. - show us the file you created in /etc/rc.d/rc4.d/.
4. check the make sure the execute bit is set - show us the results
of (for example in my case it would be)
Also, could you post your /var/log/Xorg0.log file?

What do you mean by kms enabled

the file created in /etc/rc.d/rc4.d/...
is supposed to load the radeon driver with kernel modesetting
turned on (the modeset=1 option)

http://en.wikipedia.org/wiki/Mode-setting

for me this card/driver combo with kms is weird.

I have to disable kms when booting and make sure
the drivers do not get loaded.

if I let the driver load automatically
it tries to load with kms enabled but fails
and resorts to userspace modesetting.

and I have the problems I mentioned.

instead, I load the driver with kms enabled
before I startx (which is what the file in
/etc/rc.d/rc4.d/ is supposed to do).

and then the problems are gone.

well the files you wanted me to mcedit say the stuff you wanted them to have in them and i did the chmod command you said. So what else would need to be done then ?

If kcnewslackuser is starting in runlevel 3, the new file will never be run...correct? I would suspect that is the problem...maybe
should be placed into rc.local or at the very least be copied over to rc3.d/.

That said I have no experience with radeon drivers so I'm shooting in the dark.

yes but when he runs startx...
doesn't it then go into runlevel 4?
maybe the /etc/rc.d/rc.sysvinit file is not executable?

I do not load the driver from rc.local myself because
I do not like the way the display changes half way
through the boot up process when the driver gets loaded.

loading it the way I do...yes it still changes but
I don't really notice it since it happens so close
to when x starts (I briefly see one line of small text).

Otherwise the text is normal the first half of booting...
and then the display changes and the text is small
for the next half.