Michael Hamilton

Because of another issue with the driver (not DDC related) I've reverted to Nvidia driver 525.116.04 - hopefully they will eventually fix their driver.

Nvidia driver 545.29.06 with kernel 6.7.2 and either ddcutil 1.4.1 or 2.1.4 seems to be working OK now. Thats with a passive DP-DVI cable and a DP-DP cable.

While debugging this I was deleting the `displays` cache without deleting the `dsa` cache. Could that cause issues? I was seeing some unexpected errors issuing getvcp/setvcp - they were transient...

After running vdu_controls with 2.0.0-rc1 all of today, I see I definitely need to pass `--disable-displays-cache` for all ddcutil invocations, not just for detect. Otherwise the different error behaviour defeats...

> After running vdu_controls with 2.0.0-rc1 all of today, I see I definitely need to pass `--disable-displays-cache` for all ddcutil invocations, not just for detect. Otherwise the different error behaviour...

> The `--enable-displays-cache` seems to be enabled by default. I have two monitors, I powered one down, which results in: > > ``` > % ddcutil detect > Invalid display...

> @digitaltrails I've added changes to branch 2.0.0-dev intended to avoid restoring stale cached display references. I was not able to replicate your problem of a display ref for a...

One difference between --disable-display-cache/--enable-displays-cache is what happens after a previously identified edid specified VDU gets powered off or suspended. Doing a getvcp to the edid with cache off returns the...

> It turns out that using slave address x13 as a proxy for whether the monitor is turned on does not always work. I have a monitor, (Samsung U32H750x) that...

Thanks for the explanation, so `--enable-displays-cache` was directed at speeding up all operations, quite different from caching in `vdu_controls`. I've been using `--enable-dynamic-sleep` as my daily-driver right back from the...