HP SVA V2.1 System Administration Guide

Table A-1 Troubleshooting (continued)
RemarkProblem
This could be a problem with your display devices. If you
are using a video switch between your display nodes and
display devices, try hooking your display devices directly
to the display nodes.
Another possibility may appear using the
sva_chromium_dmx.sh script. Depending on the
display hardware on your cluster, use of the
sva_chromium_dmx.sh script in non-interactive mode
may not start all the tiles in a multi-tile display with the
correct resolutions. Normally, all tiles should share the
same resolution as determined by the Display Surface
default resolution. This problem is more likely to appear
in displays that use analog video connections.
After you begin a job using the sva_chromium_dmx.sh
script, DMX indicates that it is starting by means of a
message in the upper-left corner tile of a multi-tile display.
The remaining tiles are black until the visualization
application starts. You may have the problem if the
application starts with an image that appears incorrectly
offset in the upper-left tile when compared to the
remaining tiles in the display. This may be because the
tiles are using different resolutions.
You can verify the resolutions on the individual tiles by
running the following command from the head node for
each display node cabled to its respective display tile:
% xwininfo -root -display n1:0
Substitute each display node used to drive the tiles in
your display for n1.
There is a Site Configuration File tag that fixes this
problem. It is the SVA_FILL_DISPLAYS_ON_STARTUP
tag in the SVA_CLUSTER section of the Site Configuration
File. Set the value of this tag to “yes” in the Site
Configuration File. This requires root privileges.
From any cluster node, enter the following command:
# svaputdata SVA_CLUSTER
SVA_FILL_DISPLAYS_ON_STARTUP yes
If the problem persists, contact HP Technical Support.
Sub-portions of an image (individual tiles) are different
sizes relative to one another on a multi-tile display.
56 Troubleshooting