Can't boot into TW anymore after zypper dup to 20220410 with kernel 5.17.1-1

Sorry, I hate to have to go to the forum with a “TW doesn’t boot anymore”, but the sad truth is I am somewhat lost.

I updated TW this morning to 20220410 with the customary “zypper dup”, in addition allowing vendor changes with “–allow-vendor-change”. It gave me kernel 5.17.1-1. In order to complete the update, I updated may grub configuration, and I checked for config file changes with “rpmconfigcheck”.

Admittedly, I had not updated my TW for a few months. The last kernel before had been 5.14.14. Not sure about the TW release date back then - December 2021 or January 2022?

No other changes had been done to my TW system for a very long time, it has been running perfectly. The original installation had been in 2019, and I can say I am very happy with its performance and stability.

After the update today, TW won’t boot into the latest kernel 5.17.1-1.

Booting into both my older kernels present, 5.14.14-1 and 5.13.0-1, works without any problems.

During start-up, the following messages on screen are IDENTICAL for all of my kernels, including the 5.17.1-1:Loading Linux [version] …

Loading initial ramdisk …
bbswitch: No suitable _DSM call found.
nouveau [address (?) hard to read]: volt: Type mismatch between the voltage table type and the GPIO table. Fallback to GPIO mode.

I have been getting these messages for quite some time, no problems until now.

However, with kernel 5.17.1-1 today, TW doesn’t arrive at the Plasma screen anymore. After the last message from nouveau, a static underscore character appears for some seconds. Thereafter, the screen goes all black and remains in that state. I let it sit for a couple of minutes. No reaction to CTRL-ALT-F3 or CTRL-ALT-F7. All I can do is turn the laptop power switch off.

My laptop is an old HP EliteBook 8570w. Graphics card is NVIDIA GK107GLM (Quadro K1000M), running on nouveau. Graphics platform is X11. Plasma version now is 5.24.4, KDE Frameworks 5.92.0, Qt version 5.15.2. I am not sure exactly about the latest kernel version: grub and boot message tell 5.17.1-1-default, while YaST2 Software says 5.17.1-1.2 is installed. The TW root disk is btrfs, other disks are ext4 and NTFS; they all get mounted properly.

Sorry again to be lost and without a clue. Please, can somebody help? Let me know what other information I should provide.

What I am thinking about:
Should I regenerate the 5.17.1-1 initial ramdisk, even though there were no particular errors seen when “zypper dup” did this during the update? How to do this without affecting the older ones?
I did regenerate the grub config file, several times even.

Further thoughts of mine:

Since my older kernels work, there is no need to go back to snapshots of the btrfs root dir. (Luckily, never did this before …)

I am not saying (yet) that it is kernel 5.17.1 that is causing this boot failure. But anyway, kernel 5.17.1 is the first one of the 5.17 series that came to TW, snapshot 20220331. Hmm …?

Maybe I would like to work forward from the last functioning kernel I happen to have, 5.14.14 as of 20211025.
So I would like to install kernels 5.15.12 as of 20220101, 5.16.15 as of 20220319. Those are the latest ones of each 5.n series.
However, they are not in the “official” openSUSE Tumbleweed repos.

How can I get those two kernels 5.15.12 and 5.16.15? How do I install them? Please, could somebody help with this?

I know that the route of trying the kernel series I missed out on might be a dead-end road. And I must make sure not to destroy the two working kernels I have, 5.14.14 and 5.13.0.

But I would really like to receive hints on what I can do (system logs?) to find out why 5.17.1 boots into a black screen. Thanks a lot in advance.

Update: I configured the systemd journalling to be persistent (Storage=persistent, put into a drop-in config file). Thus, there are more boot logs available now to “journalctl -b -number”, as opposed to the TW standard configuration which logs only the current boot. I now need to look at the journal from a failed boot into kernel 5.17.1 and check what is seriously different to successful boots into my older kernels, keeping in mind that the kernel is not necessarily the culprit. And please, let me have your help, even when the diagnoses have not advanced enough yet.

I did what I started in the last post, look at the systemd journalling when booting my TW either into kernel 5.14.14-1 (that works well as usual) or into 5.17.1-1 (which fails). The failure of booting 5.17.1 seems related to SDDM and nouveau. Therefore I filtered the two journals by grep’ping for nouveau or sddm. Here are the results.

First, logging from booting into 5.14.14-1 - works fine. You see its start-up at 10:16, and the log ends some time later when I executed the journalctl command.

