Finally: Overclocking EPYC Rome ES

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
D

dragonian

Member
Jan 3, 2020
47
30
18
I have 2 H11SSL-i v2 boards running with ZS1711E3VIVG5 (Rome ES 32c) cpus

I was able to update the IPMI to the latest with the older Rome BIOS 32MB (on the 1st page of this thread) I unchecked all of the "preserve" boxes -- I believe this is important.

Firmware Revision: 01.52.00
Firmware Build Time: 11/18/2019
BIOS Version: 2.0a
BIOS Build Time: 08/08/2019
Redfish Version: 1.0.1
CPLD Version: 02.b4.02

I do get sensor readings:
Name Status Reading
CPU TempNormal45 degrees C
System TempNormal43 degrees C
Peripheral TempNormal41 degrees C
M2NVMeSSD Temp1N/ANot Present!
VRMCpu TempNormal41 degrees C
VRMSoc TempNormal51 degrees C
VRMABCD TempNormal40 degrees C
VRMEFGH TempNormal42 degrees C
DIMMA1 TempN/ANot Present!
DIMMB1 TempN/ANot Present!
DIMMC1 TempNormal38 degrees C
DIMMD1 TempNormal39 degrees C
DIMME1 TempN/ANot Present!
DIMMF1 TempN/ANot Present!
DIMMG1 TempNormal39 degrees C
DIMMH1 TempNormal37 degrees C
FAN1N/ANot Present!
FAN2Normal600 R.P.M
FAN3Normal1600 R.P.M
FAN4Normal700 R.P.M
FAN5Normal1100 R.P.M
FANANormal1000 R.P.M
FANBNormal1000 R.P.M
12VNormal11.984 Volts
5VCCNormal4.96 Volts
3.3VCCNormal3.259 Volts
VBAT Battery presence detected.
VDDCRNormal1.165 Volts
VMEMABCDNormal1.225 Volts
VMEMEFGHNormal1.214 Volts
VDD_5_DUALNormal5.099 Volts
VDD_33_DUALNormal3.242 Volts
SOCRUNNormal1.095 Volts
SOCDUALNormal0.886 Volts
 
R

RolloZ170

Well-Known Member
Apr 24, 2016
6,944
2,142
113
dragonian said:
I was able to update the IPMI to the latest with the older Rome BIOS 32MB (on the 1st page of this thread) I unchecked all of the "preserve" boxes -- I believe this is important.
Click to expand...
and are you able to see sensors(i.e. CPU voltages) in the IPMI frontend ?
 
A

alex_stief

Well-Known Member
May 31, 2016
884
313
63
39
Sooo... Epyc Milan aka Zen3 Epyc should be right around the corner for retail availability. At least I hope so.
What might be the chances of getting those CPUs to run on a rev.1 Supermicro H11DSi. It's still the same socket after all, and some of you managed to get Rome CPUs running on rev. 1 boards.
 
R

RolloZ170

Well-Known Member
Apr 24, 2016
6,944
2,142
113
alex_stief said:
What might be the chances of getting those CPUs to run on a rev.1 Supermicro H11DSi.
Click to expand...
the upper 16MB of a BIOS H11DSi rev.2(naples/rome)) is flashed on the rev. 1 board.
if there will be a BIOS rome/milan for the H11DSi then there is IMHO a chance.
 
B

Brainbug

New Member
Jul 5, 2015
12
2
3
56
@I.nfraR.ed Thanks for making the Linux version.

From the k10temp sources, it looks like tctl has a 27C offset. Does this mean that the actual CPU temperatures are 27C lower than reported? Curious, as the idle temp seems high, but matches what is shown in IPMI. (Load gets up to mid 90s, which seems accurate based on the 3990x reviews, but ** really ** high for a server CPU. If it was actually 90-27C = 63C, that would make me feel much better...)

For others using Linux with ZS processors, newer kernels have better sensor support for Zen2 systems - However, they aren't correctly detected by the kernel as the Processor version for Rome ZS is 0x30 vice 0x31.

For improved temp support, open "drivers/hwmon/k10temp.c" as sudo/root and search for "0x31". Add "case 0x30:" between "break;" and "case 0x31"

Code: 
        } else if (boot_cpu_data.x86 == 0x17 || boot_cpu_data.x86 == 0x18) {
                data->temp_adjust_mask = ZEN_CUR_TEMP_RANGE_SEL_MASK;
                data->read_tempreg = read_tempreg_nb_zen;
                data->show_temp |= BIT(TDIE_BIT);       /* show Tdie */
                data->is_zen = true;

                switch (boot_cpu_data.x86_model) {
                case 0x1:       /* Zen */
                case 0x8:       /* Zen+ */
                case 0x11:      /* Zen APU */
                case 0x18:      /* Zen+ APU */
                        k10temp_get_ccd_support(pdev, data, 4);
                        break;
                case 0x30:
                case 0x31:      /* Zen2 Threadripper */
                case 0x71:      /* Zen2 */
                        k10temp_get_ccd_support(pdev, data, 8);
                        break;
                }
        }
