-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DDC communication fails with a Lenovo T24i-10 #467
Comments
Attempting to read feature X10 (Brightness) is part of the tests as to whether the monitor supports DDC; I've yet to see a monitor that does not implement that feature. Strangely, it is however readable when performed by command probe. What is the output of ddcutil --bus 7 getvcp 10 --verbose? |
Also, as a workaround, consider using option --skip-ddc-checks, introduced in release 2.1.0. Testing DDC communication occurs in two parts. At the basic I2C layer, there's a simple check that I2C slave address x37 (DDC) is alive. At the higher DDC layer, communication is tested by actually attempting to read feature x10 (which should always exist) and also to read several features that are expected not to exists, to check for the possibility that the monitor reports unsupported features incorrectly. Option --skip-ddc-checks skips the latter tests. (The option was introduced to improve performance of scripts invoking ddcutil repeatedly for the same device.) |
but sometimes it also only prints this:
|
Using
However, observer the outputs of these commands:
The error is a different one, but it still fails to set the brightness. |
All of these errors reflect DDC communication failure. Please submit the output of ddcutil detect --verbose --ddcdata. This should show the bytes of the packets returned by the monitor. |
|
I'm getting basically the same output on my BenQ GW2480 on running
|
I have a Lenovo T24i-10 connected via HDMI and get an error when using
ddcutil detect
. I think the monitor should support DDC, but right now, it doesn't work withddcutil
On my Samsung C34J79xddcutil
works as expected.Output for
ddcutil detect
:Output of
i2cdetect -y 7
, maybe it is of interest:Output of
ddcutil interrogate
: interrogate.txtPlease let me know if I can supply you with more information.
The text was updated successfully, but these errors were encountered: