From: Brian P. <bri...@tu...> - 2007-11-30 22:02:44
|
Peter Clifton wrote: > Hi, > > I'm having some strange (seemingly) depth buffer related issues running > VTK. > > I've got the Intel X driver version 2.1.0 (+ Ubuntu Gutsy patches), and > mesa version 7.0.1 (Ubuntu Gutsy - might have some patching). > > When I run a simple test program: > > MESA_DEBUG=1 ipython -wthread vtk_test.py > > Where vtk_test.py is from the first example here: > http://scipy.org/Cookbook/MayaVi/mlab > > I get this warning: > Mesa warning: glEnable(GL_DEPTH_TEST) but no depth buffer It means your window wasn't created with a Z/depth buffer, but the program is trying to enable/use depth buffering. > I initially thought I'd messed something up in compiling mesa head, > libdrm head, drm head dri drivers, and was trying to use those with both > 2.1.0 and 2.2.0 X drivers (recompiled each time with the new DRI). > > (Testing to see if the bug I was seeing had been fixed). > > When testing newer DRI, I had to patch the 2.1.0 driver to use some of > the new ioctl interface. > > I've since reverted to Gutsy versions of mesa, the kernel modules, > libdri and the Intel Xorg driver, and the Mesa warning persists. > > Should there be a depth buffer? > >>From Xorg.0.log: > > (II) intel(0): [drm] DRM interface version 1.3 > (II) intel(0): [drm] created "i915" driver at busid "pci:0000:00:02.0" > (II) intel(0): [drm] added 8192 byte SAREA at 0xf8c14000 > (II) intel(0): [drm] mapped SAREA 0xf8c14000 to 0xb7bc7000 > (II) intel(0): [drm] framebuffer handle = 0xd0040000 > (II) intel(0): [drm] added 1 reserved context for kernel > (II) intel(0): Unable to use TTM-based memory manager with DRM version > 1.6 > (II) intel(0): [drm] Registers = 0xe8400000 > (II) intel(0): [drm] ring buffer = 0xd0000000 > (II) intel(0): [drm] init sarea width,height = 1400 x 1400 (pitch 2048) > (II) intel(0): [drm] Mapping front buffer > (II) intel(0): [drm] Front Buffer = 0x2a008000 > (II) intel(0): [drm] Back Buffer = 0xd4000000 > (II) intel(0): [drm] Depth Buffer = 0xd5000000 > (II) intel(0): [drm] textures = 0xd8000000 > (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432 > > So it "should" be there in theory? It depends on the GLX visual being chosen. > One of the guys on the VTK list suggested trying with GL_DEPTH_BITS=32 > (which doesn't help... You mean 'export MESA_GLX_DEPTH_BITS=32'? That's for software rendering only. > if I don't have a depth buffer available, I > presume it won't!) Is this variable going to be useful in general for > future visualisations though, if I can get a depth buffer working? My guess is there's a bug somewhere in the python code related to GL and window creation. Do other OpenGL apps (or demos like glxglears) seem OK? -Brian |