Package Details: nvidia-390xx-utils 390.151-2

Git Clone URL: https://aur.archlinux.org/nvidia-390xx-utils.git (read-only, click to copy)
Package Base: nvidia-390xx-utils
Description: NVIDIA drivers utilities
Upstream URL: https://www.nvidia.com/
Licenses: custom
Conflicts: nvidia-390xx-libgl, nvidia-libgl, nvidia-utils
Provides: nvidia-390xx-libgl, nvidia-libgl, nvidia-utils, opengl-driver, vulkan-driver
Replaces: nvidia-390xx-libgl
Submitter: Svenstaro
Maintainer: jonathon
Last Packager: jonathon
Votes: 37
Popularity: 0.32
First Submitted: 2020-03-11 17:29 (UTC)
Last Updated: 2022-05-26 10:20 (UTC)

Required by (230)

Sources (6)

Pinned Comments

jonathon commented on 2022-05-26 09:46 (UTC)

Please don't flag this package out-of-date unless a new version has been released by NVIDIA.

jonathon commented on 2021-12-26 22:44 (UTC) (edited on 2021-12-26 22:44 (UTC) by jonathon)

The DKMS package guidelines are explicit that linux-headers should not be a dependency of any DKMS package.

As a concrete example of why including that as a hard dependency is a bad idea, what happens when linux is not an installed kernel?

jonathon commented on 2020-10-19 12:41 (UTC) (edited on 2021-05-11 14:18 (UTC) by jonathon)

PACKAGE NEEDS LONG TERM MAINTAINER

I have adopted the 390xx packages to keep them secure. I do not run any 390xx hardware so will not notice any breakages and cannot test any changes.

Until such time as someone else steps up to maintain these packages - ideally someone who actually has 390xx hardware - I have to rely on you to tell me what changes are needed.

Don't expect a response if you post only "this doesn't work", and do not email me to complain about the package not working!

Use this forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1946926

A binary package is also available in my kernel-lts unofficial user repository.

Latest Comments

jonathon commented on 2022-05-26 09:46 (UTC)

Please don't flag this package out-of-date unless a new version has been released by NVIDIA.

rootyp commented on 2022-05-18 08:05 (UTC) (edited on 2022-05-18 08:05 (UTC) by rootyp)

First at all thanks for the driver, i wish to know how to mentain it or make such a package as i'm still use a GT119. And i can tell this clone it's work better than the driver from my past windows 10Xcleaner than. Seems like you know what to do with a machine.
>thank you<

BlackIkeEagle commented on 2022-03-13 10:51 (UTC)

for the upcoming 5.17 kernel: https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/herecura/kernel-5.17.patch by Joan Bruguera

Acconic commented on 2022-01-16 03:19 (UTC)

Need to install linux-headers, otherwise it will fail when installing the package.
Error message:

(2/3) Install DKMS modules ==> ERROR: Missing mnt kernel headers for module nvidia/390.147. ==> ERROR: Missing lost+found kernel headers for module nvidia/390.147. ==> ERROR: Missing sys kernel headers for module nvidia/390.147. ==> ERROR: Missing var kernel headers for module nvidia/390.147. ==> ERROR: Missing lib kernel headers for module nvidia/390.147. ==> ERROR: Missing run kernel headers for module nvidia/390.147. ==> ERROR: Missing usr kernel headers for module nvidia/390.147. ==> ERROR: Missing etc kernel headers for module nvidia/390.147. ==> ERROR: Missing srv kernel headers for module nvidia/390.147. ==> ERROR: Missing root kernel headers for module nvidia/390.147. ==> ERROR: Missing opt kernel headers for module nvidia/390.147. ==> ERROR: Missing dev kernel headers for module nvidia/390.147. ==> ERROR: Missing boot kernel headers for module nvidia/390.147. ==> ERROR: Missing lib64 kernel headers for module nvidia/390.147. ==> ERROR: Missing version kernel headers for module nvidia/390.147. ==> ERROR: Missing sbin kernel headers for module nvidia/390.147. ==> ERROR: Missing tmp kernel headers for module nvidia/390.147. ==> ERROR: Missing home kernel headers for module nvidia/390.147. ==> ERROR: Missing proc kernel headers for module nvidia/390.147. ==> ERROR: Missing bin kernel headers for module nvidia/390.147.

