coreutils VS System76 Power Management

Not that it should represent the rubicon of when to/not to rewrite code, but when you do, you do trade one set of bugs for a new set of bugs: https://github.com/uutils/coreutils/issues

Would be interesting to see a a Debian derivative that combines this with the Rust Implementation Of GNU Coreutils.[1] Could be a big win for memory safety and performance.

[1] https://github.com/uutils/coreutils

uutils /coreutils is also a great project. It has many contributors, and it also is a great resource to learn.

You might be interested in this? https://github.com/uutils/coreutils

Already did it. Checkmate, as i believe your people say.

There is already a rust implementation of coreutiils that uses a single binary like BusyBox or toybox. https://github.com/uutils/coreutils

Ah yes, std, that famous crate that is unusable for systems programming. God forbid anyone do any "systems" programming that uses std.

See: https://github.com/pop-os/system76-power

Also refer to https://github.com/pop-os/system76-power/issues/153 for setting environment variables and making simple scripts with it.

One example would be, I had problems with running native version of Substance Designer. And it had something to do with always using GPU or setting environment variables(https://github.com/pop-os/system76-power/issues/153). But I wouldn't know what to look for if a random guy on a forum didn't tell me to use it with NVIDIA Graphics.

[Update 2022-02-21] It appears that there are two packages, System76-io-dkms and System76-power. From what I gather only the first is necessary. I'm not sure how to install third-party DKMS modules that are not in the official repos. The official Void documentation on this topic is sparse, is there somewhere I can look this up?

Initially it only worked with Intel CPUs but it seems it supports AMD APUs now according to this Github issue https://github.com/pop-os/system76-power/issues/73

system76-power

The performance modes are going to affect how much power the system is using (and thus how much heat it's generating), not the fan curves directly. Those profiles are defined in the system76-power application, source code here: https://github.com/pop-os/system76-power/blob/master/src/daemon/profiles.rs

The script uses udev rules that are run at specific kernel events. It creates one rule for when the Laptop switches to battery power and another for when the Laptop switches to wall power. Both rules run system76-power while providing one of the available power profiles as an argument. I went with battery and balanced respectively.

Try the fix listed here: https://github.com/pop-os/system76-power/issues/358