Unable to boot kernel 6.5.2-1.1 after zypper dup today

English Install/Boot/Login
#1

I did a zypper dup today and all completed fine. Then I rebooted my system and it comes up with the grub screen and when I hit enter the screen goes black and then it boots again. If I select the previous 6.4 kernel the system boots just fine. Also will not boot into recovery using 6.5.2.

Cannot find anything in journal and boot logs show nothing obvious. This is an AMD CPU system with integral graphics if that makes a difference.

I realise there is nothing to go on so far so how do I make some progress with this and get some diagnostics out of the system please?

Stuart

#2

do you have by any chance also a nvidia in your system?

do you get the login screen?
If yes, can you select plasma wayland for login?

#3

I do not have NVIDIA in my system at all. Not tried selecting Wayland.

I must add that I have an INTEL laptop with Intel HD graphics and that boots kernel 6.5.2 fine, just not my AMD system.

Stuart

#4

@broadstairs Hi, all good here with both X11 and Wayland on GNOME (It is MicroOS, but that should not matter…)

AMD CPU and Dual AMD GPU graphics…

inxi -SCGxxz

System:
  Kernel: 6.5.2-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    Desktop: GNOME v: 44.4 Distro: openSUSE MicroOS
CPU:
  Info: quad core model: AMD A10-9600P RADEON R5 10 COMPUTE CORES 4C+6G
    bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
  Speed (MHz): avg: 1200 min/max: 1200/2400 boost: enabled cores: 1: 1200
    2: 1200 3: 1200 4: 1200 bogomips: 19170
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard
    driver: amdgpu v: kernel arch: GCN-3 bus-ID: 00:01.0
  Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 M440/M445 530/535
    620/625 Mobile] vendor: Hewlett-Packard driver: amdgpu v: kernel
    arch: GCN-3 bus-ID: 04:00.0 temp: 33.0 C
  Device-3: Chicony HP Wide Vision HD driver: uvcvideo type: USB
    bus-ID: 1-1.3:3
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.0
    compositor: gnome-shell driver: X: loaded: modesetting dri: radeonsi
    gpu: amdgpu resolution: 1366x768~60Hz
  API: OpenGL v: 4.6 Mesa 23.1.7 renderer: AMD Radeon R5 Graphics (carrizo
    LLVM 16.0.6 DRM 3.54 6.5.2-1-default) direct-render: Yes

switcherooctl inxi -SCGxxz

System:
  Kernel: 6.5.2-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    Desktop: GNOME v: 44.4 Distro: openSUSE MicroOS
CPU:
  Info: quad core model: AMD A10-9600P RADEON R5 10 COMPUTE CORES 4C+6G
    bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
  Speed (MHz): avg: 1199 high: 1200 min/max: 1200/2400 boost: enabled cores:
    1: 1200 2: 1200 3: 1197 4: 1200 bogomips: 19170
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard
    driver: amdgpu v: kernel arch: GCN-3 bus-ID: 00:01.0
  Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 M440/M445 530/535
    620/625 Mobile] vendor: Hewlett-Packard driver: amdgpu v: kernel
    arch: GCN-3 bus-ID: 04:00.0 temp: 34.0 C
  Device-3: Chicony HP Wide Vision HD driver: uvcvideo type: USB
    bus-ID: 1-1.3:3
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.0
    compositor: gnome-shell driver: X: loaded: modesetting dri: radeonsi
    gpu: amdgpu resolution: 1366x768~60Hz
  API: OpenGL v: 4.6 Mesa 23.1.7 renderer: AMD Radeon R7 M340 (iceland LLVM
    16.0.6 DRM 3.54 6.5.2-1-default) direct-render: Yes
#5

One question how am I supposed to select Wayland? Can’t find any option for it.

Stuart

#6

Forget the question about Wayland found out how to do it. The issue in my case is that I do not get to the KDE login screen, all I see is GRUB panel then a black screen and then back to bott and GRUB panel again. Wayland works on previous kernel OK.

Stuart

Update:- Just tried again booting having selected Wayland on previous kernel boot. Now when booting 6.5.2 kernel I do see the message about the kernel and loading ramdisk before I then get bounced back to boot and the GRUB screen.

#7

I have the same issue on one of my desktops with a Nvidia gpu after doing a zypper dup and booting to kernel 6.5. When it boots it won’t boot to the GUI login screen. I only get the tty login prompt.

Booting to kernel 6.4 boots fine.

#8

@Maverick1024 This is about AMD GPU and CPU… Just a FWI, for me all good with Nvidia as well…

@broadstairs at Grub, if you press e to edit and then on the linuxefi line at the end, enter nomodeset and press F10 to boot, does that get you further?

#9

@malcolmlewis Yes somewhat I see the logo screen I normally get when booting but then it gives up again and gets me back to a grub screen. I also tried changing to runlevel 3 or 1 but neither boots always returning to grub. My system disk I boot from is an NVME SSD if that matters. Also I am not using linuxefi just plain linux when I edit the grub commands.

Hardware is:-

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)
CPU AMD Ryzen 5 3400G with Radeon Vega Graphics

Stuart

#10

@broadstairs disable plymouth, so add nomodeset plymouth.enable=0 and see if you can glean more info…

#11

That does nothing at all. I did try removing the quiet option which does display some messages but the flash past so quickly it is unreadable and then reboots, I have no idea if they get saved anywhere or at least I’ve not found anywhere. Most things I do find are from booting the old kernel in order to update here. This system has no dual boot so I have no way to boot a new OS and see any logs which may be there from the failed boot.

Stuart

#12

@broadstairs if you boot to the new kernel, then boot the old kernel, does journalctl -b -1 show 6.5.x booting?

#13

No I can only find the 6.4.12 kernel boots so it’s not writing to journal.

Thanks for all the suggestions so far, it’s late here now I’ll continue in the morning.

Stuart

#14

I found the boot process to be extremely slow in a vm ((vmware) with kernel kernel-default-6.5.2-1.1
and got also a lot of key bounces. like “zyppppper” , “cddddd” etc.

Booted 6.4.12-1-default, all fine; just removed the offending kernel and the booting was fast again, no keystroke issues.

#15

@roelandjansen Nothing to do with my problem, I can’t get a running system at all, even runlevel1!

Stuart

#16

Done some more testing today and used my phone to video the fast scrolling messages and this seems to show that TW is starting up and it is processing USB devices when it all gives up. Need a better video as I might have missed the last message!

Also created a bootable USB HDD with another distro so I could boot that and investigate what might be in /var/log but so far cannot see anything in there on the TW bootable SSD root partition - it says log is empty! Need to take another. look at that. I only have minimal USB devices connected, my keyboard and mouse via a KVM and a webcam. I tried connecting the USB dongle to the desktop directly but it still fails to boot.

This is driving me nuts!

Stuart

#17

Just realised why the /var/log are empty, I’d forgotten that I created a /var partition so I’ll do another test and this time I should see something if I look in the right place :face_with_open_eyes_and_hand_over_mouth: :face_with_open_eyes_and_hand_over_mouth:

Stuart

#18

Having looked at the correct partition I am unable to find any relevant log files and I think because this test system is quite old I can’t open any journal files. Next option is to copy them to a usb stick and try from my TW system with kernel 6.4.

Stuart

#19

You do know if /var/log/journal/ doesn’t exist, there won’t be any persistent systemd logs, right?

#20

Yes but I had forgotten that I had created a separate partition for var and there is data in that var/log directory but I am unable to open any of the journal files with my old bootable usb system as it complains about the format. So if I copy them I should be able open them on TW booted with kernel 6.4.

Stuart