[jwhat]

Hi Weblacky,

yes I read the manual ;-) tried "-help", which is why I was surprised that script did not seem to explicitly have graphics diags as part of listed test:

<<START LIST>>
###### Start Diagnostic List ########################################
## List of available diagnostics. Structure is as follows:
## diagName = Name of the diagnostic ex: "grizzly"
## diagBin = Name of diagnostic binary ex: "griz_script"
## diagDesc = Short description of the diagnostic ex: "System Stress Test"
## diagFunc = Function that runs the diagnostic. (See below for documentation on the function)
## diagBasic = String to pass to diagFunc when script is in Basic mode. (Or "NORUN" if diag does not run in that mode)
## diagNormal = String to pass to diagFunc when script is in Normal mode. (Or "NORUN" if diag does not run in that mode)
## diagExt = String to pass to diagFunc when script is in Extensive mode. (Or "NORUN" if diag does not run in that mode)
##
## To add a diagnostic - add it to this list and create a function (towards the bottom) to create a command line
## See the diag section for information on what the function needs to do.
##
## Diags are executed in the order they appear on this list.

@diags = (
# olperi
{"diagName" => "olperi", "diagBin" => "olperi", "diagDesc" => "CPU Diagnostic", "diagFunc" => \&runOlperi, "diagBasic" => "lvl1", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# torpedo
{"diagName" => "torpedo", "diagBin" => "torpedo", "diagDesc" => "CPU Floating Point Unit Diagnostic", "diagFunc" => \&runTorpedo, "diagBasic" => "lvl1", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olmem
{"diagName" => "olmem", "diagBin" => "olmem", "diagDesc" => "Online Memory Diagnostic (Check /var/adm/SYSLOG for error message)", "diagFunc" => \&runOlmem, "diagBasic" => "lvl1", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
{"diagName" => "olcmt", "diagBin" => "olcmt", "diagDesc" => "Cache/Memory Test (Check /var/adm/SYSLOG for error message)", "diagFunc" => \&runOlcmt, "diagBasic" => "lvl1", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# oldisk
{"diagName" => "oldisk", "diagBin" => "oldisk", "diagDesc" => "Disk Diagnostic", "diagFunc" => \&runOldisk, "diagBasic" => "NORUN", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olpci
{"diagName" => "olpci", "diagBin" => "olpci", "diagDesc" => "PCI Config Space Dump/Decode", "diagFunc" => \&runOlpci, "diagBasic" => "NORUN", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olenet
{"diagName" => "olenet", "diagBin" => "olenet", "diagDesc" => "BaseIO Ethernet Diagnostic", "diagFunc" => \&runOlenet, "diagBasic" => "NORUN", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olsio
{"diagName" => "olsio", "diagBin" => "olsio", "diagDesc" => "Serial Port Diagnostic", "diagFunc" => \&runOlsio, "diagBasic" => "NORUN", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olrti
{"diagName" => "olrti", "diagBin" => "olrti", "diagDesc" => "Real Time Interrupt Test", "diagFunc" => \&runOlrti, "diagBasic" => "NORUN", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olusb
{"diagName" => "olusb", "diagBin" => "olusb", "diagDesc" => "USB Diagnostic", "diagFunc" => \&runOlusb, "diagBasic" => "NORUN", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olrtr
{"diagName" => "olrtr", "diagBin" => "olrtr", "diagDesc" => "Router Diagnostic", "diagFunc" => \&runOlrtr, "diagBasic" => "lvl1", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# pandora
{"diagName" => "pandora", "diagBin" => "pandora", "diagDesc" => "System Stress Test", "diagFunc" => \&runPandora, "diagBasic" => "lvl1", "diagNormal" => "lvl1", "diagExt" => "lvl2" },
# olvst
{"diagName" => "olvst", "diagBin" => "olvst", "diagDesc" => "Generic Network test using Sockets", "diagFunc" => \&runOlvst, "diagBasic" => "NORUN", "diagNormal" => "NORUN", "diagExt" => "lvl1" }

);
###### End Diagnostic List ##########################################
<<END LIST>>

The list is from the "runalldiags" script.

I was trying to find the individual test executable, as when I run the script I get crash in reboot on PCI test, even thought the "offliine" test goes ok...

Maybe the graphics is part of "pandora" stress test...

EDIT #1:
Ok ran just "pandora" and it reports will run: io tests, fpu tests, mem tests, gfx tests, ntwk tests
So it is the "pandora" stress test that has the graphics test.

Cheers from Oz,


jwhat/John.