I didn't received yet and I plan to mount it in january
I didn't received yet and I plan to mount it in january
https://developer.amd.com/wp-content/resources/55803_0.54-PUB.pdfHello!
I've updated the ZenStates app with Rome CPUID, however I haven't figured out the P-States (or manual overclock) yet.
There is no BKDG for family 17h and setting the well-known P-State MSRs doesn't change the CPU frequency. I have no access to NDA stuff.
If I set the P-State, then read it back it shows the newly set multiplier, but the actual frequency is still the old one. Same with the Linux script.
So I'm currently scratching my head over this.
It would help if you report that at least it detects the CPU correctly.
Performance Bias options "might" work, perhaps some of the others, but not P-State
I'm not even sure if the MSR are shared between Matisse and Rome.
Hopefully it won't "break" your system, but apparently I have no way to test.
EPYC1 shared the CPUID with desktop parts, but now Rome has a new CPUID.
Download zip from my github releases page: irusanov/ZenStates
Changelog:
- Added Rome support (P-States won't work, but at least it should start without complaining about unsupported CPU)
- Added support for 32-bit OS (tested on XP SP3 x86)
- Reduced .NET Framework version to 4.0 (lowest I can go for the current codebase)
Update 21 Aug:
I have managed to change the frequency with commands to SMU. Unfortunately there's no public document describing all commands. I've updated the readme with what I've been able to find so far mostly by trial and error method. Should be able to provide at least manual overclock soon.
irusanov/ZenStates
i tried zenstate and only cpu1 is affected, the second cpu is not.
I have a H11DSI-NT with 7601 (2 cpu).
Anything i can do?
Hello
So about multiple CPUs configuration you just need to start AsusZenstates as usual,click on apply in order to apply your custom pstates settings to CPU0.
-Once is done go in task manager,find AsusZsSrv.exe (not AsusZenStates.exe) then click on define affinity.
-After you'll change Group 0 to group 1,check "use all core" and click Ok.
-Now you're able to modify the CPU1 pstates by clicking on apply in AsusZenstates app.
In order to revert to CPU0 just change group 0 and don't forget to check "use all core" in define affinity .
Each time you reboot the computer you'll need to apply this process.
If you get an "access denied" error when you want to change the cpu affinity just kill the process and restart it .
I also contacted supermicro in order to ask for a custom bios but they didn't approve my request unless you pay at least 500 motherboard/BIOS...
Imgur
I hope everything is clear for you
Thank you
I added the procedure to the start post.i tried zenstate and only cpu1 is affected, the second cpu is not.
I have a H11DSI-NT with 7601 (2 cpu).
Anything i can do?
It's untested, we don't know if Rome custom pstates or custom cpb settings works, and about zenstates, it still hasn't be updated for Rome if I'm rightSo, to summarize, do we have overclocking support on Rome now? With the zenstates application or only with a modded bios?
AMD Epyc Rome is in someway unlocked as far as i know. The Bios Mod P-States will most likely not work and Zenstates does not have Zen2 Support yet. I think i have everything to implement Zen2 support but infared/irusanov seems to have taken some time of from this project and the forums.So, to summarize, do we have overclocking support on Rome now? With the zenstates application or only with a modded bios?
In the video i posted we have a guy claiming it's possbile and so is the word in the street.Has anyone managed to overclock a Zen2 EPYC (7xx2) in any motherboard?
I think some of the CBS options won't work because these are leftovers meant for TR3. They're labled SSP (starship) and Rome is VH (valhalla). But as i said from the start bios P-states will not work.I have made some progress with the EPYCD8 board.
Memory OC works fine. I settled for 3200 and tightened timings because 3200 is officially supported by the CPU and the board. The test BIOS v2.42 removes higher settings so I haven't tried going higher. BIOS v2.30 goes all the way up to 4200 IIRC.
P states are completely ignored.
Boost Fmax is completely ignored.
TDP limit is NOT ignored, and this lead to a finding that may sink the OC potential - as far as I can tell, this board is limited to 200W. Bumping the TDP form "auto" (180W) to 200W bumps the full load all-core boost from about 3000 to 3125, but going further makes no difference. The problem being that with P states ignored - preventing undervolting, and TDP limited to 200W, scope for OC is effectively non-existent because the TDP limit even prevents hitting the maximum boost clocks under full load on all cores.
Another observation - MCH counts toward the TDP. Going from 2933 memory speed to 3200 reduced boost clocks under full load. So there is a tradeoff to be chosen between memory bandwidth and boost clocks.
Ooooh, so that's what happened to Valhalla: it became Epyc!I think some of the CBS options won't work because these are leftovers meant for TR3. They're labled SSP (starship) and Rome is VH (valhalla). But as i said from the start bios P-states will not work.
You could just hook up a IR i2c dongle and bring your TDP back in place. Would also be interesting how that's handled by the SMU, since it looses control over anything the voltage controller does.
I might be able to mod your newer bios so you can use the higher memory OC options with the newer version, if there's any need for that.
Valhalla became Rome and Starship became Castle Peak. And the rest of the codenames probabaly won't even make sense to the insiders.Ooooh, so that's what happened to Valhalla: it became Epyc!
@topic: Imagine EVGA (or some other madman brand) coming out with a SR-4 dual SP3r2 board with insane VRMs, holy shit. 128 cores at 4 GHz plus will make minced meat of every workload!
I'm not sure there is much point. Even going to 3200 from 2933 has impacted the TDP enough to reduce the boost slightly under full load. And there is only about an extra 10% I could get out of the timings, so 3600 would just turn into a massive time sink for questionable benefit.I might be able to mod your newer bios so you can use the higher memory OC options with the newer version, if there's any need for that.
You really need to stop fanboying EVGA. Having had two SR-2 motherboards, I can very confidently say they were the most garbage grade board I have ever had the misfortune of owning. There were so many firmware bugs and hardware design faults it wasn't even funny. It was unfit for purpose. Off the top of my head:Ooooh, so that's what happened to Valhalla: it became Epyc!
@topic: Imagine EVGA (or some other madman brand) coming out with a SR-4 dual SP3r2 board with insane VRMs, holy shit. 128 cores at 4 GHz plus will make minced meat of every workload!
Why shouldn't they?Hello, all I have a question, Why should anyone overlock their AMD?
There is actually only one pro for overclocking: performance. It’s why gamers and PC enthusiasts overclock a CPU and a GPU (graphics processor unit). When you send more voltage to either the CPU or GPU, the graphics increase, response times within applications are reduced, and benchmarks can identify peak performance for complex software.Why shouldn't they?
Having spent the last 25 years working with computers and electronics all day every day, I can honestly say that I have _never_ seen a single instance of ASIC failure due to OC-ing. Once it is dialled in and stable, an OC-ed system will go on for decades, until something happens that would kill it regardless of OC (dust clogging resulting in massive overheating, PSU failure, or something along those lines).The biggest issue with overclocking is the reduction in a component’s lifespan. You can overclock a CPU, GPU, motherboard or RAM, but sending increased volts gradually damages these components. Damage is caused by heat generated from increased power. Additional heat doesn’t usually ruin a circuit immediately, so the damage is seen gradually over time.