Open benjamb opened 4 months ago
A display can be marked "Invalid" for any number of reasons. It may not support DDC/CI, but except for laptop displays this is quite rare. Some monitors allow for disabling DDC/CI in the OSD. The Nvidia proprietary driver can require some special settings. Most commonly, the received DDC data packets are not as expected. This is what status DCRC_DDC_DATA indicates. For more detail, option --ddcdata (previously --ddc) reports the invalid data instances and option --stats errors reports data error counts.
Sometimes data errors can be resolved by increasing the wait time (aka sleep time) between writing a request packet to the monitor and attempting to read the reply packet. Disable dynamic sleep adjustment (--disable-dynamic-sleep) and try setting an explicit sleep multiplier, e.g. --sleep-multiplier 2.0 which doubles the time ddcutil waits between writing a request packet and reading the reply. Generally speaking, if a sleep-multiplier value of 2.0 does not resolve the problem, a greater value will not work either.
Looking at your interrogate output, it appears that is not the case that the reply packet contains invalid data, but that there's no returned data at all. I'm not sure that to make of this, but I would try explicitly setting a high sleep multiplier.
You can ignore that last paragraph about it appearing that no reply packet data was returned. That was due to a bug in interrogate.
From a glance at documentation for the monitor and browsing through the menu, it claims to support DDC/CI, yet it is detected as an invalid display.
Output of
sudo ddcutil detect -v
:I've attached the output of
sudo ddcutil interrogate --verbose
.ddc.txt