Guys I just stumbled on this trying to update today. What should I do?
:: installing nvidia-utils (520.56.06-2) breaks dependency 'nvidia-utils=515.65.01' required by linux518-nvidia
-> error installing repo packages
You’ll need to remove the 5.18 kernel. I ran into the same issue and that’s all I did and the update completely after that.
I have the same issue, but removing 5.18 did not resolve it
Did you do the update afterwards? did you post your inxi -F? Even if the same issue as above did you explain what is happening? You should do these things.
I’m sorry, not too familiar with how things work around here 
here is what happens when I tried pacman -Syyu
:: Synchronizing package databases...
core 163.0 KiB 554 KiB/s 00:00 [#####################################] 100%
extra 1834.1 KiB 8.57 MiB/s 00:00 [#####################################] 100%
community 7.4 MiB 14.4 MiB/s 00:01 [#####################################] 100%
multilib 174.6 KiB 2.05 MiB/s 00:00 [#####################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-utils (520.56.06-2) breaks dependency 'nvidia-utils=515.76' required by linux515-rt-nvidia
:: installing nvidia-utils (520.56.06-2) breaks dependency 'nvidia-utils=515.76' required by linux519-rt-nvidia
and the inxi -F
ystem:
Host: ComputerName Kernel: 5.19.0-3-rt10-MANJARO arch: x86_64 bits: 64
Desktop: Xfce v: 4.16.1 Distro: Manjaro Linux
Machine:
Type: Desktop System: Gigabyte product: Z390 I AORUS PRO WIFI v: N/A
serial: <superuser required>
Mobo: Gigabyte model: Z390 I AORUS PRO WIFI-CF v: x.x
serial: <superuser required> UEFI-[Legacy]: American Megatrends v: F7
date: 10/15/2019
CPU:
Info: 6-core model: Intel Core i7-8700 bits: 64 type: MT MCP cache:
L2: 1.5 MiB
Speed (MHz): avg: 1400 min/max: 800/4600 cores: 1: 800 2: 800 3: 800
4: 800 5: 800 6: 800 7: 800 8: 800 9: 3200 10: 800 11: 3200 12: 3200
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 515.76
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3 driver: X:
loaded: nvidia gpu: nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2 v: 4.6.0 NVIDIA
515.76
Audio:
Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel
Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel
Device-3: Logitech [G533 Wireless Headset Dongle] type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound API: ALSA v: k5.19.0-3-rt10-MANJARO running: yes
Sound Server-1: PulseAudio v: 16.1 running: yes
Sound Server-2: PipeWire v: 0.3.58 running: yes
Network:
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi
IF: wlo1 state: up mac: 70:9c:d1:7d:97:f9
Device-2: Intel Ethernet I219-V driver: e1000e
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: 18:c0:4d:86:c3:52
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
Local Storage: total: 1.14 TiB used: 497 GiB (42.5%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T2B0C-00PXH0
size: 931.51 GiB
ID-2: /dev/sda model: DIGISTOR 256GB size: 238.47 GiB
Partition:
ID-1: / size: 915.81 GiB used: 497 GiB (54.3%) fs: ext4 dev: /dev/nvme0n1p1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 45.0 C pch: 55.0 C mobo: 37.0 C gpu: nvidia
temp: 39 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 27%
Info:
Processes: 370 Uptime: 1d 20h 18m Memory: 31.29 GiB used: 4.58 GiB (14.6%)
Shell: Bash inxi: 3.3.22
Make sure you have a LTS kernel installed and you should be good. I recommend 5.15 or 5.10 (not the RT kernels). Check which one are installed:
mhwd-kernel -li
Remove these RT kernels if you don’t know why you installed them (these are RT modified kernels for specific usage), then do the update.
sudo mhwd-kernel -r linux515-rt
sudo mhwd-kernel -r linux519-rt
sudo pacman -Syyu
1 Like
After restoring a backup due to a bad boot, I was able to go back to 5.15 LTS and remove RT kernels. After that I was able to successfully make the nvidia update. Thank you for the help!
That really doesn’t resolve the actual issue, cause right now you should be ob the 6.0 kernel and the nVidia 520 driver update should not of had any issue with kernel 5.19. If you’re going to have multiple kernels in my book LTS, 5.19, and the current 6.0?. When you do you inxi -F use ~~~ above and below it so it’s formatted like below. I suggest you fix your above post as well.
░▒▓ ~ inxi -F
System:
Host: Unimatrix-Zero Kernel: 6.0.2-arch1-1 arch: x86_64 bits: 64
Desktop: KDE Plasma v: 5.26.1 Distro: XeroLinux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 4204
date: 01/28/2021
CPU:
Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP cache: L2: 3 MiB
Speed (MHz): avg: 2375 min/max: 2200/4208 cores: 1: 2200 2: 2919 3: 2186
4: 2200 5: 2200 6: 2200 7: 2200 8: 3600 9: 2195 10: 2200 11: 2200 12: 2200
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: nvidia v: 520.56.06
Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: nvidia
gpu: nvidia resolution: 2560x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA
520.56.06
Audio:
Device-1: NVIDIA TU116 High Definition Audio driver: snd_hda_intel
Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel
Sound API: ALSA v: k6.0.2-arch1-1 running: yes
Sound Server-1: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Intel I211 Gigabit Network driver: igb
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: a8:5e:45:55:75:ae
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
driver: btusb
Report: bt-adapter ID: hci0 state: up address: 33:03:30:09:F5:65
Drives:
Local Storage: total: 20.92 TiB used: 12.16 TiB (58.1%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD Blue SN570 500GB
size: 465.76 GiB
ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0B-00YS70
size: 465.76 GiB
ID-3: /dev/sdb type: USB vendor: Seagate model: Expansion HDD
size: 7.28 TiB
ID-4: /dev/sdc type: USB vendor: Seagate model: ST8000AS0002-1NA17Z
size: 7.28 TiB
ID-5: /dev/sdd type: USB vendor: Seagate model: ST330006 51NS
size: 2.73 TiB
ID-6: /dev/sde type: USB vendor: Seagate model: ST3000DM 001-1E6166
size: 2.73 TiB
Partition:
ID-1: / size: 465.46 GiB used: 30.4 GiB (6.5%) fs: btrfs dev: /dev/sda2
ID-2: /boot/efi size: 299.4 MiB used: 608 KiB (0.2%) fs: vfat
dev: /dev/sda1
ID-3: /home size: 465.46 GiB used: 30.4 GiB (6.5%) fs: btrfs
dev: /dev/sda2
ID-4: /var/log size: 465.46 GiB used: 30.4 GiB (6.5%) fs: btrfs
dev: /dev/sda2
ID-5: /var/tmp size: 465.46 GiB used: 30.4 GiB (6.5%) fs: btrfs
dev: /dev/sda2
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 47.0 C mobo: 39.0 C gpu: nvidia temp: 38 C
Fan Speeds (RPM): cpu: 1358 case-1: 0 case-2: 0 case-3: 0 gpu: nvidia
fan: 0%
Info:
Processes: 432 Uptime: 9h 47m Memory: 23.39 GiB used: 8.23 GiB (35.2%)
Shell: Zsh inxi: 3.3.22
He probably had issues because he probably didn’t install kernels and video drivers the proper way, I guess. Anyway he fixed his issue so your post is like hitting the wind, no purpose (maybe I’m wrong and the user will come back and reply, but I doubt it, usual forum thing).
Also maybe the RT packages have an issue and it doesn’t resolve the replacement properly (yes it was not the normal kernels, it was the RT he was having issues with, not the normal). I’m too lazy to check.
Corrected Format. Thank you for letting me know Probably gonna stay away from multiple kernels at least until I’m more comfortable with how Linux works
Me being new to Linux in general, I just assumed that using the GUI kernel/pacman windows would be the recommended option.
It is indeed (depending on which GUI you’re talking about), all is in the Manjaro WIKI for proper procedures 
For the kernel, just use the LTS (non RT) kernels, they get support for multiple years so you’re less likely to use a dropped/ended kernel (which will then result in issue in the case of Nvidia drivers, as they will not exist for the non existent kernel installed on the machine, leading to issues during update process).
Just keep an eye on the announcement threads, there is always the list of supported kernels, and the announce of End Of Life (EOL) kernel that will be dropped soon (so these EOL kernels you remove before they get dropped for good in Manjaro).
1 Like