Package Details: lib32-nvidia-vulkan-utils 570.123.14-1

Git Clone URL: https://aur.archlinux.org/nvidia-vulkan.git (read-only, click to copy)
Package Base: nvidia-vulkan
Description: NVIDIA drivers utilities (32-bit) (vulkan developer branch)
Upstream URL: https://developer.nvidia.com/vulkan-driver
Licenses: custom
Conflicts: lib32-nvidia-libgl, lib32-nvidia-utils
Provides: lib32-nvidia-libgl, lib32-nvidia-utils, lib32-opengl-driver, lib32-vulkan-driver
Replaces: lib32-nvidia-libgl
Submitter: jcstryker
Maintainer: ventureo
Last Packager: ventureo
Votes: 31
Popularity: 0.30
First Submitted: 2018-06-23 01:17 (UTC)
Last Updated: 2025-05-14 06:42 (UTC)

Required by (16)

Sources (11)

Latest Comments

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

jcstryker commented on 2018-09-10 21:40 (UTC) (edited on 2018-09-11 02:21 (UTC) by jcstryker)

@pikimeister

The module needs to be rebuilt with every kernel update. That is why the official repos bump the package version each time they release a kernel. I don't do that with this package because it includes all the other utils needed to use the driver. You simply need to build nvidia-vulkan again with each kernel, and if you use early kernel module loading you need to rebuild your initramfs.

I wish there was a better way to handle this, this all stems from nvidia's shenanigans with their kernel module. It frustrates the official maintainers as well.

pikimeister commented on 2018-09-09 06:48 (UTC) (edited on 2018-09-09 06:49 (UTC) by pikimeister)

Hello,

This package doesn't seem to work with latest kernel version provided by archlinux (4.18.6-arch1-1-ARCH).

X doesn't start.

Had to uninstall this version and install nvidia 396.54-3 (from default repos) in order to overcome the issue.

jcstryker commented on 2018-09-01 10:45 (UTC) (edited on 2018-09-01 10:48 (UTC) by jcstryker)

@theriddick

That's very strange, it builds fine with no infinite loop on my test server using aurutils and on my desktop using yay.

Which aur helper are you using?

theriddick commented on 2018-09-01 06:09 (UTC)

Well it installed on my system but for some reason it kept infinite loop downloading and installing over and over, dunno why. Canceling it didn't appear to break anything and the packages are installed fine. (along with utils/32bit utils)

t-ask commented on 2018-08-17 18:30 (UTC)

Just to let you know. Kernel update 4.18 leads to "installing linux (4.18.1.arch1-1) breaks dependency 'linux<4.18' required by nvidia-vulkan"

tskaar commented on 2018-08-07 20:13 (UTC) (edited on 2018-08-07 20:16 (UTC) by tskaar)

Based on this commit and this commit, you need to change the line _extramodules=extramodules-4.17-arch to _extramodules=extramodules-ARCH in the PKGBUILD

jcstryker commented on 2018-08-05 13:39 (UTC)

@SeriousBug

This is due to a change in the extramodules directory with the latest kernel package in the arch repos. Should be resolved now, let me know if you have any other issues.

<deleted-account> commented on 2018-08-05 08:37 (UTC)

The build is failing for me with the following error:

==> Starting build()...
cat: /usr/lib/modules/extramodules-4.17-ARCH/version: No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...

The file does indeed seem to be missing. Is there some package I'm missing, or is this due to a change in the kernel packages?

jcstryker commented on 2018-07-22 04:16 (UTC)

@twisty

The regular nvidia-vulkan is packaged for the standard linux kernel in the main repos, while nvidia-vulkan-dkms is packaged for use with dkms and can be used with any kernel(standard, linux-lts, linux-hardened, etc.)

https://wiki.archlinux.org/index.php/Dynamic_Kernel_Module_Support

Feature-wise there is no difference, so when in doubt use the non-dkms version.

twisty commented on 2018-07-22 03:13 (UTC)

What is the difference between the two packages (dkms vs not)?

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