Ubuntu Gutsy Installation Guide

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. sudo apt-get update sudo apt-get install linux-restricted-modules-generic restricted-manager sudo apt-get install xorg-driver-fglrx sudo depmod -a

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

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

Download page: Catalyst -- File:. This package contains both the 32-bit and 64-bit driver.

Change to the directory you downloaded the file. 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 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:

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

If using 64bit make sure to collect package "ia32-libs" before you continue!

Create .deb packages:

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.

As an alternative, you can just use

which will download all the needed packages by itself and also automatically detects the Ubuntu version used.

If this step fails on amd64/x86_64 with a No such file or directory message about missing files in X11R6/lib, follow these instructions and come back here. Also check that your download path 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: gksu gedit /etc/default/linux-restricted-modules-common

Kubuntu/KDE users type in: kdesu kate /etc/default/linux-restricted-modules-common

Add "fglrx" to the line "DISABLED_MODULES"

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.4) is in use.

You may also need to edit the file (if it exists): gksu gedit /etc/modprobe.d/blacklist-restricted 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/: sudo rm /usr/src/fglrx-kernel*.deb

Install .deb packages:

sudo dpkg -i xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb

Additional 64-bit instructions

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:

sudo apt-get install -f

Catalyst 8.3 on 64-bit systems requires the --force-overwrite command in the above dpkg command: sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb

Im not wrhoty to be in the same forum. ROTFL

Configure the Driver
sudo aticonfig --initial Then: sudo aticonfig --overlay-type=Xv
 * NOTE THIS WILL ERASE SETTINGS IN /etc/X11/xorg.conf you should be sure there is a backup.
 * 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.
 * Note: Alternative in the overlay-type to "Xv" can be "opengl" or "disable" if the TV-out makes problems in videos.

Hi Matthias,Unfortunately no. I haven't had the time to look into it again. Very busy with work I'm airafd  not even enough time to blog!If you find or figure anything out though please let me know

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!! sudo aticonfig --enable-monitor=tv To change back to VGA: sudo aticonfig --enable-monitor=crt1 Some have had luck with both mirrored. sudo aticonfig --force-monitor=crt1 sudo aticonfig --enable-monitor=crt1,tv reboot after that and it should mirror the CRT1 onto the TV.

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

Verifying
Run the following command to check its output to ensure the fglrx driver is installed properly:

$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

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 sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

The  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:
 * $ less /var/log/Xorg.0.log |grep EE if this command returns  then remove the kernel module and reinstall it.
 * $ sudo dkms remove -m fglrx -v 8.471 --all


 * Remove all the packages provided by the  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  package. Your problem is probably somewhere else. (taken from ).


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

Switch FGLRX_ACPI_SWITCH_POWERSTATES to true

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:
 * 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
Your awnser was just what I needed. Its made my day!

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

It may be necessary to create the /usr/X11R6/lib directory first:

sudo mkdir /usr/X11R6/lib

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  or   returns a Segmentation fault like this: $ 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

Set output of libGL to verbose with $ export LIBGL_DEBUG=verbose

Run  or   again 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

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 ls -l /usr/lib/dri/ |grep fglrx_dri -rw-rw 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so

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

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

Now I know who the brainy one is, Ill keep lokinog for your posts.

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

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

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

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

Revert to Xorg driver
If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing sudo dpkg-reconfigure xserver-xorg 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:

sudo apt-get install --reinstall libgl1-mesa-glx