jonathon commented on 2021-12-26 22:44 (UTC) (edited on 2021-12-26 22:44 (UTC) by jonathon)

The DKMS package guidelines are explicit that linux-headers should not be a dependency of any DKMS package.

As a concrete example of why including that as a hard dependency is a bad idea, what happens when linux is not an installed kernel?

Shalrath commented on 2021-12-26 04:22 (UTC)

linux-headers should be a hard dependency of this because installation fails without them. Dkms is a dependency of the package, but the linux-headers are only an optional dependency of dkms, so it is possible that this package is installed without the linux-headers being present, leading to a failure.

DAC324 commented on 2021-12-21 11:09 (UTC)

@duht: See https://aur.archlinux.org/pkgbase/nvidia-390xx-utils/#comment-836318 and check if it can help you as well.

@all: I am using an ancient desktop PC equipped with a GeForce GTX 560 card, and since kernel 5.16-rc4, there are no problems with suspend here.

quimkaos commented on 2021-12-21 01:04 (UTC) (edited on 2021-12-21 01:19 (UTC) by quimkaos)

Anyone having a complete broken xorg after last update? i'm getting a blinking cursor and only TTY access. The driver shows loaded lspci...

ignore me ... i fixed it... had to force mkinitcpio -P

duht commented on 2021-12-21 00:26 (UTC) (edited on 2021-12-21 00:32 (UTC) by duht)

Thank you @jonathon.
I thought this bug is only related to this poorly supported nvidia-390xx driver in conjunction with newest xorg-server, like previous ABI bug (there is no problem with nouveau), but it looks like a general xserver issue. Thanks again.

jonathon commented on 2021-12-20 23:59 (UTC)

Yes: https://bugs.archlinux.org/task/73075 . Fix is imminent.

Also, an issue with Xorg isn't an issue with this package. Please use the forum for this sort of thing.

duht commented on 2021-12-20 23:56 (UTC) (edited on 2021-12-21 00:00 (UTC) by duht)

After upgrading xorg-server to v21.1.2 I can't resume my laptop from suspend.
On nouveau everything works fine.
Downgrading server to 21.1.1 resolves the problem so issue is related to nvidia-390xx driver and newest xorg-server.
I'm wondering if anyone else has this problem?

duht commented on 2021-12-18 22:34 (UTC) (edited on 2021-12-18 22:38 (UTC) by duht)

@jonathon 30-nvidia-ignoreabi.conf is not needed with 390.147

deliodc commented on 2021-11-17 20:21 (UTC)

Thanks a lot @Scarlet and @Juggrnaut

I was have the error message:

primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) NVIDIA: Use the -ignoreABI option to override this check.

The solution for me was edit the file /etc/bumblebee/xorg.conf.nvidia like the recommendation of @Juggrnaut and add in the Section "Device" zone, the follow lines:

Section "Device"
    ...
    BusID "PCI:01:00:0"
    Option "AllowExternalGpus" "true"  # If the GPU is external
    ...
EndSection

+info

And at the end of the file, add the follow section like the recommendation of @Scarlet:

Section "ServerFlags"
        Option "IgnoreABI" "1"
EndSection

jonathon commented on 2021-11-15 23:26 (UTC) (edited on 2021-11-15 23:26 (UTC) by jonathon)

Or, just update your copy of nvidia-390xx-utils as it includes an override file.

DAC324 commented on 2021-11-15 13:49 (UTC) (edited on 2021-11-15 13:50 (UTC) by DAC324)

For all those with that Xorg ABI error and having no /etc/X11/xorg.conf: Search for a file called /etc/X11/xorg.conf.d/20-server_flags.conf. If it does not exist yet, create it. Amend the file and paste the well-known contents there:

Section "ServerFlags"
  Option "IgnoreABI" "1"
EndSection

Let's see if Nvidia indeed fixes that. According to https://bbs.archlinux.org/viewtopic.php?pid=2003589#p2003589, Nvidia stated it is supported and receives compat fixes until the end of 2022.

Juggrnaut commented on 2021-11-13 17:40 (UTC) (edited on 2021-11-14 02:01 (UTC) by Juggrnaut)

After adding in "IgnoreABI" to "/etc/bumblebee/xorg.conf.nvidia" I now receive the following error and it doesn't load:

(WW) NVIDIA: The driver will continue to load, but may behave strangely.