Apr 13 10:16:04 susytmblwdke8570 kernel: fb0: switching to nouveaufb from EFI VGA
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: vgaarb: deactivate vga console
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: NVIDIA GK107 (0e73c0a2)
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: bios: version 80.07.40.00.01
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: mxm: BIOS version 3.0
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: volt: Type mismatch between the voltage table type and the GPIO table. Fallback to GPIO mode.
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: fb: 2048 MiB DDR3
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f13 00010034
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 03: 08015fd6 0f420020
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 04: 08015f92 00020020
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 05: 08014fc6 0f420010
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 06: 08014f82 00020010
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 08: 04038fb6 0f420014
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 10: 02027fa6 0f420010
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 11: 02027f62 00020010
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 13: 02049f00 00000000
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 00: 00000040
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 05: 02000546
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 07: 00010746
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 08: 00020847
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 09: 00000900
Apr 13 10:16:04 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
Apr 13 10:16:05 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: allocated 1600x900 fb: 0xa0000, bo 000000005015864d
Apr 13 10:16:05 susytmblwdke8570 kernel: fbcon: nouveau (fb0) is primary device
Apr 13 10:16:06 susytmblwdke8570 kernel: nouveau 0000:01:00.0: [drm] fb0: nouveau frame buffer device
Apr 13 10:16:06 susytmblwdke8570 kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
Apr 13 10:16:08 susytmblwdke8570 kernel: snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
Apr 13 10:16:17 susytmblwdke8570 sddm[1835]: Initializing...
Apr 13 10:16:17 susytmblwdke8570 sddm[1835]: Starting...
Apr 13 10:16:17 susytmblwdke8570 sddm[1835]: Logind interface found
Apr 13 10:16:17 susytmblwdke8570 sddm[1835]: Adding new display on vt 7 ...
Apr 13 10:16:17 susytmblwdke8570 sddm[1835]: Loading theme configuration from ""
Apr 13 10:16:17 susytmblwdke8570 sddm[1835]: Display server starting...
Apr 13 10:16:17 susytmblwdke8570 sddm[1835]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{fafe6b55-cae8-4d08-a0e4-05d7a7f0b21d} -background none -noreset -displayfd 17 -seat seat0 vt7
Apr 13 10:16:18 susytmblwdke8570 sddm[1835]: Setting default cursor
Apr 13 10:16:18 susytmblwdke8570 sddm[1835]: Running display setup script  "/usr/etc/X11/xdm/Xsetup"
Apr 13 10:16:18 susytmblwdke8570 sddm[1835]: Display server started.
Apr 13 10:16:18 susytmblwdke8570 sddm[1835]: Socket server starting...
Apr 13 10:16:18 susytmblwdke8570 sddm[1835]: Socket server started.
Apr 13 10:16:18 susytmblwdke8570 sddm[1835]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf"
Apr 13 10:16:18 susytmblwdke8570 sddm[1835]: Greeter starting...
Apr 13 10:16:18 susytmblwdke8570 sddm-helper[1853]: [PAM] Starting...
Apr 13 10:16:18 susytmblwdke8570 sddm-helper[1853]: [PAM] Authenticating...
Apr 13 10:16:18 susytmblwdke8570 sddm-helper[1853]: [PAM] returning.
Apr 13 10:16:18 susytmblwdke8570 systemd-logind[1081]: New session 1 of user sddm.
Apr 13 10:16:18 susytmblwdke8570 systemd[1855]: pam_unix(systemd-user:session): session opened for user sddm(uid=460) by (uid=0)
Apr 13 10:16:19 susytmblwdke8570 systemd[1]: Started Session 1 of User sddm.
Apr 13 10:16:19 susytmblwdke8570 sddm-helper[1853]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=460) by (uid=0)
Apr 13 10:16:19 susytmblwdke8570 sddm[1835]: Greeter session started successfully
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: High-DPI autoscaling Enabled
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: Reading from "/usr/share/xsessions/icewm.desktop"
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: Reading from "/usr/share/xsessions/plasma5.desktop"
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf"
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: Connected to the daemon.
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: QFont::fromString: Invalid description '(empty)'
Apr 13 10:16:19 susytmblwdke8570 sddm[1835]: Message received from greeter: Connect
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: Loading file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml...
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: QObject: Cannot create children for a parent that is in a different thread.
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: QObject: Cannot create children for a parent that is in a different thread.
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: QObject: Cannot create children for a parent that is in a different thread.
Apr 13 10:16:19 susytmblwdke8570 sddm-greeter[1863]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Apr 13 10:16:20 susytmblwdke8570 dbus-daemon[1035]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.23' (uid=460 pid=1863 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-JBmkxo")
Apr 13 10:16:20 susytmblwdke8570 dbus-daemon[1035]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.23' (uid=460 pid=1863 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-JBmkxo")
Apr 13 10:16:20 susytmblwdke8570 sddm-greeter[1863]: Adding view for "LVDS-1" QRect(0,0 1600x900)
Apr 13 10:16:21 susytmblwdke8570 sddm-greeter[1863]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.24'
Apr 13 10:16:21 susytmblwdke8570 sddm-greeter[1863]: Message received from daemon: Capabilities
Apr 13 10:16:21 susytmblwdke8570 sddm-greeter[1863]: Message received from daemon: HostName
Apr 13 10:16:26 susytmblwdke8570 sddm-greeter[1863]: Reading from "/usr/share/xsessions/plasma5.desktop"
Apr 13 10:16:26 susytmblwdke8570 sddm[1835]: Message received from greeter: Login
Apr 13 10:16:26 susytmblwdke8570 sddm[1835]: Reading from "/usr/share/xsessions/plasma5.desktop"
Apr 13 10:16:26 susytmblwdke8570 sddm[1835]: Reading from "/usr/share/xsessions/plasma5.desktop"
Apr 13 10:16:26 susytmblwdke8570 sddm[1835]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startplasma-x11"
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1960]: [PAM] Starting...
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1960]: [PAM] Authenticating...
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1960]: [PAM] Preparing to converse...
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1960]: [PAM] Conversation with 1 messages
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1960]: [PAM] returning.
Apr 13 10:16:26 susytmblwdke8570 sddm[1835]: Authenticated successfully
Apr 13 10:16:26 susytmblwdke8570 sddm-greeter[1863]: Message received from daemon: LoginSucceeded
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1853]: [PAM] Closing session
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1853]: pam_unix(sddm-greeter:session): session closed for user sddm
Apr 13 10:16:26 susytmblwdke8570 sddm-helper[1853]: [PAM] Ended.
Apr 13 10:16:26 susytmblwdke8570 sddm[1835]: Auth: sddm-helper exited successfully
Apr 13 10:16:26 susytmblwdke8570 sddm[1835]: Greeter stopped.
Apr 13 10:16:27 susytmblwdke8570 sddm-helper[1960]: pam_unix(sddm:session): session opened for user myself(uid=1000) by (uid=0)
Apr 13 10:16:27 susytmblwdke8570 sddm-helper[1960]: Starting: "/usr/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\""
Apr 13 10:16:27 susytmblwdke8570 sddm-helper[1971]: Adding cookie to "/run/user/1000/xauth_eKSkyB"
Apr 13 10:16:27 susytmblwdke8570 sddm[1835]: Session started
Apr 13 10:16:31 susytmblwdke8570 kernel: nouveau 0000:01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
Apr 13 10:16:31 susytmblwdke8570 kernel: nouveau 0000:01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2
Apr 13 10:16:31 susytmblwdke8570 kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
Apr 13 10:16:31 susytmblwdke8570 kernel: nouveau 0000:01:00.0: msvld: init failed, -19
Apr 13 10:23:33 susytmblwdke8570 sddm[1835]: Authentication error: "Process crashed"
Apr 13 10:23:33 susytmblwdke8570 sddm[1835]: Auth: sddm-helper crashed (exit code 15)
Apr 13 10:23:33 susytmblwdke8570 sddm[1835]: Authentication error: "Process crashed"
Apr 13 10:23:33 susytmblwdke8570 sddm[1835]: Auth: sddm-helper exited with 15
Apr 13 10:23:33 susytmblwdke8570 sddm[1835]: Socket server stopping...
Apr 13 10:23:33 susytmblwdke8570 sddm[1835]: Socket server stopped.
Apr 13 10:23:33 susytmblwdke8570 sddm[1835]: Display server stopping...
Apr 13 10:23:34 susytmblwdke8570 sddm[1835]: Display server stopped.
Apr 13 10:23:34 susytmblwdke8570 sddm[1835]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Apr 13 10:23:34 susytmblwdke8570 sddm[1835]: Removing display ":0" ...
Apr 13 10:23:34 susytmblwdke8570 sddm[1835]: Adding new display on vt 7 ...
Apr 13 10:23:34 susytmblwdke8570 sddm[1835]: Loading theme configuration from ""
Apr 13 10:23:34 susytmblwdke8570 sddm[1835]: Display server starting...
Apr 13 10:23:34 susytmblwdke8570 sddm[1835]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{7d8c1308-8be5-4fc4-9d9d-8b947f172963} -background none -noreset -displayfd 18 -seat seat0 vt7
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Setting default cursor
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Running display setup script  "/usr/etc/X11/xdm/Xsetup"
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Display server started.
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Socket server starting...
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Socket server started.
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf"
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Greeter starting...
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Signal received: SIGTERM
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Socket server stopping...
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Socket server stopped.
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Display server stopping...
Apr 13 10:23:35 susytmblwdke8570 sddm-helper[3740]: [PAM] Starting...
Apr 13 10:23:35 susytmblwdke8570 sddm-helper[3740]: [PAM] Authenticating...
Apr 13 10:23:35 susytmblwdke8570 sddm-helper[3740]: [PAM] returning.
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Display server stopped.
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Apr 13 10:23:35 susytmblwdke8570 sddm[1835]: QProcess: Destroyed while process ("/usr/libexec/sddm/sddm-helper") is still running.
Apr 13 10:23:35 susytmblwdke8570 display-manager[1809]: Starting service sddm

