Ubuntu: Difference between revisions

From cchtml.com
(→‎Unsupported-specific: do not panic when aticonfig does not work)
(→‎Unsupported adapter: scripts do not work on 11.1)
Line 35: Line 35:
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).
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.)
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 ==

Revision as of 20:32, 6 February 2011

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
  • 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 aticonfig tool, more information can be found at Configuring.

Installation

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

Verifying | Configuring | Troubleshooting