| Summary: | DRI2 prevents indirect glx | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Andrian Nord <NightNord> |
| Component: | General | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | mgariepy |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: | https://launchpad.net/bugs/785368 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Andrian Nord
2010-05-15 14:03:15 UTC
P.S. It seems to be unclear, but with mesa on client side, that are old enough to not have dri2, it's working just ok. (In reply to comment #0) > When running glx programs with dri2-enabled mesa on client side, it will return > > X Error of failed request: BadRequest (invalid request code or no such > operation) > Major opcode of failed request: 128 (DRI2) > Minor opcode of failed request: 1 (DRI2Connect) > Serial number of failed request: 19 > Current serial number in output stream: 19 > > export LIBG_ALWAYS_INDIRECT=1 > does the trick Does your server have DRI2? It sounds like it does not. Server side: night@nord ~ % glxinfo| grep DRI2 OpenGL renderer string: Mesa DRI R600 (RV710 9553) 20090101 TCL DRI2 From log: [ 1776.639] (II) RADEON(0): [DRI2] Setup complete [ 1776.639] (II) RADEON(0): [DRI2] DRI driver: r600 [ 1777.054] (II) GLX: Initialized DRI2 GL provider for screen 0 Client side is other machine: indirect glx -> via network. Patch posted: http://lists.freedesktop.org/archives/mesa-dev/2011-May/007789.html A less robust version was tested by the reporter on IRC. Ping. Can somebody please push Adam's patch, or the one in http://article.gmane.org/gmane.comp.video.mesa3d.devel/26942 ? Fixed in fbc2fcf685d22ec9bc9465e1f731529979497eaa |
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.