cchtml.com - User contributions [en]

Ubuntu Feisty Installation Guide

2013-01-17T23:49:50Z

208.65.192.1: /* Ubuntu-specific Issues */

The [[:Category:Releases|latest]] fglrx driver supports Radeon 9500 and the X-series cards up to HD2900. Workstation cards are not supported.

Hello! edeggda interesting edeggda site! I'm really like it! Very, very edeggda good!

Very nice site!

Hello! ebdeedd interesting ebdeedd site! I'm really like it! Very, very ebdeedd good!

Very nice site!

==See Also==
*[[Frequently Asked Questions]]
*[[Performance Issues]]
*[[Troubleshooting]]
*[http://www.petitiononline.com/x200MLin/petition.html Petition for better ATI/AMD Radeon XPRESS 200M Linux Drivers]
* [http://ubuntuforums.org/showpost.php?p=2221323

[[Category:Installation Documentation]]

Ubuntu Feisty Installation Guide

2013-01-17T23:48:37Z

208.65.192.1: /* Pre-Installation Checks */

The [[:Category:Releases|latest]] fglrx driver supports Radeon 9500 and the X-series cards up to HD2900. Workstation cards are not supported.

Hello! edeggda interesting edeggda site! I'm really like it! Very, very edeggda good!

== Installation ==

===Method 1: Install the Driver the Ubuntu Way===
<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-generic restricted-manager
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
</pre>

Note: The second line of the above may not be necessary. If apt says it cannot find the "linux-restricted-modules" package, try line 3. If that fails, check your sources.list (see top of page)

If the system complains about dependencies, use your preferred package manager to download python2.4 and, if necessary, its dependencies.

===Method 2: Install the 8.42.3 Driver Manually===

*Note: ''This is just an alternative installation method for the section above. It might help if you still get 'DRI missing' errors.''

Download the ATI driver installer:
[http://www2.ati.com/drivers/linux/ati-driver-installer-8.42.3-x86.x86_64.run ati-driver-installer-8.42.3-x86.x86_64.run] (this installer is for 32bit '''and''' 64bit systems)

'''Alternatively:''' You can get the newest driver from here: [http://ati.amd.com/support/drivers/linux/linux-radeon.html].

Change to the download directory. Make sure that you have the ''universe'' and ''multiverse'' repositories enabled in ''/etc/apt/sources.list'' before doing these steps.

There is a detailed manual with screenshots at [https://wiki.ubuntu.com/AddingRepositoriesHowto Ubuntu Wiki].

By default, Ubuntu does not enable the Universe and Multiverse repositories. But they include some important programs and codecs, so it is highly recommended to activate them.

''Install necessary tools:''
<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper \
debconf libstdc++5 linux-headers-generic
</pre>

''Create .deb packages:''
<pre>
sudo chmod u+x ati-driver-installer-<version>.run
# e.g. sudo chmod u+x ./ati-driver-installer-8-8-x86.x86_64.run
sudo ./ati-driver-installer-<version>.run --buildpkg Ubuntu/<release>
# e.g. sudo ./ati-driver-installer-8-8-x86.x86_64.run --buildpkg Ubuntu/hardy
</pre>

''Blacklist old fglrx module from linux-restricted-modules:''

*Note: You only need to do this if you've installed the driver from Method 2 above.

As ubuntu's ''linux-restricted-modules'' package includes the fglrx module from an old driver version (8.28.8), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.

Ubuntu/Gnome users type in:
<pre>gksu gedit /etc/default/linux-restricted-modules-common</pre>

Kubuntu/KDE users type in:
<pre>kdesudo kate /etc/default/linux-restricted-modules-common</pre>

Add "fglrx" to the line "DISABLED_MODULES"
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.42.3-1*.deb \
fglrx-kernel-source_8.42.3-1*.deb \
fglrx-amdcccle_8.42.3-1*.deb
</pre>

*Note: If you have a 64 bit install, the above dpkg command will likely complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you recieve this error, issue the following command after the above dpkg command, which will force the installation of all of the 32 bit dependencies, and then the amdccle package:

<pre>
sudo apt-get install -f
</pre>

''Remove any old fglrx debs from /usr/src/:''
<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Fix broken dependencies''
*Note: ''You only need to do this if you have installed previous versions of these drivers using this method before.''
<pre>
sudo apt-get -f install
</pre>

''Compile the kernel module:''
*Note: ''Since Catalyst 7.12, this step is not needed anymore, because the fglrx-kernel-source package compiles and installs the module.''
<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a
</pre>

It's necessary, because sometimes this file is written by other packages, and so there's no 3D acceleration.

''Create the following folder''

<pre>
sudo mkdir /lib/modules/$(uname -r)/volatile
</pre>

''Create a symbolic link''

<pre>
sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko
</pre>

'''IMPORTANT''': You have to recompile the kernel module after each kernel update!

===Configure the Driver===
*Note Method 2 Users: Before you carry out this step you must reboot your machine. Or else the fglrx driver will not be in use on xorg.conf and using the aticonfig options will cause a memory dump and not intialise the Driver properly.
*Note: An '''alternative''' to the '''aticonfig --initial''' command is to edit ''/etc/X11/xorg.conf'' and replace the string "ati" with "fglrx" in the "Device" section. This way you won't lose your old "Screen" and "Monitor" settings. Afterwards you can use aticonfig for setting overlay etc. Another alternative is '''aticonfig --initial --force''' if you encounter issues with the first command.
<pre>
sudo aticonfig --initial
</pre>
Then:
<pre>
sudo aticonfig --overlay-type=Xv
</pre>
*Note: Is there an alternative to the previous step?

===Finish the Installation===
Now save any open document and reboot your system:
<pre>
sudo shutdown -r now
</pre>
*Note: An '''alternative''' to rebooting is to restart the X Server by pressing your CTRL ALT BACKSPACE keys. You must remove any old kernel modules such as "drm" "radeon" or "fglrx" using the "rmmod" command. Example: <code>sudo rmmod fglrx</code>

== Post-Installation Checks ==
===Verifying===
Run the following command to check its output to ensure the fglrx driver is installed properly:
<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON 9600/9700 Series
OpenGL version string: 2.0.6650 (8.40.4)
</pre>
The <code>OpenGL vendor string</code> should read '''ATI''' and not '''Mesa'''.

If you see a message like 'Xlib: extension "XFree86-DRI" missing on display ":1.0"' then you may have to add the following to /etc/X11/xorg.conf (see [http://ubuntuforums.org/showthread.php?t=292642#post1714920]):
{{Box File|/etc/X11/xorg.conf|
<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection
</pre>
}}

=== Additional configure with aticonfig tool ===
You can even more configure the driver with the '''aticonfig''' tool, more information can be found at [[Configuring]].

For example: <br>
* use powerplay option to switch power state for battery friendly or performance mode
* use dual head or one big desktop mode
* turn second monitor on/off on the fly

==Ubuntu-specific Issues==

Tocuhdwon! That's a really cool way of putting it!

=== If suspend is not working ===

If suspend stops working after fglrx installation, meaning display will not initialize after attempting to resume, then changing a few options has been reported to work for some hardware. 

For ATI X700 and ATI X1100 on Acer Aspire 5051:
{{Box File|/etc/default/acpi-support|
<pre>
SAVE_VBE_STATE=false
POST_VIDEO=true
USE_DPMS=false
</pre>
}}

For ATI X1300 and the ATI X1400 on a Dell Inspiron 9400 or Lenovo Thinkpad T60, also for ATI X1600 on Asus Z96J (using install method 2):
{{Box File|/etc/default/acpi-support|
<pre>
POST_VIDEO=false
</pre>
}}

==See Also==
*[[Frequently Asked Questions]]
*[[Performance Issues]]
*[[Troubleshooting]]
*[http://www.petitiononline.com/x200MLin/petition.html Petition for better ATI/AMD Radeon XPRESS 200M Linux Drivers]
* [http://ubuntuforums.org/showpost.php?p=2221323

[[Category:Installation Documentation]]

Red Hat Enterprise Linux

2012-09-11T08:17:44Z

208.65.192.1: /* Important Note as of 5/18/2009 */

"Red Hat Enterprise Linux is the leading platform for open source computing. It is sold by subscription, delivers continuous value and is certified by top enterprise hardware and software vendors. From the desktop to the datacenter, Enterprise Linux couples the innovation of open source technology and the stability of a true enterprise-class platform." -redhat.com

Please note that Red Hat Enterprise Linux and Fedora Core are distantly related and are not the same product. Please see the [[Fedora]] distribution page for more details.

Another option for those wanting the stability of RHEL, there are various RHEL clones, some of them listed below:

- [http://centos.org/ CentOS] is a community effort which tracks each RHEL release and update and offers up2date and yum service. All this for free, donations encouraged.

- The [http://linux.startcom.org/ StartCom Linux] operating systems, are based on the RedHat Enterprise and Fedora source code each modified with reliability, security and efficiency in mind, to fit the tasks assigned to each flavor of StartCom Linux.

Hello! bkddkkd interesting bkddkkd site! I'm really like it! Very, very bkddkkd good!

Very nice site!

Hello! eagcbgk interesting eagcbgk site! I'm really like it! Very, very eagcbgk good!

==Tips and Tricks==
If you have SELinux enabled and set to enforcing you may need to change the context of the fglrx_dri.so file for it to load properly:

chcon -t textrel_shlib_t /usr/lib/dri/fglrx_dri.so

Substitute lib with lib64 where appropriate.

Tip for Centos 5.4 x86_64 kernel 2.6.18+
Before installing the driver package it is absolutely vital to ensure that version/build number in /lib/modules/{your kernel build}/build/include/linux/utsrelease.h number is EXACTLY the same as the output of uname -r

for example
uname-r
2.6.18-164.el5
cat /lib/modules/2.6.18-164.el5/build/include/linux/utsrelease.h
#define UTS_RELEASE "2.6.18-164.'''1.15'''.el5"

fglrx.ko will NOT be built and installed properly due to the discrepancy (1.15) in utsrelease.h.

In most cases modifying utsrelease.h solves the problem

==Related Resources==
[http://ati.amd.com/support/drivers/linux/linux-radeon.html Follow link "ATI Driver Installer"]

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

Ubuntu Maverick Installation Guide

2012-07-30T14:24:57Z

208.65.192.1: /* Hardware Video Decode Acceleration (EXPERIMENTAL) */

__TOC__

Hello! aakdccc interesting aakdccc site! I'm really like it! Very, very aakdccc good!

Very nice site!

Hello! gdcebcg interesting gdcebcg site! I'm really like it! Very, very gdcebcg good!

Very nice site!

=Updating Catalyst/fglrx=

DO NOT try to install a new version over an old one. Follow the 'Removing the Driver' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.

=Removing Catalyst/fglrx=
The uninstall script in the first command will only exist if you downloaded the drivers and installed the directly (rather than building packages as this guide does). Skip the first command if it does not exist.
$ sudo sh /usr/share/ati/fglrx-uninstall.sh
$ sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev* xorg-driver-fglrx

If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]
$ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
$ sudo apt-get install xserver-xorg-video-ati
$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup

= Issues =

== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==

If the installation fails and you find the above message in /var/lib/dkms/fglrx/8.780/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:
$ ls -la /usr/bin/gcc
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.4 in Ubuntu Maverick). This should allow you to install fglrx:
$ sudo ln -sf /usr/bin/gcc-4.4 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
$ sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957

== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==
Most likely, you probably did not have the "ia32-libs" package installed beforehand. If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

$ sudo apt-get -f install

Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:
$ sudo dpkg -i --force-overwrite fglrx*.deb

== Problems Starting Xserver ==

If you get a black screen hang, the first thing to check is if xorg.conf is the problem.

You can disable the xorg.conf with:
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled

Reboot and check to see if things work now.

You can reinstate the file with:
$ sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf

Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick for me -

$ start on filesystem
$
$ script
$ chmod 0666 /dev/null
$ chmod 0666 /lib/udev/devices/null
$ end script

This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (amdconfig --tls=0) to get things to stay stable!

If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:
$ sudo amdconfig --acpi-services=off
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.

== Slow Maximizing Windows/General 2D Slowness ==
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. If you're not running compositing/desktop effects, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:
$ sudo amdconfig --set-pcs-str=DDX,ForceXAA,TRUE

In the last case (at least) it is essential to run it without the Xorg server working. To do so, press CTRL+ALT+F1, log in and type the following (this will close all your programs so save your work before):
$ sudo service gdm stop
$ sudo amdconfig --set-pcs-str=DDX,ForceXAA,TRUE
$ sudo service gdm start

== Unsupported Hardware Watermark ==
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help.

If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a newer version of Catalyst than the one you're running.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run
$ chmod +x amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run
$ sh amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --extract driver
$ sudo mv /etc/ati/control ~/control.bak
$ sudo cp driver/common/etc/ati/control /etc/ati

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
$ sudo apt-get remove xserver-xgl
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
$ DISPLAY=:0 glxinfo | grep render
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

== Hang at logout ==

If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorisation files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server.

Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do:
(assuming that the installer is in the directory we used to install)

$ cd ~/catalyst{{Catalystversion}}
$ sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
$ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
$ sudo chmod +x /etc/ati/authatieventsd.sh

This problem can be fixed permanently with:

$ sudo mkdir -p /var/lib/xdm/authdir
$ sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles

If that doesn't work then you can disable atieventsd with this command:

$ sudo /usr/sbin/update-rc.d -f atieventsd remove

You'll have to restart for this to take effect.

== Suspend/Hibernation ==

Suspend hibernation '''works''' with the latest driver.

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)

<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection
</pre>

Another way to get it working is to do enable Composite, but when you want to suspend simply disable Compiz Fusion. How would you do that? Easy! Install the fusion-icon package (in repos by default):

$ sudo apt-get install fusion-icon

After you have done that, launch it (Applications > System > Compiz Fusion Icon) and it appears in your notification area. To switch, simply right-mouse click on the icon and select Metacity. Your desktop will flicker and windows will dissapear, but after a while they appear again. Now try to suspend.

When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)

KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.

Hopefully this helped some people, as it did for me!
Solution posted by zwyber@gmail.com

== Can't remove fglrx with dpkg (diversion issue) ==

If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:
<pre>dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
$ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

== This module/version combo is already installed ==

If you get this error-message, simply uninstall the previous version before installing the new one with:
$ sudo dkms remove -m fglrx --all

== New kernel installed? ==
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:
$ sudo dkms build -m fglrx -k `uname -r`
$ sudo dkms install -m fglrx -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]

== amdconfig not found after installation & "module does not exist" after boot ==
This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous use of fglrx through the Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing amdconfig --initial after driver installation, you might end up not having the amdconfig available at all:
<pre>amdconfig: command not found</pre>
After booting you might receive X error '(EE) Failed to load module "fglrx" (module does not exist, 0)'. These do not necessarily indicate that the installation has failed completely. On command line, do
$ ls /usr/lib/fglrx/bin
and see if the command lists some Ati related programs. If they are listed but not found from /usr/bin, it is possible that the "update-alternatives" fglrx .deb installation does has been ignored. See man update-alternatives for more information about the concept and workings of alternatives. In practice, update-alternatives is supposed to create several symbolic links to the files in the fglrx directory, but it will be ignored if the alternatives for the very related gl_conf entry has been set to manual. Do
$ update-alternatives --get-selections | grep gl_conf
and see if the mode is manual instead of auto and if mesa is mentioned instead of fglrx in the path that is printed. In this case you need to
$ sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf
to set fglrx as the active alternative. You can alternatively (no pun intended) and additionally change the gl_conf into automatic mode before the installation this way:
$ sudo update-alternatives --auto gl_conf
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.