Hello everyone! I installed Arch on my EeePC 901 and everything seems to run smoothly, until I noticed that the fan is not working. I did a little search on the forums, to check if someone already had to face something similar but with no success.
This is the output of pwmconfig:
# pwmconfig revision 5857 (2010-08-22)
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.
Found the following devices:
hwmon0 is acpitz
hwmon1/device is coretemp
hwmon2 is eeepc
Found the following PWM controls:
Giving the fans some time to reach full speed...
Found the following fan sensors:
hwmon2/fan1_input current speed: 0 ... skipping!
There are no working fan sensors, all readings are 0.
Make sure you have a 3-wire fan connected.
You may also need to increase the fan divisors.
See doc/fan-divisors for more information.
This is the output of fancontrol:
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration file
And this is the output of sensors:
Adapter: Virtual device
temp1: +62.0°C (crit = +85.0°C)
Adapter: ISA adapter
Core 0: +18.0°C (crit = +90.0°C)
Adapter: ISA adapter
fan1: 0 RPM
I'm pretty a newbie and I don't know what to do, is there someone who can give me some advice please?
Thanks to all.
Hey, congrats on your fresh install.
A non-working fan sounds dangerous though.
I don't own an eeePC, but there seem to be a number of packages in the AUR for those.
Have a look at this one - which sounds right to me by description: https://aur.archlinux.org/packages.php?ID=59044
Or one of the numerous wiki's here on Asus hardware has hints maybe (beware of outdated info relating to kernels <3.0): https://wiki.archlinux.org/index.php/Category:ASUS
But in fact usually the kernel autodetect should configure the fan for you.
It may help others to give you more direct input, if you post (1) your daemon array from rc.conf and (2) the output of
. Also look in
after boot for messages regarding the cpu scaling/fans.
I just re-read and see you already quote output from fancontrol, which maybe the package I link above.
If yes: Check if the daemon it needs is loaded (https://aur.archlinux.org/packages.php?ID=14774)
Last edited by Strike0 (2012-07-05 21:28:18)
Thank you for your answer, sorry but I can't check the forums too often...
The Wiki page about my model dosen't give any advice on this subject.
I installed the eeepc-fancontrol package, the daemon is running but the fan is still dead
Here is my modules and daemons from rc.conf:
MODULES=(rfkill acpi-cpufreq eeepc_laptop asus_eee bluetooth snd-hda-intel)
DAEMONS=(syslog-ng crond dbus acpid alsa networkmanager bluetooth sensors eeepc-fancontrol lxdm)
Here is an extract of dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] ACPI: SSDT 3f7aeb80 004F0 (v01 PmRef CpuPm 00003000 INTL 20060113)
[ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 13 pages/cpu @f6d28000 s31424 r0 d21824 u53248
[ 0.000000] pcpu-alloc: s31424 r0 d21824 u53248 alloc=13*4096
[ 0.000000] pcpu-alloc:  0  1
[ 0.000000] Initializing CPU#0
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] CPU 0 irqstacks, hard=f6408000 soft=f640a000
[ 0.003934] Initializing cgroup subsys cpuacct
[ 0.004052] CPU: Physical Processor ID: 0
[ 0.004056] CPU: Processor Core ID: 0
[ 0.004063] mce: CPU supports 5 MCE banks
[ 0.004081] CPU0: Thermal monitoring enabled (TM2)
[ 0.068794] CPU0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02
[ 0.106708] CPU 1 irqstacks, hard=f64ca000 soft=f64cc000
[ 0.006666] Initializing CPU#1
[ 0.120050] Brought up 2 CPUs
[ 0.140706] ACPI: SSDT 3f7ae180 0023C (v01 PmRef Cpu0Ist 00003000 INTL 20060113)
[ 0.141330] ACPI: SSDT (null) 0023C (v01 PmRef Cpu0Ist 00003000 INTL 20060113)
[ 0.143480] ACPI: SSDT 3f7ae450 00724 (v01 PmRef Cpu0Cst 00003001 INTL 20060113)
[ 0.144055] ACPI: SSDT (null) 00724 (v01 PmRef Cpu0Cst 00003001 INTL 20060113)
[ 0.144612] ACPI: SSDT 3f7ae0b0 000CC (v01 PmRef Cpu1Ist 00003000 INTL 20060113)
[ 0.145209] ACPI: SSDT (null) 000CC (v01 PmRef Cpu1Ist 00003000 INTL 20060113)
[ 0.145428] ACPI: SSDT 3f7ae3c0 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20060113)
[ 0.146619] ACPI: SSDT (null) 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20060113)
[ 0.188472] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.800625] cpuidle: using governor ladder
[ 0.800771] cpuidle: using governor menu
[ 2.353676] ACPI: Requesting acpi_cpufreq
[ 2.672731] microcode: CPU0 sig=0x106c2, pf=0x4, revision=0x212
[ 3.000420] microcode: CPU1 sig=0x106c2, pf=0x4, revision=0x212
[ 11.170288] asus_eee version 0.39a1 init sucessfully
[ 11.170304] asus_eee informs writable=1 is dangerous: think before writing, do not let your CPU burns out!
And here is the output of lsmod:
Module Size Used by
fuse 60090 2
asus_eee 8416 0
rfcomm 28281 8
bnep 7062 2
i915 388286 3
joydev 7695 0
btusb 10048 0
arc4 1118 2
i2c_algo_bit 4615 1 i915
drm_kms_helper 29171 1 i915
drm 170915 3 i915,drm_kms_helper
usbhid 31733 0
microcode 8825 0
intel_agp 8752 1 i915
intel_gtt 11229 3 i915,intel_agp
iTCO_wdt 10705 0
iTCO_vendor_support 1545 1 iTCO_wdt
serio_raw 3709 0
coretemp 4702 0
i2c_i801 7088 0
pcspkr 1455 0
psmouse 70891 0
evdev 7630 19
uas 7277 0
agpgart 21967 3 drm,intel_agp,intel_gtt
soundcore 4378 1 snd
thermal 6563 0
i2c_core 16653 8 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev,asus_eee
hid 67113 1 usbhid
video 9883 1 i915
ac 1796 0
battery 5085 0
button 3614 1 i915
eeepc_laptop 12813 0
pci_hotplug 20534 1 eeepc_laptop
sparse_keymap 2532 1 eeepc_laptop
acpi_cpufreq 5141 0
mperf 1023 1 acpi_cpufreq
processor 23783 1 acpi_cpufreq
sd_mod 26959 5
pata_acpi 2388 0
ata_generic 2391 0
ata_piix 19608 3
uhci_hcd 19776 0
libata 146119 3 pata_acpi,ata_generic,ata_piix
scsi_mod 112541 4 uas,usb_storage,libata,sd_mod
ehci_hcd 35958 0
I purged some clearly unrelated modules, sorry if the quotes are full of useless info but I don't know what I'm looking for...
Fan works fine on my eeepc 901 with eee-control and nothing in MODULES
@lspw: It is fine to post long console output here in the forum, but use [ code ] tags instead of [ quote ] please.
That way the box gets scroll bars for the output.
You have a lot of eee-specific daemons and modules loaded there.
It'll be interesting to read if stronnag's tip gets it working for you.
Tried as Stronnag said, but nothing changed.
In fact adding "blacklist eeepc_laptop" in /etc/modprobe.d/.conf is useless, the module is loaded even in that case.
I'm thinking that maybe is a problem connected with fan divisors, but I don't know how to change them since I can't find the correct section to edit in /etc/sensors3.conf and the only module noticed by sensors-detect is coretemp.
I have the same problem with 1001ha. See my posts. If I run "sensors", it does not show fan. Do you have a solution?
Owning one OpenRC (artoo way) and other three systemd machines
I also hve a eeepc 901 with the same problem...anything solution?