I’m facing a similar issue to that described in the linked topic below.
@Terry-Rosinski, have you solved your reported issue yet?
Moderator edit: Topic split, with link to former topic it was originally appended to.
Have you performed an upgrade using zypper dup from a terminal as root?
Yes, that’s what prevented me from getting to the login screen after I recently executed zyyper dup. Looking at the journalctl log, it suggests that gdm failed to start.
Can you share the graphics hardware details?
inxi -GSaz
Sharing terminal output can be challenging without a working desktop environment. If necessary save the output to a file first
inxi -GSaz > info.txt
Transfer to USB memory stick. Use udisksctl to manage the USB storage device from a VT…
You can take the memory stick to a PC with a working graphical environment and post the results as requested.
Hello. Here’s my information.
System:
Kernel: 6.14.1-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc
avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.14.1-1-default
root=UUID=2a387da8-db01-438b-bef8-9a64d5ed041e splash=silent quiet security=apparmor psi=1
mitigations=auto
Console: tty 1 DM: GDM v: 48.0 Distro: openSUSE Tumbleweed 20250414
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Dell
driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: HDMI-A-1
empty: HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Opal XT [Radeon R7 M265/M365X/M465] vendor: Dell
driver: radeon v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm
built: 2011-20 pcie: gen: 2 speed: 5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s
bus-ID: 01:00.0 chip-ID: 1002:6604 class-ID: 0380 temp: 32.0 C
Device-3: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-1.8:3 chip-ID: 1bcf:2b8b class-ID: 0e02
Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6 driver: X:
loaded: intel,modesetting,vesa alternate: fbdev gpu: i915 tty: 240x67
Monitor-1: HDMI-A-1 model: Dell Inspiron 5348 serial: <filter> built: 2013 res: 1920x1080
dpi: 96 gamma: 1.2 size: 510x287mm (20.08x11.3") diag: 585mm (23") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
API: OpenGL Message: GL data unavailable in console. Try -G --display
API: Vulkan Message: No Vulkan data available.
API: EGL Message: EGL data unavailable in console, eglinfo missing.
Info: Tools: api: glxinfo,vulkaninfo x11: xprop,xrandr
At least one Southern Islands AMD GPU user has reported trouble using the radeon kernel module (driver). First ensure that xf86-video-amdgpu is installed, then try a test boot: At the Grub menu, strike the E key, navigate to the end of the linu line (which usually is wrapped onto one or two more lines), append a space and radeon.si_support=0 amdgpu.si_support=1, then proceed with boot. If this solves the issue, a space and radeon.si_support=0 amdgpu.si_support=1 need to be added to /etc/default/grub’s GRUB_CMDLINE_LINUX_DEFAULT= line within its quotes, then /boot/grub2/grub.cfg must be regenerated using sudo grub2-mkconfig -o /boot/grub2/grub.cfgfor a lasting workaround (“fix”).
My Southern Islands GPU has never needed the psi=1 option that yours contains, so it may no longer be needed or desirable. Try also booting with it omitted using the same testing manner as with the two si_support= options. If no apparent issues apparently result from its removal, you may remove it from /etc/default/grub, and either run grub2-mkconfig as above, or just let the next kernel installation do it for you.
I’ve been using radeon.si_support=0 amdgpu.si_support=1 with my Southern Islands “Oland” GPU ever since discovering the “experimental” option to use the amdgpu module instead of the radeon module, for too many years to remember.
1 Like
[retracted for further investigation…]
I tried the 6.14.2 TW kernel in Slowroll without using radeon.si_support=0 amdgpu.si_support=1 and it works fine, suggesting radeon.si_support=0 amdgpu.si_support=1 may be no help to poster gmg137 
# inxi -GSaz --vs --za
inxi 3.3.38-00 (2025-04-06)
System:
Kernel: 6.14.2-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm parameters: root=LABEL=[filter]
mitigations=off noresume
Desktop: … Distro: openSUSE Tumbleweed-Slowroll 20250402
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R5 430
OEM R7 240/340 Radeon 520 OEM] vendor: Dell driver: radeon v: kernel
alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm
built: 2011-20 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3
speed: 8 GT/s ports: active: DP-1,DVI-I-1 empty: none bus-ID: 01:00.0
chip-ID: 1002:6611 class-ID: 0300 temp: 51.0 C
Display: x11 server: X.Org v: 21.1.15 compositor: kwin_x11 driver: X:
loaded: radeon unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
Screen-1: 0 s-res: 4240x1440 s-dpi: 120 s-size: 897x304mm (35.31x11.97")
s-diag: 947mm (37.29")
…
It was also OK rebooting again using the radeon kernel driver with the modesetting display driver instead of the radeon display driver. I suppose it could be worth trying the modesetting display driver, by restarting X or rebooting after either: 1-uninstalling xf86-video-ati, or 2-creating a file in /etc/X11/xorg.conf.d/25-dix.conf (filename & quoted “Identifier” string not important) containing:
Section "Device"
Identifier "DIX"
Driver "modesetting"
EndSection
I booted again with radeon.si_support=0 amdgpu.si_support=1 omitted, and psi=1 added, and it worked OK too.
Thank you very much, I was able to get to the login screen properly by adding radeon.si_support=0 amdgpu.si_support=1 . 
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.