You are not logged in.

#1 2020-02-19 04:05:16

aravindpallipara
Member
Registered: 2020-01-22
Posts: 13

Acer sf315-41 laptop cooling fan not detected in sensors

Here's the output of the

sensors-detect
# sensors-detect version 3.6.0
# System: Acer Swift SF315-41 [V2.12] (laptop)
# Board: RR Becks_RR
# Kernel: 5.5.4-arch1-1 x86_64
# Processor: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx (23/17/0)

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): 
Module cpuid loaded successfully.
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...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h 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'...               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): 
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
Module i2c-dev loaded successfully.

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: AMDGPU DM i2c hw bus 0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: dmdc (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

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

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

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


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK
Unloading cpuid... OK

And the output of

sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +49.9°C  (high = +70.0°C)
Tctl:         +49.9°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +50.0°C  (crit = +98.0°C)

ath10k_hwmon-pci-0100
Adapter: PCI adapter
temp1:        +45.0°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.90 V  

amdgpu-pci-0200
Adapter: PCI adapter
vddgfx:           N/A  
vddnb:            N/A  
edge:         +49.0°C  (crit = +80.0°C, hyst =  +0.0°C)

The fan speed or well fan itself isn't detected, that wouldn't bug me too much if fan was working while using linux - it isn't. Thankfully the temperature rarely rises above 60 C.
How can I solve this?
I tried mounting acerhdf module(which isn't loaded by default), which kept failing

modprobe acerhdf verbose=1 fanon=62000 fanoff=52000 interval=10 kernelmode=1

with

modprobe: ERROR: could not insert 'acerhdf': Invalid argument

What are the other avenues I should look to?

Last edited by aravindpallipara (2020-02-19 04:05:56)

Offline

Board footer

Powered by FluxBB