Installing Tumbleweed on a new machine consisting of an AMD Ryzen 5 8600G processor mounted on an ASRock A620M Pro RS mother board which uses the AMD A620 chipset. Chapter 3.
The first chapter led to being given a patch to alleviate the problem of a virtual hub.
Now I have arrived at discovering that the display system doesn’t complete loading. This is the result of journalctl | grep drm which I would like interpreting:
Jul 13 11:18:12 localhost kernel: ACPI: bus type drm_connector registered
Jul 13 11:18:12 localhost kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Jul 13 11:18:12 localhost kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Jul 13 11:18:12 localhost kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Jul 13 11:18:17 localhost systemd[1]: Starting Load Kernel Module drm...
Jul 13 11:18:17 localhost systemd[1]: modprobe@drm.service: Deactivated successfully.
Jul 13 11:18:17 localhost systemd[1]: Finished Load Kernel Module drm.
Jul 13 11:18:17 localhost kernel: [drm] Initialized amdxdna_accel_driver 0.0.0 for 0000:0d:00.1 on minor 0
Jul 13 11:18:18 localhost kernel: [drm] amdgpu kernel modesetting enabled.
Jul 13 11:18:18 localhost kernel: [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x15BF 0x1849:0x35BF 0x05).
Jul 13 11:18:18 localhost kernel: [drm] register mmio base: 0xF6700000
Jul 13 11:18:18 localhost kernel: [drm] register mmio size: 524288
Jul 13 11:18:18 localhost kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
Jul 13 11:18:18 localhost kernel: [drm] Detected VRAM RAM=512M, BAR=512M
Jul 13 11:18:18 localhost kernel: [drm] RAM width 64bits DDR5
Jul 13 11:18:18 localhost kernel: [drm] amdgpu: 512M of VRAM memory ready
Jul 13 11:18:18 localhost kernel: [drm] amdgpu: 7532M of GTT memory ready.
Jul 13 11:18:18 localhost kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
Jul 13 11:18:18 localhost kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Jul 13 11:18:18 localhost kernel: [drm] Loading DMUB firmware via PSP: version=0x08005000
Jul 13 11:18:19 localhost.localdomain kernel: [drm] Display Core v3.2.325 initialized on DCN 3.1.4
Jul 13 11:18:19 localhost.localdomain kernel: [drm] DP-HDMI FRL PCON supported
Jul 13 11:18:19 localhost.localdomain kernel: [drm] DMUB hardware initialized: version=0x08005000
Jul 13 11:18:19 localhost.localdomain kernel: [drm] ring gfx_32768.1.1 was added
Jul 13 11:18:19 localhost.localdomain kernel: [drm] ring compute_32768.2.2 was added
Jul 13 11:18:19 localhost.localdomain kernel: [drm] ring sdma_32768.3.3 was added
Jul 13 11:18:19 localhost.localdomain kernel: [drm] ring gfx_32768.1.1 ib test pass
Jul 13 11:18:19 localhost.localdomain kernel: [drm] ring compute_32768.2.2 ib test pass
Jul 13 11:18:19 localhost.localdomain kernel: [drm] ring sdma_32768.3.3 ib test pass
Jul 13 11:18:19 localhost.localdomain kernel: amdgpu 0000:0c:00.0: [drm] Registered 4 planes with drm panic
Jul 13 11:18:19 localhost.localdomain kernel: [drm] Initialized amdgpu 3.63.0 for 0000:0c:00.0 on minor 1
Jul 13 11:18:19 localhost.localdomain kernel: fbcon: amdgpudrmfb (fb0) is primary device
Jul 13 11:18:19 localhost.localdomain kernel: amdgpu 0000:0c:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Jul 13 11:18:19 localhost.localdomain kernel: [drm] pre_validate_dsc:1627 MST_DSC dsc precompute is not needed
Jul 13 11:18:20 localhost.localdomain kernel: amdgpu 0000:0c:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - optc314_disable_crtc line:145
Previous suggestions is that it is a problem with amdgpu, but looking at the sequence of events, I wonder if it’s not drm having problems before initializing amdgpu.
I think it’s going to be a bug report either to kernel devs or amdgpu - where do I go to get my head bitten off ?