cchtml.com - User contributions [en]

Ubuntu Precise Installation Guide

2012-06-21T19:36:52Z

202.156.10.13: Undo revision 8632 by 176.32.73.44 (talk)

__TOC__

= The Options =
Users with ATI cards have the following driver options:
* '''vesa''' - very basic, lacks 2D/3D acceleration, and focuses on compatibility with all VESA-compliant graphics cards. It is good for starting the GUI environment when no accelerated driver is available/working, and little else.
* '''ati''' - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards).
* '''radeon''' - open source driver supporting all Radeon cards. This driver has excellent 2D acceleration and compatibility with the Linux graphics stack. 3D acceleration is sufficient for desktop effects and a nice set of native Linux games. Power management is now comparable to the Catalyst driver.
* '''Catalyst (a.k.a fglrx)''' a proprietary "blob" (closed source binary) driver designed by ATI, with 3D code based off of their Windows driver. Only RadeonHD chips are supported on recent Linux distros.

= Updated Open Source Driver PPA's =
* '''"Ubuntu-X"''' : This PPA offers the latest stable releases of video driver-related components. Follow the instructions at: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
* '''Xorg-edgers''': This bleeding-edge PPA offers video driver-related components straight from their code (git) repositories. Follow the instructions at: https://launchpad.net/~xorg-edgers/+archive/ppa

= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =
*PLEASE READ FIRST!
'''Which cards are no longer supported by ATI?'''
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid/10.04 (and later). If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION RADEON USERS'''
|-
| NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Precise (or anything later than Lucid/10,04)! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers. 
|}

== Using Ubuntu-supplied fglrx/Catalyst ==

This may not give you the latest drivers, but should be safest. On Ubuntu Precise, this will install Catalyst 8.960, which is roughly equivalent to Catalyst 12-4. NOTE: You must have the restricted repository enabled in Applications -> Ubuntu Software Center -> Edit -> Software Sources... for this to work. After you complete the install, skip to [[Ubuntu_Precise_Installation_Guide#Generate_a_new_.2Fetc.2FX11.2Fxorg.conf_file|Generate a new /etc/X11/xorg.conf file]].

=== Command line ===

sudo apt-get install fglrx fglrx-amdcccle

=== GUI ===

You must have jockey-common and jockey-gtk (or jockey-kde for Kubuntu) packages installed. For the default Ubuntu desktop (Unity), go to the dashboard home and search for "Additional Drivers" in the applications search field (or double-click the "available driver" notification icon) and activate the "ATI/AMD proprietary FGLRX graphics driver".

== Installing Catalyst Manually (from AMD/ATI's site) ==

IMPORTANT NOTE: Installing Catalyst 12-4 on 32-bit Precise currently requires a patch. It is recommended to use the fglrx package from Ubuntu instead, but the patch procedure can be found here: http://ubuntuforums.org/showthread.php?t=1969827

I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).

===''Before you start''===
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).
or Applications->Ubuntu Software Center->Edit->Software sources->Other software: check canonical partners.

Install the prerequisite packages:
sudo apt-get install build-essential cdbs dh-make dkms execstack dh-modaliases fakeroot libqtgui4

''If you are using the x86_64 architecture (64 bit)'':
sudo apt-get install ia32-libs-multiarch:i386 lib32gcc1 libc6-i386
cd /usr ; sudo ln -svT lib /usr/lib64

===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
wget <nowiki>http://www2.ati.com/drivers/linux/amd-driver-installer-</nowiki>{{Catalystdashversion}}-x86.x86_64.run
chmod +x amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run

===''Create and install .deb packages.'' ===
sh ./amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --buildpkg Ubuntu/precise
sudo dpkg -i fglrx*.deb

If building .deb packages fails, there is also an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation]

===''In case of failure:''===

Remember these steps before you reboot your computer.

If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.

sudo startx

If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of "Could not stat /usr/lib64/fglrx/switchlibGL" which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/.

If all else fails, revert your xorg.conf and reboot.

sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf

This should return your original display.

==''Generate a new /etc/X11/xorg.conf file''==

Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.

=== Generic Config ===
This will work for most people:
sudo amdconfig --initial -f

=== Minimal Config ===
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:

Section "Device"
Identifier "ATI radeon 6870"
Driver "fglrx"
EndSection

=== X2/Dual GPU Cards ===
If you have an X2 card (e.g. 4870X2 or 5970), use... '''!!Do not use for two separate cards in crossfire!!'''
sudo amdconfig --initial -f --adapter<nowiki>=</nowiki>all

=== Dual/Multi Monitors ===
If you have a dual monitor display (also known as "Big Desktop"), use:
sudo amdconfig --initial -f
sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553. Be advised that you may need to manually set the correct refresh rate for your second monitor through catalyst.

==''Force use of the new xorg.conf (if necessary)''==
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, use the following command:

sudo amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

==''Test your installation''==
NOTE: if you don't reboot first, fglrxinfo gives an error message.
Reboot the computer and type
fglrxinfo
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and
Catalyst version you are using.)
</pre>
Now, try:
fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
sudo amdconfig --tls=0

This is a raelly intelligent way to answer the question.

= Alternative Manual Installation =
WARNING: This method is incompatible with Debian/Ubuntu Filesystem Hierarchy and may cause issues, especially when trying to remove or upgrade Catalyst. It is highly recommended to build .deb pakages. USE AT OWN RISK.

This is another method of manual installation that may work best for laptop users who have a hybrid setup (i.e. Intel HD onboard graphics with an AMD discrete GPU).

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.orig
./amd-driver-installer-{{Catalystdashversion}}-x86/x86_64.run

Click "Install Driver on X.Org" rather than "Generate distribution specific driver package". Select the "Automatic" install option.

= Hardware Video Decode Acceleration (EXPERIMENTAL) =

== Using XBMC player (XvBA) ==

XBMC has added support for accelerating video using XvBA/libxvba directly, but the support is currently not in the xbmc package in Ubuntu's repositories. To install the XvBA-enabled version of xbmc:

sudo apt-add-repository ppa:wsnipex/xbmc-xvba-eden
sudo apt-get update
sudo apt-get install xbmc

== Using the xvba-va Driver (VA-API) ==
This is confirmed to work for newer RadeonHD GPU's (those with UVD2). If you have a RadeonHD 4000-series or newer, you have UVD2. To see the complete list: http://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_enabled_GPUs

sudo apt-get install xvba-va-driver libva-glx1 libva-x11-1 vainfo
vainfo

vainfo should return something like the following (and no errors):
libva: libva version 0.32.0
Xlib: extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/fglrx_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA API version: 0.32
vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8
vainfo: Supported profile and entrypoints
VAProfileH264High : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD

If vainfo returns an error, you may need to create a symlink:

sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so #for 64-bit
sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so #for 32-bit

Once you've confirmed that vainfo is correct, you can test video playback. A good test player for xvba is VLC. You can enable xvba in Tools -> Preferences -> Input and Codecs. Check the box named "Use GPU acceleration (experimental)" and then restart VLC.

=Updating Catalyst/fglrx=

DO NOT try to install a new version over an old one. Follow the 'Removing Catalyst/fglrx' 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 them 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*

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
sudo rm -rf /etc/ati

If you receive

$ E: Internal Error, No file name for libgl1-mesa-dri

Change the third command above to:

sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core

= Issues =

== Video Tearing ==

AMD/ATI claims that the "Tear Free Video" option is enabled by default, but that wasn't the case with Catalyst 12-3 installed on Kubuntu 12.04.
If you're having issues with tearing, make sure that "Tear Free Video" is on. You can find this option in the Catalyst Control Center under 'Display Options' or you can use the following command:
sudo amdconfig --sync-video=on
The option will not take effect until you restart X (i.e. log out).

If you're using compositing, you should also make sure that vsync is enabled in the compositor's settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.

=== kwin ===
You can enable vsync for kwin in System Settings -> Desktop Effects -> Advanced tab

=== Compiz (Unity/GNOME-Shell) ===
TODO: See if there's a friendlier way to make sure vsync is enabled without installing ccsm.

Install the compiz settings manager:
sudo apt-get install compizconfig-settings-manager
ccsm

The 'Sync to Vblank' is found in the 'OpenGL' subsection of the 'General' group

== Hybrid Graphics and Catalyst==

There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU's. Newer systems (those with PowerXpress >= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU's, and systems with older ATI GPU's have a mux, but don't quote that.

=== ATI/ATI Hybrids ===
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though I don't know if that applies to all ATI/ATI hybrids or only the muxless ones. One would use amdconfig's PowerXpress options to switch back and forth between the integrated and discrete cards, like so:

amdconfig --pxl # List current activated GPU
sudo amdconfig --px-dgpu # Activate discrete GPU (High-Performance mode), must re-start X to take effect
sudo amdconfig --px-igpu # Activate integrated GPU (Power-Saving mode), must re-start X to take effect

After switching, one would log out and back in to restart X.

=== Intel/ATI Hybrids ===

TODO: Status unknown at this time

== 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/<version_number>/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.6 in Ubuntu Precise). This should allow you to install fglrx:
sudo ln -sf /usr/bin/gcc-4.6 /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

How could any of this be better satetd? It couldn't.

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

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.

== 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 <nowiki>http://www2.ati.com/drivers/linux/amd-driver-installer-</nowiki>{{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

== 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 authorization 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.

== 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 ==
This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous fglrx installs, including those through 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.

== "update-alternatives: error" during install ==
During installation you may receive the following message:
<pre>update-alternatives: error: unable to make /usr/lib/xorg/modules/drivers/fglrx_drv.so.dpkg-tmp a symlink to /etc/alternatives/fglrx_drv: No such file or directory</pre>
This can be easily solved by creating directory "drivers" under /usr/lib/xorg/modules/
sudo mkdir /usr/lib/xorg/modules/drivers

== 'Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.' during deb generation ==
During installation you may receive the following message:
<pre>Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.</pre>
This can happen when your /tmp folder is mounted with the option "noexec". The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]

== Black screen after uninstalling old amd drivers ==
Start you computer in recovery mode and exit to root shell.
Remount your partitions in rw mode:
mount -rw -o remount /
...
Go to your download directory and proceed with building and installing the drivers in recovery mode.
All should be fine after a reboot.

== References ==

<references/>

Ubuntu Dapper Installation Guide

2006-07-26T16:05:53Z

202.156.2.43: /* Installing the driver */

== Method 1: Installing Dapper's Included Driver (8.25.18) ==

The included fglrx driver supports Radeon 8500+ and the X-series cards up to X1900.

Unfortunately OpenGL seems to be broken for R200 cards (everything below Radeon 9500) in this driver version. This may be fixed by replacing ''/usr/lib/libGL.so.1.2'' with a''libGL.so.1.2'' from the previous driver version (8.24.8). To do this download this file: [http://files.covertprestige.info/important/libGL.so.1.2] and then copy it to the /usr/lib/ directory.

=== Installing the driver ===

Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

Use this guide to enable them: https://help.ubuntu.com/community/Repositories/Ubuntu#what

<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

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.

=== Confirm that it works ===
<pre>
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)
</pre>

=== Troubleshooting for Method 1 ===

*The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors. You should really include this when you are asking for help somewhere.

*It might be necessary to create a symlink to get accelerated OpenGL:
:<pre>sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri</pre>

*AMD64 users: It may also be necessary to update /etc/profile if using GDM. Update the $LIBGL_DRIVERS_PATH variable to point to the dri path above.

*To ensure you automatically get the current ''linux-restricted-modules'' package with kernel updates, you should install the linux-restricted-modules-??? package matching your kernel-type (without version numer), e.g. ''linux-restricted-modules-386'', ''linux-restricted-modules-686'' or ''linux-restricted-modules-k7''.

*If you used Method 2 before, you have to unblacklist fglrx again by editing ''/etc/default/linux-restricted-modules-common''

*See [[#Troubleshooting for both Methods|Troubleshooting for both Methods]]

 

== Method 2: Generating/Installing Ubuntu packages for the 8.26.18 drivers in Ubuntu Dapper Manually ==

'''Important Change:''' Installation of this driver '''no longer requires''' removing the linux-restricted-modules package in order to work. There is a new blacklist feature in Ubuntu Dapper that you can use to go around this.

=== blacklist old fglrx module from linux-restricted-modules ===

<pre>sudo gedit /etc/default/linux-restricted-modules-common</pre>
Edit ''DISABLED_MODULES'' to include fglrx
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

=== Installing the new driver ===

Download the ATI driver installer: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.26.18-x86.run 32bit Installer]

This guide refers to the 32bit version of the driver. If you are using a x86_64 System you need the [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/64bit/ati-driver-installer-8.26.18-x86_64.run 64bit Installer]. The installation procedure should be the same as for 32bit, except some filenames will differ slightly.

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.

''Install necessary tools:''

<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential
sudo apt-get install fakeroot dh-make debconf libstdc++5 gcc-3.4-base
</pre>

''Create .deb packages:''

<pre>
chmod +x ati-driver-installer-8.26.18-x86.run
./ati-driver-installer-8.26.18-x86.run --buildpkg Ubuntu/dapper
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.26.18-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.26.18-1_i386.deb
sudo dpkg -i fglrx-control_8.26.18-1_i386.deb
</pre>

''Remove any old fglrx deb's from /usr/src/:''

<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Compile the kernel module:''

<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a
</pre>

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

''Update the xorg.conf file:''

<pre>
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

=== Confirm that it worked ===

<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.5879 (8.26.18)
</pre>

=== Troubleshooting for Method 2===

==== Upgrade from Breezy ====
If method 2 doesn't work first time round, and you have upgraded from a Breezy installation, try this:

Remove previous versions of the fglrx driver:
<pre>
sudo dpkg -r fglrx-control
sudo dpkg -r fglrx-kernel-source
sudo dpkg -r xorg-driver-fglrx
</pre>

dpkg will list dependencies for xorg-driver-fglrx which will need up be removed, for example:

<pre>
sudo dpkg -r fglrx-kernel
sudo dpkg -r fglrx-kernel-2.6.12-10-686-smp
sudo dpkg -r xorg-driver-fglrx
</pre>

Proceed with method 2

 
== Troubleshooting for both Methods ==

=== General ===

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

=== 2D speed ===

If you suffer from slow 2D speed it might help to set
Option "XaaNoOffscreenPixmaps"
in the fglrx section of ''/etc/X11/xorg.conf''

=== HP Notebook dv5029us / dv5040us / zv6000 ===

If you have an HP Notebook Computer (or Compaq) such as the HP dv5029us, dv5040us or zv6000 series, it is needed to modify the BIOS configuration. It seems for some reason using sideport memory (the card's onboard memory only) leads to an apparent system crash although the logs show successful initialization of DRI. It is needed to run the BIOS setup screen, go to memory options, and select UMA+Sideport memory and assign a value to it (I assigned an extra 128M from the system RAM). Boot the computer and the fglrx driver will work. FGLRX version is 8.24.8 on an i386 Ubuntu Dapper install.

* Ubuntu FGLRX drivers 8.25.18, do not work properly on the dv5029us (Radeon Xpress 200M) as of this writing (5/30/2006). It is needed to revert to 8.24.8 for this specific computer in order to get proper 3D acceleration, and 2D with no tearing off.

** ATI Driver 8.26.18, does not work with the Radeon Express 200M. Some HP/Compaq laptops only have working 3D support with ONLY UMA video memory( Sideport+UMA won't work ). This is due to a 1 year old flaw in the ATI driver. If you want to use your onboard/Sideport memory, you can only get 2D support by adding [ Option "no_dri" "yes"] to the fglrx driver section of /etc/X11/xorg.conf

* jul-22-2006, marciowb wrote: I have a HP Pavilion zv6000 - a notebook computer with AMD64 - and it have a ATI Radeon Xpress 200M with 128MB of dedicated memory (Sideport) and it accepts to use shared memory (UMA), also. But if I try to use Sideport or Sideport+UMA the 3D acceleration fails and/or my computer hangs. It works fine if I configure its BIOS to use only UMA, including with a good 3D acceleration performance. Configured to use only UMA it works with the ATI Driver 8.26.18 and 8.25.18, but I was unable to do it works the ATI Driver 8.24.8. I tried several times to use 8.24.8 but it doesn't seem to work with 3D acceleration, only 2D. I see the Xorg.log file the fglrx driver fails to load the DRI driver. I used the Kubuntu with the Linux kernel 2.6.15-26-amd64-generic.

=== HP zt3000 / Compaq nx7000 ===
Beginning with ATI driver version 8.19, the drivers fail to properly detect modelines that are compatible with the LCD screen of the HP zt3000 (and equivalent Compaq nx7000 model), and they must be inserted into xorg.conf manually. For the 1680x1050 LCD screen, inserting the following modelines into the "Monitor" section works:
Modeline "640x350" 119.12 640 1728 1760 1840 350 1052 1058 1080
Modeline "640x400" 119.12 640 1728 1760 1840 400 1052 1058 1080
Modeline "720x400" 119.12 720 1728 1760 1840 400 1052 1058 1080
Modeline "640x480" 119.12 640 1728 1760 1840 480 1052 1058 1080
Modeline "800x600" 119.12 800 1728 1760 1840 600 1052 1058 1080
Modeline "1024x768" 119.12 1024 1728 1760 1840 768 1052 1058 1080
Modeline "1152x864" 119.12 1152 1728 1760 1840 864 1052 1058 1080
Modeline "1280x960" 119.12 1280 1728 1760 1840 960 1052 1058 1080
Modeline "1280x1024" 119.12 1280 1728 1760 1840 1024 1052 1058 1080
Modeline "832x624" 119.12 832 1728 1760 1840 624 1052 1058 1080
Modeline "1280x768" 119.12 1280 1728 1760 1840 768 1052 1058 1080
Modeline "1280x800" 119.12 1280 1728 1760 1840 800 1052 1058 1080
Modeline "1152x768" 119.12 1152 1728 1760 1840 768 1052 1058 1080
Modeline "1400x1050" 119.12 1400 1728 1760 1840 1050 1052 1058 1080
Modeline "1440x900" 119.12 1440 1728 1760 1840 900 1052 1058 1080
Modeline "1600x1024" 119.12 1600 1728 1760 1840 1024 1052 1058 1080
Modeline "1680x1050" 119.12 1680 1728 1760 1840 1050 1052 1058 1080

If you have the "1920x1200" version of the HP zt3000 the Modeline is:
Modeline "1920x1200" 150.75 1920 2016 2048 2185 1200 1202 1208 1235

=== 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</pre>

[[Category:Installation Documentation]]

Ubuntu Dapper Installation Guide

2006-07-26T16:05:30Z

202.156.2.43: /* Installing the driver */

== Method 1: Installing Dapper's Included Driver (8.25.18) ==

The included fglrx driver supports Radeon 8500+ and the X-series cards up to X1900.

Unfortunately OpenGL seems to be broken for R200 cards (everything below Radeon 9500) in this driver version. This may be fixed by replacing ''/usr/lib/libGL.so.1.2'' with a''libGL.so.1.2'' from the previous driver version (8.24.8). To do this download this file: [http://files.covertprestige.info/important/libGL.so.1.2] and then copy it to the /usr/lib/ directory.

=== Installing the driver ===

Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

Use this guide to enable them: https://help.ubuntu.com/community/Repositories/Ubuntu#what [https://help.ubuntu.com/community/Repositories/Ubuntu#what]

<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

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.

=== Confirm that it works ===
<pre>
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)
</pre>

=== Troubleshooting for Method 1 ===

*The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors. You should really include this when you are asking for help somewhere.

*It might be necessary to create a symlink to get accelerated OpenGL:
:<pre>sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri</pre>

*AMD64 users: It may also be necessary to update /etc/profile if using GDM. Update the $LIBGL_DRIVERS_PATH variable to point to the dri path above.

*To ensure you automatically get the current ''linux-restricted-modules'' package with kernel updates, you should install the linux-restricted-modules-??? package matching your kernel-type (without version numer), e.g. ''linux-restricted-modules-386'', ''linux-restricted-modules-686'' or ''linux-restricted-modules-k7''.

*If you used Method 2 before, you have to unblacklist fglrx again by editing ''/etc/default/linux-restricted-modules-common''

*See [[#Troubleshooting for both Methods|Troubleshooting for both Methods]]

 

== Method 2: Generating/Installing Ubuntu packages for the 8.26.18 drivers in Ubuntu Dapper Manually ==

'''Important Change:''' Installation of this driver '''no longer requires''' removing the linux-restricted-modules package in order to work. There is a new blacklist feature in Ubuntu Dapper that you can use to go around this.

=== blacklist old fglrx module from linux-restricted-modules ===

<pre>sudo gedit /etc/default/linux-restricted-modules-common</pre>
Edit ''DISABLED_MODULES'' to include fglrx
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

=== Installing the new driver ===

Download the ATI driver installer: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.26.18-x86.run 32bit Installer]

This guide refers to the 32bit version of the driver. If you are using a x86_64 System you need the [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/64bit/ati-driver-installer-8.26.18-x86_64.run 64bit Installer]. The installation procedure should be the same as for 32bit, except some filenames will differ slightly.

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.

''Install necessary tools:''

<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential
sudo apt-get install fakeroot dh-make debconf libstdc++5 gcc-3.4-base
</pre>

''Create .deb packages:''

<pre>
chmod +x ati-driver-installer-8.26.18-x86.run
./ati-driver-installer-8.26.18-x86.run --buildpkg Ubuntu/dapper
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.26.18-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.26.18-1_i386.deb
sudo dpkg -i fglrx-control_8.26.18-1_i386.deb
</pre>

''Remove any old fglrx deb's from /usr/src/:''

<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Compile the kernel module:''

<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a
</pre>

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

''Update the xorg.conf file:''

<pre>
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

=== Confirm that it worked ===

<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.5879 (8.26.18)
</pre>

=== Troubleshooting for Method 2===

==== Upgrade from Breezy ====
If method 2 doesn't work first time round, and you have upgraded from a Breezy installation, try this:

Remove previous versions of the fglrx driver:
<pre>
sudo dpkg -r fglrx-control
sudo dpkg -r fglrx-kernel-source
sudo dpkg -r xorg-driver-fglrx
</pre>

dpkg will list dependencies for xorg-driver-fglrx which will need up be removed, for example:

<pre>
sudo dpkg -r fglrx-kernel
sudo dpkg -r fglrx-kernel-2.6.12-10-686-smp
sudo dpkg -r xorg-driver-fglrx
</pre>

Proceed with method 2

 
== Troubleshooting for both Methods ==

=== General ===

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

=== 2D speed ===

If you suffer from slow 2D speed it might help to set
Option "XaaNoOffscreenPixmaps"
in the fglrx section of ''/etc/X11/xorg.conf''

=== HP Notebook dv5029us / dv5040us / zv6000 ===

If you have an HP Notebook Computer (or Compaq) such as the HP dv5029us, dv5040us or zv6000 series, it is needed to modify the BIOS configuration. It seems for some reason using sideport memory (the card's onboard memory only) leads to an apparent system crash although the logs show successful initialization of DRI. It is needed to run the BIOS setup screen, go to memory options, and select UMA+Sideport memory and assign a value to it (I assigned an extra 128M from the system RAM). Boot the computer and the fglrx driver will work. FGLRX version is 8.24.8 on an i386 Ubuntu Dapper install.

* Ubuntu FGLRX drivers 8.25.18, do not work properly on the dv5029us (Radeon Xpress 200M) as of this writing (5/30/2006). It is needed to revert to 8.24.8 for this specific computer in order to get proper 3D acceleration, and 2D with no tearing off.

** ATI Driver 8.26.18, does not work with the Radeon Express 200M. Some HP/Compaq laptops only have working 3D support with ONLY UMA video memory( Sideport+UMA won't work ). This is due to a 1 year old flaw in the ATI driver. If you want to use your onboard/Sideport memory, you can only get 2D support by adding [ Option "no_dri" "yes"] to the fglrx driver section of /etc/X11/xorg.conf

* jul-22-2006, marciowb wrote: I have a HP Pavilion zv6000 - a notebook computer with AMD64 - and it have a ATI Radeon Xpress 200M with 128MB of dedicated memory (Sideport) and it accepts to use shared memory (UMA), also. But if I try to use Sideport or Sideport+UMA the 3D acceleration fails and/or my computer hangs. It works fine if I configure its BIOS to use only UMA, including with a good 3D acceleration performance. Configured to use only UMA it works with the ATI Driver 8.26.18 and 8.25.18, but I was unable to do it works the ATI Driver 8.24.8. I tried several times to use 8.24.8 but it doesn't seem to work with 3D acceleration, only 2D. I see the Xorg.log file the fglrx driver fails to load the DRI driver. I used the Kubuntu with the Linux kernel 2.6.15-26-amd64-generic.

=== HP zt3000 / Compaq nx7000 ===
Beginning with ATI driver version 8.19, the drivers fail to properly detect modelines that are compatible with the LCD screen of the HP zt3000 (and equivalent Compaq nx7000 model), and they must be inserted into xorg.conf manually. For the 1680x1050 LCD screen, inserting the following modelines into the "Monitor" section works:
Modeline "640x350" 119.12 640 1728 1760 1840 350 1052 1058 1080
Modeline "640x400" 119.12 640 1728 1760 1840 400 1052 1058 1080
Modeline "720x400" 119.12 720 1728 1760 1840 400 1052 1058 1080
Modeline "640x480" 119.12 640 1728 1760 1840 480 1052 1058 1080
Modeline "800x600" 119.12 800 1728 1760 1840 600 1052 1058 1080
Modeline "1024x768" 119.12 1024 1728 1760 1840 768 1052 1058 1080
Modeline "1152x864" 119.12 1152 1728 1760 1840 864 1052 1058 1080
Modeline "1280x960" 119.12 1280 1728 1760 1840 960 1052 1058 1080
Modeline "1280x1024" 119.12 1280 1728 1760 1840 1024 1052 1058 1080
Modeline "832x624" 119.12 832 1728 1760 1840 624 1052 1058 1080
Modeline "1280x768" 119.12 1280 1728 1760 1840 768 1052 1058 1080
Modeline "1280x800" 119.12 1280 1728 1760 1840 800 1052 1058 1080
Modeline "1152x768" 119.12 1152 1728 1760 1840 768 1052 1058 1080
Modeline "1400x1050" 119.12 1400 1728 1760 1840 1050 1052 1058 1080
Modeline "1440x900" 119.12 1440 1728 1760 1840 900 1052 1058 1080
Modeline "1600x1024" 119.12 1600 1728 1760 1840 1024 1052 1058 1080
Modeline "1680x1050" 119.12 1680 1728 1760 1840 1050 1052 1058 1080

If you have the "1920x1200" version of the HP zt3000 the Modeline is:
Modeline "1920x1200" 150.75 1920 2016 2048 2185 1200 1202 1208 1235

=== 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</pre>

[[Category:Installation Documentation]]

Ubuntu Dapper Installation Guide

2006-07-26T16:03:47Z

202.156.2.43: /* Installing the driver */

== Method 1: Installing Dapper's Included Driver (8.25.18) ==

The included fglrx driver supports Radeon 8500+ and the X-series cards up to X1900.

Unfortunately OpenGL seems to be broken for R200 cards (everything below Radeon 9500) in this driver version. This may be fixed by replacing ''/usr/lib/libGL.so.1.2'' with a''libGL.so.1.2'' from the previous driver version (8.24.8). To do this download this file: [http://files.covertprestige.info/important/libGL.so.1.2] and then copy it to the /usr/lib/ directory.

=== Installing the driver ===

Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!
Use this guide to enable them: [https://help.ubuntu.com/community/Repositories/Ubuntu#what]

<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

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.

=== Confirm that it works ===
<pre>
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)
</pre>

=== Troubleshooting for Method 1 ===

*The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors. You should really include this when you are asking for help somewhere.

*It might be necessary to create a symlink to get accelerated OpenGL:
:<pre>sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri</pre>

*AMD64 users: It may also be necessary to update /etc/profile if using GDM. Update the $LIBGL_DRIVERS_PATH variable to point to the dri path above.

*To ensure you automatically get the current ''linux-restricted-modules'' package with kernel updates, you should install the linux-restricted-modules-??? package matching your kernel-type (without version numer), e.g. ''linux-restricted-modules-386'', ''linux-restricted-modules-686'' or ''linux-restricted-modules-k7''.

*If you used Method 2 before, you have to unblacklist fglrx again by editing ''/etc/default/linux-restricted-modules-common''

*See [[#Troubleshooting for both Methods|Troubleshooting for both Methods]]

 

== Method 2: Generating/Installing Ubuntu packages for the 8.26.18 drivers in Ubuntu Dapper Manually ==

'''Important Change:''' Installation of this driver '''no longer requires''' removing the linux-restricted-modules package in order to work. There is a new blacklist feature in Ubuntu Dapper that you can use to go around this.

=== blacklist old fglrx module from linux-restricted-modules ===

<pre>sudo gedit /etc/default/linux-restricted-modules-common</pre>
Edit ''DISABLED_MODULES'' to include fglrx
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

=== Installing the new driver ===

Download the ATI driver installer: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.26.18-x86.run 32bit Installer]

This guide refers to the 32bit version of the driver. If you are using a x86_64 System you need the [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/64bit/ati-driver-installer-8.26.18-x86_64.run 64bit Installer]. The installation procedure should be the same as for 32bit, except some filenames will differ slightly.

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.

''Install necessary tools:''

<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential
sudo apt-get install fakeroot dh-make debconf libstdc++5 gcc-3.4-base
</pre>

''Create .deb packages:''

<pre>
chmod +x ati-driver-installer-8.26.18-x86.run
./ati-driver-installer-8.26.18-x86.run --buildpkg Ubuntu/dapper
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.26.18-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.26.18-1_i386.deb
sudo dpkg -i fglrx-control_8.26.18-1_i386.deb
</pre>

''Remove any old fglrx deb's from /usr/src/:''

<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Compile the kernel module:''

<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a
</pre>

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

''Update the xorg.conf file:''

<pre>
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

=== Confirm that it worked ===

<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.5879 (8.26.18)
</pre>

=== Troubleshooting for Method 2===

==== Upgrade from Breezy ====
If method 2 doesn't work first time round, and you have upgraded from a Breezy installation, try this:

Remove previous versions of the fglrx driver:
<pre>
sudo dpkg -r fglrx-control
sudo dpkg -r fglrx-kernel-source
sudo dpkg -r xorg-driver-fglrx
</pre>

dpkg will list dependencies for xorg-driver-fglrx which will need up be removed, for example:

<pre>
sudo dpkg -r fglrx-kernel
sudo dpkg -r fglrx-kernel-2.6.12-10-686-smp
sudo dpkg -r xorg-driver-fglrx
</pre>

Proceed with method 2

 
== Troubleshooting for both Methods ==

=== General ===

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

=== 2D speed ===

If you suffer from slow 2D speed it might help to set
Option "XaaNoOffscreenPixmaps"
in the fglrx section of ''/etc/X11/xorg.conf''

=== HP Notebook dv5029us / dv5040us / zv6000 ===

If you have an HP Notebook Computer (or Compaq) such as the HP dv5029us, dv5040us or zv6000 series, it is needed to modify the BIOS configuration. It seems for some reason using sideport memory (the card's onboard memory only) leads to an apparent system crash although the logs show successful initialization of DRI. It is needed to run the BIOS setup screen, go to memory options, and select UMA+Sideport memory and assign a value to it (I assigned an extra 128M from the system RAM). Boot the computer and the fglrx driver will work. FGLRX version is 8.24.8 on an i386 Ubuntu Dapper install.

* Ubuntu FGLRX drivers 8.25.18, do not work properly on the dv5029us (Radeon Xpress 200M) as of this writing (5/30/2006). It is needed to revert to 8.24.8 for this specific computer in order to get proper 3D acceleration, and 2D with no tearing off.

** ATI Driver 8.26.18, does not work with the Radeon Express 200M. Some HP/Compaq laptops only have working 3D support with ONLY UMA video memory( Sideport+UMA won't work ). This is due to a 1 year old flaw in the ATI driver. If you want to use your onboard/Sideport memory, you can only get 2D support by adding [ Option "no_dri" "yes"] to the fglrx driver section of /etc/X11/xorg.conf

* jul-22-2006, marciowb wrote: I have a HP Pavilion zv6000 - a notebook computer with AMD64 - and it have a ATI Radeon Xpress 200M with 128MB of dedicated memory (Sideport) and it accepts to use shared memory (UMA), also. But if I try to use Sideport or Sideport+UMA the 3D acceleration fails and/or my computer hangs. It works fine if I configure its BIOS to use only UMA, including with a good 3D acceleration performance. Configured to use only UMA it works with the ATI Driver 8.26.18 and 8.25.18, but I was unable to do it works the ATI Driver 8.24.8. I tried several times to use 8.24.8 but it doesn't seem to work with 3D acceleration, only 2D. I see the Xorg.log file the fglrx driver fails to load the DRI driver. I used the Kubuntu with the Linux kernel 2.6.15-26-amd64-generic.

=== HP zt3000 / Compaq nx7000 ===
Beginning with ATI driver version 8.19, the drivers fail to properly detect modelines that are compatible with the LCD screen of the HP zt3000 (and equivalent Compaq nx7000 model), and they must be inserted into xorg.conf manually. For the 1680x1050 LCD screen, inserting the following modelines into the "Monitor" section works:
Modeline "640x350" 119.12 640 1728 1760 1840 350 1052 1058 1080
Modeline "640x400" 119.12 640 1728 1760 1840 400 1052 1058 1080
Modeline "720x400" 119.12 720 1728 1760 1840 400 1052 1058 1080
Modeline "640x480" 119.12 640 1728 1760 1840 480 1052 1058 1080
Modeline "800x600" 119.12 800 1728 1760 1840 600 1052 1058 1080
Modeline "1024x768" 119.12 1024 1728 1760 1840 768 1052 1058 1080
Modeline "1152x864" 119.12 1152 1728 1760 1840 864 1052 1058 1080
Modeline "1280x960" 119.12 1280 1728 1760 1840 960 1052 1058 1080
Modeline "1280x1024" 119.12 1280 1728 1760 1840 1024 1052 1058 1080
Modeline "832x624" 119.12 832 1728 1760 1840 624 1052 1058 1080
Modeline "1280x768" 119.12 1280 1728 1760 1840 768 1052 1058 1080
Modeline "1280x800" 119.12 1280 1728 1760 1840 800 1052 1058 1080
Modeline "1152x768" 119.12 1152 1728 1760 1840 768 1052 1058 1080
Modeline "1400x1050" 119.12 1400 1728 1760 1840 1050 1052 1058 1080
Modeline "1440x900" 119.12 1440 1728 1760 1840 900 1052 1058 1080
Modeline "1600x1024" 119.12 1600 1728 1760 1840 1024 1052 1058 1080
Modeline "1680x1050" 119.12 1680 1728 1760 1840 1050 1052 1058 1080

If you have the "1920x1200" version of the HP zt3000 the Modeline is:
Modeline "1920x1200" 150.75 1920 2016 2048 2185 1200 1202 1208 1235

=== 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</pre>

[[Category:Installation Documentation]]

Ubuntu Dapper Installation Guide

2006-04-18T13:33:07Z

202.156.2.43: /* Installing the driver */

== Method 1: Installing Dapper's Included Driver (8.23.7) ==

The included fglrx driver supports Radeon 8500+ and the X-series cards up to X850.

=== Installing the driver ===

Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo apt-get install xorg-driver-fglrx
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

Note: In Dapper the last 2 steps is not necessary and if applied will duplicate in the Xorg.conf file the entry for "screen" and "device". Maybe is not a problem because it works.
Anyway an alternative to the "aticonfig" command is to edit the Xorg.conf and change the string "ati" with "fglrx" in the "device" section. You have also to add in the same section:

Option "VideoOverlay" "on"

Option "OpenGLOverlay" "off"

Option "UseInternalAGPGART" "off"

=== Confirm that it works ===
<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.5695 (8.23.7)
</pre>

=== Troubleshooting ===

*The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

*It might be necessary to create a symlink to get accelerated OpenGL:
:<pre>sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri</pre>

*You can force early loading of the fglrx module by adding it to /etc/modules

*To ensure you automatically get the current ''linux-restricted-modules'' package with kernel updates, you should install the linux-restricted-modules-??? package matching your kernel-type (without version numer), e.g. ''linux-restricted-modules-386'', ''linux-restricted-modules-686'' or ''linux-restricted-modules-k7''.

*If you used Method 2 before, you have to unblacklist fglrx again by editing ''/etc/default/linux-restricted-modules-common''

== Method 2: Generating/Installing Ubuntu packages for the newer 8.24.8 drivers in Ubuntu Dapper ==

'''Important Change:''' Installation of this driver '''no longer requires''' removing the linux-restricted-modules package in order to work. There is a new blacklist feature in Ubuntu Dapper that you can use to go around this.

=== Blacklist old fglrx module from linux-restricted-modules ===

<pre>sudo gedit /etc/default/linux-restricted-modules-common</pre>
Edit ''DISABLED_MODULES'' to include fglrx
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

=== Installing the new driver ===

Download the ATI driver installer: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.24.8-x86.run 32bit Installer]

This guide refers to the 32bit version of the driver. If you are using a x86_64 System you need the [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/64bit/ati-driver-installer-8.24.8-x86_64.run 64bit Installer]. The installation procedure should be the same as for 32bit, except some filenames will differ slightly.

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.

''Install necessary tools:''

<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential
sudo apt-get install fakeroot dh-make debconf libstdc++5 gcc-3.3-base
</pre>

''Create .deb packages:''

<pre>
chmod +x ati-driver-installer-8.24.8-x86.run
./ati-driver-installer-8.24.8-x86.run --buildpkg Ubuntu/dapper
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.24.8-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.24.8-1_i386.deb
sudo dpkg -i fglrx-control_8.24.8-1_i386.deb
</pre>

''Remove any old fglrx deb's from /usr/src/:''

<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Compile the kernel module:''

<pre>
sudo module-assistant prepare,update
sudo module-assistant build,install fglrx
</pre>

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

''Update the xorg.conf file:''

<pre>
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

=== Confirm that it worked ===

<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.5755 (8.24.8)
</pre>

=== Troubleshooting ===

==== General ====

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

==== HP dv5029us Notebook PC ====

If you have an HP Notebook Computer such as the HP dv5029dvus it is needed to modify the BIOS configuration. It seems for some reason using sideport memory (the card's onboard memory only) leads to an apparent system crash although the logs show successful initialization of DRI. It is needed to run the BIOS setup screen, go to memory options, and select UMA+Sideport memory and assign a value to it (I assigned an extra 128M from the system RAM). Boot the computer and the fglrx driver will work. FGLRX version is 8.23.7 on an i386 Ubuntu Dapper install.

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

[[Category:Installation Documentation]]