firmware-open VS Popsicle

This reminds me a lot of FW update a8dd6c2, since rolled back, which came out about 4 months ago and caused problems with darp8 (e.g. https://github.com/system76/firmware-open/issues/469, https://www.reddit.com/r/System76/comments/1692nd2/darter_pro_fails_to_resume_after_fw_a8dd6c2/, https://www.reddit.com/r/System76/comments/168oehz/new_coreboot_update/)

I suspect that my current settings are still "overkill", so I'm wondering if there's a nice way (in the absence of https://github.com/system76/firmware-open/pull/365 being merged!) to find out what the minimum speed is I can get away with without my laptop spontaneously combusting? :D

There is an issue about this: https://github.com/system76/firmware-open/issues/407 They closed it (because there was an update), but yeah it's definitely not fixed. You can subscribe to this issue to see what's going on, but do not get your hopes high - they will rarely, if ever, update the issue.

There isn't a way without flashing the firmware at least once, but there is this PR instead which exposes userspace fan controls, which might work with some of the fan control software in Linux.

Issue opened: https://github.com/system76/firmware-open/issues/432

What Framework can't offer is Coreboot with Management Engine Cleaner and other great specs. System76 just announced a new fully open source bios for their intel 10th - 13 th gen models: https://github.com/system76/firmware-open/blob/77abfadf24c9a0c45ae042cd71d3ce7be26c846e/FEATURES.md

Hi! I check the firmware-open repository from time to time and noticed that since the initial release a few potentially interesting things have been committed (e.g. Disable ME by default on everything but TGL-U or Support for NVIDIA Dynamic Boost ). Should I wait for the "official" update to show up in firmware-manager? These changes seem to have been released quite some time ago, but there is no trace of them in the GUI. I am inclined to build and flash it myself. I've flashed my ec in the past, but I don't want to set the versions of ec and firmware-open too far apart. What's the policy here? There is this warning here about "normal" users who should not do this themselves. Perhaps I am not normal :-/

popsicle

I'd use Etcher primarily due to it simplicity, and it's available on several platforms. Popsicle next if you have a linux system.

There is also a project called Popsicle that lets you image multiple drives https://github.com/pop-os/popsicle

https://github.com/pop-os/popsicle worked for me across multiple systems

AppImage: https://github.com/pop-os/popsicle/releases

Rust projects that need more recognition imo are: * Zola * Spot * Popsicle * Plume

https://github.com/system76/firmware-open/files/6728054/galp5-disable-me.zip https://github.com/system76/firmware-open/files/6728055/lemp10-disable-me.zip -> Extract .img file, flash to a USB flash drive with Popsicle (https://github.com/pop-os/popsicle, btw it is installed in pop os as "usb flasher") , and then boot from the USB flash drive to flash the firmware.

Not sure how you get a raw request to that URL. It's a directory. This weekend I've made the CLI translatable as well. Translations are stored in https://github.com/pop-os/popsicle/tree/master/i18n