rockowitz

Your results are consistent with the fact that the single byte read change was made only to the EDID reading on the I2C bus, not to DDC communication. So the...

I've added code to further parameterize how I2C writes and reads are performed. The latest version of ddcutil on github contains some special code that exercises these variations (16 permutations)...

Thanks for running the tests. Here are my takeaways. Everything works with the special Nvidia driver settings, and always works with the Samsung U238E590, so the question is whether ddcutil's...

The document source is maintained offline, and the generated html pages are uploaded.  Please send the changes you would like to see.  I will review and incorporate them as appropriate. ...

Thank you for pointing out the discrepancy between the documentation for command **detect** and its current behaviour. The current development branch, 1.2.0- dev, has been modified to be consistent with...

My best hunch, and it's just that, is that there's a problem in the monitor's DDC implementation.  More specifically, it may be that the DDC input is not always being...

Please send the output of "sudo ddcutil environment --verbose" for the alternate configuration. Sanford On 5/9/19 8:00 AM, k-kolev wrote: > > Today I tested with different monitor - Fujitsu...

Please ignore the previous message.  I just saw the interrogate output that was attached to the email that went directly to me. Sanford On 5/9/19 8:00 AM, k-kolev wrote: >...

The output of the interrogate command is baffling.  At lines 348/351, in the environment portion of interrogate, there's a simple test of reading feature x10 that succeeds.  But later communication...

Bottom line, i2cdetect shows slave address x37 (DDC) is responsive in both cases.  I'm out of ideas. That the problem happens with 2 different monitors suggest it's not the monitor's...