Whether erverything really is perfect with my systems, is left up for further scrutiny. At least that stuff works.

… to be continued in next post …

… continued from last post …

Now, logging from booting into 5.17.1 - fails, it doesn’t display the sddm greeter and stops with a black screen. The last line seen in this filtered journal log is when sddm receives the SIGTERM caused by my switching power off, as the system does not react anymore.

Apr 13 10:24:01 susytmblwdke8570 kernel: fb0: switching to nouveau from EFI VGA
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: vgaarb: deactivate vga console
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: NVIDIA GK107 (0e73c0a2)
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: bios: version 80.07.40.00.01
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: mxm: BIOS version 3.0
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: volt:  Type mismatch between the voltage table type and the GPIO table.  Fallback to GPIO mode.
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: fb: 2048 MiB DDR3
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f13 00010034
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 03: 08015fd6 0f420020
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 04: 08015f92 00020020
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 05: 08014fc6 0f420010
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 06: 08014f82 00020010
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 08: 04038fb6 0f420014
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 10: 02027fa6 0f420010
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 11: 02027f62 00020010
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB outp 13: 02049f00 00000000
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 00: 00000040
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 05: 02000546
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 07: 00010746
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 08: 00020847
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: DCB conn 09: 00000900
Apr 13 10:24:01 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
Apr 13 10:24:02 susytmblwdke8570 kernel: nouveau 0000:01:00.0: DRM: allocated 1600x900 fb: 0xa0000, bo 00000000320145ea
Apr 13 10:24:02 susytmblwdke8570 kernel: fbcon: nouveaudrmfb (fb0) is primary device
Apr 13 10:24:03 susytmblwdke8570 kernel: nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
Apr 13 10:24:03 susytmblwdke8570 kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
Apr 13 10:24:05 susytmblwdke8570 kernel: snd_hda_intel 0000:01:00.1:  bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
Apr 13 10:24:13 susytmblwdke8570 sddm[1828]: Initializing...
Apr 13 10:24:13 susytmblwdke8570 sddm[1828]: Starting...
Apr 13 10:24:13 susytmblwdke8570 sddm[1828]: Logind interface found
Apr 13 10:24:13 susytmblwdke8570 sddm[1828]: Adding new display on vt 7 ...
Apr 13 10:24:13 susytmblwdke8570 sddm[1828]: Loading theme configuration from ""
Apr 13 10:24:13 susytmblwdke8570 sddm[1828]: Display server starting...
Apr 13 10:24:13 susytmblwdke8570 sddm[1828]: Running: /usr/bin/X  -nolisten tcp -auth /run/sddm/{f1367224-30e1-4cf2-b6e8-e3303f8e15f0}  -background none -noreset -displayfd 17 -seat seat0 vt7
Apr 13 10:24:14 susytmblwdke8570 sddm[1828]: Failed to read display number from pipe
Apr 13 10:24:14 susytmblwdke8570 sddm[1828]: Could not start Display server on vt 7
Apr 13 10:24:53 susytmblwdke8570 display-manager[1802]: Starting service sddm
Apr 13 10:24:53 susytmblwdke8570 sddm[1828]: Signal received: SIGTERM

