Changes

Jump to: navigation, search

Ubuntu Gutsy Installation Guide

7,350 bytes added, 18:44, 5 July 2013
m
Protected "Ubuntu Gutsy Installation Guide": Excessive vandalism (‎[edit=autoconfirmed] (indefinite) ‎[move=autoconfirmed] (indefinite))
dors-andrey-viagra1.txt;3;10== Installation ==
doorsFor most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 7.txt;10;15(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.
==Specific Issues=Method 1: Install the Driver the Ubuntu Way===This will install the driver that is currently in the repositories. It may be older than the current version from AMD.<pre>sudo apt-get update sudo apt-get install linux-restricted-modules-generic restricted-managersudo apt-get install xorg-driver-fglrxsudo depmod -a</pre> The second line of the above may not be necessary. If apt says it cannot find the "linux-restricted-modules" package, try line 3. If that fails, check your sources.list (see top of page) If the system complains about dependencies, use your preferred package manager to download python2.4 and, if necessary, its dependencies. ===Method 2: Install the Catalyst 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 {{catalystversion}} -- File: {{catalystfilename}}. 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 [https://wiki.ubuntu.com/AddingRepositoriesHowto Ubuntu Wiki]. By default, Ubuntu did not enable the Universe and Multiverse repositories, but now in Gutsy, both Universe and Multiverse are activated by default. ''Install necessary tools:''{{Box Terminal|sudo apt-get update sudo apt-get install build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)}} ''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:'' {{Box Terminal|sudo sh {{catalystfilename}} --buildpkg Ubuntu/gutsy}}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{{Box Terminal|sudo sh ./{{catalystfilename}} --buildpkg Ubuntu --autopkg}}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 <tt>No such file or directory</tt> message about missing files in <tt>X11R6/lib</tt>, [http://emmetcaulfield.net/Tech/Ubuntu64+ATI follow these instructions] and come back here. Also check that your 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:<pre>gksu gedit /etc/default/linux-restricted-modules-common</pre> Kubuntu/KDE users type in:<pre>kdesu kate /etc/default/linux-restricted-modules-common</pre> Add "fglrx" to the line "DISABLED_MODULES"{{Box File|/etc/default/linux-restricted-modules-common|<pre>DISABLED_MODULES="fglrx"</pre>}}Please note that after the modification above, the "Restricted Driver Manager" will signal "ATI accelerated 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):<pre>gksu gedit /etc/modprobe.d/blacklist-restricted</pre>Put a # in front of the line "blacklist fglrx", if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration. ''Remove any old fglrx debs from /usr/src/:''<pre>sudo rm /usr/src/fglrx-kernel*.deb</pre> ''Install .deb packages:'' <pre>sudo dpkg -i xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb</pre> ''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:
=== 3D desktop effects ===<pre>The new ATI drivers use AIGLX so there is not need to sudo apt-get install XGL that older drivers (-f< 8.40) required./pre>
Remove this section from to Catalyst 8.3 on 64-bit systems requires the /etc/X11/xorg.conf file.The new xorg server enables "Composite" by default.''--force-overwrite'' command in the above ''dpkg'' command:
<pre>
# Section "Extensions"# Option "Composite" "sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.476-0"# EndSection*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb
</pre>
Compiz does I’m not know about wrhoty to be in the fglrx driversame forum. You can either skip the checksROTFL
===Configure the Driver===*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.<pre>mkdir sudo aticonfig --p ~initial</.config/compiz && echo SKIP_CHECKS=yes pre>Then:<pre> ~/.config/compiz/compizsudo aticonfig --overlay-managertype=Xv</pre>*Note: Alternative in the overlay-type to "Xv" can be "opengl" or "disable" if the TV-out makes problems in videos.
or add it to ====Alternative: Configure the compiz white listDriver, and clear The Manual Way:====An alternative to the blacklist pci Ids variable "''sudo aticonfig''" commands is to edit "''*Recommended*/etc/X11/xorg.conf''" and change the "Device" section for the video card as shown below. This way you won't lose your old settings.<pre>gksu gedit /etc/X11/xorg.conf</pre><pre>Section "Device" [...]# Driver "vesa" Driver "fglrx" Option "VideoOverlay" "on" Option "OpenGLOverlay" "off" [...]EndSection</pre>
<pre>sudo gedit /usr/bin/compiz</pre>
==== TV - Out ====
The composite TV-Out is not working simultaneously with the VGA on my System. To use it I have turned the VGA off and only the TV on. Attention! This command turns off your Monitor!!
<pre>
sudo aticonfig --enable-monitor=tv
</pre>
To change back to VGA:
<pre>
sudo aticonfig --enable-monitor=crt1
</pre>
Some have had luck with both mirrored.
<pre>
# Driver whitelistsudo aticonfig --force-monitor=crt1WHITELISTsudo aticonfig --enable-monitor="fglrx nvidia intel ati radeon i810"crt1,tv
</pre>
reboot after that and it should mirror the CRT1 onto the TV.
===Finish the Installation===
Now save any open document and reboot your system:
<pre>
sudo shutdown -hr now
</pre>
*Note: An '''alternative''' to rebooting is to restart the X Server by pressing your CTRL ALT BACKSPACE keys. You must remove any old kernel modules such as "drm" "radeon" or "fglrx" using the "rmmod" command. Example: <code>sudo rmmod fglrx</code>
*Note: Another way to reboot:
<pre>
# blacklist based on the pci ids # BLACKLIST_PCIIDS="$T"BLACKLIST_PCIIDS=""sudo reboot
</pre>
== Post-Installation Checks and Tweaks ==
===Verifying===
Run the following command to check its output to ensure the fglrx driver is installed properly:
You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz$fglrxinfo PLUGIN_PATH="/usr/lib/compiz/"display: :0.0 screen: 0OpenGL vendor string: ATI Technologies Inc.OpenGL renderer string: ATI MOBILITY RADEON X300OpenGL version string: 2.1.7415 Release
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly64bit Users only ( 32bit users can continue to the fglrxinfo test ), after rebooting you may have noticed that you cant open aticonfig, and the fglrxinfo test below may not show ati in the info from the test, to fix this in terminal do the following command
<pre>
COMPIZ_NAME="compizsudo ln -s /usr/lib/libGL.real" # Final name for compiz (compizso.real) 1.2 /usr/lib/libGL.so.1
</pre>
After the necessary configurations, just restart X and enjoy the cool effects.
The <code>OpenGL vendor string</code> should read '''ATI''' and not '''Mesa'''. '''If it still does says ''Mesa'' and not work''ATI'', locate even after re-enabling the driver from the Restricted-manager:'''You can try the following::*<pre>$ less /var/log/Xorg.0.log |grep EE</etcpre> if this command returns <code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</xdgcode> then remove the kernel module and reinstall it.:: <pre>$ sudo dkms remove -m fglrx -v 8.471 --all</compizpre> :*Remove all the packages provided by the <code>xserver-xorg-video-all</compizcode> meta-managerpackage (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'').ubuntu [::If you can't log in after this line may instead be , you'll have to log in to a terminal in the login screen, and reinstall the <code>xserver-xorg-video-all</etccode> package. Your problem is probably somewhere else. (taken from [http:/xdg/compizubuntuforums.org/showpost.php?p=3655658&postcount=139]). :*Remove the package xserver-xgl. ::'''Explanation:''' If you installed this previously in order to make compiz-manager] and see 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 contains returns an infinite loop in ATI renderer, itmeans that xgl is being displayed indirectly on the display 1. If (Taken from [http://ubuntuforums.org/showthread.php?t=740287])::'''Warning:''' This might make your compiz stop working as it doesis 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, comment out the line however be aware that sometimes it causes the infinite loopodd hangsSwitch ENABLE_LAPTOP_MODE to true {{Box File|/etc/default/acpi-support|
<pre>
# . /etc/xdg/compiz/compizSwitch to laptop-manager.ubuntumode on battery power - off by default as it causes odd# hangs on some machinesENABLE_LAPTOP_MODE=true
</pre>
}}
For Kubuntu you need some extra steps:Switch FGLRX_ACPI_SWITCH_POWERSTATES to true{{Box File|/etc/default/fglrx|
<pre>
sudo apt-get install compiz compiz-kde compizconfig-settings-manager compiz-core compiz-fusion-plugins-main compiz-plugins# Uncomment the next line to enable powerstate switching on ACPI# events for lid open/close and AC adapter on/offFGLRX_ACPI_SWITCH_POWERSTATES=true
</pre>
}}
 
=== Additional configure with aticonfig tool ===
You can configure the driver even further with the '''aticonfig''' tool, more information can be found at [[Configuring]].
 
For example: <br>
* use powerplay option to switch power state for battery friendly or performance mode
* use dual head or one big desktop mode
* turn second monitor on/off on the fly
To test 3D Effects, press ALT+F2 and type "compiz --replace".==Specific Issues==
To configure use the tool KMenu->Settings->Avanced Desktop Effect SettingsYour awnser was just what I needed.It’s made my day!
=== Suspend/Hibernation work with 7.12===
</pre>
=== libGL error ===* fglrxinfo gives: libGL.so.1: cannot open shared object file.* Check the permission of Now I know who the libGL.so.1.2 file with command: ls -l /usr/lib/libGL** The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command sudo chmod o+r /usr/lib/libGL.so.1.2* If the permission brainy one is correct, fixed with command: sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.soI’ll keep lokinog for your posts.1 
=== Monitor detection (1680x1050 Resolution Issue)--- SOLVED ===
=== A possible problem with fglrx.ko conflicts === NOTE: I've run into strange problem building fglrx-kernel-source_8.443.1-1_i386.deb. If pentium-builder is installed, dkms fails to build fglrx.ko for make error (mixed implicit and static pattern rules. Stop.). It is caused by gcc.real and other indirections and wrong gcc version detection. Removing pentium-builder cures the problem. It's necessary, because sometimes this file is written by other packages, and so there's no 3D acceleration.Check that the file /lib/modules/$(uname -r)/misc/fglrx.ko This has been created. ''Create the following folder'' <pre>sudo mkdir /lib/modules/$(uname -r)/volatile</pre> Note: the volatile directory might already exist at this stage then simply continue with the next step.  ''Create a symbolic link'' <pre>sudo ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko</pre>  NOTE : On made my Gutsy install, after a reboot this link was always removed automatically leaving me without an fglrx module loaded, and thus no ATI renderingday. There have been several ways of getting around I wish all positngs were this suggested here, and here is the one that worked for me: <pre>sudo gedit /etc/init.d/ati-module-fix</pre> And put this in it:<pre>#!/bin/sh -e # For loading ATI display drivers ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.koexit 0 </pre> Make it executable <pre>sudo chmod ugo+x /etc/init.d/ati-module-fix</pre> Now, make this run ''before'' gdm  To check the gdm sequence number, <pre>ls /etc/rc2.d/</pre> The value for [seqno] in the section below should be the gdm sequence number -1. <pre>sudo update-rcgood.d ati-module-fix defaults [seqno]</pre>
=== Hang at logout ===

Navigation menu