General :: How To Get CPU Fan To Stop Spinning When Idle
Aug 11, 2011
I have a PC which I built ~3 years ago which had been running smoothly and silently until recently. Now, the CPU fan likes to spin up to 1200-1500 RPM even when it's idle, which is rather annoying. I have not made any recent changes (software-wise or hardware-wise) to it.
I installed the lm-sensors and hddtemp packages (via apt-get) and configured them. Here's a typical output at steady-state, where the computer's been idle for a while and the fans have been spinning for the same while:
These all seem fairly normal to me, so I'm perplexed as to why the fan continues to run at such a high RPM. What does the ALARM that's reported for in6 mean? Is it important? I've been playing around with the fancontrol daemon, trying to see if I could get better results than with the default fan management. Using the pwmconfig utility, I generated the following /etc/fancontrol file:
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/pci0000:00/0000:00:18.3 hwmon1=devices/platform/it87.552
DEVNAME=hwmon0=k8temp hwmon1=it8718
FCTEMPS= hwmon1/device/pwm1=hwmon0/device/temp1_input
FCFANS= hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP= hwmon1/device/pwm1=35
MAXTEMP= hwmon1/device/pwm1=60
MINSTART= hwmon1/device/pwm1=180
MINSTOP= hwmon1/device/pwm1=100
This only sort of works—as soon as I enable the fancontrol daemon, the fan shuts off at first (good), but the temperatures of the 7 different sensors slowly rise, even when everything is idle. Eventually, when the Core0 Temp sensors goes past 35°, the fan comes back on, and then it alternates from being on and off at around 500-700 RPM, as the temperature goes back and forth across the boundary. It's certainly much more pleasant than 1200-1500 RPM, but it's still far from desirable.
Here's an example of the sensors output in that situation:
$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +36.0°C
Core0 Temp: +38.0°C
Core1 Temp: +34.0°C
Core1 Temp: +30.0°C
it8718-isa-0228
Adapter: ISA adapter .....
cpu0_vid: +1.100 V
I opened up the case, and the CPU heat sink felt warm but not excessively hot. I tried taking off the heat sink, cleaning off the thermal paste, putting on new thermal paste, and putting the heat sink back on, but that didn't seem to have much of an effect, if any. The two other heat sinks—one on the built-in AMD 780G graphics chipset and the other on the AMD SB700 southbridge—felt noticeably hotter than the CPU heat sink. So, my question is this: What should I do to get this computer back to the state where the fan is off when it's idle? Can I solve this with a smarter fancontrol configuration?
I cleaned out the heat sink and fan as best I could with compressed air (there wasn't a whole lot of dust, but I got rid of what I could), but still no dice. Rebooting into the BIOS configuration gives me the same results—the fan still runs at 1100-1200 RPM, and the system and CPU temperatures are reported as 40-44°C. Should I add another fan? The integrated GPU and the SB heatsinks felt significantly warmer to the tough than the CPU heatsink. The BIOS reports a system fan speed and NB fan speed of 0 rpm (since I don't have more than one fan).
If I use Gnome, is "gnome-power-preferences" the only place where I can configure the system to stop or not to stop spinning HDD as a power saving tool? Is there any other option outside GUI?
I've bought a new notebook. The hard drive won't stop spinning down and then spinning up again during load. I don't want HD power saving, so I disabled it within
I've been using Ubuntu 10.x for several months without any major problems. Everything was fine until this week.
In the past few days there's been a strange new problem. When I turn my computer on, it works fine for 10 minutes, and then the hard drive suddenly starts spinning and won't stop. While this happens the computer is virtually unusable. Mouse moves slow and jerky; apps don't respond; and eventually the windows close by themselves, the whole screen goes blank, and the system reboots. The whole process takes a long time, sometimes 30 minutes.
The only change I made just before this problem started was upgrading Firefox Beta 4 version 10 to the latest version 11. So, I deleted it, and went back to the latest stable version 3.6.x. That seemed to fix the problem for a day or so. But then it started happening again. I deleted all signs of Firefox; it still happens. So it's not a browser issue.
I am stumped. Today I started my computer and just let it sit there without opening any programs at all except the system monitor. It ran fine for the usual 10-15 minutes, nothing changed out of the ordinary in terms of computer resources used in the system monitor, and then suddenly the drive started spinning wildly again .....
Right now my computer's been on for 10 minutes and I am typing this message .... but who knows what will happen right now.
I am using a toshiba sattelite L300 laptop, and i am facing severe overheating issues as a result of the cooling fan Barely even spinning / not spinning at all.
Temps have been as high as 110 degrees, It's extremely frustrating.
I am running OpenSUSE 11.2 (but I do not suspect that this is distribution-specific).Linux bach 2.6.31.8-0.1-desktop #1 SMP PREEMPT 2009-12-15 23:55:40 +0100 i686 i686 i386 GNU/Linux.I am running in runlevel 3 while trying to sort this out.When smartd runs, it spins up my Western Digital drives from standby, but not my Samsung drive.Anyone know why blkid, edd_id and devkit-disks-pa are reading my standby drives? And are these reads sufficient to make drives spin up? I'm not sure what to look at next.
how to log out an idle session. I was using putty to connect to a Debian machine to edit my .profile file. I got disconnected. Ideally I would want to log back into my own session. If anyone can let me know how to do it, please? If not I want to open a new session and then log off my first session (see below pts/0).
I want to get the system idle time till a mouse move or a key press. How is it possible to get it from a char terminal running through ssh/telnet as well as a from an X-terminal session?
Suppose I am almost sure that from last Thursday, 3.00pm up to the same day at 10.00pm I was away from the machine, but not absolutely sure. Linux probably knows better than me. Maybe there will be a text file from which I could infer the keyboard was idle from Thu 2.40pm up to 11.10 pm. In this case, I would reach absolute certainty. But where could such file be in the /. tree or what could its name be (for in the latter case an updatedb followed by locate would do)?
whats the difference between restarting/stopping apache using 'service httpd restart/stop' and apachectl restart/stop. I know that using 'service httpd restart' is actually a script in /etc/init.d/httpd but what about apachectl?
All the kill idle user processes scripts I've seen don't take into account that the user might have multiple sessions open. Such is the case with one of our clients. Currently, every hour or two I need to do the following:
This will get the TTY and idle time for all users.
For each idle time over a half hour, I do the following (TTY is the TTY from the previous command with a space.
I then kill those processes.
There must be a way to do this automatically in a bash or perl script. I've tried both, but can't seem to get things to work properly.
i've gotten my fedora 12 to the point where i can run python3 scripts from command line and can call up python 2.6.2 idle with the command 'idle' from command line. what command will call up python3 (3.1.2 to be exact) idle?
I'm trying to understand if anyone is left on a server. Basically I manage a simple linux server remotely used by 3-4 individuals. I can never tell if someone is actually on or not using w/who.What I'm seeing is some people having what appears to be inactive/lost VNC sessions. I don't understand idle fully, but I do believe a program (without user interaction) can clear idle back to 0, correct?Anyway, I'm asking because every now and then I need to reboot the server, and I do not want to interrupt any program working on calculations or waiting on having the data saved.
Code: me@matrix:~> w 06:59:54 up 170 days, 9:13, 16 users, load average: 0.52, 0.16, 0.06
I think I have found the problem to my Ubuntu laptop locking up, and it is most likely overheating. Is there any way to keep the CPU fan spinning at 100% constantly? I tried setting it up in the BIOS but it is an old laptop and I can't control it from there.
I updated from 9.10 karmic to 10.04 LTS. Everything worked fine until, I restarted. Upon logout there are no splash screen like I had before in the 9.10, and my fan on my gfx are going crazy, spining at 100%. Well then I got to the grub loader, and discovered my boot splash was gone to. The only thing which is displayed on the screen are: mount dev /dev failed device71 Starting up. Then 10 seconds later alot of texts shows up and I get the login screen. I've looked around on the forum and other sites for a solution, but with no luck.
it gets the hdd very warm and keeps the fan on constantly as well generally heating the whole system . was so bad i ended up having to go back to windows anything i can do to get the hdd to go in standy by when in active like windows ???? cause i hate windows and love ubuntu but i dont wanna burn up my machine to keep ubuntu
I am a regular ubuntu user from 7.10 till now. Now I am using 11.04. This problem never happened with previous releases. When I open more than 4 windows in firefox or whenever I open "Ubuntu Software Center" the hard disk keeps spinning, mouse and keyboard are frozen. I tried to reboot from tty1. It takes around 3 minutes to get the command prompt after pressing Ctrl + Alt + F1. I reinstalled 11.04 several times. This problem is not solved. I have applied all the updates. What program is exactly causing this problem?
I have got an Acer 3820T laptop. Among many problems that it seems to have with linux, the most critical one is that when I boot into linux, the fan stops spinning. I have already verified that the relevant modules are loaded into the kernel,
Code:
~$ modprobe --first-time -a processor thermal fan acpi-cpufreq coretemp Password: WARNING: Module processor already in kernel (builtin). WARNING: Module thermal already in kernel (builtin).
while doing FTP through command prompt, connections times out after some time remaining idle, but doing ftp through browser, connection doesn't time out after some time remaining idle... why is it so?
What I have noticed on several versions of Ubuntu, both 32 and 64 bit (including 9.10, 10.04 b2 and UNR 9.10) is that after the launch of Firefox (including the current 3.6.3 version), I continue to get a spinning cursor for more than 10 seconds after the FF window is present and ready to accept input. Sometimes I get it only when moving the cursor outside the FF window and other times it will be in the window, too. I have even noticed it persist for a short time after quitting FF. I think it's definitely related to FF because I don't see this occur unless FF is launched, not even when another browser (Chromium in this case) is launched. To add to the mystery, I see it in Ubuntu and Mint 8 xfce, but not in Ubuntu-based distros with simpler window managers like Mint 8 fluxbox or CrunchBang 9.04 (openbox). To try to get rid of this, I have tried various FF configuration speedups available from the Net - changes implemented through about:config. These do speed up FF, but they don't get rid of the spinning wheel.As far as I can tell, the spinning wheel has no impact on FF operation - it doesn't stop me from entering a url and accessing it, though perhaps it slows down implementation.
I'm running the latest slackware64-current on my Dell laptop (Inspiron 1420). I rarely run it on battery power, so I don't know when this behavior started, but now it seems when I'm on battery power the hard drive likes to spin down and then spin up. This is not after 5 minutes or so of inactivity. This is 30 seconds of inactivity because I'm reading a web page or something. There is a noticable delay in the response of the system as a whole when the drive is having to spin back up. I'm also using xfce-4.6.2 with the xfce power manager. I've checked the settings, and I don't see anything about spinning down the hard drives. I've also looked through some ACPI rules, but I'm coming up empty.
When I run Ubuntu liveCD (Lucid), even when no programs are running and cpu is 98% idle, the CD Rom continues spinning constantly, even though it apparently isn't accessing any files. At this rate, the motor will burn out prematurely.I don't think this is normal. How can I troubleshoot this and keep it from running?
i am unable to play bbc videos although videos and other videos work fine. i believe i have the latest flash player installed and i installed bbc iplayer from the software center of ubuntu. i am running 64 bit ubuntu 10.10. when i click on a video on bbc i see the photo showing the start of the video but it doesn't progress past that; i just get the hourglass (wheel?) spinning around for a long time.
I'm trying to install v10.10 on my Sony Vaio VGN-NS150J, 4gb ram, 2gb core 2 duo, 320 gb HD...to no avail. The live CD boots, but the dvd drive stops spinning after i click the install button...the one that says i can't turn back. Nothing seems affected by quitting the install. I have no idea what to do except to not turn back to VistaOS. I intensely dislike that "operating system".
Mac Hard Drive Data Recovery is needed when your disks are not spinning up, hard drive unmountable, killed a hard drive without backing up, or if you have experienced a hard drive crash.
First of all I have to say I love Fedora, just switched from openSuSE after the system was kinda sluggish the last 2 or 3 versions. But one thing I always liked was the fact that when the system went into suspend my external harddrive spun down and after resuming it spun up again as soon as I tried to access a file. Now in Fedora the harddrive continues spinning and is unavailable after resuming. There is nothing about the harddrive in dmesg, not during suspending and not even when i unplug it after resuming.