←back to thread

132 points cl3misch | 2 comments | | HN request time: 0s | source
Show context
voidbert ◴[] No.40712750[source]
Please consider the risks of the following vulnerability before deciding whether or not to undervolt: https://plundervolt.com/
replies(6): >>40712818 #>>40712825 #>>40712902 #>>40713134 #>>40713189 #>>40713668 #
rany_ ◴[] No.40712818[source]
In all likelihood this tool does not work for most users, specifically in response to this vulnerability. If you're on the latest microcode, undervolting is no longer possible due to Intel's mitigation: https://www.intel.com/content/www/us/en/security-center/advi...
replies(1): >>40714772 #
1. gravescale ◴[] No.40714772[source]
Which is a pity because my i7 Lenovo laptop is acoustically and thermally some kind of jet turbine in a case, because I was foolish enough to believe a review, and I really wish I could undervolt it so it can make it to lunchtime on a charge.
replies(1): >>40767386 #
2. rany_ ◴[] No.40767386[source]
I was actually wrong about that, it turned out to be possible on my 11th gen Intel CPU but it was definitely not as easy as it should've been.

I used https://github.com/datasone/setup_var.efi to modify the UEFI variables. The README has all the info you'd need. It turns out that both a BIOS and microcode update is required to kill off this feature, and you could just configure the BIOS to not lock it.