Nvidia Driver Upgrade Results in File Conflict Message

[kitman]

Hi.

I’m doing a zypper dup run -

sudo zypper  --pkg-cache-dir /data/chris/zypp/ dup -D --download-only

But it results in a conflict with nvidia

File /usr/lib/modprobe.d/50-nvidia-default.conf
  from install of
     nvidia-gfxG05-kmp-default-470.161.03_k6.1.6_1-58.26.x86_64 (nVidia Graphics Drivers)
  conflicts with file from install of
     nvidia-open-driver-G06-signed-kmp-default-525.85.05_k6.1.8_1-2.1.x86_64 (openSUSE-Tumbleweed-Oss)

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no): 

I didn’t select the nvidia-open-driver so I don’t know why it’s mentioned or how to proceed from here to resolve this.

[kitman]

I found via another post this -

sudo zypper addlock nvidia-open-driver-G06-signed-kmp-default

That removes the conflict. Is this the way to go before I commit to the upgrade?

[hui]

Yes.

Latest updates killed my GUI (4th week of Jan'23) - Kernel 6.8.1?

Not super skilled, so bear with me. Have been running Leap for years, but got tired of the full upgrades required so I switched to Tumbleweed in December (maybe a bad choice…). So here it is 2 months later and my laptop will not boot into GUI mode after the last batch of updates that came down. I get “Localhost login” and that’s it. I did manage to roll back with help from the internet, so I am up and running - for now. So what’s the next step? Never update again? I know it is probably the dis…

[highgrounder]

I’m a Tumbleweed user as well.

I’m using G06 driver and still met the error message. Seems the closed source kernel module in Nvidia repo didn’t manage to catch up with the open source kernel module in Tumbleweed repo?

Problem: the to be installed nvidia-open-driver-G06-signed-kmp-default-525.85.05_k6.1.8_1-3.1.x86_64 conflicts with ‘nvidia-driver-G06-kmp’ provided by the installed nvidia-driver-G06-kmp-default-525.85.05_k6.1.6_1-6.1.x86_64
Solution 1: deinstallation of nvidia-driver-G06-kmp-default-525.85.05_k6.1.6_1-6.1.x86_64
Solution 2: deinstallation of nvidia-open-driver-G06-signed-kmp-default-525.85.05_k6.1.7_1-1.1.x86_64
Solution 3: keep obsolete nvidia-open-driver-G06-signed-kmp-default-525.85.05_k6.1.7_1-1.1.x86_64

[arvidjaar]

@highgrounder

Problem: the to be installed nvidia-open-driver-G06-signed-kmp-default-525.85.05_k6.1.8_1-3.1.x86_64 conflicts with ‘nvidia-driver-G06-kmp’ provided by the installed nvidia-driver-G06-kmp-default-525.85.05_k6.1.6_1-6.1.x86_64

Bug 1207520 – nvidia-open-driver-G06-signed incorrectly declares compatibility with too much hardware (suse.com)

[highgrounder]

I saw the bug report already. I believe it’s about nvidia-open-driver-G06-signed-kmp-default is automatically installed on the device that uses G04 or G05 driver. My problem is different since I use G06 driver.

[arvidjaar]

@highgrounder

My problem is different since I use G06 driver.

Your problem is exactly the same.

@highgrounder

I believe it’s about nvidia-open-driver-G06-signed-kmp-default is automatically installed on the device that uses G04 or G05 driver.

It is about nvidia-open-driver-G06-signed-kmp-default being automatically installed. Period.

[highgrounder]

Hmm interesting thanks for the explanation. I’ve been using my device with nvidia-open-driver-G06-signed-kmp-default installed for a week without any issue until I met the error in the update. I thought it was a part of the G06 driver packages.

[arvidjaar]

@highgrounder

I’ve been using my device with nvidia-open-driver-G06-signed-kmp-default installed for a week

Sorry?

@highgrounder

provided by the installed nvidia-driver-G06-kmp-default-525.85.05_k6.1.6_1-6.1.x86_64

Currently installed is binary driver and zypper attempts to install open source driver.