Slimmed down CLI version?

[sp00n]

So far I've been using PBO2 Tuner resp. "pbodebug" from PJVol to set the Curve Optimizer values while running the CoreCycler script, however PJVol mentioned that he has stopped developing his tools, and they don't support Ryzen 8000 and 9000 yet, and so probably never will.

Which makes me wonder, would it be possible to create a stripped down version of SMUDebugTool that let's you only set the Curve Optimizer values using the command line, which I could then use as a replacement to support the newer Ryzen generations as well?

As far as I can tell the tool right now doesn't support any CLI commands, but I also don't have that great experience with C programs, so I might have missed something.

[irusanov]

Hi,
This debug tool is mostly a spaghetti code app, but I had the idea to restart zenstates (completely new app) development which would support PBO and also CLI, or extract the PBO functionality in a new "Tuner", but this means yet another app to support. This is more of a wishful thinking at the moment. I can quickly code a PBO-only app, but people will expect some sort of a support afterwards.

You're right, the debug tool does not support CLI.

[rawhide-kobayashi]

I'm working on a CLI for the capabilities presented by ZenStates-Core.

Setting CO values is supported, and that's the only thing currently supported... But it is supported.

https://github.com/rawhide-kobayashi/ryzen-smu-cli

[irusanov]

@rawhide-kobayashi Cool! The current implementation of the core disable map only supports up to 2 CCDs and the code you see in the debug tool is, most often than not, a quick patch that I plan to "fix" later, but never do. In theory the array can be extended and the logic changed so it supports more CCDs, but I've never had a server hardware to actually test anything. On a multi-processor systems I would need to account for the fact that the other processors would run on a different bus and the current code only supports bus 0.

PS: The current situation with the WinRing0 driver is not making it any easier to continue with the projects. I was ready to halt the development completely, but didn't manage to announce it quick enough before the next Windows update "reverted" it for now. Hopefully we'll get a new secure driver which projects like this would be able to use in the future.

[rawhide-kobayashi]

I see. Thank you. If I ever get my hands on a threadripper or epyc system that supports PBO, I'll certainly give it a try myself...

I haven't had any issues using winring0 from local disks, but in the last week my windows systems have started to refuse to run it from network shares. I didn't change anything. Thanks Microsoft!