<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#c8">Comment # 8</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 Alex Deucher from <a href="show_bug.cgi?id=102820#c7">comment #7</a>) > I think it blocks modes that require 6Ghz timings if the platform isn't > validated for them. What does "platform isn't validated for 6Ghz timings" mean? Both the RX 460 and the 4k TV I use are officially advertised as supporting 4k @ 60Hz, and indeed they work just fine in that mode if commit ebbf7337e2daacacef3e01114e6be68a2a4f11b4 is not part of the kernel. > Does everything work correctly if you remove the modes > from your monitor section? Removing the (not really used) ModeLine statements from the X11 config does in fact change the symptoms when commit ebbf7337e2daacacef3e01114e6be68a2a4f11b4 is present: X11 will start then, but only to use what xrandr says to be a "3840x2160 @ 30Hz" mode, but which the display picks up as some not-really-filling-the-whole-screen signal, with black borders on both sides (so an image is shown but compressed horizontally - in the usually active "just scan" mode and also even if the display is manually forced to a 16:9 aspect ratio).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>