Verifying: Difference between revisions

From cchtml.com
No edit summary
mNo edit summary
Line 1: Line 1:
pasmontro
{{VCT-on-top}}
{{VCT-on-top}}



Revision as of 20:07, 27 October 2007

Distribution Neutral Steps

Verifying | Configuring | Troubleshooting


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.

fglrxinfo

$ fglrxinfo
display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 2.0.5804 (8.25.0)

fgl_glxgears

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 when you run fgl_glxgears, 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

Links

http://linux.coconia.net/general/ati.htm
http://m.domaindlx.com/LinuxHelp/ati/ati.htm (mirror)

Verify with Linux tools

glxinfo

This command line option should report "direct" rendering.

$ glxinfo | grep direct

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

Xorg.0.log

The X.org 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