cchtml.com - User contributions [en]

HP

2008-12-17T03:01:55Z

80.90.160.194: FIELD_OTHER

FIELD_MESSAGE_rozelze

===Desktops===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|HP A1629.uk Pavilion
|ATI Radeon Xpress 200
|Unknown
|-
|HP t5735 Thin Client
|ATI Radeon X1250
|Works
|Debian 4.x
|}

===Laptops===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|Pavilion L2005cu
|XPRESS 200M
|Works
|-
|Pavilion zv6000
| XPRESS 200M 5955
|Works
|Fedora 7
|Driver 8.24.8 is known to work, 8.25.18 and 8.26.18 are broken. You have to enable Sideport UMA and assign 128MB of memory as the chipset always reports it is equipped with 256MB no matter what you configure it to. Driver 8.40.4 works, but cannot suspend to ram or hibernate.
|-
|Special Edition L2000
| XPRESS 200M 5955
|Works
|-
|Compaq nx8220
| Ati X600
|Works
|-
|HP nw8240
| Mobility Radeon X700
|Works*
|Ubuntu 08.04 (Hardy Heron)
|fglrx v8.50.3 works fine. Suspend/Resume works if not using Compiz. For Compiz issue, see: [http://ati.cchtml.com/show_bug.cgi?id=960 Bug #960]
--[[User:Deragon|deragon]] 01:21, 15 July 2008 (CDT)

Old comment:

Tested under SUSE Factory with xorg 7.2, fglrx module/driver v8.35.5 patched to build with kernel 2.6.20 -- still can't get suspend-to-ram (s3) to work properly. OpenGL acceleration works fine at 1920x1600px but Google Earth caused a system hang, which I'll try to fix using fglrx v8.36 and changing settings with Catalyst.
|-
|HP nc6400
| Ati X1300
|Works
|Gentoo
|Tested under xorg 7.1 with xgl/beryl
|-
|HP nc8230
|Radeon Mobility X600
|Works
|Debian/GNU unstable
|Tested under Debian/GNU unstable under xorg 7.2-5, kernel 2.6.18-3-686-bigmem and running the ATI-supplied installation package v8.38.6. Works fine, haven't verified TV-out et al, but running dual x-servers (dual-head with diffrent resolutions) works fine.
|-
|HP nw8440
|Radeon Mobility X1600
|Works
|Ubuntu 7.04
|
|-
|HP nw8440
|Radeon Mobility X1600
|Total failure
|Fedora 9
|
|-
|Compaq 8510p
|Radeon HD 2600
|Does not build RPMs anymore
|Fedora 9 (2008/11/16)
|Build process produces some files that are not included or ignored, so RPM package building fails. Tested with ATI Radeon driver 8.11.
|
|-
|HP nx6125
|XPRESS 200M 5955
|Works
|
* Gentoo
* Debian Etch
* Ubuntu 7.10
|
Hibernate (RAM), Vanilla-Kernel-suspend (disk) & TV-Out work out of the box (Kernel 2.6.23 & 8.42.3). Good OpenGL performance (even with compiz-fusion/AIGLX). 
LCD-brightness can only be changed in VT (Ctrl+Alt+F1 -> change brightness -> switch back to X works).
|-
|Compaq Presario R4125US
|XPRESS 200M 5955
|Works
|Kubuntu 8.04
|Working under Kubuntu 8.04 Hardy Heron. Xorg 7.3 Kernel 2.6.24-19. Driver version 8.51.3 manually extracted. Logout hangs till you issue the command: sudo /usr/sbin/update-rc.d -f atieventsd remove. Afterward no logout hangs. Haven't tested Suspend/Hibernate as I don't use these functions.
|-
|}

FIELD_MESSAGE_sitmonliri

Ubuntu Edgy Installation Guide

2008-12-17T01:13:14Z

80.90.160.194: FIELD_OTHER

In Ubuntu Edgy 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.

FIELD_MESSAGE_catrocrol

== Method 2: Generating/Installing Ubuntu packages for the new 8.30.3 drivers in Ubuntu Edgy Manually ==

The new fglrx driver supports Radeon '''9'''500+ (older cards will not work!) and the X-series cards up to X1900.

=== Disable Composite Extension ===

In Ubuntu Edgy the Composite extension is enabled by default, however, ''fglrx'' does not yet support Composite with DRI. In order to to disable Composite you have to edit the ''xorg.conf'' file:
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add these lines at the end of the file:
{{Box File|/etc/X11/xorg.conf|
<pre>Section "Extensions"
Option "Composite" "Disable"
EndSection</pre>
}}

=== 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.28.8), 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>
}}

