Ubuntu: Difference between revisions
(revert) |
(manually copy+pasting unsupported adapte) |
||
(53 intermediate revisions by 32 users not shown) | |||
Line 13: | Line 13: | ||
* If you want to use a newer version of the driver than the one which comes with your distribution and you have ''linux-restricted-modules'' installed, you have to disable the fglrx kernel module from ''linux-restricted-modules'' because it will invariably get in the way of your more recent drivers. Detailed information on how to achieve this can be found in the distribution-specific guides. | * If you want to use a newer version of the driver than the one which comes with your distribution and you have ''linux-restricted-modules'' installed, you have to disable the fglrx kernel module from ''linux-restricted-modules'' because it will invariably get in the way of your more recent drivers. Detailed information on how to achieve this can be found in the distribution-specific guides. | ||
* You can configure the driver with the ''' | * You can configure the driver with the '''amdconfig''' tool, more information can be found at [[Configuring]]. | ||
=== Old Version gets installed during update === | === Old Version gets installed during update === | ||
When updating a manual install - that is removing the old install and installing the new version - | When updating a manual install - that is removing the old install and installing the new version - | ||
the old version might get installed again. This was observed starting with 8.10. If this happens it might help to remove the old version then delete the debian package files of the old version and run "sudo apt-get clean" before installing the new version. See the Ubuntu version dependent install documentation for instructions how to perform these steps. As soon as a new Catalyst version (current is | the old version might get installed again. This was observed starting with 8.10. If this happens it might help to remove the old version then delete the debian package files of the old version and run "sudo apt-get clean" before installing the new version. See the Ubuntu version dependent install documentation for instructions how to perform these steps. As soon as a new Catalyst version (current is 12.10 - as of Nov. 09, 2012) is available, these instructions might get updated. | ||
Very nice site! | |||
== Installation == | == Installation == | ||
* [[Ubuntu Wily Installation Guide| Wily 15.10]] | |||
* [[Ubuntu Vivid Installation Guide| Vivid 15.04]] | |||
* [[Ubuntu Utopic Installation Guide| Utopic 14.10]] | |||
* [[Ubuntu Trusty Installation Guide| Trusty 14.04]] | |||
* [[Ubuntu Saucy Installation Guide| Saucy 13.10]] | |||
* [[Ubuntu Raring Installation Guide| Raring 13.04]] | |||
* [[Ubuntu Quantal Installation Guide| Quantal 12.10]] | |||
* [[Ubuntu Precise Installation Guide| Precise 12.04]] | * [[Ubuntu Precise Installation Guide| Precise 12.04]] | ||
* [[Ubuntu Oneiric Installation Guide| Oneiric 11.10]] | * [[Ubuntu Oneiric Installation Guide| Oneiric 11.10]] | ||
Line 32: | Line 41: | ||
* [[Ubuntu Feisty Installation Guide|Feisty 7.04]] | * [[Ubuntu Feisty Installation Guide|Feisty 7.04]] | ||
* [[Ubuntu Edgy Installation Guide|Edgy 6.10]] | * [[Ubuntu Edgy Installation Guide|Edgy 6.10]] | ||
* [[Ubuntu Dapper Installation Guide|Dapper 6. | * [[Ubuntu Dapper Installation Guide|Dapper 6.06]] | ||
* [[Ubuntu Breezy Installation Guide|Breezy 5.10]] | * [[Ubuntu Breezy Installation Guide|Breezy 5.10]] | ||
Line 44: | Line 53: | ||
At this stage, do not panic! This does not necessarily imply a problem with the module, indeed your card may be not officially supported. Numerous reports on forums show that users end up using the drivers successfully anyway, e.g. for an HD 6850 card (BARTS codename). To force Xorg to load the driver for fglrx anyway, just manually create a minimal xorg.conf file, as suggested on this wiki (follow the tutorials). The module should then load and everything else should (hopefully) work. (On my system even the Catalyst Control Center was working at that point.) Except you have the "Unsupported hardware" mark on a corner of the screen, but that is another problem... (Forum users report they have been able to get rid of this as well, although caution should be used as the hack scripts seem not to work with version 11.1 of the Catalyst drivers.) | At this stage, do not panic! This does not necessarily imply a problem with the module, indeed your card may be not officially supported. Numerous reports on forums show that users end up using the drivers successfully anyway, e.g. for an HD 6850 card (BARTS codename). To force Xorg to load the driver for fglrx anyway, just manually create a minimal xorg.conf file, as suggested on this wiki (follow the tutorials). The module should then load and everything else should (hopefully) work. (On my system even the Catalyst Control Center was working at that point.) Except you have the "Unsupported hardware" mark on a corner of the screen, but that is another problem... (Forum users report they have been able to get rid of this as well, although caution should be used as the hack scripts seem not to work with version 11.1 of the Catalyst drivers.) | ||
== Related Resources == | == Related Resources == |
Latest revision as of 00:21, 21 August 2016
Tips and Tricks
- To build your own .deb packages for Ubuntu you will need to install at least the following packages from the apt repositories:
- build-essential
- fakeroot
- dh-make
- debconf
- execstack
- dh-modaliases
- Moreover for latest releases, the following package simplifies module installation:
- dkms
- If you want to use a newer version of the driver than the one which comes with your distribution and you have linux-restricted-modules installed, you have to disable the fglrx kernel module from linux-restricted-modules because it will invariably get in the way of your more recent drivers. Detailed information on how to achieve this can be found in the distribution-specific guides.
- You can configure the driver with the amdconfig tool, more information can be found at Configuring.
Old Version gets installed during update
When updating a manual install - that is removing the old install and installing the new version - the old version might get installed again. This was observed starting with 8.10. If this happens it might help to remove the old version then delete the debian package files of the old version and run "sudo apt-get clean" before installing the new version. See the Ubuntu version dependent install documentation for instructions how to perform these steps. As soon as a new Catalyst version (current is 12.10 - as of Nov. 09, 2012) is available, these instructions might get updated.
Very nice site!
Installation
- Wily 15.10
- Vivid 15.04
- Utopic 14.10
- Trusty 14.04
- Saucy 13.10
- Raring 13.04
- Quantal 12.10
- Precise 12.04
- Oneiric 11.10
- Natty 11.04
- Maverick 10.10
- Lucid 10.04
- Karmic 9.10
- Jaunty 9.04
- Intrepid 8.10
- Hardy 8.04
- Gutsy 7.10
- Feisty 7.04
- Edgy 6.10
- Dapper 6.06
- Breezy 5.10
Unsupported adapter
Specific notes for Radeon HD 6xxx cards with no official support yet (see Hardware#Not_Yet_Supported_or_Unoffically_Supported).
After installing the fglrx module, you might get the following message when trying to configure X through aticonfig:
aticonfig: No supported adapters detected
Also you might see that the fglrx module has not been used by Xorg (no line saying ‘‘LoadModule: "fglrx"’’ in /var/log/Xorg.0.log). Also on my system I had segmentation faults from the ati Catalyst Control Center (amdcccle).
At this stage, do not panic! This does not necessarily imply a problem with the module, indeed your card may be not officially supported. Numerous reports on forums show that users end up using the drivers successfully anyway, e.g. for an HD 6850 card (BARTS codename). To force Xorg to load the driver for fglrx anyway, just manually create a minimal xorg.conf file, as suggested on this wiki (follow the tutorials). The module should then load and everything else should (hopefully) work. (On my system even the Catalyst Control Center was working at that point.) Except you have the "Unsupported hardware" mark on a corner of the screen, but that is another problem... (Forum users report they have been able to get rid of this as well, although caution should be used as the hack scripts seem not to work with version 11.1 of the Catalyst drivers.)
Related Resources
- Ubuntuforums.org Video forum: Dapper
Distribution Neutral Steps |