rockowitz

Also, as a workaround, consider using option ***--skip-ddc-checks***, introduced in release 2.1.0. Testing DDC communication occurs in two parts. At the basic I2C layer, there's a simple check that I2C...

All of these errors reflect DDC communication failure. Please submit the output of **ddcutil detect --verbose --ddcdata**. This should show the bytes of the packets returned by the monitor.

Looking at the **interrogate** output, it looks like the monitor is returning bad data. Try executing command **ddcutil detect --verbose --ddcdata --stats** and submit the output. Also, does option ***--sleep-multiplier...

Confirmed bad data is coming from the monitor. Other than increasing sleep time and retrying requests, there's nothing more ddcutil can do. Some users have had success using a modified...

It is conceivable that **ddcutil** could be ported to run under WSL, but that would be a major project. The lower layers of **ddcutil** code responsible for I2C communication would...

As the problem arose with the update to Plasma 6.1, I suspect it has to do with changes to PowreDevil, which has had a lot of changes. See [PowerDevil in...

The i2detect output in the interrogate log shows that I2C slave address x50 (EDID) is responsive on /dev/i2c-2, but slave address x37 (DDC) is not. (In case you're unfamiliar with...

Please submit the output of **ddcutil interrogate** as an attachment.

When you say everything else fails, are you including **getvcp** etc? The **detect** command internally performs **getvcp** operations to test DDC communication and read the VCP version. The **interrogate** output...

I may have misinterpreted your cached sleep multiplier data. Try explicitly setting a high sleep multiplier using option ***sleep-multiplier 2.0***