I have a NUC with an 11th generation Tiger Lake processor and it has been working fine with 13.1-BETA3 using graphics/drm-devel-kmod. The Iris-Xe GPU doesn't work with drm-kmod as of yet I believe. I just upgraded to 13.1-RC1 and it's as if it doesn't even try to display any graphics. It doesn't change to the high resolution/small text console mode and of course X fails to run. As an experiment I installed graphics/drm-kmod, which used to half work then give a blank screen, but it doesn't even try to do that, which is odd. One difference is that the Intel AX201 WiFi is auto-detected, whereas before it only worked when I loaded everything myself.
Created attachment 232869 [details] dmesg of RC1
Created attachment 232870 [details] dmesg of working beta3
I accidentally set the component as USB. There doesn't seem to be one for graphics, so hopefully misc will be OK.
Does recompiling the ports works ? I believe (but haven't investigated yet) that something in linuxkpi broke the abi.
It still fails after recompilation, using hte latest ports and src.
I don't see any lines corresponding to drm in your dmesg, can you share the lines when you kldload i915kms ? Thanks.
(In reply to Neal Nelson from comment #5) Are you using 5.4.144.g20220223 of drm-fbsd13-kmod ? It works with drm-fbsd13-kmod-5.4.144.g20220128 on 13.1-BETAs, but it dosen't work on 13.1-RC1.(In reply to Neal Nelson from comment #5)
Recompiling, reinstalling and reloading drm-kmod and dependencies in a 13.1-RC1/amd64 poudriere jail with a 2022Q2 ports tree worked for me, on 13.1-RC1/amd64 Apr 2 12:56:36 e17 pkg[54311]: drm-fbsd13-kmod-5.4.144.g20220128 deinstalled Apr 2 12:56:41 e17 pkg[54319]: drm-kmod-g20190710_1 deinstalled Apr 2 12:56:49 e17 pkg[54325]: gpu-firmware-kmod-g20210330 deinstalled Apr 2 12:57:46 e17 pkg[54340]: gpu-firmware-kmod-g20210330 installed Apr 2 12:57:46 e17 pkg[54340]: drm-fbsd13-kmod-5.4.144.g20220223 installed Apr 2 12:57:47 e17 pkg[54340]: drm-kmod-g20190710_1 installed So drm-fbsd13-kmod got upgraded from 5.4.144.g20220128 to 5.4.144g20220223
(In reply to Neal Nelson from comment #0) Note the change from drm-devel-kmod to drm-kmod on 13.1 both seems odd to me; does that mean drm was hand-built from ports as well? In which case this is not a KBI problem I presume. Can you show us the output of as well please? grep kld_list /etc/rc.conf
This might be our old friend "KBI not stable" between minor releases. Unlike in the 12.x time frame, though, we've made substantial efforts to keep it stable, but have not test suite that will confirm correctness. We should make sure that the same sources compiled against a 13.0 kernel FAIL when loaded on a 13.1 kernel and then bisect to find where that stopped working (after my direct commit to stable/13 0437d10e359ea1cbefff8d17cd18ca491dbbd5d7 to restore the 13.0 KBI). I am mostly AFK this weekend (spring is here!), so someone else needs to do the legwork. There's only 141 commits, so it should be only 9 bisection attempts to find the culprit.
oh, wait. 141 commits to linuxkpi, but 2735 to the branch. Still, only 11 or 12 steps to bisecting...
(In reply to Warner Losh from comment #11) Given people say it happened between BTEA3 and RC1 there are very few commits. I installed an RC1 and pkg installed drm-fbsd13-kmod and the module i915kms.ko loads. My current guess is that D33915 MFCed with the new struct field at the end ( https://cgit.freebsd.org/src/commit/?h=releng/13.1&id=c325d9edeff568d3d38891b2916bd5bd0e9bf8e3 ) is causing trouble and adjusting the check to be >= 0 for BUS_PROBE_DEFAULT will do the trick ... and it does seem to as now I get drmn0: fb0: i915drmfb frame buffer device ... I'll deal with this before RC2; the binary packages are still fine; the MFC rules and requested solution to the problem in D33915 are not. Let's take that there.
(In reply to Bjoern A. Zeeb from comment #12) For the clarity of everyone and for something to quote. The drm-fbd13-kmod binary modules should be fine (though I know little about them). A changed I merged to stable/13 and 13.1-RC1 prevents the modules from probing (loading). This will likely look like a silent error. The drm.ko and the driver module (e.g., i915kms.ko) will be loaded but "nothing happens". While the fix is not in the tree yet, this should be fixed before RC2. I'll get email updates or commit messages sent here.
https://reviews.freebsd.org/D34754 has what should be a fix.
Warner fixed it in stable/13: https://cgit.FreeBSD.org/src/commit/?id=86d5c66106610f083deda03ce0c661a51b2dd723 https://cgit.FreeBSD.org/src/commit/?id=aa61c28b4242ce3f86f1ae7807ae95887cbe9d11
Just installed 13.1-RC2 and everything seems to be working again. Thanks.
Thanks for testing and thanks to the people who fixed this.