cchtml.com - User contributions [en]

Verifying

2013-03-16T22:19:33Z

46.137.18.7: /* fglrxinfo */

It is assumed that you have completed the [[Installation|installation process]].

==Verify with ATI tools==
If the installation has worked, then any 3D application should work without issue. A simple way to verify without any possibility of failure is to verify the following occurs. Please note that you may have needed to go through [[:Category:Distributions|distribution specific]] process to enable the 3D support.
> I don’t know if it’s me, but on the wall display with 9 dlsipays, it seems the parallel renderer is struggling…It's actually not the renderer, but the image capture tool which is struggling to record almost full-screen. With larger models this configuration does indeed struggle, which is not surprising considering you have 9 GL context and 4 processes on a single GPU .I am using Capture Me on Mac OS X anybody knows a better tool?

===fgl_glxgears===
You can also run the ATI provided application called fgl_glxgears which should show a spinning cube with the venerable glxgears running on each face.

If you run fgl_glxgears and the cube spins but is lacking any cogs on the faces, the faces being instead various shades of blue and/or you get an error message like:

<pre>
Using GLX_SGIX_pbuffer
913 frames in 5.0 seconds = 182.600 FPS
783 frames in 5.0 seconds = 156.600 FPS
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 14 (X_GetGeometry)
Resource id in failed request: 0x0
Serial number of failed request: 51
Current serial number in output stream: 51
</pre>

Then your installation most presumably failed!

===Links===
http://linux.coconia.net/general/ati.htm 
http://m.domaindlx.com/LinuxHelp/ati/ati.htm (mirror)
==Verify with Linux tools==
===glxinfo===
This command line option should report "direct" rendering.
$ glxinfo | grep direct

(For Debian 4.0, install the mesa-utils package to get glxinfo.)

===Xorg.0.log===
The X.org X server log file also contains useful information to verify installation was successful. It is located on most Linux distributions at <code>/var/log/Xorg.0.log</code> and can be opened by any text editor.

'''You can now move on to [[Configuring|configuring the driver]].'''

{{VCT}}
[[Category:NeedsUpdating]]

Slackware: ATI SlackBuild (ENG)

2013-03-16T08:10:42Z

46.137.18.7: /* Introduction */

It's really great that people are shiarng this information.

= 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 installer can be downloaded from the [http://ati.amd.com/support/driver.html official web site] directly.
{{Warning|Warning|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.}}
{{Helpful Hint|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. ...).}}

Since drivers also contain a kernel module which will be compiled directly on your system, you'll need the kernel source in use.

