ES Xeon Discussion

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I had read that before and it was where I got this idea, not realizing that it wasn't a mix of cores but based on amount of them.
Considering that I wouldn't expect to have more than 24 or 26 cores on an Asrock W790, that sounds very good.
Is there a chart, list, or projected graph anywhere with correlated core counts to clock speed for D0?
Something like this or this (SST-PP section aka Speed Step Technology for some SKUs configurable via BIOS where you can select number of cores from very limited set of configurations) ?
I think it's not widely available for ES versions apart from generic info like in RolloZ170' post from HWINFO64 above (which IMV is different from SST-PP since it's more related to Turbo limits which is normally restricted by duration, although you can select core affinity on operating system level too)
 
Last edited:
S2600WF BIOS Mod Update

After dumping the BIOS via SPI, I added the updated microcode—surprisingly straightforward for a first attempt!

Finally, no more error messages in the management interface. Previously, the errors were severe enough to halt the system, but now it’s stable.

Turbo Boost seems to work fine. All cores boost to around 3 GHz, and with fewer cores active, it can clock even higher.

Any recommendations for additional tweaks or features to include in a modded BIOS?

I can’t run Geekbench at the moment since it doesn’t support ES chips, but I’ve been using PassMark PerformanceTest for Linux instead: PassMark PerformanceTest.

During benchmarks with all cores turbo-enabled, temperatures stay below 66°C, which is great. Fan control through the BIOS works well, keeping the server relatively quiet.

Performance is comparable to a Xeon 8260, but since this is a dual-CPU system, the benchmark results are roughly double those of a single CPU setup.

I’m still unsure about memory configuration and benchmarking. MemTest86 runs without errors and completed a full pass, but I could use advice on how to properly configure or test the memory for optimal performance.
 

Attachments

  • 1000016642.jpg
    1000016642.jpg
    75.2 KB · Views: 30
  • no-error.jpg
    no-error.jpg
    30.4 KB · Views: 29
  • 1000016656.jpg
    1000016656.jpg
    67.2 KB · Views: 23
Good day everyone,
I’ve been attempting to boot QDCS on my Chinese X99 motherboards (Jingsha X99-8D3 and Huananzhi X99-8M-F), but sadly without success. Here is the summary of what I have done:

  1. According to this CPU-World link https://www.cpu-world.com/sspec/QD/QDCS.html, QDCS has CPUID 0306F0h. Having said that, every BIOS I tried that has 306F0 microcode only showed Q-code FF. A person on the CPU-World page also commented that the CPU only supports DDR3, which I already confirmed as on my Huananzhi board (runs DDR4 and BIOS doesn’t have 306F0 microcode), it stopped at Q-code B7 (memory error). That left all of my following steps conducted on my Jingsha X99-8D3 (runs DDR3).
  2. When I tried to remove 306F0 microcode, the board got past FF but got stuck at 79 (PCH Initialization). This made me thought about downgrading the ME as I have known several instances in which the ME blocks the CPU from loading. It still didn’t work out, however.
I read a post on Xianyu (Chinese second-hand market) in which the seller claimed that his QDCU (also an A0 sample) booted on his unspecified ASRock MB, but after he updated the BIOS, it no longer did. Does anyone happen to know any motherboard which has booted up this CPU? If not, can someone offer some insights as to what should be modified in the BIOS? I would gladly appreciate your precious help.
 
Last edited:
Happy Christmas,

Stupid question, gygabyte MS33-AR0 ("BIOSVersion" : "R07") - latest I'm afrade, xeon ES QYFS .
Is no POST nor video Output = dead cpu?
Some activity on CPU sensors, if I read it right, but feels like it's just MB hickup.
s-l1600.png
 
..Is no POST nor video Output = dead cpu?
Some activity on CPU sensors, if I read it right, but feels like it's just MB hickup...
Do you have couple of post codes from the sequence before hangup?
Looks something like this on my SM MB:
1735036332152.png
Generally it should tell you what's wrong (what detection stage has some issues like CPU/RAM/Chipset/GPU/PCIe etc.).
Then refer to relevant BIOS type manual to decode from post code into textual description.
 
Last edited:
Do you have couple of post codes from the sequence before hangup?

I might be wrong here, but as far as I understood MS33 doesn't have POST snooping, logs show power events and that basically it.
I'll look into redfish api may be I can get more out of mainboard.


Generally it should tell you what's wrong (what detection stage has some issues like RAM/CPU/PCIe etc.)



I'd expect so, but I don't think it gets to that stage. I remove everything from mainboard except CPU and PSU connection.
No beep for missing memory.
 
...I might be wrong here, but as far as I understood MS33 doesn't have POST snooping, logs show power events and that basically it.
I'll look into redfish api may be I can get more out of mainboard...
Worst case scenario - you probably can get relatively cheap SPI/GPIO or perhaps even LPC/PCIe diagnostics/debug board (sometimes called post tester, motherboard analyzer, etc.) for £5-£20 on ebay which will show codes to you on built-in display (LCD or 7-segment pack).
 
Last edited:
Worst case scenario - you probably can get relatively cheap SPI/GPIO or perhaps even LPC/PCIe diagnostics/debug board (sometimes called post tester, analyzer, etc.) for £5-£20 on ebay which will show codes to you on built-in display (LCD or 7-segment pack).
Oh wow! Thanks! I didn't know that such thing exists will look into it.
 
Stupid question, gygabyte MS33-AR0 ("BIOSVersion" : "R07") - latest I'm afrade, xeon ES QYFS .
Is no POST nor video Output = dead cpu?
have you checked the MS33 with other CPU first ?
QYFQ runs on MS33-CPA BIOS F09 which is very very similar to MS33-AR0 F07 (i have too but not installed)
so dead motherboard or bad CPU installation, the mainboard usualy don't beep,
you can see all in the BMCWebGUI, update BIOS there.
note: to see the lately flashed new BIOS version in BMCWebGUI you need successfully POST. This is for historical reason and
the BMC Firmware is universal to all boards with AST2600, some have dual BIOS and the Firmware still can't know which BIOS is running.
MS33-CPA_QYFQ_F09.jpg
 
Hi @RolloZ170, thanks a ton for reply.

have you checked the MS33 with other CPU first ?
Nope. I have only one at the moment. Considering to buying one from somebody you know on ebay.

QYFQ runs on MS33-CPA BIOS F09 which is very very similar to MS33-AR0 F07 (i have too but not installed)
so dead motherboard or bad CPU installation, the mainboard usualy don't beep,
you can see all in the BMCWebGUI, update BIOS there.
That what I'd like to figure out. But it looks like to do so I have to get MB or CPU. And sine CPU is cheaper. I think I'll get it first after Christmas.
+ based on what you are saying about beeping and MB show stats, funs are spinning I hope it's CPU. I wish there were way to be more certain but what one can do:(


note: to see the lately flashed new BIOS version in BMCWebGUI you need successfully POST. This is for historical reason and
the BMC Firmware is universal to all boards with AST2600, some have dual BIOS and the Firmware still can't know which BIOS is running.
That's very helpful, since I flashed F0 with GbtUtility-2.1.78.jar both and it still shows R07.
 
That's very helpful, since I flashed F0 with GbtUtility-2.1.78.jar both and it still shows R07.
why do you use this crap ? you can update/downgrade BIOS with BCMWebGUI.
are you sure you have installed the CPU properly ? have you modern PSU ? (not 20 year old)
That what I'd like to figure out. But it looks like to do so I have to get MB or CPU.
checked if there is any POST code yet ?
 
why do you use this crap ? you can update/downgrade BIOS with BCMWebGUI.
I tried few of them. Wasn't sure if gigabyte removed ES macrocodes from new firmware.
Also somebody claimed here https://forums.servethehome.com/ind...board-bios-recovery-jumper.40812/#post-452184 that at least it give him video output.
And yes I flash them both ways UI and GbtUtility. Actually I'd prefer GbtUtility since it spits out info during flashing.
but in both cases I see "bios flash alert" in MB log.


are you sure you have installed the CPU properly ?
I hope so. Did it twice. The second time I didn't screw fun properly, just place CPU in carrier to socket. In hope to here some beeps at least or events in log. And seems MB detected it and didn't power it up.

have you modern PSU ? (not 20 year old)
Asus ROG Strix 1000 W
 
I hope so. Did it twice. The second time I didn't screw fun properly, just place CPU in carrier to socket. In hope to here some beeps at least or events in log. And seems MB detected it and didn't power it up
you need 80 kilogramms pressure.
The second time I didn't screw fun properly, just place CPU in carrier to socket.
can burn out CPU and motherboard easy.
 
...I hope so. Did it twice. The second time I didn't screw fun properly, just place CPU in carrier to socket. In hope to here some beeps at least or events in log. And seems MB detected it and didn't power it up...
To me it felt like for LGA4677 there's resistance spring-s (on both sides) which prevents carrier-mounted CPU from landing onto contacts fully, it's simply impossible to have all contacts in right position without sufficient pressure, at the same time if some random contacts are connected but some are not then there's a possibility of having wrong current balance leading to (m)Amps flowing via pins which are not designed for it, this can easily result in bricked CPU or MB.
 
Last edited:
And yes I flash them both ways UI and GbtUtility. Actually I'd prefer GbtUtility since it spits out info during flashing.
but in both cases I see "bios flash alert" in MB log.
ID: 26 BMC Event sensor of type OEM logged a BMC Event : BIOS Update Image-1 Success was asserted