graphdiag(1G)graphdiag(1G)NAMEgraphdiag - run diagnostics on the graphics device
SYNOPSISgraphdiag [-l <n>] [-t <n>] [-e <n>] [-v <level>] [-s] [-r <test name>]
[-d <display>] [-h|-?]
DESCRIPTIONgraphdiag(1G) will run a set of diagnostics on the graphics hardware to
verify that the hardware is working correctly.
NOTE: If OpenGL is not on the system, graphdiag is only able to per‐
form a subset of the tests. In this case, graphdiag will use the X
Server alone to verify that the hardware is working as expected.
OPTIONSgraphdiag accepts the following command line options:
-l n Loop control. Specifies how many loops to execute based on the
value of n. The default number of loops is 1. Note that this
option is not allowed with the -t option.
-t n Time control. Specifies how much time in seconds to loop for
based on the value of n. A value of zero (0) indicates loop
forever or until a break command. Note that this option is not
allowed with the -l option.
-e n Errors allowed. Specifies the number of errors allowed before
exiting. The default value is zero (0), so the first error
will cause the program to exit.
-v level
Verbosity level. Specifies the degree of verbosity based on
the value of level. A level of one (1) displays error messages
only to stderr. Levels above one will log varying degrees of
information messages to stdout up to a maximum level of three
(3). The following levels are defined:
1 - Only error messages are logged.
2 - Additional logging of start and end time for testing
along with warnings.
3 - Additional logging of periodic progress reports.
The default level is two (2).
-s List the names of all the possible tests. See descriptions
below.
-r test name
Run a specific test identified by test name. Use the -s option
to get a list of possible tests.
-d display
Specifies the display to use, for example display_host:0.0. If
this option is not used, graphdiag will use the display speci‐
fied by the DISPLAY environment variable.
-h or -?
Displays descriptions for the above options.
EXPLANATION OF TESTS
X SERVER TESTS:
TestXLines - draws multiple connected lines and verifies that the num‐
ber of pixels drawn is as expected.
TestXWindowMove - moves a window around on the screen and verifies that
the contents do not change.
TestXWindowClip - draws a primitive outside the window boundaries and
verifies that it is clipped correctly.
TestXBuffer - uses the X server to clear the framebuffer with red,
green and blue values and then reads back the pixels to verify that all
color channels are correct.
OPENGL TESTS:
TestOglPipeline - writes and reads values to each buffer and verifies
that the values are correct.
TestOglGeoAcc - draws simple 3D primitives and verifies that they were
rendered correctly. Pixel counts are used for verification since
checksums can vary on different types of graphics cards.
TestOglVectors - draws 3D vectors and verifies that the correct number
of pixels were drawn.
TestOglTextures - maps a pattern to several shapes and verifies that
the correct number of pixels of the right colors are written.
TestOglLights - draws a white rectangle and lights it with red, green
and blue lights, then verifies that the pixels are colored correctly.
TestOglTexMem - fills the texture memory with textures and then maps
them to the screen to verify that the texture memory is working prop‐
erly.
DEPENDENCIESgraphdiag requires that an X Server is running.
SEE ALSOgraphinfo(1G)AUTHORgraphdiag(1G) was developed by HP.
graphdiag(1G)
