Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
22117 Discussions

Vulkan Loading Issues in Steam: Version Mismatch and Errors Ubuntu 24.1 | Kernel 6.13 | Messa 25-git

Posihdun
New Contributor I
2,580 Views
Environment
Linux  
 DistroUbuntu 24.10
 Kernel Build6.13.0-061300-generic
 Machine Targetx86_64
 Version#202501302155 SMP PREEMPT_DYNAMIC Sat Feb 8 09:06:55 UTC 2025
 DESKTOP_SESSIONubuntu-xorg
 DISPLAY:0
Hardware
CPUs16 
MemoryPhysical Available30 GB
System Disk SpaceFree315 GB
Current Dir Disk SpaceFree316G
Executable Info
Exe Directory/usr/bin
Current Directory/home/posihdun/vulkan/1.4.304.1
App VersionVersion 1.3
Vulkan API Version1.4.304
Byte Format64-bit



I’m encountering issues with Vulkan not loading in Steam what stops me from running games that require dx12, and I'm not sure how to troubleshoot the problem.

Steps Taken:

  • Tried to force Steam to use the system-wide Vulkan defaults.
  • Discovered that Steam was using an older version of Vulkan when installed via Snap or Flatpak.
  • Managed to get Steam (via the steam_installer.deb) to use the system-wide Vulkan, but I’m still getting the following error:
    • 'VK_KHR_surface'
    • 'VK_KHR_xlib_surface'
  • I also tried running Steam through Wine, but it fails to start entirely.
  • I downloaded Vulkan SDK and other tools to help with logging and debugging, but I haven’t made any progress.
  • I was able to run raytracing bench marks with Phoronixs, hitting 65-90FPS maxed out settings @ 1920*1080.

It seems like Vulkan is working, but there may be a mismatch between the version of Vulkan that Steam is using and the one installed on my system.

I should note that I downloaded Vulkan samples from Git, but only a few of them run. It’s possible I compiled the package incorrectly.

I've attached the HTML and JSON (converted to text file) with my GPU and system information.

Any insight or steps for debugging would be greatly appreciated!

INFO:
GPU INFO UPLOAD




Edit: I want to note I have followed these steps and still doesn't help
Intel Drivers 
INTEL GPU PREVIEW GIT 

- Steam loads up successfully and OpenGL is enabled, but Vulkan isn't. I can run benchmarks in Steam, but only for titles that use lower than DX12.

(Virus scan in progress ...)
0 Kudos
1 Solution
Posihdun
New Contributor I
306 Views

1000014748.jpg

Solved! Here's What Worked for Me:
==================================

This thread has gotten long, so I’m dropping the full solution here. After a lot of trial and error, I finally got everything working , and with that, I’m running the game smoothly!

 

Key Takeaways:
--------------
I tested Steam across Snap, .deb, and Flatpak versions, and here’s what I observed:

- Snap (Steam): Successfully builds GPU topology using Mesa driver 24 — decent performance.
- .deb (Steam): GPU topology refused to build no matter what I tried — completely broken for me.
- Flatpak (Steam): GPU topology builds successfully using Mesa driver 25, with  llvmpipe as a fallback.

 

System Info:
------------
Hardware:
- Motherboard: ASRock X570 Phantom Gaming 4
- CPU: AMD Ryzen™ 7 5800XT × 16
- GPU: Intel® Graphics (BMG G21)
- RAM: 32.0 GiB
- Storage: 2.5 TB

Software:
- Firmware: P5.63
- OS: Ubuntu 24.10 (64-bit)
- Kernel: Linux 6.14.1
- GNOME: Version 47
- Display Server: Wayland

 

OS: Freedesktop SDK 24.08 (Flatpak runtime)

KERNEL: 6.14.1-061401-generic

CPU: AMD Ryzen 7 5800XT 8-Core

GPU: Intel Mesa Intel (BMG G21)

