Will FreeBSD 15.1 support AMD 9070XT GPUs?

fahrenheit said:
MrBSD would you consider opening tickets for the rebar and the wayland issues
Click to expand...
I really cant do that. Im open for testing and reporting here.
fahrenheit said:
(also are you trying with mesa-devel or the standard mesa package?).
Click to expand...
Yes. Im using mesa-devel package installed from official FreeBSD repo.
fahrenheit said:
In any case thank you for helping figuring out what is needed for rdna 4 support.
Click to expand...
Im here to help.
fahrenheit said:
Ah, one other request if you have the time, can you test with the 20260309 firmware package with rebar enabled also? It would be good to know if that is working as there's already a PR open for that. If it is not I'll open the PR for 20260519.

Regards
Click to expand...
The issue is still there with 20260309. I rebuilt the package with that tag, i went to BIOS, disabled Resizable Bar and driver failed to load. Went to BIOS again, enabled Resizable Bar, driver loaded properly.
 
MrBSD said:
I really cant do that. Im open for testing and reporting here.

Yes. Im using mesa-devel package installed from official FreeBSD repo.

Im here to help.

The issue is still there with 20260309. I rebuilt the package with that tag, i went to BIOS, disabled Resizable Bar and driver failed to load. Went to BIOS again, enabled Resizable Bar, driver loaded properly.
Click to expand...
Okay, I understand, thanks in any case.

So the good news is that there's already a PR open with a firmware package that actually works. The rebar issue is a pain but at least it's a known issue now. The wayland one is funny, at least we still have X :P
 
fahrenheit said:
Hmm, that would point to firmware version issues (i.e. like in a roulette).
MrBSD or matt_k can you check with the latest tag (20260519) and if not working with the main branch?

Thanks
Click to expand...
I tried 20260309 and also the method from hikiliki post #38

