Thanks for the information, here are my suggestions
Please follow the topology below to connect the monitor and RM1 (connect both the monitor and RM1 to the same splitter)
In this case, please avoid using the GLKVM app first, use browser local access instead
GL-RM1 (Comet) - GL.iNet KVM Docs
I have connected everything according to the diagram. Max res is still 2560 x 1440. Monitor is 3840 x 2160. Or 3840 x 1600. These are not available in windows settings or the Nvidia Control app when the monitor is connected with HDMI. My card is Nvidia gtx 750ti, and I verified the max resolution spec is more than enough to fit a 3840 x 1600 image.
Having said that, the remote system does appear. However I still can't see the bios screen. Once windows is running, the screen appears. I believe it will let me just tap f12 repeatedly when the video is disconnected during reboot.
Do you have any other monitors connected to your computer besides the splitter? Please keep it connected only with the splitter, which can eliminate some display priority issues.
In addition, as far as I know, Dell computers usually use F2 to enter BIOS, and the time is very fast, and you need to press it quickly within 1~2 seconds when the computer starts.
Using a splitter will automatically use the intersection of two displays, for example, one 4K and one 2K, the splitter will automatically adjust the 2K resolution output to support both displays at the same time.
I only have the one dell 3840 x 2160 monitor. It is still connected according to the diagram.
Yes, the amount of time to press f12 is relatively quick, but I am able to set a 10 delay to give more time to press the key after video is lost connection.
I am using:
Which says it supports 4k. I don't know where the bottleneck is unless the Rm1 itself is not capable of 4k. Using 8k hdmi cables and the factory one that came with the Rm1.
Side note: It does have 4 dip switches for EDID on it that I have not seen on any other design. It is also power.
I also have a splitter (mentioned above) that is dp in, dp and hdmi out. Using that splitter again for testing purposes. Hdmi is blurry compared to dp, so this splitter allows, as far as I can tell, the dp signal to pass through. The remaining problem is that there is no EDID in the app or web page that matches my monitor. The closest selection is the 3840 x 2160. While my monitor will go up to 2160, the default in windows is 3840 x 1600. The ill effect of this mismatch is that the mouse pointer tracks based on the larger horizontal setting. If I could get some help with creating a custom EDID for my monitor, I think that may resolve the issue.
The original issue remains however - no DOS screen during rebooting. Keyboard and mouse almost always work, and as mentioned earlier, can be used to blindly tap F12 for the boot menu (dell).
So that's where we are as I see it.
Well, I am about done trying to get this device to work.
Hdmi splitter = can't get to bios screen. Same with the DP to DP + HDMI. Tried resetting it a few times with some success, though short lived.
The only way I could get to the dell logo was to completely remove the device. Once I plugged in the DP to the video card DP, totally normal behavior. Cables are high quality and monitor has no problems connected directly.
I tried to locate the EDID hex code for my monitor, (dell u3818dw) but what I found, the resolution is not correct, should not be 3840 x 2160. The monitor should be 3840 x 1600. So, even when I had a remote connection within windows, the mouse would not track. This should be fixable.
Manually hitting f12 to get the boot menu, and leaving it there, I could not see it remotely. Video disconnected. Video starts to work once windows loads, but then the Comet serves no purpose. Can't see a blue screen to know what is needed to repair windows.
EDID database I have provided a resolution of 3840x1600 here
Using the 3840x1600 EDID, and entering that as a custom EDID, causes the remote session to come up looking like this:
Dell U3818DW supports hdmi 2.0 and I’m using HDMI certified v2.1, 8k cables. I have just recently been able to create a custom resolution in the Nvidia Control Panel, which is the only way I could get the monitor to display native. Right now, the signal is going through a splitter that has dip switches to select the display mode – 4k+2ch audio. It has a scaling dip switch as well which is set to 4k for both of its hdmi outs. The RM1 is supposed to receive the same 4k signal as the other port of the splitter. Without this particular splitter, the max monitor res is only 2560x1440. So this splitter seems like a good one.
Changing the pre-defined EDIDs doesn’t seem to affect the appearance of this screen.
I’m happy to get my monitor to display at native res. I feel like this remote video is so close to working properly, but I’m not sure what else to try.
UPDATE:
This awful looking screen changed after toggling windows display resolution from native to something lower, back to 3840-2160. Monitor native res is 3840x1600, but will display 3840x2160 oddly enough. Sooo, when I changed the resolution in windows this way, Comet would display (by default I guess) that higher resolution, filling out the whole screen and the remote mouse tracks with my local mouse. Since the native res is 1600, which is an option in Windows Display Settings, when I changed it to the native res, and that worked as well, I thought, yippee, I'll finally get native resolution when connected remotely. Instead what I got was a much wider screen, squeezed into the width of my laptop 1920x1080p screen. The ratio at 2160 seems ok to my eyes - I can't tell if there is any stretching or squishing going on. By the way I upgraded to 1.4 beta before doing this test. Keep in mind that based on my experiences to date, this success may not last, for reasons unknown to me.
The RM1 EDID setting as you can see in this second screenshot, is 2560x1440. I don't know what effect that might have if I change it, so I am leaving it alone for now. Note the screen res shown at the bottom of this window - it's 1920x1080 unless that's my laptop screen. You can see the Windows Display settings are still reading 3840x2160. All of my connections are with HDMI 2.1, 8K cables. I am still using the splitter recommended by GLKVM staff earlier, which has one HDMI in, and two out. The splitter has two customizable dip switches - one is for the desired output (4k) on one or both outs. The other dipswitch is for scaling on/off. I have it set to 4k, and scaling on for both outs (one goes to the RM1, the other to the monitor. These are the setting that work (for the time being). Your mileage may vary using different equipment and settings for a different size monitor. Mine is a Dell U3818DW, which is a 38" curved screen with native res of 3840x1600, but will as I mentioned, go up to 3840x2160 as shown in this new screenshot.
I hope this helps someone, and maybe gives Staff more feedback to iron out resolution details.
