CPU / FANS detection

Hey there,
I’m new to Garuda, came from windows. I am trying to get my system to see my sensors but so far I’ve had no luck.
I have tried using sensors-detect but it reports that I have no sensors. I can see my CPU utilization, clockspeed but not power consumption for some reason, and I can see everything about the GPU except for fans.
None of the case fans are recognized by the system either and I’m not sure why. I tried to look for the sensors manually in system monitor for example but since they weren’t detected in the first place I couldn’t find them.
I have a ryzen 7700 and a 9070 xt.

>>sensors
amdgpu-pci-1100
Adapter: PCI adapter
vddgfx:      930.00 mV
vddnb:         1.19 V
edge:         +36.0°C
PPT:          30.16 W

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +41.5°C
Tccd1:        +34.4°C

nvme-pci-1000
Adapter: PCI adapter
Composite:    +43.9°C  (low  =  -5.2°C, high = +83.8°C)
(crit = +87.8°C)

amdgpu-pci-0300
Adapter: PCI adapter
vddgfx:      261.00 mV
fan1:             N/A
edge:         +50.0°C  (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
junction:     +53.0°C  (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
mem:          +72.0°C  (crit = +108.0°C, hyst = -273.1°C)
(emerg = +113.0°C)
PPT:          40.00 W  (cap = 304.00 W)

nvme-pci-0d00
Adapter: PCI adapter
Composite:    +39.9°C  (low  =  -0.1°C, high = +99.8°C)
(crit = +109.8°C)

and this is the output for sensors-detect --auto:

# sensors-detect version 3.6.0+git
# System: ASRock B650M-HDV/M.2 [Default string]
# Kernel: 6.13.8-zen1-1-zen x86_64
# Processor: AMD Ryzen 7 7700 8-Core Processor (25/97/2)

Running in automatic mode, default answers to all questions
are assumed.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
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...                             No
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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd802
(logical device B has address 0x290, could be sensors)
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 systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     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):
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):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-2)
Do you want to scan it? (YES/no/selectively):
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 0x4a
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

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-3)
Do you want to scan it? (YES/no/selectively):

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-4)
Do you want to scan it? (YES/no/selectively):

Next adapter: AMDGPU SMU 0 (i2c-5)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU SMU 1 (i2c-6)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-7)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-8)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-9)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-10)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM aux hw bus 0 (i2c-11)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM aux hw bus 1 (i2c-12)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-13)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-14)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-15)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-16)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM aux hw bus 1 (i2c-17)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM aux hw bus 2 (i2c-18)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM aux hw bus 3 (i2c-19)
Do you want to scan it? (yes/NO/selectively):

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

Did you use sensors in terminal?

sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +52.0°C  

nvme-pci-0200
Adapter: PCI adapter
Composite:    +37.9°C  (low  = -273.1°C, high = +83.8°C)
                       (crit = +84.8°C)
Sensor 1:     +37.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +43.9°C  (low  = -273.1°C, high = +65261.8°C)

amdgpu-pci-0300
Adapter: PCI adapter
vddgfx:        1.45 V  
vddnb:       918.00 mV 
edge:         +43.0°C  
PPT:           6.00 W  

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.20 V  
power1:        0.00 W  

Please follow the template and post your garuda-inxi .

5 Likes

sorry, in included it now.

Nope :slight_smile: thats sensors we need

3 Likes

ah okay I misunderstood

