Will FreeBSD 15.1 support AMD 9070XT GPUs?

MrBSD said:
No. Because i dont use display managers. What i said about SDDM was just a test. Im starting my desktops from tty. I removed both SDDM and KDE because they all suck even when everything works.
Click to expand...
Did you try it with an another card? It's just when starting from CLI, I had this issue with my iGPU as well, it worked fine with Ly
 
DoctorRainer said:
Did you try it with an another card?
Click to expand...
Why should i? This is not a troubleshooting thread. KDE on FreeBSD is working with other cards. The goal is to make it work with RDNA4 based card.
DoctorRainer said:
It's just when starting from CLI, I had this issue with my iGPU as well, it worked fine with Ly
Click to expand...
I suggest you read this thread from the beginning as well as this one before you reply here or make any suggestions. Ly is not going to work because plasma-wayland is not working with this experimental combination of drm-612-kmod and amd firmware on RDNA4 based cards. If i cant start it directly, there is nothing that Ly can do to magically make it working. Stop forcing it please.
 
MrBSD said:
I suggest you read this thread from the beginning as well as this one before you reply here or make any suggestions. Ly is not going to work because plasma-wayland is not working with this experimental combination of drm-612-kmod and amd firmware on RDNA4 based cards. If i cant start it directly, there is nothing that Ly can do to magically make it working. Stop forcing it please.
Click to expand...
-_-
1781804399297.jpeg
 
UPD:
Refresh rate is capped at 120hz on my 240hz monitor. I wonder, if it's a limitation of the current driver or could it be that I messed something up? Don't get me wrong, the system is buttery smooth right now even with 120hz, but it's still concerning that I cannot select the native refresh rate
1781805964722.png
 
cmicallef said:
Can you please dump the card's vendor id, device id, etc with pciconf (e.g. pciconf -lv | grep -C 3 9070 )
Click to expand...
sh: 
subclass   = PCI-PCI
vgapci0@pci0:3:0:0:     class=0x030000 rev=0xc3 hdr=0x00 vendor=0x1002 device=0x7550 subvendor=0x1da2 subdevice=0x2490
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Navi 48 [Radeon RX 9070/9070 XT/9070 GRE]'
    class      = display
    subclass   = VGA
hdac0@pci0:3:0:1:       class=0x040300 rev=0x00 hdr=0x00 vendor=0x1002 device=0xab40 subvendor=0x1002 subdevice=0xab40

I bought it here Sapphire Pulse RX 9070, if you want exact details
 
MrBSD said:
Ly is not going to work because plasma-wayland is not working with this experimental combination of drm-612-kmod and amd firmware on RDNA4 based cards. If i cant start it directly, there is nothing that Ly can do to magically make it working
Click to expand...
Well, if it works for me with Ly, then it's clearly *magically* making it work. Like I said before, I had EXACTLY the same issue as you did when I was trying to run it via tty myself. The issue should NOT be related to you using RDNA4. That's why I asked if you tried to run it with another AMD GPU, since you would get the SAME issue with mouse/keyboard not working. It is because there are slightly different ways to do so. I'm just saying you could at least try Ly where more knowledgeable people could put everything correctly. But generally speaking, if I check the command that Ly actually runs, /usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-wayland should work for you, since it works for me
 
UPDATE:

I bought new DisplayPort 2.1 cable instead of the HDMI I used before and now it it works in 4K@240hz. Which is a bit weird, because Windows 11 worked in 4K@240hz with that HDMI cable
 