To see the power usage by core, open "drivers/hwmon/amd_energy.c" and search for "0x31". In the "x86_cpu_id_cpu_ids[]" struct, change the 0x31 to 0x30. (Note this will stop this driver from working for retail Zen2 CPUs, and only work for ES)

Code: 
static const struct x86_cpu_id cpu_ids[] __initconst = {
        X86_MATCH_VENDOR_FAM_MODEL(AMD, 0x17, 0x30, NULL),
        {}
};
Remove the compiled drivers, then rebuild, and reload
Code: 
 $>rm drivers/hwmon/amd_energy.o drivers/hwmon/amd_energy.mod.o drivers/hwmon/amd_energy.ko drivers/hwmon/k10temp.o drivers/hwmon/k10temp.ko drivers/hwmon/k10temp.mod.o
$> make
$> make modules_install
$> modprobe k10temp amd_energy
When you run sensors, you should now get output that resembles:
Code: 
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +44.8 C
Tdie: +44.8 C
Tccd1: +43.2 C
Tccd2: +42.8 C
Tccd3: +42.8 C
Tccd4: +42.8 C
Tccd5: +41.5 C
Tccd6: +45.0 C
Tccd7: +41.0 C
Tccd8: +43.5 C

amd_energy-isa-0000
Adapter: ISA adapter
Ecore000: 2.76 kJ
Ecore001: 2.57 kJ
Ecore002: 2.63 kJ
Ecore003: 2.57 kJ
Ecore004: 2.63 kJ
Ecore005: 2.54 kJ
Ecore006: 2.62 kJ
...
Ecore062: 3.54 kJ
Ecore063: 3.47 kJ
Esocket0: 1.13 MJ
 
Last edited:
I

irgen

Member
Jan 14, 2021
33
5
8
Guys still trying to make it work with zs1711e3vivg5 , now i replaced h11ssl v1.0 with rev. 2.0 board, it boots into windows fine but when i try to give it more-less significant load like CB it goes black screen and reboots after 1 sec. What could it be? Currently im using just one 8gb 2400 stick and for windows 10 i just borrowed ssd of old lenovo pc - so it is not fresh install and thap pc was intel.. so i have some devices with yellow mark it does not found drivers for, could that be the issue?
forgot to mention i did not overclock it yet
 
R

RolloZ170

Well-Known Member
Apr 24, 2016
6,944
2,142
113
irgen said:
zs1711e3vivg5 , now i replaced h11ssl v1.0 with rev. 2.0 board
Click to expand...
which BIOS version ?
irgen said:
so i have some devices with yellow mark it does not found drivers for, could that be the issue?
Click to expand...
if you install the Rome drivers there will be some yellow marks left, that are dummy devices. you can manualy install them or leave it as it is.
 
R

RolloZ170

Well-Known Member
Apr 24, 2016
6,944
2,142
113
irgen said:
AMD platform is something new to me - do i need some drivers for the CPU?
Click to expand...
any CPU needs drivers. they are normaly included in the chipset drivers. EPYC is system on chip.
download the SP3 IO Driver from the supermicro page of your motherboard.
 
I

irgen

Member
Jan 14, 2021
33
5
8
RolloZ170 said:
any CPU needs drivers. they are normaly included in the chipset drivers. EPYC is system on chip.
download the SP3 IO Driver from the supermicro page of your motherboard.
Click to expand...
thank you i will try to install this driver and see if anything changes!
 
  • Like
Reactions: RolloZ170
I

irgen

Member
Jan 14, 2021
33
5
8
RolloZ170 said:
which Power supply ? 8 Pin (EPS) connected ?
Click to expand...
Yes 8 pin is connected, but 4 pin is not. I tried to run Vraybench software on just one core , using Set Affinity, and going one-by-one cores found out that it immediately crashes if running on core 6-7 (which is core 3 in hwinfo)
Does that means i have a broken cpu? Also RomeOverclock.exe does not run on my system its just says -program stopped working - right after i launch
edit RomeOverclock 1.0 works but RomeOverclock 1.0.1 does not. So i was able to finish the benchmark with 3300 al cores but 3 disabled with SetAffinity. Is there a way i can disable that in bios?
 
Last edited:
R

RolloZ170

Well-Known Member
Apr 24, 2016
6,944
2,142
113
irgen said:
I tried to run Vraybench software on just one core , using Set Affinity, and going one-by-one cores found out that it immediately crashes if running on core 6-7 (which is core 3 in hwinfo)
Does that means i have a broken cpu?
Click to expand...
that would be my next suspection. a broken core. yes, highly possible unfortunaly :rolleyes:
 
You must log in or register to reply here.
Top Bottom