Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add support for AMD Ryzen Z1 Extreme #13

Open
Dr1fte opened this issue Oct 29, 2024 · 2 comments
Open

Please add support for AMD Ryzen Z1 Extreme #13

Dr1fte opened this issue Oct 29, 2024 · 2 comments
Assignees

Comments

@Dr1fte
Copy link

Dr1fte commented Oct 29, 2024

When changing the p-state from 100.0000 to 104.5. It shows in zen timings that the KClk and Bclk has synced with the setting applied. However, during testing on both p-state settings. 100.0000 always yields the same results as 104.5. This is in cinebench r15.
IMG_3710
IMG_3709

the system can crash if the p-state is set higher to example - 104.75. But it’s not consistently crashing. Which signifies that the change is taking place. But I have no idea where. As adjusting the p-state clock. Should result in better performance.

@Dr1fte
Copy link
Author

Dr1fte commented Oct 29, 2024

Z1-extreme rog ally - testing the program setting bclk to 106 causes instant crash. It runs stable at 104.5. Consistently causes lower performance in graphical benchmarks. Shows no improvement or reduction in memory tests (even if zen timings says that clocks have changed) and shows no improvement or slowdown in CPU only benchmarks both in single and multithreaded scenarios. Is it possible that it doesnt apply the BCLK properly?

@irusanov
Copy link
Owner

irusanov commented Nov 3, 2024

On my lenovo laptop, going over a certain bclk slows it down. I can't tell if the bclk option does something on the Z1 as I don't have the device. Have you tried testing at 101.5 - 102?
I think the better option would be to set curve optimizer values if that is even allowd on that device, it would get better results than adjusting bclk, which is a bad idea on these locked chips.
Have you checked if cpuz detects the higher bclk?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants