[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Home]
Board
Settings Home
/g/ - Technology



Thread archived.
You cannot reply anymore.



File: hqdefault.jpg (54 KB, 480x360)
54 KB
54 KB JPG
I don't understand. Intel/motherboard manufacturers rolled out an update of ME which is fixing the bug? Or you should wait for OS'es fix the bug? I mean the ME update is out there. Do I need just that or do I need to update the OS?
>>
The ME is literally a small computer running completely independent from your mainboard firmware or operating system.
The only thing to patch is the software inside. Whether that happens through a BIOS update (with the mainboard firmware re-flashing the ME on first boot) or an "updated driver" for your OS doesn't matter.
>>
the ME bug is a different one and it was patched on will be patched by updating the bios or ME.

this Kernel leak is a different one and you need a kernel/OS update to avoid it with a 30% performance hit




Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.