If a ZimaBlade suddenly loses Mini DisplayPort output, first determine whether the board is still booting and reachable over the network. A working network path with no picture points toward the display signal, adapter, BIOS, or hardware path rather than a completely dead board.
The source case remained unresolved even after multiple adapters, displays, a CMOS reset, and an external GPU. Because the original user later reported no solution, this guide should not pretend there is a single verified fix. The goal is to narrow the failure safely and know when to stop troubleshooting and contact hardware support.
Step 1: Check Whether ZimaBlade Is Actually Booting
ZimaBlade does not have a conventional power LED that proves the whole system has booted. Wait at least 30 seconds, then check your router's DHCP client list for the device or try its known IP address.
The current ZimaBlade hardware guide specifically recommends checking the router when the screen stays black.
Step 2: Use a Direct MiniDP Display Path
ZimaBlade's documented video output is Mini DisplayPort 1.2. USB-A video adapters and many USB-C display accessories depend on additional USB graphics or alternate-mode support and are not equivalent tests of the native MiniDP path.
Use a direct MiniDP-to-DisplayPort cable if possible. If the monitor only accepts HDMI, use a known-good MiniDP-to-HDMI adapter, but recognize that the adapter itself becomes another failure point.
Step 3: Test the Display Before ZimaOS Loads
Watch from power-on. If you never see firmware/BIOS output, the issue is unlikely to be only a ZimaOS desktop setting—ZimaOS does not provide a conventional local desktop anyway.
If firmware output appears but disappears during Linux boot, then collect kernel display messages such as:
dmesg | grep -i -E 'drm|i915|display|edid'Messages like “Cannot find any crtc or sizes” indicate that the graphics driver initialized but did not detect a usable display mode/path.
Step 4: Reset CMOS Only Once, Then Re-Test
A BIOS display setting can cause unusual output behavior, so resetting CMOS to defaults is a reasonable test. After doing it, boot with the minimum hardware configuration: RAM, network, and a direct display cable.
If there is still no firmware output, repeatedly clearing CMOS is unlikely to add useful evidence.
Step 5: Remove Add-In GPUs and Extra PCIe Hardware
An external GPU being visible in lspci does not mean the board firmware will initialize it as a primary display device. For troubleshooting, remove the eGPU and return to the native MiniDP path.
This also reduces power and PCIe variables.
How to Interpret a Corrupted DMI Table Warning
The source user saw a firmware warning about a corrupted DMI table. A DMI parsing warning can indicate unusual firmware data, but the forum did not prove it caused the missing video. Do not jump directly from that log line to reflashing firmware.
A BIOS reflash without reliable display or recovery access can make the system harder to recover. Escalate to IceWhale support before attempting firmware recovery procedures not documented for your exact board revision.
When the Board Is Reachable but Video Is Still Dead
If SSH or the web UI works, collect the board model, ZimaOS version, lspci -k, relevant dmesg output, and the exact cables/adapters tested. This is strong evidence that the compute and network paths are alive while the display path is not.
The ZimaOS boot troubleshooting guide provides a broader checklist.
When to Contact Support
If you have no firmware video with a direct known-good cable, multiple monitors fail, CMOS defaults do not help, and the system is either unreachable or still reports no display connector, stop swapping software. The source thread reached this boundary and support escalation was the responsible next step.
FAQ
Can ZimaOS run normally with no local video?
Yes. ZimaOS is primarily managed through its web interface. A server can be fully usable over the network even with no attached display.
Does a USB-C-to-HDMI adapter test the native ZimaBlade display output?
No. The documented native display port is Mini DisplayPort. Use the direct MiniDP path when isolating a hardware display problem.
Does an i915 “Cannot find any crtc or sizes” message prove the GPU is dead?
No. It means the driver did not find a usable display configuration. Cable, adapter, EDID, connector, firmware, or hardware faults are still possible.
Should I flash the BIOS if I see a DMI warning?
Not solely because of that warning. The source thread did not prove causation, and firmware recovery should follow exact vendor guidance.