=== 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.30.3.run ati-driver-installer-8.30.3.run] (this installer is for 32bit '''and''' 64bit systems)

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>
sudo ln -sf bash /bin/sh
bash ati-driver-installer-8.30.3.run --buildpkg Ubuntu/edgy
sudo ln -sf dash /bin/sh
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.30.3-1*.deb
sudo dpkg -i fglrx-kernel-source_8.30.3-1*.deb
sudo dpkg -i fglrx-control_8.30.3-1*.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>

'''IMPORTANT''': 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>

'''Note:'''
You could also edit your ''/usr/X11/xorg.conf'' file to change your driver to '''fglrx''' then run:

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

This way your ''xorg.conf'' file will stay clean.

''Now 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.6119 (8.30.3)
</pre>

<pre>
$ glxinfo | grep render
direct rendering: Yes
</pre>

If your direct rendering is disabled, you may have to symlink the dri folder:

<pre>
sudo mkdir /usr/X11R6/lib/modules
sudo ln -s /usr/lib/dri /usr/X11R6/lib/modules/
</pre>

=== Troubleshooting for Method 2===

==== 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>

 

=== The module compiles, but doesn't work ===
For some reason fglrx may need gcc-4.0 to compile, if you experience some message related to gcc version in dmesg, try this:

First we'll install it

<pre>
sudo apt-get install gcc-4.0
</pre>

and link it to gcc.

<pre>
sudo ln -sf /usr/bin/gcc-4.0 /usr/bin/gcc
</pre>

After doing the module-assistant steps, you may want to return gcc to 4.1 by default:

<pre>
sudo ln -sf /usr/bin/gcc-4.1 /usr/bin/gcc
</pre>

== Troubleshooting for both Methods ==

=== General ===

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

=== DRI does not work although the fglrx module is loaded ===

If fglrxinfo shows:
<pre>
OpenGL vendor string: Mesa project: www.mesa3d.org
</pre>

Make sure the Composite extension is disabled, add this to your /etc/X11/xorg.conf file:
<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection
</pre>

This should also resolve the corrupted mouse cursor problem in dual-head mode.

=== Module isn't loaded ===
If the fglrx module isn't loaded try to add ''fglrx'' to /etc/modules on a new line. See also [https://launchpad.net/distros/ubuntu/+bug/63912 bug 63912].

{{Box File|/etc/modules|
<pre>
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

fglrx
</pre>
}}

=== 2D speed ===

If you suffer from slow 2D speed it might help to set
Option "XaaNoOffscreenPixmaps"
in the fglrx device 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.

Note: if ''modprobe fglrx'' can't find the ''fglrx'' module, try rebuilding your kernel module dependency:

<pre>
sudo depmod -a
</pre>

=== 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>

TurboLinux

2008-12-16T23:27:27Z

80.90.160.194: FIELD_OTHER

FIELD_MESSAGE_chipasda

Troubleshooting

2008-12-16T20:17:11Z

80.90.160.194: FIELD_OTHER

==X Server Related Issues==

