Thanks for the update. I really need to get access to an amdgpu-compatible card sooner rather than later, since the only AMD GPU I have requires the old fglrx drivers. If some benevolent soul reading this would be interested in helping out this project, a donation of such a GPU would help ensure VirtualGL's platform neutrality.
DRC On 3/29/19 7:01 PM, 'Richard' via VirtualGL User Discussion/Support wrote: > On Mon, 18 Mar 2019 22:54:37 -0500 > DRC <[email protected]> wrote: > >> Cases 1, 2, 3: >> >> VGL_FORCEALPHA was required because of the amdgpu drivers, as previously >> noted. > > I thought I should mention that I have uncovered another workaround for > amdgpu and mesa which has been working for me as effectively as the > VGL_FORCEALPHA method. I used the mesa DRIconf program to set the option: > "Create all visuals with a depth buffer" and clear the option "Allow exposure > of visuals and fbconfigs with RGB10A2 formats" because if that is set too > then the fix doesn't work. Note that this is applied to the Mesa > configuration and not to VGL. > -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/0de379d7-81fe-61ce-5a01-bfb67f2e864c%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
