Just purchased my first Comet. Plugged it in according to instructions. Went to other computer on the same network–no detection. Tried a different machine on the same network–no detection. Manually added the machine using the serial–success!
Met with the dreaded white screen. Did some googling and found the issues on the forum. Did a manual update a few times to get the firmware current, and BAM–No HDMI Signal Detected. Dug a little deeper into the forums and found some suggestions, such as rebooting, changing cords, dual reboot. Nothing worked. The machine will display on other monitors with the original cord and the cord that came with the Comet, so I don’t think it’s the cord or the server.
The log has some weird messages about impossible resolutions and refresh rates. I’m open to any suggestions at this point.
Currently, I’m using all accessories that were included in the box–Comet with included charger, HDMI, and USB-C. Machine is a NASKiller with and ASRock motherboard, Intel z790 platform using onboard video. Log snippet follows:
[ 18.150109] dwc3 ffd00000.dwc3: device reset
[ 18.266750] dwc3 ffd00000.dwc3: device reset
[ 18.266872] android_work: did not send uevent (0 0 (null))
[ 18.387384] android_work: sent uevent USB_STATE=CONNECTED
[ 18.392261] configfs-gadget gadget: high-speed config #1: b
[ 18.392549] android_work: sent uevent USB_STATE=CONFIGURED
[ 22.000663] lt6911c 1-002b: Resolution: 24x0@1021 fps (htotal=1168, vtotal=1) audio: 0 realaudio: 0
[ 22.000717] lt6911c 1-002b: lt6911c_rcv_supported_res: unsupported resolution 24x0@1021
[ 22.000730] m00_f_lt6911c 1-002b: lt6911c_get_timing: rcv err res, return no signal!
[ 22.212062] lt6911c 1-002b: 0xD211 is ff
[ 29.895357] lt6911c 1-002b: Resolution: 22x0@68 fps (htotal=1018, vtotal=0) audio: 0 realaudio: 0
[ 29.895422] lt6911c 1-002b: lt6911c_rcv_supported_res: width and height must be divisible by 4
[ 29.895442] m00_f_lt6911c 1-002b: lt6911c_get_timing: rcv err res, return no signal!
[ 30.109563] lt6911c 1-002b: 0xD211 is ff
[ 39.506778] lt6911c 1-002b: Resolution: 2x0@73512 fps (htotal=1966, vtotal=1) audio: 0 realaudio: 0
[ 39.506848] lt6911c 1-002b: lt6911c_rcv_supported_res: width and height must be divisible by 4
[ 39.506868] m00_f_lt6911c 1-002b: lt6911c_get_timing: rcv err res, return no signal!
[ 39.719229] lt6911c 1-002b: 0xD211 is ff
I did. I used the help guide to pick a 1024x768 and a 1920x1080 from the GitHub list (although the 1024x768 decode showed up as a 1080p one in the drop down). I also tried the defaults in the dropdown to be thorough.
Unraid documentation says it defaults to 1024x768/60. The two monitors tested are 1080p and 2160p respectively, and they both display the server gui.
Thanks! Email sent. I’ve tried some other Custom EDIDs from the link in the meantime. The logs show similar abnormal resolutions/framerates resulting in no HDMI signal. No video yet.
Been combing logs here and on the machine off and on today. Still no luck. I’m not sure what to do at this point. Tried more custom EDIDs. Both web and app fail to render. The logs all look the same now.
I can try that when I get home from work today. I have a windows machine online that already has an IPKVM solution in place, so I can swap it with this one to troubleshoot. I did notice while testing this machine I’m getting a consistent error in the linux logs when first connecting the Comet:
I spent quite a bit of time yesterday and this morning working on this again. It does work on two other windows machines–a GDP Pocket3, and an older custom-built gaming computer running Windows 10 with an MSI Gaming 7 motherboard.
After checking with the Unraid community on a couple of different forums, it doesn’t seem to be related to the operating system as several users with the same processor and OS are running it.
I believe this points to an incompatibility with the ASRock motherboard, the z790 chipset, or a combination of the two. The only consistent path I could follow was, regardless of any setting change, the system log would detect the KVM then throw
Thanks for your update.
I noticed that you have another IPKVM. I wonder if this one can work in your NASkiller?
In addition, can you export the complete log to me again before the Comet reboot.
I can do that. The windows server with the other kvm is running parity, so I need to keep that in place until it completes tomorrow. I can get the logs from the NASKiller build this afternoon and send them to you. I’m also going to try putting an HDMI splitter with passthrough in line to see if that will work.
Thank you. Please note that when you use a HDMI splitter, you need to configure the EDID of the Comet to match the resolution of your local monitor before connecting. Otherwise, issues may occur.
