cchtml.com - User contributions [en]

Slackware: ATI SlackBuild (ENG)

2010-09-23T07:58:54Z

80.181.167.115: /* Known problems */

== 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) or later.

== 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 which inserted it into the installer, then simply run:
# sh installer.run --buildpkg Slackware/All
or, if drivers are quite recent, it suffices:
# sh installer.run --buildpkg
Otherwise, in order to create and install directly the packages you can use (always with recent versions of the driver):
# sh installer.run --buildandinstallpkg

此处的意思是：如果是新装的系统，直接运行本处的最后一个命令即可同时完成创建包和安装包的过程。

== 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

（如果进行了上一小节的 --buildandinstallpkg则本小节的命令可不必再执行）

接下来，执行

# sh installer.run

即可进入ATI配置的界面，完成显卡的简单配置。

== 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.
= Patching the drivers =
Ati drivers are usually not compatible with brand new version of kernel linux.
You often need to patch the driver so that you can create the kernel module successfully.
Since Ati Catalyst > 8.11 you can patch Ati drivers within the "internal slackbuild" before that same slackbuild compiles the kernel module.

In order to do that, you just have to create (or download from the Internet) a patch and rename it like this: 
''/etc/ati/patch/patch-ATI_DRIVER_VERSION-KERNEL_VERSION'' 
where 
ATI_DRIVER_VERSION must be equal to the output of: 
$ sh installer.run -i | head -n1 | cut -d'-' -f2 
KERNEL_VERSION must be equal to the output of: 
uname -r
If ''/etc/ati/patch'' doesn't exist, it must be made.

For example, if the former command outputs "8.55" and the latter "2.6.27.6", you need to name the patch ''/etc/ati/patch/patch-8.56-2.6.27.6''.

The ''internal slackbuild'' will find the patch automatically and, if the command ''patch'' is installed, it will run: 
# patch -p0 < /etc/ati/patch/patch-8.56-2.6.27.6

= 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 [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch] (md5sum: 4207f41a71035dc2eed3ea9346b881bb) 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: 
''External slackbuild''

* Copy the patch in the ''/etc/ati/custom-package/patch'' directory

''Internal slackbuild (only with Ati Catalyst > 8.11)'' 
* Copy the patch in the ''/etc/ati/patch'' directory (if it doesn't exist you must create it)

The SlackBuild will find and apply the patch automatically. In order to uninstall it you simply need to delete it.

In order 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) or later. Let's hope that Mesa drivers can also be used for these cards.
The '''external SlackBuild''' is deprecated because now the ''internal slackbuild'' can apply patch natively. 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@gmail.com''' posting me the output generated by Only_Module option.

Slackware: ATI SlackBuild (ENG)

2010-09-23T07:57:22Z

80.181.167.115: /* Patching the drivers */

== 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) or later.

== 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 which inserted it into the installer, then simply run:
# sh installer.run --buildpkg Slackware/All
or, if drivers are quite recent, it suffices:
# sh installer.run --buildpkg
Otherwise, in order to create and install directly the packages you can use (always with recent versions of the driver):
# sh installer.run --buildandinstallpkg

此处的意思是：如果是新装的系统，直接运行本处的最后一个命令即可同时完成创建包和安装包的过程。

== 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

（如果进行了上一小节的 --buildandinstallpkg则本小节的命令可不必再执行）

接下来，执行

# sh installer.run

即可进入ATI配置的界面，完成显卡的简单配置。

== 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.
= Patching the drivers =
Ati drivers are usually not compatible with brand new version of kernel linux.
You often need to patch the driver so that you can create the kernel module successfully.
Since Ati Catalyst > 8.11 you can patch Ati drivers within the "internal slackbuild" before that same slackbuild compiles the kernel module.

In order to do that, you just have to create (or download from the Internet) a patch and rename it like this: 
''/etc/ati/patch/patch-ATI_DRIVER_VERSION-KERNEL_VERSION'' 
where 
ATI_DRIVER_VERSION must be equal to the output of: 
$ sh installer.run -i | head -n1 | cut -d'-' -f2 
KERNEL_VERSION must be equal to the output of: 
uname -r
If ''/etc/ati/patch'' doesn't exist, it must be made.

For example, if the former command outputs "8.55" and the latter "2.6.27.6", you need to name the patch ''/etc/ati/patch/patch-8.56-2.6.27.6''.

The ''internal slackbuild'' will find the patch automatically and, if the command ''patch'' is installed, it will run: 
# patch -p0 < /etc/ati/patch/patch-8.56-2.6.27.6

= 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 [http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch] (md5sum: 4207f41a71035dc2eed3ea9346b881bb) 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: 
''External slackbuild''

* Copy the patch in the ''/etc/ati/custom-package/patch'' directory

''Internal slackbuild (only with Ati Catalyst > 8.11)'' 
* Copy the patch in the ''/etc/ati/patch'' directory (if it doesn't exist you must create it)

The SlackBuild will find and apply the patch automatically. In order to uninstall it you simply need to delete it.

In order 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) or later. Let's hope that Mesa drivers can also be used for these cards.
The '''external SlackBuild''' is deprecated because now the ''internal slackbuild'' can apply patch natively. 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@gmail.com''' posting me the output generated by Only_Module option.