hikiliki's method leads to page fault ring: 157
Jun 8 19:59:48 slaanesh login[5689]: ROOT LOGIN (root) ON ttyv0
Jun 8 20:03:46 slaanesh kernel: drmn0: <drmn> on vgapci0
Jun 8 20:03:46 slaanesh kernel: vgapci0: child drmn0 requested pci_enable_io
Jun 8 20:03:46 slaanesh syslogd: last message repeated 1 times
Jun 8 20:03:46 slaanesh kernel: [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x7590 0x1043:0x0639 0xC0).
Jun 8 20:03:46 slaanesh kernel: [drm] register mmio base: 0xF7C00000
Jun 8 20:03:46 slaanesh kernel: [drm] register mmio size: 524288
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 0 <soc24_common>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 1 <gmc_v12_0>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 2 <ih_v7_0>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 3 <psp>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 4 <smu>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 5 <dm>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 6 <gfx_v12_0>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 7 <sdma_v7_0>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 8 <vcn_v5_0_0>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 9 <jpeg_v5_0_0>
Jun 8 20:03:46 slaanesh kernel: [drm] add ip block number 10 <mes_v12_0>
Jun 8 20:03:46 slaanesh kernel: drmn0: Fetched VBIOS from ROM BAR
Jun 8 20:03:46 slaanesh kernel: amdgpu: ATOM BIOS: 115-G262BPL0-101
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/psp_14_0_2_sos.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/psp_14_0_2_ta.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/smu_14_0_2.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/dcn_4_0_1_dmcub.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_pfp.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_me.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_rlc.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_mec.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_imu.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/sdma_7_0_0.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/vcn_5_0_0.bin'
Jun 8 20:03:46 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_uni_mes.bin'
Jun 8 20:03:46 slaanesh syslogd: last message repeated 1 times
Jun 8 20:03:46 slaanesh kernel: drmn0: Trusted Memory Zone (TMZ) feature not supported
Jun 8 20:03:46 slaanesh kernel: drmn0: PCIE atomic ops is not supported
Jun 8 20:03:46 slaanesh kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
Jun 8 20:03:46 slaanesh kernel: drmn0: VRAM: 16304M 0x0000008000000000 - 0x00000083FAFFFFFF (16304M used)
Jun 8 20:03:46 slaanesh kernel: drmn0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
Jun 8 20:03:46 slaanesh kernel: [drm] Detected VRAM RAM=16304M, BAR=256M
Jun 8 20:03:46 slaanesh kernel: [drm] RAM width 128bits GDDR6
Jun 8 20:03:46 slaanesh kernel: [drm] amdgpu: 16304M of VRAM memory ready
Jun 8 20:03:46 slaanesh kernel: [drm] amdgpu: 15819M of GTT memory ready.
Jun 8 20:03:46 slaanesh kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
Jun 8 20:03:46 slaanesh kernel: drmn0: PCIE GART of 512M enabled (table at 0x0000008000000000).
Jun 8 20:03:46 slaanesh kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Jun 8 20:03:46 slaanesh kernel: iicbus0: <Philips I2C bus> on lkpi_iic0
Jun 8 20:03:46 slaanesh kernel: iic0: <I2C generic I/O> on iicbus0
Jun 8 20:03:46 slaanesh kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Jun 8 20:03:46 slaanesh kernel: iicbus1: <Philips I2C bus> on lkpi_iic1
Jun 8 20:03:46 slaanesh kernel: iic1: <I2C generic I/O> on iicbus1
Jun 8 20:03:46 slaanesh kernel: [drm] Loading DMUB firmware via PSP: version=0x0A000C00
Jun 8 20:03:46 slaanesh kernel: [drm] Found VCN firmware Version ENC: 1.12 DEC: 9 VEP: 0 Revision: 26
Jun 8 20:03:46 slaanesh kernel: drmn0: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0)
Jun 8 20:03:46 slaanesh kernel: drmn0: in page starting at address 0x0000000000f00000 from client 18
Jun 8 20:03:46 slaanesh kernel: drmn0: MMVM_L2_PROTECTION_FAULT_STATUS_LO32:0x00000D3B
Jun 8 20:03:46 slaanesh kernel: drmn0: Faulty UTCL2 client ID: MP0 (0x6)
Jun 8 20:03:46 slaanesh kernel: drmn0: MORE_FAULTS: 0x1
Jun 8 20:03:46 slaanesh kernel: drmn0: WALKER_ERROR: 0x5
Jun 8 20:03:46 slaanesh kernel: drmn0: PERMISSION_FAULTS: 0x3
Jun 8 20:03:46 slaanesh kernel: drmn0: MAPPING_ERROR: 0x1
Jun 8 20:03:46 slaanesh kernel: drmn0: RW: 0x0
Jun 8 20:03:46 slaanesh kernel: drmn0: failed to load ucode DMCUB(0x3D) drmn0: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x910D)
Jun 8 20:03:46 slaanesh kernel: drmn0: RAS: optional ras ta ucode is not available
Jun 8 20:03:46 slaanesh kernel: drmn0: RAP: optional rap ta ucode is not available
Jun 8 20:03:46 slaanesh kernel: drmn0: SECUREDISPLAY: securedisplay ta ucode is not available
Jun 8 20:03:46 slaanesh kernel: drmn0: smu driver if version = 0x0000002e, smu fw if version = 0x00000033, smu fw program = 0, smu fw version = 0x00664600 (102.70.0)
Jun 8 20:03:46 slaanesh kernel: drmn0: SMU is initialized successfully!
Jun 8 20:03:46 slaanesh kernel: [drm] Display Core v3.2.301 initialized on DCN 4.0.1
Jun 8 20:03:46 slaanesh kernel: [drm] DP-HDMI FRL PCON supported
Jun 8 20:03:46 slaanesh kernel: [drm] Wait for DMUB auto-load failed: 3
Jun 8 20:03:46 slaanesh kernel: [drm] DMUB hardware initialized: version=0x0A000C00
Jun 8 20:03:46 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:03:48 slaanesh syslogd: last message repeated 10 times
Jun 8 20:03:48 slaanesh kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Jun 8 20:03:48 slaanesh kernel: iicbus2: <Philips I2C bus> on lkpi_iic2
Jun 8 20:03:48 slaanesh kernel: iic2: <I2C generic I/O> on iicbus2
Jun 8 20:03:48 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:03:48 slaanesh kernel: lkpi_iic3: <LinuxKPI I2C> on drmn0
Jun 8 20:03:48 slaanesh kernel: iicbus3: <Philips I2C bus> on lkpi_iic3
Jun 8 20:03:48 slaanesh kernel: iic3: <I2C generic I/O> on iicbus3
Jun 8 20:03:48 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:03:52 slaanesh syslogd: last message repeated 21 times
Jun 8 20:03:52 slaanesh kernel: lkpi_iic4: <LinuxKPI I2C> on drmn0
Jun 8 20:03:52 slaanesh kernel: iicbus4: <Philips I2C bus> on lkpi_iic4
Jun 8 20:03:52 slaanesh kernel: iic4: <I2C generic I/O> on iicbus4
Jun 8 20:03:52 slaanesh kernel: drmn0: SE 2, SH per SE 2, CU per SH 8, active_cu_number 32
Jun 8 20:03:52 slaanesh kernel: drmn0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jun 8 20:03:52 slaanesh kernel: drmn0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jun 8 20:03:52 slaanesh kernel: drmn0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jun 8 20:03:52 slaanesh kernel: drmn0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jun 8 20:03:52 slaanesh kernel: drmn0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jun 8 20:03:52 slaanesh kernel: drmn0: ring sdma0 uses VM inv eng 9 on hub 0
Jun 8 20:03:52 slaanesh kernel: drmn0: ring sdma1 uses VM inv eng 10 on hub 0
Jun 8 20:03:52 slaanesh kernel: drmn0: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Jun 8 20:03:52 slaanesh kernel: drmn0: ring jpeg_dec uses VM inv eng 1 on hub 8
Jun 8 20:03:52 slaanesh kernel: [drm] ring gfx_1.1.1 was added
Jun 8 20:03:52 slaanesh kernel: [drm] ring compute_1.2.2 was added
Jun 8 20:03:52 slaanesh kernel: [drm] ring sdma_1.3.3 was added
Jun 8 20:03:52 slaanesh kernel: [drm] ring gfx_1.1.1 ib test pass
Jun 8 20:03:52 slaanesh kernel: [drm] ring compute_1.2.2 ib test pass
Jun 8 20:03:52 slaanesh kernel: [drm] ring sdma_1.3.3 ib test pass
Jun 8 20:03:52 slaanesh kernel: vgapci0: child drmn0 requested pci_get_powerstate
Jun 8 20:03:52 slaanesh kernel: drmn0: Using BACO for runtime pm
Jun 8 20:03:52 slaanesh kernel: sysctl_add_oid: can't re-use a leaf (hw.dri.debug)!
Jun 8 20:03:52 slaanesh kernel: lkpi_iic5: <LinuxKPI I2C> on drm1
Jun 8 20:03:52 slaanesh kernel: iicbus5: <Philips I2C bus> on lkpi_iic5
Jun 8 20:03:52 slaanesh kernel: iic5: <I2C generic I/O> on iicbus5
Jun 8 20:03:52 slaanesh kernel: lkpi_iic6: <LinuxKPI I2C> on drm2
Jun 8 20:03:52 slaanesh kernel: iicbus6: <Philips I2C bus> on lkpi_iic6
Jun 8 20:03:52 slaanesh kernel: iic6: <I2C generic I/O> on iicbus6
Jun 8 20:03:52 slaanesh kernel: [drm] Initialized amdgpu 3.61.0 for drmn0 on minor 0
Jun 8 20:03:52 slaanesh kernel: VT: Replacing driver "efifb" with new "drmfb".
Jun 8 20:03:52 slaanesh kernel: [drm] pre_validate_dsc:1629 MST_DSC dsc precompute is not needed
Jun 8 20:03:53 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:04:00 slaanesh syslogd: last message repeated 42 times
Jun 8 20:04:00 slaanesh kernel: start FB_INFO:
Jun 8 20:04:00 slaanesh kernel: height=1440 width=2560 depth=32
Jun 8 20:04:00 slaanesh kernel: pbase=0x0 vbase=0xfffffe01488dc000
Jun 8 20:04:00 slaanesh kernel: name=drmn0 id=amdgpudrmfb flags=0x0 stride=10240
Jun 8 20:04:00 slaanesh kernel: end FB_INFO
Jun 8 20:04:01 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:04:10 slaanesh syslogd: last message repeated 49 times
Jun 8 20:05:17 slaanesh syslogd: exiting on signal 15
Jun 8 20:05:53 slaanesh syslogd: kernel boot file is /boot/kernel/kernel
Jun 8 20:05:53 slaanesh kernel: Waiting (max 60 seconds) for system process `vnlru' to stop... done
Jun 8 20:05:53 slaanesh kernel: Waiting (max 60 seconds) for system process `syncer' to stop...
Jun 8 20:05:53 slaanesh kernel: Syncing disks, vnodes remaining... 0 0 done
Jun 8 20:05:53 slaanesh kernel: All buffers synced.
20260309 method leads to page fault ring: 158
Jun 8 20:22:40 slaanesh login[47361]: ROOT LOGIN (root) ON ttyv0
Jun 8 20:22:44 slaanesh kernel: drmn0: <drmn> on vgapci0
Jun 8 20:22:44 slaanesh kernel: vgapci0: child drmn0 requested pci_enable_io
Jun 8 20:22:44 slaanesh syslogd: last message repeated 1 times
Jun 8 20:22:44 slaanesh kernel: [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x7590 0x1043:0x0639 0xC0).
Jun 8 20:22:44 slaanesh kernel: [drm] register mmio base: 0xF7C00000
Jun 8 20:22:44 slaanesh kernel: [drm] register mmio size: 524288
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 0 <soc24_common>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 1 <gmc_v12_0>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 2 <ih_v7_0>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 3 <psp>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 4 <smu>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 5 <dm>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 6 <gfx_v12_0>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 7 <sdma_v7_0>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 8 <vcn_v5_0_0>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 9 <jpeg_v5_0_0>
Jun 8 20:22:44 slaanesh kernel: [drm] add ip block number 10 <mes_v12_0>
Jun 8 20:22:44 slaanesh kernel: drmn0: Fetched VBIOS from ROM BAR
Jun 8 20:22:44 slaanesh kernel: amdgpu: ATOM BIOS: 115-G262BPL0-101
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/psp_14_0_2_sos.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/psp_14_0_2_ta.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/smu_14_0_2.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/dcn_4_0_1_dmcub.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_pfp.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_me.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_rlc.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_mec.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_imu.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/sdma_7_0_0.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/vcn_5_0_0.bin'
Jun 8 20:22:44 slaanesh kernel: drmn0: successfully loaded firmware image 'amdgpu/gc_12_0_0_uni_mes.bin'
Jun 8 20:22:44 slaanesh syslogd: last message repeated 1 times
Jun 8 20:22:44 slaanesh kernel: drmn0: Trusted Memory Zone (TMZ) feature not supported
Jun 8 20:22:44 slaanesh kernel: drmn0: PCIE atomic ops is not supported
Jun 8 20:22:44 slaanesh kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
Jun 8 20:22:44 slaanesh kernel: drmn0: VRAM: 16304M 0x0000008000000000 - 0x00000083FAFFFFFF (16304M used)
Jun 8 20:22:44 slaanesh kernel: drmn0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
Jun 8 20:22:44 slaanesh kernel: [drm] Detected VRAM RAM=16304M, BAR=256M
Jun 8 20:22:44 slaanesh kernel: [drm] RAM width 128bits GDDR6
Jun 8 20:22:44 slaanesh kernel: [drm] amdgpu: 16304M of VRAM memory ready
Jun 8 20:22:44 slaanesh kernel: [drm] amdgpu: 15819M of GTT memory ready.
Jun 8 20:22:44 slaanesh kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
Jun 8 20:22:44 slaanesh kernel: drmn0: PCIE GART of 512M enabled (table at 0x0000008000000000).
Jun 8 20:22:44 slaanesh kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Jun 8 20:22:44 slaanesh kernel: iicbus0: <Philips I2C bus> on lkpi_iic0
Jun 8 20:22:44 slaanesh kernel: iic0: <I2C generic I/O> on iicbus0
Jun 8 20:22:44 slaanesh kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Jun 8 20:22:44 slaanesh kernel: iicbus1: <Philips I2C bus> on lkpi_iic1
Jun 8 20:22:44 slaanesh kernel: iic1: <I2C generic I/O> on iicbus1
Jun 8 20:22:44 slaanesh kernel: [drm] Loading DMUB firmware via PSP: version=0x0A000C00
Jun 8 20:22:44 slaanesh kernel: [drm] Found VCN firmware Version ENC: 1.12 DEC: 9 VEP: 0 Revision: 26
Jun 8 20:22:44 slaanesh kernel: drmn0: [mmhub] page fault (src_id:0 ring:158 vmid:0 pasid:0)
Jun 8 20:22:44 slaanesh kernel: drmn0: in page starting at address 0x0000000000f00000 from client 18
Jun 8 20:22:44 slaanesh kernel: drmn0: MMVM_L2_PROTECTION_FAULT_STATUS_LO32:0x00000D3D
Jun 8 20:22:44 slaanesh kernel: drmn0: Faulty UTCL2 client ID: MP0 (0x6)
Jun 8 20:22:44 slaanesh kernel: drmn0: MORE_FAULTS: 0x1
Jun 8 20:22:44 slaanesh kernel: drmn0: WALKER_ERROR: 0x6
Jun 8 20:22:44 slaanesh kernel: drmn0: PERMISSION_FAULTS: 0x3
Jun 8 20:22:44 slaanesh kernel: drmn0: MAPPING_ERROR: 0x1
Jun 8 20:22:44 slaanesh kernel: drmn0: RW: 0x0
Jun 8 20:22:44 slaanesh kernel: drmn0: failed to load ucode DMCUB(0x3D) drmn0: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x910D)
Jun 8 20:22:44 slaanesh kernel: drmn0: RAS: optional ras ta ucode is not available
Jun 8 20:22:44 slaanesh kernel: drmn0: RAP: optional rap ta ucode is not available
Jun 8 20:22:44 slaanesh kernel: drmn0: SECUREDISPLAY: securedisplay ta ucode is not available
Jun 8 20:22:44 slaanesh kernel: drmn0: smu driver if version = 0x0000002e, smu fw if version = 0x00000033, smu fw program = 0, smu fw version = 0x00664600 (102.70.0)
Jun 8 20:22:44 slaanesh kernel: drmn0: SMU is initialized successfully!
Jun 8 20:22:44 slaanesh kernel: [drm] Display Core v3.2.301 initialized on DCN 4.0.1
Jun 8 20:22:44 slaanesh kernel: [drm] DP-HDMI FRL PCON supported
Jun 8 20:22:44 slaanesh kernel: [drm] Wait for DMUB auto-load failed: 3
Jun 8 20:22:44 slaanesh kernel: [drm] DMUB hardware initialized: version=0x0A000C00
Jun 8 20:22:45 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:22:47 slaanesh syslogd: last message repeated 10 times
Jun 8 20:22:47 slaanesh kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Jun 8 20:22:47 slaanesh kernel: iicbus2: <Philips I2C bus> on lkpi_iic2
Jun 8 20:22:47 slaanesh kernel: iic2: <I2C generic I/O> on iicbus2
Jun 8 20:22:47 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:22:47 slaanesh kernel: lkpi_iic3: <LinuxKPI I2C> on drmn0
Jun 8 20:22:47 slaanesh kernel: iicbus3: <Philips I2C bus> on lkpi_iic3
Jun 8 20:22:47 slaanesh kernel: iic3: <I2C generic I/O> on iicbus3
Jun 8 20:22:47 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:22:51 slaanesh syslogd: last message repeated 21 times
Jun 8 20:22:51 slaanesh kernel: lkpi_iic4: <LinuxKPI I2C> on drmn0
Jun 8 20:22:51 slaanesh kernel: iicbus4: <Philips I2C bus> on lkpi_iic4
Jun 8 20:22:51 slaanesh kernel: iic4: <I2C generic I/O> on iicbus4
Jun 8 20:22:51 slaanesh kernel: drmn0: SE 2, SH per SE 2, CU per SH 8, active_cu_number 32
Jun 8 20:22:51 slaanesh kernel: drmn0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jun 8 20:22:51 slaanesh kernel: drmn0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jun 8 20:22:51 slaanesh kernel: drmn0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jun 8 20:22:51 slaanesh kernel: drmn0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jun 8 20:22:51 slaanesh kernel: drmn0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jun 8 20:22:51 slaanesh kernel: drmn0: ring sdma0 uses VM inv eng 9 on hub 0
Jun 8 20:22:51 slaanesh kernel: drmn0: ring sdma1 uses VM inv eng 10 on hub 0
Jun 8 20:22:51 slaanesh kernel: drmn0: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Jun 8 20:22:51 slaanesh kernel: drmn0: ring jpeg_dec uses VM inv eng 1 on hub 8
Jun 8 20:22:51 slaanesh kernel: [drm] ring gfx_1.1.1 was added
Jun 8 20:22:51 slaanesh kernel: [drm] ring compute_1.2.2 was added
Jun 8 20:22:51 slaanesh kernel: [drm] ring sdma_1.3.3 was added
Jun 8 20:22:51 slaanesh kernel: [drm] ring gfx_1.1.1 ib test pass
Jun 8 20:22:51 slaanesh kernel: [drm] ring compute_1.2.2 ib test pass
Jun 8 20:22:51 slaanesh kernel: [drm] ring sdma_1.3.3 ib test pass
Jun 8 20:22:51 slaanesh kernel: vgapci0: child drmn0 requested pci_get_powerstate
Jun 8 20:22:51 slaanesh kernel: drmn0: Using BACO for runtime pm
Jun 8 20:22:51 slaanesh kernel: sysctl_add_oid: can't re-use a leaf (hw.dri.debug)!
Jun 8 20:22:51 slaanesh kernel: lkpi_iic5: <LinuxKPI I2C> on drm1
Jun 8 20:22:51 slaanesh kernel: iicbus5: <Philips I2C bus> on lkpi_iic5
Jun 8 20:22:51 slaanesh kernel: iic5: <I2C generic I/O> on iicbus5
Jun 8 20:22:51 slaanesh kernel: lkpi_iic6: <LinuxKPI I2C> on drm2
Jun 8 20:22:51 slaanesh kernel: iicbus6: <Philips I2C bus> on lkpi_iic6
Jun 8 20:22:51 slaanesh kernel: iic6: <I2C generic I/O> on iicbus6
Jun 8 20:22:51 slaanesh kernel: [drm] Initialized amdgpu 3.61.0 for drmn0 on minor 0
Jun 8 20:22:51 slaanesh kernel: VT: Replacing driver "efifb" with new "drmfb".
Jun 8 20:22:51 slaanesh kernel: [drm] pre_validate_dsc:1629 MST_DSC dsc precompute is not needed
Jun 8 20:22:51 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:23:04 slaanesh syslogd: last message repeated 70 times
Jun 8 20:23:04 slaanesh kernel: start FB_INFO:
Jun 8 20:23:04 slaanesh kernel: height=1440 width=2560 depth=32
Jun 8 20:23:04 slaanesh kernel: pbase=0x0 vbase=0xfffffe013e093000
Jun 8 20:23:04 slaanesh kernel: name=drmn0 id=amdgpudrmfb flags=0x0 stride=10240
Jun 8 20:23:04 slaanesh kernel: end FB_INFO
Jun 8 20:23:05 slaanesh login[47661]: in prompt_tty(): tcsetattr(): Inappropriate ioctl for device
Jun 8 20:23:05 slaanesh login[47661]: 1 LOGIN FAILURE ON ttyv1
Jun 8 20:23:05 slaanesh syslogd: exiting on signal 15
Jun 8 20:23:54 slaanesh syslogd: kernel boot file is /boot/kernel/kernel
Jun 8 20:23:54 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:23:54 slaanesh kernel: Waiting (max 60 seconds) for system process `vnlru' to stop... done
Jun 8 20:23:54 slaanesh kernel: drmn0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 8 20:23:54 slaanesh syslogd: last message repeated 20 times
Jun 8 20:23:54 slaanesh kernel: Waiting (max 60 seconds) for system process `syncer' to stop...
Jun 8 20:23:54 slaanesh kernel: Syncing disks, vnodes remaining... 0 0 done
Jun 8 20:23:54 slaanesh kernel: All buffers synced.
Jun 8 20:23:54 slaanesh kernel: Uptime: 55s
 
