rockowitz

Than you for the listings. Now I have a dump of (relevant portions of) /sys for the amdgpu case as well as the i915 case. I'm hoping I'll be able...

No, it's just confusing until you know what's going on.

The current 1.0.2-dev branch contains experimental code to detect "phantom" displays, at least in your case. If one is found, **detect** reports it as a "Phantom Display" as opposed to...

Likely ddcci. It's interesting to see how it causes failure. Try using option **--force-slave-address**. If ioctl(I2C_SLAVE) fails, ddcutil will retry using I2C_SLAVE_FORCE. Expect to see a diagnostic message for this...

So **--force-slave-address** solves the conflict with ddcci. Does ddcci continue to work? What to send to stdout and what to send to stderr can be a grey area. I've tweaked...

The current 1.0.2-dev build contains several changes to address the problems you've detected: - Fix the cause of the assert() failure when the setting the I2C slave address returns -EBUSY...

Thanks for the kudos. I'm not convinced that the solution works for drivers other than amdgpu and i915, which is why the check is coded the way it is: check...

Please submit the output of **sudo ddcutil interrogate** as an attachment. Please also submit the output of **sudo ddcutil detect --f4** as an attachment.

I myself have a U32H750, which is the same monitor, only bigger. I'm a little baffled by your description of USB hubs with HDMI output.  What exactly are they?  What...

There are problems in the DRM drivers (i915, amdgpu, etc.). A lot of effort has gone into the upcoming release to detect and to some extent work around these problems....