Bug 108806 - AMDGPU Failed to read EDID from display
Summary: AMDGPU Failed to read EDID from display
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-20 04:01 UTC by Michael Lindman
Modified: 2019-11-19 09:05 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
boot log showing EDID failure (91.61 KB, text/plain)
2018-11-20 04:01 UTC, Michael Lindman
no flags Details

Description Michael Lindman 2018-11-20 04:01:59 UTC
Created attachment 142526 [details]
boot log showing EDID failure

When connecting one of my monitors to the system it defaults to 1024x768 and not the native resolution and grepping through the kernel logs shows that AMDGPU fails to read the EDID of the display.

[    5.054779] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.

The display was working fine as of kernel 4.18.18 with the issues arising upon 4.19.2.

I am using a POLARIS 10 GPU and both displays are connected to DisplayPort with the Asus PG2780 having the issues with failing to grab the EDID.

DisplayPort-0 LG 25UM65-P
DisplayPort-1 ASUS PG278Q
Comment 1 Bernard Sébastien 2019-03-10 15:19:03 UTC
Same problem here with RX480 and ASUS PG278Q.
Can't figure out what's broken.
Is it the bios of the card, the EDID of the monitor or the code in the amdgpu module ?
Comment 2 Cameron 2019-07-12 01:30:17 UTC
I'm also having having the "No EDID read." issue with this monitor and a wx 5100. With the generic Ubuntu 5.0.0-20 kernel on 10.94 as well as on my custom 5.1.17 kernel.

However, I don't even get anything on the screen. My monitor just flashes from black to lighter black... However, I'm running on POWER (PPC) so I may be encountering additional issues in my case.

However, the petitboot firmware gives me a text screen. The firmware is running 4.19.0 which suggests that something has broken since then as others have suggested.
Comment 3 Martin Peres 2019-11-19 09:05:04 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/615.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.