Intel meteor lake

[monocat]

I'm on an ASUS Zenbook 14 OLED UX3405MA, Core Ultra 7 155H, Meteor Lake-H with the Arc iGPU. I sent the project two full hardware probes already, back in August and December 2025 — dmesg, kldload logs, the panic traces, all of it. Not attaching them again, they should be in the archive under my earlier posts if anyone wants to check.

What I actually do on this machine is photo editing — GIMP, darktable, RawTherapee. No video encode, no OpenCL. So all I need is i915kms loading stable and Mesa/iris doing its job for the desktop, that's it.

I saw drm-kmod 6.12.85_2 back in June claims a Meteor Lake fix (#418), but people posting after that release are still hitting black screens and force-probe panics on this exact chipset. So where does that actually leave things right now — is it holding stable for anyone on Meteor Lake with 6.12.85_2 on 15.1 or 16-CURRENT, or is it still a coin flip?

And is there an actual version being aimed at for this — 6.13, 6.14, whatever — that I could watch on GitHub, or is it just "whenever it happens"? I'm not asking for a date, just something concrete to follow instead of guessing.

Last thing — for someone who never touches VA-API or OpenCL, is there anything else still broken on Meteor Lake beyond the display driver itself?

I'd genuinely rather hear "nobody knows yet" than get pointed at another thread that doesn't answer this. Already been down that road a few times.

 

[siladi]

Cool. First post coming through good and strong... Note to self, I really need to learn how to type that character, cannot find it anywhere on my keyboard ...

Anyways, more to the point the place you want is this https://github.com/freebsd/drm-kmod

More specifically to meteorlake , to be read in it's entirety: https://github.com/freebsd/drm-kmod/issues/485

You can also join in the excitment and hop on https://github.com/freebsd/drm-kmod/pull/469 to test things and report back your findings.

 

[T-Daemon]

I saw drm-kmod 6.12.85_2 back in June claims a Meteor Lake fix (#418), but people posting after that release are still hitting black screens and force-probe panics on this exact chipset.

The issue seems to be fixed on 16.0-CURRENT, with commit "linuxkpi: Fix cancel_delayed_work_sync() return value":

drm-612-kmod on 16-current blank screen - Meteor Lake (0x7d55) · Issue #485 · freebsd/drm-kmod

Describe the bug After loading i915kms from console screen becomes blank. The only way to recover is to reboot. No errors reported in dmesg or messages. hw.i915kms.enable_guc=3 in /boot/loader.conf...

github.com

linuxkpi: Fix cancel_delayed_work_sync() return value by ryanfahy314 · Pull Request #2268 · freebsd/freebsd-src

Summary This PR fixes the LinuxKPI workqueue delayed work sync behavior to better match the Linux workqueue API contract. I found this while debugging Intel Arc A770/DG2 support on 15.1-STABLE whic...

github.com

And is there an actual version being aimed at for this — 6.13, 6.14, whatever — that I could watch on GitHub,

Check from time to time on https://github.com/freebsd/drm-kmod pull requests (open and closed) from "dumbbell", e.g.: Update to Linux 6.13 , ready to test on 16.0-CURRENT. Testing instructions can be found in the linked pull request.

If you have a Github account, one can enable "Notifications", but I'm not sure what exactly this includes .

I'd genuinely rather hear "nobody knows yet" than get pointed at another thread that doesn't answer this. Already been down that road a few times.

You can only be sure if try it yourself on your specific machine. To make the testing easier, if your file system is ZFS, create a (disposable) boot environment. If it's not, consider your next fresh install to be Root-on-ZFS.