<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [bisected][DC] commit ebbf7337e2daacacef3e01114e6be68a2a4f11b4 prevents X11 from starting" href="https://bugs.freedesktop.org/show_bug.cgi?id=102820#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [bisected][DC] commit ebbf7337e2daacacef3e01114e6be68a2a4f11b4 prevents X11 from starting" href="https://bugs.freedesktop.org/show_bug.cgi?id=102820">bug 102820</a> from <a class="email" href="mailto:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> dwagner</a> <pre>(In reply to Harry Wentland from <a href="show_bug.cgi?id=102820#c19">comment #19</a>) > Created <a href="attachment.cgi?id=137476" name="attach_137476" title="drm/amd/display: Default HDMI6G support to true. Log VBIOS table error.">attachment 137476</a> <a href="attachment.cgi?id=137476&action=edit" title="drm/amd/display: Default HDMI6G support to true. Log VBIOS table error.">[details]</a> <a href='page.cgi?id=splinter.html&bug=102820&attachment=137476'>[review]</a> [review] > drm/amd/display: Default HDMI6G support to true. Log VBIOS table error. > > Can you see if this helps? Our Windows driver definitely checks the HDMI6G > flag from VBIOS but it will default to allow 6G on HDMI if the VBIOS check > fails. > > This patch is porting the same behavior in the hopes that it will help with > your issue. I had to change "ctx->logger" into "enc110->base.ctx->logger" to make your patch compile (applied on today's head of amd-staging-drm-next). Yes, that patch changes the behaviour for the better: HDMI 2.0 modes - especially 4k@60Hz work fine with this patch applied on my system. Tried multiple reboots, result was consistent. > If this patch works a dmesg log with the amdgpu.dc_log=1 option on the > kernel would help us understand the root cause a bit better. I did enable amdgpu.dc_log=1 on the kernel command line - but there is no "Failed to get encoder_cap_info from VBIOS..." message visible in dmesg, which makes me wonder what makes the new code path differ from the old one. (Attaching dmesg output below.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>