Bottom Line: A Red LED Only Proves Some Power Is Present—it Does Not Prove ZimaBlade Booted Correctly
The original board showed a red light but had no video and no network. One case ultimately received a replacement. Another similar case later traced the problem to the onboard network port. So treat the LED as the start of diagnosis, not a “board is healthy” signal.
Verify the Power Supply Can Actually Negotiate 12V / 3A
The official ZimaBlade power requirements specifies a Type-C 12V/3A power adapter. An older ZimaBlade troubleshooting guide also explains that a red board LED can appear even when USB-C PD negotiation has fallen back and the board is not receiving the required operating power.
USB-IF's USB Power Delivery provides the underlying standard context.
Reseat the DDR3L RAM Before Chasing Software
ZimaBlade has no onboard RAM. Remove power, reseat the SO-DIMM, and confirm it is DDR3L/1.35V-compatible. A partially seated module can produce exactly the “lights but no usable boot” experience.
The ZimaBlade hardware specs provides the current hardware reference.
For the network-side check, DHCP is the normal way a new device obtains an address on a home LAN. RFC 2131 is the protocol reference behind the router client list.
Use a Direct MiniDP-to-DP Cable and Check the Router DHCP List
Current ZimaBlade docs warn that display adapters can be fussy. A direct Mini DisplayPort-to-DisplayPort path is a better test than stacking HDMI adapters. At the same time, check the router's DHCP list—no display does not necessarily mean no boot.
If There Is Still No Video and No Network, Reset RTC Once
The original IceWhale response recommended resetting the RTC battery. That is a reasonable hardware recovery step after power/RAM/cable checks. Do it once, then retest from a known-good power supply and Ethernet port.
When to Stop Troubleshooting
If correct power, known-good DDR3L, direct display, RTC reset and Ethernet still produce no network activity or video, collect the serial/model information and contact support. The original case eventually required replacement hardware, so endless OS reinstalls would not have helped.
The Zima device discovery applies only once the board actually reaches the network.
