https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #11 from Alex Deucher ---
(In reply to alvarex from comment #10)
> check here
> https://wiki.archlinux.org/index.php/AMDGPU#Overclocking
>
> and it's documented on the kernel source
The arch wiki has some errors in it as well. He
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #10 from alvarex ---
check here
https://wiki.archlinux.org/index.php/AMDGPU#Overclocking
and it's documented on the kernel source
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=106177
alvarex changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #8 from alvarex ---
same effect as Christoph Haag mentions echoing pp_dpm_mclk and pp_mclk_od
reports nothing changed.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #7 from alvarex ---
I can confirm this behaviour with kernel 4.16 and point release 16 and 18 it
works as I would expect, with kernel 4.17, 4.18.14 and 4.19 from drm fixes git
it doesn't work. Setting feature mask have no effect.
Po
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #6 from Christoph Haag ---
I have not tried amdgpu.ppfeaturemask=0x etc. yet.
If a behavior change like that is intended, there should be some easily
accessible documentation about it somewhere.
1288 MHz (SCLK) is the factor
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #5 from Alex Deucher ---
Please use debugfs (e.g., /sys/kernel/debug/dri/0/amdgpu_pm_info) to check the
current clocks.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #4 from tempel.jul...@gmail.com ---
I'm on a RX 560.
I can confirm that with 4.17, behavior has quite changed a lot. I don't think
it's buggy for Polaris, but not documented correctly.
To make values "stick" in pp_sclk_od, you have t
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #3 from gr...@sub.red ---
At least I had the same behaviour, value not "sticky" and no impact on actual
clock.
I noticed it when I tested 4.17-rc2, actually wanted to test the "wattman"
functionality. Then noticed, it doesn't work on
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #2 from Christoph Haag ---
I just tried 4.16.7 and overclocking still works on the 4.16 version.
And I think on 4.17rc3 it still doesn't work.
Do you mean on 4.16.6 overclocking does not work for you? Then it's probably
not the same
https://bugs.freedesktop.org/show_bug.cgi?id=106177
gr...@sub.red changed:
What|Removed |Added
CC||gr...@sub.red
--- Comment #1 from gr...@
https://bugs.freedesktop.org/show_bug.cgi?id=106177
Bug ID: 106177
Summary: overclocking doesn't work with 4.17-rc1
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
12 matches
Mail list logo