Unable to satisfy dependency 'nvidia-utils=550.90.07'

Support System Updates
1 
LANG= LC_ALL= pamac update -a                                                             1 ✘ 
Preparing...
Sincronización de bases de datos de paquetes...
Refreshing AUR...                                                                                          
Warning: ignoring package replacement (cpufrequtils-008-3 => cpupower-6.9-1)                               
Resolving dependencies...
Warning: cannot resolve "nvidia-utils=550.90.07", a dependency of "linux66-nvidia"
Warning: cannot resolve "nvidia-utils=550.90.07", a dependency of "linux68-nvidia"
Warning: cannot resolve "nvidia-utils=550.90.07", a dependency of "linux69-nvidia"
Error: Failed to prepare transaction:
could not satisfy dependencies:
- unable to satisfy dependency 'nvidia-utils=550.90.07' required by linux66-nvidia

More with the same problem, being addressed here

2

Please search the forum - several topics already exist - with solution.

sudo mhwd-kernel -i linux66 rmc
3

Maybe I’m a bit clumsy, I don’t see it, can you put the URL?

4 
Error: You can't reinstall your current kernel. Please use 'pacman -Syu' instead to update.
5 
sudo mhwd-kernel -i linux66 -rmc                                                          1 ✘ 
Error: Invalid argument.
Please choose one of the available kernels:
   * linux419
   * linux510
   * linux515
   * linux54
   * linux61
   * linux610
   * linux66
   * linux68
   * linux69
   * linux61-rt
   * linux66-rt
   * linux67-rt
6

If you want to work on this one / remove this one, you need to boot another one of the kernels you have installed.
You can’t remove or reinstall the one that is in use.

7

As this is recurring topic - please see → [How To] Handle Nvidia conflicts on sync

8

I’m confused, the provided link seems to refer to unsupported kernels. Neither of my kernels are unsupported as far as I can tell.

"linux61-nvidia"
"linux66-nvidia"
9

That is correct - to use this command - the unsupported kernel must be the active kernel.

Otherwise use e.g.

sudo mhwd-kernel -r linux68

My apologies - it should be sudo mhwd-kernel -i linux66 rmc

10

None of the solutions work, it seems to be a problem with the update, more users have the same problem:

11

Since 550.90.07 is in all branches - in don’t see why this should an issue

spacing added for readability

 $ mbn info nvidia-utils -q
Branch         : archlinux
Name           : nvidia-utils
Version        : 550.90.07-1
Repository     : extra
Build Date     : Sun 09 Jun 2024 01:16:28 
Packager       : Sven-Hendrik Haase <svenstaro@archlinux.org>

Branch         : unstable
Name           : nvidia-utils
Version        : 550.90.07-2
Repository     : extra
Build Date     : Thu 06 Jun 2024 01:51:45 
Packager       : Mark Wagie <mark@manjaro.org>

Branch         : testing
Name           : nvidia-utils
Version        : 550.90.07-2
Repository     : extra
Build Date     : Thu 06 Jun 2024 01:51:45 
Packager       : Mark Wagie <mark@manjaro.org>

Branch         : stable
Name           : nvidia-utils
Version        : 550.90.07-2
Repository     : extra
Build Date     : Thu 06 Jun 2024 01:51:45 
Packager       : Mark Wagie <mark@manjaro.org>

So am I

12

“Maybe” simply the files are not or have not been synchronized on the servers.

13

That would point to a mirror issue - try switching mirror

sudo pacman-mirrors --continent

The Austrian mirror I use has the correct packages.

10:08:18 ○ [fh@tiger] ~
 $ pamac info nvidia-utils
Name                  : nvidia-utils
Version               : 550.90.07-2
Description           : NVIDIA drivers utilities
URL                   : http://www.nvidia.com/
Licenses              : custom
Repository            : extra
Installed Size        : 622,7 MB
Groups                : --
Depends On            : libglvnd egl-wayland
Optional Dependencies : nvidia-settings: configuration tool
                        xorg-server: Xorg support [Installed]
                        xorg-server-devel: nvidia-xconfig
                        opencl-nvidia=550.90.07: OpenCL support
Provides              : vulkan-driver opengl-driver nvidia-libgl nvidia-utils=550.90.07
Replaces              : nvidia-libgl
Conflicts With        : nvidia-libgl
Packager              : Mark Wagie <mark@manjaro.org>
Build Date            : tor 06 jun 2024 01:51:45 CEST
Validated By          : MD5 Sum  SHA-256 Sum  Signature


10:08:32 ○ [fh@tiger] ~
 $ pamac info linux66-nvidia
Name                  : linux66-nvidia
Version               : 550.90.07-2
Description           : NVIDIA drivers for linux
URL                   : http://www.nvidia.com/
Licenses              : custom
Repository            : extra
Installed Size        : 53,6 MB
Groups                : linux66-extramodules
Depends On            : linux66 nvidia-utils=550.90.07
Optional Dependencies : --
Provides              : nvidia=550.90.07 NVIDIA-MODULE
Replaces              : --
Conflicts With        : --
Packager              : Mark Wagie <mark@manjaro.org>
Build Date            : tor 06 jun 2024 02:18:50 CEST
Validated By          : MD5 Sum  SHA-256 Sum  Signature
14
15

I just saw it - I cannot imagine how this came to be - I can only

:facepalm:

At least I got to write the how-to - factually it is a recurring issue - usually with EOL kernels.

linux68 is EOL which is why I replied as I did - my apologies …

16

Better a poor response than none at all, intent to help is appreciated, thank you.

2 Likes
17

No need to apologize, your contributions here more than enough outweighs the odd slip-up.

18

With that I do not agree - but thank you for your understanding - much appreciated

  • I know I was too quick here
  • I know how many times I have seen variations over this
  • I you knew how many times I have repeated myself
  • That is why I provided the search comment
  • I even went on to create a proper search link
  • I went on to create a how-to I could refer back to instead of repeating myself
2 Likes
19

Update went through without protests but the happiness was short-lived. Now I’m unable to boot into Plasma, stuck at Reached graphical interface. Switching to the free driver “solved” the problem but it’s just a temporary solution. Seems like others have a similar problem.

1 Like
20

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.