SunVTS 3.0 User's Guide

Testing Frame Buffers

If you are running SunVTS on a frame buffer that is running a graphics test, a false error may occur. This is not a problem when you are running windows (OPEN LOOK or CDE).

No other graphic application can be run in the same window once you start the graphic test.

To Activate the Frame Buffer Test

If you are using the CDE or OPEN LOOK SunVTS interface, from the Option menu of the graphic test, select Enable for the frame buffer locking option.

If you are working from the command line, you can enable frame buffer locking by specifying a command-line argument.

(See the test command line arguments in the SunVTS 3.0 Test Reference Manual.)

# ./fbtest -o dev=cgthree0,lock=Enable

Caution -

Do not run TTY mode and frame buffer tests concurrently on the console monitor; the frame buffer tests may fail.

Note -

If window locking is disabled (unlocked) on frame buffers that are running vtsui, or you move the mouse, you will receive spurious error messages. Even slight mouse movements can cause a test to fail.

Testing Multiple Frame Buffers

These rules apply when testing multiple frame buffers (displays) simultaneously:

You can test multiple frame buffers on a system simultaneously, but only the console monitor can run windows. The console monitor is the monitor connected to the frame buffer appointed by /dev/fb.

The frame buffer that is running windows must have frame buffer locking enabled to avoid spurious test failures. Other frame buffers must have frame buffer locking disabled.

By default, SunVTS enables frame buffer locking for the console frame buffer (/dev/fb). If your system has more than one frame buffer, you must disable frame buffer locking for all frame buffers except the one running windows. If you are running a frame buffer test from a command line, you can disable or enable frame buffer locking by specifying a command-line argument. (See the test command-line descriptions in the SunVTS 3.0 Test Reference Manual.) For example, if you were running the generic frame buffer test (fbtest), you would use the lock=Disable/Enable option to disable frame buffer locking:
```
#./fbtest -o dev=cgthree0,lock=Enable
```

If you start SunVTS from a screen other than the console monitor, Frame buffer locking is not available. You must enable the frame buffer lock for the console monitor, as shown in the example above. The SunVTS user interface cannot display on a monitor if frame buffer locking is disabled.