On 7/31/2024 at 9:40 PM, Krazier said:

Hi, I'm new here and I want to read the documentation. Where can I find it? Where is that question mark?
Thanks  

The ? Symbol at the top right of the GUI can be used to turn the help built into the GUI on/off at the page level.    You can also normally click on the text for a setting to do it for just that field.

 

The online documentation is accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

The ? Symbol at the top right of the GUI can turn the help built into the GUI on/off at the page level.    You can also do it for individual fields by clicking on the text name of the field.

 

the online documentation is accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

Hi, 

first of all: Great plugin! Already safed a buck on one of my machines. 

 

However, another machine got an error: 
I happened to set

PCI PM Control: enable 

and 

Power Profile: Power Super Safe

Now I can neither log into the webgui nor via SSH. 

Is there any way to revert these settings from the boot stick? 

 

Thanks ahead! 

Resolved this by myself: 
/boot/config/plugins/autotweak/autotweak.cfg

 

For anyone who runs into this issue. 

Nice plugin, on boot I've been getting a repeated console log errors claiming "no such device or address" for /dev/tty on line 26 (echoing log messages with script name prepended) of the emhttp/plugins/autotweak script despite the fact I can see it in the directories for /sys and /dev. Let me know if I'm doing something silly or if you need any additional logs to clear things up. Thanks for contributing!

does this work with tips and tweaks plugin? I'm not sure what your plugin touches network wise and what tips and tweaks touches..

On 11/2/2024 at 10:17 AM, Kevinf63 said:

Nice plugin, on boot I've been getting a repeated console log errors claiming "no such device or address" for /dev/tty on line 26 (echoing log messages with script name prepended) of the emhttp/plugins/autotweak script despite the fact I can see it in the directories for /sys and /dev. Let me know if I'm doing something silly or if you need any additional logs to clear things up. Thanks for contributing!

I've got the same error. Not sure how to resolve it.

On 11/2/2024 at 12:17 AM, Kevinf63 said:

Nice plugin, on boot I've been getting a repeated console log errors claiming "no such device or address" for /dev/tty on line 26 (echoing log messages with script name prepended) of the emhttp/plugins/autotweak script despite the fact I can see it in the directories for /sys and /dev. Let me know if I'm doing something silly or if you need any additional logs to clear things up. Thanks for contributing!

 

I fixed it in 1.3.13. It was just a harmless bug. I forgot to comment out the debug logging.

On 11/26/2024 at 12:00 AM, shanelord said:

I've got the same error. Not sure how to resolve it.

 

I fixed it in 1.3.13. It was just a harmless bug. I forgot to comment out the debug logging.

On 11/14/2024 at 2:18 AM, bmartino1 said:

does this work with tips and tweaks plugin? I'm not sure what your plugin touches network wise and what tips and tweaks touches..

 

I would say no. They try to configure some of the same stuff.

Bit of an odd request, but would you consider changing your version numbering to use YYYY.MM.DD ? Ex: if you released today it would be 2024.12.02 (and if you released twice today your second release would be 2024.12.02a or 2024.12.02.01 or something).

The reason I ask is your plugin is the only one I have installed that doesn't use this convention. The main benefit to users (myself included) is if in some distant future you stop maintaining the plugin it is easier to tell when the plugin was last updated. For example, I currently don't have any plugins installed that are older than 2023. This is mostly by chance, but occasionally I will look for plugins that haven't received an update in a long time and see if there's a fork or alternative, or if the functionality got built into the unRAID OS, or if I'm having some kind of issue updating a specific plugin for some reason. I've also seen a few cases where another dev will come along and make a fork (just mentioned that, but wanted to point out the alternate dev aspect) of a plugin that seems like it's no longer maintained.

 

A valid argument against this is the date as a version can create a sense of "there SHOULD be an update" even if there are no issues with the plugin and it's considered feature complete. If it ain't broke, don't fix it. So I can understand if you're against it.

 

