VMD-L Mailing List

From: John Stone (johns_at_ks.uiuc.edu)
Date: Sat Aug 12 2006 - 13:34:42 CDT

Hi,
  This indicates that there's something wrong with your installation:
Info) OpenGL renderer: Mesa GLX Indirect

Ideally, you would not be using Mesa, nor would you be using an Indirect
OpenGL context. You're not remote displaying VMD from another machine
are you? I don't know if Mandriva has a video driver for your card, but
if not, you may wish to check the ATI web site, as using Mesa is not
recommended for running demancing apps like VMD. The "indirect" context
is also problematic, but that could be anything from an improperly set
DISPLAY environment variable, or one of several other possibilities.

If anyone else has an ATI FireGL V3100, please chime in...

  John Stone
  vmd_at_ks.uiuc.edu

On Sat, Aug 12, 2006 at 07:52:07PM -0400, Wei Liu wrote:
> Dear John Stone,
>
> Thanks for your quick response. The graphic card installed in my computer is
> ATI FireGL V3100. The following the VMD startup message.
>
> Info) VMD for LINUX, version 1.8.4 (April 17, 2006)
> Info) http://www.ks.uiuc.edu/Research/vmd/
> Info) Email questions and bug reports to vmd_at_ks.uiuc.edu
> Info) Please include this reference in published work using VMD:
> Info) Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
> Info) Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
> Info) -------------------------------------------------------------
> Info) Multithreading available, 1 CPU detected.
> Info) OpenGL renderer: Mesa GLX Indirect
> Info) Features: RN MDE MTX PP PS
> Info) GLSL rendering mode is NOT available.
> Info) Textures: 2-D (2048x2048), Multitexture (8)
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000adXRequest.143: BadLength (poly request too large or internal Xlib
> length error) 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x30000ad
> vmd > XRequest.143: BadLength (poly request too large or internal Xlib length
> er
> ror) 0x30000ad
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x44
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x44
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x44
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x44
> XRequest.143: BadLength (poly request too large or internal Xlib length error)
> 0
> x44
>
> Hopefully you could help me to solve this problem.
>
> Wei
>
>
> On Saturday 12 August 2006 11:40 am, John Stone wrote:
> > Hi,
> > Which video chipset and driver are you using on your machine?
> > This sounds to me like a buggy graphics driver. If you can email
> > me the VMD startup message that will be helpful in determining what's
> > happening on your machine.
> >
> > John Stone
> > vmd_at_ks.uiuc.edu
> >
> > On Sat, Aug 12, 2006 at 02:23:58PM -0400, Wei Liu wrote:
> > > Dear all,
> > >
> > > I am a new user of VMD and I just installed the precompiled version of
> > > VMD on Mandriva Linux 2006. When I start the program by typing "vmd",
> > > error messages appear in the vmd console window as the following.
> > >
> > > XRequest.143: BadLength (poly request too large or internal Xlib length
> > > error) 0x30000ad
> > >
> > > and
> > >
> > > XRequest.143: BadLength (poly request too large or internal Xlib length
> > > error) 0x44
> > >
> > > I can still load my pdb file and display it in VMD opengl window as
> > > lines, but if I choose the drawing method as newcartoon, the program will
> > > shut down automatically. Does anybody meet such a problem? Any
> > > suggestions will be highly appreciated.
> > >
> > > Regards
> > > Wei Liu 

-- 
NIH Resource for Macromolecular Modeling and Bioinformatics
Beckman Institute for Advanced Science and Technology
University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
Email: johns_at_ks.uiuc.edu                 Phone: 217-244-3349
  WWW: http://www.ks.uiuc.edu/~johns/      Fax: 217-244-6078