http://bugs.winehq.org/show_bug.cgi?id=10697
--- Comment #19 from Michał Kazior kazikcz@gmail.com 2007-12-25 05:39:40 --- I did as you told me to. I compiled Mesa, played a bit (using pure wine build), and here's what I found out:
1. I compiled Mesa with 'linux-dri-x86' config first, as this was used in the PKGBUILD of Mesa in my ArchLinux. The outcome is a libGL.so.1.2, libGLU.so.1.3.070001 and libGLw.so.1.0.0. I copied the libGL to the /usr/lib and changed the symlinks. Glxinfo reported no direct rendering (I presume this means it's using Mesa), however glxgears worked as before (no significant frame drop). I tried running StarCraft in these RenderTargetLockModes: 'textex/readtex' (both) - the screen is still as white as it was 'auto' - the game no longer crashes, but is incredibly slow (an improvement)
This means it somewhat fixed the PBO failure.
2. Then, I compiled Mesa with 'linux-x86' and got: libGL.so.1.5.070001, libGLU.so.1.3.070001, libGLw.so.1.0.0 and libOSMesa.so.6.5.3. I copied the libGL and libOSMesa to the /usr/lib and changed the symlinks. This time glxgears slowed down from 1200fps to 200fps. The results are: 'textex/readtex' (both) - the screen is in monochrome red 'auto' - the game crashes like it was before
I applied your earlier patch for the 'red screen bug' and the game started to render correctly (as a sidenote: it worked at least four times slower than in GDI; I could see how the game screen gets drawn from top to bottom, but I guess that's because it's doing software OpenGL).
I think it's not a driver bug, but rather an OpenGL extensions issue (maybe a bug or a slightly different usage; I have no idea, because I've never did anything using OpenGL before)
Oh, and I found this: http://www.nvnews.net/vbulletin/showthread.php?t=73108&highlight=pbo which may be somewhat related to the PBO issue here.