GPU DRIVER: 4.6 Mesa 25.0.3 (git-c3afa2a74f)

RAM: 31 GB

 

The Breakthrough (Flatpak Fix):
-------------------------------
Initially, Flatpak Steam also wouldn't load GPU topology properly(at first). This started while I was trying to get Steam to recognize an external drive for games already installed on my system.

I installed and ran:

flatpak run com.github.tchx84.Flatseal

I used Flatseal to grant Steam Flatpak permissions to access the drive, but that still didn’t work. Frustrated, I hit the reset button in Flatseal , not knowing what it would do.

After that, I restarted Steam (Flatpak) and boom! GPU topology built successfully using the latest Mesa Vulkan drivers , no errors whatsoever.

 

FF7 Rebirth:
-------------------------
Even though other games started running flawlessly (no screen tearing, no weird issues), FF7 Rebirth still threw a DirectX error on launch.

So I dug deeper and added the following to the launch options:

VKD3D_CONFIG=dxr VKD3D_FEATURE_LEVEL=12_2 VKD3D_SHADER_MODEL=6_6 %command%

Launched the game , shaders started compiling , and minutes later I’m running around in the open world. Absolutely smooth!

 

Final Thoughts:
---------------
From my experience:

- Flatpak Steam = best choice. Clean, modern Mesa drivers. Easy to control permissions using Flatseal.
- Snap Steam = just okay. Some compatibility issues, but at least it builds GPU topology.
- .deb Steam = nightmare. Broken GPU detection, failed builds, and just generally not worth the hassle right now.

 

If you're on Ubuntu with newer hardware and using Mesa and VKD3D, I highly recommend Flatpak Steam paired with Flatseal for control.

Let me know if anyone needs help replicating this setup — happy to share more!

View solution in original post

0 Kudos
21 Replies
Posihdun
New Contributor I
2,424 Views
Executable Info😁
Exe Directory/usr/bin
Current Directory/home/posihdun/vulkan/1.4.304.1
App VersionVersion 1.3
Vulkan API Version1.4.304
Byte Format64-bit

 

 

 

Vulkan Driver Info
Standard Paths  
/etc/vulkan/icd.d  
/usr/share/vulkan/icd.d  
[0]radeon_icd.x86_64.json 
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so
[1]intel_hasvk_icd.x86_64.json 
 JSON File Version1.0.0
 API Version1.3.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_intel_hasvk.so
[2]virtio_icd.x86_64.json 
 JSON File Version1.0.0
 API Version1.3.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_virtio.so
[3]lvp_icd.x86_64.json 
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_lvp.so
[4]virtio_icd.i686.json 
 JSON File Version1.0.0
 API Version1.3.305
 Library Path/usr/lib/i386-linux-gnu/libvulkan_virtio.so
 FAILED TO LOAD!/usr/lib/i386-linux-gnu/libvulkan_virtio.so: wrong ELF class: ELFCLASS32
[5]radeon_icd.i686.json 
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/i386-linux-gnu/libvulkan_radeon.so
 FAILED TO LOAD!/usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
[6]intel_icd.x86_64.json 
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_intel.so
[7]intel_hasvk_icd.i686.json 
 JSON File Version1.0.0
 API Version1.3.305
 Library Path/usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so
 FAILED TO LOAD!/usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so: wrong ELF class: ELFCLASS32
[8]intel_icd.i686.json 
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/i386-linux-gnu/libvulkan_intel.so
 FAILED TO LOAD!/usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
[9]lvp_icd.i686.json 
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/i386-linux-gnu/libvulkan_lvp.so
 FAILED TO LOAD!/usr/lib/i386-linux-gnu/libvulkan_lvp.so: wrong ELF class: ELFCLASS32
[10]dzn_icd.x86_64.json 
 JSON File Version1.0.0
 API Version1.1.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_dzn.so
