Catalyst 10.7: Difference between revisions

From cchtml.com
(Created page with 'ATI Catalyst Linux 10.7 driver<br /> Revision Number: 10.7 (8.753)<br /> Release Date: 7/26/2010<br /> Description: Automated installer and Display Drivers for X.Org 6.8, 6.9, 7.…')
 
 
Line 3: Line 3:
Release Date: 7/26/2010<br />
Release Date: 7/26/2010<br />
Description: Automated installer and Display Drivers for X.Org 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4, or 7.5 <br />
Description: Automated installer and Display Drivers for X.Org 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4, or 7.5 <br />
'''Troubleshooting'''
This version officially supports Ubuntu Lucid, but in order to generate the distribution-specific package for it you might need to first type in terminal:
sudo apt-get install execstack dh-make
Otherwise there will be an error, this was found out from reading /usr/share/ati/fglrx-install.log after an unsuccessful install.
It might also be necessary to run the uninstall script found in the same folder (/usr/share/ati/) if a previous driver was installed before or
an install failed. Note that the installer does not tell if the package generation fails, this is only mentioned in the logfile.
After this, it is possible to generate the packages using the installer.
Tested on a 64-bit AMD CPU.


== External Links ==
== External Links ==

Latest revision as of 20:05, 9 August 2010

ATI Catalyst Linux 10.7 driver
Revision Number: 10.7 (8.753)
Release Date: 7/26/2010
Description: Automated installer and Display Drivers for X.Org 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4, or 7.5

Troubleshooting

This version officially supports Ubuntu Lucid, but in order to generate the distribution-specific package for it you might need to first type in terminal:

sudo apt-get install execstack dh-make

Otherwise there will be an error, this was found out from reading /usr/share/ati/fglrx-install.log after an unsuccessful install. It might also be necessary to run the uninstall script found in the same folder (/usr/share/ati/) if a previous driver was installed before or an install failed. Note that the installer does not tell if the package generation fails, this is only mentioned in the logfile.

After this, it is possible to generate the packages using the installer.

Tested on a 64-bit AMD CPU.


External Links