Intel Posts Updated Raptor Lake Microcode For Linux: Fixes Voltage Issue & Other Bugs

[phoronix]

Phoronix: Intel Posts Updated Raptor Lake Microcode For Linux: Fixes Voltage Issue & Other Bugs

Intel off their typical second Tuesday of the month patch regiment today posted new CPU microcode just for 13th Gen "Raptor Lake" and 14th Gen "Raptor Lake Refresh" processors for Linux systems. Notable with the updated Raptor Lake CPU microcode is the internal voltage handling fix for that well known problem plaguing many Raptor Lake owners plus two other fixes...

https://www.phoronix.com/news/Intel-RPL-Microcode-Voltage

[Sonadow]

DIY and desktop hardware enthusiasts: "We demand the right to significantly overvolt for greater performance and ruin our hardware if we so desire! Who are you to tell us not to?!"

*Raptor Lake requests slightly higher voltages than specified*

DIY and desktop hardware enthusiasts: "How dare you overvolt our hardware!"

[Espionage724]

Kind of sketchy for microcode being able to silently adjust voltages; easy way to lock out limits later. I'd expect a CPU microcode update to increase security or stability, not limit my overclocking after I already paid for the hardware (and I'm sure Intel would just love for me to forget my higher perf and buy a new CPU )

I'm not sure how AMD or Intel handle this comparably, but when I've seen similar updates with AMD iirc they had it in AGESA motherboard-side. If the mobo mfg wants to limit CPUs from blowing up their VRMs or whatever, I can understand that. I'm kind-of ok with the idea of the CPU mfg lowering voltages if it's well-known hardware and science (silicon/heat dispersion) reason behind it that comes down to the chip not frying, but I don't want to see limits lowered that were otherwise usable even if it required nitrogen or something wacky, especially worst-case if it's done to sell faster CPUs.

Basically, now I gotta check microcode updates, and changelogs better be good

I have no knowledge of Intel limiting overclocking limits post-purchase with a microcode update in hostile manner, but it sounds like they have the ability to do so.

[geerge]

DIY and desktop hardware enthusiasts: "We demand the right to significantly overvolt for greater performance and ruin our hardware if we so desire! Who are you to tell us not to?!"

*Raptor Lake requests slightly higher voltages than specified*

DIY and desktop hardware enthusiasts: "How dare you overvolt our hardware!"

One is the user making a choice to risk the hardware in exchange for performance, the other is the hardware choosing slow suicide by self-immolation. These things are not the same.

[aerospace]

They can't fix chips that have already semi-fried themselves with a microcode update..

[paulocoghi]

DIY and desktop hardware enthusiasts: "We demand the right to significantly overvolt for greater performance and ruin our hardware if we so desire! Who are you to tell us not to?!"

*Raptor Lake requests slightly higher voltages than specified*

DIY and desktop hardware enthusiasts: "How dare you overvolt our hardware!"

It was more like this:

The company: "We want to be ahead of our main competitor at all costs, even if this means that our CPUs risk frying."

*Customers start to RMA their fried CPUs*

Also the company: "How dare you to RMA the CPU which fried because of our own errors!"