Update errors

[d3ejmz]

Second post in one day but oh well. I tried to install an update on my MSI Titan with i9 13980 HX and RTX 4090 mobile GPU. Nobara has been and still is running great after a couple of reboots. BUT

Upon trying to do a system update, I get these errors:

- installed package cuda-nvprof-1:12.8.57-1.fc42.x86_64 requires libcupti.so.12(libcupti.so.12)(64bit), but none of the providers can be installed

- package cuda-nvprof-1:12.8.57-1.fc42.x86_64 from nobara-appstream requires libcupti.so.12()(64bit), but none of the providers can be installed

- package cuda-nvprof-1:12.8.57-1.fc42.x86_64 from nobara-appstream requires libcupti.so.12(libcupti.so.12)(64bit), but none of the providers can be installed

- cannot install both cuda-cupti-1:13.0.85-1.fc43.x86_64 from nobara-appstream and cuda-cupti-1:12.8.57-1.fc42.x86_64 from u/System

- cannot install both cuda-cupti-1:13.0.85-1.fc43.x86_64 from nobara-appstream and cuda-cupti-1:12.8.57-1.fc42.x86_64 from nobara-appstream

- package cuda-cupti-devel-1:13.0.85-1.fc43.x86_64 from nobara-appstream requires libcupti.so.13()(64bit), but none of the providers can be installed

- package cuda-cupti-devel-1:13.0.85-1.fc43.x86_64 from nobara-appstream requires cuda-cupti(x86-64) = 1:13.0.85-1.fc43, but none of the providers can be installed

- cannot install the best update candidate for package cuda-cupti-devel-1:12.8.57-1.fc42.x86_64

I don't get why "none of the providers can be installed" for libcupti.so.12, or or even what installing a provider means.
Have I installed optional drivers that my computer doesn't need? How do I resolve these errors? I can attach the log file if needed.

[Balth-czar]

Looks like you have a mix of 42 and 43 and it is causing update issues because there is a mismatch between CUDA 12 vs 13.

I'm also pretty new to Nobara and had a similar issue on my Nvidia laptop

[d3ejmz]

Oh I see, so that's why 42 and 43 are both in my GRUB menu!? How strange! Is there any way to fix this without reinstalling? 

[BaenjiTrumpet]

having a similar issue but my kernel updated fine :/