Hi everybody;

I made another try at running emc over ssh -Y again this morning, but it 
fails shortly after opening an incomplete axis screen, as follows:

Starting EMC2...
X Error of failed request:  BadLength (poly request too large or internal 
Xlib length error)
  Major opcode of failed request:  136 (GLX)
  Minor opcode of failed request:  1 (X_GLXRender)
  Serial number of failed request:  2579
  Current serial number in output stream:  2580
Shutting down and cleaning up EMC2...

And of course the above is far more informative than the two log files it 
suggests I read.

That machine is of course using the vesa driver, this one the most recent 
nvidia blob.

>From glxinfo on that machine:
direct rendering: No (LIBGL_ALWAYS_INDIRECT set)

Is this miss-match the root cause of the problem?

And, short of switching to a non-axis interface with no backplot abilities, 
is there a workaround?

Thanks folks.

Cheers, gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
* joeyh_ wonders if linux is supposed to lock up when you ask 100
  processes to cat the entire cd drive

------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to