New Comet hooked up to HDMI on an Asrock H670M-ITX/ax motherboard. Host OS is ESXi 8.0.
Just unhooked a Lantronix Spider to install this guy. I am getting No HDMI Signal Detected.
Hi,
Could you please export the log to us for analysis.
You can PM me or send me via email (haoyu.zheng@gl-inet.com).
I have new account so I cannot embedd more than 1 media and 1 link. Here is screenshot with working ESXi:
and I am also enclosing logs:
system_logs_20260114_142243.zip (65.0 KB)
Hi,
Hope you are doing well!
I’ve the same problem - “No HDMI signal” when using ESXi. But in fact Comet works.
What’s the workaround? First of all - log in to Comet via web. Then reboot your ESXi host, don’t close Comet web gui. ESXi will reboot, you will see BIOS messages and after that - ESXi login screen.
system_logs_20260114_141927.zip (56.6 KB
It is not working while you are not connected to Comet web ui during restart.
@Kyrie, could you please look into it?
Based on logs, The lt6911c HDMI receiver chip detects no signal.
ESXi (VMware's hypervisor) has a fundamental limitation which has No Native HDMI Passthrough and Display Abstraction
This is a hardware/virtualization limitation, not a bug. To use the Comet KVM device, you need an actual HDMI output
But after reboot it works. Please refer to No HDMI Signal detected - ESXi - #4 by darnokb
HDMI output is not present when ESXi starts when I do not open Comet web ui.
When I reboot it with open web ui it works like a charm - it loads bios, ESXi bootloader and ESXi console.
1 Like
@fisk_kvm , here is video:
1 Like
@darnokb Thank you for recording the video, I misunderstand between the ESXI virtual meachine and host of your devices.
Based on video and what you have described, I get my mind that maybe Comet KVM HDMI detection mechanism issue.
I recorded logs whether webui has been opened.
Whether or not the web UI is open depends on the "ustreamer" process.
The video stream is started on demand.
I think this command "/usr/bin/ustreamer --device=/dev/video0 -r 1920x1080 --unix=/run/kvmd/ustreamer.sock &" which start ustreamer process manully could solve your problem that keeps hdmi signal.
Because the HDMI output timings during ESXi reboot and Comet's on-demand mechanism makes this bug strange depends on opening the web-ui.
A plausible explanation is that EXSI doesn't generate pre-created video nodes for HDMI devices when they're not being inserted during startup. This is why you see the screen after rebooting—When you restart EXSI with GLVM plugged, it creates a video node for this HDMI device during initialization.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.