cchtml.com - User contributions [en]

Ubuntu Jaunty Installation Guide

2009-05-03T14:58:03Z

196.217.219.118: /* Installation Guide for Ubuntu Jaunty (v 9.04) Currently Doesnt WORK!! Be Forewarned... */

= Installation Guide for Ubuntu Jaunty (v 9.04) Currently Doesn't WORK!! Be Forewarned... =
__TOC__

= The Alternatives =
Users with ATI cards basically have these options:
# '''Open Source Drivers''' These are stable and nice, but currently have poor 3D performance, if any. If you have a Radeon X1k product or earlier, this is your only option.
# '''The Ubuntu Way''' Use the restricted-driver management system that comes with Ubuntu to install the drivers.
# '''Third (Fourth?) Party Installer''' Use envy/jockey or other installer helper.
# '''Install the drivers manually''' Using the installer downloaded from AMD's site via either package based install or direct install.

= Open Source Drivers =
By default, Ubuntu will already try to use one of the open source drivers for your hardware. If the feature set and stability work for you, then you don't need to change anything.

The drivers that may be used are
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.
* '''ati''' Actually a facade that will invoke the radeon driver.
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.
* '''radeonhd''' An alternate driver support R520 hardware and later.

By default there is no configuration file for X anymore, so X will try to do the right thing.

There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.

= The Ubuntu way =

== Restricted Drivers Manager ==
* Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available
* Go to the Restricted Drivers Manager and enable the "ATI accelerated graphics driver"
* Ubuntu will then install and configure the driver for you

Note that you will be restricted to the drivers for you version of Ubuntu that Canonical deem as stable. This may not give you the latest drivers, but should be safest.

= Installing the drivers manually =
*PLEASE READ FIRST!
This portion of the guide works, since I have used it myself. I guess the rest of the guide is broken or something or it may be because the new driver doesn't support any of the older ATI cards anymore. Which cards does ATI no longer support? Well I don't know. But if you use anything older then the Radeon HD 3000 series then I recommend you use the 9.3 driver. This guide currently is for installing 9.4. !!!SO BE CAREFUL!!!

_______________________________________________

I recommend using copy and paste. However, you can Ctrl + C in your browser but you cannot Ctrl + V in the terminal. When you have copied something simply use Shift + Insert to paste into the terminal or go to the terminals menu, select edit and click paste. This method will ensure there are no typing mistakes and will greatly speed up the install process.

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

Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.

===''Before you start''===
Install the necessary programs
{{Box Terminal|
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms
}}

===''1. Download the latest Catalyst package.''===

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

Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)

Make sure your directory path does not contain spaces

===''2. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/jaunty
}}

===''3. Just in case''===
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.

Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b

These keypresses will reboot the system safely. To remember the keypresses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring"

===''4. Install .debs.''===

Install the debs, depending on if you're on a 32-bit or 64-bit system:

* For 32-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
}}

(This may fail due to a missing dpmk. If so install this first. Also check the version numbers (8.561) against the created debs)

* For 64-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

{{Box Terminal|
sudo apt-get install -f
}}

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Finishing the Install: Configuration ==

'' Note: try auto config first (what in the heck is auto config??), and follow the question guide, reboot; if no effect observed, restore ''xorg.conf-bkp'' ''

I personally don't recommend this method but it does work. I find the method starting with "If you've used fglrx previously, you will not need to do this." to be faster and easier.
{{Box Terminal|
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf-bkp 
sudo dpkg-reconfigure xserver-xorg
}}

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

Now you'll have to edit your xorg.conf

For Ubuntu:
{{Box Terminal|
sudo gedit /etc/X11/xorg.conf
}}

For Kubuntu:
{{Box Terminal|
sudo kate /etc/X11/xorg.conf
}}

and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it doesn't give an error you should be good.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

{{Box Terminal|
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>
}}

Finally, reboot the computer and type
{{Box Terminal|
fglrxinfo
}}
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 9.4 looks like:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4800 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 2.1.8591
</pre>

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

'''HOW TO UPDATE DRIVER''': To update your driver to a new version (say 9.3 to 9.4) first disable the current driver through Ubuntu's Hardware Manager or use EnvyNG to remove the driver, then go to synaptic and search for "xorg-driver-fglrx" without the quotes and mark it for "Complete removal" and hit "Apply" then reboot your computer. Now simply repeat steps #1, 2, 4 and finally run these commends in a terminal: {{Box Terminal|sudo aticonfig --initial -f
}}

and

{{Box Terminal|
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>
}}

then reboot.

It is very important that you COMPLETELY remove the old driver which includes the config files because when upgrading without uninstalling the old driver I noticed even though the new driver installed and worked there were some annoying problems that I experienced but after I completely uninstalled the driver then reinstalled it, it worked perfectly.

