SDDM black login screen with mouse ponter

[arvidjaar]

Mar 27 12:51:51 localhost.localdomain systemd-coredump[1570]: Process 1447 (Xorg.bin) of user 0 dumped core.
                                                              
                                                              Stack trace of thread 1447:
                                                              #0  0x00007fbf7e6949ec __pthread_kill_implementation (libc.so.6 + 0x949ec)
                                                              #1  0x00007fbf7e641176 raise (libc.so.6 + 0x41176)
                                                              #2  0x00007fbf7e628917 abort (libc.so.6 + 0x28917)
                                                              #3  0x0000562e3c284dcc OsAbort (Xorg.bin + 0x1dbdcc)
                                                              #4  0x0000562e3c285e2f FatalError (Xorg.bin + 0x1dce2f)
                                                              #5  0x0000562e3c288512 n/a (Xorg.bin + 0x1df512)
                                                              #6  0x00007fbf7e641240 __restore_rt (libc.so.6 + 0x41240)
                                                              #7  0x00007fbf7c12b98d n/a (radeonsi_dri.so + 0x72b98d)

I am pretty sure somebody reported similar crash with AMD recently.

[carlos.vergara]

I can see a post with AMD GPU problems as well

Vulkan not working on two AMD gpus

Hello! I recently installed tumbleweed on two devices with an amd gpu: a steam deck and a 2 in 1 with a 7730u. They both say ERROR: [Loader Message] Code 0 : vkCreateInstance: Found no drivers! Cannot create Vulkan instance. This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that dors not support Vulkan. ERROR at /home/abuild/rpmbuild/BUILD/Vulkan-Tools-vulkan-sdk-1.3.280.0/vulkaninfo/./vulkan.h:458:vkCreateInstance failed with ERROR_INCOMPATIB…

Maybe I should do rollback and wait a few days before updating again.

[epp]

Very similar to my issue, display shows a black screen with only the mouse pointer:

Display not coming out of sleep in X11 sessions

Twice today, the system has failed to provide the KDE login screen (SDDM) when the display comes out of sleep mode, on an X11 session. This has happened on Tumbleweed, fully-upgraded, installed to both an HDD and an external USB SSD. This has so far, not occurred with a Wayland session. System would be used normally, then I leave the desktop for 5-10 minutes. When I get back, the display is correctly in sleep mode (Samsung 22-inch monitor, blue power light is blinking). When pressing the space…

[carlos.vergara]

Might be related to latest Mesa and Vullkan update from couple of days ago and amd gpu’s, because it’s working fine with intels.

I did a rollback before that update and everything works fine.

[pfmiller0]

There was a discussion about this on Reddit and they were also saying it was probably due to the Mesa update. I rolled back to before the Mesa update and that did fix the problem for me.

[totte]

SDDM would show the background and allow for the mouse cursor to move, but I couldn’t interact with it otherwise, i.e. I couldn’t log in. journalctl showed that Xorg.bin crashed (core dump), followed by others, such as kwin-x11. I’m new to snapper and I’m not sure if I can perform the zypper dist-upgrade, reboot, save the output from journalctl --boot, then reboot and snapper rollback to the previous working snapshot with the logs still in my ~.

For the time being, I locked the following packages:

kernel-firmware-amdgpu libgbm1 libgbm1-32bit libvulkan_radeon libvulkan_radeon-32bit Mesa Mesa-32bit Mesa-dri Mesa-dri-32bit Mesa-gallium Mesa-gallium-32bit Mesa-libEGL1 Mesa-libGL1 Mesa-libGL1-32bit
  Mesa-libglapi0 Mesa-libglapi0-32bit Mesa-libva Mesa-vulkan-device-select Mesa-vulkan-device-select-32bit

Here’s some information about my hardware:

totte@localhost ~> inxi -SCG
System:
  Host: localhost.localdomain Kernel: 6.8.1-1-default arch: x86_64 bits: 64
  Desktop: i3 v: 4.23 Distro: openSUSE Tumbleweed 20240327
CPU:
  Info: 16-core model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP cache:
    L2: 16 MiB
  Speed (MHz): avg: 499 min/max: 400/5714 cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    15: 400 16: 400 17: 400 18: 400 19: 400 20: 3599 21: 400 22: 400 23: 400
    24: 400 25: 400 26: 400 27: 400 28: 400 29: 400 30: 400 31: 400 32: 400
