Vulkan + AMD GPU

Hi again. I need help once more from you awesome people!

So i have been trying to make Vulkan work recently, but so far i have failed.

Graphics:  Card: Advanced Micro Devices [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series]
       Display Server: X.Org 1.18.4 drivers: ati,amdgpu (unloaded: fbdev,vesa,radeon)
       Resolution: [email protected]
       GLX Renderer: Gallium 0.4 on AMD FIJI (DRM 3.9.0 / 4.10.0-041000-lowlatency, LLVM 3.8.0)
       GLX Version: 3.0 Mesa 12.0.6

That’s my info, now i have tried various versions of Vulkan, but the result is always the same:


Vulkan API Version: 1.0.21

INFO: [loader] Code 0 : Found manifest file /home/x/.local/share/vulkan/implicit_layer.d/steamoverlay_x86_64.json, version "1.0.0"
INFO: [loader] Code 0 : Found manifest file /home/x/.local/share/vulkan/implicit_layer.d/steamoverlay_i386.json, version "1.0.0"
INFO: [loader] Code 0 : Found manifest file /usr/share/vulkan/icd.d/intel_icd.json, version "1.0.0"

Instance Extensions:
Instance Extensions	count = 3
	VK_KHR_surface                      : extension revision 25
	VK_KHR_xcb_surface                  : extension revision  5
	VK_EXT_debug_report                 : extension revision  3
/build/vulkan-jbbABz/vulkan- failed with VK_ERROR_INITIALIZATION_FAILED

Any ideas?

Additional info, the syslog revealed this happening during boot:

  kernel: [  716.363643] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
  kernel: [  716.363685] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
  kernel: [  716.560363] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
  kernel: [  716.560404] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed

Shot in the dark but do the same errors occur when using the latest generic kernel instead of low latency? I’m not seeing this issue with my RX 480 on UM 17.04.

Yeah, it was the same on the 4.4 generic kernel.

I had issues with amdgpu-pro and vulkan on 4.4. Now on 4.10 everything seems to be working well and vulkan installed easily through synaptic package manager. I haven’t tested it in game yet but it’s not showing any errors. Perhaps you could try the latest 4.10 generic kernel and see if that helps. Unfortunately I’m not sure what else could cause that specific error.


You were right, it does run on generic. How odd. But thank you!

1 Like

Glad you got it sorted out :slight_smile: