Lexa PRO staying in framebuffer mode

[ElectricJozin]

I am running a HP 850 G5 with hybrid graphics. The integrated GPU is UHD Graphics 620, the dedicated GPU is a Lexa PRO chip. FreeBSD version is 13.2.
The user is in the video group.
I am trying to use the discrete GPU so I set "hybrid graphics" in the BIOS (the only other option is integrated).
After loading the kmod of amdgpu, dmesg reports the following:

[drm] amdgpu kernel modesetting enabled.
amdgpu: ATOM BIOS: SWBRT27511.001
drmn1: successfully loaded firmware image 'amdgpu/polaris12_mc.bin'
[drm] amdgpu: 2048M of VRAM memory ready
[drm] amdgpu: 3072M of GTT memory ready.
drmn1: successfully loaded firmware image 'amdgpu/polaris12_pfp_2.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_me_2.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_ce_2.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_rlc.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_mec_2.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_mec2_2.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_sdma.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_sdma1.bin'
amdgpu: hwmgr_sw_init smu backed is polaris10_smu
drmn1: successfully loaded firmware image 'amdgpu/polaris12_uvd.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_vce.bin'
drmn1: successfully loaded firmware image 'amdgpu/polaris12_smc.bin'
amdgpu: Voltage value looks like a Leakage ID but it's not patched
amdgpu: Voltage value looks like a Leakage ID but it's not patched
amdgpu: Voltage value looks like a Leakage ID but it's not patched
amdgpu: Voltage value looks like a Leakage ID but it's not patched
amdgpu: Voltage value looks like a Leakage ID but it's not patched
amdgpu: Voltage value looks like a Leakage ID but it's not patched
amdgpu: Voltage value looks like a Leakage ID but it's not patched
[drm] Initialized amdgpu 3.40.0 20150101 for drmn1 on minor 0

But the display stays in framebuffer (no display flicking on startup) mode as confirmed by running startx. How do I check if the /dev interface was set up properly, where is it located?
What I tried:
Loading the radeonkms module -> doesn't detect the GPU, dmesg.boot contains no messages from radeonkms
Setting hw.amdgpu.exp_hw_support=1 in /boot/loader.conf -> No effect
Creating xorg.conf that uses the driver amdgpu -> startx returns no screens found

 

[Cath O'Deray]

I might have an 850 G5 in a cupboard at work.

13.2

Which version, exactly?

A fresh installation, or have you run FreeBSD for a while?

Packages from quarterly, or latest?

freebsd-version -kru ; uname -aKU

pkg -vv | grep -e url -e enabled -e priority

How do I check if the /dev interface was set up properly, where is it located?

<https://man.freebsd.org/cgi/man.cgi?query=hier&sektion=7&manpath=freebsd-current> might be improved with an entry for:

/dev/drm/

261349 – Modernise hier(7)

bugs.freebsd.org

 

[ElectricJozin]

In the meantime I switched to 14.0-current to try if drm-515-kmod fixes the issue. It sadly exhibits the same behaviour.

freebsd-version -kru ; uname -aKU

FreeBSD hackermanHuge 14.0-RC3 FreeBSD 14.0-RC3 #0 releng/14.0-n265368-c6cfdc130554: Fri Oct 27 05:57:28 UTC 2023     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400097 1400097

pkg -vv | grep -e url -e enabled -e priority

    url             : "pkg+http://pkg.FreeBSD.org/FreeBSD:14:amd64/quarterly",
    enabled         : yes,
    priority        : 0,

I am gonna try to install the same kernel module on gentoo and see if the problem is there aswell.
But I have a couple questions:
1. If I enable hw.dri.debug should the info get printed to /var/log/messages?
2. Could this a issue be described as, the modsetting driver not switching from framebuffer mode to display mode?

I think this is gonna switch to a linux issue:
manjaro launches with a black screen with the "open source drivers" option and launches normally but then freezes (the mouse still moves) with "proprietary drivers"
arch linux crashes right after loading the driver

Ok I am going to move this upstream to linux and then try to push the changes to freebsd I guess

 

[ElectricJozin]

In the meantime I switched to 14.0-current to try if drm-515-kmod fixes the issue. It sadly exhibits the same behaviour.

FreeBSD hackermanHuge 14.0-RC3 FreeBSD 14.0-RC3 #0 releng/14.0-n265368-c6cfdc130554: Fri Oct 27 05:57:28 UTC 2023     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400097 1400097

    url             : "pkg+http://pkg.FreeBSD.org/FreeBSD:14:amd64/quarterly",
    enabled         : yes,
    priority        : 0,

I am gonna try to install the same kernel module on gentoo and see if the problem is there aswell.
But I have a couple questions:
1. If I enable hw.dri.debug should the info get printed to /var/log/messages?
2. Could this a issue be described as, the modsetting driver not switching from framebuffer mode to display mode?

I think this is gonna switch to a linux issue:
manjaro launches with a black screen with the "open source drivers" option and launches normally but then freezes (the mouse still moves) with "proprietary drivers"
arch linux crashes right after loading the driver

Ok I am going to move this upstream to linux and then try to push the changes to freebsd I guess

Blacklisting amdgpu on the arch live usb works, after install amdgpu loads fine but simpledrmfb is what fbset -i outputs.