[11]nouveau_icd.x86_64.json 
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
/usr/local/etc/vulkan/icd.dNo such folder 
/usr/local/share/vulkan/icd.dNo such folder 
/home/posihdun/.local/share/vulkan/icd.dNo such folder 
VK_ICD_FILENAMES/usr/share/vulkan/icd.d/intel_icd.x86_64.json 
/usr/share/vulkan/icd.d/intel_icd.x86_64.json  
 JSON File Version1.0.0
 API Version1.4.305
 Library Path/usr/lib/x86_64-linux-gnu/libvulkan_intel.so

 

 

Vulkan Runtimes
Possible Runtime Folders  
/usr/lib  
 No libvulkan.so files found 
/usr/lib/x86_64-linux-gnu  
[0]/usr/lib/x86_64-linux-gnu/libvulkan.so.1libvulkan.so.1.4.304
/usr/lib64  
 No libvulkan.so files found 
/usr/local/lib  
[0]/usr/local/lib/libvulkan.so.1libvulkan.so.1.4.304
/usr/local/lib64No such folder 
Runtime Folder Used By via/usr/local/lib 
[0]/usr/local/lib/libvulkan.so.1libvulkan.so.1.4.304

 

 

Vulkan SDKs
System Installed SDKvulkan-sdk1.4.304.0~rc1-1lunarg24.04-1 
Vulkan Implicit Layers
/etc/vulkan/implicit_layer.dDirectory does not exist  
/usr/share/vulkan/implicit_layer.d   
[0]VkLayer_MESA_device_select.json  
  NameVK_LAYER_MESA_device_select
  DescriptionLinux device selection layer
  API Version1.4.303
  JSON File Version1.0.0
  Library PathlibVkLayer_MESA_device_select.so
  Enabled StateENABLED
 Enable Env Var--NONE--Not Defined
 Disable Env VarNODEVICE_SELECTNot Defined
/usr/local/etc/vulkan/implicit_layer.dDirectory does not exist  
/usr/local/share/vulkan/implicit_layer.dDirectory does not exist  
/home/posihdun/.local/share/vulkan/implicit_layer.d   
[1]steamfossilize_i386.json  
  NameVK_LAYER_VALVE_steam_fossilize_32
  DescriptionSteam Pipeline Caching Layer
  API Version1.3.207
  JSON File Version1.0.0
  Library Path/home/posihdun/.local/share/Steam/ubuntu12_32/libVkLayer_steam_fossilize.so
  Enabled StateDISABLED
 Enable Env VarENABLE_VK_LAYER_VALVE_steam_fossilize_1Not Defined
 Disable Env VarDISABLE_VK_LAYER_VALVE_steam_fossilize_1Not Defined
[2]steamfossilize_x86_64.json  
  NameVK_LAYER_VALVE_steam_fossilize_64
  DescriptionSteam Pipeline Caching Layer
  API Version1.3.207
  JSON File Version1.0.0
  Library Path/home/posihdun/.local/share/Steam/ubuntu12_64/libVkLayer_steam_fossilize.so
  Enabled StateDISABLED
 Enable Env VarENABLE_VK_LAYER_VALVE_steam_fossilize_1Not Defined
 Disable Env VarDISABLE_VK_LAYER_VALVE_steam_fossilize_1Not Defined
[3]steamoverlay_i386.json  
  NameVK_LAYER_VALVE_steam_overlay_32
  DescriptionSteam Overlay Layer
  API Version1.3.207
  JSON File Version1.0.0
  Library Path/home/posihdun/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so
  Enabled StateDISABLED
 Enable Env VarENABLE_VK_LAYER_VALVE_steam_overlay_1Not Defined
 Disable Env VarDISABLE_VK_LAYER_VALVE_steam_overlay_1Not Defined
