You are not logged in.

#1 2020-04-18 03:30:39

ephreal
Member
Registered: 2014-03-29
Posts: 35

[SOLVED] nvidia vulkaninfo errors

Hey all,

I'm trying to get vulkan working in order to play a few games through steam. I've verified that I have the packages from https://wiki.archlinux.org/index.php/Vulkan installed. I found a few other posts here, but they both dealt with AMD rather than nvidia.

Here is the hardware info

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] (rev a1)

and the errors from vulkaninfo

$ vulkaninfo
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.135/vulkaninfo/vulkaninfo.h:240:vkEnumerateInstanceExtensionProperties failed with ERROR_INITIALIZATION_FAILED

I've verified the icd file exists

cat /usr/share/vulkan/icd.d/nvidia_icd.json
{
    "file_format_version" : "1.0.0",
    "ICD": {
        "library_path": "libGLX_nvidia.so.0",
        "api_version" : "1.1.119"
    }
}

If there's any other info you need, just let me know.

[EDIT]

To resolve this, first verify that your graphics card is in use with

glxinfo -B

If that does not show nvidia being used, follow the instructions on https://wiki.archlinux.org/index.php/NV … phics_only to ensure that nvidia is being used.
If your graphics card is newer, use the instructions at https://wiki.archlinux.org/index.php/PR … er_offload instead.
Verify that your display manager is using xorg as the backend and then try run vulkaninfo again.

Last edited by ephreal (2020-04-18 16:39:39)

Offline

#2 2020-04-18 12:29:36

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: [SOLVED] nvidia vulkaninfo errors

Look at the troubleshooting section of that wiki page.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2020-04-18 14:20:12

ephreal
Member
Registered: 2014-03-29
Posts: 35

Re: [SOLVED] nvidia vulkaninfo errors

Hi Lone Wolf,

I did follow those instructions too when I was troubleshooting. running vulkaninfo throws the same error even after any changes. Here's the results because it looks like I did not have them in the initial post.

$ pacman -Qi vulkan-intel
error: package 'vulkan-intel' was not found

$ VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json
$ vulkaninfo
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.135/vulkaninfo/vulkaninfo.h:240:vkEnumerateInstanceExtensionProperties failed with ERROR_INITIALIZATION_FAILED

$ export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json:/usr/share/vulkan/icd.d/primus_vk_wrapper.json
$ vulkaninfo
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.135/vulkaninfo/vulkaninfo.h:240:vkEnumerateInstanceExtensionProperties failed with ERROR_INITIALIZATION_FAILED

Offline

#4 2020-04-18 14:50:05

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,427

Re: [SOLVED] nvidia vulkaninfo errors

How is your system in general configured? Are you actually driving the display with nvidia? What's your glxinfo -B output? If you did not follow anything from https://wiki.archlinux.org/index.php/NVIDIA_Optimus you are likely running off of the intel card.

Offline

#5 2020-04-18 15:15:44

ephreal
Member
Registered: 2014-03-29
Posts: 35

Re: [SOLVED] nvidia vulkaninfo errors

Hi V1del,

I think you're right on intel being the only thing running. I'll walk through those steps on the nvidia optimus page and post back with what happens.

Here's the output of glxinfo, and it does seem to indicate Intel is the only graphics card being used.

$ glxinfo -B
name of display: :1
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b)
    Version: 20.0.4
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Offline

#6 2020-04-18 15:37:53

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,427

Re: [SOLVED] nvidia vulkaninfo errors

With a graphics card this new you will likely get the best results using the official PRIME support: https://wiki.archlinux.org/index.php/PR … er_offload

Note that any of these solutions will only reliably work on pure xorg sessions, so if you are currently using a form of wayland you must switch to a xorg based session.

Offline

#7 2020-04-18 16:22:27

ephreal
Member
Registered: 2014-03-29
Posts: 35

Re: [SOLVED] nvidia vulkaninfo errors

Hi V1del,

I'll give that a look. In additional news, when I rebooted this time, I had some messages about nvidia-gpu catch my eye. I suspect something is keeping the nvidia card from being usable as grepping for nvidia in glxinfo shows nothing while grepping for intel does.
Here's the part of the dmesg output that showing the error.

$ dmesg | grep nvidia
[    6.559353] nvidia-nvlink: Nvlink Core is being initialized, major device number 236
[    6.559596] nvidia 0000:01:00.0: enabling device (0106 -> 0107)
[    6.559692] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
[    6.644923] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  440.82  Wed Apr  1 19:41:29 UTC 2020
[    6.726998] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    6.726999] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1
[    6.794682] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000

Offline

#8 2020-04-18 16:37:08

ephreal
Member
Registered: 2014-03-29
Posts: 35

Re: [SOLVED] nvidia vulkaninfo errors

And with the changes for prime offloading completed along with changing from Gnome wayland to Gnome xorg, this is now running vulkaninfo properly.

$ vulkaninfo
==========
VULKANINFO
==========

Vulkan Instance Version: 1.2.135


Instance Extensions: count = 17
===============================
        VK_EXT_acquire_xlib_display            : extension revision 1
        VK_EXT_debug_report                    : extension revision 9
        VK_EXT_debug_utils                     : extension revision 1
        VK_EXT_direct_mode_display             : extension revision 

# Not including the rest of this as it gets long
$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 8192 MB
    Currently available dedicated video memory: 7286 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 440.82
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 440.82
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 440.82
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Games are not playing properly yet, but I suspect this is now a separate issue. I'll work on troubleshooting that and message on the boards again if I get stuck.
Thank you for your help!

Offline

Board footer

Powered by FluxBB