Issues with Vulkan on Linux dev build

[garant]

I signed up just so I could post here with my solution, which I put in another thread on this site that isn't very high in the Google results. I'm putting it here, too, so others can find it more easily.

Code:

Ubuntu 16.04.2, Kernel 4.8, Mesa 17.0.X (via Padoka stable PPA), Radeon RX480, open source AMDGPU driver

I had the same issues just recently; took a few hours, but finally got it. Here's the process I had to go through:


1) I installed the LunarG Vulkan SDK. It can be found at https://vulkan.lunarg.com/sdk/home#linux, with instructions at https://vulkan.lunarg.com/doc/sdk/latest/linux/getting_started.html

This may or may not be applicable, but it was suggested in this thread, so I tried it. Still no luck. However, upon attempting to run one of the examples included with the SDK, I got an error that lead me to this post: https://patchwork.freedesktop.org/patch/139829/

2) I enabled DRI3. The quickest advice I can give is to:

Code:

Code:

sudo nano /etc/X11/xorg.conf

if empty, put this block into file for Nvidia proprietary driver users:

Code:

Section "Device"
       Identifier "GTX 1060"
       Driver "nvidia"
       Option "DRI" "3"
EndSection

With whatever "name" you want to give your graphics card.

Or, for *OPEN SOURCE* AMD users:

Code:

Section "Device"
       Identifier "RX 480"
       Driver "amdgpu"
       Option "DRI" "3"
EndSection

If not empty, you might have to start reading up a bit more, but just adding that Option of DRI3 to the same section you see it in above would probably work. You will also have to find the correct Driver parameter if you are using amdgpu-pro, but I'd recommend upgrading with the Padoka PPA for AMD users and just using that anyway.

After you've made your edits, do a quick reboot and see what happens. By the way, I'd recommend the xorg.conf edit as step 1, as it is much quicker and easier than getting the Vulkan SDK installed.

If your xorg.conf is not empty, make a backup right next to it so you can just rename them in recovery mode if something goes wrong.