[4]steamoverlay_x86_64.json  
  NameVK_LAYER_VALVE_steam_overlay_64
  DescriptionSteam Overlay Layer
  API Version1.3.207
  JSON File Version1.0.0
  Library Path/home/posihdun/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so
  Enabled StateDISABLED
 Enable Env VarENABLE_VK_LAYER_VALVE_steam_overlay_1Not Defined
 Disable Env VarDISABLE_VK_LAYER_VALVE_steam_overlay_1Not Defined

 

 

 

Vulkan Explicit

Layers

VK_LAYER_PATH   
 Path 0/usr/share/vulkan/explicit_layer.d 
 [0]VkLayer_INTEL_nullhw.json 
  NameVK_LAYER_INTEL_nullhw
  DescriptionINTEL NULL HW
  API Version1.1.73
  JSON File Version1.0.0
  Library PathlibVkLayer_INTEL_nullhw.so
 [1]VkLayer_khronos_validation.json 
  NameVK_LAYER_KHRONOS_validation
  DescriptionKhronos Validation Layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_validation.so
  Device Extensions3
  [0]VK_EXT_debug_marker
  [0]VK_EXT_validation_cache
  [0]VK_EXT_tooling_info
  Instance Extensions4
  [0]VK_EXT_debug_report
  [0]VK_EXT_debug_utils
  [0]VK_EXT_layer_settings
  [0]VK_EXT_validation_features
 [2]VkLayer_khronos_profiles.json 
  NameVK_LAYER_KHRONOS_profiles
  DescriptionKhronos Profiles layer
  API Version1.4.304
  JSON File Version1.2.1
  Library PathlibVkLayer_khronos_profiles.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [3]VkLayer_khronos_synchronization2.json 
  NameVK_LAYER_KHRONOS_synchronization2
  DescriptionKhronos Synchronization2 layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_synchronization2.so
  Device Extensions1
  [0]VK_KHR_synchronization2
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [4]VkLayer_api_dump.json 
  NameVK_LAYER_LUNARG_api_dump
  DescriptionLunarG API dump layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_api_dump.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [5]VkLayer_MESA_overlay.json 
  NameVK_LAYER_MESA_overlay
  DescriptionMesa Overlay layer
  API Version1.4.303
  JSON File Version1.0.0
  Library PathlibVkLayer_MESA_overlay.so
 [6]VkLayer_khronos_shader_object.json 
  NameVK_LAYER_KHRONOS_shader_object
  DescriptionKhronos Shader object layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_shader_object.so
  Device Extensions1
  [0]VK_EXT_shader_object
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [7]VkLayer_monitor.json 
  NameVK_LAYER_LUNARG_monitor
  DescriptionExecution Monitoring Layer
  API Version1.4.304
  JSON File Version1.0.0
  Library PathlibVkLayer_monitor.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [8]VkLayer_crash_diagnostic.json 
  NameVK_LAYER_LUNARG_crash_diagnostic
  DescriptionCrash Diagnostic Layer is a crash/hang debugging tool that helps determines GPU progress in a Vulkan application.
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_crash_diagnostic.so
  Device Extensions2
  [0]VK_EXT_debug_report
  [0]VK_EXT_tooling_info
  Instance Extensions3
  [0]VK_EXT_debug_report
  [0]VK_EXT_debug_utils
  [0]VK_EXT_layer_settings
 [9]VkLayer_gfxreconstruct.json 
  NameVK_LAYER_LUNARG_gfxreconstruct
  DescriptionGFXReconstruct Capture Layer Version 1.0.5-unknown
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_gfxreconstruct.so
  Device Extensions1
  [0]VK_EXT_tooling_info
 [10]VkLayer_screenshot.json 
  NameVK_LAYER_LUNARG_screenshot
  DescriptionLunarG image capture layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_screenshot.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
