From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-107414-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1738 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107414
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=140869&action=edit
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 stability
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" 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 found 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.
[-- Attachment #1.2: Type: text/html, Size: 3286 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-07-28 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 16:23 bugzilla-daemon [this message]
2018-07-28 16:23 ` [Bug 107414] [amdgpu] "No EDID firmware found on connector" when display forced on and EDID file provided bugzilla-daemon
2019-01-12 13:50 ` bugzilla-daemon
2019-11-19 8:45 ` 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-107414-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.