Ubuntu Lucid Installation Guide - Revision history

Dtl131: Add note on libatiuki error

2013-01-04T21:28:00Z

Add note on libatiuki error

← Older revision		Revision as of 21:28, 4 January 2013
Line 351:		Line 351:
	$ sudo update-alternatives --auto gl_conf		$ sudo update-alternatives --auto gl_conf
	After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.		After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.

			== Failed to load /usr/lib/xorg/extra-modules/modules/linux/libfglrxdrm.so ==

			https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/748308
			This error can often be fixed quickly with
			$ sudo ldconfig -v \| grep -i libatiuki

Dtl131: ATI -> AMD, remove old watermark hack

2012-01-27T03:05:14Z

ATI -> AMD, remove old watermark hack

@@ Line 68: / Line 68: @@
 This package contains both the 32-bit and 64-bit driver.
   $ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
-  $ wget http://www2.ati.com/drivers/linux/ati-driver-installer-{{catalystdashversion}}-x86.x86_64.run
+  $ wget http://www2.ati.com/drivers/linux/amd-driver-installer-{{catalystdashversion}}-x86.x86_64.run
 ===''Create .deb packages.''===
-  $ sudo sh ati-driver-installer-{{catalystdashversion}}-x86.x86_64.run --buildpkg Ubuntu/lucid
+  $ sudo sh amd-driver-installer-{{catalystdashversion}}-x86.x86_64.run --buildpkg Ubuntu/lucid
 ===''Install .debs.''===
@@ Line 210: / Line 210: @@
   $ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE
   $ sudo service gdm start

Mooninite: Protected "Ubuntu Lucid Installation Guide": Excessive vandalism ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2011-10-07T00:57:51Z

Protected "Ubuntu Lucid Installation Guide": Excessive vandalism ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

← Older revision	Revision as of 00:57, 7 October 2011
(No difference)

Mooninite: Reverted edits by 63.119.11.20 (talk) to last revision by Mooninite

2011-10-07T00:56:53Z

Reverted edits by 63.119.11.20 (talk) to last revision by Mooninite

← Older revision		Revision as of 00:56, 7 October 2011
Line 45:		Line 45:
	NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.		NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.

	~~Thanks for sharing~~. ~~What a plesuare to read!~~		== Ubuntu X Team's PPA ==
			This is an excellent PPA, frequently updated, and run by Ubuntu veterans.
			$ sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
			$ sudo apt-get update
			At this point, you should install available updates and then you can install the driver:
			$ sudo apt-get install fglrx

	== Installing the drivers manually ==		== Installing the drivers manually ==

63.119.11.20: /* Ubuntu X Team's PPA */

2011-10-07T00:35:32Z

Ubuntu X Team's PPA

← Older revision		Revision as of 00:35, 7 October 2011
Line 45:		Line 45:
	NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.		NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.

	~~== Ubuntu X Team's PPA ==~~		Thanks for sharing. What a plesuare to read!
	~~This is an excellent PPA, frequently updated, and run by Ubuntu veterans~~.
	~~$ sudo add-apt-repository ppa:ubuntu-x-swat/x-updates~~
	~~$ sudo apt-get update~~
	~~At this point, you should install available updates and then you can install the driver:~~
	~~$ sudo apt-get install fglrx~~

	== Installing the drivers manually ==		== Installing the drivers manually ==

Mooninite: Protected "Ubuntu Lucid Installation Guide": Excessive vandalism ([edit=autoconfirmed] (expires 06:19, 6 October 2011 (UTC)) [move=autoconfirmed] (expires 06:19, 6 October 2011 (UTC)))

2011-10-05T06:19:08Z

Protected "Ubuntu Lucid Installation Guide": Excessive vandalism ([edit=autoconfirmed] (expires 06:19, 6 October 2011 (UTC)) [move=autoconfirmed] (expires 06:19, 6 October 2011 (UTC)))

← Older revision	Revision as of 06:19, 5 October 2011
(No difference)

Mooninite: Reverted edits by 203.158.200.26 (talk) to last revision by Mooninite

2011-10-05T06:16:46Z

Reverted edits by 203.158.200.26 (talk) to last revision by Mooninite

← Older revision		Revision as of 06:16, 5 October 2011
Line 365:		Line 365:
	[[Category:Installation Documentation]]		[[Category:Installation Documentation]]

	~~Knwoledge wants~~ to be ~~free~~, ~~just like these articles!~~		== Aticonfig not found after installation & "module does not exist" after boot ==
			This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous use of fglrx through the Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing aticonfig --initial after driver installation, you might end up not having the aticonfig available at all:
			<pre>aticonfig: 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.

203.158.200.26: /* Aticonfig not found after installation & "module does not exist" after boot */

2011-10-05T06:04:35Z

Aticonfig not found after installation & "module does not exist" after boot

← Older revision		Revision as of 06:04, 5 October 2011
Line 365:		Line 365:
	[[Category:Installation Documentation]]		[[Category:Installation Documentation]]

	~~== Aticonfig not found after installation & "module does not exist" after boot ==~~		Knwoledge wants to be free, just like these articles!
	~~This scenario is possible when the driver installation has seemingly succeeded and is possibly related~~ to previous use of fglrx through the Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing aticonfig --initial after driver installation, you might end up not having the aticonfig available at all:
	~~<pre>aticonfig: 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.~~

Mooninite: Reverted edits by 107.20.254.236 (talk) to last revision by Dtl131

2011-10-05T01:23:56Z

Reverted edits by 107.20.254.236 (talk) to last revision by Dtl131

Show changes

107.20.254.236: xEmeSOdExJ

2011-10-04T08:50:38Z

xEmeSOdExJ

Show changes