== Finally ==
# Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422
# Restart X, if it doesn't work, you can use the "vesa", "ati", "radeon" or "radeonhd" driver in the mean time, until you make it work.
# If you downgraded X to make fglrx work: enter synaptic, make sure all packages with "xorg" and "x11" are locked so that you can update and upgrade without worries.

Done! Now run amdcccle, glxgears, warsow etc :)

= Issues =

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

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

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

----

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

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

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

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

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

----

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

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

== Hang at logout ==

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

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

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

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

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

<pre>sh ati-driver-installer-8-12-x86.x86_64.run --extract driver</pre>

<pre>sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh</pre>

(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)

<pre>sudo chmod +x /etc/ati/authatieventsd.sh</pre>

just reboot login and ctrl+alt+backspace to try

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

<blockquote>
Comment: This is a little surprising, since the comments at the beginning of /etc/default/acpi-support seem to make it quite clear that those settings are ignored unless you add "acpi-support" to SUSPEND_METHODS. --[[User:Bewst|Bewst]] 23:22, 19 December 2008 (UTC)
</blockquote>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This is a hack and should be avoided.

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

If you get this error-message, simply uninstall the previous version before installing the new one with:
{{Box Terminal|
sudo dkms remove -m fglrx -v 8.522 --all
}}

== New kernel installed? ==
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.
You can do that by these simple steps:
{{Box Terminal|
sudo dkms build -m fglrx -v 8.552 -k `uname -r` 
sudo dkms install -m fglrx -v 8.552 -k `uname -r`
}}
[[Category:Installation Documentation]]
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf

Lenovo

2008-02-29T11:05:02Z

196.217.249.190: laladara

montroc
Lenovo purchased the PC business unit of IBM.

===Laptops===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|Thinkpad T43
|Radeon Mobility X300
|Working
|SLED10,SLED10-SP1,openSUSE10.3
|-
|Thinkpad T43p
|MOBILITY FireGL V3200
|Working
|Ubuntu Gutsy
|Suspend/Resume, OpenGL
|-
|Thinkpad T60
|Radeon Mobility X1400
|Working
|SLED10-SP1,openSUSE10.3
|-
|Thinkpad T60p
|FireGL V5200
|Working
|Fedora Core 6, Ubuntu Feisty
|Suspend/Resume, OpenGL
|-
|Thinkpad T60p
|FireGL V5250
|Not Working
|-
|Thinkpad R60
|Radeon Mobility X1400
|Working
|-
|Thinkpad Z60m
|Radeon Mobility X600
|Working
|-
|Thinkpad Z61p
|MOBILITY FireGL V5200
|Working
|}

===Resources===

[http://thinkwiki.org/ ThinkWiki Community Page]

[[Category:OEMs]]

Frequently Asked Questions

2008-02-29T11:01:55Z

196.217.249.190: eldronc

lisitb
==Installation==
===How do I know fglrx is installed correctly?===
There are several ways to check if fglrx is loaded and running.
 1. Check your X.org or XFree86 log. You should see "DRI Initialization Successful."
# less /var/log/Xorg.0.log
or
# less /var/log/XFree86.0.log
2. Check glxinfo. You should see "direct" and not "indirect."
# glxinfo | grep direct
3. Check your kernel log. You should see fglrx messages near the bottom.
# dmesg
4. Check your modules. You should see fglrx loaded.
# lsmod | grep fglrx
*NOTE: [[Glxgears is not a Benchmark|glxgears]] is not a definite way of checking the installation of fglrx.

=== Is the rebooting really necessary? ===

No.

However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.

==Kernel==
===Why does fglrx not work for my bleeding-edge kernel?===
The development process of the fglrx driver and the Linux kernel are not on the same level. The fglrx driver requires some special interactions with the kernel memory API and these tend to change between kernel versions.

There is also an 11-12 week cycle required to develop, validate and test each release of an ATI driver <ref>http://www.phoronix.com/scan.php?page=article&item=735&num=1</ref>. ATI will only look to support the latest kernel that is officially out (no -rc or -git releases are supported) at the time they release a driver. Example: fglrx version A comes out Monday, but kernel version B comes out Tuesday. Kernel version B is not supported by fglrx version A. (but might be able to work anyway by doing a 'modprobe -f fglrx' in a shell)

The binary part of ATI's kernel module has no explicit dependency on the Linux kernel. There are a set of source files that provide the glue to the kernel. This is where the dependency to different kernels exist. As a result, user contributed patches for newer kernels can often be found by searching [http://ati.cchtml.com Bugzilla].

Note: That's why an opensource hardware driver is necessary. Hopefully, AMD will continue releasing more documentation and we will be able to code our own maintainable and free driver, thus freeing ourselves from this dependency on AMD's good will.

==X Configuration==
===How do I configure my system to use the fglrx driver?===
*aticonfig
:Command line program to modify the /etc/X11/xorg.conf file.
*amdcccle
:GUI program that allows detailed configuration over the driver's controls.
*/etc/X11/xorg.conf
:X configuration file. Find the Device section for your ATI card and edit the Driver line to read
Driver "fglrx"
:Note: This is the least-preferred method. Many things can stop working.

==Troubleshooting==
* See [[Troubleshooting]] page.

==See Also==
*[http://ati.amd.com/products/catalyst/linux.html Official ATI Linux Driver FAQ]

==References==
<references/>

IBM

2008-02-29T11:01:29Z

196.217.249.190: trroro

deltaelou
bozeleltc
IBM has sold the PC business unit to [[Lenovo]].

===Workstations===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|Intellistation zPro
|FireGL V3100, FireGL V7100
|Works
|-
|}

===Laptops===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|ThinkPad T42
|Radeon Mobility 9600
|Works
|openSUSE 10.2
|-
|ThinkPad T42
|Radeon Mobility 9600
|Works - No AIGLX Yet
|Ubuntu 7.10
|Good OpenGL, Relatively Stable
|-
|ThinkPad T43p
|MOBILITY FireGL V3200
|Works
|-
|ThinkPad T60
|Radeon Mobility X1300
|Works
|Gentoo 2007.0
|-
|ThinkPad Z61m
|Radeon Mobility X1400
|Works
|openSUSE 10.2
|Some tinkering in xorg.conf is needed
|-}

