Revision as of 17:19, 16 March 2013 by (talk) (fglrxinfo)
Jump to: navigation, search

It is assumed that you have completed the installation process.

Verify with ATI tools

If the installation has worked, then any 3D application should work without issue. A simple way to verify without any possibility of failure is to verify the following occurs. Please note that you may have needed to go through distribution specific process to enable the 3D support. > I don’t know if it’s me, but on the wall display with 9 dlsipays, it seems the parallel renderer is struggling…It's actually not the renderer, but the image capture tool which is struggling to record almost full-screen. With larger models this configuration does indeed struggle, which is not surprising considering you have 9 GL context and 4 processes on a single GPU .I am using Capture Me on Mac OS X anybody knows a better tool?


You can also run the ATI provided application called fgl_glxgears which should show a spinning cube with the venerable glxgears running on each face.

If you run fgl_glxgears and the cube spins but is lacking any cogs on the faces, the faces being instead various shades of blue and/or you get an error message like:

Using GLX_SGIX_pbuffer
913 frames in 5.0 seconds = 182.600 FPS
783 frames in 5.0 seconds = 156.600 FPS
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  14 (X_GetGeometry)
  Resource id in failed request:  0x0
  Serial number of failed request:  51
  Current serial number in output stream:  51

Then your installation most presumably failed!

Links (mirror)

Verify with Linux tools


This command line option should report "direct" rendering.

$ glxinfo | grep direct

(For Debian 4.0, install the mesa-utils package to get glxinfo.)


The X server log file also contains useful information to verify installation was successful. It is located on most Linux distributions at /var/log/Xorg.0.log and can be opened by any text editor.

You can now move on to configuring the driver.

Distribution Neutral Steps

Verifying | Configuring | Troubleshooting