Hi, can you please post your settings for oc? I have the same cpu. What is your Corona 1.3 bench?
This bug belongs to bios, rome es cpu does not matter, I use the official version of epyc 7702 also to need this stepOh yes that's right. I forgot to mention that there are a couple of bios settings that need to be set on the DSI for the ZS cpu's, it's finicky. So turn on IOMMU and disable Above 4G decoding and it should work
I use the default 64c scheme, and the frequency is changed to 3.2g，The time is 11.58 secondsHi, can you please post your settings for oc? I have the same cpu. What is your Corona 1.3 bench?
That's right, the original R20 running score can be increased from 31000 to 33000.This is for dual system? So you used preset 64-core Best of both and that`s it?
Does copying the second half of the bios into the bios of H11DSI0.221_D32 work?
This was the command I used for the overclock
sudo ./zenstates.py --no-gui --oc-frequency=3400
I can't change the bios myself, and I need the source code. I can contact ASRock manufacturers, they will help me modify the bios to support es.I am trying to understand the specific order that I need to follow in order to at least get my cpu to post. The cpu that I am trying to get to post (I haven't been successful yet) is the 2S1404E2VJUG5 (64-core). The mb that is the guinea pig is the sm h11ssl-nc rev 1.01. I have a naples ES cpu that does boot with that mb. I am assuming that I would need to boot with the naples cpu to be able to make sure the current bios has an Agesa < 220.127.116.11. Not sure where to check that but when I put humpty dumpty back together (currently server parts are everywhere except where they should be!) I can boot into the bios and look around for the Agesa version. If the Ageas version is ok, I think I then need to load one of your custom bios. the bios that I think I need to load is Rome_H11SSLI_Rev1. You mention "The only thing you need to do is copy the second half of the bios (the Rome part) and duplicate it on Rev. 2 boards or just upload that on Rev. 1 boards." I am not clear as to what I need to do. What do you mean by copy the second half of the bios? I was thinking that I would load the whole file (Rome_H11SSLI_Rev1) just like I would a normal bios from sm. After I sort that out and load some new bios, I am assuming my naples cpu would no longer post on that mb. I would then swap the naples cpu with the ES rome cpu and see if the bad boy boots! After that, I would need to boot that server with windows and run your overclocking sw to try and optimize. If that is successful, could I run vmware on that server and still retain the overclocking? Thanks for any pointers and for all of the hard work you have done over the past year trying to get these lost soul cpus working again!
Thanks. I am assuming when they mention < 18.104.22.168, they are talking about the Rome agesa version? the release notes for my bios (rev 1.1 mb) is on a different track. so if my bios release notes shows:you can get agesa version from release notes of the latest bios. they mention always the changes made by each bios release
I can't change the bios myself, and I need the source code. I can contact ASRock manufacturers, they will help me modify the bios to support es.
I was wondering if there was a different track for the naples cpu vs the rome cpu with regards to the agesa version. ex. for the rev 2 mb, they use a different bios that I thought was relevant to the requirement for agesa to be < 22.214.171.124 but for the rev 1.1 mb, they use a much older bios that only refers to naples. the bios for the rev 1.1 board starts with 1.0b but the bios for the rev 2 mb starts with 2.0a. their agesa seems to be related to the generation of the amd cpu (either naples or rome.) So when you reference the requirement for the agesa to be <126.96.36.199, is this referring to the rome agesa version or both the naples and rome?this higher agesa version than 1.0.03