rockowitz

I've updated the proof of concept "--f1" code in branch 1.3.3-dev to something with a coherent user interface. The changes required were extensive. To recap, **ddcutil** has to navigate schylla...

Thank you for the quick testing. Modifying the i2c-dev driver to not set the bit would be a bit of work unless you regularly build the kernel. What would probably...

@menkaur Please run **ddcutil interrogate** and submit the output as an attachment. Thank you.

Next steps: 1) Ensure you have enabled the [Special Nvidia Driver Settings](https://www.ddcutil.com/nvidia/)/ 2) Execute this and the following commands, and again submit the output as attachment(s): **ddcutil getvcp 60 --bus...

I suspect this is the same problem as #278. What happens if you build **ddcutil** from branch 1.2.2-release?

MonitorControl certainly has a larger user and contributor base than ddcutil/ddcui, but I fail to see the synergy of merging them. The former is Mac specific, the latter Linux (and...

As reported by fhe output of **ddcutil vcpinfo**, the Monitor Control Command Set spec defines feature x12 as contrast. A given monitor may or may not implement this feature.

It has been some time since I looked at the Raspberry PI, but here's what i observe/suggest. You have a DDC data error. The video driver is reading all zeros...

You can download a package for **ddcutil** 1.3.0 from repo Raspian Testing, which avoids having to build it yourself. The key question is whether whether another monitor, known to work...

Your results so far suggest that the problem is the monitor. If you are able to test your monitor on a desktop system running **ddcutil** that would confirm it. For...