rockowitz

When you say "issue", what precisely is the behavior you observe?  What commands are you executing?  Can you send a log of the output.  Also, please run "ddcutil interrogate" and...

Currently fixed in branch 1.1.0-dev.

The Radeon 5xxx cards do seem to have a lot of I2C problems. It is interesting that you report the problem with Windows programs as well (which programs, what OS...

Normally, when **ddcutil** starts, it examines each /dev/i2c device to see if it is associated with a monitor that supports DDC. This is a slow process, but even so 4-5...

As I requested above, should you with to continue discussion of this issue, "please include the output of **sudo ddcutil environment --verbose** as an attachment.". Once you've used the ***--bus***...

You are running ddcutil 0.9.8, which is quite old. In particular, it does not have the cached capabilities feature which speeds up execution of **ddcutil capabilities**. You are using the...

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...

On 3/7/20 2:19 PM, JakubFojtik wrote: > > What arguments would cause the maximum execution speed of the |setvcp| > command run one after another? > > I am using...

First, thank you for the thorough bug report and comparison and analysis.  It gives me something to work with. Here's what I believe is going on.  The original I2C bus...

On 2/2/20 6:40 PM, InconsolableCellist wrote: > > I should note too that the same situation was occurring with that > third monitor, the DELL P2214H, which is an old...