For ZimaBlade expansion, rely on the interfaces ZimaSpace currently documents—DDR3L SO-DIMM, two SATA ports, USB-C/USB, Gigabit Ethernet, MiniDP, and PCIe 2.0 x4—and treat unlabeled headers or alternate power feeds as undocumented until IceWhale publishes pin-level specifications.
The source thread asked for a complete board diagram, fan-header pinout, sensor headers, HD-audio details, and PCIe option-ROM behavior. IceWhale confirmed fan connectors exist on the back and said connector documentation was being built, but the current public ZimaBlade overview still does not provide a full electrical schematic or pinout for every unpopulated header.
What Is Officially Documented Today
The current ZimaBlade hardware overview documents:
- one DDR3L SO-DIMM slot up to 16GB;
- two SATA 3.0 ports;
- one PCIe 2.0 x4 slot;
- Gigabit Ethernet;
- USB-C, USB 3.0, and USB 2.0;
- Mini DisplayPort 1.2.
Do Not Use Unlabeled Headers as Power Inputs
An unlabeled board connector may carry fan, debug, sensor, or manufacturing signals. Without a verified voltage and pinout, probing it as an alternate power feed can damage the board.
Use the documented 12V USB-C power path for normal operation.
Fan Headers Exist, but Verify Electrical Details
An IceWhale representative in the source thread confirmed fan connectors on the back of the motherboard. That does not automatically define voltage, pin order, PWM behavior, or maximum current.
Before connecting a third-party fan, obtain current model-specific documentation or support confirmation.
Why BIOS Shows Options for Hardware You Cannot See
Generic firmware builds can expose CPU/chipset capabilities such as HD Audio, fan controls, legacy PCIe boot, or devices not physically populated on every board.
Seeing a menu item is not proof that a corresponding connector exists or is wired for end users.
PCIe Option ROM and Legacy Boot
The original user eventually found their RAID/HBA option-ROM behavior under a legacy PCIe boot setting in BIOS. That is a useful clue for older HBAs whose configuration ROM expects legacy/CSM initialization.
However, changing UEFI/Legacy settings can also affect the OS boot path. Record current settings before experimenting.
How to Inspect an HBA Without Relying on Its Option-ROM Screen
Once Linux boots, use:
lspci -nn
lspci -k
dmesg | grep -i -E 'sas|sata|scsi|ahci'If the controller and disks are visible to Linux, a missing pre-boot configuration screen may not prevent normal storage use.
Use a Risk Ladder for Undocumented Hardware
- Low risk: inspect BIOS and Linux device enumeration;
- Medium risk: attach documented PCIe/SATA/USB devices;
- High risk: connect fans to unverified headers;
- Very high risk: inject alternate power into undocumented connectors.
The hardware troubleshooting guide is a safer starting point when an expansion card does not initialize.
Document the Board Before You Modify It
Take clear photos of both sides of the board, note the hardware revision, and label the connector you are investigating. If you contact support, include those photos rather than describing “the small white header next to PCIe.”
That makes it much easier to distinguish a fan connector from a debug, sensor, or factory-programming header.
Check PCIe Power and Compatibility Separately
The PCIe 2.0 x4 slot provides the normal PCIe interface, but add-in cards can have very different power and firmware expectations. Storage HBAs, GPUs, and multi-NIC cards should be tested with the board's total power budget in mind.
If a card is visible with lspci but its own option-ROM screen never appears, the operating system may still be able to use it. If the card is absent from lspci, investigate seating, power, lane compatibility, and firmware settings first.
Save BIOS Settings Before Changing Legacy Options
Photograph the current boot and PCIe pages before enabling CSM/Legacy behavior. If the system stops booting afterward, you will have a known baseline to restore instead of guessing which setting changed.
FAQ
Is there a full public ZimaBlade schematic?
The current public hardware overview documents major interfaces but does not expose a complete electrical schematic for every board header.
Can I power ZimaBlade through an unlabeled header?
Do not do so without an official pinout and electrical rating.
Why does BIOS show HD Audio if I cannot find an audio header?
Firmware can expose chipset features that are not physically populated or intended for use on a specific board.
How do I configure an older RAID/HBA option ROM?
The source user found legacy PCIe boot settings relevant. Change firmware mode cautiously and verify the OS still boots afterward.
