system76-acpi-dkms VS ec

Is this change going to be backported to the mainline kernel? I checked the recent sources and it's not there. It's affecting everyone that does not use dkms build but relies on mainline kernel. Keyboard brightness control-keys do not work and any other attempt to change LED brightness (for instance, I use it via powerdevil controls) results in:

Looking into it, the functionality isn't yet implemented for open EC laptops. system76-power has fan curves for Thelio I/O boards, but laptop support isn't implemented yet. https://github.com/pop-os/system76-acpi-dkms/issues/9

Although System76 tries to deliver as much software as it can, it's not enough. I wasn't able to keep system76-power daemon up to this error. Looks like GNOME 41 and system76-power conflict -- and GNOME 41's power management doesn't do as good as system76-power does. Battery consumption is worse than what I get on Pop!_OS. I cannot install system76 dkms modules due to this error.

I am looking to bring the system76-acpi-dkms to NixOS.

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.