-
Notifications
You must be signed in to change notification settings - Fork 280
me_cleaner status
Nicola Corna edited this page Dec 8, 2017
·
21 revisions
Please comment here if me_cleaner works on your device (even if it is already listed as working)
| PCH | CPU | ME | SKU | Status |
|---|---|---|---|---|
| Ibex Peak | Nehalem/Westmere | 6.0 | Ignition | WORKS (1) |
| Ibex Peak | Nehalem/Westmere | 6.x | 1.5/5 MB | WORKS (1) |
| Cougar Point | Sandy Bridge | 7.x | 1.5/5 MB | WORKS |
| Panther Point | Ivy Bridge | 8.x | 1.5/5 MB | WORKS |
| Lynx/Wildcat Point | Haswell/Broadwell | 9.x | 1.5/5 MB | WORKS |
| Wildcat Point LP | Broadwell Mobile | 10.0 | 1.5/5 MB | WORKS |
| Sunrise Point | Skylake/Kabylake | 11.x | CON/COR | WORKS |
| Union Point | Kabylake | 11.6 | CON/COR | UNTESTED |
| SoC | TXE | SKU | 250b2ec |
|---|---|---|---|
| Bay Trail | 1.x | 1.25/1.375/3 MB | UNTESTED |
| Braswell/Cherry Trail | 2.x | 1.375 MB | WORKS |
Currently me_cleaner works partially on platforms with Intel Boot Guard set in Verified (+ Measured) Boot. Read this to learn more about Intel Boot Guard and its implications about me_cleaner.
(1) Currently it DOESN'T WORK with coreboot on Nehalem, see here