Comments (13)
rockowitz
commented on September 25, 2024
I reconfigured the system I'm on now to use a DVI to DP adapter instead of plugging a DVI monitor directly into the DVI output on my RX580. I wasn't able to recreate your problem on ddcutil 2.0.0, but I did trigger similar errors on 2.0.2-dev. The problem seems to be related to aggressive parallelization in display detection and attempting to avoid explicitly reading the EDID by obtaining it from /sys.
If you can, please build from branch 2.0.2-dev. If the problem does not resolve, try disabling dynamic the dynamic sleep adjustment (--disable-dynamic-sleep) and disabling parallel DDC checks (--ddc-check-async-threshold 9). On the other hand, if no problems are encountered, try either or both of the following: hidden option --i2c-bus-check-async-threshold 1 turns on parallel checking for EDIDs, and hidden utility option --f14 enables reading the EDID from /sys. Thanks.
from ddcutil.
CrashTD
commented on September 25, 2024
2.0.2-dev detect without arguments works partially. at least the double detected display is gone.
ddcutil detect
Invalid display
I2C bus: /dev/i2c-4
DRM connector: card1-DP-3
EDID synopsis:
Mfg id: SAM - Samsung Electric Company
Model: SyncMaster
Product code: 953 (0x03b9)
Serial number: HS3Q800096
Binary serial number: 1279865394 (0x4c493232)
Manufacture year: 2008, Week: 33
DDC communication failed. (getvcp of feature x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO])
Display 1
I2C bus: /dev/i2c-5
DRM connector: card1-HDMI-A-1
EDID synopsis:
Mfg id: PHL - Philips Consumer Electronics Company
Model: 247ELPH
Product code: 49286 (0xc086)
Serial number: AU51211007766
Binary serial number: 7766 (0x00001e56)
Manufacture year: 2012, Week: 11
VCP version: 2.2
Display 2
I2C bus: /dev/i2c-6
DRM connector: card1-DP-1
EDID synopsis:
Mfg id: ENC - Eizo Nanao Corporation
Model: S2202W
Product code: 6517 (0x1975)
Serial number: 73068119
Binary serial number: 16843009 (0x01010101)
Manufacture year: 2009, Week: 45
VCP version: 2.0
with arguments seems to make things better as well but now its "detection failed":
ddcutil detect --disable-dynamic-sleep --ddc-check-async-threshold 9
Display 1
I2C bus: /dev/i2c-4
DRM connector: card1-DP-3
EDID synopsis:
Mfg id: SAM - Samsung Electric Company
Model: SyncMaster
Product code: 953 (0x03b9)
Serial number: HS3Q800096
Binary serial number: 1279865394 (0x4c493232)
Manufacture year: 2008, Week: 33
VCP version: Detection failed
Display 2
I2C bus: /dev/i2c-5
DRM connector: card1-HDMI-A-1
EDID synopsis:
Mfg id: PHL - Philips Consumer Electronics Company
Model: 247ELPH
Product code: 49286 (0xc086)
Serial number: AU51211007766
Binary serial number: 7766 (0x00001e56)
Manufacture year: 2012, Week: 11
VCP version: 2.2
Display 3
I2C bus: /dev/i2c-6
DRM connector: card1-DP-1
EDID synopsis:
Mfg id: ENC - Eizo Nanao Corporation
Model: S2202W
Product code: 6517 (0x1975)
Serial number: 73068119
Binary serial number: 16843009 (0x01010101)
Manufacture year: 2009, Week: 45
VCP version: 2.0
I was just going to test --i2c-bus-check-async-threshold 1 as well but with that my monitors turned 2 x black and 1 complete green screen and my system rebooted. i'm not sure how to interpret the journal but looks like it somehow crashed KDE Power management system.
edit
tried again:
ddcutil detect --i2c-bus-check-async-threshold 1
Display 1
I2C bus: /dev/i2c-5
DRM connector: card1-HDMI-A-1
EDID synopsis:
Mfg id: PHL - Philips Consumer Electronics Company
Model: 247ELPH
Product code: 49286 (0xc086)
Serial number: AU51211007766
Binary serial number: 7766 (0x00001e56)
Manufacture year: 2012, Week: 11
VCP version: 2.2
ddcutil detect --f14
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 4c 2d b9 03 32 32 49 4c ........L-..22IL
+0010 21 12 01 03 80 2f 1e 78 2a d5 11 a4 55 49 9a 27 !..../.x*...UI.'
+0020 14 50 54 bf ef 80 b3 00 81 80 81 40 71 4f 01 01 .PT........@qO..
+0030 01 01 01 01 01 01 7c 2e 90 a0 60 1a 1e 40 30 20 ......|...`..@0
+0040 36 00 cb 28 11 00 00 1a 00 00 00 fd 00 38 4b 1e 6..(.........8K.
+0050 51 0e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
+0060 79 6e 63 4d 61 73 74 65 72 0a 20 20 00 00 00 ff yncMaster. ....
+0070 00 48 53 33 51 38 30 30 30 39 36 0a 20 20 00 1b .HS3Q800096. ..
Display 1
I2C bus: /dev/i2c-4
DRM connector: card1-DP-3
EDID synopsis:
Mfg id: SAM - Samsung Electric Company
Model: SyncMaster
Product code: 953 (0x03b9)
Serial number: HS3Q800096
Binary serial number: 1279865394 (0x4c493232)
Manufacture year: 2008, Week: 33
VCP version: Detection failed
Display 2
I2C bus: /dev/i2c-5
DRM connector: card1-HDMI-A-1
EDID synopsis:
Mfg id: PHL - Philips Consumer Electronics Company
Model: 247ELPH
Product code: 49286 (0xc086)
Serial number: AU51211007766
Binary serial number: 7766 (0x00001e56)
Manufacture year: 2012, Week: 11
VCP version: 2.2
Display 3
I2C bus: /dev/i2c-6
DRM connector: card1-DP-1
EDID synopsis:
Mfg id: ENC - Eizo Nanao Corporation
Model: S2202W
Product code: 6517 (0x1975)
Serial number: 73068119
Binary serial number: 16843009 (0x01010101)
Manufacture year: 2009, Week: 45
VCP version: 2.0
Invalid display
I2C bus: /dev/i2c-8
DRM connector: card1-DP-3
EDID synopsis:
Mfg id: SAM - Samsung Electric Company
Model: SyncMaster
Product code: 953 (0x03b9)
Serial number: HS3Q800096
Binary serial number: 1279865394 (0x4c493232)
Manufacture year: 2008, Week: 33
DDC communication failed. (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: EREMOTEIO(10)])
ddcutil detect --f14 --i2c-bus-check-async-threshold 1
Invalid display
I2C bus: /dev/i2c-4
DRM connector: card1-DP-3
EDID synopsis:
Mfg id: SAM - Samsung Electric Company
Model: SyncMaster
Product code: 953 (0x03b9)
Serial number: HS3Q800096
Binary serial number: 1279865394 (0x4c493232)
Manufacture year: 2008, Week: 33
DDC communication failed. (getvcp of feature x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO])
Display 1
I2C bus: /dev/i2c-5
DRM connector: card1-HDMI-A-1
EDID synopsis:
Mfg id: PHL - Philips Consumer Electronics Company
Model: 247ELPH
Product code: 49286 (0xc086)
Serial number: AU51211007766
Binary serial number: 7766 (0x00001e56)
Manufacture year: 2012, Week: 11
VCP version: 2.2
Display 2
I2C bus: /dev/i2c-6
DRM connector: card1-DP-1
EDID synopsis:
Mfg id: ENC - Eizo Nanao Corporation
Model: S2202W
Product code: 6517 (0x1975)
Serial number: 73068119
Binary serial number: 16843009 (0x01010101)
Manufacture year: 2009, Week: 45
VCP version: 2.0
Invalid display
I2C bus: /dev/i2c-8
DRM connector: card1-DP-3
EDID synopsis:
Mfg id: SAM - Samsung Electric Company
Model: SyncMaster
Product code: 953 (0x03b9)
Serial number: HS3Q800096
Binary serial number: 1279865394 (0x4c493232)
Manufacture year: 2008, Week: 33
DDC communication failed. (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: EREMOTEIO(10)])
do you need interrogate --verbose for every combination as well?
from ddcutil.
rockowitz
commented on September 25, 2024
There are several things going on here. First, attempting to read the EDID in parallel from all /dev/i2c devices can sometimes, but not always fail. Reading the EDID from /sys (using --f14) avoids this problem, but can encounter obscure error in the EDID that amdgpu writes to sys, which I was hoping to avoid. For now, the default is --disable-i2c-bus-check-async_threshold.
Have you tried setting a high fixed sleep-multiplier, e.g. --sleep-multiplier 2.0 --disable-dynamic-sleep. That Samsung monitor is rather old, and its DDC implementation may be marginal. Have you tried another monitor in the DP-3 slot? And do you know if your DP-DVI cable/adapter is active or passive?
from ddcutil.
CrashTD
commented on September 25, 2024
sorry for the late reply. busy days.
--sleep-multiplier 2.0 --disable-dynamic-sleep jumps between working and giving correct output to "DDC communication failed" and "VCP Version: Detection failed". the adapter is a active one, but as far i remember not exactly high-quality. the Monitor in the DP-1 slot is connected via the same adapter, so i don't think this is the problem. but i can switch it with the Samsung when i get the chance and test. currently i have no real DP monitor that i could test at that port, but will have next year. but that GPU is brand new so i don't think (or at least hope) its the port itself that is the problem.
i'm not at home until new year so i can't do further testing. will update here as soon i can.
I would like to thank you for the fast and friendly communication so far and wish you a happy new year!
from ddcutil.
CrashTD
commented on September 25, 2024
I think i can can close this. The monitor in question got replaced now and the new gets detected perfect. so I'll file this under strange quirk of this specific device.
from ddcutil.
Matt-1-2-3
commented on September 25, 2024
I am having the same issue with my LG OLED 4k C3 tv
:ddcutil detect
Invalid display
I2C bus: /dev/i2c-5
DRM connector: card1-HDMI-A-1
EDID synopsis:
Mfg id: GSM - Goldstar Company Ltd (LG)
Model: LG TV SSCR2
Product code: 33229 (0x81cd)
Serial number:
Binary serial number: 16843009 (0x01010101)
Manufacture year: 2023, Week: 1
DDC communication failed. (getvcp of feature x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO])
Display 1
I2C bus: /dev/i2c-6
DRM connector: card1-DP-1
EDID synopsis:
Mfg id: NEC - NEC Corporation
Model: EA243WM
Product code: 26725 (0x6865)
Serial number: 32117493NA
Binary serial number: 0 (0x00000000)
Manufacture year: 2013, Week: 6
VCP version: 2.0
from ddcutil.
rockowitz
commented on September 25, 2024
@Matt-1-2-3 Please ensure you are running the new release 2.1.2? Then submit the output of ddcutil interrogate
from ddcutil.
Matt-1-2-3
commented on September 25, 2024
I am attaching the output of interrogate as a text file. It's long and my user name was replaced with "myuser" and hostname with "myhost"
ddcutil --version
ddcutil 2.1.2
Copyright (C) 2015-2024 Sanford Rockowitz
License GPLv2: GNU GPL version 2 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
output.txt
from ddcutil.
rockowitz
commented on September 25, 2024
The output of command i2cdetect -y 5 on line 631 shows that while slave address x50 (EDID) is responsive, slave address x37 (DDC) is not. So whatever problem you're having is outside of ddcutil's control. I see that you're running on a Zen kernel. I suggest you try using a stock kernel. If the problem resolves, i.e. i2cdetect reports slave address x37 as responsive, the problem is an issue for the Zen developers.
from ddcutil.
Matt-1-2-3
commented on September 25, 2024
Ill reboot and try stock kernel
from ddcutil.
Matt-1-2-3
commented on September 25, 2024
Unfortunately stock kernel with the same results, new log uploaded
output_stock_kernel.txt
from ddcutil.
rockowitz
commented on September 25, 2024
The i2cdetect output in the interrogate log is unchanged. I don't see why it would show anything different, but for absolute certainty try running i2cdetect directly from the terminal, outside of ddcutil.
from ddcutil.
Matt-1-2-3
commented on September 25, 2024
from the cli itself
me@pc[~]:i2cdetect -y 5
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: 30 -- -- -- -- -- -- -- -- -- 3a -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
from ddcutil.
Related Issues (20)
- Enhancement - consider packaging module loading HOT 2
- "Keeping adjust sleep multiplier" warning shown many times HOT 1
- Monitor resets many times on boot after new udev rule installed HOT 44
- System cannot enter S0ix sleep after running ddcutil detect HOT 8
- No (DisplayLink) displays found on 2.1.4, but works on 2.0.0 HOT 6
- ddcutil 2.1.4-1: DDC communication failed HOT 3
- [debian] updating linux-image pkg fails due to ddcutil dkms module failure HOT 2
- Cannot get capabilities: Maximum DDC retries exceeded. HOT 8
- Add an option to return the capabilities for a specific feature. HOT 4
- DDC communication failed (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(15)]) HOT 1
- Ddcutil crashes when some usb devices are connected HOT 1
- `ddcutil` ignores the final entry in `XDG_DATA_DIRS` when looking for an `mccs` file HOT 1
- Cannot update beyond 1.2.2-1 HOT 2
- Samsung C24F390 - DDC communication failed HOT 1
- ddcui controls smaller than font size on Ubuntu 24.04 HOT 1
- Can't set contrast on LG 27UN880-B.AEU HOT 2
- make: deletes build_details.h before use HOT 1
- UGREEN Revodok Pro 308: ddcutil works with 1 display but not with 2 HOT 5
- Invalid checksum of Debian Trixie package HOT 2
- DDC Communication failed. [EIO in ddc_write_read_with_retry, causes: EIO] HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ddcutil.