Testing Frame Buffers

Before running a frame buffer test, determine whether the test requires frame buffer locking. Not all frame buffer tests have a locking option. Some tests set the lock automatically. Check the test chapter for each individual test to see if this step is needed. If locking is required, you can set the lock in one of two ways:

• If you are using the CDE SunVTS interface, go to the Option menu of the graphic test and select Enable for the frame buffer locking option.

• If you are working from the command line, you can enable frame buffer locking with the lock=e/d option. For example, to run the generic frame buffer test (fbtest) with a locked frame buffer, type:

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

(See the test command line argument descriptions in this manual.)

---

Caution -

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

---

Both the screen saver option and the system save/resume option of Power Management must be disabled on the system being tested before conducting any frame buffer test.

If you are using either the CDE or the Open Windows interface for SunVTS, do not conduct frame buffer tests through the dtlogin window. Log in as root and disable the auto-logout option.

---

Caution -

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

---

Testing Multiple Frame Buffers

The following rules apply when you test multiple frame buffers (displays) simultaneously:

• Only the console monitor can run the window environment (such as CDE). The console monitor is the monitor connected to the frame buffer appointed by /dev/fb. SunVTS enables frame buffer locking on the console monitor by default.

• The frame buffer that is running the window environment must have window locking enabled to avoid false test failures. All other frame buffers must have window locking disabled.

Remote Testing of Frame Buffers

If you start sunvts or vtsk from a screen other than the console monitor, frame buffer locking is not available. In this case:

• disable the window locking option on the remote screen to d.

• enable frame buffer locking for the console monitor, as shown in the example above. The SunVTS user interface cannot display on a monitor if locking is disabled.

Do not run any graphic programs (including vtsui) on the remote frame buffer during graphic testing.