Michael Hamilton

If I disable drm by adding --f12 to ~/.config/ddcutil/ddcutilrc, then the problem goes away. Maybe this nvidia 550 driver's DRM is not quite all there.

> What's the output of **ddcutil det -v --f2**? [ddcutil-det-f2.log](https://github.com/rockowitz/ddcutil/files/14528227/ddcutil-det-f2.log)

The log I attached might not contain anything useful. This is beginning to look like some driver weirdness. Yesterday I connected the monitor while the system was up. This morning...

I did a cold boot and then a hot-plug of the Beng, and the fault reoccurred. Log attached. Diff'ing the two logs shows that DRM doesn't appear to be properly...

It's the driver. I powered down an disconnected my HP DP-DP connected monitor. Same story on hotplugging. ``` Display 1 I2C bus: /dev/i2c-0 EDID synopsis: Mfg id: HWP - Hewlett...

Posted a query to forums.developer.nvidia.com: [Driver 550.54 - no update to /sys/class/drm/… on hotplug of monitor](https://forums.developer.nvidia.com/t/driver-550-54-no-update-to-sys-class-drm-on-hotplug-of-monitor/285316) Sometimes these kinds of post get no official response - but often things eventually...

> I've seen this behaviour. On my deskstop system, I've found that if a monitor is removed the edid can still be there, and if a different monitor is connected...

So I should test with the latest code? Or is this something you are pursuing yourself?

Only the 2.1.5-dev branch has any recent commits, but they're not recent as in today. Am I not seeing things right?

I'm not seeing anything interesting. `ddc_validate_display_ref()` is still erroring due to a NULL `drm_connector`. I presume this may be because `/sys/class/drm/card0-DP-1/device/card0-DP-2/edid` is empty for the hotplugged monitor, whereas for all...