Jim Helman (jimh++at++surreal)
Wed, 22 Feb 95 18:30:22 -0800
> pfInit: mmap failed for /dev/zero
hugo writes:
> mmap failed for /dev/zero
>
> You folks at SGI listening? ;-)
Yes, this error message was improved over two years ago.
I'm impressed that people are still running Performer 1.0.
You know we released Performer 1.2 for 4.0.5 as well as 5.
However the problem here is not DGL, but rather trying to run a
Performer 1.0 4.0.5 binary on a 5.2 machine with the strict
virtual memory accounting that was added in 5.1. The 4.0.5
executable will run on a 5.X machine if you add sufficient
virtual swap space with swap(1M), e.g. swap -a -v <virtual
length>, but in general running a 4.0.5 executable on a 5.X
machine is not recommended, particularly on Onyx, because of
multiprocessing restrictions that IRIX requires for compatible
lock handling.
But there could be DGL issues as well. Officially, we've never
supported DGL because networked graphics is so dang slow that
none of our real-time customers requested it. But we do see
people wanting to use remote rendering in coding and debugging
environments so we're trying to make 2.0 support it. The main
problem is Performer's desire for a video retrace clock and its
unhappiness if it does not get one on a machine that it knows
should have one. Since remote use of the glXVideoSync extension
is better supported than the old glcompat call was, remote
rendering should work better in OpenGL and 2.0.
rgds,
-jim helman
jimh++at++surreal.asd.sgi.com
415/390-1151
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:59 PDT