rockowitz
Samsung S24D300 Detection Issues
I am not able to get my Samsung S24D300 to work with ddcutil from a Raspberry Pi 4 and 5, with Raspberry OS and Ubuntu. From the other issues, I am guessing it is a monitor-specific issue but I hope there is a way around it.
Here is interrogate: interrogate-verbose.txt
Some outputs:
What options I tried so far: --disable-try-get-edid-from-sysfs, --sleep-multiplier 2.0 and other values.
Here is an interesting command output for sudo ddcutil -b 13 getvcp 10 --skip-ddc-checks:
VCP (aka MCCS) version for display is undetected or less than 2.0. Interpretation may not be accurate.
VCP code 0x10 (Brightness ): current value = 93, max value = 100
On Windows, using https://github.com/MartinGC94/MonitorConfig with Samsung drivers worked.
That getvcp --skip-ddc-checks succeeds, but detect fails, indicates that ddc communication is working, but the code that checks whether slave address x37 is active is not. This section of code was recently reworked to handle a bug in the interface between driver i2c-dev and old versions of the Nvidia proprietary video driver - the changes may address your situation as well.
If you can, please build from branch 2.2.1-dev and test again. If detect continues to fail, please execute ddcutil detect --verbose --trcfunc i2c_detect_x37 --trcfunc i2c_check_bus and submit the output. If you continue to see errors with status code DDCRC_DDC_DATA, option --ddcdata will report the invalid packets. Thanks.
I am getting the build error, following https://www.ddcutil.com/building/#building-from-git
configure.ac:52: error: possibly undefined macro: AC_MSG_NOTICE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:229: error: possibly undefined macro: AC_MSG_ERROR
configure.ac:646: error: possibly undefined macro: AC_MSG_WARN
The command that generates the error is autoconf
In the meantime, here is the dump of ddcutil setvcp 10 30 --ddcdata
DDC: Unexpected source address 0x03, should be 0x6e
DDC: i2c_response_bytes: 03 06 00 00 00 09 30 b0 00 0c 75 50 7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
DDC: Unexpected source address 0x00, should be 0x6e
DDC: i2c_response_bytes: 00 00 00 03 52 00 00 00 16 97 17 17 37 37 57 67 77 07 97 a7 b7 87 c7 e7 e7 80 15 17 27 47 47 7f ff ff ff ff ff ff ff ff
DDC: Unexpected source address 0x97, should be 0x6e
DDC: i2c_response_bytes: 97 d7 d7 80 1d 1f e0 03 83 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
DDC: Unexpected source address 0x25, should be 0x6e
DDC: i2c_response_bytes: 25 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
DDC: Unexpected source address 0x0b, should be 0x6e
DDC: i2c_response_bytes: 0b ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
DDC: Unexpected source address 0x03, should be 0x6e
DDC: i2c_response_bytes: 03 27 00 76 05 37 34 0d 0c ff ff 00 84 38 07 00 84 38 07 04 04 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
DDC: All zero response detected in ddc_i2c_write_read_raw
DDC: Unexpected source address 0x00, should be 0x6e
DDC: i2c_response_bytes: 00 00 00 00 02 00 51 7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
DDC: Unexpected source address 0x84, should be 0x6e
DDC: i2c_response_bytes: 84 51 50 03 03 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
DDC: Unexpected source address 0x11, should be 0x6e
DDC: i2c_response_bytes: 11 10 3f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Display not found
Use automake option --add-missing, i.e. automake --add-missing.
The web page will be updated when the site is updated to correspond with upcoming release 2.2.1.