<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - HP Dreamcolor display *Error* No EDID read"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110371#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - HP Dreamcolor display *Error* No EDID read"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110371">bug 110371</a>
from <span class="vcard"><a class="email" href="mailto:nicholas.kazlauskas@amd.com" title="Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>"> <span class="fn">Nicholas Kazlauskas</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=110371#c4">comment #4</a>)
<span class="quote">> (In reply to Nicholas Kazlauskas from <a href="show_bug.cgi?id=110371#c3">comment #3</a>)
> > It's hitting the "." as part of the video mode and erroring out because DRM
> > doesn't consider it a valid character.
>
> Or maybe there's two separate issues? Failure to parse the mode name
> shouldn't affect whether or not DC picks up EDID, should it?</span >
I suppose that doesn't actually influence whether the EDID has been read or is
valid. So that's a different bug.
The "No EDID read." error comes from the result from drm_get_edid(...) being
NULL, however.
While we're responsible for the actual transfers to and from the receiver the
actual logic is shared there between drivers.
(In reply to Babblebones from <a href="show_bug.cgi?id=110371#c2">comment #2</a>)
<span class="quote">> Created <span class=""><a href="attachment.cgi?id=143957" name="attach_143957" title="Dmesg output from an affected kernel">attachment 143957</a> <a href="attachment.cgi?id=143957&action=edit" title="Dmesg output from an affected kernel">[details]</a></span>
> Dmesg output from an affected kernel
>
> Here is the issue, you can see
> [ 1.335096] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.
>
> Which is about where the display turns into fruit salad.
> Please let me know if I can submit any more debug info that would assist! I
> am very much in need of running a newer kernel.</span >
Can you post a dmesg log with drm.debug=4 as part of your kernel boot
parameters?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>