Dennis HilkLinux Fix LabDE

Graphics, GPU & Display

Monitor modes disappear because EDID is invalid

Bad or missing monitor identification can remove expected modes; separate cable, dock and KVM effects from an incorrect display configuration.

Editorial source review: Start with the evidenceShare this guide
On this page
  1. Symptoms & scope
  2. Possible causes
  3. Diagnose safely
  4. Evidence-guided next steps
  5. References & review
  6. Related problems

Symptoms & scope

  • The expected resolution or refresh rate is absent.
  • Kernel messages report corrupt EDID, a checksum error or all-zero blocks.

Relevant environment

DRM/KMS display connectors; EDID comes from the monitor or an intermediary and may change when the connection path changes.

Recognizable messages (synthetic examples)
EDID block 0 (tag 0x00) checksum is invalid, remainder is 13

Compare the physical connection path and block contents; this is not proof of a damaged GPU.

EDID has corrupt header

Inspect monitor and intermediary data before forcing a resolution; a repaired-header message alone is intentionally excluded.

Possible causes

These are possible explanations, not a confirmed diagnosis. Several independent faults can coexist.

  • A cable, adapter, dock or KVM can interfere with reading monitor identification.
  • The monitor may advertise malformed data; an existing EDID override may also target the wrong connector or display.

Diagnose safely

Run one command at a time in the relevant session. Read the explanation first. Uppercase placeholders need your own values; tools and privileges vary by distribution. These commands are displayed here and never executed by the website.

Check 1

Read kernel EDID messages; administrator journal access may be necessary. Some additional details require a separately planned DRM debug boot.

journalctl -b -k --no-pager --grep='EDID|edid'

Interpret the result: A checksum or corrupt-header report indicates invalid identification. No message does not establish valid data, and not every extension error discards the base EDID.

Check 2

Replace card0-DP-1 with the affected connector from /sys/class/drm. edid-decode is a read-only utility that may need installation.

edid-decode /sys/class/drm/card0-DP-1/edid

Interpret the result: Check validation output and advertised modes. An empty file on a disconnected connector is expected; compare the direct monitor path with the intermediary path.

Evidence-guided next steps

Compare a direct monitor connection

If the issue appears through a dock or KVM, connect the same monitor directly with a known suitable cable and compare its EDID and offered modes. Change only one part of the path at a time.

Precautions: Save the display layout first and use the desktop’s automatic confirmation timeout. Never apply timings beyond the monitor’s stated capabilities.

Recovery / rollback: Reconnect the original path and restore the saved display layout if the comparison does not help.

Did this solution help you?

Share this solution#

Use a validated EDID override only when justified

If repeated direct reads establish defective EDID but a manufacturer-confirmed valid block exists, follow the kernel/distribution EDID firmware procedure for that connector. Validate the block and retain a boot entry without the override.

Precautions: Do not download an arbitrary EDID for a similarly named monitor. Early loading may require including the file in the correct initramfs.

Recovery / rollback: Remove the connector-specific override and regenerate the affected image if needed; boot the retained unmodified entry to recover display output.

Did this solution help you?

Share this solution#

References & review

This guide was prepared from primary project or distribution sources and reviewed on the date shown. This is an editorial source check, not evidence that a fix was reproduced on your hardware. Diagnostic log examples are synthetic fixtures. Version-dependent details must be checked against your installed release.