rockowitz

As per the Guidelines for Issues (#241 ), please submit the output of **sudo ddcutil interrogate** as an attachment. I am not clairvoyant.

The **i2cdetect** output shows that I2C slave address X37 is unresponsive. DDC communication is not possible. And even though slave address x50 (EDID) is responisive, reading the EDID using slave...

As I said, utility program **i2cdetect**, which is not part of **ddcutil**, shows that DDC communication is not possible. Perhaps that can be fixed, but that is a video driver...

Interesting enhancement request. Unfortunately, it's non-trivial. The logging and tracing facilities have accreted over the years, (see the output of **ddcutil --hh | grep -E "log|trace"**). Passing a format string...

JSON output is on the [list of future enhancements](https://github.com/rockowitz/ddcutil/discussions/525). You may want to comment there. From my perspective many of the items on that list have higher priority. I would...

Normal and verbose output is intended for human consumption, so modifying it is not an issue. The burden is on script writers if the output changes. On the other hand,...

I can see the argument that ddcutil/libddcutil should not perform I2C operations if it detects that the system is in an idle state, but I find it hard to imagine...

Between this issue and #429, there are multiple descriptions of the problem: it affects nvidia as well as i915, it requires explicit invocation of command line ddcutil vs it happens...

I neglected to add that as an alternative you could set environment variable POWERDEVIL_NO_DDCUTIL to disable powerdevil's use of libddcutil. Let me know which of these alternatives, if any, resolves...

First off, let me say that your work is quite impressive. The code is cleanly structured and well documented, and you've clearly gone to considerable effort to understand a complex...