rtorrent VS System76 Power Management

No 1

rtorrent and rutorrent might suit your needs. For easy setup on Debian you could use this

I've been a habitual rtorrent user but it feels like it's time to move on - it's also a little annoying that this issue has never seen traction.

Unfortunately rtorrent is pretty much dead: https://github.com/rakshasa/rtorrent/commits/master

I know it's not quite the same thing but I started using rtorrent[0] a very long time ago and it still works well for my needs.

Is there anyone who has used both who can comment on the pros and cons?

[0] https://github.com/rakshasa/rtorrent

Better in what exactly? Anyway, rtorrent seems abandoned. The last commit was 8 months ago. Transmission's last commit was 5 days ago. And regarding transmission-cli: "Prior to development of transmission-remote, the standalone client transmission-cli was created. Limited to a single torrent at a time, transmission-cli is deprecated and exists primarily to support older hardware dependent upon it. In almost all instances, transmission-remote should be used instead.".

rtorrent (pkg i rtorrent)

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