Auto Fan Boost

[ghost]

With help of AI I created a script to control fan boost based on cpu/gpu temperatures:

#!/usr/bin/env bash

CONFIG="auto_fan.conf"
CHECK_INTERVAL=5

declare -a CPU_RULES GPU_RULES
LAST_CPU_BOOST=""
LAST_GPU_BOOST=""

HYSTERESIS=3

LAST_CPU_TEMP=""
LAST_GPU_TEMP=""

# Load config
load_config() {
	local section=""
	while IFS= read -r line; do
		line=$(echo "$line" | sed 's/[[:space:]]//g')
		[[ -z "$line" || "$line" =~ ^# ]] && continue

		if [[ "$line" =~ ^\[(.*)\]$ ]]; then
			section="${BASH_REMATCH[1]}"
			continue
		fi

		if [[ "$line" =~ ^([0-9]+)-([0-9]+)=([0-9]+)$ ]]; then
			rule="${BASH_REMATCH[1]}-${BASH_REMATCH[2]}=${BASH_REMATCH[3]}"
			if [[ "$section" == "CPU" ]]; then
				CPU_RULES+=("$rule")
			elif [[ "$section" == "GPU" ]]; then
				GPU_RULES+=("$rule")
			fi
		fi
	done < "$CONFIG"
}

# Match temperature to a rule
match_boost() {
	local TEMP=$1
	local -n RULES=$2

	for rule in "${RULES[@]}"; do
		IFS='-=' read -r MIN MAX BOOST <<< "$rule"
		if (( TEMP >= MIN && TEMP <= MAX )); then
			echo "$BOOST"
			return
		fi
	done
	echo ""
}

check_g_mode() {
	awcc qm 2>/dev/null | grep -iq 'G-Mode'
}

get_temp_cpu() {
	sensors dell_ddv-virtual-0 | grep 'CPU:' | sed 's/\s\+/ /g' | cut -f 2 -d ' ' | tr -d '+' | sed 's/\..*//'
}

get_temp_gpu() {
	sensors dell_ddv-virtual-0 | grep 'Video:' | sed 's/\s\+/ /g' | cut -f 2 -d ' ' | tr -d '+' | sed 's/\..*//'
}

load_config

CLEANED=''

# Cleanup function to reset fan boost
cleanup() {
	[[ -z "$CLEANED" ]] || return
	CLEANED="YES"

	if ! check_g_mode; then
		echo "Exiting: resetting fan boosts to 0"
		awcc scb 0
		awcc sgb 0
	else
		echo "Exiting in G-Mode: leaving boosts unchanged"
	fi
	exit 0
}

# Trap script termination signals
trap cleanup SIGINT SIGTERM EXIT

while true; do
	if check_g_mode; then
		LAST_CPU_BOOST=""
		LAST_GPU_BOOST=""
		sleep "$CHECK_INTERVAL"
		continue
	fi

	CPU_TEMP=$(get_temp_cpu)
	GPU_TEMP=$(get_temp_gpu)

	[[ -z "$CPU_TEMP" || -z "$GPU_TEMP" ]] && sleep "$CHECK_INTERVAL" && continue

	CPU_BOOST=$(match_boost "$CPU_TEMP" CPU_RULES)
	GPU_BOOST=$(match_boost "$GPU_TEMP" GPU_RULES)

	if [[ -n "$CPU_BOOST" && "$CPU_BOOST" != "$LAST_CPU_BOOST" ]]; then
		if [[ -z "$LAST_CPU_TEMP" || $(( CPU_TEMP > LAST_CPU_TEMP + HYSTERESIS || CPU_TEMP < LAST_CPU_TEMP - HYSTERESIS )) -ne 0 ]]; then
			echo cpu "$CPU_TEMP $CPU_BOOST"
			awcc scb "$CPU_BOOST"
			LAST_CPU_BOOST="$CPU_BOOST"
			LAST_CPU_TEMP="$CPU_TEMP"
		fi
	fi

	if [[ -n "$GPU_BOOST" && "$GPU_BOOST" != "$LAST_GPU_BOOST" ]]; then
		if [[ -z "$LAST_GPU_TEMP" || $(( GPU_TEMP > LAST_GPU_TEMP + HYSTERESIS || GPU_TEMP < LAST_GPU_TEMP - HYSTERESIS )) -ne 0 ]]; then
			echo gpu "$GPU_TEMP $GPU_BOOST"
			awcc sgb "$GPU_BOOST"
			LAST_GPU_BOOST="$GPU_BOOST"
			LAST_GPU_TEMP="$GPU_TEMP"
		fi
	fi

	sleep "$CHECK_INTERVAL"
done

auto_fan.conf:

[CPU]
0-39=0
40-49=20
50-59=40
60-69=60
70-79=80
80-100=100

[GPU]
0-39=0
40-49=20
50-59=40
60-69=60
70-79=80
80-100=100

I don't make a pull request because I want to write it in C, but have no enough time right now.
Just wanted to share this script, and maybe someone will have a time to rewrite in C or review the code 🙂.
Would be nice to have a systemd unit with fan management.
The ChatGPT conversation: https://chatgpt.com/share/6851194a-5000-8013-bfb7-a78ea86cdc30

[tr1xem]

Looks nice I would add it in snippets

[tr1xem]

Weirdly for me fans are auto managed, if temps goes higher fan boost itself without and manual systemd service

[GasparVardanyan]

It's managed from bios, but it's not good enough 🙂

I've created a new branch and I'm planning to rewrite this in C.

[GasparVardanyan]

The current workarounds seem limited (only 3 boost levels for example) or dangerous (lm-sensors can damage the hardware with wrong usage): https://wiki.archlinux.org/title/Fan_speed_control#Dell_laptops

autoboost will be safe and flexible, just an automation of awcc boost control functionality.

[tr1xem]

It's managed from bios, but it's not good enough 🙂

I've created a new branch and I'm planning to rewrite this in C.

Well Thats awesome i could add cpu and gpu temps and fans rpm fetching in awcc itself as there are acpi calls for them too

[GasparVardanyan]

That's great! I think my progress will be slow for the C part, I'm busy now, you can wait until I rewrite this in C and then help with acpi calls. I don't want you to do the acpi part and wait for me ))

I've also added 10s delay before downboosting. Seems it's ready to be rewritten in C. This is what goings on: https://chatgpt.com/share/6851194a-5000-8013-bfb7-a78ea86cdc30

[GasparVardanyan]

I've added a systemd unit file, can you try and it? Does the current algorithm work well?

[tr1xem]

@GasparVardanyan could you add a dry run flag? which would only show what changes it would make ? not actually execute them

[GasparVardanyan]

Done. Now you can run script like sudo ./awcc_autoboost.sh dry. It will print the awcc scb and sgb commands instead of actually running them. I can't avoid sudo because it needs for qm. Also logging to /var/run/awcc is kept running, I think you don't have problem with it.
I'm can create a separate script which will assume always performance mode and work without sudo, just printing commands it wants to run.
I'm already working on the C part.

[GasparVardanyan]

I think it will be cool to give an option in configuration to switch modes too.
For example on 0-50°C temperatures we can use the balanced mode, after 50°C we can use the performance mode and enable the gaming mode after 90°C. What you think?

[GasparVardanyan]

I want to have the full picture what config file will look like to start implementing the basic stuff.

[GasparVardanyan]

We use 0xA1 for "Performance" mode in ACPI calls, but according to kernel.org it's the "Balanced Performance" mode, and there's a separate "Performance" mode 0xA4: https://docs.kernel.org/wmi/devices/alienware-wmi.html
Also the "GMODE replaces PERFORMANCE in G-Series laptops." part looks confusing for me.
Maybe we have to update the thermal profile control ACPI calls? I think we need the "Cool" mode 🙂
@tr1xem

[tr1xem]

Done. Now you can run script like sudo ./awcc_autoboost.sh dry. It will print the awcc scb and sgb commands instead of actually running them. I can't avoid sudo because it needs for qm. Also logging to /var/run/awcc is kept running, I think you don't have problem with it. I'm can create a separate script which will assume always performance mode and work without sudo, just printing commands it wants to run. I'm already working on the C part.

I think a bash daemon would be better than c? cuz its just a serivce right? dosent matter if its c and ig bash would be better as we could skip complexity

[tr1xem]

I want to have the full picture what config file will look like to start implementing the basic stuff.

I was thinking that of too with gui
Custom option would be great too I support that idea

[tr1xem]

We use 0xA1 for "Performance" mode in ACPI calls, but according to kernel.org it's the "Balanced Performance" mode, and there's a separate "Performance" mode 0xA4: https://docs.kernel.org/wmi/devices/alienware-wmi.html Also the "GMODE replaces PERFORMANCE in G-Series laptops." part looks confusing for me. Maybe we have to update the thermal profile control ACPI calls? I think we need the "Cool" mode 🙂 @tr1xem

Just noticed that But oddly 0xA1 is the performance mode as i have experienced

#!/bin/bash

c(){ echo "$1" | sudo tee /proc/acpi/call >/dev/null && sudo cat /proc/acpi/call;echo;}

for mode in 0xa{0..9} 0xa{a..b}
do
    echo "Trying mode ${mode}"
    echo "\_SB.AMWW.WMAX 0 0x15 {0x01, ${mode}, 0x00, 0x00}"
    c "\_SB.AMWW.WMAX 0 0x15 {0x01, ${mode}, 0x00, 0x00}"
done
echo "Reverting to balanced."
c "\_SB.AMWW.WMAX 0 0x15 {0x01, 0xa0, 0x00, 0x00}"

you could run this and see it on your own if you get any difference b/w 0xA1 and 0xA4
maybe the docs are outdated?

Gmode replaces performance mode is about platform profiles i suppose

In kernel docs

Note

The following method description may be incomplete and some operations have different implementations between devices.

[tr1xem]

@GasparVardanyan I reviewed and compiled it myself
It works good so far but there are few problem

• GetModeName function is bugged Return's performance mode in balance mode for me

• I guess you got the wrong logic about fan boost %

Idk if this is correct but i hope this is how it works

IF your cpu boost is 20% it means it would take ur current cpu fan rpm and add 20% of total rpm to it (cuz i have noticed my fan goes to full speed at 50% boost

• It is too senstive

Ex:

CPU BOOST  60 INTERVAL 4 UPSHIFT 0
        CPU 62[0] GPU 30[0]
        CPU 62[0] GPU 30[0]

Saying me to get to 60% boost while dell itself dont turn on fans at 65+ ( i know you could manually configure them but we have to still get close default values)

• I guess you have to first switch to manual mode then set boost (just my assumption)

• For me GPU is powered off 99% of time but yeah it cools both places ( also depends on device tho g16 and 15 have almost same design)

I would try to reverse engineer windows' awcc to see if we could get some resource neither we have to work on assumptions

The code looks good to me turn out to be great

[GasparVardanyan]

• GetModeName function is bugged Return's performance mode in balance mode for me

That's weird. I've tested this:

		enum AWCCMode_t modes [] = {
			AWCCModeQuiet,
			AWCCModeBatterySaver,
			AWCCModeBalanced,
			AWCCModePerformance,
			AWCCModeG,
		};

		for (size_t i = 0; i < sizeof (modes) / sizeof (* modes); i++) {
			AWCC.SetMode (modes [i]);
			const enum AWCCMode_t mode = AWCC.GetMode ();
			assert (mode == modes [i]);
			printf ("::: Current Mode: %s\n", AWCC.GetModeName (mode));
			system ("awcc qm");
			thrd_sleep (& (struct timespec) {.tv_sec = 2}, NULL);
		}

and the output was:

[ autoboost ]   _ ./awcc_autoboost
::: Current Mode: Quiet
Current mode: Quiet
::: Current Mode: BatterySaver
Current mode: Battery Saver
::: Current Mode: Balanced
Current mode: Balanced
::: Current Mode: Performance
Current mode: Performance
::: Current Mode: G
Current mode: Gaming (G-Mode)

IF your cpu boost is 20% it means it would take ur current cpu fan rpm and add 20% of total rpm to it (cuz i have noticed my fan goes to full speed at 50% boost

But nothing changes when I exectue awcc scb 20 multiple times. I think "boost" works like 'level of additional power'.
On my laptop rpm get's highest at 100% boost (although g-mode seems to have higher rpm), 50% gives less speed. What happens on your laptop when you set boost to 100?

Saying me to get to 60% boost while dell itself dont turn on fans at 65+ ( i know you could manually configure them but we have to still get close default values)

That's from the default config: AWCCConfig.c. I'll work on config file support so you can set these values without recompiling awcc.

• I guess you have to first switch to manual mode then set boost (just my assumption)

Do modes e.g. Balanced, Performance differ just in fan speed control? If not, don't we need to have customizable boost levels available with these modes? Currently we have separate boost levels and modes for different temperature ranges. For mode I take maximum value of temperatures of cpu and gpu and then select the appropriate mode based on the config.

I would try to reverse engineer windows' awcc to see if we could get some resource neither we have to work on assumptions

Can I help you with this? I have saved my windows partitions on a separate hard drive with dd, so I have dell's official software for my device, but I don't have a bootable windows available.

The final goal for boost/mode management is to have a central place to do the acpi calls: the daemon, but for now I can edit awcc's main.c to use autoboost's AWCC.h interface so we can easily identify bugs if any. Also after this it'll be easier to integrate the light management to AWCC.h, it's flexible, it read's a value and set's a value, then you decide you want to just print it or do something else.

[GasparVardanyan]

• GetModeName function is bugged Return's performance mode in balance mode for me

I figured it out. Because seems you use DRY_RUN:

CPU BOOST 60 INTERVAL 4 UPSHIFT 0
CPU 62[0] GPU 30[0]
CPU 62[0] GPU 30[0]

SetMode doesn't actually change the mode, and GetMode returns the actual mode. After it GetModeName works according to the actual current mode.

[GasparVardanyan]

I've added logging on /var/run/awcc

[tr1xem]

@GasparVardanyan do you happen to have a discord account if yes we could connect there im tr1x_em at discord Or matrix

[tr1xem]

Here are my values for boost levels

At Boost = 0%
Balanced Mode

CPU Fan:     1224 RPM
Video Fan:   1363 RPM
CPU:          +63.0°C  (low  =  +0.0°C, high =  +0.0°C)
Video:        +30.0°C  (low  =  +0.0°C, high =  +0.0°C)

(It goes to 0 rpm if temp are under 60)

10% Boost = 1330 RPM
20% Boost = 1676 RPM
30% Boost = 1835 RPM
50% Boost = 2642 RPM
100% Boost = 5100 RPM

GMODE = 5100 RPM

[tr1xem]

Adapter: Virtual device
CPU Fan:        0 RPM
Video Fan:      0 RPM
CPU:          +59.0°C  (low  =  +0.0°C, high =  +0.0°C)
Video:        +50.0°C  (low  =  +0.0°C, high =  +0.0°C)

The thing i was talking about
Guess we have to wait for cold weather to see how boost does its effect

[tr1xem]

Do modes e.g. Balanced, Performance differ just in fan speed control? If not, don't we need to have customizable boost levels available with these modes? Currently we have separate boost levels and modes for different temperature ranges. For mode I take maximum value of temperatures of cpu and gpu and then select the appropriate mode based on the config.

It does more than that as if you see in quite mode ur gpu is locked to 30watt it manages power and diff stuffs too

Can I help you with this? I have saved my windows partitions on a separate hard drive with dd, so I have dell's official software for my device, but I don't have a bootable windows available.

Thanks but i have dell's offical software installed too

The final goal for boost/mode management is to have a central place to do the acpi calls: the daemon, but for now I can edit awcc's main.c to use autoboost's AWCC.h interface so we can easily identify bugs if any. Also after this it'll be easier to integrate the light management to AWCC.h, it's flexible, it read's a value and set's a value, then you decide you want to just print it or do something else.

yup thats great i would add A device identifier this sunday if you merge it so that we could modify it for diff devices Eg: Suppose i get performance mode but u dont so we could remove that map if device found, i quite like your approach honestly making it a like a library

Still have to figure out why lights are bugged in your model and "GUI" a lots of todo lol

[GasparVardanyan]

Ok, I'll work on merging. I've sent you a friend request on discord

[tr1xem]

I would be working on device identifiers and lights

[GasparVardanyan]

Now we have an intelligent boost down mechanism 🙂
GasparVardanyan@fbd0ed5

[Bdem1rel]

Hi, is the auto fan boost still actively being worked on? Appreciate your work.

[tr1xem]

@Bdem1rel https://github.com/tr1xem/AWCC/tree/main/autoboost u can build it and test it works for me and gaspar

[ghost]

Hi! Current state is good enough, but things get complicated and I started rewriting it in a better, flexible way. Not ready yet.

[tr1xem]

@Bdem1rel Autoboost if merged into main its working and is stable