My Voodoo3 3000 graphic card do not work with some programs anymore. It happend after update to openSUSE 11.4. The previous 10.3 (with Mesa 7.0) works somehow, but not so good like the very old Mesa 4.0. Because the old versions cannot be compiled anymore, i will post my problems: 1) gmsh (http://geuz.org/gmsh/) coredump during startup. Compiled with enable-debug, i got the messages: libGL: XF86DRIGetClientDriverName: 1.4.3 tdfx (screen 0) libGL: OpenDriver: trying /home/nn/tmp/mesatst/inst/lib/dri//tdfx_dri.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: Interface 1.4 failed, trying 1.1 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 libGL: Can't open configuration file /home/nn/.drirc: No such file or directory. libGL: using Glide library libglide3-v3.so gmsh: swrast/s_span.c:1267: _swrast_write_rgba_span: Assertion `rb->PutValues' failed. PutValues not initialized on Voodoo3? (This has worked in openSUSE 10.3 (Mesa 7.0), but Mesa 7.0 cannot be compiled with DRI on openSUSE 11.4 anymore.) 2) All OpenGL outputs show some square artefact around the pointer in the OpenGL window if the mouse button is kept pressed. (e.g. geomview) 3) gl-117 freezes after some minutes, but i don't get any error messages. 4) extreme-tuxracer coredumps at exit, no error messages, but perhaps this is an etrace bug?
Created attachment 47281 [details] [review] quick and dirty fix (for "gmsh") This is a quick and dirty fix. Only ignore not initialized function pointer. With this "gmsh" nearly works, but a new problem arises: There seems to be a problem with opengl fond handling: the labels of the axes don't appear. Maybe a y offset problem like in version 7.0.x?
The 3dfx driver longer exists in Mesa.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.