Hello, Linux newbie here. I ran into a disk failure, and so had to install an OS again. I decided to try OM Rome, but the live boot system simply crashes merely seconds after initialising plasma. The screen goes black, then seemingly random pixels fill it, then, after quite some time, I’m thrown back to the user log in screen.
Even bigger of a problem is the fact that other distributions exhibit the very same behaviour, with the very same error logs.
The log bellow was extracted using dmesg -l err
[qui jan 16 22:04:51 2025] systemd[1]: systemd-importd.socket: Socket service systemd-importd.service not loaded, refusing.
[qui jan 16 22:04:51 2025] systemd[1]: Failed to listen on systemd-importd.socket - Disk Image Download Service Socket.
[qui jan 16 22:05:40 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, signaled seq=3151, emitted seq=3153
[qui jan 16 22:05:40 2025] amdgpu 0000:01:00.0: amdgpu: Process information: process calamares pid 2010 thread calamares:cs0 pid 2075
[qui jan 16 22:05:40 2025] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] ERROR ring kiq_0.2.1.0 test failed (-110)
[qui jan 16 22:05:40 2025] [drm:gfx_v8_0_hw_fini.llvm.10992183699379143067 [amdgpu]] ERROR KCQ disable failed
[qui jan 16 22:05:40 2025] amdgpu: cp is busy, skip halt cp
[qui jan 16 22:05:40 2025] amdgpu: rlc is busy, skip halt rlc
[qui jan 16 22:05:41 2025] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] ERROR ring comp_1.0.3 test failed (-110)
[qui jan 16 22:05:41 2025] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] ERROR ring comp_1.0.5 test failed (-110)
[qui jan 16 22:05:41 2025] [drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialize parser -125!
[qui jan 16 22:05:52 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:02 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:12 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:22 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:33 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:43 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:53 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:03 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:14 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:24 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:34 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
The only difference between any of them is the process that triggers it. It’s often calamares (installing is the first thing I try), but when the crash occurs before I even manage to open the installer, dmesg will blame Wayland itself.
Even if the issue cannot be solved here, I would like at least some information on where and how to forward this. Also, I apologise if any relevant info is missing (newb, don’t even know where to start) and will provide more if prompted. I just want my machine to work again