cchtml.com - User contributions [en]

Ubuntu Hardy Installation Guide

2008-05-06T22:04:27Z

24.254.11.230:

Ubuntu Hardy Installation Guide

2008-05-06T22:03:26Z

24.254.11.230:

Ubuntu Hardy Installation Guide

2008-04-30T00:04:32Z

24.254.11.230: /* Installation */

Ubuntu Hardy Installation Guide

2008-04-30T00:03:54Z

24.254.11.230: /* Installation */

Ubuntu Hardy Installation Guide

2008-04-30T00:03:08Z

24.254.11.230: /* Finishing the Install: Configuration */

Ubuntu Hardy Installation Guide

2008-04-30T00:01:03Z

24.254.11.230: /* Installation */

Ubuntu Hardy Installation Guide

2008-04-30T00:00:25Z

24.254.11.230: /* Finishing the Install: Configuration */

Ubuntu Hardy Installation Guide

2008-04-29T23:51:26Z

24.254.11.230: /* Installation */

Ubuntu Hardy Installation Guide

2008-04-29T23:50:39Z

24.254.11.230:

Ubuntu Hardy Installation Guide

2008-04-29T23:50:24Z

24.254.11.230:

Ubuntu Hardy Installation Guide

2008-04-29T23:49:34Z

24.254.11.230: /* Installation */

Ubuntu Hardy Installation Guide

2008-04-29T23:49:18Z

24.254.11.230: /* Installation */

Ubuntu Hardy Installation Guide

2008-04-29T23:47:28Z

24.254.11.230: /* Method 1: Install the driver the Ubuntu Way */

Ubuntu Hardy Installation Guide

2008-04-29T23:46:48Z

24.254.11.230: /* Method 2: Manual Method */

Ubuntu Hardy Installation Guide

2008-04-29T23:37:16Z

24.254.11.230: /* Method 2: Manual Method */

Ubuntu Hardy Installation Guide

2008-04-29T23:36:11Z

24.254.11.230: /* Additional 64-bit instructions */

Ubuntu Hardy Installation Guide

2008-04-29T23:35:28Z

24.254.11.230: /* Additional 64-bit instructions */

Ubuntu Gutsy Installation Guide

2008-01-20T17:04:59Z

24.254.11.230: /* Method 2: Install the Catalyst 8.1 Driver Manually */

==Pre-Installation Checks==
=== Enable "restricted" Repository ===
Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

System > Administration > Software Sources. Check "Proprietary Drivers for Devices (Restricted)" box.

== Installation ==

For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 7.10 (Gutsy) 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 driver that is currently in the repositories. It may be older than the current version from AMD.
<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 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 Catalyst 8.1 Driver Manually===

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

*Note: ''If you are running the -rt kernel, you will fail to compile the kernel module with ''"FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol '__rcu_read_lock'"''.''

Download the ATI driver installer:
[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8-01-x86.x86_64.run ati-driver-installer-8-01-x86.x86_64.run] (this installer is for 32bit '''and''' 64bit systems)

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 did not enable the Universe and Multiverse repositories, but now in Gutsy, both Universe and Multiverse are activated by default.

''Install necessary tools:''
<pre>
sudo apt-get update
sudo apt-get install build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

''Uninstall previous fglrx:''
Using Synaptic, completely remove any packages containing "fglrx" in their name.

''Create .deb packages:''
<pre>
sh ati-driver-installer-8-01-x86.x86_64.run --buildpkg Ubuntu/gutsy
</pre>
note: if this step fails with a signal being caught, and you are running the script on an NFS-mounted directory, copy it to a local partition, and it will work. The same error may result from insufficient disk space.

If this step fails on amd64/x86_64 with a <tt>No such file or directory</tt> message about missing files in <tt>X11R6/lib</tt>, [http://emmetcaulfield.net/tech/Ubuntu64+ATI follow these instructions] and come back here. Also check that your downloadpath does not contain spaces.

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

As Ubuntu Gutsy's ''linux-restricted-modules'' package includes the fglrx module from an old driver version (8.37.6), 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>kdesu 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>
}}
Please note that after the modification above, the "Restricted Driver Manager" will signal "ATI accelerated grapichs 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 (7.12) is in use.

You may also need to edit the file (if it exists):
<pre>/etc/modprobe.d/blacklist-restricted</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.

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

''Install .deb packages:''

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

*Note: If you get a 'Bad file descriptor' message concerning the xorg.conf file try switching user to root and repeating the same command without sudo. This might be valid for the following commands too. (Ubuntu Gutsy installs with no password set for root by default. You can set a password for the root by typing 'sudo passwd root' first.)

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

Nevertheless the previous command is always recommended.

===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: Alternative in the overlay-type to "Xv" can be "opengl" or "disable" if the TV-out makes problems in videos.

====Alternative: Configure the Driver, The Manual Way:====
An alternative to the "''sudo aticonfig''" commands is to edit "''/etc/X11/xorg.conf''" and change the "Device" section for the video card as shown below. This way you won't lose your old settings.
<pre>
gksu gedit /etc/X11/xorg.conf
</pre>
<pre>
Section "Device"
[...]
# Driver "vesa"
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
[...]
EndSection
</pre>

==== TV - Out ====
The composite TV-Out is not working simultaneously with the VGA on my System. To use it I have turned the VGA off and only the TV on. Attention! This command turns off your Monitor!!
<pre>
sudo aticonfig --enable-monitor=tv
</pre>
To change back to VGA:
<pre>
sudo aticonfig --enable-monitor=crt1
</pre>

===Finish the Installation===
Now save any open document and reboot your system:
<pre>
sudo shutdown -hr 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>
*Note: Another way to reboot:
<pre>
sudo reboot
</pre>

== Post-Installation Checks and Tweaks ==
===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 Radeon Xpress Series
OpenGL version string: 2.1.7170 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.4331 --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]).

'''If it says '' libGL.so.1: cannot open shared object file: No such file or directory''...'''
Check if you have a ''/usr/lib/libGL.so.1.2'', if so do this:
$ ls -l /usr/lib/libGL*
* The file permission 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:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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>

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

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

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

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

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

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>

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