= How to create Slackware packages =
== ATI Proprietary drivers or ATI Catalyst < 11.3 ==
For these drivers will be produced two packages (see [[#What do created packages contain?]]).
=== Drivers version < 8.37.6 (external SlackBuild) ===
For these types of drivers I've created an '''external SlackBuild''' for Slackware and I made [http://www.slacky.eu/~spina/fglrx/ati-slack-packager-1.1.9-noarch-1.tgz this package].

To create Slackware packages simply run:
#> installpkg ati-slack-packager-1.1.9-noarch-1.tgz
#> sh ati-driver-installer-<version>-x86.x86_64.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 ati-driver-installer-<version>-x86.x86_64.run --buildpkg Slackware/All
or, if drivers are quite recent, it suffices:
#> sh ati-driver-installer-<version>-x86.x86_64.run --buildpkg
Otherwise, in order to create and install directly the packages you can use (always with recent versions of the driver):
#> sh ati-driver-installer-<version>-x86.x86_64.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 ati-driver-installer-<version>-x86.x86_64.run --buildpkg custom-package/Only_Module
With '''internal SlackBuild''':
#> sh ati-driver-installer-<version>-x86.x86_64.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 ati-driver-installer-<version>-x86.x86_64.run --buildpkg custom-package/Only_X
With '''internal SlackBuild''':
#> sh ati-driver-installer-<version>-x86.x86_64.run --buildpkg Slackware/Only_X

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

接下来，执行

#> sh ati-driver-installer-<version>-x86.x86_64.run

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

== ATI Catalyst >= 11.3 ==
Since these drivers the '''internal SlackBuild''' make only one package, named ''fglrx-<version>-<architecture>-<release>.tgz'', that you can create with:
#> sh ati-driver-installer-<version>-x86.x86_64.run --buildpkg
You can also make and install the package directly with:
#> sh ati-driver-installer-<versione>-x86.x86_64.run --buildandinstallpkg

= 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

{{Useful Information|Note|The command:
#> aticonfig --initial
can help you. Do '''aticonfig''' without options for more infos.}}

= 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 =
== ATI Proprietary drivers or ATI Catalyst < 11.3 ==
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
{{Be Careful|Be Careful|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.

== ATI Catalyst >= 11.3 ==
During installation of the package ''fglrx-<version>-<architecture>-<release>.tgz'' some libraries that would be overwritten are renamed as FGL.renamed.library_name. Due to remove this package “cleanly” you should do:
#> aticonfig --uninstall
or, directly with the script:
#> /usr/share/ati/amd-uninstall.sh
or, also with any installer >= 11.3, with:
#> ati-driver-installer-<versione>-x86.x86_64.run --uninstall
Will remain only the directory ''/etc/ati'' with the configuration files.

= 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 ati-driver-installer-<version>-x86.x86_64.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 [http://www.slacky.eu/~spina/fglrx/patch/fglrx_10.3-4_with_2.6.33.x.diff 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 [http://www.slacky.eu/~spina/fglrx/patch/fglrx_10.4-5_with_2.6.34.diff 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 [http://www.slacky.eu/~spina/fglrx/patch/fglrx_10.9_with_Slackware64-13.1.diff 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:
<PRE>
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:
</PRE>
insert:
./2.6.x/Makefile

=== ATI Catalyst 10.10, 10.11 and kernel == 2.6.36.x ===
Download the [http://www.slacky.eu/~spina/fglrx/patch/fglrx_10.10-11_with_2.6.36.x.diff 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 [http://www.slacky.eu/~spina/fglrx/patch/fglrx_10.10-12_with_2.6.37.x.diff 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 =
== error: implicit declaration of function 'lock_kernel' and error: implicit declaration of function 'unlock_kernel' ==
You need to enable the '''Big Kernel Lock''' in your kernel configuration. You find it under the '''Kernel hacking''' menu. You can check if this option is enable with:
$> zcat /proc/config.gz | grep BKL
CONFIG_BKL=y

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

[http://www.slacky.eu/~spina/fglrx/patch/ati_to_gpl.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).

== 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:
http://www.x.org/wiki/radeon

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

= Acknowledgement =
Thank you at Ezio Ghibaudo and Federico Rota who have started this wiki and for help with the SlackBuild. Thanks also at all the [http://www.slacky.eu/ Italian Slackware Community] users for their feedback and support.

[[User:Spina|Spina]]

Ubuntu Jaunty Installation Guide

2011-07-14T19:01:18Z

46.137.55.35: ovGbklYHyxEoK

This has made my day. I wish all potisgns were this good.

Talk:Performance Issues

2011-07-14T16:47:44Z

46.137.94.45: HGirjMRtjHAlltzIanu

The genius store called, theyre runnnig out of you.

User talk:Dtl131

2011-07-14T15:24:34Z

46.137.190.67: rMPeiwTyJlyj

It was dark when I woke. This is a ray of susnhnie.

Talk:Ubuntu Dapper Installation Guide

2011-07-13T08:19:35Z

46.137.118.142: /* MYczPEaEVoUWXipa */ new section

it gets replaced only if there is a second device section in xorg.conf
so make sure, when it works with libGL.so.1.2 that there is no other device section than fglrx

copy of libGL.so.1.2 to /usr/lib/ works fine but check, if there is also one in /usr/lib/fglrx/libGL.so.1.2
if so, the copied version is replaced (i don't know why). so both have to be replaced.

Wow, I followed this and it doesn't work, either method......

Now what? nobody to turn to, no more help available. Is it an ATI problem or a Dapper one?

I would have never believed that as "advanced" as this O/S is that it is this difficult to get a display driver to work.

This is absolutely incredible....

the problem is the driver, not the operating system.. ATI should take a lesson from nVidia.

[UBfusion reporting]: Many ATI chipsets suffer from this, due to faulty libGl.so.1.2 in the new ATI drivers - use the old file from old drivers, read http://ubuntuforums.org/showthread.php?t=185033

== try using ONLY 128MB of UMA memory instead of Sideport+UMA ==

This is a really strange problem with the HP/Compaq R4000/zv6000:

Once upon a time, ATI driver fglrx_6_8_0-8.13.4-1.i386.rpm provided full DRI and 3D support on Ubuntu 5.04 kernel 2.6.10.
( wget http://www2.ati.com/drivers/linux/fglrx_6_8_0-8.13.4-1.i386.rpm )

Then, ATI's new releases only worked if we used 128MB of shared/system/UMA memory along with the 128MB of onboard video
memory many of these laptop models have.

Now, after installing Ubuntu 6.0.6 kernel 2.6.15, the ATI driver will only work with full DRI and 3D support if I
totally disable the 128MB of onboard video memory and use ONLY shared/system/UMA memory( 128MB )....

Now, with my fully functioning Ubuntu 5.0.4 installation, when I go from only Sideport to only UMA, the glxgears
output goes from ~1200fps to ~500fps

With the new kernel and Xorg server of Ubuntu 6.0.6 running only UMA video memory and the 5.0.4 version of glxgears,
output from that program is ~800fps. Still a 30% decrease in performance from using the 128MB of onboard/Sideport
video memory.

IMO, running like this is not a fix but a crippled hack and it would be really nice if HP/Compaq or ATI would tell us
what the problem is, why it exists, how it is to be fixed. So try just 128M of UMA in your BIOS and see if that enables
you to get DRI/Direct Rendering working with the ATI/fglrx driver.

OK - I noticed that the wiki had been updated to reflect the 8.26.18 release but the line relating to the Xpress 200M card not functioning with the 8.25.18 drivers was unchanged. Can someone confirm if the 8.26.18 drivers work with the 200M card or not?

Also effected my xpress 200m on 64bit hp pavillion. changing to fglrx and using the guide worked. but only at 128mb uma. this could be a problem for a few people and could be mentiblem with the Modelines configuration in xorg driving the TFT display out of sync. Try a lower resolution (say 1024x768, 800x600, 640x480); if it doesn't work try defining a manual modeline for the resolution you are trying. Good luck and keep posting! :-)

.

== MYczPEaEVoUWXipa ==

That addresses several of my concerns acutally.

Ubuntu Edgy Installation Guide

2011-06-01T23:06:37Z

46.137.94.45: TFeGIeiQE

Your awnesr was just what I needed. Its made my day!