It has a lot to do with Xorg server as well.
Nice read: »wiki.archlinux.org/index.php/ATI_Catalyst
BUT, the great thing about Arch is how transparent everything is... so how does Arch get the installer to work!?!?
That is the magic.
So we have a download from Arch for an ati_make and a makefile_compat and the driver itself from AM... Ubuntu???
Hmmmm.... So the driver itself is patched/worked/maintained by Canonical. Ubuntu is a Debian distro... this should be able to be broken down and installed on Siduction.
The Arch linux make file was altered:
said by Vi0L0 :
it is ati's code from their make.sh file, modified a bit to fit our arch linux system, used inside PKGBUILD
And Arch linux included makefile_compat patch is simplistic (looks to make 2.6 kernel's available for use):
--- 10.10/common/lib/modules/fglrx/build_mod/2.6.x/Makefile 2010-09-22 09:15:33.000000000 +0200
+++ 10.10/common/lib/modules/fglrx/build_mod/2.6.x/Makefile 2010-10-01 17:57:21.057820899 +0200
@@ -66,6 +66,7 @@
+ -DCOMPAT_ALLOC_USER_SPACE=$(COMPAT_ALLOC_USER_SPACE) \
# on first call from remote location we get into this path
Show off that hardware: join Team Discovery and Team Helix