Hi,
I’m happy to share that I’ve recently unboxed, plugged in & used a new COMET PRO GL-RM10 KVM. So far everything has worked! I need to try tailscale away from here to test true remote access, but that is a next step.
One issue I’ve had is related to HDMI pass-through & brightness.
Before the COMET device, when the display is directly connected to the “controllee”(controlled) server, I’m satisfied with the brightness of the display.
When I use the display via pass-through however, though the display works (and sound too) the brightness of the display (after pass-through) is somehow diminished. It’s seems as if the brightness has been capped with a ceiling or something or during passthrough, the brightness is reduced. The display is certainly bright enough to use, read text, see video, etc. (as I’m using the pass-through display now to type this message). It’s not quite bright enough to be as it was before the KVM was inserted as an HDMI pass-through device, which is what I would really like. To the extent that the display changes, it's not actually "pass-through".
I wonder if anyone else has seen an issue like this? or offer any advice, suggestion, help, or insight? or if any GL.iNET personnel might offer any thought or comment which might explain this? or help to be able to restore brightness or allow brightness to return?
Right now, the COMET device is plugged in on its first boot-up. After a bit more testing, I plan to reboot at least the server (and of course the in-use GPU) and see if that restores brightness or allows it to be uncapped. Re-booting the COMET itself seems an additional thing to try to see if it helps. I'll report back on this thread soon to see an any observation/experience.
thanks,
-eddie
Thank you @minmie for this PSA/link.
I forgot to mention that yes, I'm on an NVIDIA GPU...
Given the link I was somewhat saddened/frustrated to see they mention taking an action with the NVIDIA Contral Panel in Windows. I'm actually running Linux/Ubuntu 2404 with wayland/mutter in my case, so I couldn't immediately try the suggestion. I dual-booted to "Windows side" (windows 11) and nevertheless made the change there.
Though, I've since completely powered down and then booted back to "Linux side" (ubuntu 2404 w/Wayland) it seems to be better (either that or my eyes have adjusted slightly...) but it's hard to tell for sure without an objective quantitative measurement...
By the way, I've since created a tailscale account and have connected a few devices to it including my new COMET, and have also been able to use the GL.iNet COMET Pro (GL-RM10) device as a tailscale "exit node" and it worked as I was able to connect to devices not on the tailnet using it as an exit node.
thanks!
-eddie
hi @minmie I wanted to offer a follow-up note.
Even after following your advice, even if it may have helped, it did not help enough.
I remembered that I had an unused HDMI splitter lying around, and I thought to incorporate it into my HDMI setup. So now, the HDMI input from the server goes into the splitter input. One of the splitter’s outputs goes to the COMET and the other output goes to my display. And this setup gives me back the brightness I was looking for.
BTW, this is the splitter I used Amazon.com: OREI HDMI Splitter 1 in 2 Out - For TV Mirror Only - Not for Multi Monitors, No HDCP bypass, USB Powered, No Adapter Included,1080P@60Hz & 4K@30Hz Resolutions – HDMI Splitter (HD-102) : Electronics . Though it doesn’t have an “auto downscale” feature, I imagine having that feature could be helpful. Also, if anybody else does such a thing they should consider testing the copy/auto EDID switch to see how it works for them! According to the splitter manual the “copy” setting means that the “HDMI output 2” overrides “HDMI output 1” and I have my main display set as “HDMI output 2”.
Other than this HDMI issue, the COMET KVM functionality has worked quite well during testing!
thanks,
-eddie
1 Like