Read more.Quote:
And it gives notice of microcode patches for products from as far back as 2007.
Printable View
Read more.Quote:
And it gives notice of microcode patches for products from as far back as 2007.
It's good news that both my Haswell-E i7-5930K and Broadwell-E i7-6900K processors are getting the update code.
I will just have to keep an eye on the MSI site to check for Bios updates.
Looking forward to revised benchmarking with the patched chips. No word of Meltdown fixes yet Hexus?
Given the performance impact and the exploit requires local execution I was going to go with not updating. I'm ultra careful with what I download and run anyway and don't go to dodgy websites. I may not have a choice as my mobo manufacturer doesn't look like they're going to do it anyway.
I just can't see this happening for a large number of users, especially for even older systems.Quote:
it requires that your system vendor or motherboard vendor takes Intels update code and issues a BIOS update for you.
Those were patched at the OS-level, if you're on W10 you're already fixed (windows patch came out almost 2 months ago)Quote:
Originally Posted by ohmaheid
I see that Dell have already released a BIOS update for my Haswell based Latitude E7440 notebook .
"- Updated to the latest CPU microcode to address CVE-2017-5715 and associated Intel Reboot issue."
Neat.
Looked at Gigabyte's site yesterday for Z97 version - nothing there.
This has been puzzling me the past few days, microcode patches can either be loaded (patched) via the BIOS or the OS, right?
Obviously the BIOS route is better as it patches the flaw early on and is OS agnostic, Linux is typically very good when it comes to issuing microcode updates that can be loaded by the kernel and while Microsoft typically doesn't issue microcode updates the capability for Windows to load them is there, so how come Intel and Microsoft don't seem to be working on a microcode patch to be loaded by Windows on older systems?
Great, I've seen one for my Dell Latitude 7240 is available too. However, I'm not going to update for a few weeks this time around.Quote:
Originally Posted by DDY
Microsoft is rolling out new updates for Windows Fall Creators Update.
plus a lot people will have no idea how update there motherboard
when i first started to update motherboads bios years back its was a bit scary
at first.....
latest Intel April list just released: https://newsroom.intel.com/wp-conten...e-guidance.pdf
Lynnfield (i7-860 etc) and Clarkdale (i3-540 etc) (socket 1156) now have microcodes released. Bad news for older generations though, Penryn, Wolfdale, etc all list as STOPPED. So seems like if you've got an Intel Core i-something CPU you're covered. Any core 2 or older generations and you're not getting updates.
Now to figure out how to apply it when ASUS seem unlikely to release a BIOS update for my board...
As I learned recently, to my surprise, microcode updates can be applied by the OS too, it doesnt need to be a BIOS update.Quote:
Originally Posted by ik9000
Which explains why Microsoft keep distributing them via Windows Update.
Obviously for more self-service OSes this might require more effort.
thinking about it, this kind of makes sense - IIRC the main differences between Lynnfield 1156 and Sandy Bridge 1155 were to do with the memory controller as opposed to the CPU functionality per-say so if they could fix it for SB then it makes sense it was feasible to do for Lynnfield. Similarly SFAIK later CPUs still share a lot in common (albeit with some differences/extra functionality) right up to socket 1150/1151. Before 1156 though wasn't everything still s775? That presumably is a vastly different beast, and might well be so different they've called time on it?Quote:
Originally Posted by ik9000