Librem 15 v4 - ME

Hardware
1

I have a new Librem 15 v4, I was having a look at the setup having used coreboot before.

When running cbmem I get the results below which are very different to the expected output listed on the website https://puri.sm/coreboot/ can anyone advise ? I am assuming that it would be different as the v4 is not mentioned on this page.

./cbmem -c | grep ^ME
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)
ME: Current Operation State : M0 without UMA but with error
ME: Current Operation Mode : M0 without UMA
ME: Error Code : Preboot
ME: Progress Phase :
ME: Power Management Event : CM0PG->CM0
ME: Progress Phase State : Unknown phase: 0x0f state: 0xff
ME: Power Down Mitigation : YES
ME: PD Mitigation State : Issue Detected but not Recovered
ME: Encryption Key Override : Workaround Applied
ME: Encryption Key Check : FAIL
ME: PCH Configuration Info : Changed
ME: Firmware SKU : Unknown (0x7)
ME: FPF status : fused
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)
ME: Current Operation State : M0 without UMA but with error
ME: Current Operation Mode : M0 without UMA
ME: Error Code : Preboot
ME: Progress Phase :
ME: Power Management Event : CM0PG->CM0
ME: Progress Phase State : Unknown phase: 0x0f state: 0xff
ME: Power Down Mitigation : YES
ME: PD Mitigation State : Issue Detected but not Recovered
ME: Encryption Key Override : Workaround Applied
ME: Encryption Key Check : FAIL
ME: PCH Configuration Info : Changed
ME: Firmware SKU : Unknown (0x7)
ME: FPF status : fused

1 Like
2

The documention there has not been updated, but I think what you are seeing is correct. I created a task for this item, but I am not holding my breath. :slight_smile: You can find some discussion of this in some of the other forum entries, particularly the very long coreboot thread and here.

3

I’ve just pushed a major update to the coreboot page which covers this, among other things. It should be live shortly

3 Likes
4

One more question about ME - are they packages to remove from the linux install apart from amtterm, gamt, amttool ?

Thanks

5

I’m not clear on what you’re asking. Any packages which provide functionality for communicating with the ME via the AMT interface would be non-functional for two reasons: (1) the consumer (vs corporate) ME shipped on the Librem laptops doesn’t have AMT functionality, and (2) even if it did, the ME being cleaned/neutered would remove that functionality from the ME firmware. So there’s no point in removing any packages from your distro.

6

@MrChromebox, thank you! This has come up a few times, so it will be good to have the correct output there.

I will close that task in the Tracker.

2 Likes