Op 21-09-2023 om 21:49 schreef Patrick Shanahan:

...

Hi,

My son's system fails to get into a graphical environment after the zypper dup --no-allow-vendor-change issued yesterday (to TW 20230917, kernel 6.5.3.-1-default). Trying to issue startx, the Xorg.0.login his home environment says "Failed to initialize the NVIDIA kernel module¨.

* Jogchum Reitsma [09-21-23 12:28]: then you do not have the nvidia pkg for the 6.5 kernel installed. if G04, I don't believe there is one "yet".

Hmm, too bad. Is there a way to foresee this? If we had realized this, we wouldn't have updated to this snapshot.

...

Is something wrong with this snapshot?

(We thought about doing a snapper rollback, but snapper says snapper is not configured - isn't that done automagically when installing TW? It is configured in my own system, and I can't remember having done that myself.) are you utilizing btrfs? if not, sanpper rollback is not available.

Checked, root file system uses btrfs, as I would have thought in this case.

fwiw: my G04 system also cannot utilize the 6.5 kernel.

Thu, 21 Sep 2023 18:46:54 -0400 Felix Miata :

Jogchum Reitsma composed on 2023-09-21 23:59 (UTC+0200):

...

...

then you do not have the nvidia pkg for the 6.5 kernel installed. if G04, I don't believe there is one "yet".

...

Hmm, too bad. Is there a way to foresee this? If we had realized this, we wouldn't have updated to this snapshot.

1: zypper al kernel-defaul* 2: do zypper dups as you see fit 3: install new kernels as you become aware they are supported by currently available drivers

Alternatively, for those using BTRFS: simply roll back when the problem occurs.

2nd alternative: don't use NVidia's drivers. FOSS drivers (choice of two for X display) are provided. They simply don't perform as well as NVidia's, but if they do what you need, why suffer the headaches of so many other of its users?

I wish someone would convince google that google-earth can run VERY NICELY for most people without proprietary drivers if the code is adaptive. THE MINUTE that I can use google-earth flt-sim with reasonable results I'm done with nvidia anything... for good.

Op 21-09-2023 om 21:49 schreef Patrick Shanahan:

...

Hi,

My son's system fails to get into a graphical environment after the zypper dup --no-allow-vendor-change issued yesterday (to TW 20230917, kernel 6.5.3.-1-default). Trying to issue startx, the Xorg.0.login his home environment says "Failed to initialize the NVIDIA kernel module¨.

* Jogchum Reitsma [09-21-23 12:28]: then you do not have the nvidia pkg for the 6.5 kernel installed. if G04, I don't believe there is one "yet".

There is indeed no nvidia-glG05 or -4 package, says zypper info. As said, too bad that one doesn't get warned for this omission when issuing the usual zypper dup. Now we have a pretty useless system.

...

Is something wrong with this snapshot?

(We thought about doing a snapper rollback, but snapper says snapper is not configured - isn't that done automagically when installing TW? It is configured in my own system, and I can't remember having done that myself.) are you utilizing btrfs? if not, sanpper rollback is not available.

fwiw: my G04 system also cannot utilize the 6.5 kernel.

(Oops, sent this to Patrick PM...) Op 22-09-2023 om 04:35 schreef Patrick Shanahan:

* Jogchum Reitsma [09-21-23 18:04]:

...

Op 21-09-2023 om 21:49 schreef Patrick Shanahan:

...

...

Hi,

My son's system fails to get into a graphical environment after the zypper dup --no-allow-vendor-change issued yesterday (to TW 20230917, kernel 6.5.3.-1-default). Trying to issue startx, the Xorg.0.login his home environment says "Failed to initialize the NVIDIA kernel module¨.

* Jogchum Reitsma [09-21-23 12:28]: then you do not have the nvidia pkg for the 6.5 kernel installed. if G04, I don't believe there is one "yet". There is indeed no nvidia-glG05 or -4 package, says zypper info.

As said, too bad that one doesn't get warned for this omission when issuing the usual zypper dup. Now we have a pretty useless system. no, just boot a 6.4 kernel We tried that yesterday, via grub. The only result was a blinking cursor in the upper left of both screens. It was possible to go to tty01 for a terminal login, but no graphics screen.

We haven't done any research as to why this 6.4 kernel does not boot to  graphical system, that's something we should do, I think. At the moment there is no nvidia nvidia-glG05 or -04 package installed, so that could pose the problem for the 6.4 kernel? My son is gone for the weekend on an obligatory trip with his faculty (he started this year with mathematics an physics), so we won't be able to do anything before Monday. Rest me to say thanks for thinking with us! regards, Jogchum

fwiw: this is a well known situation and has been for many years now.

...

...

...

Is something wrong with this snapshot?

(We thought about doing a snapper rollback, but snapper says snapper is not configured - isn't that done automagically when installing TW? It is configured in my own system, and I can't remember having done that myself.) are you utilizing btrfs? if not, sanpper rollback is not available.

fwiw: my G04 system also cannot utilize the 6.5 kernel.

On Friday, 22 September 2023 7:21:45 AM ACST Patrick Headley wrote:

I'm not an OpenSuSE employee but I went through the described situation many times.

This sounds like a Linux thing. If you use Nvidia proprietary drivers you have to uninstall them before performing certain kernel updates. If you performed kernel updates, like performing a major version upgrade and then get the issues you are describing you can typically use the terminal to do a 'Sudo Zypper Remove Nvidia*'. Reboot and use the terminal version of Yast to reinstall the proprietary drivers. One more reboot and you should be back in business. If not, look up the documentation on blacklisting the Nouveau drivers.

*/Patrick Headley/* Linx Consulting, Inc. (303) 916-5522 pheadley@linxco-inc.com www.linxco-inc.com

Or you do it the "easy" way. 0. Blacklist Nouveau (I started with 0 because I added this last and couldn't be bothered renumbering the rest...). 1. Install DKMS. 2. Install the drivers using Nvidia's installer 3. Drivers are automatically rebuilt using DKMS when a new kernel is booted, provided that the current driver version is compatible with the new kernel (and that hasn't broken for some time). I've been doing it this way for years. Yes, when a new driver is released it has to be installed manually again (if you want/need to update), but I haven't had a failure to boot a graphical desktop for at least a couple of years. Wayland is even usable on Nvidia with KDE now (it just messes up the font sizes relative to X11, but that's easily tweaked). (And yes, I've tried quite a few times over the years installing the drivers using zypper and the distro packages but I've never gotten anything but a black screen doing it that way). -- ================================================================================================================== Rodney Baker rodney.baker@iinet.net.au ==================================================================================================================

On 9/21/23 10:27 AM, Jogchum Reitsma wrote:

...

Hi,

My son's system fails to get into a graphical environment after the zypper dup --no-allow-vendor-change issued yesterday (to TW 20230917, kernel 6.5.3.-1-default). Trying to issue startx, the Xorg.0.login his home environment says "Failed to initialize the NVIDIA kernel module¨.

Is something wrong with this snapshot?

(We thought about doing a snapper rollback, but snapper says snapper is not configured - isn't that done automagically when installing TW? It is configured in my own system, and I can't remember having done that myself.)

Thanks again for any suggestions!

regards, Jogchum