Basically, I see that sddm can’t start the display server on vt 7, since it fails to read the display number from pipe.

Again, please, I am asking for your help to understand what is happening. My capabilities do not suffice to understand the root cause. I can provide the full systemd journals, or any desired excerpt.

Thanks in advance for your help.

Apparently X server fails to start, so begin with checking its logs (likely /var/log/Xorg.0.log).

It also happened to me that after the update none of the three available Kernels started anymore. Indeed Gnome crashed with the screen indicating that something went wrong. From Yast Ncurser I uninstalled Nvidia drivers but no results, then I tried to change the login manager, but nothing. Eventually needing the computer I had to reinstall :frowning:

Sorry to hear that! Dreadful reinstalling …

Regarding your faulty system:
So you had NVIDIA as your display driver?
Which kernels did you have?

After reinstalling from which Snapshot:
Which display driver?
Which kernel?
And now it works well?

Thanks for reporting here.

Did you try booting the previous kernel
You can select that from the boot splash timeout menu

And or you can can edit the boot instructions too if required

Old NVidia seems just fine here with default FOSS drivers, kernel 5.17.2 and TW 20220413:

# inxi -IMSyz
System:
  Kernel: 5.17.2-1-default arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.24.4
    Distro: openSUSE Tumbleweed 20220413
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5B SE v: Rev 1.xx serial: <filter>
    BIOS: American Megatrends v: 1103 date: 06/04/2009
