cchtml.com - User contributions [en]

Slackware

2008-01-31T20:15:28Z

151.66.33.40:

Welcome. This bare-bone little faq details how to get fglrx working on slackware or 64 bit porting. 
You can use the '''internal Slackbuild''' or the '''external Slackbuild''' in order to have fglrx packaged for Slackware. 
The '''internal Slackbuild''' is distributed within the official ATI installer. 
The '''external Slackbuild''' is for driver version < 8.37.6 and for the latest driver patches. 
You can find more detailed information about both of them on the following links. 
Enjoy!

==Installation==
'''Internal Slackbuild'''
*[[ATI-Wiki-Slackbuild (ENG)|Wiki for internal Slackbuild (ENG)]]
*[[ATI-Wiki-Slackbuild (ITA)|Wiki per lo Slackbuild interno (ITA)]]
 
'''External Slackbuild'''
*[[ATI Slack-Packager (ENG)|Wiki for external Slackbuild (ENG)]]
*[[ATI Slack-Packager (ITA)|Wiki per lo Slackbuild esterno (ITA)]]

==Tips and Tricks==
'''Slamd64''' - You need to install GCC 3.3 libraries for fglrx. Download and install [http://www.tfd.chalmers.se/~berend/slamd64/ cxxlibs5]. You will also need to install the 32 bit compatibility libraries in /c.

==Related Resources==

{{VCT}}
[[Category:Distributions]]

Slackware

2008-01-25T22:25:13Z

151.66.33.40:

Welcome. This bare-bones little faq details how to get fglrx working on slackware. 
You can use the '''internal Slackbuild''' or the '''external Slackbuild''' in order to have fglrx packaged for Slackware. 
The '''internal Slackbuild''' is distributed within the official ATI installer. 
The '''external Slackbuild''' is for driver version < 8.37.6 and for the latest driver patches. 
You can find more detailed information about both of them on the following links. 
Enjoy!

==Installation==
*[[Slackware Installation Guide|Installation Guide]]
*[[ATI-Wiki-Slackbuild (ENG)]]
*[[ATI Slack-Packager (ENG)]]
*[[ATI Slack-Packager (ITA)]]

==Tips and Tricks==
'''Slamd64''' - You need to install GCC 3.3 libraries for fglrx. Download and install [http://www.tfd.chalmers.se/~berend/slamd64/ cxxlibs5]. You will also need to install the 32 bit compatibility libraries in /c.

==Related Resources==

{{VCT}}
[[Category:Distributions]]

Slackware: ATI SlackBuild (ENG)

2008-01-25T22:00:45Z

151.66.33.40: /* Minimal X.Org server configuration */

== Introduction ==
This wiki explains how to install the proprietary ATI drivers in a Slackware Linux distribution, creating, thanks to a SlackBuild, packages that can be installed through the '''installpkg''' command. 
This wiki DOES NOT explain how to improve performance. In particular, It provides only a minimal description of how to set up the X.Org server with the only purpose of loading the proprietary drivers (a description on how to configure the X.Org server to increase performance can be found here).
All commands starting with a '#' must be executed with root rights, while commands beginning with '$' can be performed by a user without such rights.

== Proprietary ATI Drivers and ATI Catalyst ==
Since 21 November 2007, ATI drivers have changed the name and the number version. The new drivers, which were first mentioned only as Proprietary ATI Driver, are now called ATI Catalyst. Moreover, the version number has passed from 8.XX.X to 7.XX.

When in this wiki we will talk about drivers version <8.37.6, we will refer implicitly to the old driver, such as Proprietary ATI Driver, while the new ATI Catalyst have a number version >= 8.37.6, even if, for instance, have a release number 7.11.

== Getting all the necessary ==
The proprietary ATI drivers can be downloaded from the [http://ati.amd.com/support/driver.html official web site], after selecting the Linux x86 operating system (or Linux x86_64) and selecting your video card, pressing the “go” button takes you directly into the download page from which you can download the installer (which henceforth we call installer.run). 
Since drivers also contain a kernel module which will be compiled directly on your system, you'll need the kernel source currently installed in the system as well.

'''NOTE:''' Drivers for x86 and x86_64 architectures are equivalent. 
The installer '''contains files for both architectures''', then It will be the compilation process and the package
creation process to choose the appropriate files.
This means that '''the SlackBuild will be good for Slackware and for Slackware 64-bit portings (Slamd64, Bluewhite64, etc. ...)'''.

== Important notice ==
If the downloaded driver version is less than 8.37.6, then you need to know from now that it will not work onto X.Org 7.2 server (or 1.3).

== How to create Slackware packages ==
The packages creation follows two different ways depending on whether you use the official driver version '''< 8.37.6''' or '''>= 8.37.6'''. or new '''ATI Catalyst'''. The first way uses what is called '''external SlackBuild''' while the second way what we will call '''internal SlackBuild'''. In both cases the two packages will be created and they can be installed by Slackware '''installpkg''' utility. So let's see the two cases saying that the program that here is called installer.run is the installer downloaded from ATI web site.

'''NOTE:''' The external SlackBuild use is not limited to the driver <8.37.6 but you can use it
(and at times we will see that It's the only alternative) with all versions of ATI drivers.

=== Drivers version <8.37.6 (external SlackBuild) ===
For these types of drivers I've created an '''external SlackBuild''' for Slackware and I made a package that can be found at: http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz
To create Slackware packages simply run:
# installpkg ati-slack-packager-current-noarch-1.tgz
# sh installer.run -- buildpkg custom-package/Slackware

=== Drivers version >= 8.37.6 or new ATI Catalyst (internal SlackBuild) ===
For these drivers I've sent the SlackBuild directly to ATI that has insert it inside the installer, then simply run:
# sh installer.run --buildpkg Slackware/All

== What do created packages contain? ==
The two packages created by SlackBuild, that we'll call ''fglrx-module'' and ''fglrx-x'' contain, respectively, the kernel module and the X.Org server driver currently installed in the system. In this way, if you upgrade the kernel or the X.Org server, you can create only one package.

=== Creating only fglrx-module package ===
To create just the package containing the kernel module for the currently installed kernel, simply run the installer with the ''Only_Module'' option
So with '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_Module
With internal SlackBuild:
# sh installer.run --buildpkg Slackware/Only_Module

=== Creating only fglrx-x package ===
To create just the package containing the X.Org driver currently installed in your system, simply run installer with ''Only_X'' option
With '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_X
With '''internal SlackBuild''':
# sh installer.run --buildpkg Slackware/Only_X
== Minimal X.Org server configuration ==
Once installed the two indicated packages, you must tell to the X.Org server to use ATI proprietary drivers, to do this we must check if the xorg.conf file, which is usually located in the ''/etc/X11/'' directory, contains the following items:

<tt>
Section "Module"
...
Load "dri"
Load "glx"
...
EndSection

Section "Device"
...
Driver "fglrx"
...
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection
</tt>

== Installation checking ==
To see if proprietary ATI drivers are properly installed run the command:
$ fglrxinfo
On my computer the output is:
display::0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 2.0.6650 (8.39.4)
== Remove installed packages ==
To remove installed packages you can use the '''removepkg''' utility. However, there are aspects that should be considered:
* The packages' removing don't delete fglrx's driver configuration files, these files are located in ''/etc/ati'' directory
'''NOTE:''' The /etc/ati/custom-package directory, if exists, contains the external SlackBuild and therefore should not be deleted.
* The fglrx-x package contains ATI's OpenGL libraries, and these libraries are located in the same directory of the Mesa libraries, so when you install the fglrx-x package Mesa OpenGL libraries are overridden. To restore the situation you should simply reinstall the package containing these libraries, like:
  x11 
for slackware 11, or: 
  mesa 
for slackware 12.
== Known problems ==
=== FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'paravirt_ops' ===
The error occurs during module compilation and It's due to the fact that the kernel was compiled with the option of paravirtualization active. This option among other things, prevents to load, and then to compile, modules that do not have the GPL license. Since that ATI drivers don't have this type of license, they aren't compiled. 
To work around this problem you can: 
==== Disable kernel paravirtualization option ====
The paravirtualization option is called '''CONFIG_PARAVIRT''' and generally is in the '''Processor type and features''' kernel submenu.
==== Patch ATI drivers ====
This operation is illegal because It changes the type of license issued by ATI in a GPL license. I wrote the ati_to_gpl.patch patch but I do not take any responsibility, I do not use It and I discourage the use in order to prefer the alternative to disable the paravirtualization kernel option. To use this patch You need to:
* Download and install (through installpkg) the external SlackBuild ati-slack-packager
* Copy the patch in the ''/etc/ati/custom-package/patch'' directory
* Run the installer with the command
# sh installer.run --buildpkg custom-package/Slackware
The external SlackBuild will notice the presence of the patch and It will apply It.
To uninstall the patch simply delete It from ''/etc/ati/custom-package/patch'' directory.
=== Using GLX_SGIX_pbuffer FGLTexMgr: open of shared memory object failed (Permission denied) __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!! ===
This problem is due to the lack of SHM filesystem (now called tmpfs), that is virtual memory filesystem. To work around this problem you must:
* Add into ''/etc/fstab'' file the following line:
shm /dev/shm tmpfs defaults 0 0
* Then mount the filesystem through:
# mount /dev/shm
Obviously the kernel must be predisposed for the "mounting" of this filesystem, in particular the
kernel option that must be enabled is '''CONFIG_TMPFS''' that is generally placed in '''File system --> Pseudo filesystems''' submenu. However all the compiled kernel generally have this option enabled.
=== kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel ===
The complete mistake is something like this: 
<tt>
Error:
kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel.
they are versioned as ""
instead of "`uname -r`".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
</tt>
The error, also if explained, could be not clear. In practice It results from the fact that the symbolic link: 
/lib/modules/`uname -r`/source 
/lib/modules/`uname -r`/build 
don't point to the directory where are inserted the current kernel sources (which is generally ''/usr/src/linux- 'uname-r'''). It happens to those who use a kernel contained in Slackware, so I will try to explain It in terms of Slackware "packages". This can happen:
* because the kernel source were not installed. In this case should be enough to install the source package which can be found in Slackware k/ directory. However, It is not granted that the problem will be solved, You'll need to see the second reason why there is an error.
* because sources (also if installed) do not reflect the settings of the current kernel. The new Slackware 12 has some precompiled kernels (which means different settings), while just a single package for the sources (unless seeing the branch extra/). In particular, the sources are for the SMP kernel and so if you use a non-SMP kernel can appear this error. To avoid this, after making sure that the package source has been installed, do simply the following:
# cd /usr/src/linux
# cp /boot/config .config
# make
running make, in addition to compiling the kernel modules (which we will not use), some header files are regenerated, and they will reflect the kernel configuration (as it's set in the .config file).
=== Driver 8.39.4 logo ===
This "bug" in 8.39.4 drivers results from the fact that ATI developers don't update the packager maintainers before the official releases. It should be nice first if they did test us official releases in order to certify the proper functioning of the scripts for creating packages. To solve the problem It's necessary to use the external SlackBuild as described here.
=== amdcccle don't start on slackware 12 ===
Many users of the X.Org 7.2 (or 1.3) server version fail to start properly the Catalyst. The command to run the Catalyst is:
# amdcccle
For this problem it seems there is no solution yet, but we are working on to solve it.

== Useful links ==
The discussion thread from which it was derived this article: 
http://www.slacky.eu/forum/viewtopic.php?t=18134&highlight= 
An alternative to official ATI drivers is given by the following website: 
http://www.schneider-digital.de/ 
A wiki in italian about installing and configuring ATI drivers (open source and proprietary) can be found at:
http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux

== Conclusion ==
Proprietary ATI drivers for many modern desktop and notebook PC seems are almost the only alternative to the use of 3d acceleration with linux. Unfortunately ATI developers don't make back porting and then users using drivers' version older than 8.37.6 will never go to X.Org server version 7.2 (or 1.3). Let's hope that Mesa drivers can also be used for these cards.
The '''external SlackBuild''' is always updated, this SlackBuild is thought to work with all ATI driver versions, both older and newer than 8.37.6. Many patches are applied in fact only after the online publication of official driver, then it may happen that '''internal SlackBuild''' included in the drivers fail where the '''external SlackBuild''' ati-slack-packager ends successfully. Also, because It hasn't been tested the SlackBuild with all possible versions of ATI drivers and kernels, It could happen that the module compilation fails. If so, feel free to write me at '''spina80@freemail.it''' posting me the output generated by Only_Module option.

Slackware: ATI SlackBuild (ENG)

2008-01-25T13:58:57Z

151.66.33.40:

== Introduction ==
This wiki explains how to install the proprietary ATI drivers in a Slackware Linux distribution, creating, thanks to a SlackBuild, packages that can be installed through the '''installpkg''' command. 
This wiki DOES NOT explain how to improve performance. In particular, It provides only a minimal description of how to set up the X.Org server with the only purpose of loading the proprietary drivers (a description on how to configure the X.Org server to increase performance can be found here).
All commands starting with a '#' must be executed with root rights, while commands beginning with '$' can be performed by a user without such rights.

== Proprietary ATI Drivers and ATI Catalyst ==
Since 21 November 2007, ATI drivers have changed the name and the number version. The new drivers, which were first mentioned only as Proprietary ATI Driver, are now called ATI Catalyst. Moreover, the version number has passed from 8.XX.X to 7.XX.

When in this wiki we will talk about drivers version <8.37.6, we will refer implicitly to the old driver, such as Proprietary ATI Driver, while the new ATI Catalyst have a number version >= 8.37.6, even if, for instance, have a release number 7.11.

== Getting all the necessary ==
The proprietary ATI drivers can be downloaded from the [http://ati.amd.com/support/driver.html official web site], after selecting the Linux x86 operating system (or Linux x86_64) and selecting your video card, pressing the “go” button takes you directly into the download page from which you can download the installer (which henceforth we call installer.run). 
Since drivers also contain a kernel module which will be compiled directly on your system, you'll need the kernel source currently installed in the system as well.

'''NOTE:''' Drivers for x86 and x86_64 architectures are equivalent. 
The installer '''contains files for both architectures''', then It will be the compilation process and the package
creation process to choose the appropriate files.
This means that '''the SlackBuild will be good for Slackware and for Slackware 64-bit portings (Slamd64, Bluewhite64, etc. ...)'''.

== Important notice ==
If the downloaded driver version is less than 8.37.6, then you need to know from now that it will not work onto X.Org 7.2 server (or 1.3).

== How to create Slackware packages ==
The packages creation follows two different ways depending on whether you use the official driver version '''< 8.37.6''' or '''>= 8.37.6'''. or new '''ATI Catalyst'''. The first way uses what is called '''external SlackBuild''' while the second way what we will call '''internal SlackBuild'''. In both cases the two packages will be created and they can be installed by Slackware '''installpkg''' utility. So let's see the two cases saying that the program that here is called installer.run is the installer downloaded from ATI web site.

'''NOTE:''' The external SlackBuild use is not limited to the driver <8.37.6 but you can use it
(and at times we will see that It's the only alternative) with all versions of ATI drivers.

=== Drivers version <8.37.6 (external SlackBuild) ===
For these types of drivers I've created an '''external SlackBuild''' for Slackware and I made a package that can be found at: http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz
To create Slackware packages simply run:
# installpkg ati-slack-packager-current-noarch-1.tgz
# sh installer.run -- buildpkg custom-package/Slackware

=== Drivers version >= 8.37.6 or new ATI Catalyst (internal SlackBuild) ===
For these drivers I've sent the SlackBuild directly to ATI that has insert it inside the installer, then simply run:
# sh installer.run --buildpkg Slackware/All

== What do created packages contain? ==
The two packages created by SlackBuild, that we'll call ''fglrx-module'' and ''fglrx-x'' contain, respectively, the kernel module and the X.Org server driver currently installed in the system. In this way, if you upgrade the kernel or the X.Org server, you can create only one package.

=== Creating only fglrx-module package ===
To create just the package containing the kernel module for the currently installed kernel, simply run the installer with the ''Only_Module'' option
So with '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_Module
With internal SlackBuild:
# sh installer.run --buildpkg Slackware/Only_Module

=== Creating only fglrx-x package ===
To create just the package containing the X.Org driver currently installed in your system, simply run installer with ''Only_X'' option
With '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_X
With '''internal SlackBuild''':
# sh installer.run --buildpkg Slackware/Only_X
== Minimal X.Org server configuration ==
Once installed the two indicated packages, you must tell to the X.Org server to use ATI proprietary drivers, to do this we must check if the xorg.conf file, which is usually located in the ''/etc/X11/'' directory, contains the following items:

<tt>
Section "Module"
...
Load "dri"
Load "glx"
...
EndSection
Section "Device"
...
Driver "fglrx"
...
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
</tt>
== Installation checking ==
To see if proprietary ATI drivers are properly installed run the command:
$ fglrxinfo
On my computer the output is:
display::0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 2.0.6650 (8.39.4)
== Remove installed packages ==
To remove installed packages you can use the '''removepkg''' utility. However, there are aspects that should be considered:
* The packages' removing don't delete fglrx's driver configuration files, these files are located in ''/etc/ati'' directory
'''NOTE:''' The /etc/ati/custom-package directory, if exists, contains the external SlackBuild and therefore should not be deleted.
* The fglrx-x package contains ATI's OpenGL libraries, and these libraries are located in the same directory of the Mesa libraries, so when you install the fglrx-x package Mesa OpenGL libraries are overridden. To restore the situation you should simply reinstall the package containing these libraries, like:
  x11 
for slackware 11, or: 
  mesa 
for slackware 12.
== Known problems ==
=== FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'paravirt_ops' ===
The error occurs during module compilation and It's due to the fact that the kernel was compiled with the option of paravirtualization active. This option among other things, prevents to load, and then to compile, modules that do not have the GPL license. Since that ATI drivers don't have this type of license, they aren't compiled. 
To work around this problem you can: 
==== Disable kernel paravirtualization option ====
The paravirtualization option is called '''CONFIG_PARAVIRT''' and generally is in the '''Processor type and features''' kernel submenu.
==== Patch ATI drivers ====
This operation is illegal because It changes the type of license issued by ATI in a GPL license. I wrote the ati_to_gpl.patch patch but I do not take any responsibility, I do not use It and I discourage the use in order to prefer the alternative to disable the paravirtualization kernel option. To use this patch You need to:
* Download and install (through installpkg) the external SlackBuild ati-slack-packager
* Copy the patch in the ''/etc/ati/custom-package/patch'' directory
* Run the installer with the command
# sh installer.run --buildpkg custom-package/Slackware
The external SlackBuild will notice the presence of the patch and It will apply It.
To uninstall the patch simply delete It from ''/etc/ati/custom-package/patch'' directory.
=== Using GLX_SGIX_pbuffer FGLTexMgr: open of shared memory object failed (Permission denied) __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!! ===
This problem is due to the lack of SHM filesystem (now called tmpfs), that is virtual memory filesystem. To work around this problem you must:
* Add into ''/etc/fstab'' file the following line:
shm /dev/shm tmpfs defaults 0 0
* Then mount the filesystem through:
# mount /dev/shm
Obviously the kernel must be predisposed for the "mounting" of this filesystem, in particular the
kernel option that must be enabled is '''CONFIG_TMPFS''' that is generally placed in '''File system --> Pseudo filesystems''' submenu. However all the compiled kernel generally have this option enabled.
=== kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel ===
The complete mistake is something like this: 
<tt>
Error:
kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel.
they are versioned as ""
instead of "`uname -r`".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
</tt>
The error, also if explained, could be not clear. In practice It results from the fact that the symbolic link: 
/lib/modules/`uname -r`/source 
/lib/modules/`uname -r`/build 
don't point to the directory where are inserted the current kernel sources (which is generally ''/usr/src/linux- 'uname-r'''). It happens to those who use a kernel contained in Slackware, so I will try to explain It in terms of Slackware "packages". This can happen:
* because the kernel source were not installed. In this case should be enough to install the source package which can be found in Slackware k/ directory. However, It is not granted that the problem will be solved, You'll need to see the second reason why there is an error.
* because sources (also if installed) do not reflect the settings of the current kernel. The new Slackware 12 has some precompiled kernels (which means different settings), while just a single package for the sources (unless seeing the branch extra/). In particular, the sources are for the SMP kernel and so if you use a non-SMP kernel can appear this error. To avoid this, after making sure that the package source has been installed, do simply the following:
# cd /usr/src/linux
# cp /boot/config .config
# make
running make, in addition to compiling the kernel modules (which we will not use), some header files are regenerated, and they will reflect the kernel configuration (as it's set in the .config file).
=== Driver 8.39.4 logo ===
This "bug" in 8.39.4 drivers results from the fact that ATI developers don't update the packager maintainers before the official releases. It should be nice first if they did test us official releases in order to certify the proper functioning of the scripts for creating packages. To solve the problem It's necessary to use the external SlackBuild as described here.
=== amdcccle don't start on slackware 12 ===
Many users of the X.Org 7.2 (or 1.3) server version fail to start properly the Catalyst. The command to run the Catalyst is:
# amdcccle
For this problem it seems there is no solution yet, but we are working on to solve it.

== Useful links ==
The discussion thread from which it was derived this article: 
http://www.slacky.eu/forum/viewtopic.php?t=18134&highlight= 
An alternative to official ATI drivers is given by the following website: 
http://www.schneider-digital.de/ 
A wiki in italian about installing and configuring ATI drivers (open source and proprietary) can be found at:
http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux

== Conclusion ==
Proprietary ATI drivers for many modern desktop and notebook PC seems are almost the only alternative to the use of 3d acceleration with linux. Unfortunately ATI developers don't make back porting and then users using drivers' version older than 8.37.6 will never go to X.Org server version 7.2 (or 1.3). Let's hope that Mesa drivers can also be used for these cards.
The '''external SlackBuild''' is always updated, this SlackBuild is thought to work with all ATI driver versions, both older and newer than 8.37.6. Many patches are applied in fact only after the online publication of official driver, then it may happen that '''internal SlackBuild''' included in the drivers fail where the '''external SlackBuild''' ati-slack-packager ends successfully. Also, because It hasn't been tested the SlackBuild with all possible versions of ATI drivers and kernels, It could happen that the module compilation fails. If so, feel free to write me at '''spina80@freemail.it''' posting me the output generated by Only_Module option.

Slackware: ATI SlackBuild (ENG)

2008-01-25T13:58:19Z

151.66.33.40:

== Introduction ==
This wiki explains how to install the proprietary ATI drivers in a Slackware Linux distribution, creating, thanks to a SlackBuild, packages that can be installed through the '''installpkg''' command. 
This wiki DOES NOT explain how to improve performance. In particular, It provides only a minimal description of how to set up the X.Org server with the only purpose of loading the proprietary drivers (a description on how to configure the X.Org server to increase performance can be found here).
All commands starting with a '#' must be executed with root rights, while commands beginning with '$' can be performed by a user without such rights.

== Proprietary ATI Drivers and ATI Catalyst ==
Since 21 November 2007, ATI drivers have changed the name and the number version. The new drivers, which were first mentioned only as Proprietary ATI Driver, are now called ATI Catalyst. Moreover, the version number has passed from 8.XX.X to 7.XX.

When in this wiki we will talk about drivers version <8.37.6, we will refer implicitly to the old driver, such as Proprietary ATI Driver, while the new ATI Catalyst have a number version >= 8.37.6, even if, for instance, have a release number 7.11.

== Getting all the necessary ==
The proprietary ATI drivers can be downloaded from the [http://ati.amd.com/support/driver.html official web site], after selecting the Linux x86 operating system (or Linux x86_64) and selecting your video card, pressing the “go” button takes you directly into the download page from which you can download the installer (which henceforth we call installer.run). 
Since drivers also contain a kernel module which will be compiled directly on your system, you'll need the kernel source currently installed in the system as well.

'''NOTE:''' Drivers for x86 and x86_64 architectures are equivalent. 
The installer '''contains files for both architectures''', then It will be the compilation process and the package
creation process to choose the appropriate files.
This means that '''the SlackBuild will be good for Slackware and for Slackware 64-bit portings (Slamd64, Bluewhite64, etc. ...)'''.

== Important notice ==
If the downloaded driver version is less than 8.37.6, then you need to know from now that it will not work onto X.Org 7.2 server (or 1.3).

== How to create Slackware packages ==
The packages creation follows two different ways depending on whether you use the official driver version '''< 8.37.6''' or '''>= 8.37.6'''. or new '''ATI Catalyst'''. The first way uses what is called '''external SlackBuild''' while the second way what we will call '''internal SlackBuild'''. In both cases the two packages will be created and they can be installed by Slackware '''installpkg''' utility. So let's see the two cases saying that the program that here is called installer.run is the installer downloaded from ATI web site.

'''NOTE:''' The external SlackBuild use is not limited to the driver <8.37.6 but you can use it
(and at times we will see that It's the only alternative) with all versions of ATI drivers.

=== Drivers version <8.37.6 (external SlackBuild) ===
For these types of drivers I've created an '''external SlackBuild''' for Slackware and I made a package that can be found at: http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz
To create Slackware packages simply run:
# installpkg ati-slack-packager-current-noarch-1.tgz
# sh installer.run -- buildpkg custom-package/Slackware

=== Drivers version >= 8.37.6 or new ATI Catalyst (internal SlackBuild) ===
For these drivers I've sent the SlackBuild directly to ATI that has insert it inside the installer, then simply run:
# sh installer.run --buildpkg Slackware/All

== What do created packages contain? ==
The two packages created by SlackBuild, that we'll call ''fglrx-module'' and ''fglrx-x'' contain, respectively, the kernel module and the X.Org server driver currently installed in the system. In this way, if you upgrade the kernel or the X.Org server, you can create only one package.

=== Creating only fglrx-module package ===
To create just the package containing the kernel module for the currently installed kernel, simply run the installer with the ''Only_Module'' option
So with '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_Module
With internal SlackBuild:
# sh installer.run --buildpkg Slackware/Only_Module

=== Creating only fglrx-x package ===
To create just the package containing the X.Org driver currently installed in your system, simply run installer with ''Only_X'' option
With '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_X
With '''internal SlackBuild''':
# sh installer.run --buildpkg Slackware/Only_X
== Minimal X.Org server configuration ==
Once installed the two indicated packages, you must tell to the X.Org server to use ATI proprietary drivers, to do this we must check if the xorg.conf file, which is usually located in the ''/etc/X11/'' directory, contains the following items:

<tt>
Section "Module"
...
Load "dri"
Load "glx"
...
EndSection
Section "Device"
...
Driver "fglrx"
...
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
</tt>
== Installation checking ==
To see if proprietary ATI drivers are properly installed run the command:
$ fglrxinfo
On my computer the output is:
display::0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 2.0.6650 (8.39.4)
== Remove installed packages ==
To remove installed packages you can use the '''removepkg''' utility. However, there are aspects that should be considered:
* The packages' removing don't delete fglrx's driver configuration files, these files are located in ''/etc/ati'' directory
'''NOTE:''' The /etc/ati/custom-package directory, if exists, contains the external SlackBuild and therefore should not be deleted.
* The fglrx-x package contains ATI's OpenGL libraries, and these libraries are located in the same directory of the Mesa libraries, so when you install the fglrx-x package Mesa OpenGL libraries are overridden. To restore the situation you should simply reinstall the package containing these libraries, like:
  x11 
for slackware 11, or: 
  mesa 
for slackware 12.
== Known problems ==
=== FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'paravirt_ops' ===
The error occurs during module compilation and It's due to the fact that the kernel was compiled with the option of paravirtualization active. This option among other things, prevents to load, and then to compile, modules that do not have the GPL license. Since that ATI drivers don't have this type of license, they aren't compiled. 
To work around this problem you can: 
=== Disable kernel paravirtualization option ===
The paravirtualization option is called '''CONFIG_PARAVIRT''' and generally is in the '''Processor type and features''' kernel submenu.
==== Patch ATI drivers ====
This operation is illegal because It changes the type of license issued by ATI in a GPL license. I wrote the ati_to_gpl.patch patch but I do not take any responsibility, I do not use It and I discourage the use in order to prefer the alternative to disable the paravirtualization kernel option. To use this patch You need to:
* Download and install (through installpkg) the external SlackBuild ati-slack-packager
* Copy the patch in the ''/etc/ati/custom-package/patch'' directory
* Run the installer with the command
# sh installer.run --buildpkg custom-package/Slackware
The external SlackBuild will notice the presence of the patch and It will apply It.
To uninstall the patch simply delete It from ''/etc/ati/custom-package/patch'' directory.
=== Using GLX_SGIX_pbuffer FGLTexMgr: open of shared memory object failed (Permission denied) __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!! ===
This problem is due to the lack of SHM filesystem (now called tmpfs), that is virtual memory filesystem. To work around this problem you must:
* Add into ''/etc/fstab'' file the following line:
shm /dev/shm tmpfs defaults 0 0
* Then mount the filesystem through:
# mount /dev/shm
Obviously the kernel must be predisposed for the "mounting" of this filesystem, in particular the
kernel option that must be enabled is '''CONFIG_TMPFS''' that is generally placed in '''File system --> Pseudo filesystems''' submenu. However all the compiled kernel generally have this option enabled.
=== kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel ===
The complete mistake is something like this: 
<tt>
Error:
kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel.
they are versioned as ""
instead of "`uname -r`".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
</tt>
The error, also if explained, could be not clear. In practice It results from the fact that the symbolic link: 
/lib/modules/`uname -r`/source 
/lib/modules/`uname -r`/build 
don't point to the directory where are inserted the current kernel sources (which is generally ''/usr/src/linux- 'uname-r'''). It happens to those who use a kernel contained in Slackware, so I will try to explain It in terms of Slackware "packages". This can happen:
* because the kernel source were not installed. In this case should be enough to install the source package which can be found in Slackware k/ directory. However, It is not granted that the problem will be solved, You'll need to see the second reason why there is an error.
* because sources (also if installed) do not reflect the settings of the current kernel. The new Slackware 12 has some precompiled kernels (which means different settings), while just a single package for the sources (unless seeing the branch extra/). In particular, the sources are for the SMP kernel and so if you use a non-SMP kernel can appear this error. To avoid this, after making sure that the package source has been installed, do simply the following:
# cd /usr/src/linux
# cp /boot/config .config
# make
running make, in addition to compiling the kernel modules (which we will not use), some header files are regenerated, and they will reflect the kernel configuration (as it's set in the .config file).
=== Driver 8.39.4 logo ===
This "bug" in 8.39.4 drivers results from the fact that ATI developers don't update the packager maintainers before the official releases. It should be nice first if they did test us official releases in order to certify the proper functioning of the scripts for creating packages. To solve the problem It's necessary to use the external SlackBuild as described here.
=== amdcccle don't start on slackware 12 ===
Many users of the X.Org 7.2 (or 1.3) server version fail to start properly the Catalyst. The command to run the Catalyst is:
# amdcccle
For this problem it seems there is no solution yet, but we are working on to solve it.

== Useful links ==
The discussion thread from which it was derived this article: 
http://www.slacky.eu/forum/viewtopic.php?t=18134&highlight= 
An alternative to official ATI drivers is given by the following website: 
http://www.schneider-digital.de/ 
A wiki in italian about installing and configuring ATI drivers (open source and proprietary) can be found at:
http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux

== Conclusion ==
Proprietary ATI drivers for many modern desktop and notebook PC seems are almost the only alternative to the use of 3d acceleration with linux. Unfortunately ATI developers don't make back porting and then users using drivers' version older than 8.37.6 will never go to X.Org server version 7.2 (or 1.3). Let's hope that Mesa drivers can also be used for these cards.
The '''external SlackBuild''' is always updated, this SlackBuild is thought to work with all ATI driver versions, both older and newer than 8.37.6. Many patches are applied in fact only after the online publication of official driver, then it may happen that '''internal SlackBuild''' included in the drivers fail where the '''external SlackBuild''' ati-slack-packager ends successfully. Also, because It hasn't been tested the SlackBuild with all possible versions of ATI drivers and kernels, It could happen that the module compilation fails. If so, feel free to write me at '''spina80@freemail.it''' posting me the output generated by Only_Module option.

Slackware: ATI SlackBuild (ENG)

2008-01-25T13:56:34Z

151.66.33.40:

== Introduction ==
This wiki explains how to install the proprietary ATI drivers in a Slackware Linux distribution, creating, thanks to a SlackBuild, packages that can be installed through the '''installpkg''' command. 
This wiki DOES NOT explain how to improve performance. In particular, It provides only a minimal description of how to set up the X.Org server with the only purpose of loading the proprietary drivers (a description on how to configure the X.Org server to increase performance can be found here).
All commands starting with a '#' must be executed with root rights, while commands beginning with '$' can be performed by a user without such rights.

== Proprietary ATI Drivers and ATI Catalyst ==
Since 21 November 2007, ATI drivers have changed the name and the number version. The new drivers, which were first mentioned only as Proprietary ATI Driver, are now called ATI Catalyst. Moreover, the version number has passed from 8.XX.X to 7.XX.

When in this wiki we will talk about drivers version <8.37.6, we will refer implicitly to the old driver, such as Proprietary ATI Driver, while the new ATI Catalyst have a number version >= 8.37.6, even if, for instance, have a release number 7.11.

== Getting all the necessary ==
The proprietary ATI drivers can be downloaded from the [http://ati.amd.com/support/driver.html official web site], after selecting the Linux x86 operating system (or Linux x86_64) and selecting your video card, pressing the “go” button takes you directly into the download page from which you can download the installer (which henceforth we call installer.run). 
Since drivers also contain a kernel module which will be compiled directly on your system, you'll need the kernel source currently installed in the system as well.

'''NOTE:''' Drivers for x86 and x86_64 architectures are equivalent. 
The installer '''contains files for both architectures''', then It will be the compilation process and the package
creation process to choose the appropriate files.
This means that '''the SlackBuild will be good for Slackware and for Slackware 64-bit portings (Slamd64, Bluewhite64, etc. ...)'''.

== Important notice ==
If the downloaded driver version is less than 8.37.6, then you need to know from now that it will not work onto X.Org 7.2 server (or 1.3).

== How to create Slackware packages ==
The packages creation follows two different ways depending on whether you use the official driver version '''< 8.37.6''' or '''>= 8.37.6'''. or new '''ATI Catalyst'''. The first way uses what is called '''external SlackBuild''' while the second way what we will call '''internal SlackBuild'''. In both cases the two packages will be created and they can be installed by Slackware '''installpkg''' utility. So let's see the two cases saying that the program that here is called installer.run is the installer downloaded from ATI web site.

'''NOTE:''' The external SlackBuild use is not limited to the driver <8.37.6 but you can use it
(and at times we will see that It's the only alternative) with all versions of ATI drivers.

=== Drivers version <8.37.6 (external SlackBuild) ===
For these types of drivers I've created an '''external SlackBuild''' for Slackware and I made a package that can be found at: http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz
To create Slackware packages simply run:
# installpkg ati-slack-packager-current-noarch-1.tgz
# sh installer.run -- buildpkg custom-package/Slackware

=== Drivers version >= 8.37.6 or new ATI Catalyst (internal SlackBuild) ===
For these drivers I've sent the SlackBuild directly to ATI that has insert it inside the installer, then simply run:
# sh installer.run --buildpkg Slackware/All

== What do created packages contain? ==
The two packages created by SlackBuild, that we'll call ''fglrx-module'' and ''fglrx-x'' contain, respectively, the kernel module and the X.Org server driver currently installed in the system. In this way, if you upgrade the kernel or the X.Org server, you can create only one package.

=== Creating only fglrx-module package ===
To create just the package containing the kernel module for the currently installed kernel, simply run the installer with the ''Only_Module'' option
So with '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_Module
With internal SlackBuild:
# sh installer.run --buildpkg Slackware/Only_Module

=== Creating only fglrx-x package ===
To create just the package containing the X.Org driver currently installed in your system, simply run installer with ''Only_X'' option
With '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_X
With '''internal SlackBuild''':
# sh installer.run --buildpkg Slackware/Only_X
== Minimal X.Org server configuration ==
Once installed the two indicated packages, you must tell to the X.Org server to use ATI proprietary drivers, to do this we must check if the xorg.conf file, which is usually located in the ''/etc/X11/'' directory, contains the following items:

<tt>
Section "Module"
...
Load "dri"
Load "glx"
...
EndSection
Section "Device"
...
Driver "fglrx"
...
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
</tt>
== Installation checking ==
To see if proprietary ATI drivers are properly installed run the command:
$ fglrxinfo
On my computer the output is:
display::0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 2.0.6650 (8.39.4)
== Remove installed packages ==
To remove installed packages you can use the '''removepkg''' utility. However, there are aspects that should be considered:
* The packages' removing don't delete fglrx's driver configuration files, these files are located in ''/etc/ati'' directory
'''NOTE:''' The /etc/ati/custom-package directory, if exists, contains the external SlackBuild and therefore should not be deleted.
* The fglrx-x package contains ATI's OpenGL libraries, and these libraries are located in the same directory of the Mesa libraries, so when you install the fglrx-x package Mesa OpenGL libraries are overridden. To restore the situation you should simply reinstall the package containing these libraries, like:
  x11 
for slackware 11, or: 
  mesa 
for slackware 12.
== Known problems ==
=== FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'paravirt_ops' ===
The error occurs during module compilation and It's due to the fact that the kernel was compiled with the option of paravirtualization active. This option among other things, prevents to load, and then to compile, modules that do not have the GPL license. Since that ATI drivers don't have this type of license, they aren't compiled.
To work around this problem you can:
Disable kernel paravirtualization option. 
The paravirtualization option is called '''CONFIG_PARAVIRT''' and generally is in the '''Processor type and features''' kernel submenu.
==== Patching ATI drivers ====
This operation is illegal because It changes the type of license issued by ATI in a GPL license. I wrote the ati_to_gpl.patch patch but I do not take any responsibility, I do not use It and I discourage the use in order to prefer the alternative to disable the paravirtualization kernel option. To use this patch You need to:
* Download and install (through installpkg) the external SlackBuild ati-slack-packager
* Copy the patch in the ''/etc/ati/custom-package/patch'' directory
* Run the installer with the command
# sh installer.run --buildpkg custom-package/Slackware
The external SlackBuild will notice the presence of the patch and It will apply It.
To uninstall the patch simply delete It from ''/etc/ati/custom-package/patch'' directory.
=== Using GLX_SGIX_pbuffer FGLTexMgr: open of shared memory object failed (Permission denied) __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!! ===
This problem is due to the lack of SHM filesystem (now called tmpfs), that is virtual memory filesystem. To work around this problem you must:
* Add into ''/etc/fstab'' file the following line:
shm /dev/shm tmpfs defaults 0 0
* Then mount the filesystem through:
# mount /dev/shm
Obviously the kernel must be predisposed for the "mounting" of this filesystem, in particular the
kernel option that must be enabled is '''CONFIG_TMPFS''' that is generally placed in '''File system --> Pseudo filesystems''' submenu. However all the compiled kernel generally have this option enabled.
=== kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel ===
The complete mistake is something like this: 
<tt>
Error:
kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel.
they are versioned as ""
instead of "`uname -r`".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
</tt>
The error, also if explained, could be not clear. In practice It results from the fact that the symbolic link: 
/lib/modules/`uname -r`/source 
/lib/modules/`uname -r`/build 
don't point to the directory where are inserted the current kernel sources (which is generally ''/usr/src/linux- 'uname-r'''). It happens to those who use a kernel contained in Slackware, so I will try to explain It in terms of Slackware "packages". This can happen:
* because the kernel source were not installed. In this case should be enough to install the source package which can be found in Slackware k/ directory. However, It is not granted that the problem will be solved, You'll need to see the second reason why there is an error.
* because sources (also if installed) do not reflect the settings of the current kernel. The new Slackware 12 has some precompiled kernels (which means different settings), while just a single package for the sources (unless seeing the branch extra/). In particular, the sources are for the SMP kernel and so if you use a non-SMP kernel can appear this error. To avoid this, after making sure that the package source has been installed, do simply the following:
# cd /usr/src/linux
# cp /boot/config .config
# make
running make, in addition to compiling the kernel modules (which we will not use), some header files are regenerated, and they will reflect the kernel configuration (as it's set in the .config file).
=== Driver 8.39.4 logo ===
This "bug" in 8.39.4 drivers results from the fact that ATI developers don't update the packager maintainers before the official releases. It should be nice first if they did test us official releases in order to certify the proper functioning of the scripts for creating packages. To solve the problem It's necessary to use the external SlackBuild as described here.
=== amdcccle don't start on slackware 12 ===
Many users of the X.Org 7.2 (or 1.3) server version fail to start properly the Catalyst. The command to run the Catalyst is:
# amdcccle
For this problem it seems there is no solution yet, but we are working on to solve it.

== Useful links ==
The discussion thread from which it was derived this article: 
http://www.slacky.eu/forum/viewtopic.php?t=18134&highlight= 
An alternative to official ATI drivers is given by the following website: 
http://www.schneider-digital.de/ 
A wiki in italian about installing and configuring ATI drivers (open source and proprietary) can be found at:
http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux

== Conclusion ==
Proprietary ATI drivers for many modern desktop and notebook PC seems are almost the only alternative to the use of 3d acceleration with linux. Unfortunately ATI developers don't make back porting and then users using drivers' version older than 8.37.6 will never go to X.Org server version 7.2 (or 1.3). Let's hope that Mesa drivers can also be used for these cards.
The '''external SlackBuild''' is always updated, this SlackBuild is thought to work with all ATI driver versions, both older and newer than 8.37.6. Many patches are applied in fact only after the online publication of official driver, then it may happen that '''internal SlackBuild''' included in the drivers fail where the '''external SlackBuild''' ati-slack-packager ends successfully. Also, because It hasn't been tested the SlackBuild with all possible versions of ATI drivers and kernels, It could happen that the module compilation fails. If so, feel free to write me at '''spina80@freemail.it''' posting me the output generated by Only_Module option.

Slackware: ATI SlackBuild (ENG)

2008-01-25T13:51:44Z

151.66.33.40:

== Introduction ==
This wiki explains how to install the proprietary ATI drivers in a Slackware Linux distribution, creating, thanks to a SlackBuild, packages that can be installed through the '''installpkg''' command. 
This wiki DOES NOT explain how to improve performance. In particular, It provides only a minimal description of how to set up the X.Org server with the only purpose of loading the proprietary drivers (a description on how to configure the X.Org server to increase performance can be found here).
All commands starting with a '#' must be executed with root rights, while commands beginning with '$' can be performed by a user without such rights.

== Proprietary ATI Drivers and ATI Catalyst ==
Since 21 November 2007, ATI drivers have changed the name and the number version. The new drivers, which were first mentioned only as Proprietary ATI Driver, are now called ATI Catalyst. Moreover, the version number has passed from 8.XX.X to 7.XX.

When in this wiki we will talk about drivers version <8.37.6, we will refer implicitly to the old driver, such as Proprietary ATI Driver, while the new ATI Catalyst have a number version >= 8.37.6, even if, for instance, have a release number 7.11.

== Getting all the necessary ==
The proprietary ATI drivers can be downloaded from the [http://ati.amd.com/support/driver.html official web site], after selecting the Linux x86 operating system (or Linux x86_64) and selecting your video card, pressing the “go” button takes you directly into the download page from which you can download the installer (which henceforth we call installer.run). 
Since drivers also contain a kernel module which will be compiled directly on your system, you'll need the kernel source currently installed in the system as well.

'''NOTE:''' Drivers for x86 and x86_64 architectures are equivalent. 
The installer '''contains files for both architectures''', then It will be the compilation process and the package
creation process to choose the appropriate files.
This means that '''the SlackBuild will be good for Slackware and for Slackware 64-bit portings (Slamd64, Bluewhite64, etc. ...)'''.

== Important notice ==
If the downloaded driver version is less than 8.37.6, then you need to know from now that it will not work onto X.Org 7.2 server (or 1.3).

== How to create Slackware packages ==
The packages creation follows two different ways depending on whether you use the official driver version '''< 8.37.6''' or '''>= 8.37.6'''. or new '''ATI Catalyst'''. The first way uses what is called '''external SlackBuild''' while the second way what we will call '''internal SlackBuild'''. In both cases the two packages will be created and they can be installed by Slackware '''installpkg''' utility. So let's see the two cases saying that the program that here is called installer.run is the installer downloaded from ATI web site.

'''NOTE:''' The external SlackBuild use is not limited to the driver <8.37.6 but you can use it
(and at times we will see that It's the only alternative) with all versions of ATI drivers.

== Drivers version <8.37.6 (external SlackBuild) ==
For these types of drivers I've created an '''external SlackBuild''' for Slackware and I made a package that can be found at: http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz
To create Slackware packages simply run:
# installpkg ati-slack-packager-current-noarch-1.tgz
# sh installer.run -- buildpkg custom-package/Slackware

== Drivers version >= 8.37.6 or new ATI Catalyst (internal SlackBuild) ==
For these drivers I've sent the SlackBuild directly to ATI that has insert it inside the installer, then simply run:
# sh installer.run --buildpkg Slackware/All

== What do created packages contain? ==
The two packages created by SlackBuild, that we'll call ''fglrx-module'' and ''fglrx-x'' contain, respectively, the kernel module and the X.Org server driver currently installed in the system. In this way, if you upgrade the kernel or the X.Org server, you can create only one package.

== Creating only fglrx-module package ==
To create just the package containing the kernel module for the currently installed kernel, simply run the installer with the ''Only_Module'' option
So with '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_Module
With internal SlackBuild:
# sh installer.run --buildpkg Slackware/Only_Module

== Creating only fglrx-x package ==
To create just the package containing the X.Org driver currently installed in your system, simply run installer with ''Only_X'' option
With '''external SlackBuild''':
# sh installer.run --buildpkg custom-package/Only_X
With '''internal SlackBuild''':
# sh installer.run --buildpkg Slackware/Only_X
== Minimal X.Org server configuration ==
Once installed the two indicated packages, you must tell to the X.Org server to use ATI proprietary drivers, to do this we must check if the xorg.conf file, which is usually located in the ''/etc/X11/'' directory, contains the following items:

<tt>
Section "Module"
...
Load "dri"
Load "glx"
...
EndSection
Section "Device"
...
Driver "fglrx"
...
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
</tt>
== Installation checking ==
To see if proprietary ATI drivers are properly installed run the command:
$ fglrxinfo
On my computer the output is:
display::0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 2.0.6650 (8.39.4)
== Remove installed packages ==
To remove installed packages you can use the '''removepkg''' utility. However, there are aspects that should be considered:
* The packages' removing don't delete fglrx's driver configuration files, these files are located in ''/etc/ati'' directory
'''NOTE:''' The /etc/ati/custom-package directory, if exists, contains the external SlackBuild and therefore should not be deleted.
* The fglrx-x package contains ATI's OpenGL libraries, and these libraries are located in the same directory of the Mesa libraries, so when you install the fglrx-x package Mesa OpenGL libraries are overridden. To restore the situation you should simply reinstall the package containing these libraries, like:
  x11 
for slackware 11, or: 
  mesa 
for slackware 12.
== Known problems ==
=== FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'paravirt_ops' ===
The error occurs during module compilation and It's due to the fact that the kernel was compiled with the option of paravirtualization active. This option among other things, prevents to load, and then to compile, modules that do not have the GPL license. Since that ATI drivers don't have this type of license, they aren't compiled.
To work around this problem you can:
Disable kernel paravirtualization option. 
The paravirtualization option is called '''CONFIG_PARAVIRT''' and generally is in the '''Processor type and features''' kernel submenu.
==== Patching ATI drivers ====
This operation is illegal because It changes the type of license issued by ATI in a GPL license. I wrote the ati_to_gpl.patch patch but I do not take any responsibility, I do not use It and I discourage the use in order to prefer the alternative to disable the paravirtualization kernel option. To use this patch You need to:
* Download and install (through installpkg) the external SlackBuild ati-slack-packager
* Copy the patch in the ''/etc/ati/custom-package/patch'' directory
* Run the installer with the command
# sh installer.run --buildpkg custom-package/Slackware
The external SlackBuild will notice the presence of the patch and It will apply It.
To uninstall the patch simply delete It from ''/etc/ati/custom-package/patch'' directory.
=== Using GLX_SGIX_pbuffer FGLTexMgr: open of shared memory object failed (Permission denied) __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!! ===
This problem is due to the lack of SHM filesystem (now called tmpfs), that is virtual memory filesystem. To work around this problem you must:
* Add into ''/etc/fstab'' file the following line:
shm /dev/shm tmpfs defaults 0 0
* Then mount the filesystem through:
# mount /dev/shm
Obviously the kernel must be predisposed for the "mounting" of this filesystem, in particular the
kernel option that must be enabled is '''CONFIG_TMPFS''' that is generally placed in '''File system --> Pseudo filesystems''' submenu. However all the compiled kernel generally have this option enabled.
=== kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel ===
The complete mistake is something like this: 
<tt>
Error:
kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel.
they are versioned as ""
instead of "`uname -r`".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
</tt>
The error, also if explained, could be not clear. In practice It results from the fact that the symbolic link: 
/lib/modules/`uname -r`/source 
/lib/modules/`uname -r`/build 
don't point to the directory where are inserted the current kernel sources (which is generally ''/usr/src/linux- 'uname-r'''). It happens to those who use a kernel contained in Slackware, so I will try to explain It in terms of Slackware "packages". This can happen:
* because the kernel source were not installed. In this case should be enough to install the source package which can be found in Slackware k/ directory. However, It is not granted that the problem will be solved, You'll need to see the second reason why there is an error.
* because sources (also if installed) do not reflect the settings of the current kernel. The new Slackware 12 has some precompiled kernels (which means different settings), while just a single package for the sources (unless seeing the branch extra/). In particular, the sources are for the SMP kernel and so if you use a non-SMP kernel can appear this error. To avoid this, after making sure that the package source has been installed, do simply the following:
# cd /usr/src/linux
# cp /boot/config .config
# make
running make, in addition to compiling the kernel modules (which we will not use), some header files are regenerated, and they will reflect the kernel configuration (as it's set in the .config file).
=== Driver 8.39.4 logo ===
This "bug" in 8.39.4 drivers results from the fact that ATI developers don't update the packager maintainers before the official releases. It should be nice first if they did test us official releases in order to certify the proper functioning of the scripts for creating packages. To solve the problem It's necessary to use the external SlackBuild as described here.
=== amdcccle don't start on slackware 12 ===
Many users of the X.Org 7.2 (or 1.3) server version fail to start properly the Catalyst. The command to run the Catalyst is:
# amdcccle
For this problem it seems there is no solution yet, but we are working on to solve it.

== Useful links ==
The discussion thread from which it was derived this article: 
http://www.slacky.eu/forum/viewtopic.php?t=18134&highlight= 
An alternative to official ATI drivers is given by the following website: 
http://www.schneider-digital.de/ 
A wiki in italian about installing and configuring ATI drivers (open source and proprietary) can be found at:
http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux

== Conclusion ==
Proprietary ATI drivers for many modern desktop and notebook PC seems are almost the only alternative to the use of 3d acceleration with linux. Unfortunately ATI developers don't make back porting and then users using drivers' version older than 8.37.6 will never go to X.Org server version 7.2 (or 1.3). Let's hope that Mesa drivers can also be used for these cards.
The '''external SlackBuild''' is always updated, this SlackBuild is thought to work with all ATI driver versions, both older and newer than 8.37.6. Many patches are applied in fact only after the online publication of official driver, then it may happen that '''internal SlackBuild''' included in the drivers fail where the '''external SlackBuild''' ati-slack-packager ends successfully. Also, because It hasn't been tested the SlackBuild with all possible versions of ATI drivers and kernels, It could happen that the module compilation fails. If so, feel free to write me at '''spina80@freemail.it''' posting me the output generated by Only_Module option.

Slackware: ATI SlackBuild (ENG)

2008-01-25T13:25:58Z

151.66.33.40:

Slackware: ATI SlackBuild (ENG)

2008-01-25T12:59:41Z

151.66.33.40: New page: == Introduction == This wiki explains how to install the proprietary ATI drivers in a Slackware Linux distribution, creating, thanks to a SlackBuild, packages that can be installed through...

Slackware

2008-01-25T12:46:23Z

151.66.33.40:

Welcome. This bare-bones little faq details how to get fglrx working on slackware.

==Installation==
*[[Slackware Installation Guide|Installation Guide]]
*[[ATI-Wiki-Slackbuild (ENG)]]
*[[ATI Slack-Packager (ENG)]]
*[[ATI Slack-Packager (ITA)]]

==Tips and Tricks==
'''Slamd64''' - You need to install GCC 3.3 libraries for fglrx. Download and install [http://www.tfd.chalmers.se/~berend/slamd64/ cxxlibs5]. You will also need to install the 32 bit compatibility libraries in /c.

==Related Resources==

{{VCT}}
[[Category:Distributions]]

Slackware: external SlackBuild (ENG)

2008-01-25T12:37:21Z

151.66.33.40:

== What it does ==
Starting with version 8.37.6, ATI proprietary drivers are able to create Slackware packages through an internal SlackBuild. To use this SlackBuild just run the driver's installer, the .run file that is possible to download from [http://ati.amd.com/support/driver.html ATI's official website], with the option:
--buildpkg Slackware/All
The page you're visiting is about the “twin” version of SlackBuild, which in the [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild. official wiki(ITA)] is called '''external SlackBuild'''. 
This SlackBuild deals with building Slackware packages of the ATI proprietary drivers, both versions before 8.37.6, in which the internal SlackBuild does not exist, and next versions, working just like internal SlackBuild, with the advantage that it is usually more powerful than his "brother". In fact, many patches to drivers are discovered only after the official release, this means that the internal SlackBuild may not apply them while the external, which is updated very often and whenever is needed, can do that.

== How it works ==
The use of the external SlackBuild is very easy, once downloaded and installed using the '''installpkg''' utility, simply run the ATI's installer driver with the following option: 
<tt> --buildpkg custom-package/All </tt>
What happens is exactly the same as the internal SlackBuild, and It's described in the
[http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild. official wiki(ITA)].

== News: ==
Currently the external SlackBuild is able to create Slackware packages for driver version <8.37.6 applying the patch for the new kernel series 2.6.2x. The ATI drivers version <8.37.6 weren't designed to run on these kernel and therefore they require a small patch that is applied by external SlackBuild.

* 16/01/08: added new mantainers' names, Ezio and Federico (See [[ATI Slack-Packager (ENG)#Contacts|Contacts]])
* 12/01/08: file ''amdpcsdb.default'' inserted in ''/etc/ati'', file needed for next driver version.
* 21/11/07: Small update to reflect the next official driver version.
* 03/08/07: Small update to reflect the next official driver version. ''/etc/ati/fglrxprofiles.csv'' and ''/etc/ati/fglrxrc'' are no longer distributed.
* 28/07/07: Fixed permissions in the fglrx driver configuration file, in ''/etc/ati'' directory. In addition, some files in this directory are considered administrator's “personal” configuration, and for these files has been created a .new file, which is created only if the original (the one without .new extension) does not exist. If the source exists and is equal to .new, the .new file is removed to avoid redundancy.
         The README file is moved from ''/etc/ati'' to ''/etc/ati/custom-package''.
* 27/07/07: Fixed bug in driver version 8.39.4 showing a logo in the bottom right corner of the screen.
* 07/09/07:
*# Added links to libraries like .so.
*# Based on users' reports, I have applied a driver patch in order to cancel the "error":
                
<tt>make.sh: line xxx: [: =: unary operator expected</tt> 
               
when It compiles the fglrx kernel module (which is part of the fglrx-module package). 
               
I would like to underline that "bugs" isn't in SlackBuild, but into ATI's drivers. 
               
I submitted the bug to ATI also sending the small patches to solve it, but... I'm waiting yet :).

== Download ==
The latest SlackBuild version released is [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz 1.1.9].

== Patch ==
Here are some patches that can be applied to the external SlackBuild, these patches are considered illegal and therefore are not issued in the official version. I do not take any responsibility about the use of these patches, I have written them only for culture and put online for the same reason, I do not use them and I discourage their use.
To apply the patch just copy them in ''/etc/ati/custom-package/patch'' directory, while in order to uninstall them just remove them. 
* [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch].This patch modifies the ATI drivers in order to have a GPL license so to be able to use drivers with a kernel that has the para virtualization active. The preferable alternative is to disable the kernel para virtualization as explained [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild.#Disabilitare_la_paravirtualizzazione_nel_kernel here (ITA)].

== Acknowledgments ==
I would like to thank all the [http://www.slacky.eu/ Italian Slackware Community] users for their feedback and support, especially (in alphabetical order, not certainly for importance):
* Ezio (alias ekxius),author, of an interesting [http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux wiki(ITA)] about installation and configuration of ATI drivers (open and proprietary).
* Federico (alias stan), always ready to give me advice and letting me believe more and more on the importance of the project.

== Contacts ==
Original author: 
Emanuele Tomasi < spina80ATfreemailDOTit >

Mantainer: 
Emanuele Tomasi < spina80ATfreemailDOTit > 
Ezio Ghibaudo < ekxiusATgmailDOTcom > 
Federico Rota < federico.rotaATbresciaonlineDOTit >

Slackware: external SlackBuild (ENG)

2008-01-24T13:38:30Z

151.66.33.40: New page: == What it does == Starting with version 8.37.6, ATI proprietary drivers are able to create Slackware packages through an internal SlackBuild. To use this SlackBuild just run the driver's ...

== What it does ==
Starting with version 8.37.6, ATI proprietary drivers are able to create Slackware packages through an internal SlackBuild. To use this SlackBuild just run the driver's installer, the .run file that is possible to download from [http://ati.amd.com/support/driver.html ATI's official website], with the option:
--buildpkg Slackware/All
The page you're visiting is about the “twin” version of SlackBuild, which in the [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild official wiki(ITA)] is called '''external SlackBuild'''. 
This SlackBuild deals with building Slackware packages of the ATI proprietary drivers, both versions before 8.37.6, in which the internal SlackBuild does not exist, and next versions, working just like internal SlackBuild, with the advantage that it is usually more powerful than his "brother". In fact, many patches to drivers are discovered only after the official release, this means that the internal SlackBuild may not apply them while the external, which is updated very often and whenever is needed, can do that.

== How it works ==
The use of the external SlackBuild is very easy, once downloaded and installed using the '''installpkg''' utility, simply run the ATI's installer driver with the following option: 
<tt> --buildpkg custom-package/All </tt>
What happens is exactly the same as the internal SlackBuild, and It's described in the
[http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild official wiki(ITA)].

== News: ==
Currently the external SlackBuild is able to create Slackware packages for driver version <8.37.6 applying the patch for the new kernel series 2.6.2x. The ATI drivers version <8.37.6 weren't designed to run on these kernel and therefore they require a small patch that is applied by external SlackBuild.

* 16/01/08: added new mantainers' names, Ezio and Federico (See [[ATI Slack-Packager (ENG)#Contacts|Contacts]])
* 12/01/08: file ''amdpcsdb.default'' inserted in ''/etc/ati'', file needed for next driver version.
* 21/11/07: Small update to reflect the next official driver version.
* 03/08/07: Small update to reflect the next official driver version. ''/etc/ati/fglrxprofiles.csv'' and ''/etc/ati/fglrxrc'' are no longer distributed.
* 28/07/07: Fixed permissions in the fglrx driver configuration file, in ''/etc/ati'' directory. In addition, some files in this directory are considered administrator's “personal” configuration, and for these files has been created a .new file, which is created only if the original (the one without .new extension) does not exist. If the source exists and is equal to .new, the .new file is removed to avoid redundancy.
         The README file is moved from ''/etc/ati'' to ''/etc/ati/custom-package''.
* 27/07/07: Fixed bug in driver version 8.39.4 showing a logo in the bottom right corner of the screen.
* 07/09/07:
*# Added links to libraries like .so.
*# Based on users' reports, I have applied a driver patch in order to cancel the "error":
                
<tt>make.sh: line xxx: [: =: unary operator expected</tt> 
               
when It compiles the fglrx kernel module (which is part of the fglrx-module package). 
               
I would like to underline that "bugs" isn't in SlackBuild, but into ATI's drivers. 
               
I submitted the bug to ATI also sending the small patches to solve it, but... I'm waiting yet :).

== Download ==
The latest SlackBuild version released is [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz 1.1.9].

== Patch ==
Here are some patches that can be applied to the external SlackBuild, these patches are considered illegal and therefore are not issued in the official version. I do not take any responsibility about the use of these patches, I have written them only for culture and put online for the same reason, I do not use them and I discourage their use.
To apply the patch just copy them in ''/etc/ati/custom-package/patch'' directory, while in order to uninstall them just remove them. 
* [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch].This patch modifies the ATI drivers in order to have a GPL license so to be able to use drivers with a kernel that has the para virtualization active. The preferable alternative is to disable the kernel para virtualization as explained [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild.#Disabilitare_la_paravirtualizzazione_nel_kernel here (ITA)].

== Acknowledgments ==
I would like to thank all the [http://www.slacky.eu/ Italian Slackware Community] users for their feedback and support, especially (in alphabetical order, not certainly for importance):
* Ezio (alias ekxius),author, of an interesting [http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux wiki(ITA)] about installation and configuration of ATI drivers (open and proprietary).
* Federico (alias stan), always ready to give me advice and letting me believe more and more on the importance of the project.

== Contacts ==
Original author: 
Emanuele Tomasi < spina80ATfreemailDOTit >

Mantainer: 
Emanuele Tomasi < spina80ATfreemailDOTit > 
Ezio Ghibaudo < ekxiusATgmailDOTcom > 
Federico Rota < federico.rotaATbresciaonlineDOTit >

Slackware: SlackBuild esterno (ITA)

2008-01-24T10:24:39Z

151.66.33.40: /* Come si usa */

== Cosa fa ==
A partire dalla versione 8.37.6, i driver proprietari ATI hanno la possibilità di creare dei pacchetti Slackware grazie ad uno SlackBuild interno. 
Per usare questo SlackBuild basta lanciare l'installer dei driver, il file .run che è possibile scaricarare dal [http://ati.amd.com/support/driver.html sito ufficiale ATI], tramite l'opzione:
--buildpkg Slackware/All
La pagina che state visitando parla della versione "gemella" dello SlackBuild interno, che nel [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale viene chiamato SlackBuild esterno. 
Questo SlackBuild si occupa di creare dei pacchetti Slackware dei driver proprietari ATI, sia per le versioni precedenti alla 8.37.6, nei quali lo SlackBuild interno non esiste, sia per le versioni successive, agendo esattamente come lo SlackBuild interno, con il vantaggio che generalmente è più potente del "fratello". Infatti molte patch ai driver vengono scoperte solo dopo il rilascio della versione ufficiale, questo vuol dire che lo SlackBuild interno non può applicarle mentre quello esterno, che viene aggiornato con molta frequenza ed ogni volta che ce ne è bisogno, può.

== Come si usa ==
L'uso dello SlackBuild esterno è molto semplice, una volta scaricato ed installato tramite l'utility installpkg, basta lanciare l'installer dei driver ATI con la seguente opzione: 
<tt> --buildpkg custom-package/All </tt>
Quello che accade è esattamente quello che accade con lo SlackBuild interno, e viene descritto nel
[http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale.

== Novità: ==
Attualmente lo SlackBuild esterno è in grado di creare i pacchetti Slackware dei driver versione < 8.37.6 applicando la patch per il nuovo kernel della serie 2.6.2x. I driver ATI versione < 8.37.6 non erano stati concepiti per girare con questi kernel e quindi necessitano di una piccola patch che viene applicata dallo SlackBuild esterno.

* 16/01/08: Aggiunto il nome dei nuovi maintainer, Ezio e Federico (si veda [[ATI Slack-Packager (ITA)#Contatti|Contatti]])
* 12/01/08: Viene inserito nella directory ''/etc/ati'', il file ''amdpcsdb.default'', necessario per la prossima versione dei driver.
* 21/11/07: Piccolo aggiornamento per rispecchiare la prossima versione uffigiale dei driver.
* 03/08/07: Piccolo aggiornamento per rispecchiare la prossima versione ufficiale dei driver. I file ''/etc/ati/fglrxprofiles.csv'' e ''/etc/ati/fglrxrc'' non sono più distribuiti.
* 28/07/07: Aggiustato i permessi nei file di configurazione del driver fglrx nella directory ''/etc/ati''. Inoltre alcuni file nella stessa directory sono considerati di configurazione "personale" dell'amministratore, per questi file è stato creato un nuovo file .new che viene installato solo se l'originale (quello senza il .new) non esiste. Se l'originale esiste ed è uguale al .new, il .new viene rimosso per evitate la ridondanza.
         Il file README è stato spostato, dalla directory ''/etc/ati'' nella directory ''/etc/ati/custom-package''.
* 27/07/07: Corretto il "bug" della versione 8.39.4 dei driver che mostra un logo nella parte inferiore destra dello schermo.
* 07/09/07:
*# Aggiunti i link alle librerie come .so.
*# Su segnalazione di molti utenti ho applicato una patch ai driver in modo da eliminare l'"errore": 
                
<tt>make.sh: line xxx: [: =: unary operator expected</tt> 
               
quando viene compilato il modulo per il kernel fglrx (che fa parte del pacchetto fglrx-module). 
               
Tengo a precisare che il "bug" non è nello SlackBuild, ma nei driver ATI. 
               
Ho segnalato il "bug" alla ATI inviando anche la piccola patch per risolverlo ma...aspetto ancora :).

== Download ==
L'ultima versione dello SlackBuild esterno è la [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz 1.1.9]

== Patch ==
Di seguito ci sono alcune patch che si possono applicare allo SlackBuild esterno, queste patch sono ritenute illegali e pertanto non vengono rilasciate nella versione ufficiale. Non mi prendo nessuna responsabilità sull'uso di queste patch, le ho scritte solo per cultura e le metto online per lo stesso motivo, non le uso e ne sconsiglio l'uso.
Per applicare le patch basta copiarle nella directory ''/etc/ati/custom-package/patch'', mentre per disinstallarle basta rimuoverle. 
* [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch].Questa patch modifica i driver ATI in modo che presentino una licenza GPL cossicché da poter usare i driver con un kernel che ha la paravirtualizzazione attiva. L'alternativa preferibile è di disabilitare la paravirtualizzazione del kernel come spiegato [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild.#Disabilitare_la_paravirtualizzazione_nel_kernel qui].

== Ringraziamenti ==
Ringrazio tutti gli utenti dell' [http://www.slacky.eu/ Italian Slackware Community] per il loro feedback e il loro appoggio morale, in particolare ringrazio (in ordine alfabetico, non certo per importanza):
* Ezio (alias ekxius), autore, tra l'altro di un interessante [http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux wiki] sull'installazione e configurazione dei driver ATI (open e proprietari).
* Federico (alias stan), che è sempre pronto a darmi consigli facendomi credere sempre di più nell'importanza del progetto.

== Contatti ==
Autore originale: 
Emanuele Tomasi < spina80ATfreemailDOTit >

Mantainer: 
Emanuele Tomasi < spina80ATfreemailDOTit > 
Ezio Ghibaudo < ekxiusATgmailDOTcom > 
Federico Rota < federico.rotaATbresciaonlineDOTit >

Slackware: SlackBuild esterno (ITA)

2008-01-23T21:01:06Z

151.66.33.40:

== Cosa fa ==
A partire dalla versione 8.37.6, i driver proprietari ATI hanno la possibilità di creare dei pacchetti Slackware grazie ad uno SlackBuild interno. 
Per usare questo SlackBuild basta lanciare l'installer dei driver, il file .run che è possibile scaricarare dal [http://ati.amd.com/support/driver.html sito ufficiale ATI], tramite l'opzione: 
<tt> --buildpkg Slackware/All </tt> 
La pagina che state visitando parla della versione "gemella" dello SlackBuild interno, che nel [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale viene chiamato SlackBuild esterno. 
Questo SlackBuild si occupa di creare dei pacchetti Slackware dei driver proprietari ATI, sia per le versioni precedenti alla 8.37.6, nei quali lo SlackBuild interno non esiste, sia per le versioni successive, agendo esattamente come lo SlackBuild interno, con il vantaggio che generalmente è più potente del "fratello". Infatti molte patch ai driver vengono scoperte solo dopo il rilascio della versione ufficiale, questo vuol dire che lo SlackBuild interno non può applicarle mentre quello esterno, che viene aggiornato con molta frequenza ed ogni volta che ce ne è bisogno, può.

== Come si usa ==
L'uso dello SlackBuild esterno è molto semplice, una volta scaricato ed installato tramite l'utility installpkg, basta lanciare l'installer dei driver ATI con la seguente opzione: 
<tt> --buildpkg custom-package/All </tt> 
Quello che accade è esattamente quello che accade con lo SlackBuild interno, e viene descritto nel
[http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale.

== Novità: ==
Attualmente lo SlackBuild esterno è in grado di creare i pacchetti Slackware dei driver versione < 8.37.6 applicando la patch per il nuovo kernel della serie 2.6.2x. I driver ATI versione < 8.37.6 non erano stati concepiti per girare con questi kernel e quindi necessitano di una piccola patch che viene applicata dallo SlackBuild esterno.

* 16/01/08: Aggiunto il nome dei nuovi maintainer, Ezio e Federico (si veda [[ATI Slack-Packager (ITA)#Contatti|Contatti]])
* 12/01/08: Viene inserito nella directory ''/etc/ati'', il file ''amdpcsdb.default'', necessario per la prossima versione dei driver.
* 21/11/07: Piccolo aggiornamento per rispecchiare la prossima versione uffigiale dei driver.
* 03/08/07: Piccolo aggiornamento per rispecchiare la prossima versione ufficiale dei driver. I file ''/etc/ati/fglrxprofiles.csv'' e ''/etc/ati/fglrxrc'' non sono più distribuiti.
* 28/07/07: Aggiustato i permessi nei file di configurazione del driver fglrx nella directory ''/etc/ati''. Inoltre alcuni file nella stessa directory sono considerati di configurazione "personale" dell'amministratore, per questi file è stato creato un nuovo file .new che viene installato solo se l'originale (quello senza il .new) non esiste. Se l'originale esiste ed è uguale al .new, il .new viene rimosso per evitate la ridondanza.
         Il file README è stato spostato, dalla directory ''/etc/ati'' nella directory ''/etc/ati/custom-package''.
* 27/07/07: Corretto il "bug" della versione 8.39.4 dei driver che mostra un logo nella parte inferiore destra dello schermo.
* 07/09/07:
*# Aggiunti i link alle librerie come .so.
*# Su segnalazione di molti utenti ho applicato una patch ai driver in modo da eliminare l'"errore": 
                
<tt>make.sh: line xxx: [: =: unary operator expected</tt> 
               
quando viene compilato il modulo per il kernel fglrx (che fa parte del pacchetto fglrx-module). 
               
Tengo a precisare che il "bug" non è nello SlackBuild, ma nei driver ATI. 
               
Ho segnalato il "bug" alla ATI inviando anche la piccola patch per risolverlo ma...aspetto ancora :).

== Download ==
L'ultima versione dello SlackBuild esterno è la [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz 1.1.9]

== Patch ==
Di seguito ci sono alcune patch che si possono applicare allo SlackBuild esterno, queste patch sono ritenute illegali e pertanto non vengono rilasciate nella versione ufficiale. Non mi prendo nessuna responsabilità sull'uso di queste patch, le ho scritte solo per cultura e le metto online per lo stesso motivo, non le uso e ne sconsiglio l'uso.
Per applicare le patch basta copiarle nella directory ''/etc/ati/custom-package/patch'', mentre per disinstallarle basta rimuoverle. 
* [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch].Questa patch modifica i driver ATI in modo che presentino una licenza GPL cossicché da poter usare i driver con un kernel che ha la paravirtualizzazione attiva. L'alternativa preferibile è di disabilitare la paravirtualizzazione del kernel come spiegato [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild.#Disabilitare_la_paravirtualizzazione_nel_kernel qui].

== Ringraziamenti ==
Ringrazio tutti gli utenti dell' [http://www.slacky.eu/ Italian Slackware Community] per il loro feedback e il loro appoggio morale, in particolare ringrazio (in ordine alfabetico, non certo per importanza):
* Ezio (alias ekxius), autore, tra l'altro di un interessante [http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux wiki] sull'installazione e configurazione dei driver ATI (open e proprietari).
* Federico (alias stan), che è sempre pronto a darmi consigli facendomi credere sempre di più nell'importanza del progetto.

== Contatti ==
Autore originale: 
Emanuele Tomasi < spina80ATfreemailDOTit >

Mantainer: 
Emanuele Tomasi < spina80ATfreemailDOTit > 
Ezio Ghibaudo < ekxiusATgmailDOTcom > 
Federico Rota < federico.rotaATbresciaonlineDOTit >

Slackware: SlackBuild esterno (ITA)

2008-01-23T20:57:52Z

151.66.33.40:

== Cosa fa ==
A partire dalla versione 8.37.6, i driver proprietari ATI hanno la possibilità di creare dei pacchetti Slackware grazie ad uno SlackBuild interno. 
Per usare questo SlackBuild basta lanciare l'installer dei driver, il file .run che è possibile scaricarare dal [http://ati.amd.com/support/driver.html sito ufficiale ATI], tramite l'opzione: 
<tt> --buildpkg Slackware/All </tt> 
La pagina che state visitando parla della versione "gemella" dello SlackBuild interno, che nel [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale viene chiamato SlackBuild esterno. 
Questo SlackBuild si occupa di creare dei pacchetti Slackware dei driver proprietari ATI, sia per le versioni precedenti alla 8.37.6, nei quali lo SlackBuild interno non esiste, sia per le versioni successive, agendo esattamente come lo SlackBuild interno, con il vantaggio che generalmente è più potente del "fratello". Infatti molte patch ai driver vengono scoperte solo dopo il rilascio della versione ufficiale, questo vuol dire che lo SlackBuild interno non può applicarle mentre quello esterno, che viene aggiornato con molta frequenza ed ogni volta che ce ne è bisogno, può.

== Come si usa ==
L'uso dello SlackBuild esterno è molto semplice, una volta scaricato ed installato tramite l'utility installpkg, basta lanciare l'installer dei driver ATI con la seguente opzione: 
<tt> --buildpkg custom-package/All </tt> 
Quello che accade è esattamente quello che accade con lo SlackBuild interno, e viene descritto nel
[http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale.

== Novità: ==
Attualmente lo SlackBuild esterno è in grado di creare i pacchetti Slackware dei driver versione < 8.37.6 applicando la patch per il nuovo kernel della serie 2.6.2x. I driver ATI versione < 8.37.6 non erano stati concepiti per girare con questi kernel e quindi necessitano di una piccola patch che viene applicata dallo SlackBuild esterno.

* 16/01/08: Aggiunto il nome dei nuovi maintainer, Ezio e Federico (si veda [[ATI Slack-Packager (ITA)#Contatti|Contatti]])
* 12/01/08: Viene inserito nella directory ''/etc/ati'', il file ''amdpcsdb.default'', necessario per la prossima versione dei driver.
* 21/11/07: Piccolo aggiornamento per rispecchiare la prossima versione uffigiale dei driver.
* 03/08/07: Piccolo aggiornamento per rispecchiare la prossima versione ufficiale dei driver. I file ''/etc/ati/fglrxprofiles.csv'' e ''/etc/ati/fglrxrc'' non sono più distribuiti.
* 28/07/07: Aggiustato i permessi nei file di configurazione del driver fglrx nella directory ''/etc/ati''. Inoltre alcuni file nella stessa directory sono considerati di configurazione "personale" dell'amministratore, per questi file è stato creato un nuovo file .new che viene installato solo se l'originale (quello senza il .new) non esiste. Se l'originale esiste ed è uguale al .new, il .new viene rimosso per evitate la ridondanza.
         Il file README è stato spostato, dalla directory ''/etc/ati'' nella directory ''/etc/ati/custom-package''.
* 27/07/07: Corretto il "bug" della versione 8.39.4 dei driver che mostra un logo nella parte inferiore destra dello schermo.
* 07/09/07:
*# Aggiunti i link alle librerie come .so.
*# Su segnalazione di molti utenti ho applicato una patch ai driver in modo da eliminare l'"errore": 
                
<tt>make.sh: line xxx: [: =: unary operator expected</tt> 
               
quando viene compilato il modulo per il kernel fglrx (che fa parte del pacchetto fglrx-module). 
               
Tengo a precisare che il "bug" non è nello SlackBuild, ma nei driver ATI. 
               
Ho segnalato il "bug" alla ATI inviando anche la piccola patch per risolverlo ma...aspetto ancora :).

== Download ==
L'ultima versione dello SlackBuild esterno è la [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz 1.1.9]

== Patch ==
Di seguito ci sono alcune patch che si possono applicare allo SlackBuild esterno, queste patch sono ritenute illegali e pertanto non vengono rilasciate nella versione ufficiale. Non mi prendo nessuna responsabilità sull'uso di queste patch, le ho scritte solo per cultura e le metto online per lo stesso motivo, non le uso e ne sconsiglio l'uso.
Per applicare le patch basta copiarle nella directory ''/etc/ati/custom-package/patch'', mentre per disinstallarle basta rimuoverle. 
* [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch].Questa patch modifica i driver ATI in modo che presentino una licenza GPL cossicché da poter usare i driver con un kernel che ha la paravirtualizzazione attiva. L'alternativa preferibile è di disabilitare la paravirtualizzazione del kernel come spiegato [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild.#Disabilitare_la_paravirtualizzazione_nel_kernel qui].

== Ringraziamenti ==
Ringrazio tutti gli utenti dell' [http://www.slacky.eu/ Italian Slackware Community] per il loro feedback e il loro appoggio morale, in particolare ringrazio (in ordine alfabetico, non certo per importanza):
* Ezio (alias ekxius), autore, tra l'altro di un interessante [http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux wiki] sull'installazione e configurazione dei driver ATI (open e proprietari).
* Federico (alias stan), che è sempre pronto a darmi consigli facendomi credere sempre di più nell'importanza del progetto.

== Contatti ==
Autore originale: 
Emanuele Tomasi 〈spina80ATfreemailDOTit〉

Mantainer: 
Emanuele Tomasi 〈spina80ATfreemailDOTit〉 
Ezio Ghibaudo 〈ekxiusATgmailDOTcom〉 
Federico Rota 〈federico.rotaATbresciaonlineDOTit〉

Slackware: SlackBuild esterno (ITA)

2008-01-23T20:56:41Z

151.66.33.40:

== Cosa fa ==
A partire dalla versione 8.37.6, i driver proprietari ATI hanno la possibilità di creare dei pacchetti Slackware grazie ad uno SlackBuild interno. 
Per usare questo SlackBuild basta lanciare l'installer dei driver, il file .run che è possibile scaricarare dal [http://ati.amd.com/support/driver.html sito ufficiale ATI], tramite l'opzione: 
<tt> --buildpkg Slackware/All </tt> 
La pagina che state visitando parla della versione "gemella" dello SlackBuild interno, che nel [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale viene chiamato SlackBuild esterno. 
Questo SlackBuild si occupa di creare dei pacchetti Slackware dei driver proprietari ATI, sia per le versioni precedenti alla 8.37.6, nei quali lo SlackBuild interno non esiste, sia per le versioni successive, agendo esattamente come lo SlackBuild interno, con il vantaggio che generalmente è più potente del "fratello". Infatti molte patch ai driver vengono scoperte solo dopo il rilascio della versione ufficiale, questo vuol dire che lo SlackBuild interno non può applicarle mentre quello esterno, che viene aggiornato con molta frequenza ed ogni volta che ce ne è bisogno, può.

== Come si usa ==
L'uso dello SlackBuild esterno è molto semplice, una volta scaricato ed installato tramite l'utility installpkg, basta lanciare l'installer dei driver ATI con la seguente opzione: 
<tt> --buildpkg custom-package/All </tt> 
Quello che accade è esattamente quello che accade con lo SlackBuild interno, e viene descritto nel
[http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild wiki] ufficiale.

== Novità: ==
Attualmente lo SlackBuild esterno è in grado di creare i pacchetti Slackware dei driver versione < 8.37.6 applicando la patch per il nuovo kernel della serie 2.6.2x. I driver ATI versione < 8.37.6 non erano stati concepiti per girare con questi kernel e quindi necessitano di una piccola patch che viene applicata dallo SlackBuild esterno.

* 16/01/08: Aggiunto il nome dei nuovi maintainer, Ezio e Federico (si veda [[ATI Slack-Packager (ITA)#Contatti|Contatti]])
* 12/01/08: Viene inserito nella directory ''/etc/ati'', il file ''amdpcsdb.default'', necessario per la prossima versione dei driver.
* 21/11/07: Piccolo aggiornamento per rispecchiare la prossima versione uffigiale dei driver.
* 03/08/07: Piccolo aggiornamento per rispecchiare la prossima versione ufficiale dei driver. I file ''/etc/ati/fglrxprofiles.csv'' e ''/etc/ati/fglrxrc'' non sono più distribuiti.
* 28/07/07: Aggiustato i permessi nei file di configurazione del driver fglrx nella directory ''/etc/ati''. Inoltre alcuni file nella stessa directory sono considerati di configurazione "personale" dell'amministratore, per questi file è stato creato un nuovo file .new che viene installato solo se l'originale (quello senza il .new) non esiste. Se l'originale esiste ed è uguale al .new, il .new viene rimosso per evitate la ridondanza.
         Il file README è stato spostato, dalla directory ''/etc/ati'' nella directory ''/etc/ati/custom-package''.
* 27/07/07: Corretto il "bug" della versione 8.39.4 dei driver che mostra un logo nella parte inferiore destra dello schermo.
* 07/09/07:
*# Aggiunti i link alle librerie come .so.
*# Su segnalazione di molti utenti ho applicato una patch ai driver in modo da eliminare l'"errore": 
                
<tt>make.sh: line xxx: [: =: unary operator expected</tt> 
               
quando viene compilato il modulo per il kernel fglrx (che fa parte del pacchetto fglrx-module). 
               
Tengo a precisare che il "bug" non è nello SlackBuild, ma nei driver ATI. 
               
Ho segnalato il "bug" alla ATI inviando anche la piccola patch per risolverlo ma...aspetto ancora :).

== Download ==
L'ultima versione dello SlackBuild esterno è la [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz 1.1.9]

== Patch ==
Di seguito ci sono alcune patch che si possono applicare allo SlackBuild esterno, queste patch sono ritenute illegali e pertanto non vengono rilasciate nella versione ufficiale. Non mi prendo nessuna responsabilità sull'uso di queste patch, le ho scritte solo per cultura e le metto online per lo stesso motivo, non le uso e ne sconsiglio l'uso.
Per applicare le patch basta copiarle nella directory ''/etc/ati/custom-package/patch'', mentre per disinstallarle basta rimuoverle. 
* [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch].Questa patch modifica i driver ATI in modo che presentino una licenza GPL cossicché da poter usare i driver con un kernel che ha la paravirtualizzazione attiva. L'alternativa preferibile è di disabilitare la paravirtualizzazione del kernel come spiegato [http://www.slacky.eu/wikislack/index.php?title=ATI_Proprietary_drivers._Ecco_uno_slackbuild.#Disabilitare_la_paravirtualizzazione_nel_kernel qui].

== Ringraziamenti ==
Ringrazio tutti gli utenti dell' [http://www.slacky.eu/ Italian Slackware Community] per il loro feedback e il loro appoggio morale, in particolare ringrazio (in ordine alfabetico, non certo per importanza):
* Ezio (alias ekxius), autore, tra l'altro di un interessante [http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux wiki]sull'installazione e configurazione dei driver ATI (open e proprietari).
* Federico (alias stan), che è sempre pronto a darmi consigli facendomi credere sempre di più nell'importanza del progetto.

== Contatti ==
Autore originale: 
Emanuele Tomasi 〈spina80ATfreemailDOTit〉

Mantainer: 
Emanuele Tomasi 〈spina80ATfreemailDOTit〉 
Ezio Ghibaudo 〈ekxiusATgmailDOTcom〉 
Federico Rota 〈federico.rotaATbresciaonlineDOTit〉

Slackware: SlackBuild esterno (ITA)

2008-01-23T20:27:54Z

151.66.33.40:

Slackware: SlackBuild esterno (ITA)

2008-01-23T20:26:23Z

151.66.33.40:

Slackware: SlackBuild esterno (ITA)

2008-01-23T20:12:22Z

151.66.33.40:

Slackware: SlackBuild esterno (ITA)

2008-01-23T20:12:01Z

151.66.33.40: New page: = ATI Slack-Packager (ITA) = == Cosa fa == A partire dalla versione 8.37.6, i driver proprietari ATI hanno la possibilità di creare dei pacchetti Slackware grazie ad uno SlackBuild intern...

= ATI Slack-Packager (ITA) =
== Cosa fa ==
A partire dalla versione 8.37.6, i driver proprietari ATI hanno la possibilità di creare dei pacchetti Slackware grazie ad uno SlackBuild interno. 
Per usare questo SlackBuild basta lanciare l'installer dei driver, il file .run che è possibile scaricarare dal [http://ati.amd.com/support/driver.html sito ufficiale ATI]

Slackware

2008-01-23T20:02:17Z

151.66.33.40:

Welcome. This bare-bones little faq details how to get fglrx working on slackware.

==Installation==
*[[Slackware Installation Guide|Installation Guide]]
*[[ATI Slack-Packager (ITA)]]

==Tips and Tricks==
'''Slamd64''' - You need to install GCC 3.3 libraries for fglrx. Download and install [http://www.tfd.chalmers.se/~berend/slamd64/ cxxlibs5]. You will also need to install the 32 bit compatibility libraries in /c.

==Related Resources==

{{VCT}}
[[Category:Distributions]]