On Thu, November 30, 2017 05:38, Zoran Stojsavljevic wrote: >> Last resort is to flash back the OEM image but I'm hoping to avoid that. > > I would suggest to do this step now. As interim step, Then you can verify > everything you are trying to do > with Coreboot. The first and obvious step is to check for MCU using dmesg, > if any exists. If yes, the next > step, probably, is to retrieve MCU from BIOS and port it to Coreboot, so > you can be sure that this is not > an issue. > > Then you can verify all the rest:XEN, Cubes and etc., and record use cases > wit logs, before returning > back to Coreboot.
That is a painful (because this laptop needs to be completely disassembled to get at the flash chip, and it's a Lenovo crippled InsydeH2O EFI BIOS with phone home capability) but logical approach. Thanks, will report back on where this problem bisection leads and/or a resolution when I get there. -- coreboot mailing list: [email protected] https://mail.coreboot.org/mailman/listinfo/coreboot
