The following rules apply when you test multiple frame buffers (displays) simultaneously:
You can test multiple frame buffers on a system at the same time, but only one frame buffer can run the window environment.
To avoid incorrect test failures, for those frame buffer tests that have a window locking option, the frame buffer that runs the window environment, such as CDE or OPEN LOOK software, must have window locking enabled. Any other frame buffers must have window locking disabled.
If window locking is disabled (unlocked) on frame buffers that are running, the SunVTS tests can return false error messages if you move the mouse during testing. Even a slight mouse movement can cause a test to fail.
By default, SunVTS enables window locking on the console monitor (frame buffers that are the /dev/fb named device).
If you are running a frame buffer test from a command line, you can disable Window Locking by specifying a command line argument (see the test command line descriptions in this manual). For example, when running the generic frame buffer test (fbtest), use the lock=e/d option to enable or disable Window Locking. The example below shows the command that enables Window locking (frame buffer locking):
#./fbtest -o dev=cgthree0,lock=e
The frame buffer locking option does not work when you start sunvts or vtsk remotely. In this case, disable the window locking option to d. Do not run any graphic programs (including vtsui) on that frame buffer during graphic testing.