Ubuntu – Fan is always on, CPU usage is rather low and can’t find the fan or thermal_zone proc files

acpifancontrolpower-management

I have an Asus N76VB notebook with Ubuntu 14.04 and TLP for power managment. However, the fan is always on. It's not really loud, but it's annoying. My CPU usage is around 1-2%. It's clocked at 1.20 GHz.

I've added acpi=force to my boot parameters but it doesn't change anything.

/proc/acpi/fan: No such file or directory
/proc/acpi/thermal_zone: No such file or directory

I've loaded all Asus ACPI modules.

lsmod | grep asus:

asus_nb_wmi            16990  0 
asus_wmi               24191  1 asus_nb_wmi
sparse_keymap          13948  1 asus_wmi
video                  19476  2 i915,asus_wmi
wmi                    19177  2 mxm_wmi,asus_wmi

Somehow, it can read the temperatures.

sensors:

acpitz-virtual-0
Adapter: Virtual device
temp1:        +43.0°C  (crit = +108.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +44.0°C  (high = +87.0°C, crit = +105.0°C)
Core 0:         +44.0°C  (high = +87.0°C, crit = +105.0°C)
Core 1:         +42.0°C  (high = +87.0°C, crit = +105.0°C)
Core 2:         +39.0°C  (high = +87.0°C, crit = +105.0°C)
Core 3:         +39.0°C  (high = +87.0°C, crit = +105.0°C)

asus-isa-0000
Adapter: ISA adapter
temp1:        +43.0°C  

I really hope someone knows how to solve this. Almost all information I could find was about saving power to create less heat.


I got Intel and NVIDIA (GeForce 740M) graphics but I'm almost anytime on Intel.

$ sudo lshw -c display
  *-display               
       description: VGA compatible controller
       product: 3rd Gen Core processor Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:43 memory:f7400000-f77fffff memory:d0000000-dfffffff ioport:f000(size=64)

fwts fan:

http://pastebin.com/tCRW4Tn6

Best Answer

  • Canonical developed something called FWTS which will systematically test the ACPI features provided and report on their health and possible corrective solutions. Run it and post the contents here (pastbin please) and to a launchpad bug against the linux-kernel.

    At a minimum run the "thermal_trip fan" tests.

    [continued using results from FWTS]

    Test 2 of 2: Load system, check CPU fan status.
    Test how many fans there are in the system. Check for the current status of the
    fan(s).
    Loading CPUs for 20 seconds to try and get fan speeds to change.
    Fan cooling_device0 current state did not change from value 0 while CPUs were
    busy.
    Fan cooling_device1 current state did not change from value 0 while CPUs were
    busy.
    Fan cooling_device2 current state did not change from value 0 while CPUs were
    busy.
    Fan cooling_device3 current state did not change from value 0 while CPUs were
    busy.
    Fan cooling_device4 current state did not change from value 0 while CPUs were
    busy.
    Fan cooling_device5 current state did not change from value 0 while CPUs were
    busy.
    Fan cooling_device6 current state did not change from value 0 while CPUs were
    busy.
    Fan cooling_device7 current state did not change from value 0 while CPUs were
    busy.
    
    ADVICE: Did not detect any change in the CPU related thermal cooling device
    states. It could be that the devices are returning static information back to
    the driver and/or the fan speed is automatically being controlled by firmware
    using System Management Mode in which case the kernel interfaces being examined
    may not work anyway.
    

    OK. That confirms the issue, there's no feedback.

    It doesn't appear that you have the asus-laptop module installed. Sometimes these laptop specific support modules do the trick for these components

    $ sudo modprobe asus-laptop
    

    This appears to have worked at one time, Ubuntu 12.04 on asus n76vb fan speed not working, which would make your case a regression. Unfortunately in that case the remedy was "I updated a bunch of stuff and it worked" :(.

  • Related Question