Hello,
Is there any way to adjust ventilation speed?
Thank you 
best regards
1 Like
So github app is not working.
Fan speed control - ArchWiki
joe@joe-Asusgx502gw ~ $ sudo sensors-detect
[sudo] password for joe:
# sensors-detect version 3.6.0+git
# System: ASUSTeK COMPUTER INC. Zephyrus S GX502GW_GX502GW [1.0] (laptop)
# Board: ASUSTeK COMPUTER INC. GX502GW
# Kernel: 6.6.83-1-MANJARO x86_64
# Processor: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (6/158/10)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
AMD Family 19h thermal sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Using driver `i2c-i801' for device 0000:00:1f.4: Cannon Lake-H (PCH)
Module i2c-dev loaded successfully.
Next adapter: i915 gmbus dpb (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpc (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus misc (i2c-2)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpd (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: AUX A/DDI A/PHY A (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: SMBus I801 adapter at efa0 (i2c-5)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x48
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410/ADT7420'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP435'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... No
Client found at address 0x52
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor chip!)
Next adapter: Synopsys DesignWare I2C adapter (i2c-6)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-7)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-9)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-10)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 7 at 1:00.0 (i2c-11)
Do you want to scan it? (yes/NO/selectively): y
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Do you want to generate /etc/conf.d/lm_sensors? (YES/no): y
Created symlink '/etc/systemd/system/multi-user.target.wants/lm_sensors.service' → '/usr/lib/systemd/system/lm_sensors.service'.
Unloading i2c-dev... OK
joe@joe-Asusgx502gw ~ $ pwmconfig
You need to be root to run this script.
joe@joe-Asusgx502gw ~ $ sudo pwmconfig
# pwmconfig version 3.6.0+git
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
/usr/bin/pwmconfig: There are no pwm-capable sensor modules installed
Thank you
At this stage, you’ve only performed a basic check with sensors-detect (section 1.1).
Please refer to the Arch Wiki and follow the steps up to section 1.4.
FYI : Why Github is not working. (orphand, out of date)
yay asus-fan-control
2 aur/asus-fan-control 3.13.0-1 (+3 0.00) (Orphaned)
Fan control for ASUS devices running Linux.
1 aur/asus-fan-dkms-git v0.9.1.r54.gd9ccff8-1 (+11 0.00) (Out-of-date: 2023-10-19)
Kernel module allowing to control (both) fan inside various ASUS laptops
The package is orphand. Need to be maintained.
1 Like
I stoped after Section 1.2, because in the cli
1 Like
What is the output of this
sudo sensors
and if excist
cat /etc/conf.d/lm_sensors
Look if you can find RPM in the output.
sudo sensors | grep RPM # or rpm
sudo sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +50.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +45.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +48.0°C (high = +100.0°C, crit = +100.0°C)
Core 2: +46.0°C (high = +100.0°C, crit = +100.0°C)
Core 3: +50.0°C (high = +100.0°C, crit = +100.0°C)
Core 4: +45.0°C (high = +100.0°C, crit = +100.0°C)
Core 5: +48.0°C (high = +100.0°C, crit = +100.0°C)
ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.00 A)
pch_cannonlake-virtual-0
Adapter: Virtual device
temp1: +49.0°C
BAT0-acpi-0
Adapter: ACPI interface
in0: 15.40 V
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +38.0°C
asus-isa-0000
Adapter: ISA adapter
cpu_fan: 2500 RPM
gpu_fan: 2500 RPM
nvme-pci-0200
Adapter: PCI adapter
Composite: +38.9°C (low = -273.1°C, high = +80.8°C)
(crit = +81.8°C)
Sensor 1: +38.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +38.9°C (low = -273.1°C, high = +65261.8°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +45.0°C
cat /etc/conf.d/lm_sensors
# Generated by sensors-detect on Sun Mar 30 07:13:36 2025
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).
HWMON_MODULES="coretemp"
1 Like
First another check .
What kernel do you use.
Because another kernel could solve this issue.
uname -r
And specs of your machine.
inxi -Fxxc0
1 Like
If you want to see all installed kernels:
mhwd-kernel -li
To see available kernels in Manjaro/Mabox:
mhwd-kernel -l
1 Like
I found this
yay nbfc-linux
Getting started with the GUI
After installing NBFC-Linux you can configure it by running sudo nbfc-qt.
uname -r
6.6.84-1-MANJARO
inxi -Fxxc0
System:
Host: joe-Asusgx502gw Kernel: 6.6.84-1-MANJARO arch: x86_64 bits: 64
compiler: gcc v: 14.2.1
Desktop: Xfce v: N/A wm: Openbox dm: LightDM Distro: Mabox
base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: Zephyrus S GX502GW_GX502GW v: 1.0
serial: <superuser required>
Mobo: ASUSTeK model: GX502GW v: 1.0 serial: <superuser required>
UEFI: American Megatrends v: GX502GW.312 date: 01/05/2021
Battery:
ID-1: BAT0 charge: 62.7 Wh (79.7%) condition: 78.7/76.1 Wh (103.4%)
volts: 15.4 min: 15.4 model: ASUSTeK ASUS Battery serial: N/A
status: not charging
CPU:
Info: 6-core model: Intel Core i7-9750H bits: 64 type: MT MCP
arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
Speed (MHz): avg: 900 min/max: 800/4500 cores: 1: 900 2: 900 3: 900 4: 900
5: 900 6: 900 7: 900 8: 900 9: 900 10: 900 11: 900 12: 900 bogomips: 62431
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: none
bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: NVIDIA TU106BM [GeForce RTX 2070 Mobile / Max-Q] vendor: ASUSTeK
driver: nvidia v: 570.133.07 arch: Turing pcie: speed: 2.5 GT/s lanes: 8
ports: active: none empty: DP-1,HDMI-A-1,eDP-2 bus-ID: 01:00.0
chip-ID: 10de:1f50
Display: x11 server: X.Org v: 21.1.16 compositor: Picom v: 12.5 driver: X:
loaded: modesetting,nvidia unloaded: fbdev alternate: nouveau,nv,vesa
dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: eDP-1 model: Sharp LQ156M1JW09 res: 1920x1080 hz: 240 dpi: 142
diag: 395mm (15.5")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: iris inactive: wayland
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 25.0.2-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
GT2) device-ID: 8086:3e9b
Info: Tools: api: eglinfo,glxinfo gpu: nvidia-settings,nvidia-smi
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a348
Device-2: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 8 bus-ID: 01:00.1
chip-ID: 10de:10f9
API: ALSA v: k6.6.84-1-MANJARO status: kernel-api with: aoss
type: oss-emulator
Server-1: sndiod v: N/A status: off
Server-2: JACK v: 1.9.22 status: off
Server-3: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370
IF: wlo1 state: up mac: d0:ab:d5:01:e7:12
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168
IF: eno2 state: down mac: 04:d4:c4:7b:df:ad
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-14:4
chip-ID: 8087:0aaa
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 953.87 GiB used: 271.35 GiB (28.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB1T0HALR-00000
size: 953.87 GiB speed: 31.6 Gb/s lanes: 4 serial: S3W6NX0M522177
temp: 27.9 C
Partition:
ID-1: / size: 937.53 GiB used: 271.35 GiB (28.9%) fs: ext4
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 299.4 MiB used: 288 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: N/A pch: 43.0 C mobo: N/A
Fan Speeds (rpm): cpu: 2400
Info:
Memory: total: 32 GiB available: 31.2 GiB used: 3.63 GiB (11.6%)
Processes: 306 Power: uptime: 5h 26m wakeups: 3 Init: systemd v: 257
default: graphical
Packages: pm: pacman pkgs: 1170 Compilers: gcc: 14.2.1 Shell: Bash
v: 5.2.37 running-in: terminator inxi: 3.3.37
mhwd-kernel -li
Currently running: 6.6.84-1-MANJARO (linux66)
The following kernels are installed in your system:
* linux66
mhwd-kernel -l
* linux510
* linux515
* linux54
* linux61
* linux612
* linux613
* linux614
* linux66
* linux61-rt
* linux612-rt
* linux613-rt
* linux66-rt
Something is controlling my vent - because if I make something it works faster - but never turn off - even at 40C…
Do you mean to install nbfc-linux?
Yes.
It looks quite userfriendly way, with GUI.
It is a fork of the original NBFC. (not maintained anymore)
search for nbfc on
And follow the way to this fork on github. The fork is called nbfc-linux. There is also a git version.
yay nbfc-linux
I am curious if this will work.
1 Like
There were 2 versions. Nbfc-linux 0.2.7-1 and 0.2.7.r13. I choose the 0.2.7-1.
sudo nbfc-qt
[sudo] password for joe:
sudo: nbfc-qt: command not found
Try the other one.
The readme is from git version.
So maybe only git version has gui.
yay -S nbfc-linux-git
Yep GUI is working, but not working…
I can start, has recommendations, but no effects. Can see the temp, but no for the rev, and so. 
I think we should try with manual ortodox method = gui.
I read through the config possibilities…
So the only thing I would like to reach to turn off the vent under 50C.
Did you try…
nbfc config -r
If there is at least one model, try to apply this profile and see how fan speeds are being handled.
For example:
$ nbfc config -a "Asus Zenbook UX430UA"
1 Like
Can you give output from…
ls /opt/nbfc/Configs/
1 Like