How can I check if Intel ME is disabled or not?

[FranklyFlawless]

@jam

If you know other methods, please share.

Coreboot Firmware on Purism Librem Devices – Purism

Verifying the Intel ME is Neutralized

You can confirm the ME condition by utilizing the same cbmem utility as above:

coreboot/util/cbmem$ sudo ./cbmem -c | grep ME

the most important lines are the 7 that match these output:

for Librem 13v1/15v2:

ME: FW Partition Table : OK
ME: Bringup Loader Failure : NO
ME: Firmware Init Complete : NO
ME: Manufacturing Mode : YES
ME: Boot Options Present : NO
ME: Update In Progress : NO
ME: Current Working State : Initializing ...

for Librem 13v2/15v3 and newer:

ME: Host Firmware Status Register 1 : 0xFFFFFFFF
ME: Host Firmware Status Register 2 : 0xFFFFFFFF
ME: Host Firmware Status Register 3 : 0xFFFFFFFF
ME: Host Firmware Status Register 4 : 0xFFFFFFFF
ME: Host Firmware Status Register 5 : 0xFFFFFFFF
ME: Host Firmware Status Register 6 : 0xFFFFFFFF
ME: FW Partition Table : BAD
ME: Bringup Loader Failure : YES
ME: Firmware Init Complete : YES
ME: Manufacturing Mode : YES
ME: Boot Options Present : YES
ME: Update In Progress : YES
ME: D3 Support : YES
ME: D0i3 Support : YES
ME: Low Power State Enabled : YES
ME: CPU Replaced : YES
ME: CPU Replacement Valid : YES
ME: Current Working State : Unknown (15)
…

Disclaimer: ME neutralization and disablement is an ongoing and repeated effort requiring tailored work across different models and chipsets (for example, we once found the ME cleaner tool to cause problems with Wi-Fi on Skylake, and had to solve that first).

Output from Librem 14:

[NOTE ]  coreboot--TIMELESS--LESSTIME--PureBoot-Release-30 Thu Jan 01 00:00:00 UTC 1970 x86_32 bootblock starting (log level: 7)...
[NOTE ]  coreboot--TIMELESS--LESSTIME--PureBoot-Release-30 Thu Jan 01 00:00:00 UTC 1970 x86_32 romstage starting (log level: 7)...
[DEBUG]  CBMEM:
[NOTE ]  coreboot--TIMELESS--LESSTIME--PureBoot-Release-30 Thu Jan 01 00:00:00 UTC 1970 x86_32 postcar starting (log level: 7)...
[NOTE ]  coreboot--TIMELESS--LESSTIME--PureBoot-Release-30 Thu Jan 01 00:00:00 UTC 1970 x86_32 ramstage starting (log level: 7)...
[DEBUG]  Reference Code - ME = 9.0.7b.20
[DEBUG]  MEBx version = 0.0.0.0
[DEBUG]  ME Firmware Version = Consumer SKU
[DEBUG]  BS: BS_DEV_ENUMERATE run times (exec / console): 2 / 0 ms
[DEBUG]  ME: HFSTS1                      : 0xFFFFFFFF
[DEBUG]  ME: HFSTS2                      : 0xFFFFFFFF
[DEBUG]  ME: HFSTS3                      : 0xFFFFFFFF
[DEBUG]  ME: HFSTS4                      : 0xFFFFFFFF
[DEBUG]  ME: HFSTS5                      : 0xFFFFFFFF
[DEBUG]  ME: HFSTS6                      : 0xFFFFFFFF
[DEBUG]  ME: Manufacturing Mode          : YES
[DEBUG]  ME: SPI Protection Mode Enabled : NO
[DEBUG]  ME: FW Partition Table          : BAD
[DEBUG]  ME: Bringup Loader Failure      : YES
[DEBUG]  ME: Firmware Init Complete      : YES
[DEBUG]  ME: Boot Options Present        : YES
[DEBUG]  ME: Update In Progress          : YES
[DEBUG]  ME: D0i3 Support                : YES
[DEBUG]  ME: Low Power State Enabled     : YES
[DEBUG]  ME: CPU Replaced                : YES
[DEBUG]  ME: CPU Replacement Valid       : YES
[DEBUG]  ME: Current Working State       : 15
[DEBUG]  ME: Current Operation State     : 7
[DEBUG]  ME: Current Operation Mode      : 15
[DEBUG]  ME: Error Code                  : 15
[DEBUG]  ME: CPU Debug Disabled          : YES
[DEBUG]  ME: TXT Support                 : YES
[DEBUG]  FSP MEMORY  2. 0x99c4e000 0x003b0000
[DEBUG]  TIME STAMP  5. 0x99c2c000 0x00000910
[DEBUG]  MEM INFO    7. 0x99c29000 0x00000f48
[DEBUG]    FSP RUNTIME 1. 0x99ffebe0 0x00000004