Closed foxt closed 1 year ago
The DDC response packets that ddcutil reads are invalid. Sometimes the packets are entirely zero, sometimes they have a repeated byte in them. Typically this indicates a marginal DDC implementation in the monitor.
Things to try:
Option --sleep-multipler 4
Some monitors need extra time to prepare a response. This option increases the time ddcutil waits between sending a request to the monitor and trying to read a response. With a value or 4, a 200 ms wait mandated by the DDC/CI specification becomes 800 ms.
Option --maxtries "0,15,0"
I2C is an inherently unreliable protocol. This option increases the number of times ddcutil retries a write request/read response sequence, in this case from the default 10 to 15.
If neither of these solve the problem, execute the following command and send the output as an attachment:
$ ddcutil detect --verbose --stats --trace i2c --trace ddcio
I know these monitors are DDC compatible, as I have a script that works with these monitors connected to macOS.
I have two HP monitors, the 22xi and 22vx, both fail to control via ddcutil