rockowitz

Thanks for the report. I have hardened branch 2.1.5-dev to avoid the abort. However, there's a more fundamental problem. Release 2.x makes extensive use of /sys and drm in an...

Feature definition file are optional. The message you are seeing is informational. You are seeing it because ***--verbote*** output is requested. Similarly, "Feature x60 does not support verification is also...

Fascinating problem. I have no idea what's going on, but do have a few suggestions for next steps. A slightly modified version of your program runs with no problem on...

The **interrogate** output shows a number of issues: - The system journal is full of use-after-free errors in the the nvidia driver. so driver operations are suspect - You are...

For background, see [DDC Over DisplayPort](https://www.ddcutil.com/displayport/) and [USB-C DisplayPort Alt Mode](https://www.ddcutil.com/typec/). The USB-C to HDMI adapter is an active adapter. From the USB-C side, it's as if its communicating with...

When you connect your Asus monitor using the USB-C to HDMI adapter does it work? With the HP monitor, what is the output of: **ddcutil detect --ddcdata** **ddcutil detect --ddcdata...

There are impressively many things going on in your very thorough report. Let me make an initial cut at addressing them. First, to rule out ddcutil's involvement in the original...

Re the docking station, I was just pointing to that as another situation in which the monitor appears on multiple /dev/i2c devices. I have a hunch that, and it's only...

VCP feature codes are 1 byte values, from 0 to 255. The Monitor Control Command Set spec specifies a subset of these. For example feature x10 is brightness. No monitor...

Commonly, DDC communication failures entail data corruption, i.e. malformed packets. Such errors are sometimes correctable by increasing the time between packet writes and reads (i.e. with option ***--sleep-multiplier***). In this...