Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

SGI performer Frequently Asked Questions (FAQ)
Section - -98- 1.1 Bug Installing on Indy or Indigo2 XL

( Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Restaurant inspections ]


Top Document: SGI performer Frequently Asked Questions (FAQ)
Previous Document: -97- 1.1 Bug with Multipipe Onyx
Next Document: -99- 1.1 Bug Unable to determine Indy graphics type
See reader questions & answers on this topic! - Help others by sharing your knowledge

  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.

  /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

User Contributions:

Comment about this article, ask questions, or add new information about this topic:




Top Document: SGI performer Frequently Asked Questions (FAQ)
Previous Document: -97- 1.1 Bug with Multipipe Onyx
Next Document: -99- 1.1 Bug Unable to determine Indy graphics type

Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
sgi-faq@viz.tamu.edu (The SGI FAQ group)





Last Update March 27 2014 @ 02:12 PM