From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108806] AMDGPU Failed to read EDID from display
Date: Tue, 20 Nov 2018 04:01:59 +0000 [thread overview]
Message-ID: <bug-108806-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1246 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108806
Bug ID: 108806
Summary: AMDGPU Failed to read EDID from display
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: michael.lindman@gmail.com
Created attachment 142526
--> https://bugs.freedesktop.org/attachment.cgi?id=142526&action=edit
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
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2683 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-11-20 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 4:01 bugzilla-daemon [this message]
2018-11-20 4:03 ` [Bug 108806] AMDGPU Failed to read EDID from display bugzilla-daemon
2018-11-20 9:09 ` bugzilla-daemon
2019-03-10 15:19 ` bugzilla-daemon
2019-07-12 1:30 ` bugzilla-daemon
2019-11-19 9:05 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108806-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.