Package Details: nvidia-vulkan-utils 535.43.09-1

Git Clone URL: https://aur.archlinux.org/nvidia-vulkan.git (read-only, click to copy)
Package Base: nvidia-vulkan
Description: NVIDIA drivers utilities
Upstream URL: https://developer.nvidia.com/vulkan-driver
Licenses: custom
Conflicts: nvidia-libgl, nvidia-settings, nvidia-utils
Provides: nvidia-libgl, nvidia-settings, nvidia-utils, opengl-driver, vulkan-driver
Replaces: nvidia-libgl
Submitter: jcstryker
Maintainer: jcstryker
Last Packager: jcstryker
Votes: 31
Popularity: 0.000005
First Submitted: 2018-06-23 01:17 (UTC)
Last Updated: 2023-09-05 03:22 (UTC)

Dependencies (10)

Required by (309)

Sources (4)

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 Next › Last »

Nocifer commented on 2018-11-14 15:25 (UTC)

@wyre what do you mean? Of course I applied the patches, that's how I managed to build the package, I just didn't provide the modified PKGBUILD and the two patch files because I wanted to wait for a response from @jcstryker first.

Also, what kind of error does your pacman return? In my case everything built smoothly and all the modules installed correctly, in fact right now I'm booted in a 4.19 system with the nvidia-vulkan modules active. The only problem is that these API changes aren't compatible with the LTS kernel (which I keep installed as a backup), but that's a minor thing. Could it be that you also have the LTS kernel installed, and these errors are produced by it?

jfernandz commented on 2018-11-14 14:04 (UTC) (edited on 2018-11-14 14:35 (UTC) by jfernandz)

lib32-opencl-nvidia-vulkan and lib32-opencl-nvidia-390xx should are in conflict. They are not.

And ... despite of your driver can be compiled and built with those patches ... pacman returns a fail when dkms try to install the module in 4.19 kernel, after the package have been installed. So ... sure, we must wait until nvidia decides merge this features in the main branch.

jfernandz commented on 2018-11-14 13:33 (UTC)

@Nocifer why did you not modify the PKGBUILD to apply this patchs in prepare()?

Nocifer commented on 2018-11-14 12:23 (UTC) (edited on 2018-11-14 12:32 (UTC) by Nocifer)

Alright, I looked it up a bit more and it seems it is indeed a change in the API. Also, apparently the 396.54.09 branch will no longer be supported by Nvidia for kernel 4.19 and above, which presumably means they aim to merge it with the main 410 branch at some point in the near future. When exactly, I obviously couldn't say.

In the meantime, the package can be built with just a couple of minor changes.

https://pastecode.xyz/view/0b9f007e

https://pastecode.xyz/view/a7406bb4

Nocifer commented on 2018-11-13 21:38 (UTC) (edited on 2018-11-13 21:40 (UTC) by Nocifer)

Getting the following build error with kernel 4.19:

 ../src/NVIDIA-Linux-x86_64-396.54.09/kernel/nvidia-drm/nvidia-drm-encoder.c:219:11: error: implicit declaration of function ‘drm_mode_connector_attach_encoder’; did you mean ‘drm_connector_attach_encoder’? [-Werror=implicit-function-declaration]
 ret = drm_mode_connector_attach_encoder(connector, encoder);
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       drm_connector_attach_encoder

Changing it as suggested produces further, similar errors:

     drm_mode_connector_update_edid_property(
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     drm_connector_update_edid_property

Could this indicate a recent change in the KMS API..?

Also, some quick googling got me this:

https://devtalk.nvidia.com/default/topic/1043938/nvidia-geforce-4xx-series-drivers-segfault-with-kernel-4-19-x/

mozo commented on 2018-11-13 19:06 (UTC)

Hello, please update it to linux-headers<4.19.1. Thank you.

Kuchiriel commented on 2018-10-31 05:13 (UTC)

cat: /usr/lib/modules/extramodules-ARCH/version: Arquivo ou diretório inexistente

SilverMight commented on 2018-10-29 20:05 (UTC)

@jcstryker

Nevermind, after checking dmesg I realized I needed to run mkinitcpio. Thanks

jcstryker commented on 2018-10-29 19:28 (UTC)

@SilverMight

I currently run the DKMS version with the stock kernel. Any error messages when you run dmesg?

SilverMight commented on 2018-10-29 19:25 (UTC)

Can't seem to get this to boot using the DKMS package on stock and zen kernel

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 Next › Last »