<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93826#c63">Comment # 63</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93826">bug 93826</a>
from <span class="vcard"><a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to iuno from <a href="show_bug.cgi?id=93826#c62">comment #62</a>)
<span class="quote">> It works for me, too, but I already said that ;-)
>
> However, the problem Pavel describes is another bothersome issue. PowerPlay
> changes to the higher memory DPM state which results in ~40 Watts (Hawaii;
> estimated from memory, have to measure and confirm again) more power draw.
> The higher DPM state is required, otherwise the flickering appears.
> On Windows, this isn't the case and WQHD at 144 Hz works with the low memory
> clock. I assume they raise the voltage independently to the clock in that
> case to maintain stability.</span >
Are you forcing the power state to high? The mclk shouldn't be affected by the
display clock.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>