Filip Lewiński

### CBmem log summary I've dumped and went through the logs for each of the confirmed reproducibly (not)working sticks above and this is what I've managed to notice: XHCI initialization,...

After further analysis, it turned out coreboot would disable PCI `00:0d.0` upon init, responsible for the USB3/USB-C stack. The issue has been patched by https://github.com/Dasharo/coreboot/pull/499 and confirmed to be resolved.

@macpijan after the fixes this issue seems to be resolved: ``` ============================================================================== Tpm2-Commands ============================================================================== Checking if tpm2-tools is installed... Package tpm2-tools is installed TPMCMD001.001 Check if both SHA1 and SHA256...

Addressed by https://github.com/Dasharo/coreboot/pull/515 - lowered the minimum brightness level achievable via hotkeys.

@macpijan Yeah, installation and testing on Windows went well besides that

@macpijan on the 1.2.0 it doesn't get stuck on initial frequency, but then it doesn't run on expected frequency either. I've mentioned it and linked the logs in https://github.com/Dasharo/dasharo-issues/issues/763

@BeataZdunczyk couldn't manage to reproduce this one

It used to be pretty much unbearable, allowing the platform to be used for like 30sec at most. After building from the [byt_fsp_parity](https://github.com/Dasharo/coreboot/tree/byt_fsp_parity) branch however, it hasn't occurred for a...

Checked the logs: `[DEBUG] No SPI lockdown configuration.` Looks like setting flash lock configurations has to be implemented for each Bay Trail platform separately, keeping in mind the flash chip...

Managed to get BIOS lock to work so far: ``` ubuntu@3mdeb:~$ sudo flashrom -p internal -w read_dirty.rom -c "W25Q64JV-.Q" [sudo] password for ubuntu: flashrom v1.2-1033-g24b8fcf-dirty on Linux 6.5.0-45-generic (x86_64) flashrom...