Standard Paths   
 /etc/vulkan/etc/vulkan/explicit_layer.dNo such folder
 /usr/share/vulkan/usr/share/vulkan/explicit_layer.d 
 [0]VkLayer_INTEL_nullhw.json 
  NameVK_LAYER_INTEL_nullhw
  DescriptionINTEL NULL HW
  API Version1.1.73
  JSON File Version1.0.0
  Library PathlibVkLayer_INTEL_nullhw.so
 [1]VkLayer_khronos_validation.json 
  NameVK_LAYER_KHRONOS_validation
  DescriptionKhronos Validation Layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_validation.so
  Device Extensions3
  [0]VK_EXT_debug_marker
  [0]VK_EXT_validation_cache
  [0]VK_EXT_tooling_info
  Instance Extensions4
  [0]VK_EXT_debug_report
  [0]VK_EXT_debug_utils
  [0]VK_EXT_layer_settings
  [0]VK_EXT_validation_features
 [2]VkLayer_khronos_profiles.json 
  NameVK_LAYER_KHRONOS_profiles
  DescriptionKhronos Profiles layer
  API Version1.4.304
  JSON File Version1.2.1
  Library PathlibVkLayer_khronos_profiles.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [3]VkLayer_khronos_synchronization2.json 
  NameVK_LAYER_KHRONOS_synchronization2
  DescriptionKhronos Synchronization2 layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_synchronization2.so
  Device Extensions1
  [0]VK_KHR_synchronization2
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [4]VkLayer_api_dump.json 
  NameVK_LAYER_LUNARG_api_dump
  DescriptionLunarG API dump layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_api_dump.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [5]VkLayer_MESA_overlay.json 
  NameVK_LAYER_MESA_overlay
  DescriptionMesa Overlay layer
  API Version1.4.303
  JSON File Version1.0.0
  Library PathlibVkLayer_MESA_overlay.so
 [6]VkLayer_khronos_shader_object.json 
  NameVK_LAYER_KHRONOS_shader_object
  DescriptionKhronos Shader object layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_shader_object.so
  Device Extensions1
  [0]VK_EXT_shader_object
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [7]VkLayer_monitor.json 
  NameVK_LAYER_LUNARG_monitor
  DescriptionExecution Monitoring Layer
  API Version1.4.304
  JSON File Version1.0.0
  Library PathlibVkLayer_monitor.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [8]VkLayer_crash_diagnostic.json 
  NameVK_LAYER_LUNARG_crash_diagnostic
  DescriptionCrash Diagnostic Layer is a crash/hang debugging tool that helps determines GPU progress in a Vulkan application.
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_crash_diagnostic.so
  Device Extensions2
  [0]VK_EXT_debug_report
  [0]VK_EXT_tooling_info
  Instance Extensions3
  [0]VK_EXT_debug_report
  [0]VK_EXT_debug_utils
  [0]VK_EXT_layer_settings
 [9]VkLayer_gfxreconstruct.json 
  NameVK_LAYER_LUNARG_gfxreconstruct
  DescriptionGFXReconstruct Capture Layer Version 1.0.5-unknown
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_gfxreconstruct.so
  Device Extensions1
  [0]VK_EXT_tooling_info
 [10]VkLayer_screenshot.json 
  NameVK_LAYER_LUNARG_screenshot
  DescriptionLunarG image capture layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_screenshot.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 /usr/local/etc/vulkan/usr/local/etc/vulkan/explicit_layer.dNo such folder
 /usr/local/share/vulkan/usr/local/share/vulkan/explicit_layer.d 
 [0]VkLayer_khronos_validation.json 
  NameVK_LAYER_KHRONOS_validation
  DescriptionKhronos Validation Layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_validation.so
  Device Extensions3
  [0]VK_EXT_debug_marker
  [0]VK_EXT_validation_cache
  [0]VK_EXT_tooling_info
  Instance Extensions4
  [0]VK_EXT_debug_report
  [0]VK_EXT_debug_utils
  [0]VK_EXT_layer_settings
  [0]VK_EXT_validation_features
 [1]VkLayer_khronos_profiles.json 
  NameVK_LAYER_KHRONOS_profiles
  DescriptionKhronos Profiles layer
  API Version1.4.304
  JSON File Version1.2.1
  Library PathlibVkLayer_khronos_profiles.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [2]VkLayer_khronos_synchronization2.json 
  NameVK_LAYER_KHRONOS_synchronization2
  DescriptionKhronos Synchronization2 layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_synchronization2.so
  Device Extensions1
  [0]VK_KHR_synchronization2
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [3]VkLayer_api_dump.json 
  NameVK_LAYER_LUNARG_api_dump
  DescriptionLunarG API dump layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_api_dump.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [4]VkLayer_khronos_shader_object.json 
  NameVK_LAYER_KHRONOS_shader_object
  DescriptionKhronos Shader object layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_khronos_shader_object.so
  Device Extensions1
  [0]VK_EXT_shader_object
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [5]VkLayer_monitor.json 
  NameVK_LAYER_LUNARG_monitor
  DescriptionExecution Monitoring Layer
  API Version1.4.304
  JSON File Version1.0.0
  Library PathlibVkLayer_monitor.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 [6]VkLayer_crash_diagnostic.json 
  NameVK_LAYER_LUNARG_crash_diagnostic
  DescriptionCrash Diagnostic Layer is a crash/hang debugging tool that helps determines GPU progress in a Vulkan application.
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_crash_diagnostic.so
  Device Extensions2
  [0]VK_EXT_debug_report
  [0]VK_EXT_tooling_info
  Instance Extensions3
  [0]VK_EXT_debug_report
  [0]VK_EXT_debug_utils
  [0]VK_EXT_layer_settings
 [7]VkLayer_gfxreconstruct.json 
  NameVK_LAYER_LUNARG_gfxreconstruct
  DescriptionGFXReconstruct Capture Layer Version 1.0.5
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_gfxreconstruct.so
  Device Extensions1
  [0]VK_EXT_tooling_info
 [8]VkLayer_screenshot.json 
  NameVK_LAYER_LUNARG_screenshot
  DescriptionLunarG image capture layer
  API Version1.4.304
  JSON File Version1.2.0
  Library PathlibVkLayer_screenshot.so
  Device Extensions1
  [0]VK_EXT_tooling_info
  Instance Extensions1
  [0]VK_EXT_layer_settings
 $HOME/.local/share/vulkan/explicit_layer.d/home/posihdun/.local/share/vulkan/explicit_layer.dNo such folder
