https://bugs.freedesktop.org/show_bug.cgi?id=111762
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111762
Alex Deucher changed:
What|Removed |Added
Severity|normal |enhancement
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #15 from Alex Deucher ---
pp_od_clk_voltage isn't implemented yet for navi. There are patches on the
mailing list:
https://patchwork.freedesktop.org/series/69152/
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #14 from Alex Deucher ---
(In reply to tempel.julian from comment #13)
> It might be that, just not in hex. E.g. VddcLookupTable entry 1 returns a
> Vdd of 65282.
Correct. 65282 is 0xff02 which is a virtual voltage id. The driver
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #13 from tempel.jul...@gmail.com ---
It might be that, just not in hex. E.g. VddcLookupTable entry 1 returns a Vdd
of 65282.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #12 from Alex Deucher ---
(In reply to tempel.julian from comment #11)
> It was just a bit inconvenient that for my Polaris card the Vdds were
> defined as garbage values when parsing the default pp_table. Though
> specifying custom
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #11 from tempel.jul...@gmail.com ---
That really looks suspicious.
Looks like the issue of voltage resetting itself to default I mentioned earlier
when using custom power play stables might not apply to Navi:
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #10 from zamundaa...@gmail.com ---
I'm already using ppfeaturemask=0xfffd7fff, it doesn't unlock anything - or at
least CoreCtrl doesn't show anything.
In the journald log I see a lot of these lines, always grouped together:
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #9 from tempel.jul...@gmail.com ---
Thank you, I'll try it out at some point.
I also got an email by fin4478 with the suggestion to try out
amdgpu.ppfeaturemask=0xfffd7fff.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #8 from Matt Coffin ---
(In reply to Matt Coffin from comment #7)
> This patch should take care of the problem by treating navi10's TDPODLimit
> the same as vega20 does: https://patchwork.freedesktop.org/series/69090/
Sorry for the
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #7 from Matt Coffin ---
This patch should take care of the problem by treating navi10's TDPODLimit the
same as vega20 does: https://patchwork.freedesktop.org/series/69090/
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #6 from tempel.jul...@gmail.com ---
Tested custom soft power play table via UPP on Polaris and it generally seems
to work well (might be able to test Navi at a later time).
However, there is the issue that the voltage gets reset
https://bugs.freedesktop.org/show_bug.cgi?id=111762
L.S.S. changed:
What|Removed |Added
CC||ragnaros39...@yandex.com
--- Comment #5 from
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #4 from tempel.jul...@gmail.com ---
Thanks for the hint @ Andrew Sheldon, SPPT being possible on Linux totally
passed me by. Will test it with my cheap Polaris card first, which made me
stick with custom fan curve anyway.
Regarding
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #3 from zamundaa...@gmail.com ---
I have the same (or at least a similar) bug.
/sys/class/drm/card1/device/hwmon/hwmon3/power1_cap_max in my case gives the
default 220W (value: 22000).
$ cat
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #2 from Andrew Sheldon ---
As a workaround, use upp instead as a workaround (write to the powerplay binary
directly). See: https://github.com/sibradzic/upp
I suggest using 5.4-rcX as AMD's wip kernels (amd-staging-drm-next and
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #1 from tempel.jul...@gmail.com ---
Still happens with current 5.5-wip/drm-next kernels.
I don't know if it is supposed to be implemented, but there seems to be some
bug apart from that:
Just reading sysfs entries at
https://bugs.freedesktop.org/show_bug.cgi?id=111762
Bug ID: 111762
Summary: RX 5700 XT Navi - amdgpu.ppfeaturemask=0x
causes stuttering and does not unlock
clock/voltage/power controls
Product: DRI
18 matches
Mail list logo