Slackware: ATI SlackBuild (ITA)

2010-09-23T07:53:49Z

80.181.167.115: /* Patchare i driver */

=Introduzione=
Questo wiki spiega come installare i driver propritari ATI con la distribuzione linux Slackware, creando, grazie ad uno SlackBuild, dei
pacchetti che possono essere installati tramite il comando '''installpkg'''.

Il wiki NON spiega come migliorare le prestazioni. In particolare fornisce solo una descrizione minimale di come impostare il server X.Org
con l'unico scopo di far funzionare i driver proprietari (una descrizione su come configurare il server X.Org per ottenere prestazioni
più elevate la potete trovare [http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux qui]).

Tutti i comandi che iniziano con un '#' devono essere eseguiti con i diritti dell'utente root, mentre quello che iniziano con '$' possono
essere eseguiti anche da un utente senza tali diritti.

=ATI Proprietary Driver e ATI Catalyst=
A partire dal 21 Novembre 2007 i driver ATI hanno cambiato nome e numero di versione. I nuovi driver, che prima venivano
indicati solo come '''ATI Proprietary Driver''', ora si chiamano '''ATI Catalyst'''. Non solo, il numero di versione
è passato da '''8.XX.X''' a '''7.XX'''.

Quando in questo articolo si parlerà dei driver ''versione < 8.37.6'', ci si riferirà implicitamente ai
vecchi driver, ovvero agli ATI Proprietary Driver, i nuovi ATI Catalyst sono da considerarsi ''versione >= 8.37.6'',
anche se, ad esempio, hanno come numero di release 7.11.

=Come ottenere tutto il software necessario=
I driver proprietari ATI possono essere scaricati dal sito ufficiale: http://ati.amd.com/support/driver.html, dopo aver selezionato il
sistema operativo Linux x86 (o Linux x86_64) e selezionato la propria scheda video, premendo il tasto "go" si arriva direttamente alla
pagina del download da cui bisognerà scaricare l'installer (che d'ora in poi chiameremo ''installer.run'').
Dato che i driver contengono anche un modulo del kernel che verrà compilato direttamente sul vostro sistema, è necessario
avere anche i sorgenti del kernel attualmente installato sul sistema.

'''NOTA:''' I driver per le architetture x86 e x86_64 sono equivalenti. L'installer infatti contiene i file per entrambe
le architetture, sarà poi il processo di compilazione e creazione dei pacchetti che sceglierà i file adeguati.
Questo vuol dire che lo SlackBuild andrà bene sia per la Slackware sia per le varie versioni porting a 64 bit
(Slamd64, Bluewhite64, etc...).

=Nota IMPORTANTE=
Se la versione dei driver che si è scaricata è minore della 8.37.6 allora dovete sapere fin d'ora che non funzioneranno con
il server X.Org 7.2 (o 1.3) o successivi.