Graphics:
  Device-1: AMD Hawaii PRO [Radeon R9 290/390] driver: amdgpu v: kernel
  Device-2: AMD Raphael driver: amdgpu v: kernel
  Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~144Hz
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.6 renderer: AMD
    Radeon R9 200 Series (radeonsi hawaii LLVM 18.1.1 DRM 3.57
    6.8.1-1-default)
  API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib

[mchnz]

@epp

Very similar to my issue, display shows a black screen with only the mouse pointer:

Twice today, the system has failed to provide the KDE login screen (SDDM) when the display comes out of sleep mode, on an X11 session. This has happened on Tumbleweed, fully-upgraded, installed to both an HDD and an external USB SSD. This has so far, not occurred with a Wayland session. System would be used normally, then I leave the desktop for 5-10 minutes. When I get back, the display is correctly in sleep mode (Samsung 22-inch monitor, blue power light is blinking). When pressing the space…

I’ve just encountered what you described, also in X11. I found I could alt-ctrl-F1 to a console and then login as root use loginctl to unlock the session (I suspect I didn’t need to be root):

1. Run loginctl to list sessions
2. Run loginctl unlock-session N

Hopefully that might work for you too.

[pfmiller0]

I was able to make a little progress today. I locked the mesa packages and updated all the rest of my packages. After this was done SDDM worked, but Plasma still crashed when I tried to log into a Wayland session. When I switched to an X session that worked, and I am currently in an updated Plasma 6.0.3 session.

Unfortunately, Kitty is not behaving well after this update, frequently using 250% cpu, but if I switched to Konsole things seem to be running ok.

[croak8171]

Im not sure if your error is related to mine, but I was able to fix mine by installing two packages: libvulkan_radeon and Mesa-vulkan-device-select. Good luck!

https://forums.opensuse.org/t/vulkan-not-working-on-two-amd-gpus/173595/2

Summary

@carlos.vergara

I can see a post with AMD GPU problems as well

[keellambert]

hi,
fwiw, information only any feedback appreciated.
i found after update could not get to kde desktop nor load from live iso.
Work around employed on start-up edited the startup script with:-
modprobe.blacklist=radeon
amdgpu.si_support=0
later the above was inserted into the boot string to make permanent.
Beware: this limited screen resolution to 800x600 (4:3)! But at least, laptop just about useable.
cheers

[bandes]

Hi, since last Tumblweed update i have a similar problem.
I detected sddm is producing a crash in the system. So i started the system in init 3 (editing grub witn a 3 at the end of the init command) and ran:
‘update-alternatives --config default-displaymanager’ as root and chosing xdm als default display manager.
With gdm did not work, with gdm black screen as well, with sddm, after a crash, i could logon form terminal and start the X-session with startx.
As I said, for me now the system works with xdm als presentation-logon screen.
Waiting for a fix.
Best regads, hopefuly it helps

[pfmiller0]

I already had those packages installed, so not a fix for me unfortunately.

[Fltlander2]

Don’t know if this will help you but with all the troubleshooting that I did, I finally found my fix:
As a workaround I used the following cmdline options:
radeon.cik_support=0 radeon.si_support=0 amdgpu.si_support=1 amdgpu.cik_support=1

Edit your grub menu to get into the desktop and then
Add these options to your GRUB_CMDLINE_LINUX_DEFAULT that you find in /etc/default/grub and then run ‘grub2-mkconfig -o /boot/grub2/grub.cfg’ afterwards to update /boot/grub2/grub.cfg.

[conram]

There are two versions of SDDM in the repositories.
What is the output of
zypper se sddm
Might be this is the missing link.
I just installed the plasma patterns to see if I will have a problem with SDDM. So far it’s all good. I am using nvidia maybe that’s why I am not affected.

[keellambert]

hi Fltlander2,

thanks for sharing, that fixed to problem for me too. laptop now back to normal.

cheers

[carlos.vergara]

Thank you for sharing @Fltlander2, it works

Let’s just hope Mesa comes with a fix soon.

[totte]

The 24.0.3-372.1 version of Mesa appears to have resolved my issue. I removed all the locks, ran zypper refresh and zypper dist-upgrade followed by rebooting – and SDDM is now displayed and interactive as I expect it to.

[totte]

Logging in after boot works, but SDDM or the screen locker will freeze after the monitor has been turned off after the default value of 10 minutes.

[pfmiller0]

Update to 24.0.3 didn’t make a difference for me, same issue.

[steve_lynn]

Doesn’t work for me. Still need “modprobe.blacklist=radeon” in grub conf to get any graphic display.