View previous topic :: View next topic |
Author |
Message |
theaks n00b
Joined: 30 Sep 2004 Posts: 30
|
Posted: Wed Oct 13, 2004 7:55 am Post subject: Reducing fan speed |
|
|
I've just set up lm-sensors and can detect my cpu temp. I've got an amd64 system and i'm wondering how i can reduce my fans speed manually from inside linux?
Also is there a daemon that can do it for me based to the cpus temp? |
|
Back to top |
|
|
imacomputa n00b
Joined: 05 May 2004 Posts: 18
|
Posted: Wed Oct 27, 2004 7:44 pm Post subject: |
|
|
I am also trying to find a solution to fan speed adjustment, but in my case I want to crank the fan speed up.
This is for an AMD64 notebook. _________________ Hey kid! I'm a computa'. Stop all the downloadin'. Help computa'. |
|
Back to top |
|
|
KozmoNaut Apprentice
Joined: 09 Dec 2002 Posts: 168 Location: Denmark
|
Posted: Wed Oct 27, 2004 8:13 pm Post subject: |
|
|
Theres a script called "fancontrol" included in the lmsensors package.
Run pwmconfig first to generate a config file (it sets up stuff like min and max temps and the corresponding fan speeds). After that you can tweak the /etc/fancontrol file, but that's probably not neccesary.
I put this in my /etc/conf.d/local.start:
Code: | /usr/sbin/fancontrol & > /dev/null |
Which makes it run on startup and not stop until I kill it _________________ War. War never changes. |
|
Back to top |
|
|
alkan Guru
Joined: 06 Aug 2004 Posts: 385 Location: kasimlar yaylasi
|
Posted: Thu Oct 28, 2004 4:21 am Post subject: |
|
|
fancontrol works beautifully on my machine. My fans(CPU and PS) are quiet and only kick in under heavy load. I added following init script (/etc/init.d/fancontrol)
Code: |
start() {
ebegin "Starting fancontrol"
start-stop-daemon --start --background --pidfile /var/run/fancontrol.pid --exec /usr/sbin/fancontrol
eend $? "Failed to start fancontrol"
}
stop() {
ebegin "Stopping fancontrol"
start-stop-daemon --stop --pidfile /var/run/fancontrol.pid
eend $? "Failed to stop fancontrol"
}
|
Code: |
rc-update add fancontrol default
|
Here is the my /etc/fancontrol configuration file
Code: |
INTERVAL=10
FCTEMPS=*-0290/pwm2=*-0290/temp2_input *-0290/pwm1=*-0290/temp3_input
FCFANS=*-0290/pwm2=*-0290/fan1_input *-0290/pwm1=*-0290/fan2_input
MINTEMP=*-0290/pwm2=45 *-0290/pwm1=45
MAXTEMP=*-0290/pwm2=60 *-0290/pwm1=55
MINSTART=*-0290/pwm2=0 *-0290/pwm1=0
MINSTOP=*-0290/pwm2=0 *-0290/pwm1=0
|
That is minimum CPU fan speed at 45 degree CPU temperature, maximum CPU fan speed at 60 degree CPU temperature. Similarly minumum Power Supply (PS) fan speed at 45 degree main board temperature, maximum PS fan speed at 55 degree main board temperature.
you can also manually set the fan speeds.
Code: |
echo 255 > /sys/bus/i2c/devices/1-0290/pwm1
|
echo 0 for minimum fan speed, echo 255 for full fan speed. pwm1(first fan) pwm2(second fan).....etc. the above path and configuration file is machine depended.
If you set CPU fan speed to a lower value manually, Cooling may not be enough, resulting overheated and burned CPU. Better use fancontrol script
Last edited by alkan on Thu Oct 28, 2004 3:03 pm; edited 1 time in total |
|
Back to top |
|
|
josh Guru
Joined: 05 Feb 2003 Posts: 473 Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
Posted: Thu Oct 28, 2004 12:55 pm Post subject: |
|
|
I don't have the /sys/bus/i2c directory. How can I get that? Is it something that needs to be enabled in the kernel? _________________ -Josh |
|
Back to top |
|
|
alkan Guru
Joined: 06 Aug 2004 Posts: 385 Location: kasimlar yaylasi
|
Posted: Thu Oct 28, 2004 2:57 pm Post subject: |
|
|
Yes, You need to enable
Code: |
Device Drivers -->
I2C Support -->
<*> I2C Support
<*> I2C DeviceInterface
I2C Hardware Bus Support ->
(Enable Your Bus system)
Hardware Sensors Chip Support -->
(Enable whatever sensor chip you have)
|
You can also enable those as modules for all the chips listed in there if you don't know what chip you have. Then try loading them one at a time to see if it works. lm_sensors does it automatically for you.
|
|
Back to top |
|
|
FearlessSpiff n00b
Joined: 26 Sep 2004 Posts: 69
|
Posted: Thu Oct 28, 2004 9:16 pm Post subject: |
|
|
I just installed lm_sensors but am surprised, that i don't have pwm functionality on my new SN95G5/3.5AMD64/and my GeForce. The thing is, i have to absolutly turn down the GeForce Fan. It is driving me crazy. On full speed all the time. I think it is the Temp3 indicator. But how can i throttle the fan speed now?
Code: | it87-isa-0290
Adapter: ISA adapter
VCore 1: +1.07 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +1.46 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +6.53 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +4.87 V (min = +4.76 V, max = +5.24 V)
+12V: +11.84 V (min = +11.39 V, max = +12.61 V)
-12V: -20.36 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -2.56 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +4.81 V (min = +4.76 V, max = +5.24 V)
VBat: +3.04 V
fan1: 907 RPM (min = 0 RPM, div = 16)
fan2: 0 RPM (min = 332 RPM, div = 16)
fan3: 4963 RPM (min = 664 RPM, div = 8)
M/B Temp: +49 C (low = +15 C, high = +40 C) sensor = thermistor
CPU Temp: +22 C (low = +15 C, high = +45 C) sensor = diode
Temp3: +47 C (low = +15 C, high = +45 C) sensor = thermistor |
Then im asking myself why i cant "modprobe ic2-isa". Maybe this is the problem, that changing Fanspeed doesn't work? |
|
Back to top |
|
|
alkan Guru
Joined: 06 Aug 2004 Posts: 385 Location: kasimlar yaylasi
|
Posted: Thu Oct 28, 2004 10:00 pm Post subject: |
|
|
I assume it is a typo, you should modprobe i2c-isa (not ic2-isa)
Well, if your hardware doesn't support PWM. There is no easy way to speed down the fan. You can buy a quiter fan.
I remember seeing a script which emulates the PWM by turning on-off the fan very quickly (which is what PWM does). But can't remember where and what was the name. If you have the functionalty of turning the fan on and off, you can write a simple script to do that. |
|
Back to top |
|
|
FearlessSpiff n00b
Joined: 26 Sep 2004 Posts: 69
|
Posted: Thu Oct 28, 2004 10:16 pm Post subject: |
|
|
Omg, i m too stupid i enabled it in the kernel, not as module... Sorry. |
|
Back to top |
|
|
orionrobots Apprentice
Joined: 07 Oct 2003 Posts: 289 Location: London, Uk
|
Posted: Fri Oct 29, 2004 12:07 pm Post subject: |
|
|
alkan wrote: | If you have the functionalty of turning the fan on and off, you can write a simple script to do that. |
While this is exactly what PWM does - I would *seriously* advice against implementing this in a script. If your script stops (for whatever reason - and sometimes they do), you could leave a system in a fan off state. Bad move - game over.
To be fair, working with a lot of PWM based robot transmissions, it is always something better implemented in a dedicated controller, which I would hope there is somewhere in the chipset... _________________ Danny Staple, curator of http://orionrobots.co.uk
Adopt an unanswered post initiative https://forums.gentoo.org/search.php?search_id=unanswered |
|
Back to top |
|
|
FearlessSpiff n00b
Joined: 26 Sep 2004 Posts: 69
|
Posted: Fri Oct 29, 2004 1:13 pm Post subject: |
|
|
Yeah, i never intended to do this. The sad thing is, that the fan can be controlled. I use a utility in Windows to do so. So i know that it could work. I also think, that this regulation of fan speeds belongs into the bios of the mainboard/graphic card and not into a piece of software running on an OS. |
|
Back to top |
|
|
alkan Guru
Joined: 06 Aug 2004 Posts: 385 Location: kasimlar yaylasi
|
Posted: Fri Oct 29, 2004 3:56 pm Post subject: |
|
|
Quote: | If your script stops (for whatever reason - and sometimes they do), you could leave a system in a fan off state. Bad move - game over. |
It has the same risks as IO chips with built-in PWM (widely used today). your driver or script stops (for whatever reason), you could leave a system in a fan PWM value 0 or not enough for cooling - game over again.
Many of the recent systems (even old systems) uses an IO chip to handle fan speeds and to read-in various sensors. Speed or status of the fan is controlled by the OS throught the ACPI. There are security measures can be taken (like set them to the max when driver stops, lm_sensors's fancontrol script does that). I have been using my system for 3 years now (linux and windoz) without single failure.
I agree a dedicated hardware would be rock-solid but it wouldn't be as customizable. That's why there is ACPI, to manage the hardware more efficiently (especially when power consumption of chips are going sky-rocket). A dedicated hardware can be a backup system on top of the software power management.
An example to the customization is my system. My PS fan sits on top of CPU, So When CPU fan is not enough, I rev-up the PS fan to help cool the CPU. Or If the ambient temperature is already high I don't force the fans as hard. I use an advandced PID feedback system to manage the hardware I have. The program I've written in C++ reads in various sensors such as temperatures, system load..., accept some paramaters such as capacity of the fans, cooling coefficients..., after some calculations it adjusts fan speeds, does CPU throttling..., in an intelligent way such that if There is nothing runing, it slows the CPU, otherwise rev-up fans and even turn-off some hardware not in use. If I am working on the computer or it is night (I am sleeping in the same room) it switches to the quiet mode and so on. It is overkill, but it was a project for just learning things. |
|
Back to top |
|
|
mm/ol n00b
Joined: 24 Jun 2004 Posts: 56 Location: Montreal
|
Posted: Wed Dec 08, 2004 5:19 am Post subject: |
|
|
This thread saved my ears. <3 |
|
Back to top |
|
|
Cintra Advocate
Joined: 03 Apr 2004 Posts: 2111 Location: Norway
|
Posted: Wed Dec 08, 2004 8:02 am Post subject: |
|
|
Very nice solution guys...
btw, for those who aren't aware, there are mechanical solutions which take up a pci slot's space on the back of your system, and in my case, control the rear chassis fans.
The one I use has three speeds, which I run either on max while compiling, or on low normally. It makes listening to music that much more enjoyable..
regards _________________ "I am not bound to please thee with my answers" W.S. |
|
Back to top |
|
|
eqxro n00b
Joined: 28 Nov 2004 Posts: 67 Location: In a warm place
|
Posted: Wed Dec 08, 2004 9:04 am Post subject: |
|
|
Okay, a quick tip, something I noticed myself... I kept my box closed, and the fans were running @ 5000RPM, 50/40C (CPU/MB temp). opening up the case and intensive use (HL2, NFSU2), made the temp go up to 45, fans at 4000. Normal use: 35/30 @ 3200 RPM. On a cold day, i got it down to 28/24 C, 3000 RPM. Less noise |
|
Back to top |
|
|
Cintra Advocate
Joined: 03 Apr 2004 Posts: 2111 Location: Norway
|
Posted: Wed Dec 08, 2004 4:42 pm Post subject: |
|
|
Sounds like blocked filters to me
mvh _________________ "I am not bound to please thee with my answers" W.S. |
|
Back to top |
|
|
tnt Veteran
Joined: 27 Feb 2004 Posts: 1221
|
Posted: Sat Mar 12, 2005 11:58 pm Post subject: |
|
|
I have brand new Chaintech VNF4 Ultra board with NForce4 Ultra chipset.
In window$ I've tried "SpeedFan" and I was able to control speed of two fans connected to the board. Other two (there's four fan connectors on the board) can not be controled.
But, in gentoo I can't control fans...
I've done sensors-detect and detected IT8712F, the same one "SpeedFand" detected in window$:
Code: | Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Success!
(confidence 8, driver `it87')
...
Probing for `ITE 8712F Super IO Sensors'
Success... found at address 0x0290
|
I have /sys/devices/platform/i2c-0/0-0290/ but there's no pwm* files:
Code: | titan 0-0290 # ls -la
total 0
drwxr-xr-x 3 root root 0 Mar 13 00:45 .
drwxr-xr-x 4 root root 0 Mar 13 00:45 ..
-rw-r--r-- 1 root root 4096 Mar 13 00:45 alarms
-rw-r--r-- 1 root root 4096 Mar 13 00:45 detach_state
-rw-r--r-- 1 root root 4096 Mar 13 00:45 fan1_div
-r--r--r-- 1 root root 4096 Mar 13 00:45 fan1_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 fan1_min
-rw-r--r-- 1 root root 4096 Mar 13 00:45 fan2_div
-r--r--r-- 1 root root 4096 Mar 13 00:45 fan2_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 fan2_min
-rw-r--r-- 1 root root 4096 Mar 13 00:45 fan3_div
-r--r--r-- 1 root root 4096 Mar 13 00:45 fan3_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 fan3_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in0_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in0_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in0_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in1_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in1_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in1_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in2_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in2_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in2_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in3_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in3_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in3_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in4_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in4_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in4_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in5_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in5_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in5_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in6_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in6_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in6_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in7_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 in7_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 in7_min
-r--r--r-- 1 root root 4096 Mar 13 00:45 in8_input
-r--r--r-- 1 root root 4096 Mar 13 00:45 name
drwxr-xr-x 2 root root 0 Mar 13 00:45 power
-r--r--r-- 1 root root 4096 Mar 13 00:45 temp1_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 temp1_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 temp1_min
-rw-r--r-- 1 root root 4096 Mar 13 00:45 temp1_type
-r--r--r-- 1 root root 4096 Mar 13 00:45 temp2_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 temp2_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 temp2_min
-rw-r--r-- 1 root root 4096 Mar 13 00:45 temp2_type
-r--r--r-- 1 root root 4096 Mar 13 00:45 temp3_input
-rw-r--r-- 1 root root 0 Mar 13 00:45 temp3_max
-rw-r--r-- 1 root root 0 Mar 13 00:45 temp3_min
-rw-r--r-- 1 root root 4096 Mar 13 00:45 temp3_type |
I'm using "stable" gentoo-dev-sources 2.6.9-r14 on amd64.
Should I use some more recent kernel or what?
_________________ gentoo user |
|
Back to top |
|
|
Small_Penguin Tux's lil' helper
Joined: 27 May 2005 Posts: 140
|
Posted: Fri May 27, 2005 6:33 pm Post subject: |
|
|
tnt wrote: | Probing for `ITE 8712F Super IO Sensors'
Success... found at address 0x0290 |
Maybe, this problem can be solved by using lm_sensors-2.9.1, which you probably have to compile and install by yourself (no ebuild for my arch). |
|
Back to top |
|
|
skakz Guru
Joined: 03 Jul 2004 Posts: 380 Location: Ischia/Napoli/Italia/Terra
|
Posted: Mon Jun 06, 2005 11:04 am Post subject: |
|
|
hi all
i have this i2c modules build in the kernel: eeprom i2c-isa it87 i2c-viapro, so i don't modpbore anything!
sensors works fine:
Code: |
omega linux # sensors
it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.66 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +0.00 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +3.66 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +5.05 V (min = +4.76 V, max = +5.24 V)
+12V: +12.03 V (min = +11.39 V, max = +12.61 V)
-12V: -17.36 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -6.64 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +5.08 V (min = +4.76 V, max = +5.24 V)
VBat: +4.08 V
fan1: 3590 RPM (min = 0 RPM, div = 8)
fan2: 3276 RPM (min = 2657 RPM, div = 2)
fan3: 0 RPM (min = 2657 RPM, div = 2) ALARM
CPU Temp: +42°C (low = +15°C, high = +40°C) sensor = thermistor
CPU Temp: +40°C (low = +15°C, high = +45°C) sensor = thermistor
Temp3: -1°C (low = +15°C, high = +45°C) sensor = disabled
eeprom-i2c-1-52
Adapter: SMBus Via Pro adapter at e800
Memory type: DDR SDRAM DIMM
Memory size (MB): 512
|
i have a7v600-x MB
sensors version 2.9.0 with libsensors version 2.9.0
2.6.11 kernel
CoolerMaster ASBV83 JET 7 with fan control knob that controls fan speeds from my frontal plate
now i want to configure dynamic fan speed so i do:
Code: |
omega root # pwmconfig
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 PWM controls:
0-0290/pwm1
0-0290/pwm2
0-0290/pwm3
Found the following fan sensors:
0-0290/fan1_input current speed: 3668 RPM
0-0290/fan2_input current speed: 3276 RPM
0-0290/fan3_input current speed: 0 ... skipping!
Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:
Testing pwm control 0-0290/pwm1 ...
0-0290/fan1_input ... speed was 3668 now 3668
no correlation
0-0290/fan2_input ... speed was 3276 now 3276
no correlation
No correlations were detected.
There is either no fan connected to the output of 0-0290/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)? n
...
|
yes.. i didn't hear anything...
Code: |
...
Testing pwm control 0-0290/pwm2 ...
0-0290/fan1_input ... speed was 3668 now 3668
no correlation
0-0290/fan2_input ... speed was 3276 now 3276
no correlation
No correlations were detected.
There is either no fan connected to the output of 0-0290/pwm2,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)? n
...
|
same...
Code: |
....
Testing pwm control 0-0290/pwm3 ...
0-0290/fan1_input ... speed was 3668 now 3668
no correlation
0-0290/fan2_input ... speed was 3276 now 3308
no correlation
No correlations were detected.
There is either no fan connected to the output of 0-0290/pwm3,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)? n
...
|
did you trust? same...
Code: |
...
Testing is complete.
Please verify that all fans have returned to their normal speed.
The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)? y
What should be the path to your fancontrol config file (/etc/fancontrol)?
/etc/fancontrol does not exist, shall I create it now (y)? y
chown: `root.root' syntax is obsolete; use `:' since this will be removed in the future
Loading configuration from /etc/fancontrol ...
Select fan output to configure, or other action:
1) Change INTERVAL 3) Save and quit
2) Just quit 4) Show configuration
select (1-n): 4
Common Settings:
INTERVAL=10
select (1-n):
omega root #
|
WTF?? my config is 1 line????
so i decided to make my own config...
here it is:
Code: |
omega root # cat /etc/fancontrol
INTERVAL=10
FCTEMPS=*-0290/pwm2=*-0290/temp2_input *-0290/pwm1=*-0290/temp1_input
FCFANS=*-0290/pwm2=*-0290/fan2_input *-0290/pwm1=*-0290/fan1_input
MINTEMP=*-0290/pwm2=38 *-0290/pwm1=40
MAXTEMP=*-0290/pwm2=50 *-0290/pwm1=55
MINSTART=*-0290/pwm2=0 *-0290/pwm1=0
MINSTOP=*-0290/pwm2=0 *-0290/pwm1=0
|
but running fancontrol doesn't produce any effect on my fans
Code: |
omega root # fancontrol
Loading configuration from /etc/fancontrol ...
Common settings:
INTERVAL=10
Settings for *-0290/pwm2:
Depends on *-0290/temp2_input
Controls *-0290/fan2_input
MINTEMP=38
MAXTEMP=50
MINSTART=0
MINSTOP=0
Settings for *-0290/pwm1:
Depends on *-0290/temp1_input
Controls *-0290/fan1_input
MINTEMP=40
MAXTEMP=55
MINSTART=0
MINSTOP=0
Enabling PWM on fans...
Starting automatic fan control...
|
even if i force 0 in pwm1 or pwm2 nothing happened
Code: |
omega root # cat /sys/bus/i2c/devices/0-0290/pwm1
255
omega root # echo 0 > /sys/bus/i2c/devices/0-0290/pwm1
omega root # sensors | grep fan1
fan1: 3590 RPM (min = 0 RPM, div = 8)
omega root #
|
This is a campaign in favor of my ears.
We plead you to participate _________________ Linux Registered User n.340423
Linux User Group Ischia
www.tush.it |
|
Back to top |
|
|
skakz Guru
Joined: 03 Jul 2004 Posts: 380 Location: Ischia/Napoli/Italia/Terra
|
Posted: Tue Jun 07, 2005 2:07 pm Post subject: |
|
|
*cabunk* _________________ Linux Registered User n.340423
Linux User Group Ischia
www.tush.it |
|
Back to top |
|
|
<3 Veteran
Joined: 21 Oct 2004 Posts: 1081
|
Posted: Wed Sep 28, 2005 7:19 am Post subject: |
|
|
alkan wrote: | fancontrol works beautifully on my machine. My fans(CPU and PS) are quiet and only kick in under heavy load. I added following init script (/etc/init.d/fancontrol)
Code: |
start() {
ebegin "Starting fancontrol"
start-stop-daemon --start --background --pidfile /var/run/fancontrol.pid --exec /usr/sbin/fancontrol
eend $? "Failed to start fancontrol"
}
stop() {
ebegin "Stopping fancontrol"
start-stop-daemon --stop --pidfile /var/run/fancontrol.pid
eend $? "Failed to stop fancontrol"
}
|
Code: |
rc-update add fancontrol default
|
|
Sorry for the newb question but I don't know how to get this init script working. I made a file called /etc/init.d/fancontrol and copied/pasted your code into that file then I did a Code: |
rc-update add fancontrol default
|
and I get this error
Code: | #rc-update add fancontrol default
* fancontrol not executable; skipping
| can someone tell me what this means? |
|
Back to top |
|
|
PaulBredbury Watchman
Joined: 14 Jul 2005 Posts: 7310
|
Posted: Wed Sep 28, 2005 7:33 am Post subject: |
|
|
<3 wrote: | * fancontrol not executable; skipping |
To make it executable:
Code: | chmod +x /etc/init.d/fancontrol |
|
|
Back to top |
|
|
<3 Veteran
Joined: 21 Oct 2004 Posts: 1081
|
Posted: Wed Sep 28, 2005 7:42 am Post subject: |
|
|
thx |
|
Back to top |
|
|
blossa Apprentice
Joined: 13 Jan 2005 Posts: 169
|
Posted: Sat Oct 29, 2005 7:21 pm Post subject: |
|
|
alkan wrote: | fancontrol works beautifully on my machine. My fans(CPU and PS) are quiet and only kick in under heavy load. I added following init script (/etc/init.d/fancontrol)
Code: |
start() {
ebegin "Starting fancontrol"
start-stop-daemon --start --background --pidfile /var/run/fancontrol.pid --exec /usr/sbin/fancontrol
eend $? "Failed to start fancontrol"
}
stop() {
ebegin "Stopping fancontrol"
start-stop-daemon --stop --pidfile /var/run/fancontrol.pid
eend $? "Failed to stop fancontrol"
}
|
Code: |
rc-update add fancontrol default
|
|
I don't get it... The init script don't work. If I try to start it nothing happens, no error messages, nothing. But if I run /usr/sbin/fancontrol fancontrol starts and works great.
Any hints?
Thnx!
/Anders |
|
Back to top |
|
|
<3 Veteran
Joined: 21 Oct 2004 Posts: 1081
|
Posted: Sat Oct 29, 2005 9:01 pm Post subject: |
|
|
are you sure you did a
Code: | rc-update add fancontrol default |
if so what happens when you do a
Code: | /etc/init.d/fancontrol start |
|
|
Back to top |
|
|
|