===Resources===

[http://thinkwiki.org/ ThinkWiki Community Page]

[[Category:OEMs]]

Category:NewsSite

2008-02-29T04:43:51Z

196.217.249.190: roelcoel

vierdronmonr
Any articles scoured from the Internet mentioning the ATI driver should end up here. Some good, some great, some not so great. Sometimes the news agregators (like [http://slashdot.org Slashdot] have lots of useful bits in their comments, include them as well.

You can also see this list [[In the News|organized in reverse chronological order]].

Phoronix

2008-02-29T04:40:42Z

196.217.249.190: cachileto

trmonsitlal
'''2007-01-10''' : [http://www.phoronix.com/vr.php?view=8426 ATI Linux Display Driver v8.33.6] 
'''2006-12-22''' : [http://www.phoronix.com/vr.php?view=8266 ATI Year in Review 2006] 
'''2006-12-13''' : [http://www.phoronix.com/vr.php?view=8168 ATI Linux Display Driver v8.32.5] 
'''2006-11-15''' : [http://www.phoronix.com/vr.php?view=7876 ATI Linux Display Driver v8.31.5] 
'''2006-10-31''' : [http://www.phoronix.com/vr.php?view=7715 ATI Linux Display Driver v8.30.3] 
'''2006-09-20''' : [http://www.phoronix.com/vr.php?view=7375 ATI Linux Display Driver v8.29.6] 
'''2006-08-18''' : [http://www.phoronix.com/vr.php?view=7188 ATI Linux Display Driver v8.28.8] 
'''2006-07-28''' : [http://www.phoronix.com/vr.php?view=7085 ATI Linux Display Driver v8.27.10] 
'''2006-06-26''' : [http://www.phoronix.com/vr.php?view=6879 ATI Linux Display Driver v8.26.18] 
'''2006-05-24''' : [http://www.phoronix.com/vr.php?view=6656 ATI Linux Display Driver v8.25.18] 
'''2006-04-12''' : [http://www.phoronix.com/vr.php?view=6290 ATI Linux Display Driver v8.24.8] 
'''2006-03-09''' : [http://www.phoronix.com/vr.php?view=5974 ATI Linux Display Driver v8.23.7] 
'''2006-02-09''' : [http://www.phoronix.com/vr.php?view=5744 ATI Linux Display Driver v8.22.5] 
'''2006-01-18''' : [http://www.phoronix.com/vr.php?view=5590 ATI Linux Display Driver v8.21.7] 
'''2005-11-12''' : [http://www.phoronix.com/vr.php?view=5056 ATI POWERPlay] 
'''2005-11-11''' : [http://www.phoronix.com/vr.php?view=5055 ATI Linux Display Driver v8.19.10] 
'''2005-10-12''' : [http://www.phoronix.com/vr.php?view=4768 ATI Linux Display Driver v8.18.6] 
'''2005-06-09''' : [http://www.phoronix.com/vr.php?view=3600 ATI Linux Display Driver v8.14.13] 

[[Category:NewsSite]]