rockowitz

There have recently been 2 reports (by @slavov-viii on issue #125 and @kowalc0 on issue #67) that setting brightness (feature x10) fails on Benq and Lenovo monitors when Dynamic Contrast...

@daher13 **This is a significant change to my prior response***. The message you are seeing, which should occur only for verbose output, is purely informational. For most features, a new...

This is a different question. Assuming the values for HDMI-1 and HDMI-2 conform to the MCCS specification and are x11 and x12 on your monitor, you need to write **ddcutil...

HDMI-2 is 0x12 = 18. x0c is the value for Component video 1 i.e. you want **ddcutil setvcp 60 x12** or **ddcutil setvcp x60 x12** For values, see **ddcutil vcpinfo...

I'm at a loss for what else to add. The **vcpinfo** output is telling you what all the possible values are for feature x60, according to the MCCS (Monitor Control...

When you write "although ddcutil detectds the USB-C port it can't read the features/capabilities of the monitor", here's what I think you're describing: The ddcutil command, and indirectly ddcui, scans...

The "sniffing" system can be running Linux, Mac, or Windows.  the I2CDriver card is connected to the sniffer over USB (the connector on the card is Micro-USB.  So yes, since...

The problem is clearly with the monitor, though the problem may appear only with a particular video card. Every I2C read response packet starts with a double x6e byte. ....

One thing to keep in mind in your tests if your have multiple connections to the monitor. Some monitors respond to DDC communication only on the currently selected input. Others...

Displays vary in how they implement DDC when multiple monitors are attached.  Feature code x60 is particularly problematic. For some, setvcp works only if issued from the device whose input...