You are not logged in.
I have a ASUS AMD Radeon HD7850 1GB GDDR5 and I am pretty sure my GPU supports Vulkan.
In Windows I may need to lower the settings completely, but in the end I get respectable FPS. Although I try to open BeamNG.Drive and all I get is this:
"It is possible that your hardware/OS does not meet the minimum requirements. Please contact our support team."
At the moment I have the open source stable mesa driver installed, with amdvlk, both also chosen while installing Steam. I have tried using that and the propriotery driver, and all 3 implementations of Vulkan.
In AMDGPU page I went through the installation part and Enabling Southern Islands (SI) support.
There was another forum post covering this:
https://bbs.archlinux.org/viewtopic.php?id=253843
where I tried what he done while managing to fix nothing.
This is what I get when I type:
lspci -k | grep -A 3 -E "(VGA|3D)" 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Subsystem: ASUSTeK Computer Inc. Device 045b
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpuTyping:
vulkaninfo WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /usr/lib/amdvlk64.so. Skipping this driver.
ERROR: [Loader Message] Code 0 : terminator_CreateInstance: Found no drivers!
Cannot create Vulkan instance.
This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that does not support Vulkan.
ERROR at /usr/src/debug/vulkan-tools/Vulkan-Tools-1.3.269/vulkaninfo/./vulkaninfo.h:688:vkCreateInstance failed with ERROR_INCOMPATIBLE_DRIVERIrrelevant but now I am going to sleep right now it is 23:45 for me at the time I will post this and I am using the forum as my last resort. ![]()
EDIT: Alright.... If you read the last comments you can see that I reinstalled, and even then for some reason I was not able to get Vulkan to work. But I figured it out. The Radeon driver was running instead of amdgpu one so I had to do this:
I had to set module parameters like this:
sudo modprobe amdgpu radeon.si_support=0 amdgpu.si_support=1 sudo modprobe radeon radeon.cik_support=0 amdgpu.cik_support=0 .
After that, I set kernel parameters the simplest way possible (for myself), I opened:
/etc/default/grub and modified this:
Before:
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet" After:
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet radeon.cik_support=0 amdgpu.cik_support=0 radeon.si_support=0 amdgpu.si_support=1" Than in folder
/etc/modprobe.d/ I made 2 files 1 called
amdgpu.conf and typed this in:
options amdgpu si_support=1
options amdgpu cik_support=0and
radeon.conf Than I typed in:
options radeon si_support=0
options radeon cik_support=0After that, I went into the terminal and typed (not sure if I had to type both but oh well):
sudo mkinitcpio -p linux sudo mkinitcpio -P And make sure to install vulkan-radeon and lib32-vulkan-radeon it seems because amdvlk does not seem to work.
And after all that, sure enough, with the vulkan-radeon, I GOT EVERYTHING TO WORK!!! Reinstalling may not have been the wisest idea but at least now I know how to set up the driver and vulkan to work properly. ![]()
Last edited by BokeeXD (2025-01-04 13:36:33)
Offline
remove amdvlk & lib32-amdvlk, install vulkan-radeon & lib32-vulkan-radeon .
run and post the outputs of
$ vulkanifo --summary
$ pacman -Qs vulkanPlease use code-tags to make the outputs more readable, see https://bbs.archlinux.org/help.php#bbcode
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
HD7850 - release: 05. mar. 2012
recent versions dropped support for such old gpus
either use older drivers
or get a newer gpu
Offline
recent versions dropped support for such old gpus
Only rocm and amd proprietary drivers did, mesa and mesa parts like vulkan-radeon hasn't dropped them.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
remove amdvlk & lib32-amdvlk, install vulkan-radeon & lib32-vulkan-radeon .
run and post the outputs of
$ vulkanifo --summary $ pacman -Qs vulkanPlease use code-tags to make the outputs more readable, see https://bbs.archlinux.org/help.php#bbcode
WARNING: radv is not a conformant Vulkan implementation, testing use only.
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.295
Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_headless_surface : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 4
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
Instance Layers: count = 4
--------------------------
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
Devices:
========
GPU0:
apiVersion = 1.3.289
driverVersion = 24.2.3
vendorID = 0x1002
deviceID = 0x6819
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Radeon HD 7800 Series (RADV PITCAIRN)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 24.2.3-arch1.1
conformanceVersion = 0.0.0.0
deviceUUID = 00000000-0100-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000 local/lib32-vulkan-icd-loader 1.3.295-1
Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/lib32-vulkan-radeon 1:24.2.3-1
Open-source Vulkan driver for AMD GPUs - 32-bit
local/spirv-tools 2024.2-1 (vulkan-devel)
API and commands for processing SPIR-V modules
local/vulkan-headers 1:1.3.295-1 (vulkan-devel)
Vulkan header files
local/vulkan-icd-loader 1.3.295-1
Vulkan Installable Client Driver (ICD) Loader
local/vulkan-radeon 1:24.2.3-1
Open-source Vulkan driver for AMD GPUs
local/vulkan-tools 1.3.269-1 (vulkan-devel)
Vulkan Utilities and ToolsLast edited by BokeeXD (2024-09-23 09:48:42)
Offline
Looks ok now and things should be working, do they not?
Offline
It was that easy. THANK YOU SO MUCH NOW BEAMNG RUNS :DDDDD
Offline
Guess we reopening the thread. I installed Steam again (i briefly uninstalled it so I can get rid of amdvlk and lib32-amdvlk, but when I was installing it back it was not bothering about anything), installed Wine and dxvk, installed Flatpak so I can install Sober so my brother can play roblox on this and now I don't have working Vulkan.
[bokeexd@archlinux ~]$ lspci -k | grep -A 3 -E "(VGA|3D)"
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Subsystem: ASUSTeK Computer Inc. Device 045b
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu[bokeexd@archlinux ~]$ vulkaninfo --summary
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR at /usr/src/debug/vulkan-tools/Vulkan-Tools-1.3.269/vulkaninfo/./vulkaninfo.h:237:vkEnumeratePhysicalDevices failed with ERROR_INITIALIZATION_FAILED[bokeexd@archlinux ~]$ pacman -Qs vulkan
local/dxvk-bin 2.4-2
A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running
3D applications on Linux using Wine (Windows DLL binary files)
local/goverlay 1.2-1
A GUI to help manage Vulkan/OpenGL overlays
local/lib32-vulkan-icd-loader 1.3.295-1
Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/lib32-vulkan-radeon 1:24.2.3-1
Open-source Vulkan driver for AMD GPUs - 32-bit
local/mangohud 0.7.2-2
A Vulkan overlay layer for monitoring FPS, temperatures, CPU/GPU load and
more.
local/spirv-tools 2024.2-1 (vulkan-devel)
API and commands for processing SPIR-V modules
local/vulkan-headers 1:1.3.295-1 (vulkan-devel)
Vulkan header files
local/vulkan-icd-loader 1.3.295-1
Vulkan Installable Client Driver (ICD) Loader
local/vulkan-radeon 1:24.2.3-1
Open-source Vulkan driver for AMD GPUs
local/vulkan-tools 1.3.269-1 (vulkan-devel)
Vulkan Utilities and ToolsLast edited by BokeeXD (2024-09-23 11:22:49)
Offline
Where's goverlay coming from and what did you configure in it? Output of
printenv?
Offline
I guess that was the problem then.... I forgot to mention goverlay but it is over because I gave up and reinstalled, I really thought flatpak was the problem and even after removing it and everything related to it, vulkan still did not work.... Thanks a lot yall you really helped me here!
Offline
Reinstalling should be used as a last resort and if you don't understand the action you did to cause the issue you're bound to repeat them... Very likely incorrectly configured VK_DEVICE_DRIVER environment variable or similar.
Offline