rockowitz

I'm afraid there's nothing more I can suggest.

As you've probably noticed, the Xiaomi Mi is, to say the least, a very problematic monitor from a DDC perspective. See issue #153. The failure of DDC communication when sending...

Nothing more to suggest, I'm afraid.

Please clarify what is meant by the display crashing and monitor reboot. What exactly is seen. Does rebooting entail turning the monitor off and back on? As a workaround, I...

Per the Monitor Control Command Set (MCCS) spec, value x05 is a write-only value documented as "Write only value to turn off display". Whether this actually completely turns off the...

Yes, release 2.1.5 is long overdue. (Also, given the extent of changes it will become 2.2.0). The problem is that watching for display connection/disconnection in libddcutil has been "almost" done...

This definitely is an issue for the Iamdgpu driver folks. It may be a driver issue, or it may be hardware. Running ddcutil may trigger the bug, but nothing ddcutil...

Observations: running as user soggy-pancake, not root - no dmesg output - DisplayLink checks produce garbage output (irrelevant to your issues) get-edid/parse-edid not installed, so those tests unavailable distribution: Arch...

I'm not sure what to make of your data. It certainly suggests there's a problem with dynamic sleep. The sleep time on the first example is approximately 5 times that...

The normal location for ddcutil config file is $HOME/.config/ddcutil/ddcutilrc. It's not so much that the checks themselves are seem unreliable with your monitor, its that they entail several DDC/CI operations,...