| View previous topic :: View next topic |
| Author |
Message |
bulkin
n00b
Joined: 08 Nov 2008
Posts: 20
|
 Posted: Mon Jan 20, 2020 10:28 pm Post subject: |
 |
|
Mesa should be built with vulkan support, then vulkan-loader should succeed in finding radv.
| Code: |
bulkin@bc:~$ vulkaninfo
ERROR: [Loader Message] Code 0 : libGLX_nvidia.so.0: cannot open shared object file: No such file or directory
ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
WARNING: radv is not a conformant vulkan implementation, testing use only.
|
|
|
| Back to top |
|
 |
davydm
n00b
Joined: 06 Jan 2017
Posts: 73
|
| Posted: Tue Jan 21, 2020 3:26 am Post subject: |
|
|
Before completing a cleanup of nvidia drivers, I had this:
| Code: |
$ eselect opengl list
Available OpenGL implementations:
[1] nvidia
[2] xorg-x11 *
|
(ie, correct opengl selected); however vulkaninfo kept trying to use libGLX from nvidia. So having done
| Code: |
emerge --depclean nv-codec-headers nvidia-drivers
|
(nv-codec-headers was pulling in nvidia drivers), I now have an nvidia-free system and vulkaninfo errors with:
| Code: |
$ vulkaninfo
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.
/var/tmp/portage/dev-util/vulkan-tools-1.1.124/work/Vulkan-Tools-119e7c3bbae122f6cc5d778d068fb91e0e85d6a9/vulkaninfo/vulkaninfo.h:291: failed with ERROR_INCOMPATIBLE_DRIVER
|
naturally, there's only one opengl implementation now, and it's selected:
| Code: |
$ eselect opengl list
Available OpenGL implementations:
[1] xorg-x11 *
|
The problem now isn't opengl -- native opengl games (eg quake3) are working fine, high framerate and glxinfo reports (amongst a lot of other data):
| Code: |
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD NAVI10 (DRM 3.35.0, 5.4.13-gentoo-x86_64, LLVM 9.0.1) (0x731f)
Version: 19.3.2
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 4.5
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
|
My current challenge is to get vulkan working since the proton compatibility tool (and other native games like Rise Of The Tomb Raider) depends on it. Searching a bit more after last night, it seems that "radv" is the radeonsi vulkan implementation that should be in mesa, and I've seen a report at Phoronix of mesa 20.0 outperforming the closed-source amdgpu-pro driver in recent vulkan testing (https://www.phoronix.com/scan.php?page=article&item=mesa20radv-aco-amdvlk&num=1). I don't see a release for version 20 of mesa, even at GitHub (https://github.com/mesa3d/mesa/releases): latest there is 19.3.2 -- same version I currently have installed, so this is leading me to believe that either I should wait for 20.0 to drop or give mesa-9999 a go. I'd really appreciate input on this -- I'm not sure if I'm on the right track, really, mostly guessing. |
|
| Back to top |
|
|
davydm
n00b
Joined: 06 Jan 2017
Posts: 73
|
| Posted: Tue Jan 21, 2020 3:57 am Post subject: |
|
|
Thanks for all the help, everyone. I haven't been sleeping properly for the last few weeks and it shows. I could have sworn I read the use flags for mesa many many times without spotting:
| Code: |
vulkan : Enable Vulkan drivers
|
setting that on, rebuilding mesa & rebooting to ensure it's correctly loaded and vulkaninfo is happy with me:
| Code: |
Vulkan Instance Version: 1.1.125
|
and Hellblade starts up fine.
Thanks again for all the help. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
