C H A P T E R 2 |
Sun XVR-2500 and XVR-300 Graphics Accelerator Test (graphicstest) |
This chapter describes how to use graphicsttest for both the XVR-300 and XVR-2500. The following topics are included:
graphicstest verifies the functionality of XVR-2500 and XVR-300 frame buffers. Test accuracy is checked using direct image comparison against compressed images. Failed pixel locations are printed as error messages.
Caution - Do not run any other application or screen saver program that uses the frame buffer's accelerator port while running graphicstest. This combination causes SunVTS to return incorrect errors. |
To run graphicstest as super user, you must use the console device or start the desktop with the -ac option.
Note - The CDE desktop is an X client that prevents the X server from restarting after each graphicstest finishes testing the kfb device. |
Disable all screen savers before testing any graphics device. To disable the Solaris screen saver, type the following at a UNIX prompt:
To turn Display Power Management off, type the following at a UNIX prompt:
The display resolution must be 1280x1024. To change resolution, go to a UNIX prompt and type:
You must run graphicstest through the SunVTS user interface. The desktop must be running on the XVR-2500, and the desktop must be setup to run in 24-bit mode (the default depth for XVR-2500). Perform on of the following procedures prior to performing graphicstest to ensure that the test runs as smoothly as possible.
To Run graphicstest in a Desktop GUI |
1. Turn Power Management off, if it is enabled. See graphicstest Test Requirements for XVR-2500.
2. Verify that no other program is running that might modify the screen during the test.
3. Verify that you have permission to lock the X server. graphicstest is designed to lock the X server during testing to prevent screen changes.
4. Verify that the JDS login window is not displayed during testing.
5. For frame buffers other than kfb, verify that the desktop is running on one frame buffer only.
If a kfb device is in the platform, the desktop must not be run on any other non-kfb graphics devices in the system when performing SunVTS.
Note - To perform graphicstest on kfb frame buffers, the desktop must be running on each kfb device in the system. |
To reach the following dialog box, right-click on the test name in the System Map and select Test Parameter Options. Because graphics test can test multiple types of frame buffers, the test name that is displayed will correspond to the particular frame buffer being tested. If you do not see this test in the System Map, you might need to expand the collapsed groups, or your system might not include the device appropriate to this test. Refer to the SunVTS User's Guide.
By default, all graphicstest options are enabled.
Due to the nature of graphic tests, reading data from, or writing data to the frame buffer during graphic tests disturbs user operation. For this reason, graphicstest is only available in Functional test mode.
/opt/SUNWvts/bin/sparcv9/graphicstest standard_arguments -o dev=device_name open=Enable/Disable dma=Enable/Disable mem=Enable/Disable chip=Enable/Disable B=n F=n S=value.
Disable all screen savers before testing any graphics device. To disable the Solaris screen saver, type the following at a UNIX prompt:
To turn Display Power Management off, type the following at a UNIX prompt:
For full instructions on testing frame buffers, see Frame Buffer Tests.
Perform all of the following procedures prior to performing graphicstest to ensure that the test runs as smoothly as possible.
To Run graphicstest for XVR-300 With the Window System |
1. Turn Power Management off, if it is enabled. See graphicstest Test Requirements.
2. Verify that no other program is running that might modify the screen during the test.
3. Verify that you have permission to lock the X server. graphicstest is designed to lock the X server during testing to prevent screen changes.
4. Verify that the JDS login window is not displayed during testing.
5. If you are running the window system and testing multiple framebuffers, make sure you set Group Concurrency of Graphics to 1.
To Run graphicstest for XVR-300 From the Command Line |
1. Turn Power Management off, if it is enabled. See graphicstest Test Requirements.
2. Ensure that no other program is running that might modify the screen during the test.
3. Ensure that the frame buffer being tested is not the console device. Console messages might modify the screen.
To reach the following dialog box, right-click on the test name in the System Map and select Test Parameter Options. Because graphics test can test multiple types of frame buffers, the test name that is displayed will correspond to the particular frame buffer being tested. If you do not see this test in the System Map, you might need to expand the collapsed groups, or your system might not include the device appropriate to this test. Refer to the SunVTS User's Guide. By default, all graphicstest options are enabled.
Due to the nature of graphic tests, reading data from, or writing data to the frame buffer during graphic tests disturbs user operation. For this reason, graphicstest is only available in Functional test mode.
TABLE 2-4 lists the graphicstest Supported Test Modes for XVR-300.
/opt/SUNWvts/bin/sparcv9/graphicstest standard_arguments -o dev=device_name open=Enable/Disable dma=Enable/Disable mem=Enable/Disable chip=Enable/Disable B=n F=n S=value
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.