I managed to start plasma wayland session on AMD RDNA4 card but keyboard and mouse are not responding. It didnt crash because i can see tray icons appearing while my startup applications are loading. If anyone wants to try, follow these instructions.

First disable SDDM or whatever display manager you are using, and make sure that your non-root account is in video group.

Install seatd and plasma
Code: 
# pkg install kde seatd
Enable seatd and dbus
Code: 
 # sysrc seatd_enable="YES" && sysrc dbus_enable="YES"
Start seatd service or reboot the system.
Code: 
# service seatd start
Create a script in your ~ directory.
Code: 
echo "exec dbus-run-session startplasma-wayland" > ~/start_plasma.sh
Make it executable
Code: 
chmod +x start_plasma.sh
Start plasma wayland by typing
Code: 
./start_plasma.sh

As i said above, keyboard and mouse are completely cut once desktop appears. You wont be able to go to TTY. Its hard reboot from here, but Plasma wayland session definitely starts.
 
MrBSD said:
I managed to start plasma wayland session on AMD RDNA4 card but keyboard and mouse are not responding. It didnt crash because i can see tray icons appearing while my startup applications are loading. If anyone wants to try, follow these instructions.

First disable SDDM or whatever display manager you are using, and make sure that your non-root account is in video group.

Install seatd and plasma
Code: 
# pkg install kde seatd
Enable seatd and dbus
Code: 
 # sysrc seatd_enable="YES" && sysrc dbus_enable="YES"
