Allan Schaffer (aschaffe)
Tue, 9 Nov 93 13:13:56 -0800
BACKGROUND: The problems are related to the way that
Performer recognizes the graphics hardware in the machine.
Since the Indy was introduced after Performer 1.1 released,
Performer is unable to match the graphics type (NEWPORT) with
the hardware types it knows. This effects both the
installation and run-time applications.
PROBLEM 1: Faulty install. /usr/lib/libpr.a,
/usr/lib/libpr-g.a, /usr/src/Performer/demo/perfly, and
/usr/src/Performer/src/perfly/Makefile are machine-tagged in
inst as platform-specific and will not be installed by
default.
WORKAROUND: You must remove IRIS Performer 1.1 from your
machine and re-install, explicitly defining the graphics
hardware type. LIGHT (Entry) graphics is the closest
approximation to NEWPORT.
% su
# versions remove performer_eoe
# versions remove performer_dev
# inst -f <pathname> -m GFXBOARD=LIGHT
PROBLEM 2: Performer 1.1 applications display the message:
"unable to determine graphics type -1. Default: VENICE"
WORKAROUND: The above message means that Performer was
unable to match NEWPORT graphics to a known graphics type,
and has defaulted to VENICE (RealityEngine). This could
cause some anomalous behavior in your application. There is
no specific workaround at this time.
PROBLEM 3: /usr/src/Performer/demo/perfly fails with the
error message:
"perfly: rld: Fatal Error: cannot find soname 'libpf.so'"
WORKAROUND: You must recompile perfly from the source code
provided in /usr/src/Performer/src/perfly.
PROBLEM 4: perfly prints the following error message(s)
several times each frame:
"Performer Info:FP division by zero"
"Performer Info:FP infinity minus infinity"
WORKAROUND: This is caused by a bug in IRIS GL and is not a
fatal error. Run perfly with the "-n 2" option to disable
these (and any other) informational messages.
----
Allan Schaffer
Silicon Graphics
aschaffe++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:05 PDT