Closed sieskei closed 1 month ago
Hi. 16 is the default value of the macOS drivers; it was copied from them.
Hi. 16 is the default value of the macOS drivers; it was copied from them.
I understand. After you mentioned it, I realized exactly what I was comparing. In your case (kext), it's in decimal 16, and IORegistryExplorer shows 0x10 (hex), which is exactly 16. I apologize.
Before closing the ticket, could I ask two more questions?
Do I need to set DeviceProperties PP_PhmSoftPowerPlayTable for PP_WorkLoadPolicyMask to work correctly?
Are these the allowed values for PP_WorkLoadPolicyMask?
@sieskei All the listings of valid values online are incorrect, even WhateverGreen. NootRX does not support setting values with DeviceProperties, modify the kext itself.
@sieskei All the listings of valid values online are incorrect, even WhateverGreen. NootRX does not support setting values with DeviceProperties, modify the kext itself.
For me, manually changing it is not a problem. The question is - I don't know which values are valid. :) Although 16 (0x10) is the correct value, there is an annoying coil whine on both video cards, and I'm wondering what else to set.
Duplicate of #36
macOS Version
Sonoma
What is your CPU's model?
i9-11900KB
What is your GPU's model?
RX 6650 XT
Please describe the behaviour in detail.
Hello, first I want to congratulate you on the good work and effort you've put in.
I have two hackintoshes (NUC 11 Extreme) with GPUs 6650XT and 6800XT. Everything works fine, but PP_WorkLoadPolicyMask on both GPUs has a value of 10 and they have an annoying coil whine. I noticed that in the plist file a value of 16 is set for the controllers, but it fails to set.
I changed it to 1 (default) and it works. I also tried with 4 (powersaving), and it also works.
I actually solved the problem, I just wanted to share that the value 16 (which I don't know what it means) fails to set.
Regards, Miro
What should've happened instead?
Maybe it should be set to 1 by default?
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
No response
Bug report submission terms