Slackware: ATI SlackBuild (ENG)

From cchtml.com
Revision as of 17:15, 9 January 2011 by Spina (talk | contribs) (Added patch for Catalyst 10.10-12 and kernel 2.6.37.x)


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 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, Slackware64 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.

Drivers version < 8.37.6 (external SlackBuild)

For these types of drivers I've created an external SlackBuild for Slackware and I made this package.

To create Slackware packages simply run: 

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

NOTE: The external SlackBuild use is limited to the driver < 8.37.6 since from new Catalyst 8.11 you can pass the patches at the internal SlackBuild.

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: 

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

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

Section "DRI"
       Group   0
       Mode    0666
EndSection

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

Patches

Here some patches and how to use there:

ATI Catalyst 10.3, 10.4 and kernel == 2.6.33.x

Download the patch into /tmp, so:

  • For Catalyst 10.3 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.3-4_with_2.6.33.x.diff /etc/ati/patch/patch-8.712-$(uname -r)
#> sh ati-driver-installer-10-3-x86.x86_64.run --buildpkg
  • For Catalyst 10.4 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.3-4_with_2.6.33.x.diff /etc/ati/patch/patch-8.723-$(uname -r)
#> sh ati-driver-installer-10-4-x86.x86_64.run --buildpkg

ATI Catalyst 10.4, 10.5 and kernel == 2.6.34

Download the patch into /tmp, so:

  • For Catalyst 10.4 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.4-5_with_2.6.34.diff /etc/ati/patch/patch-8.723-$(uname -r)
#> sh ati-driver-installer-10-4-x86.x86_64.run --buildpkg
  • For Catalyst 10.5 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.4-5_with_2.6.34.diff /etc/ati/patch/patch-8.732-$(uname -r)
#> sh ati-driver-installer-10-4-x86.x86_64.run --buildpkg

ATI Catalyst 10.9 and Slackware64 13.1 or current

Download the patch into /tmp, so to do: 

#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.9_with_Slackware64-13.1.diff /etc/ati/patch/patch-8.771-$(uname -r)
#> sh ati-driver-installer-10-9-x86.x86_64.run --buildpkg

at one point the installer asks: 

can't find file to patch at input line 4
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ru ./2.6.x/Makefile ../../../../../../fglrx-install.uZLF8t/common/lib/modules/fglrx/build_mod//2.6.x/Makefile
|--- ./2.6.x/Makefile   2010-09-01 16:05:31.000000000 +0200
|+++ ../../../../../../fglrx-install.uZLF8t/common/lib/modules/fglrx/build_mod//2.6.x/Makefile  2010-09-23 08:47:24.000000000 +0200
--------------------------
File to patch:

insert: 

./2.6.x/Makefile

ATI Catalyst 10.10, 10.11 and kernel == 2.6.36.x

Download the patch into /tmp, so:

  • For Catalyst 10.10 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.10-11_with_2.6.36.x.diff /etc/ati/patch/patch-8.783-$(uname -r)
#> sh ati-driver-installer-10-10-x86.x86_64.run --buildpkg
  • For Catalyst 10.11 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.10-11_with_2.6.36.x.diff /etc/ati/patch/patch-8.791-$(uname -r)
#> sh ati-driver-installer-10-11-x86.x86_64.run --buildpkg

ATI Catalyst 10.10, 10.11 e 10.12 e kernel == 2.6.37.x

Download the patch into /tmp, so:

  • For Catalyst 10.10 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.10-12_with_2.6.37.x.diff /etc/ati/patch/patch-8.783-$(uname -r)
#> sh ati-driver-installer-10-10-x86.x86_64.run --buildpkg
  • For Catalyst 10.11 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.10-12_with_2.6.37.x.diff /etc/ati/patch/patch-8.791-$(uname -r)
#> sh ati-driver-installer-10-11-x86.x86_64.run --buildpkg
  • For Catalyst 10.12 do:
#> mkdir -p /etc/ati/patch/
#> mv /tmp/fglrx_10.10-12_with_2.6.37.x.diff /etc/ati/patch/patch-8.801-$(uname -r)
#> sh ati-driver-installer-10-12-x86.x86_64.run --buildpkg

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 patch:

ati_to_gpl.patch (md5sum: 4207f41a71035dc2eed3ea9346b881bb)

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: 

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

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).

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: http://www.schneider-digital.de/

A wiki in italian about installing and configuring ATI drivers (open source and proprietary): 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 (alias 1.3) or later. Let's hope that Mesa drivers can also be used for these cards.

Also, It could happen that the module compilation fails. If so, feel free to write me at tomasiATcliDOTdiDOTunipiDOTit posting me the output generated by Only_Module option.

Thank you at Ezio Ghibaudo and Federico Rota who have started this wiki and for help with the SlackBuild.

Retrieved from "http://wiki.cchtml.com/index.php?title=Slackware:_ATI_SlackBuild_(ENG)&oldid=6294"