Jump to content

Welcome to ExtremeHW

Welcome to ExtremeHW, register to take part in our community, don't worry this is a simple FREE process that requires minimal information for you to signup.

 

Registered users can: 

  • Start new topics and reply to others.
  • Show off your PC using our Rig Creator feature.
  • Subscribe to topics and forums to get updates.
  • Get your own profile page to customize.
  • Send personal messages to other members.
  • Take advantage of site exclusive features.
  • Upgrade to Premium to unlock additional sites features.
IGNORED

Intel to fuse off AVX512 on Alder Lake silicon going forward


ENTERPRISE

Recommended Posts

Quote

 

The AVX512 issue had emerged even before Intel released its new 12th Gen Core CPU series. The company released an optimization guide for its new architecture that initially mentioned AVX512 instruction support, but only on the Performance cores. Intel quickly corrected itself by removing AVX512 support from the guide and later from the CPUs themselves through a microcode update. 

Eventually, most 600-series motherboards received an update, that removed official support for AVX512. Interestingly, though, some companies still tried to offer partial support through hidden BIOS options. Nevertheless, this should change soon, as the updated Alder Lake silicon will no longer have this part of the chip physically enabled.

 

In a short statement to Tom’s Hardware, Intel confirmed that it will now fuse off the instruction from the silicon:

Source 

 

I saw this coming after motherboard manufacturers defied Intel and kept the instruction set alive, at least to some degree.

  • Thanks 1

£3000

Owned

 Share

CPU: AMD Ryzen 9 7950X3D
MOTHERBOARD: MSI Meg Ace X670E
RAM: Corsair Dominator Titanium 64GB (6000MT/s)
GPU: EVGA 3090 FTW Ultra Gaming
SSD/NVME: Corsair MP700 Pro Gen 5 2TB
PSU: EVGA Supernova T2 1600Watt
CASE: be quiet Dark Base Pro 900 Rev 2
FANS: Noctua NF-A14 industrialPPC x 6
Full Rig Info

£200

Owned

 Share

CPU: AMD RX-427BB
RAM: 16GB Corsair 1600MHZ DDR3L
SSD/NVME: WD Blue 250GB M.2 SATA SSD
NETWORK: Intel I350 -T4
CASE: HP Thin Client T730
Full Rig Info

£3000

Owned

 Share

CPU: 2 x Xeon|E5-2696-V4 (44C/88T)
RAM: 128GB|16 x 8GB - DDR4 2400MHz (2Rx8)
MOTHERBOARD: HP Z840|Intel C612 Chipset
GPU: Nvidia Quadro P2200
HDD: 4x 16TB Toshiba MG08ACA16TE Enterprise
SSD/NVME: Intel 512GB 670p NVMe (Main OS)
SSD/NVME 2: Samsung 1TB 980 NVMe (VM's)
SSD/NVME 3: 2x Seagate FireCuda 1TB SSD's (Apps)
Full Rig Info
Link to comment
Share on other sites

11 minutes ago, Avacado said:

Yea, read about this at lunch. I'll be selling off my "Early" sample 12900KF with AVX-512 on ebay in the future. 

In order to take advantage of your particular sample's "extra" features, the prospective customer will need a motherboard that has never been updated beyond a certain point in time, correct?  Forgive my ignorance, but I am under the impression that "BIOS" files sometimes contain pieces of code that become "permanent" even if the user reverts back to a previous BIOS at a later date.  "Microcode" is the term I see used most frequently in discussions pertaining to these changes.  I do not mean to imply that individuals with access to the requisite tools could not undo these changes, only that it will require more than a thumb drive and internet connection.

TDM

Owned

 Share

CPU: 5950x
MOTHERBOARD: Dark Hero
GPU: Aorus 6900XT Extreme WF
RAM: G. Skill Ripjaws V 64GB 3600 14-14-14-34
WC CPU BLOCK: Watercool Heatkiller IV
WC PUMP: XTOP Revo / FLT 120 + 3 D5's
SSD/NVME: Samsung 980 Pro
CASE: Gutted Enthoo Pro 2
Full Rig Info
Link to comment
Share on other sites

3 hours ago, ArchStanton said:

In order to take advantage of your particular sample's "extra" features, the prospective customer will need a motherboard that has never been updated beyond a certain point in time, correct?  Forgive my ignorance, but I am under the impression that "BIOS" files sometimes contain pieces of code that become "permanent" even if the user reverts back to a previous BIOS at a later date.  "Microcode" is the term I see used most frequently in discussions pertaining to these changes.  I do not mean to imply that individuals with access to the requisite tools could not undo these changes, only that it will require more than a thumb drive and internet connection.

Yes, you are correct. @Falkentynehas done some work over on OCN detailing how to roll back microcode to re-enable it. AVX-512 was defaulted to off with E cores enabled in the beginning. 

 

Here is the link:

WWW.OVERCLOCK.NET

 

  • Thanks 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...

Important Information

This Website may place and access certain Cookies on your computer. ExtremeHW uses Cookies to improve your experience of using the Website and to improve our range of products and services. ExtremeHW has carefully chosen these Cookies and has taken steps to ensure that your privacy is protected and respected at all times. All Cookies used by this Website are used in accordance with current UK and EU Cookie Law. For more information please see our Privacy Policy