[Bug 297014] HDMI does not expose 120/144 Hz modes and rejects manual modes (Intel, Meteor Lake)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D297014

--- Comment #2 from Oliver <[email protected]> ---
(In reply to Oleksandr Kryvulia from comment #1)

**MORE AI WRITING BECAUSE IM A NOOB, SORRY ABOUT THAT**



I did some more testing.

Following the suggestion above, I tested both `drm-latest-kmod` and
`drm-612-kmod` on 16.0-CURRENT. Both behave identically, so this doesn't ap=
pear
to be specific to the latest DRM branch.

The original HDMI issue is unchanged. The monitor's EDID is read correctly =
and
advertises 120 Hz and 144 Hz, but the DRM connector only exposes 60 Hz mode=
s.
If I manually add the EDID's 120 Hz or 144 Hz timings with `xrandr`, switch=
ing
to them still fails with:

```text id=3D"wygzrm"
xrandr: Configure crtc failed
```

While testing, I also noticed another issue that may or may not be related.=
 The
driver loads the DMC firmware successfully, but then fails to initialize the
GPU microcontroller:

```text id=3D"itvfmw"
drmn0: successfully loaded firmware image 'i915/mtl_dmc.bin'
drmn0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.23)
drmn0: [drm] *ERROR* GT0: Enabling uc failed (-5)
drmn0: [drm] *ERROR* GT0: Failed to initialize GPU, declaring it wedged!
```

On the previous branch I've used, similar initialization errors disappeared
after installing `gpu-firmware-kmod`. In this case, `gpu-firmware-kmod` is
installed, but the errors remain, so I'm not sure whether that's expected on
Meteor Lake or indicates a separate problem.

If it's useful, I'm happy to test patches or provide any additional logs.

--=20
You are receiving this mail because:
You are the assignee for the bug.=