(WW) NVIDIA: This driver was compiled against the X.Org server SDK from commit 4c00369024c9754e670fca37804711fef2980e2f and may not be compatible with the final version of this SDK.


UPDATE <SOLVED> I've figured out my issue and posting it in case anyone else runs into the same problem.

Prior to the recent updates, I never needed to modify the "/etc/bumblebee/xorg.conf.nvidia" file and it worked just fine OOTB. Now after the recent updates, I had to modify that file to now also include the BusID of the nvidia card. Details found here: https://wiki.archlinux.org/title/Bumblebee#Multiple_NVIDIA_Graphics_Cards_or_NVIDIA_Optimus

So after adding in the BusID (along with the "IgnoreABI" setting), it is working again.

CyrIng commented on 2021-11-10 23:21 (UTC)

Do you guys have a solution to avoid the XID errors which freeze desktop ?

JKMooney commented on 2021-11-10 22:07 (UTC)

Impressive, a patch put in place within a day....and here I was getting ready to just concede "end of life" for this old card ;)

jonathon commented on 2021-11-10 17:47 (UTC) (edited on 2021-11-10 17:47 (UTC) by jonathon)

I've included an override file with 390.144-3 as a stop-gap until Nvidia update the driver - while things might randomly break, at least Xorg will load...

hute37 commented on 2021-11-10 17:17 (UTC)

@Scarlet, work like a charm!. For lazy ones like me still using bumblebee the xorg,conf is: /etc/bumblebee/xorg.conf.nvidia

quimkaos commented on 2021-11-10 16:57 (UTC)

@Scarlet Thank you for that!! That was really useful! In my case i had to create a xorg.conf in /etc/X11/ only with that section, since i had no xorg.conf file.

polucifier commented on 2021-11-10 16:37 (UTC)

@Scarlet, thanks a lot.

Scarlet commented on 2021-11-10 09:51 (UTC) (edited on 2021-11-10 09:52 (UTC) by Scarlet)

May be useful for someone. As now Xorg's version of ABI is 25.2 after updating Xorg to 21.1.1 I had to add these lines to xorg.conf to start graphics successfully.

Section "ServerFlags"
Option "IgnoreABI" "1"
EndSection

air-g4p commented on 2021-09-05 07:53 (UTC)

@jonathon - Thanks for the updated PKGBUILD.

It compiled and installed against all of my kernels today, without issue.

Cheers

BlackIkeEagle commented on 2021-09-04 14:21 (UTC)

@jonathon, that's fine, I only made it build, so if there is a better patch, awesome :)

jonathon commented on 2021-09-04 11:38 (UTC)

@BlackIkeEagle, thank you for the patch! Although it's basically the same, I've included Stefan's here as the functionality test should be a little more robust.

air-g4p commented on 2021-09-04 08:03 (UTC)

@BlackIkeEagle - Thank you for your great work on the 5.14 patch and the updated PKGBUILD.

Installed without error against all 4 my of kernels, which include 5.14, 5.13 and the 5.12 series.

If anyone needs to build nvidia-390xx-dkms against 5.14 kernels, you can grab everything you need at:

https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/tree/herecura/

Thanks again Ike!

BlackIkeEagle commented on 2021-08-23 19:05 (UTC)

patch for the upcoming 5.14 kernel:

https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/herecura/kernel-5.14.patch

deliodc commented on 2021-08-02 01:36 (UTC)

Thanks Jonathon and collaborators, it still works (2021/08/02) !

My steps
  • pacman -Syyu
  • ("breaks the dkms driver", with the new kernel version)
  • download latest snapshot of this AUR package. Download snapshot
  • extract .tar.gz package to new directory.
  • go to the new directory and execute with user account makepkg -sri
  • Install de builded binary.
  • reboot
  • And test the new kernel version with the new driver version with primusrun glxinfo
System info
$uname -srv
Linux 5.13.7-arch1-1 #1 SMP PREEMPT Sat, 31 Jul 2021 13:18:52 +0000
$ pacman -Qee | grep -i nvidia
lib32-nvidia-390xx-utils 390.138-2
lib32-opencl-nvidia-390xx 390.138-2
nvidia-390xx-dkms 390.144-1
nvidia-390xx-utils 390.144-1
opencl-nvidia-390xx 390.144-1

(maybe i need to update my 32bit nvidia drivers haha)

Thanks all for your work and contributions!

