Upgrade to 15.2 without Nouveau

When I put in the command to upgrade from 15.1 to 15.2, I got a warning that it would include the Nouveau driver. The warning said Nouveau wasn’t recommended for KDE, which is what I use, and plus I had a bunch of problems with the Optimus-Nouveau thing when I first installed openSUSE. How do I do the upgrade without accepting Nouveau?

I think that message is exclusively about xf86-video-nouveau, which provides the DDX driver, but it may also apply to Mesa-dri-nouveau. You can deny acceptance, which should enable the driver all my NVidia GPUs use, modesetting, the upstream default. If after the upgrade you are unhappy, you can add them without answering the question one way or the other by downloading either or both manually and using rpm -Uvh to upgrade them.

please post Your repos

$ zypper lr -d

There is not such a thing as **the **command to upgrade from 15.1 to 15.2.

Please always shoiw what you do: command and output, by copy/paste between CODE tags (the # button in the tool bar of the post editor) in your post. Only so others can see what you did and what you got. And that is cricial when you want help.

I followed the instructions in the SDB. As they describe, I switched my repos to 15.2

zypper --releasever=15.2 ref

My repos normally are

 1 | http-download.opensuse.org-36146ea8 | openSUSE:Leap:15.1:Update                        | Yes     | (r ) Yes  | Yes
 2 | openSUSE-Leap-${releasever}-1       | openSUSE-Leap-15.1-1                             | Yes     | (r ) Yes  | Yes
 3 | openSUSE_Leap_${releasever}_Update  | Online updates for openSUSE Leap:15.1 (standard) | Yes     | (r ) Yes  | No
 4 | repo-debug                          | Debug Repository                                 | No      | ----      | ----
 5 | repo-debug-non-oss                  | Debug Repository (Non-OSS)                       | No      | ----      | ----
 6 | repo-debug-update                   | Update Repository (Debug)                        | No      | ----      | ----
 7 | repo-debug-update-non-oss           | Update Repository (Debug, Non-OSS)               | No      | ----      | ----
 8 | repo-non-oss                        | Non-OSS Repository                               | Yes     | (r ) Yes  | Yes
 9 | repo-oss                            | Main Repository                                  | Yes     | (r ) Yes  | Yes
10 | repo-source                         | Source Repository                                | No      | ----      | ----
11 | repo-source-non-oss                 | Source Repository (Non-OSS)                      | No      | ----      | ----
12 | repo-update                         | Main Update Repository                           | Yes     | (r ) Yes  | Yes
13 | repo-update-non-oss                 | Update Repository (Non-Oss)                      | Yes     | (r ) Yes  | Yes
14 | snappy                              | snappy                                           | Yes     | (r ) Yes  | Yes

Then I used

zypper --releasever=15.2 dup

I was prompted about whether I wanted to continue. I said yes and it gave me this

In order to install ‘Mesa-dri-nouveau’, you must agree to terms of the following license agreement:
WARNING: Nouveau DRI/3D driver selected.

This driver is considered experimental and is known to have issues with
applications that use certain 3D acceleration features of modern
NVIDIA hardware.

Symptoms include application crashes or lockups & crashes of your system’s
graphical environment. Older Hardware and less demanding applications may work
just fine and do benefit from the Hardware acceleration features this driver
offers over software emulation.

Use of this driver is especially not recommended for use with the KDE Desktop
Environment or Qt-based Applications.

The hardware vendor potentially offers alternative drivers.

Please click “I agree” if you accept the risks that may come with the
installation of this driver. Choose “I disagree” to prevent installation
of the driver and use software emulation instead.
Do you agree with the terms of the license? [yes/no] (no):
I said no, and it said
Aborting installation due to user disagreement with Mesa-dri-nouveau package license.
So yeah, denying acceptance didn’t cause it to switch drivers; it just cancelled the installation.

OT: I was almost done composing a response when the phone rang 2 hours ago. When I came back, all the work was wiped out due to the forum’s automatic logout after an unspecified period of time. Best as I can recall is what follows, as I’m in need of sleep ASAP and can hardly think.

# inxi -SGy
  Host: big41 Kernel: 5.3.18-lp152.41-default x86_64 bits: 64 Desktop: KDE 3
  Distro: **openSUSE Leap 15.2**
  Device-1: NVIDIA GF108 [GeForce GT 630] driver: nouveau v: kernel
  **Display: server: X.Org 1.20.3 driver: loaded: modesetting**
  unloaded: fbdev,vesa **resolution: 1920x1200**~60Hz
  **OpenGL: renderer: llvmpipe** (LLVM 9.0.1 128 bits) v: 3.3 Mesa 19.3.4
# rpm -qa | grep veau

You can

zypper al xf86-video-nouveau


zypper al Mesa-dri-nouveau

and repeat zypper dup to get a result similar to mine if you first zypper rm or rpm -e either or both. With most NVidia GPUs, these two packages for some unfathomable number of users are simply not needed, as above shown from one of mine. Thus, there is no need to accept any Nouveau license.

Thanks for the sleepy reply, but I’m still a little stuck. I added both those locks and started to run the upgrade, but I kept getting many “this requirement could not be provided” messages that asked me to either deinstall things, keep my obsolete versions, break the packages by failing to install the dependencies, or remove the locks. The requirements that couldn’t be provided were things like “kio” and “libQt5Gui,” and honestly I’m not knowledgeable enough to know what these are and what they have to do with the Nouveau drivers that I locked. Eventually I just canceled the upgrade because I wasn’t sure I was doing the right thing by keeping the obsolete versions of everything.

Why does locking these two graphics drivers cause so many dependencies for other things to be incapable of being installed? What choices should I be making when these messages come up? I really do not know what I’m doing.

My graphics as of now:

Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel
Device-2: NVIDIA GP107GLM [Quadro P1000 Mobile] driver: N/A
Device-3: Chicony type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.3 driver: modesetting resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 18.3.2

Before zypper dup, lets try upgrading only the package management system, its dependencies, and a few other foundational underpinnings:

zypper -v in --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release
zypper -v in --download-in-advance device-mapper glibc multipath-tools mdadm systemd udev aaa_base

Expect several broken dep complaints. Choose ignore, as they should be fixed later, when dup is run. Once this has completed:

zypper -v up --no-recommends

Script will log all subsequent screen output to a file named typescript. Alternatively to --no-recommends, you can make that switch more permanent by editing /etc/zypp/zypp.conf to read thus:

 solver.onlyRequires = true

This is my setting for all installations. I don’t remember whether by default it is commented out, or = false, or both. This phase shouldn’t raise any questions. When the up finishes it’s time for the balance, but if you wish, you can do a dry run first so that typescript’s record can be evaluated before really proceeding:

zypper -v dup --dry-run --download-only

If you want, susepaste typescript for us to evaluate. To end the typescript capture, Ctrl-D.

I’m unsure why more than a few dependencies were hit, but expect --no-recommends/solver.onlyRequires = true to reduce or eliminate most. One I expect is related to the meta-package xorg-x11-driver-video, of which xf86-video-nouveau is a part. That meta-package and the many drivers it calls are mostly space wasters as long as you’re sticking to using NVidia graphics. Thus, choose remove or do not install for xf86-video-* and xorg-x11-driver-video, except for two: xf86-video-fbdev and xf86-video-vesa. These two are fallbacks that can be useful for troubleshooting from a running X.

For now, I’m again very short on sleep, only three hours since my last post in this thread…

Tried that, but the same thing is happening. I did the ‘in’ and ‘up’ that you suggested, and then the dup with --no-recommends. It still gives me lots of dependencies and I kept choosing to keep the obsolete ones, but there are so many. Here’s what I got before I canceled: https://pastebin.com/AaYHSL33

But please sleep before responding!

Seems you have a whole bunch of locked files? You have to let files move from the lp151 to the lp152 versions as indicated in the output…

All those deps are on account of my #6 post, so undo the lock causing them:

zypper rl Mesa-dri-nouveau

then remove the nouveau DDX and all the inapplicable video drivers

zypper rl xf86-video-nouveau
zypper rm xorg-x11-driver-video xf86-video-*
zypper al xf86-video-nouveau
zypper in xf86-video-fbdev xf86-video-vesa

The rm will probably cause removal of another Xorg meta-package or two, which is fine, just let it.

But if I don’t lock it, the upgrade will install Mesa-dri-nouveau, right? Should I be concerned about that?

Don’t be. IMO Mesa shouldn’t be broken into multiple packages. It’s configured as an all or none dependency system, even though various parts couldn’t be relevant, e.g. nouveau for an intel user, or amdgpu for an nvidia user. I don’t think a license commitment could be required for Mesa-dri-nouveau anyway, because of the all or none business.

Well, thanks very much for the thorough advice, again! I did the upgrade and it all went smoothly.