0 Kudos
Earl_Intel
Moderator
2,395 Views

Hi Posihdun,


Thank you for posting in the communities!


I'm sorry to hear that your system is giving you trouble. Please supply the information requested here so that we may better assist you and identify the best course of action. We can better adapt our service to your unique circumstances with the use of this information:


  • Have you tried updating your Graphics Drivers to the latest version?
  • is your system working fine before you encounter this issue? if yes, what are the changes on the system before the issue happen?


Also, kindly run this on your system so that I can also gauge the following peripherals and the driver versions that you have:

Intel® System Support Utility for Windows*

Once finished downloading, open the tool, click on scan (leave the default items checked), click next, then save the system information to a .txt file. Please provide us the .txt file.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Posihdun
New Contributor I
2,351 Views

First of all, I am using Ubuntu and have tested my GPU in Windows, where it functions without issues.

When I first installed my GPU, I was running Ubuntu 24.04 with Kernel 6.8, but the card was not cooperating with my system at all. After updating to Ubuntu 24.10 and the latest Kernel 6.13, my system was able to utilize the card properly.

However, the issue arises when trying to load applications that require DirectX 12 (Dx12) aka Vulkan in steam. This might be beyond the scope of this forum, but I wanted to see if anyone has insights on potential solutions.

For reference, my GPU works perfectly fine for development tasks such as Android development and other workloads without any issues.


System Details

