Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Philips 276E8V invalid monitor, but only one of two #410

Closed
jonas-w opened this issue Apr 28, 2024 · 8 comments
Closed

Philips 276E8V invalid monitor, but only one of two #410

jonas-w opened this issue Apr 28, 2024 · 8 comments

Comments

@jonas-w
Copy link

jonas-w commented Apr 28, 2024 •
edited
Loading

As you can see in the output of ddcutil detect the first monitor gets detected without issues (and I can also change its brightness), but the second one is marked as 'Invalid Display'.

Click on details for the output of ddcutil detect

Display 1
   I2C bus:  /dev/i2c-8
   DRM connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 2082 (0x00000822)
      Manufacture year:     2020,  Week: 4
   VCP version:         2.2

Invalid display
   I2C bus:  /dev/i2c-9
   DRM connector:           card1-DP-2
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 1110 (0x00000456)
      Manufacture year:     2018,  Week: 46
   DDC communication failed. (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)])

Both are connected to my RX 7900 XTX via Displayport.

I bought both at the same time a few years ago, but it seems like the 'Invalid' one is a bit older.

I'm using NixOS and sway.

ddcutil interrogate output:
ddcutil_interrogate.txt
@rockowitz
Copy link
Owner

See the suggestions on issue #409.

What's peculiar here is that one monitor is responsive, one not. I assume you've tried swapping them.

@jonas-w
Copy link
Author

jonas-w commented May 2, 2024

@rockowitz sorry for the late reply, yeah I swapped cables and ports on the graphics card, but the same monitor (same SN) was detected as invalid.

The suggestions from #409 did not change anything, it looks the same with and without the sleep options.

Output of ddcutil detect --disable-dynamic-sleep --sleep-multiplier 2.0 --stats errors --ddcdata 
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
DDC: Unexpected source address 0x70, should be 0x6e
DDC: i2c_response_bytes: 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
Display 1
   I2C bus:  /dev/i2c-8
   DRM connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 2082 (0x00000822)
      Manufacture year:     2020,  Week: 4
   VCP version:         2.2

Invalid display
   I2C bus:  /dev/i2c-9
   DRM connector:           card1-DP-2
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 1110 (0x00000456)
      Manufacture year:     2018,  Week: 46
   DDC communication failed. (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)])


EXECUTION STATISTICS

DDC Related Errors:  

Count   Status Code                          Description
   10   DDCRC_DDC_DATA               (-3001) DDC data error 
    1   DDCRC_RETRIES                (-3007) maximum retries exceeded  (derived)
Total errors: 11

Errors Wrapped in Retry:  

Count   Status Code                          Description
   10   DDCRC_DDC_DATA               (-3001) DDC data error 
Total errors: 10

I've also factory reset both, but did also change nothing.

@rockowitz
Copy link
Owner

I'd say you have your answer, though if you swapped the cable along with the monitor it could be that.

@jonas-w
Copy link
Author

jonas-w commented May 6, 2024

I'd say you have your answer

Basically a monitor issue?

@rockowitz
Copy link
Owner

Monitor or possibly cable, depending on how you did the swap.

@jonas-w
Copy link
Author

jonas-w commented May 6, 2024

Monitor or possibly cable, depending on how you did the swap.

Then monitor :/ As I used the same port and cable which worked for the other monitor.

@jonas-w jonas-w closed this as completed May 6, 2024
@jonas-w
Copy link
Author

jonas-w commented May 6, 2024 •
edited
Loading

Okay reopening this one.

I just connected the monitor that didn't work via HDMI and now it got detected and I also could set the brightness. But while one (the one that was working previously) was connected via DP and the other (that didn't work) via HDMI, the one connected via DP was detected but I couldn't set its brightness.

ddcutil detect while one was connected via DP and the other via DP and HDMI 
Display 1
   I2C bus:  /dev/i2c-7
   DRM connector:           card1-HDMI-A-2
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 1110 (0x00000456)
      Manufacture year:     2018,  Week: 46
   VCP version:         2.2

Display 2
   I2C bus:  /dev/i2c-8
   DRM connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 2082 (0x00000822)
      Manufacture year:     2020,  Week: 4
   VCP version:         2.2

Display 3
   I2C bus:  /dev/i2c-9
   DRM connector:           card1-DP-2
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 1110 (0x00000456)
      Manufacture year:     2018,  Week: 46
   VCP version:         2.2

After I disconnected the HDMI cable and connected the 'non working' one via DP, it still was detected, but I'm now still only able to set the brightness for the 'working one'.

ddcutil detect after unplugging HDMI 
Display 1
   I2C bus:  /dev/i2c-8
   DRM connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 2082 (0x00000822)
      Manufacture year:     2020,  Week: 4
   VCP version:         2.2

Display 2
   I2C bus:  /dev/i2c-9
   DRM connector:           card1-DP-2
   EDID synopsis:
      Mfg id:               PHL - Philips Consumer Electronics Company
      Model:                PHL 276E8V
      Product code:         49551  (0xc18f)
      Serial number:        
      Binary serial number: 1110 (0x00000456)
      Manufacture year:     2018,  Week: 46
   VCP version:         2.2

EDIT: now I realized that I need to specify the display number, so currently I can set the brightness for both when I either specify -d 1 or -d 2, I'll see what is the state after I reboot.

@jonas-w jonas-w reopened this May 6, 2024
@jonas-w
Copy link
Author

jonas-w commented May 6, 2024

Okay, for whatever reason it just works.

So for future reference: The 'solution' was to connect the nonworking monitor via HDMI and then running ddcutil detect, afterward it just works 🤷🏼‍♂️

@jonas-w jonas-w closed this as completed May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rockowitz @jonas-w