Info:
  Processes: 161 Uptime: 0h 12m Memory: 3.83 GiB used: 849.2 MiB (21.6%)
  Shell: Bash inxi: 3.3.15
# inxi -Gayz
Graphics:
  **Device**-1: NVIDIA **GF119** **NVS 310**] vendor: Hewlett-Packard **driver: nouveau**
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: DP-1,DP-2
    empty: none bus-ID: 01:00.0 chip-ID: 10de:107d class-ID: 0300
  **Display**: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.1
    compositor: kwin_x11 **driver: X: loaded: modesetting gpu: nouveau**
    display-ID: :0 screens: 1
  **Screen**-1: 0 s-res: **4240x1440** s-dpi: 120 s-size: 897x304mm (35.31x11.97")
    s-diag: 947mm (37.29")
  Monitor-1: DP-1 pos: primary,left model: Acer K272HUL serial: <filter>
    built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  Monitor-2: DP-2 pos: right model: Lenovo L2251x Wide serial: <filter>
    built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
    size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  OpenGL: renderer: NVD9 v: 4.3 Mesa 22.0.1 direct render: Yes

I had two Kernel 5.16 .-- which I was using to use the proprietary Nvidia driver from Repository and Kernel 5.17.1 which I didn’t use because it didn’t work with owners. Then there was an update of Kernel 5.17 .-- from zypper-dup and suddenly Gnome crashed, and from there I was no longer able to start a graphical session, I couldn’t even log in. I made several attempts, eliminating the proprietary Nvidia drivers by forcing the updating of the nouveau and all the video drivers, trying to delete the Gnome configuration files among the hidden files, and finally changing the login manager … all useless. Reinstallation was mandatory due to having to use the primary computer. Now I have reinstalled but with the new kernel 5.17 .-- the proprietary Nvidia drivers don’t work, I searched the available OpenSuse software for a 5.16 Kernel. working and now everything works with proprietary Nvidia:)

I zypper dup‘ed my TW to snapshot 20220419 with kernel 5.17.3 this morning, having skipped 20220413 (k 5.17.2) and 20220415. So I received kernel 5.17.3 as well as kernel-firmware 20220411 today.

Great: The issue reported here is gone. Everything works again with k 5.17.3 and my old configuration with nouveau, SDDM, X, Plasma.

Just a side note: My other Linux installation on the same laptop as TW is Manjaro. I updated Manjaro today, and I ran into the same problem with kernels 5.17.1, 5.16.18, 5.15.32. Going back to 5.10.109 helped. (These are the kernels they provide.) My Manjaro has nouveau, LightDM, X, Xfce. LightDM is the one notable difference to TW, except for the Desktops. Luckily, Manjaro accepted Ctrl+Alt+F3 to get into TTY mode, when the DM stalled during start-up.

So I hope for two things going forward:
(1) No further issues of this kind with kernels > 5.17.3, which resolved matters on TW at least.
(2) Hope that the issue disappears also in Manjaro, once the get to 5.17.3.

was going to start this exact thread the other day.

Always do my updates first on a non-critical (test) machine. and yep. total brick… XFCE TW (gecko spin)

Regards
Jordan