All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108806] AMDGPU Failed to read EDID from display
Date: Fri, 12 Jul 2019 01:30:17 +0000	[thread overview]
Message-ID: <bug-108806-502-tu2CoqpcvQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108806-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108806

--- Comment #2 from Cameron <cam@neo-zeon.de> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1492 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-07-12  1:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  4:01 [Bug 108806] AMDGPU Failed to read EDID from display bugzilla-daemon
2018-11-20  4:03 ` bugzilla-daemon
2018-11-20  9:09 ` bugzilla-daemon
2019-03-10 15:19 ` bugzilla-daemon
2019-07-12  1:30 ` bugzilla-daemon [this message]
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-tu2CoqpcvQ@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.