Hopefully though, you'll consider it, again as I mentioned your plugin is the only one I have installed that doesn't use this convention, so if nothing else, maybe just to be versioning the way most other plugins version (following the crowd isn't always a bad thing).

 

Anyway thanks for reading either way.

I run powertop. (as in powertop --auto-tune &>/dev/null  )

 

every time I start my unraid server - would this be an example of doing something that would conflict with your plugin?

 

Thanks

On 2/3/2025 at 1:46 AM, awediohead said:

I run powertop. (as in powertop --auto-tune &>/dev/null  )

 

every time I start my unraid server - would this be an example of doing something that would conflict with your plugin?

 

Thanks

 

 

Yes,  it would conflict. The plugin configures same power management parameters as powertop does and many other stuff. The only deliberate difference is that this plugin avoids enabling autosuspend for USB devices.

You can verify this after restarting your system before running powertop --auto-tune command. Just start powertop and check the Tunables tab on the gui.

 

On 4/8/2024 at 2:00 PM, InternetD said:

Also amd_pstate=active (with the upcoming 6.6 kernel) for Zen2 and newer AMD CPUs. After that the performance and especially the powersave governor are working way better.

 

Schedutil should be also preferred before ondemand/performance if amd_pstate is not availabe for your CPU.

 

Also the possibility to blacklist certain devices yourself. For example my M.2 SSD doesn't like L1+ (L1.1 and L1.2) but the rest seems fine.

 

PS:

 

In the case you want to blacklist the M.2 for everybody.

 

I just upgraded to 7.0 and if I remove amd_pstate=passive from syslinux boot it defaults to ACPI driver. On my system it should now default to amd_pstate right? Anyway, if I add it back it now loads that driver. But can we actually use p_state=active now?

 

Regarding this plugin, this shouldn't be paired with tips and tweaks right? Since it's an "auto" plugin I'm a bit wary of installing it

On 2/10/2025 at 2:19 PM, Sptz87 said:

I just upgraded to 7.0 and if I remove amd_pstate=passive from syslinux boot it defaults to ACPI driver. On my system it should now default to amd_pstate right? Anyway, if I add it back it now loads that driver. But can we actually use p_state=active now?

So far I know amd_pstate is not on per default because of various possible hardware and UEFI configurations. Your UEFI must have CPPC enabled (something the kernel can't do by itself), for example possibly found in CBS > NBIO > SMU > CPPC. So you still need to put amd_pstate=active as a boot entry and choose either the powersave or performance governor after booting. I would choose the former until your workload require that extra few ms latency.

 

On 2/10/2025 at 2:19 PM, Sptz87 said:

 

Regarding this plugin, this shouldn't be paired with tips and tweaks right? Since it's an "auto" plugin I'm a bit wary of installing it

The only incompatibility I know are the entry for CPU governors that can override each other. As for myself I have have stopped using Autotweak because of random USB stability issues either after days, sometimes after weeks of use. For now I enforce sleep on my NVIDIA GPU and limit the cTDP of my CPU while also allowing my disks to spin off.

An alternative would be installing and using powertop: allow L0 and L1 in your UEFI PCIE settings to be sure, use --auto-tune-dump once and blacklist NVME, USB and any device known to be notorious as a user script.

 

The NVME Issue was gone with a newer device since I reached far over the max TBW value and replaced said NVME in time.

Edited April 20, 20251 yr by InternetD

I really like this plugin and use it on both my servers, but would it be possible to add a function to set a specific power profile best on a cron job?
One server I use to host a couple of VMs for coworkers and would like to set the power profile to performance, but at the end of the workday I like to it to set to power saving mode.

The best way would be if it could be setup based on a cron job.

 

Thanks allot in advance

17 hours ago, brainbudt said:

I really like this plugin and use it on both my servers, but would it be possible to add a function to set a specific power profile best on a cron job?
One server I use to host a couple of VMs for coworkers and would like to set the power profile to performance, but at the end of the workday I like to it to set to power saving mode.

The best way would be if it could be setup based on a cron job.

 

Thanks allot in advance

All of the features of the GUI is available in the script used by the GUI. "Power profile" setting on GUI uses these two functions:

 

/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_scaling_governor 
/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_cpu_performance_preference 

 

If you execute them they give you a little help about the possible parameters.

You can set powersave "Power profile" like this:

/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_scaling_governor "powersave"
/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_cpu_performance_preference "balance_power"

 

And you can set performance "Power profile" like this:

 

/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_scaling_governor "performance"
/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_cpu_performance_preference "performance"

 

And you can set balanced "Power profile" like this:

/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_scaling_governor "powersave"
/usr/local/emhttp/plugins/autotweak/scripts/autotweak set_cpu_performance_preference "balance_performance"

 

These log their output into /var/log/syslog.

Just be aware that these functions do not modify permanently these parameters (not saved in the config). So if you open the GUI you will see that last set "Power profile". And if you modify any parameter the GUI will reapply that "Power profile".

Thanks allot! This will work perfectly for me.

I see this on initialization sometimes. No idea what this is about.

On 5/6/2025 at 3:32 PM, andrebrait said:

I see this on initialization sometimes. No idea what this is about.

Does this happen only during boot? Can you post the full log when you modify something in the plugin's GUI and apply the changes? What type of network card/chip is in your system?

On 6/23/2025 at 8:48 PM, Fuzzy0101 said:

Does this happen only during boot? Can you post the full log when you modify something in the plugin's GUI and apply the changes? What type of network card/chip is in your system?

Only during boot, as far as I can tell.

As for network card, the only NIC enabled is an Intel X710-DA2.

Here are the logs from applying settings:

Jul 22 02:30:13 NAS ool www[1128898]: /usr/local/emhttp/plugins/autotweak/scripts/autotweak 'apply'
Jul 22 02:30:13 NAS autotweak: Appply powersupersave profile
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 0
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 1
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 10
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 11
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 12
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 13
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 14
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 15
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 2
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 3
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 4
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 5
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 6
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 7
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 8
Jul 22 02:30:13 NAS autotweak: Set scaling governor to powersave for CPU 9
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 0
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 1
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 10
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 11
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 12
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 13
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 14
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 15
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 2
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 3
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 4
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 5
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 6
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 7
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 8
Jul 22 02:30:13 NAS autotweak: Set performance preference to power for CPU 9
Jul 22 02:30:13 NAS autotweak: Set HWP Dynamic Boost to 1
Jul 22 02:30:13 NAS autotweak: Set no_turbo to 0
Jul 22 02:30:13 NAS autotweak: Failed to set ASPM policy
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:00.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:01.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:02.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:08.0
Jul 22 02:30:13 NAS autotweak: Skipping device 0000:00:14.0 with banned driver: xhci_hcd
Jul 22 02:30:13 NAS autotweak: Skipping device 0000:00:16.0 with banned driver: mei_me
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:17.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1b.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1b.2
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1b.3
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1b.4
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1c.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1c.4
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1d.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1f.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1f.2
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:00:1f.4
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:01:00.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:05:00.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:07:00.0
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:07:00.1
Jul 22 02:30:13 NAS autotweak: PCIe PM control set to 'auto' for device 0000:08:00.0
Jul 22 02:30:13 NAS autotweak: PM control set to 'auto' for ata device ata1
Jul 22 02:30:13 NAS autotweak: PM control set to 'auto' for ata device ata2
Jul 22 02:30:13 NAS autotweak: PM control set to 'auto' for ata device ata3
Jul 22 02:30:13 NAS autotweak: PM control set to 'auto' for ata device ata4
Jul 22 02:30:13 NAS autotweak: PM control set to 'auto' for ata device ata5
Jul 22 02:30:13 NAS autotweak: PM control set to 'auto' for ata device ata6
Jul 22 02:30:13 NAS autotweak: Set SATA link power management to med_power_with_dipm for host2
Jul 22 02:30:13 NAS autotweak: Set SATA link power management to med_power_with_dipm for host3
Jul 22 02:30:13 NAS kernel: ahci 0000:00:17.0: port does not support device sleep
Jul 22 02:30:13 NAS autotweak: Set SATA link power management to med_power_with_dipm for host4
Jul 22 02:30:13 NAS kernel: ahci 0000:00:17.0: port does not support device sleep
Jul 22 02:30:13 NAS autotweak: Set SATA link power management to med_power_with_dipm for host5
Jul 22 02:30:13 NAS kernel: ahci 0000:00:17.0: port does not support device sleep
Jul 22 02:30:13 NAS autotweak: Set SATA link power management to med_power_with_dipm for host6
Jul 22 02:30:13 NAS kernel: ahci 0000:00:17.0: port does not support device sleep
Jul 22 02:30:13 NAS autotweak: Set SATA link power management to med_power_with_dipm for host7
Jul 22 02:30:13 NAS kernel: ahci 0000:00:17.0: port does not support device sleep
Jul 22 02:30:13 NAS autotweak: Set nvme0 APST table entry 0 Next state: 3 Timeout: 50
Jul 22 02:30:13 NAS autotweak: Set nvme0 APST table entry 1 Next state: 3 Timeout: 50
Jul 22 02:30:13 NAS autotweak: Set nvme0 APST table entry 2 Next state: 3 Timeout: 50
Jul 22 02:30:13 NAS autotweak: Set nvme0 APST table entry 3 Next state: 4 Timeout: 500
Jul 22 02:30:14 NAS autotweak: Set nvme0 APST policy to powersupersave
Jul 22 02:30:14 NAS autotweak: Set nvme1 APST table entry 0 Next state: 3 Timeout: 50
Jul 22 02:30:14 NAS autotweak: Set nvme1 APST table entry 1 Next state: 3 Timeout: 50
Jul 22 02:30:14 NAS autotweak: Set nvme1 APST table entry 2 Next state: 3 Timeout: 50
Jul 22 02:30:14 NAS autotweak: Set nvme1 APST table entry 3 Next state: 4 Timeout: 500
Jul 22 02:30:14 NAS autotweak: Set nvme1 APST policy to powersupersave
Jul 22 02:30:14 NAS autotweak: Banned CPUs for network interface interrupt affinity: 0,12
Jul 22 02:30:14 NAS autotweak: Usable CPUs for eth0: 1-11,13-15
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 191 and tx queue 0 of eth0 to CPU 1
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 192 and tx queue 1 of eth0 to CPU 2
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 193 and tx queue 2 of eth0 to CPU 3
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 194 and tx queue 3 of eth0 to CPU 4
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 195 and tx queue 4 of eth0 to CPU 5
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 196 and tx queue 5 of eth0 to CPU 6
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 197 and tx queue 6 of eth0 to CPU 7
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 198 and tx queue 7 of eth0 to CPU 8
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 199 and tx queue 8 of eth0 to CPU 9
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 200 and tx queue 9 of eth0 to CPU 10
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 201 and tx queue 10 of eth0 to CPU 11
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 202 and tx queue 11 of eth0 to CPU 13
Jul 22 02:30:14 NAS autotweak: Set CPU affinity of interrupt 203 and tx queue 12 of eth0 to CPU 14
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 204 and tx queue 13 of eth0 to CPU 15
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 205 and tx queue 14 of eth0 to CPU 1
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 206 and tx queue 15 of eth0 to CPU 2
Jul 22 02:30:15 NAS autotweak: Usable CPUs for eth1: 1-11,13-15
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 217 and tx queue 0 of eth1 to CPU 3
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 218 and tx queue 1 of eth1 to CPU 4
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 219 and tx queue 2 of eth1 to CPU 5
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 220 and tx queue 3 of eth1 to CPU 6
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 221 and tx queue 4 of eth1 to CPU 7
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 222 and tx queue 5 of eth1 to CPU 8
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 223 and tx queue 6 of eth1 to CPU 9
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 224 and tx queue 7 of eth1 to CPU 10
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 225 and tx queue 8 of eth1 to CPU 11
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 226 and tx queue 9 of eth1 to CPU 13
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 227 and tx queue 10 of eth1 to CPU 14
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 228 and tx queue 11 of eth1 to CPU 15
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 229 and tx queue 12 of eth1 to CPU 1
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 230 and tx queue 13 of eth1 to CPU 2
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 231 and tx queue 14 of eth1 to CPU 3
Jul 22 02:30:15 NAS autotweak: Set CPU affinity of interrupt 232 and tx queue 15 of eth1 to CPU 4
Jul 22 02:30:15 NAS autotweak: Maximum interface speed: 10000 Mb/s
Jul 22 02:30:15 NAS autotweak: TCP parameters optimized

As for the SATA power management options, it would be probably better to have a clear warning about min_power in particular, since it's a riskier option, according to the Arch Wiki

If I uninstall the plugin it will revert to default everything?

It applies settings on boot right?

On 6/23/2025 at 8:48 PM, Fuzzy0101 said:

Does this happen only during boot? Can you post the full log when you modify something in the plugin's GUI and apply the changes? What type of network card/chip is in your system?

@Fuzzy0101 after further investigating, I noticed that:

1. It always happens when I apply settings

2. It stops happening when I pass pcie_aspm=force to the kernel

3. It stops happening when I enable Native ASPM in the UEFI

So I think what's happening here is that it cannot write to /sys/module/pcie_aspm/parameters/policy.

Under some circumstances, this is not writable, such as when the BIOS is controlling ASPM.

I think you should add 1) log a better error message when this fails to be written, and 2) grey out the field for the plugin's page and an explanation of why it cannot be triggered.

Lastly, I'd like to ask you to add a caution message for the Powersave option for SATA. This is known to cause data corruption with some hardware combinations out there, so it would be best if there was a clear warning.

Also, I think the Power Profile option is changing /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference, right?

Does it also do anything for /sys/devices/system/cpu/cpu*/power/energy_perf_bias ? It's essentially the same, but with less values and it might be used when the first is not available, and uses/accepts the following values (both strings and numbers are accepted): “performance” = 0, “balance-performance” = 4, “normal”= 6, “balance-power”= 8, “power” = 15.

ps.: it uses - instead of _ , unliked /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference, which takes one of "performance", "balance_performance", "balance_power power".

Edited August 19, 2025Aug 19 by andrebrait

Maybe a status update, hardly any code survives two years without patching and major version changes...