search

rockowitz / ddcutil

Control monitor settings using DDC/CI and USB
http://www.ddcutil.com
GNU General Public License v2.0
962 stars 39 forks source link

DDC communication failed for Display Port attached monitor #19

Open jnhmn opened 7 years ago

jnhmn commented 7 years ago

Hello

I'm using 2 monitors LG 24EB23. Both attached to an Radeon R9 290 using the amdgpu driver on an Arch linux with the latest kernel (4.10.8)

I can control the monitor attached via DVI with ddcutil. But not the one attached via DP

# ddcutil detect --verbose
Output level:               Verbose
Reporting DDC data errors:  false
Trace groups active:        none
Force I2C slave address:    false

Display 1
   I2C bus:             /dev/i2c-5
   Supports DDC:        true
      I2C address 0x30 (EDID block#)  present: true 
      I2C address 0x37 (DDC)          present: true 
      I2C address 0x50 (EDID)         present: true 
      /sys/bus/i2c/devices/i2c-5/name: AMDGPU i2c bit bus 0x95
   EDID synopsis:
      Mfg id:           GSM
      Model:            24EB23
      Serial number:    (disclosed)
      Manufacture year: 2014
      EDID version:     1.3
      Product code:     0x59b4 (22964)
      Extra descriptor: Unspecified
      Video input definition: 0x80 - Digital Input
      White x,y:        0.312, 0.329
      Red   x,y:        0.652, 0.335
      Green x,y:        0.304, 0.633
      Blue  x,y:        0.152, 0.065
      Extension blocks: 0
   EDID hex dump:
              +0          +4          +8          +c            0   4   8   c   
      +0000   00 ff ff ff ff ff ff 00 1e 6d b4 59 b4 9b 02 00   .........m.Y....
      +0010   09 18 01 03 80 34 21 78 ea 3c 31 a7 55 4d a2 27   .....4!x.<1.UM.'
      +0020   10 50 54 a5 4b 00 71 4f 81 00 81 80 81 8f 95 00   .PT.K.qO........
      +0030   a9 40 b3 00 d1 c0 28 3c 80 a0 70 b0 23 40 30 20   .@....(<..p.#@0 
      +0040   36 00 08 4a 21 00 00 1a 00 00 00 fd 00 38 4b 1e   6..J!........8K.
      +0050   53 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 32   S...      .....2
      +0060   34 45 42 32 33 0a 20 20 20 20 20 20 00 00 00 ff   4EB23.      ....
      +0070   00 0a 20 20 20 20 20 20 20 20 20 20 20 20 01 d4   ..            ..
   VCP version:         2.1
   Controller mfg:      Mstar
   Firmware version:    1.1

Invalid display
   I2C bus:             /dev/i2c-8
   Supports DDC:        true
      I2C address 0x30 (EDID block#)  present: false
      I2C address 0x37 (DDC)          present: true 
      I2C address 0x50 (EDID)         present: true 
      /sys/bus/i2c/devices/i2c-8/name: card0-DP-1
   EDID synopsis:
      Mfg id:           GSM
      Model:            24EB23
      Serial number:    
      Manufacture year: 2013
      EDID version:     1.4
      Product code:     0x59b5 (22965)
      Extra descriptor: Unspecified
      Video input definition: 0xa5 - Digital Input(DisplayPort)
      White x,y:        0.312, 0.329
      Red   x,y:        0.652, 0.335
      Green x,y:        0.304, 0.633
      Blue  x,y:        0.152, 0.065
      Extension blocks: 1
   EDID hex dump:
              +0          +4          +8          +c            0   4   8   c   
      +0000   00 ff ff ff ff ff ff 00 1e 6d b5 59 01 01 01 01   .........m.Y....
      +0010   01 17 01 04 a5 34 21 78 fa 3c 31 a7 55 4d a2 27   .....4!x.<1.UM.'
      +0020   10 50 54 21 08 00 71 40 81 c0 81 00 81 80 95 00   .PT!..q@........
      +0030   a9 40 b3 00 d1 c0 28 3c 80 a0 70 b0 23 40 30 20   .@....(<..p.#@0 
      +0040   36 00 08 4a 21 00 00 1a 00 00 00 fd 00 38 3d 1e   6..J!........8=.
      +0050   53 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 32   S...      .....2
      +0060   34 45 42 32 33 0a 20 20 20 20 20 20 00 00 00 ff   4EB23.      ....
      +0070   00 0a 20 20 20 20 20 20 20 20 20 20 20 20 01 d4   ..            ..
   DDC communication failed
   Is DDC/CI enabled in the monitor's on-screen display?

(I've stripped the serial number from the first hex dump, the second was already empty)

dm17 commented 5 months ago

Anyone have it working intermittently on one DP, but not another? Also I had it working consistently with the iGPU in the same computer where the dGPU would not. Both dGPU & iGPU were AMDGPU-driven, but the iGPU was over HDMI.

In the case when it isn't working ddcutil detect --verbose shows: DDC communication failed. (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)])