You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When this repository's fix is implemented on the AMD version of the Acer Predator Helios 500 and the power cable is unplugged, pp_dpm_mclk does not fall lower than level 2, but pp_dpm_sclk falls all the way down to level 0. As such, it is still possible for the DPM bug affecting this laptop (that this repository attempts to work around) to occur, even with the fix. I have confirmed that amdgpu.ppfeaturemask=0xffff7fff is a part of the Grub entry on boot (I have also tried amdgpu.ppfeaturemask=0xfffd7fff for good measure), and I have confirmed that the script has successfullt run via sudo systemctl status acfix.
A more effective (but far less ideal) way of working around the DPM bug that has worked for me was to include amdgpu.dpm=0 in the Grub entry; this works around the bug by disabling DPM entirely rather than just the clock levels that trigger the bug in question. With that being said, this bug report has been based on behavior observed withoutamdgpu.dpm=0 being present in the Grub entry (I temporarily edited the Grub entry at boot time to remove this parameter; boots performed in this fashion consistently reproduced this issue).
The text was updated successfully, but these errors were encountered:
When this repository's fix is implemented on the AMD version of the Acer Predator Helios 500 and the power cable is unplugged,
pp_dpm_mclk
does not fall lower than level 2, butpp_dpm_sclk
falls all the way down to level 0. As such, it is still possible for the DPM bug affecting this laptop (that this repository attempts to work around) to occur, even with the fix. I have confirmed thatamdgpu.ppfeaturemask=0xffff7fff
is a part of the Grub entry on boot (I have also triedamdgpu.ppfeaturemask=0xfffd7fff
for good measure), and I have confirmed that the script has successfullt run viasudo systemctl status acfix
.A more effective (but far less ideal) way of working around the DPM bug that has worked for me was to include
amdgpu.dpm=0
in the Grub entry; this works around the bug by disabling DPM entirely rather than just the clock levels that trigger the bug in question. With that being said, this bug report has been based on behavior observed withoutamdgpu.dpm=0
being present in the Grub entry (I temporarily edited the Grub entry at boot time to remove this parameter; boots performed in this fashion consistently reproduced this issue).The text was updated successfully, but these errors were encountered: