Until now, I thought I could use Myrlyn just as well as zypper for updates, but I just tried to do an update with zypper and I got a conflict with a nvidia driver file. I aborted the update and some time later I tried to update with Myrlyn, and Myrlyn didn’t detect the dependency conflict and went ahead with the update. Afterwards I had to roll back to the last snapshot, because the NVIDIA driver wasn’t working.
I do remember that Myrlyn had identified and reported dependency conflicts before.
Hello,
Myrlyn and zypper are both relying on libzypp : Myrlyn is a graphical tool and zypper is a command line tool. So yes, Myrlyn checks for conflicts, warn and offers choice for solve them, when possible.
Can you add some information about your situation : what Nvidia package were “detected” by zypper and what output zypper gave ?
Regards
4 Likes
Let me guess: You got a file conflict the first time (with zypper) but not when you retried a second time (with Myrlyn). Right?
In that case, probably the mirror that you got that RPM from was out of sync during the first attempt, but not for the second one; or the load balancer picked a different mirror at that time.
Whatever happens at that level happens in libzypp, no matter if you are using zypper or Myrlyn. It’s literally the exact same code for both of them. If it behaves differently, it’s not a difference in the code, but in the data that the code (libzypp) receives from the remote server.
7 Likes
Right, and now after the rollback both zypper and Myrlyn are showing the conflict:
Problem: 1: the installed nvidia-common-G07-595.84-8.1.x86_64 requires '(nvidia-open-driver-G07-signed-kmp = 595.84 if nvidia-open-driver-G07-signed-kmp-meta)', but this requirement cannot be provided
deleted providers: nvidia-open-driver-G07-signed-kmp-default-595.84_k7.1.5_1-2.4.x86_64
Solution 1: Following actions will be done:
deinstallation of nvidia-common-G07-595.84-8.1.x86_64
deinstallation of nvidia-compute-G07-595.84-8.1.x86_64
deinstallation of nvidia-video-G07-595.84-8.1.x86_64
deinstallation of nvidia-compute-utils-G07-595.84-8.1.x86_64
deinstallation of nvidia-userspace-meta-G07-595.84-26.1.x86_64
Solution 2: deinstallation of nvidia-open-driver-G07-signed-kmp-meta-595.80-29.1.x86_64
Solution 3: keep obsolete nvidia-open-driver-G07-signed-kmp-default-595.84_k7.1.5_1-2.4.x86_64
Solution 4: break nvidia-common-G07-595.84-8.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
I suspect that, in my haste, I selected “Package Update” instead of “Dist-Upgrade” in Myrlyn.
Thanks for the support
Okay, so it wasn’t a file conflict as I suspected, but a real dependency conflict.
This sounds very plausible.
Especially in the context of NVidia driver updates with the library parts and the kmp package (different for each major and minor kernel version) and the kmp meta package serving as a bracket to keep the matching parts together this can make a great difference.
I’ve been thinking about a dedicated “NVidia driver assistant” tool (or page in Myrlyn?) for quite a while, but I fear that would open a whole new can of worms; starting with a user interface that normal humans can understand, offering just the right amount of choices and still being able to do disaster recovery, and of course testing and ongoing support for the inevitable problematic cases. I am not so sure if that is realistic.
1 Like
I also stumbled upon this issue yesterday and I’m fairly sure I only used zypper dup and don’t have myrlyn at all.
Then I saw this post, which seems to be an issue of needing to wait for the kernel to be available: Nvidia Update. Which one?
I had to rollback since I chose option 1 which put me back with the noveau driver. I’ll choose option 3 for now and wait until the update is available
1 Like
Sounds interesting. It could include a hardware check and information on whether the optimal driver(-version) is installed and what alternatives are available (with pros and cons). Even though many Linux users are switching or have already switched to AMD (and I, too, have a computer with an AMD GPU), NVIDIA will continue to play a major role in the Linux world.
I had the same issue, my bad of course for now simply canceling the update until the issue is solved, luckily there is snapper, so rolling back is a breeze.