Project

General

Profile

Actions

Bug #670

open
JS

Lenovo M720q: Incorrect DDI B mapping in VBT prevents DisplayPort detection

Bug #670: Lenovo M720q: Incorrect DDI B mapping in VBT prevents DisplayPort detection

Added by Johannes Sjölund 26 days ago. Updated 24 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
board support
Target version:
Start date:
10/27/2026
Due date:
% Done:

0%

Estimated time:
Affected versions:
Needs backport to:
Affected hardware:
Affected OS:

Description

Hardware and software

  • System: Lenovo ThinkCentre M720q Tiny
  • CPU: Intel Core i5-8400T
  • GPU: Intel UHD Graphics 630 (8086:3e92)
  • Motherboard PCB identifier: IQ3X0IL
  • PCB revision: 1.0
  • Identification method: Physical inspection of the motherboard silkscreen
  • Physical display outputs tested: DisplayPort and HDMI
  • Coreboot: 26.09
  • Payload: MrChromebox EDK II
  • OS: Arch Linux, using the i915 DRM driver
  • VBT: src/mainboard/lenovo/m720q_m920q/data.vbt

The PCB identifier and revision were confirmed directly from the motherboard rather than SMBIOS, since the original DMI information is no longer available after replacing the Lenovo firmware with Coreboot.

Problem

The VBT included with the M720q/M920q mainboard describes EFP1 (device handle 0x0004) as a DVI/HDMI output on DDI B.

However, on my M720q, the physical DisplayPort connector is connected to DDI B.

This was confirmed by monitoring hotplug events in Linux:

  • Connecting/disconnecting the physical DisplayPort cable triggers HPD events on DDI B.
  • With the original VBT, i915 treats DDI B as HDMI, creates an HDMI connector, and attempts DDC/GMBUS communication.
  • The connected DisplayPort monitor is not detected correctly.

VBT correction

I modified the EFP1 child-device entry in BDB block 2 (General Definitions):

Field Original Modified
Device handle 0x0004 (EFP1) Unchanged
Device type 0x60d2 (DVI-D) 0x68c6 (DisplayPort)
DVO port 0x01 (HDMI-B) 0x07 (DP-B)
AUX channel 0x00 0x10 (AUX-B)

The VBT checksum was recalculated. The VBT size and all other child-device entries were preserved.

The resulting VBT was validated using intel_vbt_decode.

Verification

I first tested the modified VBT without reflashing Coreboot, using the Linux i915.vbt_firmware module parameter.

The modified VBT was loaded successfully and verified against the kernel's i915_vbt debugfs data.

With this change:

  • Linux creates DP-1 on DDI B.
  • AUX-B communication works and DPCD reads succeed.
  • DisplayPort link training succeeds.
  • The monitor is detected and can display an image.

I then included the modified data.vbt in Coreboot, rebuilt and flashed the BIOS region.

Results with libgfxinit and corrected VBT

  • EDK II over DisplayPort: Working.
  • EDK II over HDMI: Working.
  • Linux over HDMI: Working without intervention.
  • Linux over DisplayPort at 1280×720: Working without intervention.
  • Linux over DisplayPort at 3840×2160: The initial modeset can result in a black screen. A subsequent KMS modeset to 3840×2160 at 59.94 Hz restores the image.

Results with FSP GOP and corrected VBT

  • Linux detects both physical outputs correctly.
  • Both outputs can display an image after a hotplug event or an additional modeset.
  • No visible EDK II output was obtained.

Separate high-resolution modeset issue

On a Samsung Odyssey G95NC running in Picture-in-Picture mode, the initial Linux modeset at 3840×2160 may leave the DisplayPort output black.

The DRM logs show successful DisplayPort link training followed by a CPU pipe A FIFO underrun.

A manual modeset using:

modetest -M i915 -s 111:3840x2160-59.94

restores the image, while the 60 Hz mode tested did not.

The monitor advertises multiple 3840×2160 modes with different timing parameters. This may be a separate monitor/EDID/i915 compatibility issue and does not appear necessary to reproduce the VBT port-mapping problem.

Questions

  1. Is the supplied VBT expected to describe all M720q/M920q hardware variants?
  2. Could the existing EFP1 configuration be incorrect for the M720q's physical DisplayPort wiring?
  3. Would a corrected VBT, a board-specific override, or a documentation update be the preferred solution?

I can provide the original and modified VBT decode output, exact byte-level changes, Coreboot configuration, CBMEM logs and Linux DRM debug logs.

I have not verified this correction on other M720q/M920q hardware variants.


Files

M720q.jpg (707 KB) M720q.jpg Johannes Sjölund, 10/27/2026 07:01 AM
candidate_dp_b_hdmi_c_padded.vbt (4.5 KB) candidate_dp_b_hdmi_c_padded.vbt Matt DeVillier, 10/27/2026 10:26 PM
candidate_dp_b_hdmi_c_padded_228.vbt (4.5 KB) candidate_dp_b_hdmi_c_padded_228.vbt Matt DeVillier, 10/27/2026 10:26 PM
libgfxinit-228-connectors.txt (12.2 KB) libgfxinit-228-connectors.txt Johannes Sjölund, 10/29/2026 07:21 AM
libgfxinit-228-cbmem.log (101 KB) libgfxinit-228-cbmem.log Johannes Sjölund, 10/29/2026 07:21 AM

