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.