Open Konsole (or any terminal emulator), issue inxi -GSaz copy the whole terminal output including leading and trailing prompt (CTRL+SHIFT+C) and paste here.
There are other threads about problems with similar HW with mixed results, for instance resolved-trying-to-install-slowroll-on-an-amd-ryzen-5-8600g-apu and trying-to-install-slowroll-on-an-amd-ryzen-5-8600g-apu.
Apparently there are problems with wayland on those chips, but the basic system might still work.
Just for test you may append “3” to the boot command line (at the boot screen press “E” for “Edit”, look for the line beginning with “linux”, append 3 without quotes and then F10 to boot), you should land at a console prompt and you should be able to issue your username and password and login to a terminal session. If your username was not properly setup, “root” and root password should also work.
If that works, at least we have a way to try and understand what went wrong.
Thanks for the links - I also know what to expect passing that command.
I was thinking of having another try and saving the installer’s log to the system, maybe it might be useful. The other idea was using Agama to install - apparently it went without hitch (and I could install Slowroll which I’m thinking of, as the last kernel update has given me a rash of screen freezes…)
Anyway, I’ll get back to you (I only have the one monitor)
inxi -GSaz - doesn’t recognise command… my keyboard is azerty and everything is in qwerty… I’ll try again
The results are in (after changing the keyboard layout… installing inxi… and restarting this one which had had another screen freeze while I was away)
linux@localhost:~> inxi -GSaz
System:
Kernel: 6.15.3-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=(hd0)/boot/x86_64/loader/linux splash=silent quiet
systemd.show_status=yes root=live:CDLABEL=openSUSE_Tumbleweed_KDE_Live
rd.live.image rd.live.overlay.persistent rd.live.overlay.cowfs=ext4
Desktop: KDE Plasma v: 6.4.0 tk: Qt v: N/A info: frameworks v: 6.15.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: openSUSE Tumbleweed 20250624
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: ASRock
driver: N/A alternate: amdgpu arch: RDNA-3 code: Phoenix
process: TSMC n4 (4nm) built: 2023+ pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.0 chip-ID: 1002:15bf class-ID: 0300
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev gpu: N/A display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99")
s-diag: 338mm (13.3")
Monitor-1: Unknown-1 mapped: None-1 res: mode: 1024x768 hz: 60
scale: 100% (1) size: N/A modes: 1024x768
API: OpenGL v: 4.5 vendor: mesa v: 25.1.4 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: llvmpipe (LLVM 20.1.6 256 bits)
device-ID: ffffffff:ffffffff memory: 14.37 GiB unified: yes
API: Vulkan v: 1.4.313 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM
20.1.6 256 bits) driver: N/A device-ID: 10005:0000 surfaces: N/A
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo,vulkaninfo de: kscreen-console,kscreen-doctor
wl: wayland-info x11: xdpyinfo, xprop, xrandr
8600G was released Apr 16, 2024, so no way it should be too new for TW. RDNA-3 originated 2.5 years ago. That said, inxi says no kernel graphics module has loaded. The live image may have the same kernel module and firmware as the installed system, and if this is the case, inxi has pointed out a serious problem. The most common result of this situation is the firmware it needs is broken or unavailable. I don’t know the details, but recently, and possibly still now, kernel-firmware-amdgpu was broken for some AMD GPUs. If you can boot the installed system using 3 on bootloader’s linu line as @OrsoBruno suggested, you can issue command sudo zypper se -s kernel-firmware-amdgpu to determine installed and available versions. If an “a” version is available that is newer than your “i” version, then sudo zypper ref && sudo zypper dup may be enough to fix this issue. From a minimalist installation, you also could be missing other graphics software as well, but most important is to get the amdgpu kernel driver loaded, then see if something else could be missing.
@Cyclonick for whatever reason, amdgpu is not being used?
Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: ASRock
driver: N/A alternate: amdgpu
The fixed kernel-firmware-amdgpu version 20250620 was in snapshot 20250623 so any newer install image (or the network version) should be OK.
EDIT: then another update to 20250623 (current as of this writing) was in snapshot 20250624.
When it hangs, I end up with a command line prompt, so I could start there !
The amdgpu info I have came from starting in rescue mode…
When I chose my software, the only thing I touched were kde applications - I left anything system strictly alone !
OK, off again!
The first command gave me two option - the first I think the installed one, and the second in the repo - they were the same
I took a photo of the last screen in recovery mode - it may help
* Sat Jun 21 08:00:00 2025 Takashi Iwai <tiwai@suse.com>
- Update to version 20250620 (git commit 49c833a10ad9):
* amdgpu: add arcturus IP discovery firmware
* amdgpu: add gc 11.0.0 kicker firmware
* amdgpu: add gc 9.5.0 firmware
* amdgpu: add picasso ip discovery firmware
* amdgpu: add psp 13.0.0 kicker firmware
* amdgpu: add psp 13.0.12 firmware
* amdgpu: add raven2 ip discovery firmware
* amdgpu: add raven ip discovery firmware
* amdgpu: add sdma 4.4.4 firmware
* amdgpu: add smu 13.0.0 kicker firmware
* amdgpu: add vcn 5.0.1 firmware
* amdgpu: update aldebaran firmware
* amdgpu: update beige_goby firmware
* amdgpu: update dimgrey_cavefish firmware
* amdgpu: update gc 10.3.6 firmware
* amdgpu: update gc 11.0.0 firmware
* amdgpu: update gc 11.0.1 firmware
* amdgpu: update gc 11.0.2 firmware
* amdgpu: update gc 11.0.3 firmware
* amdgpu: update gc 11.0.4 firmware
* amdgpu: update gc 11.5.0 firmware
* amdgpu: update gc 11.5.1 firmware
* amdgpu: update gc 11.5.2 firmware
* amdgpu: update gc 12.0.0 firmware
* amdgpu: update gc 12.0.1 firmware
* amdgpu: update gc 9.4.3 firmware
* amdgpu: update gc 9.4.4 firmware
* amdgpu: update navi10 firmware
* amdgpu: update navi12 firmware
* amdgpu: update navi14 firmware
* amdgpu: update navy flounder firmware
* amdgpu: update psp 13.0.0 firmware
* amdgpu: update psp 13.0.10 firmware
* amdgpu: update psp 13.0.11 firmware
* amdgpu: update psp 13.0.14 firmware
* amdgpu: update psp 13.0.6 firmware
* amdgpu: update psp 13.0.7 firmware
* amdgpu: update psp 14.0.1 firmware
* amdgpu: update psp 14.0.2 firmware
* amdgpu: update psp 14.0.3 firmware
* amdgpu: update psp 14.0.4 firmware
* amdgpu: update renoir firmware
* amdgpu: update sdma 7.0.0 firmware
* amdgpu: update sdma 7.0.1 firmware
* amdgpu: update sienna cichlid firmware
* amdgpu: update smu 13.0.0 firmware
* amdgpu: update smu 13.0.10 firmware
* amdgpu: update smu 13.0.7 firmware
* amdgpu: update smu 14.0.2 firmware
* amdgpu: update smu 14.0.3 firmware
* amdgpu: update vangogh firmware
* amdgpu: update vcn 4.0.0 firmware
* amdgpu: update vcn 4.0.2 firmware
* amdgpu: update vcn 4.0.4 firmware
* amdgpu: update vcn 4.0.5 firmware
* amdgpu: update vcn 4.0.6 firmware
* amdgpu: update vcn 5.0.0 firmware
* amdgpu: update vega10 firmware
* amdgpu: update vega12 firmware
* amdgpu: update vega20 firmware
Above is from changelog of current kernel-firmware-amdgpu 20250623. I see nothing that suggests Phoenix was touched. Please run inxi -Gaz again to see whether driver: N/A or driver: amdgpu results. If the amdgpu driver loaded, ensure susepaste command is installed, installing with zypper if necessary, then do susepaste -e "10080" /var/log/Xorg.0.logand provide the resulting URL here.
Am I going in with the live image or in the command line when I attempt to start…?
I still wonder if the install didn’t finish properly - as I said, it told me it was going to reboot and never did. Are there logs I can go fishing for?
Booting the installed system provides easiest access to troubleshooting information we need, even if that means only shell prompts can be reached. Live image data collection is limited and/or more difficult to acquire. Installer reboot could have occurred without producing any visible screen output if firmware was absent or broken.
Driver : amdgpu
susepaste instruction result : can’t read /var/log/Xorg.0.log
Check if Xorg.0.log exists in ~/.local/share/xorg/. Also check for Xorg.1.log both places. If Wayland is being attempted instead of Xorg, then journalctl needs to be consulted for closest equivalent information. I don’t use Wayland, so don’t know just what to look for there. As root, journalctl -b | grep aile might be a start, as could dmesg | grep aile. zypper se -si kernel-firmware-amdgpu xf86-video-amdgpu would tell us exactly which firmware and amd display driver are installed.
The result of dmesg | grep aile : 1: T443 hub 6-0:1.0 config failed, hub doesn’t have any ports
2: Platform regulatory.0 : Direct firmware load failed for regulatory.db failed with error -2
3 : Cfg80211 : failed to load regulatory.db
result of zypper command - same amdgpu as before for xf86-video-amdgpu the resulting table contained no entries for the package (either installed or in repo)
It’s not just your installation. I just did a dup from 20250611 to 20250626 on a somewhat older AMDGPU PC, and it hangs about the time KMS is supposed to engage when booting the newly installed 6.12.34 LTS kernel. Booting the prior 6.14.6 kernel, which was not allowed to have its initrd rebuilt during, before or after the dup, works just fine. Current state:
# inxi -SMz
System:
Kernel: 6.14.6-2-default arch: x86_64 bits: 64
Console: pty pts/3 Distro: openSUSE Tumbleweed 20250626
Machine:
Type: Desktop Mobo: Gigabyte model: F2A88XM-D3H v: x.x serial: N/A
UEFI: American Megatrends v: F9 date: 12/25/2015
# inxi -Gaz
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
vendor: Gigabyte driver: amdgpu v: kernel alternate: radeon arch: GCN-2
code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17 ports:
active: DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 00:01.0 chip-ID: 1002:130f
class-ID: 0300
Display: unspecified server: X.Org v: 21.1.15 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: modesetting dri: radeonsi
gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
Monitor-1: DVI-D-1 pos: right model: Dell P2213 serial: <filter>
built: 2013 res: mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: NEC EA243WM
serial: <filter> built: 2011 res: mode: 1920x1200 hz: 60 scale: 100% (1)
dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1")
ratio: 16:10 modes: max: 1920x1200 min: 640x480
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.4 glx-v: 1.4
direct-render: yes renderer: AMD Radeon R7 Graphics (radeonsi kaveri ACO
DRM 3.61 6.14.6-2-default) device-ID: 1002:130f memory: 1000 MiB
unified: no
API: Vulkan v: 1.4.313 layers: 1 device: 0 type: integrated-gpu name: AMD
Radeon R7 Graphics (RADV KAVERI) driver: mesa radv v: 25.1.4
device-ID: 1002:130f surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 20.1.6 256 bits) driver: mesa llvmpipe v: 25.1.4 (LLVM 20.1.6)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info,wlr-randr
x11: xdpyinfo, xprop, xrandr
# zypper se -si amdgpu | grep OSS
i+ | kernel-firmware-amdgpu | package | 20250623-1.1 | noarch | OSS
i | libdrm_amdgpu1 | package | 2.4.124-2.3 | x86_64 | OSS
i+ | xf86-video-amdgpu | package | 23.0.0-3.3 | x86_64 | OSS
# zypper se -si Mesa | grep OSS
i+ | Mesa | package | 25.1.4-418.1 | x86_64 | OSS
i+ | Mesa-demo-egl | package | 9.0.0-5.1 | x86_64 | OSS
i+ | Mesa-demo-es | package | 9.0.0-5.1 | x86_64 | OSS
i+ | Mesa-demo-x | package | 9.0.0-5.1 | x86_64 | OSS
i+ | Mesa-dri | package | 25.1.4-418.1 | x86_64 | OSS
i+ | Mesa-gallium | package | 25.1.4-418.1 | x86_64 | OSS
i+ | Mesa-libEGL1 | package | 25.1.4-418.1 | x86_64 | OSS
i+ | Mesa-libGL1 | package | 25.1.4-418.1 | x86_64 | OSS
i+ | Mesa-vulkan-device-select | package | 25.1.4-418.1 | x86_64 | OSS
# zypper se -si l-long l-defa | grep x86
il | kernel-default | package | 6.14.6-2.1 | x86_64 | (System Packages)
il | kernel-default | package | 6.13.8-1.1 | x86_64 | (System Packages)
il | kernel-default | package | 6.11.8-1.1 | x86_64 | (System Packages)
il | kernel-default | package | 6.10.11-1.1 | x86_64 | (System Packages)
il | kernel-longterm | package | 6.6.74-1.1 | x86_64 | (System Packages)
il | kernel-longterm | package | 6.12.34-1.1 | x86_64 | OSS
#
I’m going to install an older version of kernel-firmware-amdgpu along with the 6.15.3 kernel to see what happens. I have the following I can try:
> ls -gGh kernel-firmware-amdgpu-202506*
-rw-r--r-- 1 25M Jun 13 01:50 kernel-firmware-amdgpu-20250606-1.1.noarch.rpm
-rw-r--r-- 1 25M Jun 23 12:12 kernel-firmware-amdgpu-20250616-1.1.noarch.rpm
-rw-r--r-- 1 26M Jun 23 09:09 kernel-firmware-amdgpu-20250620-1.1.noarch.rpm
-rw-r--r-- 1 26M Jun 24 16:01 kernel-firmware-amdgpu-20250623-1.1.noarch.rpm
#
……
6.15.3 with kernel-firmware-amdgpu-20250606 works normally. 6.15.3 with kernel-firmware-amdgpu-20250616 works too, and so too with 20250620 and 20250623; and now so does 6.12.34. 
I need another mental break, and then think about this some more……
Thanks for all your efforts
I’ll try to explain what is going on, I’m going to have to post a separate thread.
The fundamental problem is “config failed hub doesn’t have any ports! (error -19)”
Somewhere in the chipset AMD has created a virtual hub. This is identified by the kernel as physical hub and therefore looks for ports - which, of course, don’t exist - so boot crashes.
Apparently patch has been proposed (about 2 weeks ago) but I suppose it has to be tested before release.
I’ll post the couple of links I’ve found that explain the situation in the new thread.
USB port access or configuration surely cannot be indispensable to booting to a Plasma desktop, so that error surely must be irrelevant to your problem here.
Is all the installed software listed in post #36, other than old kernels, also installed on yours? It’s not an exhaustive list, but going lean, if also having excluding recommends, could have caused something needed to be omitted. What do the following report?:
zypper se -six sddm gdm lightdm xdm kdm | grep OSSsystemctl list-unit-files | grep dm | grep -vE 'mdadm|mdm|timer|udev|event|nfs'systemctl status sddm.service
Here I have:
# zypper se -six sddm gdm lightdm xdm kdm | grep OSS
i | sddm | package | 0.21.0-6.1 | x86_64 | OSS
i | xdm | package | 1.1.17-3.1 | x86_64 | OSS
# systemctl list-unit-files | grep dm | grep -vE 'mdadm|mdm|timer|udev|event|nfs'
sddm.service enabled disabled
xdm.service disabled disabled
# systemctl status sddm.service
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; preset: disabled)
Drop-In: /etc/systemd/system/display-manager.service.d
└─override.conf
Active: active (running) since Sat 2025-06-28 16:40:39 EDT; 38min ago
Invocation: 3d40c0d8716140ba8f316a023d4690ac
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 851 (sddm)
Tasks: 14 (limit: 7994)
CPU: 7.562s
CGroup: /system.slice/sddm.service
├─ 851 /usr/bin/sddm
└─2427 /usr/bin/Xorg.bin -nolisten tcp -dpi 120 -background none -seat seat0 vt1 -auth /run/sddm/xauth_EiVwsH -noreset -displayfd 16
Jun 28 17:19:11 ga88x sddm[851]: Loading theme configuration from "/usr/share/sddm/themes/maldives/theme.conf"
Jun 28 17:19:11 ga88x sddm[851]: Greeter starting...
Jun 28 17:19:11 ga88x sddm-helper[2443]: [PAM] Starting...
Jun 28 17:19:11 ga88x sddm-helper[2443]: [PAM] Authenticating...
Jun 28 17:19:11 ga88x sddm-helper[2443]: [PAM] returning.
Jun 28 17:19:11 ga88x sddm-helper[2443]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=466) by sddm(uid=0)
Jun 28 17:19:11 ga88x sddm-helper[2443]: Writing cookie to "/tmp/xauth_gbCIHo"
Jun 28 17:19:11 ga88x sddm-helper[2443]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-tcsVsw --theme /usr/share/sddm/themes/maldives"
Jun 28 17:19:11 ga88x sddm[851]: Greeter session started successfully
Jun 28 17:19:11 ga88x sddm[851]: Message received from greeter: Connect
#
I’m afraid it is… and it’s happening to people trying to install Fedora, Mandriva etc. It’s the kernel which refuses to go any further and if, as in recovery mode, it does go further, it stops because the configuration hasn’t loaded so there are no drivers to run anything.