Update:
I bought a new motherboard+CPU+accessories, the card 9060 is now working properly with drm-612-kmod built from ports + necessary firmware packages. Resizable SAM in BIOS is enabled. I did not try to disable it yet. If anyone is interested, I may try it.
Code: 
[I] ~ $ pkg info | grep firmware
gpu-firmware-amd-kmod-dcn-3-1-5-20260519.1501000 Firmware modules for dcn_3_1_5 AMD GPUs
gpu-firmware-amd-kmod-dcn-4-0-1-20260519.1501000 Firmware modules for dcn_4_0_1 AMD GPUs
gpu-firmware-amd-kmod-gc-10-3-6-20260519.1501000 Firmware modules for gc_10_3_6 AMD GPUs
gpu-firmware-amd-kmod-gc-12-0-0-20260519.1501000 Firmware modules for gc_12_0_0 AMD GPUs
gpu-firmware-amd-kmod-kaveri-20250109.1501000 Firmware modules for kaveri AMD GPUs
gpu-firmware-amd-kmod-psp-13-0-5-20260519.1501000 Firmware modules for psp_13_0_5 AMD GPUs
gpu-firmware-amd-kmod-psp-14-0-2-20260519.1501000 Firmware modules for psp_14_0_2 AMD GPUs
gpu-firmware-amd-kmod-sdma-5-2-6-20260519.1501000 Firmware modules for sdma_5_2_6 AMD GPUs
gpu-firmware-amd-kmod-sdma-7-0-0-20260519.1501000 Firmware modules for sdma_7_0_0 AMD GPUs
gpu-firmware-amd-kmod-smu-14-0-2-20260519.1501000 Firmware modules for smu_14_0_2 AMD GPUs
gpu-firmware-amd-kmod-vcn-3-1-2-20260519.1501000 Firmware modules for vcn_3_1_2 AMD GPUs
gpu-firmware-amd-kmod-vcn-5-0-0-20260519.1501000 Firmware modules for vcn_5_0_0 AMD GPUs
wifi-firmware-ath12k-kmod-wcn7850_hw20-20251125 Firmware modules for the ath12k (wcn7850_hw20) WiFi NIC driver
[I] ~ $ pkg info | grep drm
drm-612-kmod-6.12.85.1501000_1 Direct Rendering Manager (DRM) GPU drivers
drm_info-2.10.0                Dump info about DRM devices
libdrm-2.4.133,1               Direct Rendering Manager library and headers
 
[I] ~ $ pciconf -lv | grep -B3 display
vgapci0@pci0:3:0:0:    class=0x030000 rev=0xc0 hdr=0x00 vendor=0x1002 device=0x7590 subvendor=0x1043 subdevice=0x0639
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Navi 44 [Radeon RX 9060 XT]'
    class      = display
Note: do not be confused by these:
dcn_3_1_5, gc_10_3_6, psp_13_0_5, sdma_5_2_6, vcn_3_1_2
those were for my integrated radeon graphics card, which is now disabled in BIOS. The RX9060 does not work when the integrated card is enabled in BIOS, kdldloading amdgpu leads to some kind of confusion and reboot (unsuprisingly, the computer does not know which card do I want).
 
matt_k said:
Update:
I bought a new motherboard+CPU+accessories, the card 9060 is now working properly with drm-612-kmod built from ports + necessary firmware packages. Resizable SAM in BIOS is enabled. I did not try to disable it yet. If anyone is interested, I may try it.
Code: 
[I] ~ $ pkg info | grep firmware
gpu-firmware-amd-kmod-dcn-3-1-5-20260519.1501000 Firmware modules for dcn_3_1_5 AMD GPUs
gpu-firmware-amd-kmod-dcn-4-0-1-20260519.1501000 Firmware modules for dcn_4_0_1 AMD GPUs
gpu-firmware-amd-kmod-gc-10-3-6-20260519.1501000 Firmware modules for gc_10_3_6 AMD GPUs
gpu-firmware-amd-kmod-gc-12-0-0-20260519.1501000 Firmware modules for gc_12_0_0 AMD GPUs
gpu-firmware-amd-kmod-kaveri-20250109.1501000 Firmware modules for kaveri AMD GPUs
gpu-firmware-amd-kmod-psp-13-0-5-20260519.1501000 Firmware modules for psp_13_0_5 AMD GPUs
gpu-firmware-amd-kmod-psp-14-0-2-20260519.1501000 Firmware modules for psp_14_0_2 AMD GPUs
gpu-firmware-amd-kmod-sdma-5-2-6-20260519.1501000 Firmware modules for sdma_5_2_6 AMD GPUs
gpu-firmware-amd-kmod-sdma-7-0-0-20260519.1501000 Firmware modules for sdma_7_0_0 AMD GPUs
gpu-firmware-amd-kmod-smu-14-0-2-20260519.1501000 Firmware modules for smu_14_0_2 AMD GPUs
gpu-firmware-amd-kmod-vcn-3-1-2-20260519.1501000 Firmware modules for vcn_3_1_2 AMD GPUs
gpu-firmware-amd-kmod-vcn-5-0-0-20260519.1501000 Firmware modules for vcn_5_0_0 AMD GPUs
wifi-firmware-ath12k-kmod-wcn7850_hw20-20251125 Firmware modules for the ath12k (wcn7850_hw20) WiFi NIC driver
[I] ~ $ pkg info | grep drm
drm-612-kmod-6.12.85.1501000_1 Direct Rendering Manager (DRM) GPU drivers
drm_info-2.10.0                Dump info about DRM devices
libdrm-2.4.133,1               Direct Rendering Manager library and headers
 
[I] ~ $ pciconf -lv | grep -B3 display
vgapci0@pci0:3:0:0:    class=0x030000 rev=0xc0 hdr=0x00 vendor=0x1002 device=0x7590 subvendor=0x1043 subdevice=0x0639
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Navi 44 [Radeon RX 9060 XT]'
    class      = display