air-g4p commented on 2021-07-10 13:23 (UTC) (edited on 2021-07-10 13:25 (UTC) by air-g4p)

@jonathon - Confirmed today that nvidia-390xx-dkms 390.143-4 builds correctly and installs without issue against: 5.13.1-arch1-1 as well as against my various 5.12.X kernels.

Cheers!

iron_overheat commented on 2021-07-04 21:26 (UTC) (edited on 2021-07-04 21:30 (UTC) by iron_overheat)

DKMS no longer builds on 5.13.0. Tried reinstalling DKMS and nvidia-390xx-dkms itself, no luck. Warnings and errors:

[...]

/var/lib/dkms/nvidia/390.143/build/nvidia/nv-mmap.c: In function ���nv_encode_caching���:
/var/lib/dkms/nvidia/390.143/build/nvidia/nv-mmap.c:255:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
  255 |             if (NV_ALLOW_CACHING(memory_type))
      |                ^
/var/lib/dkms/nvidia/390.143/build/nvidia/nv-mmap.c:257:9: note: here
  257 |         default:
      |         ^~~~~~~

[...]

/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:188:23: error: initialization of ���int (*)(struct drm_plane *, struct drm_atomic_state *)��� from incompatible pointer type ���int (*)(struct drm_plane *, struct drm_plane_state *)��� [-Werror=incompatible-pointer-types]
 188 |     .atomic_check   = nv_drm_plane_atomic_check,
     |                       ^~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:188:23: note: (near initialization for ���nv_plane_helper_funcs.atomic_check���)
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:189:23: error: initialization of ���void (*)(struct drm_plane *, struct drm_atomic_state *)��� from incompatible pointer type ���void (*)(struct drm_plane *, struct drm_plane_state *)��� [-Werror=incompatible-pointer-types]
  189 |     .atomic_update  = nv_drm_plane_atomic_update,
     |                       ^~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:189:23: note: (near initialization for ���nv_plane_helper_funcs.atomic_update���)
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:190:23: error: initialization of ���void (*)(struct drm_plane *, struct drm_atomic_state *)���   from incompatible pointer type ���void (*)(struct drm_plane *, struct drm_plane_state *)��� [-Werror=incompatible-pointer-types]
  190 |     .atomic_disable = nv_drm_plane_atomic_disable,
      |                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:190:23: note: (near initialization for ���nv_plane_helper_funcs.atomic_disable���)
  CC [M]  /var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-gem.o
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:272: /var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1847: /var/lib/dkms/nvidia/390.143/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.13.0-174-tkg-cacule/build'
make: *** [Makefile:81: modules] Error 2

CyrIng commented on 2021-07-01 07:57 (UTC)

I've been crossing XID errors with screen crashes.

Rolling back to 390.143-1 (+ Linux 5.12.13) is so far stable

NullRoute commented on 2021-06-09 21:27 (UTC) (edited on 2021-06-09 21:35 (UTC) by NullRoute)

Confirmed working on Jun. 9th, 2021

  • Linux 5.12.9
  • Nvidia 390.143

Linux Kernel 5.12.9 installed packages:

  • linux-5.12.9.arch1-1-x86_64
  • linux-api-headers-5.12.3-1-any
  • linux-firmware-20210511.7685cf4-1-any
  • linux-headers-5.12.9.arch1-1-x86_64

Nvidia Driver 390.143 installed packages:

  • nvidia-390xx-utils-390.143-3-x86_64
  • nvidia-390xx-dkms-390.143-3-x86_64
  • nvidia-390xx-settings-390.143-2-x86_64
  • opencl-nvidia-390xx-390.143-3-x86_64
  • libxnvctrl-390xx-390.143-2-x86_64

