From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111482] Sapphire Pulse RX 5700 XT power consumption
Date: Tue, 10 Sep 2019 19:27:43 +0000 [thread overview]
Message-ID: <bug-111482-502-0kOb17IuTR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111482-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2990 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111482
--- Comment #17 from Robert <freedesktop@postfach.xyz> ---
Thanks Andrew! I played around a little bit with the refresh rates. Between
40-60Hz there is no difference in idle power consumption. The mem clock stays
at 875Mhz and can't be changed.
The best refresh rate with 8W idle power consumption I could get was at 39Hz:
cvt12 5120 1440 39 -b
xrandr --output DisplayPort-2 --newmode "5120x1440_39.00_rb2" 297.51 5120 5128
5160 5200 1440 1453 1461 1467 +hsync -vsync
xrandr --output DisplayPort-2 --addmode DisplayPort-2 "5120x1440_39.00_rb2"
xrandr --output DisplayPort-2 --mode "5120x1440_39.00_rb2"
This causes the mem clock to go up to 625Mhz at first but it can be switched
back to 100Mhz with
echo "0" > /sys/class/drm/card0/device/pp_dpm_mclk
Regarding my statement when using 30Hz in the last comment:
"""
It basically works but moving windows a little bit faster or moving the mouse
pointer around looks "interesting".
"""
For this "flickering" that I saw and which was quite annoying I found a
workaround :-) It looked like something didn't refresh fast enough. So I
thought playing around with some frequencies would be a good idea... And the
mem clock was the obvious one to start with. So I was setting the mem clock to
500Mhz with
echo "1" > /sys/class/drm/card0/device/pp_dpm_mclk
Then the "flickering" went away :-) But of course that brought idle power
consumption to 24W. So just for fun I switched back to 100Mhz with
echo "0" > /sys/class/drm/card0/device/pp_dpm_mclk
Funny enough the "flickering" stayed away :-))) So for now after I start KDE
plasma I enter Konsole and execute
echo "1" > /sys/class/drm/card0/device/pp_dpm_mclk
echo "0" > /sys/class/drm/card0/device/pp_dpm_mclk
and be happy :D
One final observation: I tried out kernel 5.3-rc8. With that kernel there is no
way to reduce idle power consumption. It stays at 34W regardless what you do.
But with this tag
https://cgit.freedesktop.org/~agd5f/linux/tag/?h=drm-next-5.4-2019-08-30 (which
basically is kernel 5.3-rc3 with the Navi10 patches for kernel 5.4 - if I got
it right ;-) ) idle power consumption is as expected.
So my whole issue basically comes down to this: If you have a resolution of
5120x1440 and a refresh rate of > 39Hz your idle power consumption stays at max
and there is (at least until now) nothing you can do about it. So if I had used
a lower resolution or a smaller screen I wouldn't have had an issue at all ;-)
S... happens :D
But anyways: Thanks so much for your help and also to Ilia! I'm now happy with
my setup so far. It would be very interesting if there is really some kind of a
cap with 5120x1444@39Hz or if this this "only" a firmware problem, a driver
problem, a config error or something completely different. Maybe we'll find out
in our next lives :D
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4030 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-10 19:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 8:43 [Bug 111482] Sapphire Pulse RX 5700 XT power consumption bugzilla-daemon
2019-08-26 23:07 ` bugzilla-daemon
2019-08-27 4:47 ` bugzilla-daemon
2019-08-27 7:25 ` bugzilla-daemon
2019-08-27 22:20 ` bugzilla-daemon
2019-08-28 14:25 ` bugzilla-daemon
2019-08-29 16:27 ` bugzilla-daemon
2019-09-03 9:35 ` bugzilla-daemon
2019-09-03 16:54 ` bugzilla-daemon
2019-09-04 1:16 ` bugzilla-daemon
2019-09-04 22:16 ` bugzilla-daemon
2019-09-05 1:01 ` bugzilla-daemon
2019-09-05 2:20 ` bugzilla-daemon
2019-09-05 14:21 ` bugzilla-daemon
2019-09-05 14:24 ` bugzilla-daemon
2019-09-05 14:53 ` bugzilla-daemon
2019-09-05 18:16 ` bugzilla-daemon
2019-09-08 2:02 ` bugzilla-daemon
2019-09-10 19:27 ` bugzilla-daemon [this message]
2019-09-27 10:49 ` bugzilla-daemon
2019-09-27 10:51 ` bugzilla-daemon
2019-09-28 7:38 ` bugzilla-daemon
2019-09-28 9:05 ` bugzilla-daemon
2019-09-28 10:14 ` bugzilla-daemon
2019-10-05 11:55 ` bugzilla-daemon
2019-10-05 12:20 ` bugzilla-daemon
2019-10-06 4:45 ` bugzilla-daemon
2019-10-07 8:31 ` bugzilla-daemon
2019-10-07 10:05 ` bugzilla-daemon
2019-10-26 8:33 ` bugzilla-daemon
2019-11-01 3:01 ` bugzilla-daemon
2019-11-02 4:22 ` bugzilla-daemon
2019-11-03 16:55 ` bugzilla-daemon
2019-11-04 16:31 ` bugzilla-daemon
2019-11-04 16:42 ` bugzilla-daemon
2019-11-04 23:48 ` bugzilla-daemon
2019-11-05 0:37 ` bugzilla-daemon
2019-11-05 0:43 ` bugzilla-daemon
2019-11-05 0:50 ` bugzilla-daemon
2019-11-05 5:57 ` bugzilla-daemon
2019-11-08 1:35 ` bugzilla-daemon
2019-11-08 1:36 ` bugzilla-daemon
2019-11-08 6:36 ` bugzilla-daemon
2019-11-19 9:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111482-502-0kOb17IuTR@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox