cchtml.com - User contributions [en]

Red Hat Enterprise Linux

2009-05-31T00:42:03Z

69.0.17.67: /* Important Note as of 5/18/2009 */

"Red Hat Enterprise Linux is the leading platform for open source computing. It is sold by subscription, delivers continuous value and is certified by top enterprise hardware and software vendors. From the desktop to the datacenter, Enterprise Linux couples the innovation of open source technology and the stability of a true enterprise-class platform." -redhat.com

Please note that Red Hat Enterprise Linux and Fedora Core are distantly related and are not the same product. Please see the [[Fedora]] distribution page for more details.

Another option for those wanting the stability of RHEL, there are various RHEL clones, some of them listed below:

- [http://centos.org/ CentOS] is a community effort which tracks each RHEL release and update and offers up2date and yum service. All this for free, donations encouraged.

- The [http://linux.startcom.org/ StartCom Linux] operating systems, are based on the RedHat Enterprise and Fedora source code each modified with reliability, security and efficiency in mind, to fit the tasks assigned to each flavor of StartCom Linux.

==Installation Workaround for RHEL clones==
Installation of current RPMs like fglrx_6_8_0-8.42.3-1.i386.rpm may fail on RHEL clones with this error message:

FATAL: Module fglrx not found.
/var/tmp/rpm-tmp.5182: line 807: [: =: unary operator expected

The problem is that the installation script searches for the string "Red Hat" in /etc/redhat-release. So before installing the RPM simply replace "CentOS" by "Red Hat" in /etc/redhat-release using a text editor. After the RPM has installed successfully I recommend to restore your old /etc/redhat-release. For StartCom Linux create the file /etc/redhat-release with the string "Red Hat" in it. This seems to have been fixed as of CentOS 5.1.

==Red Hat Enterprise Linux 4 Update 3 (RHEL 4.3 and CentOS 4.3)==
The ATI GUI installer worked just fine for me with my Radeon 9700 Pro and CentOS (RHEL) 4.3. ATI claims to "officially" support both RHEL and SUSE, So contrary to the complex install procedure shown on the SUSE pages of this wiki, if you have RHEL, I would go with the simplest approach in the Related Resources link below.
==Red Hat Enterprise Linux 4 Update 6==
The ATI GUI installer on a ThinkPad T60 needed to install kernel-devel and rpm-build
# up2date -f kernel-devel rpm-build
# ./ati-driver-installer-8-4-x86.x86_64.run --listpkg
# ./ati-driver-installer-8-4-x86.x86_64.run --buildpkg RedHat/RHEL4

==Red Hat Enterprise Linux 5.0 (RHEL 5.0 and CentOS 5.0)==
fglrx versions up to and including 8.36.5 require that you install some compatabiliy RPMs.

Here is what I did to get the fglrx driver to run with my FireGX 5150 on CentOS 5.0:

Install ATI driver 8.36.5.

Display all compat-* RPMs if you like:
yum list "compat-*"

Install the compat RPMs. I installed a bunch of them that I need for other reasons:
yum install compat-libstdc -33 compat-glibc compat-gcc-34 compat-readline compat-libf2c
I do not know which if these RPMs are actually needed for fglrx. They appear above ordered from most likely, to least likely to be needed.

As of CentOS 5.1 (and thus, probably, RHEL 5.1) the only compat library required is compat-libstdc++-33. Note that you may need to temporarily disable SELinux (setenforce 0) during the fglrx install or SELinux will block part of the install. I backed out the install (rpm -e), turned off SELinux and re-ran the install so no idea whether it will work if you don't turn off SELinux. Once the install is complete, you can re-enable SELinux with setenforce 1.

The aticonfig program crashes, so you will have to edit /etc/X11/xorg.conf file yourself. All I had to do was change the driver from "vesa" to, "fgrlx":
Section "Device"
Identifier "Videocard0"
Driver "fglrx"
EndSection

As of CentOS 5.1 (and probably RHEL 5.1) this is no longer the case. aticonfig --initial works as expected.

Reboot

A couple of notes to the really good summary above...
You also need the -devel RPMs for most of the packages listed (and a number not). After that I managed to get the aticonf program to not crash by doing:
aticonfig --initial=dual-head --screen-layout=right
You also should add the following to your xorg.conf file:

Section "Extensions"
Option "Composite" "0"
EndSection

However there are still problems with the fgrlx driver. Even after all of this and a reboot fglrxinfo still says the system is using Mesa GLX Indirect rendering. Also the ATI Catalyst Control Center (amdcccle) will now restart X when you try to run it. Basically it is a mess and I think we need to wait until an updated driver comes along for RHEL 5.

The above no longer appears to be the case as of centOS 5.1. I did not need any devel rpms and fglrxinfo shows:

[root@bend ~]# /usr/bin/fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: Radeon X1300/X1550 Series
OpenGL version string: 2.1.7276 Release

== Important Note as of 5/18/2009 ==
None of the above seems to work for an ATI Radeon HD4670 (512 MB) with the Dell S2409W 24" widescreen LCD on a Dell XPS 435MT (core i7-920) running under 64 bit CentOS 5.3 with the latest updates as of 5/18/2009. "Automatic" installation of the ATI Catalyst 9.4 driver seems to run smoothly, fglrxinfo detects and reports the graphics hardware, and aticonfig --initial reports that it saved a backup of xorg.conf. However, restart X11 (or reboot the PC) and what you get is an incomprehensible screen full of big squares peppered with little dots. Alt-R will reboot the PC and allow use of CD 1 to reboot linux in rescue mode, after which the driver's uninstall script works nicely. So no permanent harm seems to be done.

Here is what finally worked on this particular hardware:

First, to save time and effort, as root edit /etc/inittab and change runlevel to 3. Replace this line
<pre>id:5:initdefault:</pre>
with
<pre># id:5:initdefault:
# for tinkering with display and xorg.conf
# boots to text mode, requires startx to start X
id:3:initdefault:</pre>
Then the system will boot to multiuser with text display, and X can be started by startx.

Next, make sure that the required packages have been installed. After reading the installation instructions, I used CentOS 5.3's graphical Package Manager to install the Development Libraries, Gnome Software Development, and X Software Development. Undoubtedly this adds more than the bare minimum, but disk space is cheap and (my) time is not.

I took the path of generating and testing rpms. This made it easy to back out of any drivers that failed to work (and plenty failed)--just ^-Alt-Backspace to break out of X, then at the command line
<pre>rpm -e drivername</pre>
e.g.
<pre>rpm -e fglrx64_7_1_0</pre>
and finally make sure that /etc/X11/xorg.conf was restored to a copy of its original form.

'''Caution:''' when testing, one version (8.6) responded to startx by blanking the screen for several seconds, during which the fans in the Dell XPS 435 revved up and stayed revved up. This made me nervous as I imagined the possibility that the video card might overheat (read something about that somewhere on the WWW in connection with a different card and a different driver). I had to repeatedly press ^-Alt-Del and ^-Alt-Backspace to stop it and reboot.

Finally I discovered that the 8.8 version worked with my hardware.

'''Installing the version 8.8 driver'''

The ATI page for the 8.8 version actually placed a file called ati-driver-installer-8-7-x86.x86_64.run on my Desktop. The name suggests that it's 8.7, but I tried it anyway.

As root,
<pre>sh ./ati-driver-installer-8-7-x86.x86_64.run</pre>
brought up a panel that I used to select "Generate Distribution Specific Driver Package." I selected RedHat/RHEL5_64a (RedHat/RHEL5 for 32 bit). The driver package turned out to be an rpm called fglrx64_7_1_0-8.512-1.x86_64.rpm (fglrx_7_1_0-8.512-1.i386.rpm for 32 bit).

Then I ran
<pre>rpm -Uvh fglrx64_7_1_0-8.512-1.x86_64.rpm</pre>
which failed with an error message that indicated it needed compat-libstdc++-33. After installing that, I tried installing the fglrx... rpm again, which succeeded. Finally, I typed
<pre>aticonfig --initial</pre>
at the system prompt.

I rebooted, logged in as myself (not root), ran startx, and was relieved to see that the display was in a higher resolution mode, and ATI Catalyst Control Center now appeared in the System / Preferences and System / Administration menus.

Turns out I couldn't run ATI Catalyst Control Center as myself--had to su, then run amdcccle at the command line.

After verifying that all was well, as root I restored the boot runlevel to 5 by editing /etc/inittab again.

Did a bit of tinkering and got the following performance out of glxgears: 720 frames in 5.4 sec = 133 FPS.
Doesn't seem too impressive. fgl_glxgears causes a segmentation fault and exits. Dragging windows around the screen, I see a distinct lag between when I drag something and when it finally gets to its location. But at least I'm not looking at a 1200x800 display.

==Tips and Tricks==
If you have SELinux enabled and set to enforcing you may need to change the context of the fglrx_dri.so file for it to load properly:

chcon -t textrel_shlib_t /usr/lib/dri/fglrx_dri.so

Substitute lib with lib64 where appropriate.

==Related Resources==
[http://ati.amd.com/support/drivers/linux/linux-radeon.html Follow link "ATI Driver Installer"]

{{VCT}}
[[Category:Distributions]]
[[Category:NeedsUpdating]]

Red Hat Enterprise Linux

2009-05-31T00:33:33Z

69.0.17.67: /* Important Note as of 5/18/2009 */

"Red Hat Enterprise Linux is the leading platform for open source computing. It is sold by subscription, delivers continuous value and is certified by top enterprise hardware and software vendors. From the desktop to the datacenter, Enterprise Linux couples the innovation of open source technology and the stability of a true enterprise-class platform." -redhat.com

Please note that Red Hat Enterprise Linux and Fedora Core are distantly related and are not the same product. Please see the [[Fedora]] distribution page for more details.

Another option for those wanting the stability of RHEL, there are various RHEL clones, some of them listed below:

- [http://centos.org/ CentOS] is a community effort which tracks each RHEL release and update and offers up2date and yum service. All this for free, donations encouraged.

- The [http://linux.startcom.org/ StartCom Linux] operating systems, are based on the RedHat Enterprise and Fedora source code each modified with reliability, security and efficiency in mind, to fit the tasks assigned to each flavor of StartCom Linux.

==Installation Workaround for RHEL clones==
Installation of current RPMs like fglrx_6_8_0-8.42.3-1.i386.rpm may fail on RHEL clones with this error message:

FATAL: Module fglrx not found.
/var/tmp/rpm-tmp.5182: line 807: [: =: unary operator expected

The problem is that the installation script searches for the string "Red Hat" in /etc/redhat-release. So before installing the RPM simply replace "CentOS" by "Red Hat" in /etc/redhat-release using a text editor. After the RPM has installed successfully I recommend to restore your old /etc/redhat-release. For StartCom Linux create the file /etc/redhat-release with the string "Red Hat" in it. This seems to have been fixed as of CentOS 5.1.

==Red Hat Enterprise Linux 4 Update 3 (RHEL 4.3 and CentOS 4.3)==
The ATI GUI installer worked just fine for me with my Radeon 9700 Pro and CentOS (RHEL) 4.3. ATI claims to "officially" support both RHEL and SUSE, So contrary to the complex install procedure shown on the SUSE pages of this wiki, if you have RHEL, I would go with the simplest approach in the Related Resources link below.
==Red Hat Enterprise Linux 4 Update 6==
The ATI GUI installer on a ThinkPad T60 needed to install kernel-devel and rpm-build
# up2date -f kernel-devel rpm-build
# ./ati-driver-installer-8-4-x86.x86_64.run --listpkg
# ./ati-driver-installer-8-4-x86.x86_64.run --buildpkg RedHat/RHEL4

==Red Hat Enterprise Linux 5.0 (RHEL 5.0 and CentOS 5.0)==
fglrx versions up to and including 8.36.5 require that you install some compatabiliy RPMs.

Here is what I did to get the fglrx driver to run with my FireGX 5150 on CentOS 5.0:

Install ATI driver 8.36.5.

Display all compat-* RPMs if you like:
yum list "compat-*"

Install the compat RPMs. I installed a bunch of them that I need for other reasons:
yum install compat-libstdc -33 compat-glibc compat-gcc-34 compat-readline compat-libf2c
I do not know which if these RPMs are actually needed for fglrx. They appear above ordered from most likely, to least likely to be needed.

As of CentOS 5.1 (and thus, probably, RHEL 5.1) the only compat library required is compat-libstdc++-33. Note that you may need to temporarily disable SELinux (setenforce 0) during the fglrx install or SELinux will block part of the install. I backed out the install (rpm -e), turned off SELinux and re-ran the install so no idea whether it will work if you don't turn off SELinux. Once the install is complete, you can re-enable SELinux with setenforce 1.

The aticonfig program crashes, so you will have to edit /etc/X11/xorg.conf file yourself. All I had to do was change the driver from "vesa" to, "fgrlx":
Section "Device"
Identifier "Videocard0"
Driver "fglrx"
EndSection

As of CentOS 5.1 (and probably RHEL 5.1) this is no longer the case. aticonfig --initial works as expected.

Reboot

A couple of notes to the really good summary above...
You also need the -devel RPMs for most of the packages listed (and a number not). After that I managed to get the aticonf program to not crash by doing:
aticonfig --initial=dual-head --screen-layout=right
You also should add the following to your xorg.conf file:

Section "Extensions"
Option "Composite" "0"
EndSection

However there are still problems with the fgrlx driver. Even after all of this and a reboot fglrxinfo still says the system is using Mesa GLX Indirect rendering. Also the ATI Catalyst Control Center (amdcccle) will now restart X when you try to run it. Basically it is a mess and I think we need to wait until an updated driver comes along for RHEL 5.

The above no longer appears to be the case as of centOS 5.1. I did not need any devel rpms and fglrxinfo shows:

[root@bend ~]# /usr/bin/fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: Radeon X1300/X1550 Series
OpenGL version string: 2.1.7276 Release

== Important Note as of 5/18/2009 ==
None of the above seems to work for an ATI Radeon HD4670 (512 MB) with the Dell S2409W 24" widescreen LCD on a Dell XPS 435MT (core i7-920) running under 64 bit CentOS 5.3 with the latest updates as of 5/18/2009. "Automatic" installation of the ATI Catalyst 9.4 driver seems to run smoothly, fglrxinfo detects and reports the graphics hardware, and aticonfig --initial reports that it saved a backup of xorg.conf. However, restart X11 (or reboot the PC) and what you get is an incomprehensible screen full of big squares peppered with little dots. Alt-R will reboot the PC and allow use of CD 1 to reboot linux in rescue mode, after which the driver's uninstall script works nicely. So no permanent harm seems to be done.

Here is what finally worked on this particular hardware:

First, to save time and effort, as root edit /etc/inittab and change runlevel to 3. Replace this line
<pre>id:5:initdefault:</pre>
with
<pre># id:5:initdefault:
# for tinkering with display and xorg.conf
# boots to text mode, requires startx to start X
id:3:initdefault:</pre>
Then the system will boot to multiuser with text display, and X can be started by startx.

Next, make sure that the required packages have been installed. After reading the installation instructions, I used CentOS 5.3's graphical Package Manager to install the Development Libraries, Gnome Software Development, and X Software Development. Undoubtedly this adds more than the bare minimum, but disk space is cheap and (my) time is not.

I took the path of generating and testing rpms. This made it easy to back out of any drivers that failed to work (and plenty failed)--just ^-Alt-Backspace to break out of X, then at the command line
<pre>rpm -e drivername</pre>
e.g.
<pre>rpm -e fglrx64_7_1_0</pre>
and finally make sure that /etc/X11/xorg.conf was restored to a copy of its original form.

'''Caution:''' when testing, one version (8.6) responded to startx by blanking the screen for several seconds, during which the fans in the Dell XPS 435 revved up and stayed revved up. This made me nervous as I imagined the possibility that the video card might overheat (read something about that somewhere on the WWW in connection with a different card and a different driver). I had to repeatedly press ^-Alt-Del and ^-Alt-Backspace to stop it and reboot.

Finally I discovered that the 8.8 version worked with my hardware.

'''Installing the version 8.8 driver'''

The ATI page for the 8.8 version actually placed a file called ati-driver-installer-8-7-x86.x86_64.run on my Desktop. The name suggests that it's 8.7, but I tried it anyway.

As root,
<pre>sh ./ati-driver-installer-8-7-x86.x86_64.run</pre>
brought up a panel that I used to select "Generate Distribution Specific Driver Package." I selected RedHat/RHEL5_64a (RedHat/RHEL5 for 32 bit). The driver package turned out to be an rpm called fglrx64_7_1_0-8.512-1.x86_64.rpm (fglrx_7_1_0-8.512-1.i386.rpm for 32 bit).

Then I ran
<pre>rpm -Uvh fglrx64_7_1_0-8.512-1.x86_64.rpm</pre>
and after the installer exited, typed
<pre>aticonfig --initial</pre>
at the system prompt.

I rebooted, logged in as myself (not root), ran startx, and was relieved to see that the display was in a higher resolution mode, and ATI Catalyst Control Center now appeared in the System / Preferences and System / Administration menus.

Turns out I couldn't run ATI Catalyst Control Center as myself--had to su, then run amdcccle at the command line.

After verifying that all was well, as root I restored the boot runlevel to 5 by editing /etc/inittab again.

Did a bit of tinkering and got the following performance out of glxgears: 720 frames in 5.4 sec = 133 FPS.
Doesn't seem too impressive. fgl_glxgears causes a segmentation fault and exits. Dragging windows around the screen, I see a distinct lag between when I drag something and when it finally gets to its location. But at least I'm not looking at a 1200x800 display.

==Tips and Tricks==
If you have SELinux enabled and set to enforcing you may need to change the context of the fglrx_dri.so file for it to load properly:

chcon -t textrel_shlib_t /usr/lib/dri/fglrx_dri.so

Substitute lib with lib64 where appropriate.

==Related Resources==
[http://ati.amd.com/support/drivers/linux/linux-radeon.html Follow link "ATI Driver Installer"]

{{VCT}}
[[Category:Distributions]]
[[Category:NeedsUpdating]]

Red Hat Enterprise Linux

2009-05-29T18:48:21Z

69.0.17.67: /* Important Note as of 5/18/2009 */

"Red Hat Enterprise Linux is the leading platform for open source computing. It is sold by subscription, delivers continuous value and is certified by top enterprise hardware and software vendors. From the desktop to the datacenter, Enterprise Linux couples the innovation of open source technology and the stability of a true enterprise-class platform." -redhat.com

Please note that Red Hat Enterprise Linux and Fedora Core are distantly related and are not the same product. Please see the [[Fedora]] distribution page for more details.

Another option for those wanting the stability of RHEL, there are various RHEL clones, some of them listed below:

- [http://centos.org/ CentOS] is a community effort which tracks each RHEL release and update and offers up2date and yum service. All this for free, donations encouraged.

- The [http://linux.startcom.org/ StartCom Linux] operating systems, are based on the RedHat Enterprise and Fedora source code each modified with reliability, security and efficiency in mind, to fit the tasks assigned to each flavor of StartCom Linux.

==Installation Workaround for RHEL clones==
Installation of current RPMs like fglrx_6_8_0-8.42.3-1.i386.rpm may fail on RHEL clones with this error message:

FATAL: Module fglrx not found.
/var/tmp/rpm-tmp.5182: line 807: [: =: unary operator expected

The problem is that the installation script searches for the string "Red Hat" in /etc/redhat-release. So before installing the RPM simply replace "CentOS" by "Red Hat" in /etc/redhat-release using a text editor. After the RPM has installed successfully I recommend to restore your old /etc/redhat-release. For StartCom Linux create the file /etc/redhat-release with the string "Red Hat" in it. This seems to have been fixed as of CentOS 5.1.

==Red Hat Enterprise Linux 4 Update 3 (RHEL 4.3 and CentOS 4.3)==
The ATI GUI installer worked just fine for me with my Radeon 9700 Pro and CentOS (RHEL) 4.3. ATI claims to "officially" support both RHEL and SUSE, So contrary to the complex install procedure shown on the SUSE pages of this wiki, if you have RHEL, I would go with the simplest approach in the Related Resources link below.
==Red Hat Enterprise Linux 4 Update 6==
The ATI GUI installer on a ThinkPad T60 needed to install kernel-devel and rpm-build
# up2date -f kernel-devel rpm-build
# ./ati-driver-installer-8-4-x86.x86_64.run --listpkg
# ./ati-driver-installer-8-4-x86.x86_64.run --buildpkg RedHat/RHEL4

==Red Hat Enterprise Linux 5.0 (RHEL 5.0 and CentOS 5.0)==
fglrx versions up to and including 8.36.5 require that you install some compatabiliy RPMs.

Here is what I did to get the fglrx driver to run with my FireGX 5150 on CentOS 5.0:

Install ATI driver 8.36.5.

Display all compat-* RPMs if you like:
yum list "compat-*"

Install the compat RPMs. I installed a bunch of them that I need for other reasons:
yum install compat-libstdc -33 compat-glibc compat-gcc-34 compat-readline compat-libf2c
I do not know which if these RPMs are actually needed for fglrx. They appear above ordered from most likely, to least likely to be needed.

As of CentOS 5.1 (and thus, probably, RHEL 5.1) the only compat library required is compat-libstdc++-33. Note that you may need to temporarily disable SELinux (setenforce 0) during the fglrx install or SELinux will block part of the install. I backed out the install (rpm -e), turned off SELinux and re-ran the install so no idea whether it will work if you don't turn off SELinux. Once the install is complete, you can re-enable SELinux with setenforce 1.

The aticonfig program crashes, so you will have to edit /etc/X11/xorg.conf file yourself. All I had to do was change the driver from "vesa" to, "fgrlx":
Section "Device"
Identifier "Videocard0"
Driver "fglrx"
EndSection

As of CentOS 5.1 (and probably RHEL 5.1) this is no longer the case. aticonfig --initial works as expected.

Reboot

A couple of notes to the really good summary above...
You also need the -devel RPMs for most of the packages listed (and a number not). After that I managed to get the aticonf program to not crash by doing:
aticonfig --initial=dual-head --screen-layout=right
You also should add the following to your xorg.conf file:

Section "Extensions"
Option "Composite" "0"
EndSection

However there are still problems with the fgrlx driver. Even after all of this and a reboot fglrxinfo still says the system is using Mesa GLX Indirect rendering. Also the ATI Catalyst Control Center (amdcccle) will now restart X when you try to run it. Basically it is a mess and I think we need to wait until an updated driver comes along for RHEL 5.

The above no longer appears to be the case as of centOS 5.1. I did not need any devel rpms and fglrxinfo shows:

[root@bend ~]# /usr/bin/fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: Radeon X1300/X1550 Series
OpenGL version string: 2.1.7276 Release

== Important Note as of 5/18/2009 ==
None of the above seems to work for an ATI Radeon HD4670 (512 MB) with the Dell S2409W 24" widescreen LCD on a Dell XPS 435MT (core i7-920) running under 64 bit CentOS 5.3 with the latest updates as of 5/18/2009. "Automatic" installation of the ATI Catalyst 9.4 driver seems to run smoothly, fglrxinfo detects and reports the graphics hardware, and aticonfig --initial reports that it saved a backup of xorg.conf. However, restart X11 (or reboot the PC) and what you get is an incomprehensible screen full of big squares peppered with little dots. Alt-R will reboot the PC and allow use of CD 1 to reboot linux in rescue mode, after which the driver's uninstall script works nicely. So no permanent harm seems to be done.

Here is what finally worked on this particular hardware:

First, to save time and effort, as root edit /etc/inittab and change runlevel to 3. Replace this line
id:5:initdefault:
with
# id:5:initdefault:
# for tinkering with display and xorg.conf
# boots to text mode, requires startx to start X
id:3:initdefault:
Then the system will boot to multiuser with text display, and X can be started by startx.

Next, make sure that the required packages have been installed. After reading the installation instructions, I used CentOS 5.3's graphical Package Manager to install the Development Libraries, Gnome Software Development, and X Software Development. Undoubtedly this adds more than the bare minimum, but disk space is cheap and (my) time is not.

I took the path of generating and testing rpms. This made it easy to back out of any drivers that failed to work (and plenty failed)--just ^-Alt-Backspace to break out of X, then at the command line
rpm -e drivername
e.g.
rpm -e fglrx64_7_1_0
and finally make sure that /etc/X11/xorg.conf was restored to a copy of its original form.

'''Caution:''' when testing, one version (8.6) responded to startx by blanking the screen for several seconds, during which the fans in the Dell XPS 435 revved up and stayed revved up. This made me nervous as I imagined the possibility that the video card might overheat (read something about that somewhere on the WWW in connection with a different card and a different driver). I had to repeatedly press ^-Alt-Del and ^-Alt-Backspace to stop it and reboot.

Finally I discovered that the 8.8 version worked with my hardware.

'''Installing the version 8.8 driver'''

The ATI page for the 8.8 version actually placed a file called ati-driver-installer-8-7-x86.x86_64.run on my Desktop. The name suggests that it's 8.7, but I tried it anyway.

As root,
sh ./ati-driver-installer-8-7-x86.x86_64.run
brought up a panel that I used to select "Generate Distribution Specific Driver Package." I selected RedHat/RHEL5_64a (RedHat/RHEL5 for 32 bit). The driver package turned out to be an rpm called fglrx64_7_1_0-8.512-1.x86_64.rpm (fglrx_7_1_0-8.512-1.i386.rpm for 32 bit).

Then I ran
rpm -Uvh fglrx64_7_1_0-8.512-1.x86_64.rpm
and after the installer exited, typed
aticonfig --initial
at the system prompt.

I rebooted, logged in as myself (not root), ran startx, and was relieved to see that the display was in a higher resolution mode, and ATI Catalyst Control Center now appeared in the System / Preferences and System / Administration menus.

Turns out I couldn't run ATI Catalyst Control Center as myself--had to su, then run amdcccle at the command line.

After verifying that all was well, as root I restored the boot runlevel to 5 by editing /etc/inittab again.

Did a bit of tinkering and got the following performance out of glxgears:
720 frames in 5.4 sec = 133 FPS
Doesn't seem too impressive. fgl_glxgears causes a segmentation fault and exits. Dragging windows around the screen, I see a distinct lag between when I drag something and when it finally gets to its location. But at least I'm not looking at a 1200x800 display.

==Tips and Tricks==
If you have SELinux enabled and set to enforcing you may need to change the context of the fglrx_dri.so file for it to load properly:

chcon -t textrel_shlib_t /usr/lib/dri/fglrx_dri.so

Substitute lib with lib64 where appropriate.

==Related Resources==
[http://ati.amd.com/support/drivers/linux/linux-radeon.html Follow link "ATI Driver Installer"]

{{VCT}}
[[Category:Distributions]]
[[Category:NeedsUpdating]]

Ubuntu Dapper Installation Guide

2006-09-06T17:05:50Z

69.0.81.235: /* WARNING: */

In Ubuntu Dapper you can choose between two methods of installing the proprietary ATI driver. If you are new to linux you should use the first method as it is a lot easier than the second one and will work well in most cases. The second method describes how to install the very latest driver version, but requires some additional work and knowledge.

== Method 1: Installing Dapper's Included Driver (8.25.18) ==

The included fglrx driver supports Radeon 8500+ and the X-series cards up to X1900.

Unfortunately OpenGL seems to be broken for R200 cards (everything below Radeon 9500) in this driver version. The [[#Troubleshooting for Method 1|Troubleshooting]] section describes how to fix this '''after''' xorg-driver-fglrx is installed.

=== Installing the driver ===

Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

Help on enabling repositories can be found at https://help.ubuntu.com/community/Repositories/Ubuntu.

<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Now Reboot your system:

<pre>
sudo shutdown -r now
</pre>

An '''alternative''' to the '''aticonfig --initial''' command is to edit ''/etc/X11/xorg.conf'' and replace the string "ati" with "fglrx" in the "Device" section. This way you won't lose your old "Screen" and "Monitor" settings. Afterwards you can use aticonfig for setting overlay etc.

=== Confirm that it works ===
<pre>
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)
</pre>

=== Troubleshooting for Method 1 ===

*The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors. You should really include this when you are asking for help somewhere.

* Unfortunately OpenGL seems to be broken for R200 cards (everything below Radeon 9500) in this driver version which results in messages like
:<pre>[fglrx] API ERROR: could not register entrypoint for Uniform2iARB</pre>
:and similar when running OpenGL applications. This may be fixed by replacing ''/usr/lib/libGL.so.1.2'' with ''libGL.so.1.2'' from the previous driver version (8.24.8). To do so download this file: [http://files.covertprestige.info/important/libGL.so.1.2 libGL.so.1.2] and then copy it to the ''/usr/lib/'' directory.

*It might be necessary to create a symlink to get accelerated OpenGL:
:<pre>sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri</pre>

*AMD64 users: It may also be necessary to update /etc/profile if using GDM. Update the $LIBGL_DRIVERS_PATH variable to point to the dri path above.

*To ensure you automatically get the current ''linux-restricted-modules'' package with kernel updates, you should install the linux-restricted-modules-??? package matching your kernel-type (without version numer), e.g. ''linux-restricted-modules-386'', ''linux-restricted-modules-686'' or ''linux-restricted-modules-k7''.

*If you used Method 2 before, you have to unblacklist fglrx again by editing ''/etc/default/linux-restricted-modules-common''

*If the screen is coming up blank on startup, start in recovery mode then try editing your /etc/X11/xorg.conf file to remove this line
: <pre>Load "extmod"</pre>
: and optionally replace it with this
<pre>SubSection "extmod"
Option "omit XVideo"
Option "omit XVideo-MotionCompensation"
Option "omit XFree86-VidModeExtension"
EndSubSection</pre>

*See [[#Troubleshooting for both Methods|Troubleshooting for both Methods]]

 

== Method 2: Generating/Installing Ubuntu packages for the 8.28.8 drivers in Ubuntu Dapper Manually ==

'''Important Change:''' Installation of this driver '''no longer requires''' removing the linux-restricted-modules package in order to work. There is a new blacklist feature in Ubuntu Dapper that you can use to go around this.

=== Blacklist old fglrx module from linux-restricted-modules ===
As ubuntu's ''linux-restricted-modules'' package includes the fglrx module from an old driver version (8.25.18), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.

<pre>sudo gedit /etc/default/linux-restricted-modules-common</pre>
Edit ''DISABLED_MODULES'' to include fglrx
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

== WARNING: == This blacklist method is incompatible with the '''xorg-driver-fglrx''' drivers from the Ubuntu apt repositories. If both are used, the system will boot with the Mesa 3d drivers, even if xorg.conf specifies to use the fglrx driver. See this post[http://ubuntuforums.org/showpost.php?p=1461583&postcount=20] for more information.

Remember to remove the blacklist before installing the package '''xorg-driver-fglrx''' with apt-get.

=== Installing the new driver ===

Download the ATI driver installer: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.28.8.run ati-driver-installer-8.28.8.run] (this installer is for 32bit '''and''' 64bit systems)

This guide refers to the 32bit version of the driver. The installation procedure for 64bit should be the same as for 32bit, except some filenames will differ slightly.

Change to the download directory. Make sure that you have the ''universe'' and ''multiverse'' repositories enabled in ''/etc/apt/sources.list'' before doing these steps.

''Install necessary tools:''

<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential
sudo apt-get install fakeroot dh-make debconf libstdc++5 linux-headers-$(uname -r)
</pre>

''Create .deb packages:''

<pre>
bash ati-driver-installer-8.28.8.run --buildpkg Ubuntu/dapper
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.28.8-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.28.8-1_i386.deb
sudo dpkg -i fglrx-control_8.28.8-1_i386.deb
</pre>

''Remove any old fglrx debs from /usr/src/:''

<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Compile the kernel module:''

<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a
</pre>

'''Note''': You have to recompile the kernel module after each kernel update!

''Update the xorg.conf file:''

<pre>
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

''Reboot:''

<pre>
sudo shutdown -r now
</pre>

=== Confirm that it worked ===

<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

=== Troubleshooting for Method 2===

==== Problems with module-assistant ====

If module-assistant is unable to build the module you may have to provide a Makefile.cpu file:
<pre>
cd /usr/src
sudo touch kernel-headers-(version)/arch/i386/Makefile.cpu
cd /usr/src/linux
sudo make scripts/
</pre>

==== xorg.conf ====

The '''aticonfig --initial''' command will not update the xorg.conf file if it already has a "fglrx" Device section.
However, you may force aticonfig to generate default Monitor, Device, and Screen sections with the following command:

<pre>
sudo aticonfig --force --initial
</pre>

==== Upgrade from Breezy ====
If method 2 doesn't work first time round, and you have upgraded from a Breezy installation, try this:

Remove previous versions of the fglrx driver:
<pre>
sudo dpkg -r fglrx-control
sudo dpkg -r fglrx-kernel-source
sudo dpkg -r xorg-driver-fglrx
</pre>

dpkg will list dependencies for xorg-driver-fglrx which will need up be removed, for example:

<pre>
sudo dpkg -r fglrx-kernel
sudo dpkg -r fglrx-kernel-2.6.12-10-686-smp
sudo dpkg -r xorg-driver-fglrx
</pre>

Proceed with method 2

 

== Troubleshooting for both Methods ==

=== General ===

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

=== 2D speed ===

If you suffer from slow 2D speed it might help to set
Option "XaaNoOffscreenPixmaps"
in the fglrx section of ''/etc/X11/xorg.conf''

=== Is the rebooting really necessary? ===

No.

However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.

=== HP Notebook dv5029us / dv5040us / zv6000 / dv8000 ===

If you have an HP Notebook Computer (or Compaq) such as the HP dv5029us, dv5040us or zv6000 series, it is needed to modify the BIOS configuration. It seems for some reason using sideport memory (the card's onboard memory only) leads to an apparent system crash although the logs show successful initialization of DRI. It is needed to run the BIOS setup screen, go to memory options, and select UMA+Sideport memory and assign a value to it (I assigned an extra 128M from the system RAM). Boot the computer and the fglrx driver will work. FGLRX version is 8.24.8 on an i386 Ubuntu Dapper install.

* Ubuntu FGLRX drivers 8.25.18, do not work properly on the dv5029us (Radeon Xpress 200M) as of this writing (5/30/2006). It is needed to revert to 8.24.8 for this specific computer in order to get proper 3D acceleration, and 2D with no tearing off.

** ATI Driver 8.26.18, does not work with the Radeon Express 200M. Some HP/Compaq laptops only have working 3D support with ONLY UMA video memory( Sideport+UMA won't work ). This is due to a 1 year old flaw in the ATI driver. If you want to use your onboard/Sideport memory, you can only get 2D support by adding [ Option "no_dri" "yes"] to the fglrx driver section of /etc/X11/xorg.conf

* jul-22-2006, marciowb wrote: I have a HP Pavilion zv6000 - a notebook computer with AMD64 - and it have a ATI Radeon Xpress 200M with 128MB of dedicated memory (Sideport) and it accepts to use shared memory (UMA), also. But if I try to use Sideport or Sideport+UMA the 3D acceleration fails and/or my computer hangs. It works fine if I configure its BIOS to use only UMA, including with a good 3D acceleration performance. Configured to use only UMA it works with the ATI Driver 8.26.18 and 8.25.18, but I was unable to do it works the ATI Driver 8.24.8. I tried several times to use 8.24.8 but it doesn't seem to work with 3D acceleration, only 2D. I see the Xorg.log file the fglrx driver fails to load the DRI driver. I used the Kubuntu with the Linux kernel 2.6.15-26-amd64-generic.

* aug-7-2006, mde wrote: I have an HP dv8120ca / dv8000 laptop with a Radeon Xpress 200M. After installing the 8.27.10 driver, no matter what I set the bios to (128 UMA+Sideport or just Sideport, UMA Only is not an option in my bios), I get the black screen/99% cpu usage problem. I have tried to contact ATI to complain about this bug... Their response: "ATI does not provide direct technical support for laptops/notebooks at this current time (telephone or email). If you require direct technical support please contact the system manufacturer of your laptop/notebook.". To contact ati's linux driver feedback team and request they fix the problem, go to [[https://support.ati.com/ics/support/KBAnswer.asp?questionID=1714 https://support.ati.com/ics/support/KBAnswer.asp?questionID=1714]]. I have written a template letter you can use for your submission should you so desire. It is available at [[http://www.rhthm.com/ati/index.html http://www.rhthm.com/ati/index.html]].

=== HP zt3000 / Compaq nx7000 ===
Beginning with ATI driver version 8.19, the drivers fail to properly detect modelines that are compatible with the LCD screen of the HP zt3000 (and equivalent Compaq nx7000 model), and they must be inserted into xorg.conf manually. For the 1680x1050 LCD screen, inserting the following modelines into the "Monitor" section works:
Modeline "640x350" 119.12 640 1728 1760 1840 350 1052 1058 1080
Modeline "640x400" 119.12 640 1728 1760 1840 400 1052 1058 1080
Modeline "720x400" 119.12 720 1728 1760 1840 400 1052 1058 1080
Modeline "640x480" 119.12 640 1728 1760 1840 480 1052 1058 1080
Modeline "800x600" 119.12 800 1728 1760 1840 600 1052 1058 1080
Modeline "1024x768" 119.12 1024 1728 1760 1840 768 1052 1058 1080
Modeline "1152x864" 119.12 1152 1728 1760 1840 864 1052 1058 1080
Modeline "1280x960" 119.12 1280 1728 1760 1840 960 1052 1058 1080
Modeline "1280x1024" 119.12 1280 1728 1760 1840 1024 1052 1058 1080
Modeline "832x624" 119.12 832 1728 1760 1840 624 1052 1058 1080
Modeline "1280x768" 119.12 1280 1728 1760 1840 768 1052 1058 1080
Modeline "1280x800" 119.12 1280 1728 1760 1840 800 1052 1058 1080
Modeline "1152x768" 119.12 1152 1728 1760 1840 768 1052 1058 1080
Modeline "1400x1050" 119.12 1400 1728 1760 1840 1050 1052 1058 1080
Modeline "1440x900" 119.12 1440 1728 1760 1840 900 1052 1058 1080
Modeline "1600x1024" 119.12 1600 1728 1760 1840 1024 1052 1058 1080
Modeline "1680x1050" 119.12 1680 1728 1760 1840 1050 1052 1058 1080

If you have the "1920x1200" version of the HP zt3000 the Modeline is:
Modeline "1920x1200" 150.75 1920 2016 2048 2185 1200 1202 1208 1235

If you have the "1280x800" version of the HP zt3000 the Modeline should be:
ModeLine "1280x800" 69.8 1280 1336 1368 1440 800 802 808 823 -hsync -vsync

** If the above ModeLine still makes the screen flicker (as it did in my zt3000) use the following ModeLine
ModeLine "1280x800" 70.875 1280 1336 1368 1440 800 802 808 823 -hsync +vsync

If you have the compaq nx7010 with 1280x800 screen then the following modeline should work:
Modeline "1280x800" 70.875 1280 1320 1352 1456 800 801 804 820 +hsync +vsync
This was determined using powerstrip in windows.

When using a Compaq NX7010 (Radeon R250Lf Mobility M9) with 1650x1050 screen, powerstrip gives the following working params (CApiTAlisation important), just use one single ModeLine:
ModeLine "1650x1050" 121.500 1680 1712 1800 1872 1050 1051 1054 1065 +Hsync +Vsync
On the Compaq NX7010, be sure to copy the 8.24.8 libGL.so.1.2 as in Troubleshooting for Method 1 above.

''Note: This line will also work on the Compaq X1000 series''

=== Revert to Xorg driver ===

If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
<pre>sudo dpkg-reconfigure xserver-xorg</pre>
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.

You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:

<pre>sudo apt-get install --reinstall libgl1-mesa</pre>

Ubuntu Dapper Installation Guide

2006-09-06T17:01:12Z

69.0.81.235: /* Blacklist old fglrx module from linux-restricted-modules */

In Ubuntu Dapper you can choose between two methods of installing the proprietary ATI driver. If you are new to linux you should use the first method as it is a lot easier than the second one and will work well in most cases. The second method describes how to install the very latest driver version, but requires some additional work and knowledge.

== Method 1: Installing Dapper's Included Driver (8.25.18) ==

The included fglrx driver supports Radeon 8500+ and the X-series cards up to X1900.

Unfortunately OpenGL seems to be broken for R200 cards (everything below Radeon 9500) in this driver version. The [[#Troubleshooting for Method 1|Troubleshooting]] section describes how to fix this '''after''' xorg-driver-fglrx is installed.

=== Installing the driver ===

Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

Help on enabling repositories can be found at https://help.ubuntu.com/community/Repositories/Ubuntu.

<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Now Reboot your system:

<pre>
sudo shutdown -r now
</pre>

An '''alternative''' to the '''aticonfig --initial''' command is to edit ''/etc/X11/xorg.conf'' and replace the string "ati" with "fglrx" in the "Device" section. This way you won't lose your old "Screen" and "Monitor" settings. Afterwards you can use aticonfig for setting overlay etc.

=== Confirm that it works ===
<pre>
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)
</pre>

=== Troubleshooting for Method 1 ===

*The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors. You should really include this when you are asking for help somewhere.

* Unfortunately OpenGL seems to be broken for R200 cards (everything below Radeon 9500) in this driver version which results in messages like
:<pre>[fglrx] API ERROR: could not register entrypoint for Uniform2iARB</pre>
:and similar when running OpenGL applications. This may be fixed by replacing ''/usr/lib/libGL.so.1.2'' with ''libGL.so.1.2'' from the previous driver version (8.24.8). To do so download this file: [http://files.covertprestige.info/important/libGL.so.1.2 libGL.so.1.2] and then copy it to the ''/usr/lib/'' directory.

*It might be necessary to create a symlink to get accelerated OpenGL:
:<pre>sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri</pre>

*AMD64 users: It may also be necessary to update /etc/profile if using GDM. Update the $LIBGL_DRIVERS_PATH variable to point to the dri path above.

*To ensure you automatically get the current ''linux-restricted-modules'' package with kernel updates, you should install the linux-restricted-modules-??? package matching your kernel-type (without version numer), e.g. ''linux-restricted-modules-386'', ''linux-restricted-modules-686'' or ''linux-restricted-modules-k7''.

*If you used Method 2 before, you have to unblacklist fglrx again by editing ''/etc/default/linux-restricted-modules-common''

*If the screen is coming up blank on startup, start in recovery mode then try editing your /etc/X11/xorg.conf file to remove this line
: <pre>Load "extmod"</pre>
: and optionally replace it with this
<pre>SubSection "extmod"
Option "omit XVideo"
Option "omit XVideo-MotionCompensation"
Option "omit XFree86-VidModeExtension"
EndSubSection</pre>

*See [[#Troubleshooting for both Methods|Troubleshooting for both Methods]]

 

== Method 2: Generating/Installing Ubuntu packages for the 8.28.8 drivers in Ubuntu Dapper Manually ==

'''Important Change:''' Installation of this driver '''no longer requires''' removing the linux-restricted-modules package in order to work. There is a new blacklist feature in Ubuntu Dapper that you can use to go around this.

=== Blacklist old fglrx module from linux-restricted-modules ===
As ubuntu's ''linux-restricted-modules'' package includes the fglrx module from an old driver version (8.25.18), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.

<pre>sudo gedit /etc/default/linux-restricted-modules-common</pre>
Edit ''DISABLED_MODULES'' to include fglrx
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

== WARNING: == Switching to the repository-provided '''xorg-driver-fglrx''' package after using this blacklist method may cause the system to hang at a black screen when starting X. This problem has been seen in Ubuntu Edgy by at least two users. See this post[http://ubuntuforums.org/showpost.php?p=1461583&postcount=20] for more information.

Remember to remove the blacklist before installing the package '''xorg-driver-fglrx''' with apt-get. If you get the black screen at startup, then boot into Recovery Mode and remove the blacklist from /etc/default/linux-restricted-modules-common before rebooting.

=== Installing the new driver ===

Download the ATI driver installer: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.28.8.run ati-driver-installer-8.28.8.run] (this installer is for 32bit '''and''' 64bit systems)

This guide refers to the 32bit version of the driver. The installation procedure for 64bit should be the same as for 32bit, except some filenames will differ slightly.

Change to the download directory. Make sure that you have the ''universe'' and ''multiverse'' repositories enabled in ''/etc/apt/sources.list'' before doing these steps.

''Install necessary tools:''

<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential
sudo apt-get install fakeroot dh-make debconf libstdc++5 linux-headers-$(uname -r)
</pre>

''Create .deb packages:''

<pre>
bash ati-driver-installer-8.28.8.run --buildpkg Ubuntu/dapper
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.28.8-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.28.8-1_i386.deb
sudo dpkg -i fglrx-control_8.28.8-1_i386.deb
</pre>

''Remove any old fglrx debs from /usr/src/:''

<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Compile the kernel module:''

<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a
</pre>

'''Note''': You have to recompile the kernel module after each kernel update!

''Update the xorg.conf file:''

<pre>
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

''Reboot:''

<pre>
sudo shutdown -r now
</pre>

=== Confirm that it worked ===

<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

=== Troubleshooting for Method 2===

==== Problems with module-assistant ====

If module-assistant is unable to build the module you may have to provide a Makefile.cpu file:
<pre>
cd /usr/src
sudo touch kernel-headers-(version)/arch/i386/Makefile.cpu
cd /usr/src/linux
sudo make scripts/
</pre>

==== xorg.conf ====

The '''aticonfig --initial''' command will not update the xorg.conf file if it already has a "fglrx" Device section.
However, you may force aticonfig to generate default Monitor, Device, and Screen sections with the following command:

<pre>
sudo aticonfig --force --initial
</pre>

==== Upgrade from Breezy ====
If method 2 doesn't work first time round, and you have upgraded from a Breezy installation, try this:

Remove previous versions of the fglrx driver:
<pre>
sudo dpkg -r fglrx-control
sudo dpkg -r fglrx-kernel-source
sudo dpkg -r xorg-driver-fglrx
</pre>

dpkg will list dependencies for xorg-driver-fglrx which will need up be removed, for example:

<pre>
sudo dpkg -r fglrx-kernel
sudo dpkg -r fglrx-kernel-2.6.12-10-686-smp
sudo dpkg -r xorg-driver-fglrx
</pre>

Proceed with method 2

 

== Troubleshooting for both Methods ==

=== General ===

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

=== 2D speed ===

If you suffer from slow 2D speed it might help to set
Option "XaaNoOffscreenPixmaps"
in the fglrx section of ''/etc/X11/xorg.conf''

=== Is the rebooting really necessary? ===

No.

However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.

=== HP Notebook dv5029us / dv5040us / zv6000 / dv8000 ===

If you have an HP Notebook Computer (or Compaq) such as the HP dv5029us, dv5040us or zv6000 series, it is needed to modify the BIOS configuration. It seems for some reason using sideport memory (the card's onboard memory only) leads to an apparent system crash although the logs show successful initialization of DRI. It is needed to run the BIOS setup screen, go to memory options, and select UMA+Sideport memory and assign a value to it (I assigned an extra 128M from the system RAM). Boot the computer and the fglrx driver will work. FGLRX version is 8.24.8 on an i386 Ubuntu Dapper install.

* Ubuntu FGLRX drivers 8.25.18, do not work properly on the dv5029us (Radeon Xpress 200M) as of this writing (5/30/2006). It is needed to revert to 8.24.8 for this specific computer in order to get proper 3D acceleration, and 2D with no tearing off.

** ATI Driver 8.26.18, does not work with the Radeon Express 200M. Some HP/Compaq laptops only have working 3D support with ONLY UMA video memory( Sideport+UMA won't work ). This is due to a 1 year old flaw in the ATI driver. If you want to use your onboard/Sideport memory, you can only get 2D support by adding [ Option "no_dri" "yes"] to the fglrx driver section of /etc/X11/xorg.conf

* jul-22-2006, marciowb wrote: I have a HP Pavilion zv6000 - a notebook computer with AMD64 - and it have a ATI Radeon Xpress 200M with 128MB of dedicated memory (Sideport) and it accepts to use shared memory (UMA), also. But if I try to use Sideport or Sideport+UMA the 3D acceleration fails and/or my computer hangs. It works fine if I configure its BIOS to use only UMA, including with a good 3D acceleration performance. Configured to use only UMA it works with the ATI Driver 8.26.18 and 8.25.18, but I was unable to do it works the ATI Driver 8.24.8. I tried several times to use 8.24.8 but it doesn't seem to work with 3D acceleration, only 2D. I see the Xorg.log file the fglrx driver fails to load the DRI driver. I used the Kubuntu with the Linux kernel 2.6.15-26-amd64-generic.

* aug-7-2006, mde wrote: I have an HP dv8120ca / dv8000 laptop with a Radeon Xpress 200M. After installing the 8.27.10 driver, no matter what I set the bios to (128 UMA+Sideport or just Sideport, UMA Only is not an option in my bios), I get the black screen/99% cpu usage problem. I have tried to contact ATI to complain about this bug... Their response: "ATI does not provide direct technical support for laptops/notebooks at this current time (telephone or email). If you require direct technical support please contact the system manufacturer of your laptop/notebook.". To contact ati's linux driver feedback team and request they fix the problem, go to [[https://support.ati.com/ics/support/KBAnswer.asp?questionID=1714 https://support.ati.com/ics/support/KBAnswer.asp?questionID=1714]]. I have written a template letter you can use for your submission should you so desire. It is available at [[http://www.rhthm.com/ati/index.html http://www.rhthm.com/ati/index.html]].

=== HP zt3000 / Compaq nx7000 ===
Beginning with ATI driver version 8.19, the drivers fail to properly detect modelines that are compatible with the LCD screen of the HP zt3000 (and equivalent Compaq nx7000 model), and they must be inserted into xorg.conf manually. For the 1680x1050 LCD screen, inserting the following modelines into the "Monitor" section works:
Modeline "640x350" 119.12 640 1728 1760 1840 350 1052 1058 1080
Modeline "640x400" 119.12 640 1728 1760 1840 400 1052 1058 1080
Modeline "720x400" 119.12 720 1728 1760 1840 400 1052 1058 1080
Modeline "640x480" 119.12 640 1728 1760 1840 480 1052 1058 1080
Modeline "800x600" 119.12 800 1728 1760 1840 600 1052 1058 1080
Modeline "1024x768" 119.12 1024 1728 1760 1840 768 1052 1058 1080
Modeline "1152x864" 119.12 1152 1728 1760 1840 864 1052 1058 1080
Modeline "1280x960" 119.12 1280 1728 1760 1840 960 1052 1058 1080
Modeline "1280x1024" 119.12 1280 1728 1760 1840 1024 1052 1058 1080
Modeline "832x624" 119.12 832 1728 1760 1840 624 1052 1058 1080
Modeline "1280x768" 119.12 1280 1728 1760 1840 768 1052 1058 1080
Modeline "1280x800" 119.12 1280 1728 1760 1840 800 1052 1058 1080
Modeline "1152x768" 119.12 1152 1728 1760 1840 768 1052 1058 1080
Modeline "1400x1050" 119.12 1400 1728 1760 1840 1050 1052 1058 1080
Modeline "1440x900" 119.12 1440 1728 1760 1840 900 1052 1058 1080
Modeline "1600x1024" 119.12 1600 1728 1760 1840 1024 1052 1058 1080
Modeline "1680x1050" 119.12 1680 1728 1760 1840 1050 1052 1058 1080

If you have the "1920x1200" version of the HP zt3000 the Modeline is:
Modeline "1920x1200" 150.75 1920 2016 2048 2185 1200 1202 1208 1235

If you have the "1280x800" version of the HP zt3000 the Modeline should be:
ModeLine "1280x800" 69.8 1280 1336 1368 1440 800 802 808 823 -hsync -vsync

** If the above ModeLine still makes the screen flicker (as it did in my zt3000) use the following ModeLine
ModeLine "1280x800" 70.875 1280 1336 1368 1440 800 802 808 823 -hsync +vsync

If you have the compaq nx7010 with 1280x800 screen then the following modeline should work:
Modeline "1280x800" 70.875 1280 1320 1352 1456 800 801 804 820 +hsync +vsync
This was determined using powerstrip in windows.

When using a Compaq NX7010 (Radeon R250Lf Mobility M9) with 1650x1050 screen, powerstrip gives the following working params (CApiTAlisation important), just use one single ModeLine:
ModeLine "1650x1050" 121.500 1680 1712 1800 1872 1050 1051 1054 1065 +Hsync +Vsync
On the Compaq NX7010, be sure to copy the 8.24.8 libGL.so.1.2 as in Troubleshooting for Method 1 above.

''Note: This line will also work on the Compaq X1000 series''

=== Revert to Xorg driver ===

If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
<pre>sudo dpkg-reconfigure xserver-xorg</pre>
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.

You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:

<pre>sudo apt-get install --reinstall libgl1-mesa</pre>