![]() (YPbPr being the color space used with analog component cables with older TVs from the 2000s and RGB being the digital standard we've been using with computers since forever). Unfortunately, I can't use the DisplayPort connection that is required by my Mac which is supplied by my work, because stupidly Apple forces HDMI outputs to use the inferior YPbPr color space, and only DisplayPort will correctly use an RGB color space. I suspect that is has something to do with the HDMI handshake. It just makes it more annoying to eventually get to a point where I can use the computer, because the damn thing has to cycle through all of the inputs before it even lets you interact with the input source menu again. Toggling this feature on or off has no effect. The monitor has an auto-source feature that will "hunt" for a signal from the 3 inputs, HDMI-1, HDMI-2, and DP-1. To make matters worse, it probably doesn't help that I have an Nvidia GPU, so I am using the proprietary driver. Because the issue persists across distros, display managers, and boot managers, my hunch is that it is something to do with the Linux kernel itself. I have gone through the installs of at least two different boot managers mostly GRUB through popular mainstream distros like Ubuntu and Fedora, and even an EFISTUB install with Arch. I have tried both GNOME and KDE (and their preferred display managers, GDM and SDDM). I cannot figure out what is causing this issue. I have not had the same success with Linux. This includes cold boots, or waking up from a suspend, or just wiggling the mouse when the screen is locked but the computer is still running. On Windows and macOS, this doesn't seem to be problem even if the monitor is in sleep mode, interacting with these devices will trigger the monitor to wake up, and everything will work normally. Once roughly 2 seconds have elapsed, it will display No signal received and go into sleep mode. ![]() This particular monitor has a flaw, in that it doesn't wait very long for a signal from an input device. Forgive the ignorance of the title, it was the best way I knew how to word it.
0 Comments
Leave a Reply. |