X12SPM-LN4F - w.BIOS 1.9 - QWAT on it.
Last edited:
ES Xeon Discussion
- Thread starter britinpdx
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I'm a bit tempted by the Xeon W-3300 CPUs since they turbo higher than the SPs, and I don't really need a ton of cores.
This thread
makes me optimistic that I can have a QS working in a Supermicro X12SPM board.
There is a bunch of W-3345 QS floating around on eBay. The pictured ones are SRKSU, like the final retail chip. This is standard for QS, right?
Any idea if these QS W-3345s will work in the X12SPM with latest BIOS? Or if I'm missing something?
This thread
makes me optimistic that I can have a QS working in a Supermicro X12SPM board.
There is a bunch of W-3345 QS floating around on eBay. The pictured ones are SRKSU, like the final retail chip. This is standard for QS, right?
Any idea if these QS W-3345s will work in the X12SPM with latest BIOS? Or if I'm missing something?
no, not a pic of cpu you get. QS = "Intel Confidential - Qxxx" like other ES
Intel Xeon W-3375 IceLake QXZL 57MB 38c 2.5 GHz 4.0 GHz 270W DDR4-3200
Intel Xeon W-3365 IceLake QXZK 48MB 32c 2.7 GHz 4.0 GHz 270W DDR4-3200
Intel Xeon W-3345 IceLake QXZJ 36MB 24c 3.0 GHz 4.0 GHz 250W DDR4-3200
Intel Xeon W-3335 IceLake QXQS 24MB 16c 3.4 GHz 4.0 GHz 250W DDR4-3200
Intel Xeon W-3323 IceLake QXQQ 21MB 12c 3.5 GHz 3.9 GHz 220W DDR4-3200
Last edited:
should work. at least ASRock SPC621 boards have Xeon W-3300 in the supported list of CPU.
edit:
gigabyte MU72-SU0 supports
- 3rd Gen Intel® Xeon® Scalable Processors
- Intel® Xeon® W-3300 Processors
Last edited:
ielectronics_alteratethis is very optimistic LOL
The Intel Xeon W-3345 is a server/workstation processor with 24 cores, launched in July 2021. It is part of the Xeon W lineup, using the Ice Lake-W architecture with Socket 4189. Thanks to Intel Hyper-Threading the core-count is effectively doubled, to 48 threads. To further increase overall system performance, up to two Xeon W-3345 CPUs can link up in a multi-processor (SMP) configuration.
Interesting. Supermicro were not as optimistic when I contracted them to ask if putting a W-3300 in a X12SPM/X12SPZ would work.
The response I got was:We actually don’t know, it’s not tested and we haven’t come to an opportunity to test it ourselves or hear from other customers who have tried it.
I do say however that Intel segregates their platforms more and more to push customers into specific combinations, for that reason I think the motherboards will simply not POST with the CPU.
Also, I don't know if I can conclude anything from this, but comparing the microcode from the BIOS of the X12SPA-TF (which does officially support W-3300) with X12SPM:
It seems they support the same CPUs?
they share same cpuid and microcode. there is only one chipset for Ice lake-SP and Ice Lake-X = C621A
I confirm. ASRock Rack SPC621D8-2L2T with latest BIOS, Xeon W-3375 QS (QXZL) works perfectly fine.
any chance to put this in a supermicro X12SPL or X12SPM ?
i have a SM board but not the pocket money for a Xeon W-3300
I do not have any SM boards of that generation. Being an ASRock fanboy the only reason for me having any SM boards was that 4th gen ASRock board was delayed so I had to buy SM X13 to test my processors And even that board is gone now - I’m switching to ASRock soon so I gave my SM setup for my daughters workstation.
And even that board is gone now - I’m switching to ASRock soon so I gave my SM setup for my daughters workstation.
What kind of answers did you expect to receive from SM?
when I sent them the MOBO for repair, where there was a problem on their part, they answered me:
"We tried to fix it but couldn't, our engineer decided that it was beyond repair"
As if I sent it for repairs to some workshop where newbies sit
I join your side, but still SM is much better, even if their RMA is lame as a duck
Guys, tell me, I downloaded this version MC Extractor v1.96.0 r279 on GitHubInteresting. Supermicro were not as optimistic when I contracted them to ask if putting a W-3300 in a X12SPM/X12SPZ would work.
We actually don’t know, it’s not tested and we haven’t come to an opportunity to test it ourselves or hear from other customers who have tried it.
I do say however that Intel segregates their platforms more and more to push customers into specific combinations, for that reason I think the motherboards will simply not POST with the CPU.
Also, I don't know if I can conclude anything from this, but comparing the microcode from the BIOS of the X12SPA-TF (which does officially support W-3300) with X12SPM:
View attachment 35027
It seems they support the same CPUs?
but nothing works for me when I drag and drop the BIOS into MCE.py
can't open anything
you need to install python and some required modules.
read MCU.txt
Code:
now Do I Open a Terminal Window in a Folder?
Open the folder you wish to open the command prompt window from.
Type cmd into the location bar at the top of the window and tap enter.
The command prompt will now be opened in the desired location.
Fixed:
Install Python 3.9.0 with
1) Set "PATH"
2) Set "py Launcher"
3) Set "Associate"
Open an admin command prompt in:
C:\Users\****\AppData\Local\Programs\Python\Python39\
where **** is your windows username.
and run:
python -m pip install --upgrade pip
In:
C:\Users\****\AppData\Local\Programs\Python\Python39\Scripts\
admin command prompt and run:
pip3 install colorama PLTable
Then in the same command prompt run:
pip3 install prettytable
Now you have the latest v1.0.2 PLTable and pip and will get no MCE errors in UBU Tool.
Last edited:
As RolloZ170 said, you're probably missing some dependencies. Try running:
$ pip3 install colorama
$ pip3 install pltable
It prompted me to install those. Otherwise, try running it from the terminal and see what it complains about...
I looked in the folder and programs, it turns out I have Python312
need to remove and install Python 3.9.0?
read MCU.txt
Code:
To work correctly, you need Python version 3.7 or later.
!!! Importan t!!!
Uninstall all old versions of Pyton 2.x-3.6Thanks for the information, I did everything as it says in the text
Now everything works great