Changes

Jump to: navigation, search

Ubuntu Maverick Installation Guide

3,170 bytes removed, 19:55, 24 October 2010
Revised
* '''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.
* '''radeonhd''' - an alternate driver supporting R520-R7x0 hardware. This driver is now officially deprecated in favor of radeon. If you still want to try it, see: https://help.ubuntu.com/community/RadeonHD
* '''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.
= Issues =
 
== Build Fails and Log Shows "error: implicit declaration of function ‘compat_alloc_user_space’" ==
 
This issue occurs with more recent Lucid kernels (>= 2.6.32-25-generic). A workaround is proposed here: http://ubuntuforums.org/showpost.php?p=9877727&postcount=10
 
A slightly more detailed instructions (for newbies) are here: http://ubuntuforums.org/showthread.php?s=72306ca847141e035ce8bf9b28506c76&t=1576383
== 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/8.741780/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.4 in Ubuntu LucidMaverick). This should allow you to install fglrx:
$ sudo ln -sf /usr/bin/gcc-4.4 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:
$ sudo dpkg -i --force-overwrite fglrx*.deb
 
== Crashes in WINE ==
For more information, see [http://bugs.winehq.org/show_bug.cgi?id=4561#c6 this WINEHQ bug report]. This issue should be fixed in WINE 1.1.40, so you may want to get an updated version of WINE by using [https://launchpad.net/~vivnet/+archive/vivnet-wine this PPA]. If you prefer the Ubuntu version of WINE, then turn FastTLS off:
$ sudo aticonfig --tls=0
 
== Segfault Starting Xserver ==
 
After upgrading to Catalyst 10-6 the Xserver does not start. Xorg.0.log shows a segmentation fault. Adding
BusID "PCI:1:0:0"
to the fglrx Device section in xorg.conf helps. For more information, look at [http://ati.cchtml.com/show_bug.cgi?id=1836 bug #1836] in the bugtracker.
== Problems Starting Xserver ==
== Slow Maximizing Windows/General 2D Slowness ==
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. The new acceleration code was also available in Catalyst 10-2 through 10-5 (including the Catalyst that ships with Lucid), though it was not used by default. If you're using one of those versions, you can try the new acceleration code with the following command: $ sudo aticonfig --set-pcs-str=DDX,Direct2DAccel,TRUERestart X (by logging out or rebooting) to apply the change. If you experience issues and want to return to the older, stable code: $ sudo aticonfig --del-pcs-key=DDX,Direct2DAccelIf you're using Catalyst 10-6 or laternot running compositing/desktop effects, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE
EndSection
</pre>
 
----
 
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:<i>(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! *</i>
 
:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart some others:
$ sudo modprobe -r i82875p_edac
$ sudo modprobe -r fglrx
$ sudo modprobe -r intel-agp
$ sudo modprobe -r agpgart
$ sudo modprobe agpgart
$ sudo modprobe intel-agp
$ sudo modprobe fglrx
 
:Blacklist the modules e7xxx_edac so it doesn't start up again when booting
$ gksu gedit /etc/modprobe.d/blacklisti82875p_edac.conf
:add the following line to the blank text file:
:<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 upgraded to your current Ubuntu install (rather than doing a clean install), you may still be using the old kernel without knowing it.
$ uname -r
:If your kernel version is less than 2.6.32, it is a kernel from a previous Ubuntu installation.
 
If this doesn't help, try 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 ==
331
edits

Navigation menu