rockowitz

It looks like a bit of debug output is turned on. Locating exactly where will likely be a pain to diagnose remotely. As a first step, please execute **ddcutil detect...

The output of the trace log does not appear to be from the same physical configuration as your original report. The detect command has no output for the LG 5K...

The output isn't happening within a low level I2C function. Let;s try **ddcutil detect --trace ddc --trace ddcio**.

I believe I've found the locus of the errant hex dump. The bug is in the infrequently executed code that checks for phantom displays. That code was apparently triggered because...

I have cleaned up the drm.h includes in branch 2.1.5-dev. Let me know if it builds properly and the problem is solved. Thanks so much for your help.

The "Failure retrieving DRM resources" message reports an unexpected error in new code under development, intended to improve performance. You can ignore it. The text in parentheses after "DDC communication...

The detail on **detect** as to why DDC communication failed has turned out to be as much a source of confusion as an explanation. With the latest update to 2.1.5-dev,...

I think that ddcutil-service will eventually become the way that most applications, or at least simple applications that now rely on screen-scraping, use ddcutil. Having a second real application, after...

The file name is quite precisely defined. The mfg-id portion of the file name is exactly the 3 character manufacturer code as specified in the EDID. The product-code is an...

Re the meaningful value in the SH byte in what otherwise is a SNC feature, the simplest extension would be to allow SNC and CNC as valid attributes, with SNC...