<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - xf86-video-intel-2.99.917 should allow edid override to known edid.bin file for AVR+TV combinations" href="https://bugs.freedesktop.org/show_bug.cgi?id=89945#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - xf86-video-intel-2.99.917 should allow edid override to known edid.bin file for AVR+TV combinations" href="https://bugs.freedesktop.org/show_bug.cgi?id=89945">bug 89945</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to lucas oldfield from <a href="show_bug.cgi?id=89945#c11">comment #11</a>) > Created <a href="attachment.cgi?id=114956" name="attach_114956" title="dmesg log with drm.debug=14 original intel driver AVR+TV w/ AVR power cycle">attachment 114956</a> <a href="attachment.cgi?id=114956&action=edit" title="dmesg log with drm.debug=14 original intel driver AVR+TV w/ AVR power cycle">[details]</a> > dmesg log with drm.debug=14 original intel driver AVR+TV w/ AVR power cycle > > Original intel driver with debugging. > > AVR power cycle. > > AVR ON -> OFF = OK as usual > > AVR OFF -> ON = failed screen and audio Here, it seems to me we get the hotplugs for AVR/TV power cycling just fine, and the EDID reading succeeds when they are powered back on. AFAICT the EDID failures happen when we get hot *un* plug for the power off, we still have the cable connected, and fail to read EDID. It seems a bit ugly, sure, but from kernel driver perspective I think it's functional. What does xrandr --verbose say after you've power cycled the AVR?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>