This is a really dumb one - if you don’t run at around 60Hz (or 75Hz, more on that below), the display will complain that the video mode you’re trying to run at is “unsupported” even if you can clearly see a perfectly functioning image behind its overlayed nag message, and then 10 seconds later the monitor says “Powering down” and automatically enters power-saving mode (which is also what it does when to actually feed it a truly unsupported refresh rate, like 120Hz).
Thing is though, if you use non-standard CVT timings, you can display at least anywhere from 48Hz to 75Hz without issue.
The dumbest part is that, despite the stock EDID only listing 60Hz refresh rates, making a custom 75Hz resolution with bog-standard non-reduced CVT timings doesn’t show the nag message, even though anything between 61Hz and 74Hz does show the nag message - 75Hz clearly drives a panel harder than 72Hz, so why the heck does it think 75Hz is fine but 72Hz isn’t?
(for reference, 59Hz, 60Hz, 61Hz, and 75Hz are the only refresh rates I found that don’t require non-standard timings to avoid the monitor’s nag message)
Oh and, because 60Hz is the first (technically the only) refresh rate in the EDID, this also means that you get to “enjoy” the Linux xrandr scaling issue of being unable to use anything but 60Hz anytime you use xrandr --set "scaling mode"
since that only looks at your monitor’s physical EDID and nothing custom:
In case anybody is wondering, this monitor’s “secret super-power” is that it absolutely sips power - I’ve measured only 10-11 watts from the wall which makes it extremely useful in summer as just a “monitor” in the most literal sense so as to minimize heat output into the room, particularly when the PC it’s connected to is located in a different room or the like.