ddcutil Fails to Detect EDID on New Ubuntu System with AOpen Monitor

[milad-s5]

Hi
The ddcutil command-line tool is not functioning as expected on a new Ubuntu 22 system when attempting to detect the EDID (Extended Display Identification Data) of an AOpen monitor. Although the ddcutil detect -v command works correctly on the original system, it returns an error on the new system, indicating that it cannot find the EDID. The error message is Failure getting EDID for /dev/i2c-1: status code=DDCRC_EDID(-3016): invalid EDID.
Upon further inspection, the EDID buffer retrieved by ddcutil contains an invalid EDID structure, which is not recognized by the tool. The read EDID on the new system is 00 FF FF FF 00 FF FF FF 00 FF FF FF 00 ... and so on. This issue is not related to the i2cdetect command, which successfully detects the I2C bus and the AOpen monitor's address range.

❯ sudo i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- -- 
50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --              

[rockowitz]

Please run sudo ddcutil interrogate and submit the output as an attachment.