I was finally able to reproduce. a) I had to update my NVIDIA driver from a pretty old 185 to 260. b) Used Wine 1.3.14 (from ubuntu-wine/ppa karmic) and fr-041_debris.exe c) The problem is not between wine and the 2D xserver, but wine and the 3D Xserver. Wine must be doing a GetCurrentDisplay(). d) Wine refused to run in a truly remote indirect context (died complaining out of 3d video memory!?!) but I made it work with
VGL_DISPLAY=tcp/localhost:0 I don't pretend to understand that, but I was able to grab a wireshark trace from the lo device. Unfortunately that gives more questions than answers: I get: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 136 (GLX) Minor opcode of failed request: 16 (X_GLXVendorPrivate) Resource id in failed request: 0x3e00006 Serial number of failed request: 0 Current serial number in output stream: 113 I should have noticed before "Serial number of failed request: 0". This most certainly represents an internal error in the code handling the error. All the X servers I'm familiar with (including x.org) increment the sequence number before replying; The minimum sequence # is at least 1. Further, just looking at the trace I can see there is no such request, even if a serial of 0 were possible. The trace has all the info up to a CreatePbuffer and MakeCurrent on that ID 0x3e00006. If the serial number is bogus, the minor opcode might be also (i.e. we're barking up the wrong tree with X_GLXVendorPrivate). So Calvin, I am not sure where to go from here. If you're really looking to get something working you could try downgrading to the 185 driver. The problem is a lot harder to trace because when I use my own custom tracing tools (transparent proxy pass-through) wine refuses to run also. :( Otherwise we could at least figure out if it was the X server or wine handling of the Xerror that was at fault. -Nathan On 11-02-27 07:58 PM, DRC wrote: > Getting an indirect context should be a matter of simply running WINE > without VirtualGL and displaying from the application server to a client > machine that has a 3D-capable X server. In this case, all of the GLX and > OpenGL commands are sent over the network to the client machine. > > On Feb 27, 2011, at 5:35 PM, calvin.mor...@comcast.net > <mailto:calvin.mor...@comcast.net> wrote: > >> The issue has been reproduced using wine 1.3.13 (and I've also >> reproduced with wine versions 1.3.11-14). So far I've had the issue >> with any DirectX based Windows app used through Wine and VirtualGL. >> >> Let me know if I can help troubleshoot this. I can certainly grab a >> Wireshark trace, however I might need more guidance on forcing an >> indirect context. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
