On 2018-05-11 00:08, Nico Huber wrote:
actually, I don't see a BIOS in there at all. ... If you want to hunt more clues nevertheless, you can send us the output of `flashrom -p internal:laptop=force_I_want_a_brick -V`. IIRC, it also tells from which bus the BIOS was loaded.
I think the ME has some logging enabled and simply writes to the flash.
Nico
On 2018-05-10 23:24, David Hendricks wrote:
If this is the case, then you will need to figure out how to prevent the EC from reading/writing the ROM at the same time as flashrom. This could be as simple as disabling your OS's power management daemon to avoid stimulating it, or ...
Here comes the verbose output of flashrom as attachement. This time the output was taken after shutting down the backlight daemons: systemctl stop systemd-backlight@backlight:acpi_video0.service systemctl stop systemd-backlight@backlight:nv_backlight.service
- and see the newly loaded rom images do not differ any more (though the time between taking both images has been less this time).
wget https://www.elstel.org/uploads/celsius3.rom wget https://www.elstel.org/uploads/celsius4.rom
Is it true that these flash images do not contain a BIOS? If it still contains all ME regions that should be enough for disabling ME? How to do that - I have heard that me_cleaner only works on gen2 and gen3 MEs but that my ME would be gen1?