ec VS firmware-open

You mean this?: https://github.com/system76/ec/blob/930f16b230a1574abddc1cf313c32f1a90c994e9/src/board/system76/lemp11/board.mk

Inexplicably, the built-in curves have a 5 second delay for gazelle. This means, if your chip goes turbo, it will take 5 seconds before the fan will react. By that time, the temperature will have already spiked to 80-90 C. https://github.com/system76/ec/blob/2a8befc195cd821232d2934593d29337e4eddb3e/src/board/system76/gaze17-3060/board.mk

You can change the keyboard layout but not sure if you can replace the physical keyboard easily. https://github.com/system76/ec/blob/master/doc/keyboard-layout-customization.md

If you're wanting to try that out, it's very easy by editing the numbers within the FAN_POINT lines of this file (for your model): https://github.com/system76/ec/blob/master/src/board/system76/gaze17-3060/board.mk

I have the ec repo cloned into a sibling dir. Sorry for the confusion. Thanks for the help!

If it is identical to the Clevo that System76 uses then it may be possible to use their firmware.

This bit of documentation is also helpful, recommends getting the entire firmware-open stack and checking out the current firmware release that you're running and use that as a base for your modifications. This is important because firmware regressions are not uncommon and they often take some time before they are resolved.

As for the tracking issue, you want #213. #256 is my proposal for persisting options through power loss.

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 :-/