have not found any UEFI bitmap entry in the rome section. there is only core controlI believe i can disable that core in bios with core bitmap?
have not found any UEFI bitmap entry in the rome section. there is only core controlI believe i can disable that core in bios with core bitmap?
core bitmap definitely works, i was able to change core count from 12 to 16, playing with the values in core bitmap section. Just cant get it how it works in tandem with CCD Control option. There's 3 CCD Control menushave not found any UEFI bitmap entry in the rome section. there is only core control
can confirm 1.01 dosnt start at all on 20h2@ExecutableFix RomeOverclocker 1.0.1 on githab crashes on 1809 and does not start at all on fresh install of 20H2 .. But 1.0 version works ok
could someone check that
Hi,Linux tools can be modified, however I'm working on a better detection, since Epyc and Desktop Threadripper 3000 series (Castle Peak) share the same basic cpuid, so another more complicated detection mechanism should be implemented - at least socket type detection is needed.
If you want, you can try the modified code, however for now it works on Epyc or on TR - not on both at the same time, since command IDs are different.
Attached is the modified version of my Zenstates-Linux fork: irusanov/ZenStates-Linux
It had been tested on a ES Epyc and it worked, but this version is unofficial until I sort out the cpu detection. Ofcourse, as always, everyone is free to contribute.
You can first try to set a different frequency and if it works, proceed following the guide and mess with rest of the things. For the test, please use the CLI, then you can use the GUI as well.
Frequency works in 25MHz steps.Code:sudo ./zenstates.py --no-gui --oc-frequency=2000
Be extremely careful with voltage. Make sure you have something to monitor it with - preferably a multimeter to check the actual voltage. Zenmonitor seems to be the best currently available on Linux, but I'm not sure if it displays correct info on Epyc: ocerman/zenmonitor
MD5: 0c2fe08b1dd06bfb29f834206d95ba18
isOcFreqSupported = False
cpu_sockets = int(os.popen('cat /proc/cpuinfo | grep "physical id" | sort -u | wc -l').read())
def writesmureg(reg, value=0):
os.popen('setpci -v -s 0:0.0 b8.l={:08X}'.format(reg)).read()
os.popen('setpci -v -s 0:0.0 bc.l={:08X}'.format(value)).read()
if cpu_sockets == 2:
print("Writesmureg, two sockets")
os.popen('setpci -v -s A0:0.0 b8.l={:08X}'.format(reg)).read()
os.popen('setpci -v -s A0:0.0 bc.l={:08X}'.format(value)).read()
def readsmureg(reg):
os.popen('setpci -v -s 0:0.0 b8.l={:08X}'.format(reg)).read()
output = os.popen('setpci -v -s 0:0.0 bc.l').read()
if cpu_sockets == 2:
print("Readsmureg, two sockets")
os.popen('setpci -v -s A0:0.0 b8.l={:08X}'.format(reg)).read()
os.popen('setpci -v -s A0:0.0 bc.l').read()
return hex(output[-9:][0:8])
Based on @ExecutableFix's open source Windows tool, I modified @I.nfraR.ed's ZenStates for Rome ES on Linux and added a few missing features. My version comes with these improvements:
1. Read/Write PCI config space directly in Python instead of using setpci. I found that setpci sometimes does not work reliably (probably due to race conditions), and in one occasion it wrote a wrong VID (0x0, =1.55V) that almost killed my CPUs.
2. Dual socket support.
3. Implement some missing features, including frequency lock/unlock and reverting to default voltage/frequency.
4. Add a few preset scripts (e.g., see preset_multicore.sh) that work well on my H11DSi with dual ZS1406E2VJUG5 (untested on other systems, so you may need to adjust them for your use case).
Here is my modified ZenStates on Linux. Note that I only used/tested the CLI on a headless server and I did not use the GUI.
That's incorrect, you can boot many (if not all) systems with just one cpu installed. The second cpu is required to access all memory and pcie slots.dual socket boards need both cpu's populated to post
Can the ES/QS Rome CPUs be used in a single configuration on a dual board?
No, unfortunately not as with all the engineering samples
They will work on dual socket motherboards if they're installed with two sockets populated, not if only one is populated. This holds true for both Naples and Rome engineering samples
These aren't just any old CPUs...That's incorrect, you can boot many (if not all) systems with just one cpu installed. The second cpu is required to access all memory and pcie slots.
(Check the mainboards/systems block diagram to see what won't work if just one cpu is installed)
Do you have more info on this?Do you know if putting these in a Dell server causes them to become locked to Dell platforms? I had heard rumors that Dells blow the security fuses on the first boot.
Only selling by auction on eBay or selling here as well? Could you DM prices for a pair of 64c rome and a single 32c rome? ThanksI am selling some ROME ES chips
I have tested these on a DELL R7515 and can confirm they work.
I have 6 units to sell.
Please contact me if interested.
Do you know if putting these in a Dell server causes them to become locked to Dell platforms? I had heard rumors that Dells blow the security fuses on the first boot.
I think these CPU's are vendor locked to DELL because I could only get them to boot on DELL systems. That makes me mad at AMD for allowing this.
I think these CPU's are vendor locked to DELL because I could only get them to boot on DELL systems. That makes me mad at AMD for allowing this.
I have 4x 32 core CPUs remaining and will sell them for $400/ea + shipping. DM me if you are interested.
A compatible DELL system is USD $1679. Dell EMC PowerEdge R7515 Rack Server | Dell USA
I have the downgrade firmware and can share it.
These chips could be good for that.