System:
Kernel: 6.13.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=e6303a30-442c-46c8-bcc1-cfc46737a3e6 rw rootflags=subvol=@
vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
quiet resume=UUID=37447aa4-f982-416d-93bd-5aea9fefe774 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B650M-HDV/M.2 serial: <filter>
uuid: 93006b9c-d919-0000-0000-000000000000 UEFI: American Megatrends LLC.
v: 3.10 date: 10/25/2024
CPU:
Info: model: AMD Ryzen 7 7700 socket: AM5 bits: 64 type: MT MCP arch: Zen 4
gen: 4 level: v4 note: check built: 2022+ process: TSMC n5 (5nm)
family: 0x19 (25) model-id: 0x61 (97) stepping: 2 microcode: 0xA601209
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB
desc: 8x1024 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3469 min/max: 545/5389 boost: enabled
base/boost: 3800/5350 scaling: driver: amd-pstate-epp governor: powersave
volts: 1.3 V ext-clock: 100 MHz cores: 1: 3469 2: 3469 3: 3469 4: 3469
5: 3469 6: 3469 7: 3469 8: 3469 9: 3469 10: 3469 11: 3469 12: 3469
13: 3469 14: 3469 15: 3469 16: 3469 bogomips: 121377
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [RX 9070/9070 XT]
vendor: Sapphire driver: amdgpu v: kernel pcie: gen: 5 speed: 32 GT/s
lanes: 16 ports: active: DP-2,HDMI-A-2 empty: DP-1,HDMI-A-1,Writeback-1
bus-ID: 03:00.0 chip-ID: 1002:7550 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: ASRock
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
empty: DP-3, DP-4, DP-5, HDMI-A-3, Writeback-2 bus-ID: 11:00.0
chip-ID: 1002:164e class-ID: 0300 temp: 33.0 C
Device-3: SHENZHEN EMEET Nova
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:2 chip-ID: 328f:2015
class-ID: 0300 serial: <filter>
Display: unspecified server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: :1 screens: 1
Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1355x381mm (53.35x15.00")
s-diag: 1408mm (55.42")
Monitor-1: DP-2 pos: primary,right model: Dell S2721DGF serial: <filter>
built: 2021 res: mode: 2560x1440 hz: 165 scale: 100% (1) dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-2 pos: left model: Acer XV272U serial: <filter>
built: 2020 res: mode: 2560x1440 hz: 144 scale: 100% (1) dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: radeonsi
surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.2-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
gfx1201 ACO DRM 3.61 6.13.8-zen1-1-zen) device-ID: 1002:7550
memory: 15.62 GiB unified: no
API: Vulkan v: 1.4.309 layers: 9 device: 0 type: discrete-gpu name: AMD
Radeon Graphics (RADV GFX1201) driver: N/A device-ID: 1002:7550
surfaces: xcb,xlib device: 1 type: integrated-gpu name: AMD Radeon
Graphics (RADV RAPHAEL_MENDOCINO) driver: N/A device-ID: 1002:164e
surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe (LLVM 19.1.7 256
bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel v: kernel
pcie: gen: 5 speed: 32 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab40
class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 11:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 11:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-4: SHENZHEN EMEET Nova
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:2 chip-ID: 328f:2015
class-ID: 0300 serial: <filter>
Device-5: beyerdynamic GmbH & KG LL Adapter
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-1.2.4:7 chip-ID: 2e50:002f class-ID: 0102
serial: <filter>
API: ALSA v: k6.13.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.1 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 09:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Microsoft Xbox Wireless Adapter for Windows driver: N/A
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.1:3
chip-ID: 045e:02fe class-ID: 0000 serial: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 4.59 TiB used: 29.35 GiB (0.6%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T3X0C-00SJG0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 111130WD temp: 30.9 C scheme: GPT
SMART: yes health: PASSED on: 1y 55d 22h cycles: 2,910
read-units: 99,864,435 [51.1 TB] written-units: 217,059,528 [111 TB]
ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: A-Data model: LEGEND 710
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: VC2SAD01 temp: 33.9 C
scheme: GPT
SMART: yes health: PASSED on: 203d 6h cycles: 1,486
read-units: 57,773,692 [29.5 TB] written-units: 19,288,231 [9.87 TB]
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2FR102
family: BarraCuda 3.5 (SMR) size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 7200
serial: <filter> fw-rev: 0001 temp: 27 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 10208h+09m+01.590s
cycles: 2937 read: 7.42 TiB written: 8.93 TiB Pre-Fail:
attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
Partition:
ID-1: / raw-size: 1.83 TiB size: 1.83 TiB (100.00%) used: 29.35 GiB (1.6%)
fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2 maj-min: 259:7
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 612 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
maj-min: 259:6
ID-3: /home raw-size: 1.83 TiB size: 1.83 TiB (100.00%)
used: 29.35 GiB (1.6%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:7
ID-4: /var/log raw-size: 1.83 TiB size: 1.83 TiB (100.00%)
used: 29.35 GiB (1.6%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:7
ID-5: /var/tmp raw-size: 1.83 TiB size: 1.83 TiB (100.00%)
used: 29.35 GiB (1.6%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.43 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
ID-2: swap-2 type: partition size: 33.48 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme1n1p3 maj-min: 259:8
Sensors:
System Temperatures: cpu: 38.1 C mobo: N/A
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 33.0 C device: amdgpu temp: 35.0 C mem: 57.0 C
watts: 45.00
Info:
Memory: total: 32 GiB note: est. available: 30.43 GiB used: 3.12 GiB (10.3%)
Processes: 416 Power: uptime: 0m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.16 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 1539 pm: pacman pkgs: 1526 libs: 472 tools: octopi,paru
pm: flatpak pkgs: 13 Compilers: clang: 19.1.7 gcc: 14.2.1
Shell: garuda-inxi (sudo) default: Bash v: 5.2.37 running-in: konsole
inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2025-03-24
Last full system update: 2025-03-26
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Yes
Failed units:
 cat /etc/sensors3.conf | paste
# libsensors configuration file
# -----------------------------
#
# This default configuration file only includes statements which do not
# differ from one mainboard to the next. Only label, compute and set
# statements for internal voltage and temperature sensors are included.
#
# In general, local changes should not be added to this file, but rather
# placed in custom configuration files located in /etc/sensors.d. This
# approach makes further updates much easier.
#
# Such custom configuration files for specific mainboards can be found in
# "configs" directory of lm-sensors package.
#
# Please contribute back a configuration of your board so other users with
# the same hardware won't need to recreate it again and again.

Maybe you can change it to your MB or search about in web.

Or

systemctl status fancontrol
○ fancontrol.service - Start fan control, if configured
     Loaded: loaded (/usr/lib/systemd/system/fancontrol.service; disabled; preset: disabled)
     Active: inactive (dead)

 ╭─sgs@y7p in ~ as 🧙 took 0s
 🕙 07:53:20
[🔴] × systemctl enable --now fancontrol
Created symlink '/etc/systemd/system/multi-user.target.wants/fancontrol.service' → '/usr/lib/systemd/system/fancontrol.service'.

 ╭─sgs@y7p in ~ as 🧙 took 4s
 🕙 07:54:08
 ╰─λ systemctl status fancontrol
○ fancontrol.service - Start fan control, if configured
     Loaded: loaded (/usr/lib/systemd/system/fancontrol.service; enabled; preset: disabled)
     Active: inactive (dead)
  Condition: start condition unmet at Wed 2025-03-26 07:54:08 CET; 3s ago
             └─ ConditionFileNotEmpty=/etc/fancontrol was not met

Mär 26 07:54:08 y7p systemd[1]: Start fan control, if configured was skipped because of an unmet condition check (ConditionFileNotEmpty=/etc/fancontrol).

Hi, sorry for the delay.

Maybe you can change it to your MB or search about in web.

I didn’t find a config file for my particular motherboard but I found one for another Asrock motherboard that supposedly uses the same (controller chip?) which is Nuvoton nct6796D. I installed the config and I can see much more than before, but for some reason I still can’t see the CPU power consumption.

sensors
amdgpu-pci-0300
Adapter: PCI adapter
vddgfx:      197.00 mV
fan1:           0 RPM  (min =    0 RPM, max = 5000 RPM)
edge:         +49.0°C  (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
junction:     +52.0°C  (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
mem:          +72.0°C  (crit = +108.0°C, hyst = -273.1°C)
(emerg = +113.0°C)
PPT:          35.00 W  (cap = 304.00 W)

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +41.4°C
Tccd1:        +34.9°C

nvme-pci-1000
Adapter: PCI adapter
Composite:    +43.9°C  (low  =  -5.2°C, high = +83.8°C)
(crit = +87.8°C)

amdgpu-pci-1100
Adapter: PCI adapter
vddgfx:      940.00 mV
vddnb:         1.19 V
edge:         +36.0°C
PPT:          25.16 W

r8169_0_900:00-mdio-0
Adapter: MDIO adapter
temp1:        +39.5°C  (high = +120.0°C)

nvme-pci-0d00
Adapter: PCI adapter
Composite:    +37.9°C  (low  =  -0.1°C, high = +99.8°C)
(crit = +109.8°C)

systemctl status fancontrol

I got the exact same output but I’m not sure what to do with that to be honest.

Hi Anassh,

did you try this? I did this for it.

sudo pacman -S lm_sensors

then for a grafical one this:

sudo pacman -S psensor

then detect sensors

sudo sensors-detect 

answer yes to all asking promts or particular if unclear about consequences :wink:

then check sensors again :wink:

Seems so.

:grin:

IIRC same output before installing and detect :wink:

did you try this?

Yes I tried it but sadly I still can’t see CPU power consumption.

You need to install zenpower3-dkms from AUR chaotic-aur to get the power consumption of the CPU.
paru -S zenpower3-dkms
sudo pacman -S zenwpower3-dkms

EDIT: Don´t know your CPU is supported and in some cases it doesn´t show correct values.

EDIT2: see post from @nepti below. Thanks to @nepti for correction.

3 Likes

Just a little hint, it is not necessary to install the AUR package, zenpower3-dkms is in chaotic-aur:

sudo pacman -S zenpower3-dkms
3 Likes

not sure if I’m doing something wrong but I installed the package and ran sensors-detect again but it detected no new sensors and the output of sensors is the same as before :sweat_smile:

:person_shrugging: :slightly_smiling_face:

it’s weird my cpu is neither super new nor is it obscure :sweat_smile:

have you tried a bios update? All to often such is the issue rather than the software.

3 Likes


:smiley:

1 Like

I didn’t try that, I guess that makes sense but i did an update before i installed garuda which caused me a ton of problems (it became a lottery whether PC would boot or not whenever I turn it on lol) so i reverted back to the original bios the board came with :sweat_smile:
I might try to update it again to another version

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.