The black console-style screen on a ZimaBoard 2 running ZimaOS is normal. ZimaOS is a home-server OS with a browser-based dashboard, not a local desktop environment. IceWhale confirmed this directly in the January 2026 thread.
Changing BIOS primary graphics settings will not turn the ZimaOS console into a desktop GUI. The miniDP output is mainly useful for boot status, IP information, BIOS access and terminal-style recovery.
What the External Monitor Is Supposed to Show
The user connected miniDP-to-HDMI plus USB touch input and saw only boot/status text. That was not a failed display driver—the expected ZimaOS interface is the Web UI opened from another device.
The current ZimaOS networking guide now explicitly says ZimaOS has no desktop environment and that the attached display shows version, model and IP information.
Touch Input Has Nothing to Control Without a Local Desktop
A USB touchscreen can present itself as an input device, but ZimaOS does not ship a graphical local session for that touch controller to interact with. The normal management surface remains a browser on another computer, tablet or phone.
If You Really Need a Local Kiosk, Build One Deliberately
One option is to run a separate graphical container or kiosk stack while leaving ZimaOS itself headless. The ZimaBoard 2 kiosk guide demonstrates that architecture.
This uses extra CPU/RAM and device access, so it is a customization rather than a built-in ZimaOS feature.
When Another OS Is the Better Choice
If the primary requirement is a normal local desktop with touch-first apps, window management and direct display use, a desktop Linux distribution or another OS designed for local GUI use may be a cleaner fit.
Bottom Line
The source thread has an official answer: ZimaOS has no desktop GUI. The miniDP output working as a console means the display path is functioning. Use the Web UI for normal administration, or add a dedicated kiosk/desktop layer only if local-screen interaction is a core requirement.
