cchtml.com - User contributions [en]

Ubuntu Gutsy Installation Guide

2008-08-29T12:23:02Z

202.7.176.133: Bot spam removed

== Post-Installation Checks and Tweaks ==
===Verifying===
Run the following command to check its output to ensure the fglrx driver is installed properly:

64bit Users only ( 32bit users can continue to the fglrxinfo test ), after rebooting you may have noticed that you cant open aticonfig and the fglrxinfo test below may not show ati in the info from the test, to fix this in terminal do the following command
<pre>
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1
</pre>

<pre>
$fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON X300
OpenGL version string: 2.1.7415 Release
</pre>
The <code>OpenGL vendor string</code> should read '''ATI''' and not '''Mesa'''.

'''If it still says ''Mesa'' and not ''ATI'', even after re-enabling the driver from the Restricted-manager:'''
You can try the following:
:*<pre>$ less /var/log/Xorg.0.log |grep EE</pre> if this command returns <code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</code> then remove the kernel module and reinstall it.
:: <pre>$ sudo dkms remove -m fglrx -v 8.471 --all</pre>

:*Remove all the packages provided by the <code>xserver-xorg-video-all</code> meta-package (search for it using Synaptic or Adept), then restart the machine. The X Server should now use the new fglrx driver by force (provided the driver is being used in ''xorg.conf'').
::If you can't log in after this, you'll have to log in to a terminal in the login screen, and reinstall the <code>xserver-xorg-video-all</code> package. Your problem is probably somewhere else. (taken from [http://ubuntuforums.org/showpost.php?p=3655658&postcount=139]).

:*Remove the package 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
::<pre>DISPLAY=:0 glxinfo | grep render</pre>
::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.

Note: Here is the [[glxinfo]] of a good install (for those interested).

=== Enable laptop mode on battery power ===

Enabling laptop mode on battery power gives you much better battery life, however be aware that sometimes it causes odd hangs.

Switch ENABLE_LAPTOP_MODE to true
{{Box File|/etc/default/acpi-support|
<pre>
# Switch to laptop-mode on battery power - off by default as it causes odd
# hangs on some machines
ENABLE_LAPTOP_MODE=true
</pre>
}}

Switch FGLRX_ACPI_SWITCH_POWERSTATES to true
{{Box File|/etc/default/fglrx|
<pre>
# Uncomment the next line to enable powerstate switching on ACPI
# events for lid open/close and AC adapter on/off
FGLRX_ACPI_SWITCH_POWERSTATES=true
</pre>
}}

=== Additional configure with aticonfig tool ===
You can configure the driver even further 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

==Specific Issues==

=== 3D desktop effects ===
The new ATI drivers use AIGLX so there is not need to install XGL that older drivers (< 8.40) required.

Remove this section from to the /etc/X11/xorg.conf file.
The new xorg server enables "Composite" by default.
<pre>
# Section "Extensions"
# Option "Composite" "0"
# EndSection
</pre>

Compiz does not know about the fglrx driver. You can either skip the checks

<pre>mkdir -p ~/.config/compiz && echo SKIP_CHECKS=yes >> ~/.config/compiz/compiz-manager</pre>

or add it to the compiz white list, and clear the blacklist pci Ids variable '''*Recommended*'''

<pre>sudo gedit /usr/bin/compiz</pre>

<pre>
# Driver whitelist
WHITELIST="fglrx nvidia intel ati radeon i810"
</pre>

<pre>
# blacklist based on the pci ids
# BLACKLIST_PCIIDS="$T"
BLACKLIST_PCIIDS=""
</pre>

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

After the necessary configurations, just restart X and enjoy the cool effects.

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu [this line may instead be in /etc/xdg/compiz/compiz-manager] and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

For Kubuntu you need some extra steps:
<pre>
sudo apt-get install compiz compiz-kde compizconfig-settings-manager compiz-core compiz-fusion-plugins-main compiz-plugins
</pre>

To test 3D Effects, press ALT+F2 and type "compiz --replace".

To configure use the tool KMenu->Settings->Avanced Desktop Effect Settings.

=== Suspend/Hibernation work with 7.12===

With Gutsy release, there was a big problem using the ATI proprietary drivers. The Suspend/Hibernate function stopped working. The problem was due to the new SLUB allocator incorporated in 2.6.22 / 2.6.23 Kernel.

'''The problem has been solved in the AMD Catalyst 7.12 driver release.'''
'''UPDATE: The problem has NOT been solved in the AMD Catalyst 7.12 driver release.'''

Suspend/hibernate is not working for FireGL 5250.
For FireGL 5200, suspend works with the 7.12 fglrx kernel module loaded (which did not work before this release) , but does not work if X is running.

For Thinkpad T60 with ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:

SAVE_VBE_STATE=false

POST_VIDEO=false

Even with the above settings (like POST_VIDEO=false, etc.) my ASUS Z96J with an X1600 does not suspend.

This bug has been a serious issue for several months now. There is a lot of frustration over this, because Ubuntu/Canonical has not been helpful. They've said things like suggesting not using fglrx (thanks a lot, that really helps).

Current status on this bug can be found here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/121653/

===If you get /usr/X11R6/lib/modules/dri/fglrx_dri.so not found===

sudo ln -s /usr/lib/ /usr/X11R6/lib/modules

===If you get /usr/X11R6/lib64/modules/dri/fglrx_dri.so not found===

sudo ln -s /usr/lib/ /usr/X11R6/lib64/modules

===Segmentation Fault with glxinfo/fglrxinfo===
If <code>fglrxinfo</code> or <code>glxinfo</code> returns a Segmentation fault like this:
<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon Xpress Series
OpenGL version string: 1.4 (2.1.7170 Release)

Segmentation fault
</pre>

Set output of libGL to verbose with
<pre>$ export LIBGL_DEBUG=verbose</pre>

Run <code>fglrxinfo</code> or <code>glxinfo</code> again
<pre>libGL: XF86DRIGetClientDriverName: 8.44.3 fglrx (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/fglrx_dri.so
libGL error: dlopen /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: cannot open shared object file: Permission denied)
libGL error: unable to load driver: fglrx_dri.so
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon Xpress Series
OpenGL version string: 1.4 (2.1.7170 Release)

Segmentation fault</pre>

Don't know if its always fglrx_dri.so, but the fix is to add read permissions to the file.

Check if read permission is not there
<pre>ls -l /usr/lib/dri/ |grep fglrx_dri
-rw-rw---- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so
</pre>

Add read permission
<pre>$ sudo chmod +r /usr/lib/dri/fglrx_dri.so</pre>

Check read permission
<pre>ls -l /usr/lib/dri/ |grep fglrx_dri
-rw-rw-r-- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so
</pre>

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

=== Monitor detection (1680x1050 Resolution Issue)--- SOLVED ===

As specified in the release notes, "Connecting a display device that supports 1680x1050 to a system running Linux may result in a
maximum display resolution of 1280x1024 only being available". (from [http://ubuntuforums.org/showthread.php?t=645974 thread])

['''It works with the latest driver''']

Fglrx driver does not detect some monitors correctly, so you have to do it manually (google about your monitor spec with keyword: xorg.conf).

'''For example:''' Samsung 205BW 1680x1050 monitor needs manually set:
{{Box File|/etc/X11/xorg.conf|
<pre>
Section "Monitor"
Option "DPMS"
Identifier "samsung-monitor"
VendorName "Samsung"
ModelName "SyncMaster 205BW"
HorizSync 31.4 - 80.0
VertRefresh 56.000 - 75.000
Modeline "1680x1050" 146.25 1680 1784 1960 2240 1050 1053 1059 1089
EndSection

Section "Screen"
Identifier "samsung-screen"
Device "samsung-device"
Monitor "samsung-monitor"
Defaultdepth 24
SubSection "Display"
Depth 24
Modes "1680x1050"
EndSubSection
EndSection
</pre>
}}

=== A possible problem with fglrx.ko conflicts ===

NOTE: I've run into strange problem building fglrx-kernel-source_8.443.1-1_i386.deb. If pentium-builder is installed, dkms fails to build fglrx.ko for make error (mixed implicit and static pattern rules. Stop.). It is caused by gcc.real and other indirections and wrong gcc version detection. Removing pentium-builder cures the problem.

It's necessary, because sometimes this file is written by other packages, and so there's no 3D acceleration.
Check that the file /lib/modules/$(uname -r)/misc/fglrx.ko has been created.

''Create the following folder''

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

Note: the volatile directory might already exist at this stage then simply continue with the next step.

''Create a symbolic link''

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

NOTE : On my Gutsy install, after a reboot this link was always removed automatically leaving me without an fglrx module loaded, and thus no ATI rendering. There have been several ways of getting around this suggested here, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko
exit 0

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</pre>

=== Hang at logout ===

If you experience hangs when logging out (of X) try disabling atieventsd with this command:

<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre>

== Revert to Xorg driver ==

If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
<pre>sudo dpkg-reconfigure xserver-xorg</pre>
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.

You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:

<pre>sudo apt-get install --reinstall libgl1-mesa-glx</pre>

==See Also==
*[[Frequently Asked Questions]]
*[[Performance Issues]]
*[[Troubleshooting]]

[[Category:Installation Documentation]]

Ubuntu Hardy Installation Guide

2008-08-02T10:55:41Z

202.7.176.133: /* Follow These Instructions Carefully */

== Installation ==

For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.04 (Hardy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the "ATI accelerated graphics driver". Ubuntu will then install and configure the driver for you. If this does not provide the optimal solution you were looking for, please read ahead.

=== Method 1: Install the driver the Ubuntu Way ===

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by the Ubuntu people. Catalyst 8.3 is in the repositories.

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

The second line may not be necessary as you may already have restricted modules installed. Run it just in case. If the third line fails, you probably don't have the restricted repository enabled. See Pre-Installation.

After this, you'll may need to edit Xorg.conf:

<pre>
sudo gedit /etc/X11/xorg.conf
</pre>

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

<pre>
sudo aticonfig --initial -f
</pre>

After this you should be able to restart your computer and have the driver working. To test type

<pre>
fglrxinfo
</pre>

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

==== Post-Installation Tweaks ====
To enable hardware accelerated video on pre-R500 cards, edit '''/etc/X11/xorg.conf''' to include the following lines without '''[...]'''

<pre>
Section "Device"
[...]
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
[...]
EndSection
</pre>

Note that when Visual Effects (Compiz) are active, flickering and artifacts may occur in OpenGL applications and hardware accelerated video windows (particularly with R300 chipset). To prevent this, disable Visual Effects.

=== Method 2: Manual Method (installing Catalyst 8.7) ===

https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8-7-x86.x86_64.run

(this installer is for 32bit '''and''' 64bit systems)

==== Follow These Instructions Carefully ====

Switch to the directory you downloaded this into. (Make sure ''universe'' and ''multiverse'' are enabled in your repository sources).

If you are using the x86_64 architecture (64 bit), be sure to inst "ia32-libs" before proceeding!

<pre>
sudo apt-get update
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
</pre>

(package '''cdbs''' is required starting with Catalyst 8.7). On my machine it was installed during the package build process following the below command.

Now use the following command to create the .deb files you will be using for installation:

<pre>
sh ati-driver-installer-8-7-x86.x86_64.run --buildpkg Ubuntu/hardy
</pre>

Now we have to blacklist the driver in Ubuntu's repository, so that the new driver will be used.

<pre>
sudo gedit /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>
}}

Please note that after the modification above, the "Restricted Driver Manager" will signal "ATI accelerated graphics driver" not enabled (unticked). This is perfectly correct. At the end of the installation procedure it will signal in Status: "in use" (green light), but NOT enabled. It simply means that the fglrx module contained in the linux-restricted-modules package is not enabled, but another fglrx module (8.7) is in use.

You may also need to edit the file(s) (if they exist):
<pre>sudo gedit /etc/modprobe.d/blacklist-restricted
sudo gedit /etc/modprobe.d/blacklist-local</pre>

Put a # in front of the line "blacklist fglrx", if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration.

Install .debs:

<pre>
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
</pre>

==== Additional 64-bit instructions ====

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

Catalyst 8.7 on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
<pre>
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.512*.deb fglrx-kernel-source_8.512-0*.deb fglrx-amdcccle_8.512-0*.deb
</pre>

When installing the packages, if <tt>xorg-driver-fglrx_8.512</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].

====Fix for an error:====
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

==== Finishing the Install: Configuration ====

If you've used fglrx previously, you will not need to do this.

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist):
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
<pre>sudo aticonfig --initial -f</pre>
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:
<pre>
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1
</pre>
Finally, reboot the computer and type
<pre>
fglrxinfo
</pre>
into the terminal. If the vendor string contains ATI, you have installed the driver successfully.

Please note: Depending on the particular ATI card that you own, you may or may not automatically have all of the relevant driver features enabled. R500 and R600 cards (X1xxx, HD series, and newer) in particular will need TexturedVideo enabled in Xorg.conf (rather than the traditional VideoOverlay) in order to support Xv accelerated video playback.

=== Removing Mesa drivers ===
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, check:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''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
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
: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>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *</i>

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Specific Issues ==

=== 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. This can be fixed permanently with:

<pre>sudo mkdir -p /var/lib/xdm/authdir
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre>

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

<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre>

=== Suspend/Hibernation ===

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

For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:

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

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

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

Simply uninstall the previous version before installing the new one with
<pre>
sudo dkms remove -m fglrx -v 8.493.1 --all
</pre>

[[Category:Installation Documentation]]