Hardware Information:

  • Motherboard: ASRock X570 Phantom Gaming 4
  • Memory: 32.0 GiB
  • Processor: AMD Ryzen™ 7 5800XT (16 Threads)
  • Graphics: Intel® Graphics (BMG G21)
  • Storage: 2.5 TB

Software Information:

  • Firmware Version: P5.63
  • OS: Ubuntu 24.10 (64-bit)
  • GNOME Version: 47
  • Windowing System: Wayland
  • Kernel Version: Linux 6.13.0-061300-generic

Any suggestions or insights would be greatly appreciated!

0 Kudos
Earl_Intel
Moderator
2,329 Views

Hello Posihdun,


Thank you for sharing this information with us.


No worries, I'll check on this internally and provide you an insight on this thread as soon as I can.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Posihdun
New Contributor I
2,288 Views
I will also note that I thought there was some sort of driver mismatch or some sort of mismatch of something within the operating system so I reinstalled a Ubuntu for a clean state.
0 Kudos
Earl_Intel
Moderator
2,121 Views

Hello Posihdun,


I just have a few clarifications regarding to the issue:

  • May I know if you're a game developer or application developer? are you trying to develop a game or application?


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Posihdun
New Contributor I
2,112 Views
I'm a application developer but not in this domain.. I'm just trying to play FF7 rebirth with my new GPU in Ubuntu.... I will mention though that this whole ordeal has got me very interested into driver development for gpus and I've been up day and night trying to figure out why my system isn't loading Vulkan so I can play games that require dx12.
0 Kudos
Earl_Intel
Moderator
2,049 Views

Hello Posihdun,


Thank you for clarifying this with us.


Noted on this, I will further check what I can do on the issue you brought up.


I'll provide you an update on this thread as soon as possible.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
JeanetteC_Intel
Moderator
1,934 Views

Hello Posihdun,


As this issue is still being investigated, I need to confirm which other games besides Final Fantasy 7 Rebirth is having issues with launching from Steam in Ubuntu. Kindly verify if you have enabled Proton compatibility in Steam as well and if so, which versions have you tried using.


I will wait for your reply.



Best regards,

JeanetteC.

Intel Customer Support Technician



0 Kudos
Posihdun
New Contributor I
1,924 Views

Any game that requires DX12 will not run....

Proton compatibility Later has been enabled. I've tried:
     Proton 6 and higher
     Proton experimental | HotFix
     Proton Glorious EggRoll
None of these are working.

0 Kudos
JeanetteC_Intel
Moderator
1,838 Views

Hello Posihdun,

 

I'll take note of this and will continue with the further investigation of this issue. I'll reach out to you in case more details are needed and will post an update once available.

 

Best regards,

JeanetteC.

Intel Customer Support Technician


0 Kudos
Earl_Intel
Moderator
1,698 Views

Hi Posihdun,


Thank you for patiently waiting.


I was unable to reproduce the issue. I was able to run 2 DirectX 12 games correctly on Ubuntu 24.10 and Intel Arc B580 GPU.


* For this test I followed these steps:

  1. Started on a fresh Ubuntu installation
  2. Then followed by adding the Intel drivers as noted here: Installing Client GPUs — Intel® software for general purpose GPU capabilities documentation
  3. Restart
  4. Installed Steam and let it update.
  5. In Steam -] Compatibility -] Enabled Proton.
  6. Installed Age of Empires 2 and Cyberpunk 2077.


Recording my test here: Ubuntu 24.10 - DIrectX 12 Steam games test - Arc B580 GPU


For reference I'm attaching .txt files for Intel SSU, vulkaninfo report and clinfo so you can compare and check for differences.


If issue persists, then I suggest following the same steps as outlined above and re-test.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Posihdun
New Contributor I
1,688 Views

Hey I can't find the .txt file and also can you share the system info provided from steam.
steam--->help--->systeminfo

How did you install steam?


0 Kudos
Earl_Intel
Moderator
1,628 Views

Hello Podishdun,


Thanks for the response.