Note: do not be confused by these:
dcn_3_1_5, gc_10_3_6, psp_13_0_5, sdma_5_2_6, vcn_3_1_2
those were for my integrated radeon graphics card, which is now disabled in BIOS. The RX9060 does not work when the integrated card is enabled in BIOS, kdldloading amdgpu leads to some kind of confusion and reboot (unsuprisingly, the computer does not know which card do I want).
Click to expand...

So you have a Raphael (Ryzen 7xxx igpu) or Granite Ridge (Ryzen 9xxx igpu) integrated card. You are not the first to have to disable integrated cards to get a working system (intel igpu + nvidia dgpu have the same behavior), so I'm leaning to issues with the FreeBSD port of drm and initialization of the drm stack as it is supposed to work (hybrid graphics being the main use).

In any case congrats on being able to use your hardware :)
 
MrBSD said:
Please try it. Im really curious. Enable CSM and disable RBAR.
Click to expand...
It does not work, it reboots automatically.
fahrenheit said:
So you have a Raphael (Ryzen 7xxx igpu) or Granite Ridge (Ryzen 9xxx igpu) integrated card. You are not the first to have to disable integrated cards to get a working system (intel igpu + nvidia dgpu have the same behavior), so I'm leaning to issues with the FreeBSD port of drm and initialization of the drm stack as it is supposed to work (hybrid graphics being the main use).

In any case congrats on being able to use your hardware :)
Click to expand...
Yes, it is a Granite Ridge IGPU.

Does anyone have any idea what to look for in order to make acpi sleep work with this card? I used to use the 'zzz' command a lot. I don't even know where to start.

acpiconf -s 3 makes the computer sleep, but upon waking up, the graphics card does not wake up. The computer seems responsive though and I can reboot it via ctrl+alt+del.
acpiconf -s 4 makes the computer turn off completely.
acpiconf -s 5 does not work, even though it should.
Code: 
root@khorne:~ # sysctl hw.acpi | grep support
hw.acpi.supported_sleep_state: S3 S4 S5

root@khorne:~ # acpiconf -s 5
acpiconf: invalid sleep type (5)

I think that the sleep with acpiconf -s 3 does work, but there is something preventing the graphics card from resuming operation. (although I think this question may warrant a stand-alone thread)
 
matt_k hibernation (s4) is still not supported (see foundation ticket: https://github.com/FreeBSDFoundation/proj-laptop/issues/29) and is related with s0ix support (which is also work in progress).
S5 is shutdown so poweroff should work.
As for S3, no ideia, my suggestion is figuring out where is the issue with the following tests:
  1. Remove amdgpu from kld_list, restart and from console try to suspend and resume, it it works go to #2
  2. Load amdgpu, and still from console (i.e. don't start X or wayland) try to suspend and resume, if it works go to #3
  3. Start X or wayland, switch to console (CTRL+ATL+F2 for example) and try to suspend and resume
(adapted from: https://wiki.freebsd.org/SuspendResume )

If the issue is on #1, maybe there is some kernel sysctl that you can use (try the mailing lists or opening a ticket on bugzilla), if it's on #2 maybe there's some tunable (compat.linuxkpi.amdgpu_*) that may work (check linux forums or some such). If it's on #3 really don't know but in both cases (#2 and #3 a new ticket on the github drm-kmod repo may help).
 
fahrenheit said:
matt_k hibernation (s4) is still not supported (see foundation ticket: https://github.com/FreeBSDFoundation/proj-laptop/issues/29) and is related with s0ix support (which is also work in progress).
S5 is shutdown so poweroff should work.
As for S3, no ideia, my suggestion is figuring out where is the issue with the following tests:
  1. Remove amdgpu from kld_list, restart and from console try to suspend and resume, it it works go to #2
  2. Load amdgpu, and still from console (i.e. don't start X or wayland) try to suspend and resume, if it works go to #3
  3. Start X or wayland, switch to console (CTRL+ATL+F2 for example) and try to suspend and resume
(adapted from: https://wiki.freebsd.org/SuspendResume )

If the issue is on #1, maybe there is some kernel sysctl that you can use (try the mailing lists or opening a ticket on bugzilla), if it's on #2 maybe there's some tunable (compat.linuxkpi.amdgpu_*) that may work (check linux forums or some such). If it's on #3 really don't know but in both cases (#2 and #3 a new ticket on the github drm-kmod repo may help).
Click to expand...
Thank you, the issue is on #1, so not amdgpu related. Or at least it happens even without amdgpu. Thanks, I'll look into it and/or make a separate thread for this if I'm unable to continue by myself.
 
You must log in or register to reply here.
Back
Top