MD Updated by Matt DeVillier 26 days ago Actions #1

The FSP GOP not producing pre-OS output with the modified VBT tells me something is wrong there. Same behavior with the original one? What's the BDB version of the VBT?

JS Updated by Johannes Sjölund 26 days ago Actions #2

Thanks for taking a look!

Yes, I saw the same behavior with the original, unmodified VBT: FSP GOP did not produce any visible pre-OS output on either HDMI or DisplayPort.

Coreboot reported successful FSP-S initialization (status=0x00000000) and framebuffer information (1024x768 at 0xd0000000), but EDK II remained black.

The VBT has BDB version 212. The only changes were the EFP1 device type, DVO port and AUX channel, plus the recalculated checksum.

For comparison, switching to libgfxinit with the modified VBT produces working pre-OS output on both HDMI and DisplayPort. Linux also works on both outputs, although DisplayPort has a separate modesetting issue at 3840x2160 with my monitor.

So the lack of pre-OS output with FSP GOP was present before the VBT modification, and appears to be a separate issue.

I'm happy to provide logs or test additional configurations if that would help.

MD Updated by Matt DeVillier 26 days ago Actions #3

Thanks for the detailed report and for validating the EFP1 change.

VBT source

The in-tree data.vbt matches one of the 19 (!!) VBTs from Lenovo’s M1UKT79A image (m1ujy79usa.exe / imageM1U.ROM) byte-for-byte.

coreboot only includes one of them — EFP1 as DVI-D on HDMI-B with no AUX — which is the wrong one for your M720q. Another Lenovo SKU in the same image has EFP1 as DisplayPort/HDMI/DVI on DP-B + AUX-B and EFP2 as DVI-D on HDMI-C, which matches your HPD findings.

BDB vs CFL FSP

The Lenovo/in-tree VBTs are BDB 212. The Coffee Lake FSP sample VBT is BDB 228. That gap is not automatically fatal, but these tables are older than what the FSP package ships as a reference. They also keep fixed boot mode 1024x768 and a phantom LFP1 entry, which fits FSP GOP reporting a 1024x768 framebuffer while leaving both outputs black.

Path forward

I'm attaching 2 diff VBTs here:

  1. a DP-B + HDMI-C one extracted from the lenovo firmware, with LFP1 and the fixed boot mode removed
  2. same as the above, but migrated to the 228 BDB that the CFL FSP likely wants.

Please test both and LMK how they work for you with both Linux and FSP GOP on both outputs if possible

JS Updated by Johannes Sjölund 24 days ago Actions #4

Thanks for providing both candidate VBTs! I've now tested them on my M720q (IQ3X0IL rev 1.0), with some interesting results.

Candidate BDB 212

Tested with FSP GOP:

  • No visible pre-OS output on HDMI or DisplayPort.
  • The system did not appear to reach Linux (no SSH access).
  • I tested both an internal flash of the COREBOOT FMAP region and an external flash of the entire BIOS region using a Bus Pirate v3.b.
  • Both writes verified successfully. An external SPI readback also confirmed that the COREBOOT region matched the candidate ROM byte-for-byte.

I compared this build with my previously bootable FSP GOP build. All extracted CBFS components were identical except vbt.bin, including romstage, ramstage, FSP-M, FSP-S, bootblock and the EDK II payload. The complete ROM images differed only in the VBT's CBFS area.

Candidate BDB 228

With FSP GOP:

  • The system boots Linux successfully.
  • DisplayPort works in Linux.
  • HDMI works in Linux when connected to a separate 4K TV.
  • Neither HDMI nor DisplayPort produces visible pre-OS output in EDK II.
  • Coreboot reports successful FSP-S initialization and recognizes the VBT as valid.

With libgfxinit:

  • EDK II works over DisplayPort and HDMI.
  • Linux works over DisplayPort and HDMI.
  • S3 suspend/resume works, with both display outputs restored successfully.

This was tested with my Samsung Odyssey G95NC over DisplayPort (in PIP mode) and a separate 4K TV over HDMI.

I also confirmed that the ROM contains the exact candidate BDB 228 VBT. Linux uses the firmware-provided VBT (no external override), and the first 4517 bytes of i915_vbt match the candidate byte-for-byte.

The Samsung's HDMI input remains problematic in PIP mode, but I suspect this is a separate monitor compatibility issue. The same monitor also exhibits some unusual behavior with my NVIDIA RTX 4090.

Conclusion

Candidate BDB 228 with libgfxinit appears to work correctly on my M720q, including both physical display outputs and pre-OS graphics.

The lack of pre-OS output with FSP GOP appears to be a separate issue, since it also occurs with my earlier manually corrected VBT.

I've attached the CBMEM log and modetest connector information from the working libgfxinit + BDB 228 configuration.

I'm happy to perform additional tests if needed.

MD Updated by Matt DeVillier 24 days ago Actions #5

Johannes Sjölund wrote in #note-4:

Candidate BDB 228 with libgfxinit appears to work correctly on my M720q, including both physical display outputs and pre-OS graphics.

The lack of pre-OS output with FSP GOP appears to be a separate issue, since it also occurs with my earlier manually corrected VBT.

I've attached the CBMEM log and modetest connector information from the working libgfxinit + BDB 228 configuration.

I'm happy to perform additional tests if needed.

I'd say push a patch with this one then, and try to get a few others to test/validate it as well

Actions

Also available in: PDF Atom