=== No high-resolution video modes available ===
* Versions of the fglrx driver following 7.12 had problems with video resolutions higher than 1280 x 1024. The modes of the xorg.conf are simply ignored, and the server starts up e.g. with a resolution 1280 x 1024 (even if this resolution is not defined in xorg.conf). This is particularly a problem on LCD displays.
* [http://ati.cchtml.com/show_bug.cgi?id=160 This bug] documents the problem; it is '''fixed''' since driver version 8.2

=== No XVideo support on 690G integrated graphic chipset ===
*Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.
*Motherboard using the 690G IGP chipset don't have XVideo support. When you execute the "xvinfo" command you get "no adaptors present". This is the case by using the 8.39.4 FGLRX driver and whenever the "sudo aticonfig --overlay-type=Xv" command or the "sudo aticonfig --overlay-type=opengl" was used. ATI seem to know this as there list TVtime as an application unable to run on a 690G chip.
* XVideo works with 8-1 release (version 8.45.4). You need to change the defaults in /etc/ati/amdpcsdb (created by amdcccle, loaded by X on start, and saved on exit). With X shutdown, set VideoOverlay=Son, OpenGLOverlay=Soff, and Textured2D=STrue. (Don't use aticonfig or xorg.conf to set these. At this time, aticonfig and amdccle don't change these settings, and /etc/ati/amdpcsdb seems to override xorg.conf) (Verified on Asus M2A-VM with BIOS 1501)
* With 8-3 release (8.47.1), to get XVideo working I added ''Option "TexturedVideo" "true"'' to the xorg.conf file. It wasn't necessary to edit the /etc/ati/amdpcsdb file as described in the paragraph above; the open GL overlay can be active and it will still work.

=== System lockup on logout or switch to virtual consoles ===

If your system locks up after you logout or when you try to switch to a virtual console, this might be an instance of [http://ati.cchtml.com/show_bug.cgi?id=330 this bug]. It is likely that the problem only occurs for users with an '''Xorg version of at least 7.0'''. Probably it only affects users of '''DVI'''.

There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.

This workaround was posted as a comment to another related bug: see [http://ati.cchtml.com/show_bug.cgi?id=239#c48 here].
---------
Unfortunately "D-sub" users (like me) have the same problem.

=== BigDesktop (Dual screen) doesn't work after GDM login screen ===

This can occur on Ubuntu Feisty Fawn & Gutsy.

System > Prefrences > Screen Resolution

Select the resolution that is a combination of both screen resolutions wide and your height.

If X crashes during login, go to a virtual console using Ctrl+Alt+F1, log in, <code>sudo vim /etc/X11/xorg.conf</code>, and comment out the line which looks like the following:
{{Box File|/etc/X11/xorg.conf|
<pre> Option "DesktopSetup" "something"</pre>
}}

FIELD_MESSAGE_boceltaca

=== Graphical Anomalies ===

This was experienced with an ATI Radeon X1600 Pro 512mb:

After following instructions for both Method 1 and Method 2, whenever the Composite Extension is disabled, the display would be almost unusable, but the fglrxinfo command would display the correct information. If the Composite Extension is re-enabled the display would be usable, but fglrxinfo would report using mesa drivers.

To resolve the problem it maybe needed to lower the AGP Aperture setting in my BIOS to 128mb (or lower worked too). The AGP Aperture was initially set to 256mb. After setting the AGP Aperture to 128mb, everything worked perfectly; the Composite Extension is disabled, fglrxinfo reports the correct drivers, and direct rendering is enabled. Some systems may require setting the AGP Aperture to the highest setting (256mb or 512mb).

There's been a bug report regarding [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/150627 anomalies in Firefox] as well.

=== OpenGL framebuffer Corruption ===

This problem has been experienced on Thinkpads (T60p) with an ATI MOBILITY FireGL V5250 running driver versions 7.12, 8.01 and 8.02. Whenever any OpenGL application is rendered, the rendered output appears "scrambled" and unreadable. This problem is not very well documented and both glxgears and fgl_glxgears display this anomaly when testing.

When Anti-Aliasing is forced, the problem resides.

A solution (tested with 8.02 on Ubuntu Gutsy) to this problem is to open the ATI/AMD Catalyst Control Center and expand the item labeled '3D' in the options tree on the left-hand side of the window. From there, select "Anti-Aliasing" and check the box which reads: "Override application setting". Apply the settings and close the control center.

For an example of this anomaly, please see [http://i31.tinypic.com/244z9z8.png this image]

This solution not work on acer laptop with ATI Mobility Radeon HD 2400 XT.
kepfeltoltes.hu/view/080302/atisux_www.kepfeltoltes.hu_.jpg

=== Blank Screen with Xorg 1.3.0 ===
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:
{{Box File|/var/log/Xorg.log|
<nowiki>
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...]
4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]
</nowiki>
}}

Then you're probably using the ati-drivers with Xorg-1.3.0. If that's the case the only solution (known to me) is to use a version < 1.3.0.

Edit: I got the same problem after using the --add-pairmode argument of aticonfig (using Xorg 1.3.0). My ati mobility x300 seemes to try
sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor
signal sometimes returnes to the internal laptop monitor.
By switching to a console or shutting down the X-server, the card switches back to vga...

My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb)
and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now
work fine again with Xorg-1.3.0 .

=== Radeon GPU fan is very loud / constantly works ===
:See [http://ati.cchtml.com/show_bug.cgi?id=499 bug 499] for additional information.
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively
even when not in 3D mode. This behaviour will cause the cards' fans to function on full
blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source
"radeon" driver does not exhibit this problem.

My Ati 1650GT has the same problem.It was normal when I enter ubuntu for 1 or 2minutes,and than ,the fan became crazy..No doubt it's because the temp~

It happens too with Radeon X1800 GTO and Radeon X1900 GT.

Possible solution (at least using a Mobility Radeon X1600):
<pre>aticonfig --set-powerstate=1</pre>

To find out which powerstates your Radeon supports try:
<pre>aticonfig --lsp</pre>

=== System freezes after logout with GDM, KDM or XDM<ref>http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm/xdm hardlocks after running X session</ref> ===

If you use GDM, which is the default Login Manager on Ubuntu, modify
<pre>sudo gedit /etc/gdm/gdm.conf</pre>

{{Box File|/etc/gdm/gdm.conf|
<nowiki>AlwaysRestartServer=true</nowiki>
}}

If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following

<pre>sudo kate /etc/kde3/kdm/kdmrc</pre>

{{Box File|/etc/kde3/kdm/kdmrc|
<nowiki>TerminateServer=true</nowiki>
}}

if you use xdm, add the following to
<pre>sudo gedit /etc/X11/xdm/xdm-config</pre>

{{Box File|/etc/X11/xdm/xdm-config|
<nowiki>DisplayManager*terminateServer: true</nowiki>
}}

=== System freezes at startup of Fedora 7 after installing the driver ===

Turn off the Redhat Graphical boot from grub config:

Edit the grub config file located at /boot/grub/grub.conf and remove the 'rhgb' from the kernel line in order to disable the Redhat Graphical boot.

=== System lockup on logout with catalyst 8.01 <ref>http://www.phoronix.com/forums/showthread.php?t=7448&page=5 System lockup on logout with catalyst 8.01</ref>===
To solve this issue you need to disable atieventsd. On ubuntu you can run:
<pre>
sudo /usr/sbin/update-rc.d -f atieventsd remove
</pre>

=== Intermittent Freezes/Lockups due to AGPv3 running at 8x ===
Try forcing X to set AGP Speed to 4x
{{Box File|/etc/X11/xorg.conf|
<pre> Option "AGPv3Mask" "0x00000002"</pre>
}}
((Would be nice to put down WHERE to change this, not just to change this. The same applies to just about every hint shown above.))

+ You add it to the "Device" section for your graphics card in /etc/X11/xorg.conf.

==References==
<references/>

[[Category:Installation Documentation]]

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

Glxgears is not a Benchmark

2008-12-16T19:46:19Z

80.90.160.194: FIELD_OTHER

FIELD_MESSAGE_letoletoaltr

IBM

2008-12-16T19:35:58Z

80.90.160.194: FIELD_OTHER

IBM has sold the PC business unit to [[Lenovo]].

===Workstations===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|Intellistation zPro
|FireGL V3100, FireGL V7100
|Works
|-
|}

FIELD_MESSAGE_pasmonri

===Resources===

[http://thinkwiki.org/ ThinkWiki Community Page]

[[Category:OEMs]]

Arch Linux

2008-12-16T19:24:42Z

80.90.160.194: FIELD_OTHER

Installing and using fglrx drivers on Arch Linux should be a piece of cake, as the distro provides pre-built packages in its official repos, accessible through the pacman package manager.

The installation instructions I've taken straight from Arch's own wiki page, linked below in the External Resources section.

==Installation==

=== Stock Kernels ===

FIELD_MESSAGE_lic4tbos

====Notes====

* These packages contain '''only''' the kernel module, and depend on the <code>catalyst-utils</code> package. The <code>catalyst-utils</code> package is kernel-independent and provides the libraries and utilities for Xorg, including ATI's own <code>libGL.so</code>.
* After installing the package, you'll need to either <code>source /etc/profile</code> or log out, then back in to set up the environment properly.
* If you run both <code>kernel26</code> and <code>kernel26beyond</code> then install both catalyst module packages. They won't conflict with one another.

=== Custom Kernels ===

To install catalyst for a custom kernel, you'll need to build your own <code>catalyst-$kernel</code> package, containing the kernel module compiled specifically for your kernel.

If you are at all uncomfortable or inexperienced making packages, read up Arch's [http://wiki.archlinux.org/index.php/ABS ABS] wiki page first so things go smoothly.

==== Obtaining PKGBUILD ====
Obtain the <code>PKGBUILD</code> and <code>catalyst.install</code> files from CVS or ABS. Either:

* Visit http://www.archlinux.org/packages.php?id=10416 and click "View CVS Entries" to find them, or
* Run <code>abs</code> as root and locate the files in <code>/var/abs/extra/modules/catalyst</code>.

==== Editing the PKGBUILD and building ====
Three changes need to be made here:

'''First''', change
pkgname=catalyst
to
pkgname=catalyst-KERNEL_NAME
where KERNEL_NAME is whatever you want (custom, mm, themostawesomekernelever)

'''Second''', remove <code>kernel26</code> from the dependencies list.

'''Third''', change
_kernver=2.6.15-ARCH
to
_kernver=`uname -r`
(or directly insert the output of uname -r '''when running your custom kernel''' there)

Finally, build and install the package. (<code>makepkg -i</code> or <code>makepkg</code> followed by <code>pacman -A pkgname.pkg.tar.gz</code>)

==== Notes ====

* No changes need to be made to the <code>catalyst-utils</code> package, which is completely kernel-independent. '''All''' you need to do is compile a kernel module.
* To build and run the catalyst kernel module with 2.6.16 kernels, patches are needed! Check out the cvs entries for catalyst in testing for the required patch.

==Related Resources==
* [http://www.archlinux.org Arch Linux Homepage]
* [http://bbs.archlinux.org Arch Linux Forums]
* http://wiki.archlinux.org/index.php/ATI

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