[Bug 100885] New: Blank screen after cycling HDMI receiver input
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Apr 29 18:34:32 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=100885
Bug ID: 100885
Summary: Blank screen after cycling HDMI receiver input
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: matt at matthoran.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 131151
--> https://bugs.freedesktop.org/attachment.cgi?id=131151&action=edit
dmesg from first boot and after HDMI cycle
Since upgrading to a new HDMI receiver, I've been encountering an issue with my
Intel Graphics based systems. On first boot, HDMI output displays fine through
the receiver and on the TV. However, after cycling to another HDMI input on the
receiver and then back to the PC, the screen remains blank.
There may be a deeper issue here, as I see this before KMS has been
initialized, e.g. in the BIOS menu. However, I'm hoping there's something that
can be done to address the issue.
The EDID detected by the system is identical both before and after the cycle.
I've attached the EDID and a dmesg with debugging, which shows the messages on
first boot and then after cycling the input.
I've been able to reproduce this on multiple Intel Graphics based systems
connected to the same HDMI input.
Note that there is a forum discussion on the manufacturer's website that
discusses this specific issue as well:
http://emotivalounge.proboards.com/thread/38824/xmc-pc-hdmi-handshake-problem
Any help would be much appreciated.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170429/a3f59a56/attachment.html>
More information about the intel-gfx-bugs
mailing list