rockowitz

The issue is layers below i2c-dev, i.e. the video driver. i2c-dev "just" provides a common, standard kernel interface for all i2c drivers. However, there is one quirk that you might...

This is exciting! An actual example that can be referenced of DDC communication being fixed by lowering the bus speed! The devil, of course, is in the details: what other...

@w8jcik I created [issue 11528](https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11528) at freedesktop.org. Please comment on that issue with the details of your driver changes. I would encourage those having DDC communication errors that **ddcutil** cannot...

Thank you for the report. I'm surprised that **ddcutil** ever worked with DisplayLink. Last I looked at DisplayLink, which was some time ago, there was no support for DDC/CI. Apparently...

Commit b3573c2 is irrelevant to your problem. It applies only to libddcutil, not command line ddcutil. The relevant commit, which you located, is 28b7b345a. The solution is not trivial. The...

I posted a detailed follow-up comment, but it seems to have been lost. In brief, branch 2.1.5-dev contains special code for reading the EDID of DisplayLink devices. Let me know...

That the monitor locks up is disconcerting; it's not a behaviour I've seen. Try using options ***--bus 6 --skip-ddc-checks*** to reduced the monitor interactions on the **detect** command. The DDC...

My oops. ***--skip-ddc-checks*** is applicable to all commands, but ***--bus*** only applies to single display commands like **getvcp**. Each reduce the overhead operations at the start of commands. To submit...

A final thought is that the monitor is in Eye-Care or some other mode such as Cinema that disables external control using DDC. (I assume you've actually verified that DDC...

Thank you for the report. The issue is addressed in branch 2.1.5-dev, which changes the severity of the log messages in question from WARNING to VERBOSE. If you are running...