From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107414] "No EDID firmware found on connector" when display forced on and EDID file provided Date: Sat, 28 Jul 2018 16:23:14 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0758370120==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6B41A6E02F for ; Sat, 28 Jul 2018 16:23:14 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0758370120== Content-Type: multipart/alternative; boundary="15327949940.CDe4a.20504" Content-Transfer-Encoding: 7bit --15327949940.CDe4a.20504 Date: Sat, 28 Jul 2018 16:23:14 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D107414 Bug ID: 107414 Summary: "No EDID firmware found on connector" when display forced on and EDID file provided Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: chewi@gentoo.org Created attachment 140869 --> https://bugs.freedesktop.org/attachment.cgi?id=3D140869&action=3Dedit Kernel log showing one display on and one display off I've been using drm.edid_firmware for a long time now to provide some stabi= lity in my setup, which includes an A/V receiver that isn't always on. However, = I've found that it still isn't as stable as I'd like it to be because this alone doesn't force the display to be connected. Only the "e" option in the video parameter does that so I've added it and it works but only if the display is actually switched on at boot time! It seems that the provided EDID file is initially ignored when the "e" opti= on is checked, resulting in the following error and the display actually being forced off. [drm:amdgpu_dm_connector_mode_valid [amdgpu]] *ERROR* No EDID firmware foun= d on connector: HDMI-A-1 ,forcing to OFF! This may be because the EDID file only seems to be read during a mode set. = It certainly isn't because the file isn't available yet as I've added it to the initramfs to make sure and the second display that is switched on picks it = up. --=20 You are receiving this mail because: You are the assignee for the bug.= --15327949940.CDe4a.20504 Date: Sat, 28 Jul 2018 16:23:14 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 107414
Summary "No EDID firmware found on connector" when display = forced on and EDID file provided
Product DRI
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter chewi@gentoo.org 

Created attachment 140869 [details]
Kernel log showing one display on and one display off

I've been using drm.edid_firmware for a long time now to provide some stabi=
lity
in my setup, which includes an A/V receiver that isn't always on. However, =
I've
found that it still isn't as stable as I'd like it to be because this alone
doesn't force the display to be connected. Only the "e" option in=
 the video
parameter does that so I've added it and it works but only if the display is
actually switched on at boot time!

It seems that the provided EDID file is initially ignored when the "e&=
quot; option
is checked, resulting in the following error and the display actually being
forced off.

[drm:amdgpu_dm_connector_mode_valid [amdgpu]] *ERROR* No EDID firmware foun=
d on
connector: HDMI-A-1 ,forcing to OFF!

This may be because the EDID file only seems to be read during a mode set. =
It
certainly isn't because the file isn't available yet as I've added it to the
initramfs to make sure and the second display that is switched on picks it =
up.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15327949940.CDe4a.20504-- --===============0758370120== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0758370120==--