Nvidia Driver 390.143 packages not tried:

  • nvidia-390xx-390.143-1-x86_64 (It's recommended to always use dkms package!)

Installation Notes:

  • 1st. Backup all your old packages from /var/cache/pacman/pkg/
  • 2nd. Go into TTY mode and remove all old nvidia packages.
  • 3rd. Make sure your linux kernel is not ignored in /etc/pacman.conf
  • 4th. Upgrade your linux kernel to latest 5.12 version.
  • 5th. Install your new aur compiled nvidia driver packages.

Reboot & Enjoy! Please make sure you also report any bugs!

Thanks everyone, especially Nvidia team, package maintainer jonathon and anyone providing patches!

itsnotme commented on 2021-06-05 19:28 (UTC)

@stephenboston: That's because the three packages: nvidia-390xx-utils, opencl-nvidia-390xx, nvidia-390xx-dkms are all built from the same source and PKGBUILD file.

stephenboston commented on 2021-06-04 16:42 (UTC)

This page for nvidia 390 dkms is pointing to the repo for nvida 390 utils.

jonathon commented on 2021-05-10 16:21 (UTC) (edited on 2021-05-10 16:21 (UTC) by jonathon)

I don't think that's a packaging issue (e.g. https://github.com/OpenPIV/openpiv-python-gpu/issues/3). Maybe open a thread on the forum?

MartinDiehl commented on 2021-05-10 16:07 (UTC) (edited on 2021-05-10 16:08 (UTC) by MartinDiehl)

I have a problem with running an an MPI application (compiled on my computer)

--------------------------------------------------------------------------
An error occurred while trying to map in the address of a function.
  Function Name: cuIpcOpenMemHandle_v2
  Error string:  /usr/lib/libcuda.so.1: undefined symbol: cuIpcOpenMemHandle_v2
CUDA-aware support is disabled.
--------------------------------------------------------------------------

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x146a21675f7f in ???
#1  0x0 in ???

I assume it is related to the recent inclusion of (optional) CUDA support into openMPI (https://bugs.archlinux.org/task/68031).

On other computers, I simply get the message that CUDA support is disabled because libcuda.so is not found.

jonathon commented on 2021-04-29 10:20 (UTC)

@hute37: Not a package issue. Report to the paru maintainer.

hute37 commented on 2021-04-29 09:20 (UTC) (edited on 2021-04-29 09:20 (UTC) by hute37)

Conficts reported in latest update:

installing nvidia-390xx-utils (390.143-3) breaks dependency 'nvidia-390xx-utils=390.141' required by nvidia-390xx-dkms

running paru -Syyu, proposed the upgrade:


Aur (3) 
    nvidia-390xx-settings-390.143-2 (libxnvctrl-390xx nvidia-390xx-settings)  
    nvidia-390xx-utils-390.143-3 (nvidia-390xx-utils nvidia-390xx-dkms opencl-nvidia-390xx)

jonathon commented on 2021-04-06 11:14 (UTC)

Thank you, I've tracked down the original source for the patch and added it (with credit) to this package!

BlackIkeEagle commented on 2021-04-06 09:07 (UTC)

Manjaro has a working patch for building with the upcoming 5.12 kernel https://gitlab.manjaro.org/packages/extra/linux512-extramodules/nvidia-390xx/-/blob/master/kernel-5.12.patch

CyrIng commented on 2021-04-05 10:05 (UTC)

@jonathon Thank you

jonathon commented on 2021-04-01 18:07 (UTC)

That kind of looks like you're using mesa rather than nvidia? If you could use the linked forum thread to provide further details that would be easier than using the comments section here.

CyrIng commented on 2021-03-30 23:08 (UTC)

@jonathon Using nvidia-390xx-* plus kernel 5.11.10 and without vulkan-swrast:

systemd-coredump[....]: Process .... (chromium) of user .... dumped core.

                                              Stack trace of thread ....:
                                              #0  0x00007f... vkGetPhysicalDeviceProperties (libvulkan.so.1 + 0x32b30)
                                              #1  0x00007f... n/a (swrast_dri.so + 0xb7b124)
                                              #2  0x00007f... n/a (swrast_dri.so + 0xf99a5e)
                                              #3  0x00007f... n/a (swrast_dri.so + 0x15c067)
                                              #4  0x00007f... n/a (swrast_dri.so + 0x6e102e)
                                              #5  0x00007f... n/a (swrast_dri.so + 0x156801)
                                              #6  0x00007f... n/a (swrast_dri.so + 0x60a869)
                                              #7  0x00007f... n/a (libGLX_mesa.so.0 + 0x3bd12)
                                              #8  0x00007f... n/a (libGLX_mesa.so.0 + 0x356de)
                                              #9  0x00007f... n/a (libGLX_mesa.so.0 + 0x365f1)
...

jonathon commented on 2021-03-30 22:13 (UTC)

nvidia-utils (and nvidia-390xx-utils) provides vulkan-driver, which vulkan-swrast also provides. I wonder if this might be related to https://bugs.archlinux.org/task/65118 ...

jonathon commented on 2021-03-29 21:48 (UTC)

@Cyring, more information needed please. What exactly are you requesting?

CyrIng commented on 2021-03-29 10:02 (UTC)

Since Vulkan became a thing, It is apparently not possible to start various apps (chromium,firefox ...) without a Vulkan driver. As stated in Wiki, and despite this driver warnings: vulkan-swrast package is requested with nvidia-390

itsnotme commented on 2021-01-10 00:09 (UTC)

@carneeki: You can skip dependency version checks using the --nodeps option (or short: -d). So the full command would look like this: yay -S nvidia-390xx-dkms nvidia-390xx-utils --nodeps

jonathon commented on 2020-10-19 12:41 (UTC) (edited on 2021-05-11 14:18 (UTC) by jonathon)

PACKAGE NEEDS LONG TERM MAINTAINER

I have adopted the 390xx packages to keep them secure. I do not run any 390xx hardware so will not notice any breakages and cannot test any changes.

Until such time as someone else steps up to maintain these packages - ideally someone who actually has 390xx hardware - I have to rely on you to tell me what changes are needed.

Don't expect a response if you post only "this doesn't work", and do not email me to complain about the package not working!

Use this forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1946926

A binary package is also available in my kernel-lts unofficial user repository.

matt42 commented on 2020-09-21 15:53 (UTC)

@forcegk Sorry for the noise, this error is due to packages pulling nvidia-utils (cuda, steam and others). After uninstalling cuda and steam I could upgrade without problem.

forcegk commented on 2020-09-21 15:08 (UTC)

@matt42 : You should only be using the nvidia-390xx-utils, so you can safely uninstall nvidia-utils

matt42 commented on 2020-09-21 07:26 (UTC) (edited on 2020-09-21 07:27 (UTC) by matt42)

This package recently got a conflict with nvidia-utils. When I try to update with pacman -Syu, I get this:

:: nvidia-utils and nvidia-390xx-utils are in conflict (nvidia-libgl). Remove nvidia-390xx-utils?

And if I answer yes, it gives other errors:

error: failed to prepare transaction (could not satisfy dependencies)

:: removing nvidia-390xx-utils breaks dependency 'nvidia-390xx-utils' required by lib32-nvidia-390xx-utils

:: removing nvidia-390xx-utils breaks dependency 'nvidia-390xx-utils=390.138' required by nvidia-390xx-dkms

Should I force remove or force install something ?

Thanks.

deliodc commented on 2020-08-16 21:56 (UTC)

Thanks!

carneeki commented on 2020-07-07 16:13 (UTC)

Experienced the same problem as @zwastik and @warp4ever

I also tried @forcegk's advice with yay and encountered the same issue.

I was able to build+install by modifying the nvidia-390xx-dkms PKGBUILD and removing nvidia-390xx-utils from the depends; the dkms package requires the utils package to be installed and up to date to build which seemed a bit circular.

AnbuBlack commented on 2020-07-07 16:12 (UTC)

The upgrade is not working unless first the old version of the driver is uninstalled.

forcegk commented on 2020-07-07 14:07 (UTC)

I'd suggest installing nvidia-390xx(-dkms)first @warp4ever @zwastik, as the dependencies are all right.

With an AUR helper you can just do: yay -S nvidia-390xx-dkms nvidia-390xx-utils

(you can also add nvidia-390xx-settings to the list)

warp4ever commented on 2020-07-07 11:27 (UTC)

Same error as user zwastik

zwastik commented on 2020-07-07 02:53 (UTC) (edited on 2020-07-07 03:00 (UTC) by zwastik)

==> Finished making: nvidia-390xx-utils 390.138-3 (Mon 06 Jul 2020 10:49:34 PM -04)

==> Installing nvidia-390xx-utils package group with pacman -U...

loading packages...

resolving dependencies...

looking for conflicting packages...

error: failed to prepare transaction (could not satisfy dependencies)

:: installing nvidia-390xx-utils (390.138-3) breaks dependency 'nvidia-390xx-utils=390.132' required by nvidia-390xx-dkms

==> WARNING: Failed to install built package(s).

Samm504 commented on 2020-04-23 09:54 (UTC)

Thank you very much!

Cristophero commented on 2020-03-21 06:55 (UTC)

Muchas gracias!