Comet POE: blank/black screen

hey all,

this is another black screen experience - after getting my comet poe today and connecting all cables as described in the instructions I just see a block screen.

I am using the kvm just in my lokal network - therefor I just use the browser. No account, no Cloud Services.

the “server” I want to use the kvm for is a beelink s12 pro which has two hdmi ports (both out) with 4k and 60Hz.

From my opinion all settings are accordingly - no webrtc blocker or whatever installed in my browser (at least I do not know :slight_smile: of any)

I tried all things mentions in the faq: Blank screen displayed when using GLKVM - GL.iNet KVM Docs with no changes - still black screen

I searched in the forums - tried everything I found … still black screen.

I’ll try to attach the log export here in hope anyone can help me.

Thanks for your help,
m.

system_logs_20251007_210442.zip (38.0 KB)

after rebooting the device I see the login screen which brings me to the next issue… :see_no_evil_monkey:

my password contains an ampersat/at sign which seems not to be processed correct. tried my keyboard (german layout and just in case us layout = shift + 2) and also the virtual keyboard with no success.

I logged in using ssh on the machine and changed temporarily my password which gave me a successful login through the kvm

looks like a bug to me :slight_smile:

Have you tried with the short cut function in Toolbox.
We are currently try to improve the keyboard function since there are multiple kinds of keyboard version have different layout. Sorry for the inconvenience caused anyway.


In command line interface, sometime you need to reboot the controlled device to make the display normal.

@Kyrie thanks for the answer and the suggestion. tried the shortcut also with no luck. makes it currently unusable for me. :smirking_face:

Does the "@" can be normally typed out both in local device and remote device by "shift + 2" ?

@Kyrie I am on german keyboard layout where the @ is option+L (on osx) - but yes when I remote login into the device with ssh it can be and is treated correctly. I do not have any keyboard connected to the device but when I setup the machine it was and was treated correctly.