rockowitz

@fabian-thomas, @akdevservices Debugging these intermittent failures remotely is likely going to be a pain, but let's give it a go. Please invoke **ddcutil** with options ***--istats*** and ***---enable-dynamic-sleep***. Immediately after...

@fabian-thomas Re the phantom display issues: - What is the model of your hub? - "/sys/devices/pci0000:00/0000:00:02.0/edid" is a malformed sysfs node name. Please execute with option ***--trcfunc is_phantom_display*** and when...

The phantom displays is a device driver issue. The problem is that for one of the displays connected to the dock, it appears as both a /dev/i2c device on the...

@fabian-thomas , @akdevservices Branch 2.0.2-dev contains changes to resolve or at least further diagnose the problems reported in this issue. I suspect that the intermittent failures are the result of...

Development option --f7 disables phantom display detection. Please submit the output of **ddcutil detect --verbose ---disable-dynamic-sleep** and **ddcutil detect --verbose --disable-dynamic-sleep --f7**. Also please submit recent entries in the system...

Am I correctly inferring that **ddcutil detect** does not report the monitor attached to your hub? If so, please execute **ddcutil detect -v --f2** and submit the output as an...

I just pushed extensive changes to branch 2.0.2-dev. Please run your tests again against the updated 2.0.2-dev branch. If errors persist, please execute **ddcutil detect --verbose --f2 --trace ddc --trace...

My bad. Done.

Thank you for the quick test. Do keep me posted. If you encounter problems again, the output with just trace class DDC should be sufficient, i.e. **ddcutil detect --verbose --f2...

Reading the EDID is failing. This can be seen at approx line 677 and following, function i2c_get_raw_edid_by_fd() and i2c_get_edid_bytes_directly_using_ioctl(). There appears be a problem with your dock/hibernation/driver i915. At first...