To me, it looks like the mesa in 14.1 is too old for the cards you have. Coming from personal experience, it probably isn't worth attempting to upgrade mesa itself, because it requires a lot of dependencies to be upgraded as well (including X itself). I tried looking back and didn't see anything, but have you tried -current? It has a newer version of X and mesa. It may not be the best solution since it is unsupported and can cause breakage, but it might be worth the hassle if your cards work properly.

Already stated that I'm using slackware-current in my previous posts.

Bummer. I must've missed it.

Have you tried building a newer version of Mesa than what -current offers? There's 10.5.9 if you want to stick with the same series and 10.6.1 if you want the newest version.

If that doesn't work, I might be commiting a forum felony by suggesting this, but it might be worth opening a new thread on the main forum since this seems like a bug with -current and you're more likely to get better visibility there.

Already tried them, even tried ReaperX7's slackware so version, but no luck there either.

I have a feeling that just one thing is missing but only other error I see in xorg log is something to do with systemd, but slackware doesn't use that, maybe that's what is missing.

That systemd error is a non-issue. There was talk of forum members to get Pat to edit the build so the error didn't show, but I don't think Pat ever changed it.

Your hardware might require a newer xorg than what Slackware ships. I tried to find an easy way to download a newer version when I did a massive upgrade of my graphics stack back in January, but after a short time looking, I decided it probably wasn't worth the hassle to try and find it, then go through the difficulty of building it.

Have you tried grabbing the latest ati drivers specifically from xorg to see if they are any different than what's included with Slackware's?

Out of curiousity, does the proprietary driver work? I'm assuming you have no desire to run it since you're trying so hard to get the FOSS drivers working, but I'm curious if it even works with your hardware and the versions of programs Slackware includes. It might help us narrow down what could be the likely culprits of your problem.

Yep tried the ati and no haven't tried proprietary and you're right I have no desire to run it, need open source for other programs I intend to use, thanks for your help anyway.

It might still be worth installing the proprietary drivers so we can see if those work. Doing this might help narrow down what could be causing the problems with the FOSS drivers. I was not suggesting to use them permanently, just temporarily to help in the diagnosis process.

Sure I'll give that a try but first I'm gonna try to rebuild xorg with --enable-glamor to see if that works, I'll let you know what happens.

It wasn't the glamor, anyway read that they are built in now anyway, tried the proprietary drivers, they didn't work right away had the same black screen with curser blinking in the top left hand corner until I made a xorg.conf then it did boot in but with vesa until I modified the xorg.conf as per instructions found on the web then I had 3d support. Would like to have the mesa drivers working instead, there's one thing that's been bothering me, when installing slackware and it comes to the services section, I just press enter for the defaults already showing. Could it be that I need to add or remove a certain service, I don't know anything about that, if anyone knows if that could be the difference?

There is no service involved. You can check running as root pkgtool then choosing Setup in the menu.

Well apparently I learned that. " The reason why we need to load dri2/glamoregl earlier is both glx-xserver and glamor are a dri2 loader. And glx-xserver side has a own glapi/dispatch table implementation which is a subset of the standard mesa's implementation. So if the glx module is loaded earlier than dri2/glamoregl, then we will get an incomplete dispatch table and everything is broken in glamor then." from this link: http://www.freedesktop.org/wiki/Software/Glamor/

Unfortunately I don't know how to rectify this.

I just don't know what makes you think that glamor is involved in you issue.

What could help is see a full /var/log/Xorg.0.log. Preferably use some service like pastebin and provide the link instead of copy/pasting the result, or at least use [CODE] wrapping tags.

Also, next time please open your own thread instead of highjacking an existing one with another topic, as it is hard to follow a thread with mixed topics.

Already posted peviously

Fatal server error:
"destination is framebuffer incomplete: incomplete/missing attachment [8cd7]"

Was in my xorg log and that is exactly the error in that link to do with glamor.

No. This:

is just one line and could be misleading taken out of context.

So, please provide the full log if you really request help.

Everything else loaded just fine it was right when glx got loaded or attempted to be loaded that the error happened indicating that glx was loading before dri2 and glamor-egl.