Paul Menzel

$ make PATH="/dev/shm/heads/install/x86/bin:$PATH" BOARD=qemu-coreboot-fbwhiptail-tpm2-hotp works around the error (and hits a new one, reported in issue https://github.com/osresearch/heads/issues/1470).

Thank you for the report. If this is with upstream coreboot, it’d be great, if you uploaded the log files to the coreboot [board status repository](https://review.coreboot.org/plugins/gitiles/coreboot/+/refs/heads/master/util/board_status/README.md).

Please mention the used Linux kernel version in the commit message description of commit *[as9726_32d] Add new platform*, and say why. The latest LTS version is 6.6.

Thank you for your comment. Indeed I missed the Debian package *charon-systemd*, shipping: $ systemctl cat strongswan # /usr/lib/systemd/system/strongswan.service [Unit] Description=strongSwan IPsec IKEv1/IKEv2 daemon using swanctl After=network-online.target [Service] Type=notify ExecStart=/usr/sbin/charon-systemd...

Sorry for not updating the issue. I think it was fixed by the newer version. I haven’t heard a report from the users mentioning the issue in a long time.

> Hm, are "virtual machine images for desktop use" really a thing? :) How's that typically used? (Really wondering about it, because I'm coming mainly from the server side of...

Interesting. Can you please reference the commit disabling the feature?

@aacebedo, any updates? Is the issue fixed, so it can be closed?

Over what interface are these values read from the system firmware (“BIOS”)?

@gkammela, were you able to look into this issue. Using Debian sid/unstable with *powertop* 2.15-3 on the different system Dell XPS 13 9360, the probem is still there with an...