Frame Buffer Test (fbtest)

The fbtest is a generic test for all dumb frame buffers used with the Solaris 2.x software.

The fbtest checks the frame buffer by sequentially writing, reading, and verifying small blocks of random patterns across the entire video RAM. The block size is 64 x 64 pixels. If a miscompare occurs, the test stops with an error message that indicates the location of the error.

If a generic frame buffer device name (dvc/fb) is specified, fbtest automatically detects the depth of the frame buffer, and adjusts testing to the frame buffer size.

Figure 9-1 fbtest

---

Note - To start SunVTS with vtsui, but without vtsk, you must add the hostname to xhost as:

xhost + <hostname>.

---

fbtest Command Line Syntax

/opt/SUNWvts/bin/fbtest -o dev=device_name lock=E(nable)/D(isable)
standard_arguments

Argument	Explanation
dev=device_name	Specifies which frame buffer to be tested
lock=E(nable)/D(isable )	Enables/disables the window system locking option. See the section about Testing Multiple Frame Buffers in SunVTS 2.0 User's Guide for details. Frame buffer locking is enabled by default on the window server running the OpenWindows software.

fbtest Test Modes

Connectivity Mode Not applicable for this test.

Online Mode Not applicable for this test.

Offline Mode Due to the nature of graphic tests, reading from or writing to the frame buffer during graphic tests disturbs user operation. This test is only available in Offline Mode.

fbtest Error Messages

The fbtest error messages are listed below with explanations or probable causes:

6000 Data compare error

Probable_cause(s):

a. FB lock disabled b. Bad Frame Buffer

Recommended_Action(s):

a. Enable FB lock b. If the problem persists, call your authorized Sun service provider.

6001 Video memory error at <address>, expected: <number>,
observed: <number>

Probable_cause(s):

a. FB lock disabled b. Bad Frame Buffer

Recommended_Action(s):

a. Enable FB lock b. If the problem persists, call your authorized Sun service provider.

6002 Unable to lock frame buffer.

Probable_cause(s):

a. FB lock was enabled while Window System was not running

8000 can't acquire console semaphore

Probable_cause(s):

a. System load too heavy

b. System error

Recommended_Action(s):

a. Reduce the system load b. If the problem persists, contact your Sun service provider

8001 Parameter error - Improper test parameters supplied.

Probable_cause(s):

a. fbtest can only run in offline mode

8002 Device name missing!

Probable_cause(s):

a. Parameter error.

Recommended Action(s):

a. Must provide device name

8003 Create_Raster() failed for <name>

Probable_cause(s):

a. Parameter error b. No such device

8004 Create_Raster() failed for type RAS_CHILD

Probable Causes(s):

a. Operator error b. Software error

Recommended Action(s):

a. Check test options, mode and retry if appropriate b. Consult Support Representative

8005 Malloc failed.

Probable_cause(s):

a. System load too heavy b. System error

Recommended_Action(s):

a. Reduce the system load b. If the problem persists, call your authorized Sun service provider.