Vulkan not working with Blender after latest stable branch update

After some testing, I found that the Blender binary (downloaded from the official website) no longer works when using the Vulkan backend after installing the 580 driver, throwing the error:

00:00.547  ghost.context    | ERROR Vulkan: vkCreateSwapchainKHR(device_vk.vk_device, &create_info, nullptr, &swapchain_) resulted in code VK_ERROR_INITIALIZATION_FAILED.

Re-installing the driver had no effect.

Update: The Blender package from the Manjaro repos has the same issue. Setting the backend to OpenGL works fine, but when setting it to Vulkan, the application fails to draw a window.

It still appears to be running in the background, and nvidia-smi reports allocating GPU memory for the app, but no window opens.

Update 2: It appears to be a Vulkan specific issue with the Nvidia 580 driver, as 575 did not cause this issue.

vkcube

Selected WSI platform: wayland
zsh: segmentation fault (core dumped)  vkcube

vkcube --gpu_number 0

Selected WSI platform: wayland
Selected GPU 0: NVIDIA GeForce GTX 1050 Ti, type: DiscreteGpu
Could not find both graphics and present queues
vkcube --gpu_number 1

Selected WSI platform: wayland
GPU 1 specified is not present, GPU count = 1
Specified GPU number is not present

I reported non-functioning Vulkan on the Nvidia 580 driver 4 days ago, and I still haven’t received even an acknowledgement of the issue.

Can anyone respond, and report what can be done here?


Mod edit:- Please avoid consecutive posts. Corrected. No charge.

It is simple @campfire. Since you have an very old NVIDIA GeForce GTX 1050 Ti, you may consider to update your hardware to some GFX from AMD, which is much better supported. Otherwise you can always report your issues to NVIDIA and hope they might fix it at some point: 580 release feedback & discussion - Linux - NVIDIA Developer Forums. Simply don’t expect fixes from us when NVIDIA doesn’t provide any yet …

2 Likes

Since there are no reports of a complete loss of Vulkan function on the NVIDIA forums, this suggests that there is no issue with the driver itself.

Also, the age of the hardware is of no relevance when the driver is still officially supported by the manufacturer.

1 Like

Is this driver being updated to work with current or up-coming Kernel versions, though? :thinking:

You may not be aware of the current GTX 1050 support status.

From the compatibility list I keep locally, the last driver release to support the GeForce GTX 1050 Ti was:

Though, I believe the 580xx series did also.

If Nvidia is true to their established history of
The GeForce GTX 1050 Ti is a member of the GeForce 10 Pascal family and has been considered Legacy for a long time. With the 590xx driver release series it has been dropped from the Nvidia support list.

If Nvidia remains true to their historical treatment of support for legacy hardware, then updating your hardware to generally more compatible AMD graphics is a more than valid consideration.

Regards.

1 Like

From what i read, 6.18 will be the last kernel to support the old drivers, which support the old cards. Another thing to consider.

1 Like

May be relevant: I see mesa 26.1 has updated Vulkan support and functionality. Mesa 26.1 is out and can be downloaded. I am using it myself right now. Not NVIDIA per se, but perhaps worth looking into.

Alright, so to address the issue of the non-functioning driver, I first switched to the Unstable branch of Manjaro to get the packages as close to mainline Arch as possible.

As expected however, this did not address the issue, as vkcube continued to fail to run.


Then, I wiped out my Manjaro installation, installed CachyOS in its place, and without having to do anything else…

…the driver is fully functional.

On both the LTS kernel…

…and even on the stable kernel.


As I already strongly suspected and hinted at, it appears that the Nvidia 580 driver is incorrectly packaged/configured on Manjaro, which is why Vulkan functionality was lost completely after the upgrade from 575.

A significant bug, which would’ve been reported and fixed months ago by the manufacturer if it had been caused by the driver itself.

Rather, using the same kernel and driver version on CachyOS as I did on Manjaro, there are no issues on CachyOS.

Naturally, this concludes my presence on the Manjaro forums. Goodbye.

Fresh installation of different distro “resolved the issue”.