[PD] "error: GEM: Do not continue!"

Johannes M Zmoelnig zmoelnig at iem.kug.ac.at
Tue Apr 24 08:46:19 CEST 2001


On Tue, 24 Apr 2001, m.ash wrote:

> 
> any hints welcome.
> 
> i can keep gem running wich still works but X eats up my cpu (rendering 
> nothing)
this means, that you do not have hardware-acceleration activated. the cpu
has to do the openGL thing (because no stable opengl-context (sic!) could
be established) and this is quite much.

> i m using x4.0.3 with a matrox g400 and its latest drivers modules 
> (standards doesn't work eithert)
> ,gfx, dri , v4l ..
> 
ah strange,
i once (or twice) used a matrox g450 and it did perform quite (!!) well,
meaning that it consumed about half of the cpu but far less than without
hardware-acceleration (with the geforce-chip the rendering costs virtually
nothing -- there might be some optimization left within the matrox
hardware/software design)
the only thing i remember (sorry) is, that we had to use a specifique
constellation of matrox-drivers and xfree.
meaning that maybe the latest xfree-release will work together with the
newest matrox-modules, but maybe not. when nothing did work, i had another
look ad the matrox-homepage, and - beware! - there was another newer
driver, which i had never noticed before, and everything worked after i
downloaded this one.

the dual-head capabilities of the g450 could be used, although the
hardware-acceleration only worked on the first screen. (unfortunately, you
couldnt drag a window from one screen to the other (which i had expected),
but you had to start a programm on the specified screen. it would have
been much fun, to drag a actively rendering window and switch dynamically
between hardware and software opengl. maybe it would have been no fun at
all)

mfg.asd.f
IOhannes


> ?
> 
> ...
> 
> m.
> 
> 
> At 08:46 23.4.2001, Mark Danks wrote:
> >   GEM does some "tricks" on startup to find out what OpenGL capabilities
> >your machine/graphics card has.  This is the "const context".  This message
> >is GEM telling you that it could not create an OpenGL rendering
> >context...which means that you really shouldn't continue.
> >
> >   The first error is complaining that it can't open the X display to create
> >the rendering context.  I would assume that there is something strange going
> >on with the dual head setup.  Let me know if you need more info with the X
> >setup code.
> >
> >Later, Mark
> >
> >============================
> >= mdanks at stormfront.com
> >= Lead Programmer PS2
> >= http://www.danks.org/mark
> >============================
> >
> >
> > > -----Original Message-----
> > > From: m.ash [mailto:m.ash at gmx.at]
> > > Sent: Monday, April 23, 2001 4:21 AM
> > > To: pd-list at iem.kug.ac.at
> > > Subject: [PD] "error: GEM: Do not continue!"
> > >
> > >
> > > hi list.
> > >
> > > got gem build and running on a rh7.1 system.
> > > (which was a nightmare,..)
> > >
> > > i get following error message when creating a window:
> > >
> > > error: GEM: Could not open display %/1iso8859-15
> > > error: GEM: Error creating const context
> > > error: GEM: A serious error occured creating const Context
> > > error: GEM: Do not continue!
> > >
> > > can anyone tell what this means or is caused by?
> > > (maybe a conflict with the X (4.0.3) dual head setup?)
> > >
> > > th.
> > >
> > > m.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> 
> 
> 




More information about the Pd-list mailing list