I'll check internally if I can gather the steps on how to install Steam and the system info provided by Steam.


I'll share an update on this thread as soon as I can.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Earl_Intel
Moderator
1,443 Views

Hi Podishdun,

 

Thanks for patiently waiting.

 

Steam was installed by downloading the latest .deb file from the steam website -] double-clicking on it so it opened the installer from the App Center.

Attached are the required files from Steam, SSU and vulkantools.

 

Best regards,

Earl E.

Intel Customer Support Technician

 

(Virus scan in progress ...)
0 Kudos
Posihdun
New Contributor I
1,363 Views

I've matched the drivers and settings to your setup but still can't get the game to load. After checking other sources, it seems like others are experiencing the same issue.

At this point, I haven't been able to find a solution, so I think we can close this thread as unresolved. I'll continue troubleshooting and may need bark up  Steam/Valve tree for further answers.

I really appreciate your assistance—this process has been incredibly valuable, and I've learned a lot along the way.

I should note that Vulkan works fine, and I'm able to run benchmark tests locally. This leads me to believe the issue is more on Steam/Valve and Square Enix's end, specifically regarding the Arc B580's inability to launch Final Fantasy 7 Rebirth.

0 Kudos
VonM_Intel
Moderator
1,164 Views

Hello, Podishdun.

Thank you for your detailed update. I understand how frustrating it can be to encounter such persistent issues, especially after matching drivers and settings. It's helpful to know that others are experiencing the same problem, which suggests a broader compatibility issue. Given that Vulkan works fine and you're able to run benchmark tests locally, it does seem likely that the issue lies with Steam/Valve and Square Enix's handling of the Intel Arc B580 for Final Fantasy 7 Rebirth. I appreciate your patience and the troubleshooting efforts you've made so far.


Closing this thread as unresolved is understandable. However, let me see what I can do for this case. I'll conduct additional research on this matter and will post an update in this thread once I have more information.


Best regards,

Von M.

Intel Customer Support Technician


0 Kudos
Posihdun
New Contributor I
1,120 Views

From analyzing the logs in the attached images, I’ve pinpointed potential key issues affecting Steam and the game launch:

1. Vulkan Initialization Failure 

  • Vulkan missing requested extension 'VK_KHR_surface'
  • Vulkan missing requested extension 'VK_KHR_xlib_surface'
  • BInit - Unable to initialize Vulkan!

2. Incorrect ELF Class for Steam Overlay

The second image highlights a compatibility issue: Note I am using Proton

  • ERROR: ld.so: object '/home/posihdun/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

This error occurs because Steam is attempting to load a 32-bit shared object (.so file) on a 64-bit system. Since the game may require 32-bit libraries, this mismatch could be causing instability.

3. Wine and D3D12 Issues

The logs also mention:

  • Steam_SetMinidumpSteamID: Caching Steam ID: 76561198148174804 [API loaded no]
  • wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
  • Initializing D3D12.
  • Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpath
  • Fossilize INFO: Overriding serialization path: "/home/posihdun/.local/share/Steam/shader_cache_temp_dir_d3d12_64/fozpipelinesv6/steamapprun_pipeline_cache".

 

The primary issue appears to be Vulkan failing to initialize, likely due to missing drivers or improperly installed Vulkan support. The secondary issue is the ELF class mismatch, where Steam is attempting to load 32-bit components on a 64-bit system. These two problems combined are likely preventing the game from launching properly.

0 Kudos
Earl_Intel
Moderator
995 Views

Hi Posihdun,


Thanks for sharing this useful information with us.


Upon further checking, it will be beneficial for you to continue the investigation by contacting Steam/Valve.


It would also help to share this thread to the Steam/Valve to speed up their investigation since you already provided a wealth of information on the troubleshooting process that you undertook to address the issue.


If you need further assistance, please submit a new question as this thread will no longer be monitored.

 

Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Posihdun
New Contributor I
232 Views
0 Kudos
Reply