<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Graphical corruption with PSR - affects Plymouth only" href="https://bugs.freedesktop.org/show_bug.cgi?id=107966#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Graphical corruption with PSR - affects Plymouth only" href="https://bugs.freedesktop.org/show_bug.cgi?id=107966">bug 107966</a> from <a class="email" href="mailto:tseewald@gmail.com" title="Tom Seewald <tseewald@gmail.com>"> Tom Seewald</a> <pre>(In reply to Dhinakaran Pandiyan from <a href="show_bug.cgi?id=107966#c18">comment #18</a>) A quick > way to verify would be to check i915_edp_psr_status or dmesg with > drm.debug=14 at Plymouth's login. And compare this to a boot without > i915.fastboot=1. Can you please attach dmesg for the both test cases? What is the best way/is it possible to capture dmesg and check /sys/kernel/debug/dri/ values at the Plymouth LUKS prompt? This is relatively early in the boot process, before I have entered in the decryption password for my drive. I have verified however, that after the boot process has completed psr appears to be enabled both with fastboot on and off. > Btw, you shouldn't be needing i915.enable_psr=1 on drm-tip. PSR should be > enabled by default on a KBL refresh. Thanks, I can confirm that on drm-tip without explicitly setting i915.enable_psr=1 I have graphical corruption while typing in my LUKS password at the plymouth prompt.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>