Start seatd service or reboot the system.
Code: 
# service seatd start
Create a script in your ~ directory.
Code: 
echo "exec dbus-run-session startplasma-wayland" > ~/start_plasma.sh
Make it executable
Code: 
chmod +x start_plasma.sh
Start plasma wayland by typing
Code: 
./start_plasma.sh

As i said above, keyboard and mouse are completely cut once desktop appears. You wont be able to go to TTY. Its hard reboot from here, but Plasma wayland session definitely starts.
Click to expand...
Can you check if the issue is hardware cursor?
https://forums.freebsd.org/threads/when-to-use-drm-latest-kmod-aka-version-6-9.102642/post-761229
 
fahrenheit said:
Can you check if the issue is hardware cursor?
https://forums.freebsd.org/threads/when-to-use-drm-latest-kmod-aka-version-6-9.102642/post-761229
Click to expand...
Nope. Same thing. And those variables are for mouse pointer only. My keyboard gets cut of as well so there might me some input issue here. I also tried plugging out and then plugging in both mouse and keyboard, but nothing happens. The weirdest part is the fact that it didnt crash. Because i see telegram notifications in system tray. Its just keyboard and mouse that are dead.

And just for shit and giggles, i tried putting this...
Code: 
exec dbus-run-session startplasma-wayland
...into my .xinitrc file and start plasma with startx. It works, but plasma starts in 1024x768 resolution with no options to change it. But both keyboard and mouse work. Probably because its running through xwayland.
 
MrBSD said:
And just for shit and giggles, i tried putting this...
exec dbus-run-session startplasma-wayland...into my .xinitrc file and start plasma with startx. It works, but plasma starts in 1024x768 resolution with no options to change it. But both keyboard and mouse work. Probably because its running through xwayland.
Click to expand...
About this one, can you please post a screenie (with hardware details) of the systemsettings app? You got me really curious here...
 
astyle said:
About this one, can you please post a screenie (with hardware details) of the systemsettings app? You got me really curious here...
Click to expand...
Here is the hardware details page

Screenshot_20260609_154735.png


And this is display settings page.

Screenshot_20260609_154909.png


What you see here looks super tiny on 4K display. This small 1024x768 section is positioned on the top left side of the screen. You can barely see anything. Not sure if this is of any use because this is not how you would start KDE Plasma.
 
You must log in or register to reply here.
Back
Top