=Come creare i pacchetti per la Slackware=
La creazione dei pacchetti segue due strade differenti a seconda che si usino i driver ufficiali '''versione < 8.37.6''' oppure
'''versione >= 8.37.6 o nuovi ATI Catalyst'''.
La prima strada fa uso di quello che chiameremo '''SlackBuild esterno''' mentre la seconda di quello che chiameremo
'''SlackBuild interno'''.
In entrambi i casi verranno creati due pacchetti che potranno quindi essere installati tramite l'utiliti '''installpkg''' della Slackware.
Quindi passiamo a vedere i due casi ricordando che il programma che qui chiamiamo ''installer.run'' è l'installer che si è
scaricato dal sito della ATI.

'''NOTA:''' L'uso dello ''SlackBuild esterno'' non è limitato alla versione dei ''driver < 8.37.6'' ma lo si può usare
(e a volte vedremo che è l'unica alternativa) con tutte le versioni dei driver ATI.

==Versione dei driver < 8.37.6 (SlackBuild esterno)==
Per questi tipi di driver ho creato uno '''SlackBuild esterno''' per la slackware di cui ho fatto un pacchetto che potete trovare alla
pagina: http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/ati-slack-packager-current-noarch-1.tgz

Per creare i pacchetti slackware basta eseguire:

# installpkg ati-slack-packager-current-noarch-1.tgz
# sh installer.run --buildpkg custom-package/Slackware

==Versione dei driver >= 8.37.6 o nuovi ATI Catalyst (SlackBuild interno)==
Per questi driver lo SlackBuild l'ho inviato direttamente alla ATI che ha provveduto ad inserirlo all'interno dell'installer, quindi basta
eseguire:

# sh installer.run --buildpkg Slackware/All
o, se i driver sono abbastanza recenti (non ricordo la versione esatta), basta un semplice:
# sh installer.run --buildpkg
Oppure, per creare ed installare direttamente i pacchetti, si può usare (sempre con versioni recenti dei driver):
# sh intaller.run --buildandinstallpkg

=Cosa contengono i pacchetti creati?=
I due pacchetti creati dallo SlackBuild, che chiameremo ''fglrx-module'' e ''fglrx-x'', contengono, rispettivamente, il modulo per il
kernel attualmente installato sul sistema, e i driver per la versione del server X.Org installata.
In questo modo, se si aggiorna il kernel oppure il server X.Org si può creare solo il relativo pacchetto.

==Creare solo il pacchetto fglrx-module==
Per creare solo il pacchetto contenente il modulo per il kernel attualmente installato, basta lanciare l'installer con l'opzione
''Only_Module ''

Quindi con lo '''SlackBuild esterno''':
# sh installer.run --buildpkg custom-package/Only_Module
Con lo '''SlackBuild interno''':
# sh installer.run --buildpkg Slackware/Only_Module

==Creare solo il pacchetto fglrx-x==
Per creare solo il pacchetto contenente i driver per il server X.Org attualmente installato sul sistema, basta lanciare l'installer con
l'opzione ''Only_X''

Con lo '''SlackBuild esterno''':
# sh installer.run --buildpkg custom-package/Only_X
Con lo '''SlackBuild interno''':
# sh installer.run --buildpkg Slackware/Only_X

=Configurazione minimale del server X.Org=
Una volta installati i due pacchetti bisogna segnalare al server X.Org di usare i driver proprietari ATI, per fare questo bisogna
controllare che il file xorg.conf, che generalmente è situato nella directory /etc/X11/, contenga le seguenti voci:

Section "Module"
....
Load "dri"
Load "glx"
....
EndSection

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

Section "DRI"
Group 0
Mode 0666
EndSection

=Verifica=
Per verificare se i driver proprietari ATI sono stati correttamente installati si può eseguire il comando:
$ fglrxinfo
Sulla mia macchina l'output è:
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)

=Rimuovere i pacchetti installati=
Per rimuovere i pacchetti installati si può tranquillamente usare l'utiliti '''removepkg'''. Ci sono però aspetti che vanno
considerati:
*La rimozione dei pacchetti non elimina i file di configurazione del driver fglrx, questi file sono situati nella directory ''/etc/ati''
'''NOTA:''' La directory ''/etc/ati/custom-package'' se esiste, contiene lo SlackBuild esterno e quindi non va cancellata.
*Il pacchetto ''fglrx-x'' contiene le librerie OpenGL della ATI, e queste librerie sono posizionate nella stessa directory di quelle Mesa, indi per cui quando si installa il pacchetto ''fglrx-x'' vengono sovrascritte le OpenGL Mesa. Per ripristinare la situazione si deve semplicemente reinstallare il pacchetto contenente queste librerie, ovvero il pacchetto:
::x11
:si usa la slackware 11, oppure:
::mesa
:se si usa la slackware 12.

=Patchare i driver=
I driver ATI sono noti per essere sempre in ritardo rispetto all'aggiornamento del kernel linux. Spesso occorre quindi patchare i driver in modo tale che la creazione del modulo per il kernel abbia successo. A partire dagli ATI Catalist > 8.11 abbiamo inserito nello '''SlackBuild interno''' la possibilità di patchare i driver ATI prima che lo SlackBuild stesso esegua la compilazione del modulo per il kernel.

Per fare questo basta creare (o scaricare da internet) una patch e dargli questo path:

''/etc/ati/patch/patch-ATI_DRIVER_VERSION-KERNEL_VERSION''

dove:

ATI_DRIVER_VERSION deve essere uguale al risultato del comando:
$ sh installer.run -i | head -n1 | cut -d'-' -f2
KERNEL_VERSION deve essere uguale al risultato del comando:
$ uname -r

se la directory ''/et/ati/patch'' non esiste, va ovviamente creata.

Quindi ad esempio, se si il primo dei due comandi da come risultato '''8.56''' e il secondo '''2.6.27.6''', la patch va chiamata: ''/etc/ati/patch/patch-8.56-2.6.27.6''

Lo '''SlackBuild interno''' automaticamente noterà la patch, e, se si è in possesso del programma '''patch''', eseguirà:
# patch -p0 < /etc/ati/patch/patch-8.56-2.6.27.6

=Problemi noti=
==FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'paravirt_ops'==
L'errore accade in fase di compilazione del modulo ed è dovuto al fatto che il kernel è stato compilato con l'opzione di
paravirtualizzazione attiva. Questa opzione tra le altre cose, impedisce di caricare, e quindi di compilare, moduli che non hanno la
licenza GPL. Visto che i driver ATI non hanno questo tipo di licenza, non vengono compilati.

Per ovviare al problema si può:
===Disabilitare la paravirtualizzazione nel kernel ===
L'opzione di paravirtualizzazione si chiama '''CONFIG_PARAVIRT''' e generalmente si trova nel sottomenù
'''Processor type and features''' del kernel.
===Patchare i driver ATI===
Questa operazione è illegale poichè si deve modificare il tipo di licenza rilasciata dalla ATI in GPL.
Ho scritto la patch:

[http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/patch/ati_to_gpl.patch ati_to_gpl.patch] (md5sum: 4207f41a71035dc2eed3ea9346b881bb)

di cui non mi prendo nessuna responsabilità, io non la uso e ne sconsiglio l'uso preferendo l'alternativa di disabilitare la paravirtualizzazione del kernel.
Per usare questa patch bisogna:

'''SlackBuild esterno''':
* Copiare la patch nella directory ''/etc/ati/custom-package/patch''

'''SlackBuild interno''' (solo con ATI Catalist > 8.11):
* Copiare la patch nella directory ''/etc/ati/patch'' (se non esiste, va creata)

Lo SlackBuild noterà la presenza della patch e la applicherà. Per disinstallare la patch basterà quindi cancellarla.

==Using GLX_SGIX_pbuffer FGLTexMgr: open of shared memory object failed (Permission denied) __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!==
Questo problema è dovuto alla mancanza nel sistema del filesystem SHM (oggi chiamato tmpfs), ovvero il virtual memory filesystem.
Per ovviare al problema si deve:
* Aggiungere al file ''/etc/fstab'' la seguente riga:
shm /dev/shm tmpfs defaults 0 0
* Quindi montare il filesystem tramite:
# mount /dev/shm
Ovviamente il kernel deve essero predisposto al "montaggio" di questo filesystem, in particolare l'opzione del kernel che deve essere
abilitata è
'''CONFIG_TMPFS''' che generalmente è sistuata nel sottomenù del kernel '''File systems --> Pseudo filesystems'''.
C'è da dire però che tutti i kernel precompilati hanno generalmente questa opzione abilitata.

==kernel includes at /lib/modules/`uname -r`/build/include do not match current kernel==
L'errore completo è qualcosa del genere:

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

L'errore, se pur spiegato può non essere chiaro. In pratica deriva dal fatto che i link simbolici:
/lib/modules/`uname -r`/source
/lib/modules/`uname -r`/build
non puntano alla directory in cui sono inseriti i sorgenti del kernel attuale (che generalmente è /usr/src/linux-`uname -r`).
Accade a coloro che usano uno dei kernel contenuto nella Slackware, per cui cercherò di spiegarlo in termini di "pacchetti"
Slackware.
Questo può succedere:
* O perchè i sorgenti del kernel effettivamente non sono stati installati. In questo caso dovrebbe bastare installare il pacchetto dei sorgenti che si trova nella directory k/ della Slackware. Non è detto però che il problema venga risolto, si veda il secondo motivo per cui sussiste l'errore.
* O perchè i sorgenti (se pur installati) non rispecchiano le impostazioni dell'attuale kernel. La nuova Slackware 12 ha al suo interno un pò di kernel precompilati (che vuol dire impostazioni differenti) mentre un solo pacchetto per i sorgenti (a meno di vedere nel ramo extra/). In particolare i sorgenti sono per un kernel SMP e quindi se si utilizza un kernel precompilato non SMP può accare che si verifichi l'errore suddetto. Per ovviare basta fare quanto segue, dopo essersi assicurati che il pacchetto dei sorgenti è stato installato:
# cd /usr/src/linux
# cp /boot/config .config
# make
:eseguendo il make, oltre a compilare il kernel e relativi moduli (che poi non useremo), si rigenerano alcuni file headers che rispecchiano la configurazione del kernel (per come impostata nel file .config).

==Logo nei driver 8.39.4==
Questo "bug" nei driver 8.39.4 deriva dal fatto che gli sviluppatori ATI non aggiornano i packager mantainer prima della release
ufficiale. Sarebbe carino se facessero testare prima a noi le release ufficiali, in modo da certificare il corretto funzionamento degli
script per creare i pacchetti. Per risolvere il problema si deve usare lo SlackBuild esterno come descritto
[[#Versione dei driver < 8.37.6 (SlackBuild esterno) | qui]].

==amdcccle non parte con la slackware 12==
Molti utenti che utilizzano la versione del server X.Org 7.2 (o 1.3) non riescono a lanciare correttamente il Catalyst.
Il comando per eseguire il Catalyst è:
# amdcccle
Per questo problema sembra non esserci ancora soluzione, ma stiamo lavorando per risolverlo.

=Link utili=
La Homepage dello SlackBuild esterno per i driver ATI la trovate all'indirizzo:
http://www.cli.di.unipi.it/~tomasi/ati-slack-packager/sito/ati-slack-packager.html

La principale "non-ufficiale" fonte di informazione per quanto riguarda i driver proprietari ATI:
http://wiki.cchtml.com/index.php/Main_Page

Il thread di discussione da cui è stato tratto questo articolo:
http://www.slacky.eu/forum/viewtopic.php?t=18134&highlight=

Un alternativa ai driver ufficiali ATI è data dal seguente sito:
http://www.schneider-digital.de/

Una guida su come installare e configurare i driver Open Source ATI la trovate all'indirizzo:
http://www.slacky.eu/wikislack/index.php?title=Installazione_driver_ATI_su_Slackware_GNU/Linux

=Conclusione=
I driver proprietari ATI per molti notebook e moderni PC fissi risultano essere quasi l'unica alternativa per l'uso dell'accelerazione
3d con linux.
Purtroppo gli sviluppatori ATI non effettuano il back porting e quindi gli utenti che fanno uso dei driver precedenti alla versione 8.37.6
non potranno mai passare alla versione 7.2 (o 1.3) o successive del server X.Org. Si spera quindi che ben presto i driver Mesa possano essere usati
anche per queste schede video.

Lo '''SlackBuild esterno''' è '''deprecato''' avendo aggiunto allo '''SlackBuild interno''' la possibilità di patchare i driver.

Inoltre, dato che non si è testato lo SlackBuild con tutte le versioni dei driver ATI e kernel possibili, può succedere che
la compilazione del modulo non abbia successo. Se è il vostro caso, scrivetemi tranquillamente all'indirizzo
'''spina80@gmail.com''' postandomi l'output dell'installer lanciato con l'opzione ''Only_Module''.

Autore (data dell'ultimo aggiornamento):
[[Utente:Spina|Spina]] 08:43, 19 Dic 2007 (CET)