Page 3 of 12 FirstFirst 12345 ... LastLast
Results 21 to 30 of 119

Thread: HOWTO: Fancontrol

  1. #21
    Join Date
    Aug 2005
    Beans
    211

    Re: HOWTO: Fancontrol

    Just a warning, Speedfan was/is a good program for windows, but is not maintained or updated any more for some time now. Be carefull.

    (I use the fancontroller made by MSI for my motherboard on windows, which works for me, but is considered malware by others )

  2. #22
    Join Date
    Oct 2005
    Location
    France
    Beans
    8
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: HOWTO: Fancontrol

    Thanks for this great how to.

    My little contribution: to add the start/stop links, I rather prefer the command:
    Code:
    sudo update-rc.d fancontrol defaults 99 01
    I changed the pid file in the script:
    Code:
    PIDFILE=/var/run/fancontrol.pid
    Last edited by jotape99; November 23rd, 2005 at 12:21 AM.

  3. #23
    Join Date
    Mar 2006
    Beans
    480
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOWTO: Fancontrol

    Nevermind, got it sorted.
    Last edited by mozetti; April 17th, 2006 at 06:45 AM.

  4. #24
    Join Date
    Jul 2006
    Beans
    9

    Re: HOWTO: Fancontrol

    I recently built a computer with an Intel D945Gcz motherboard and an Intel Pentium-D 3.0 processor, and the fan sounds like a vacuum cleaner. I'd like to find a way to regulate the fan speed, as other operating systems seem to be able to do it.

    I installed lm-sensors as shown here and got an output from it:

    Code:
    lm85-i2c-0-2e
    Adapter: SMBus I801 adapter at 2000
    V1.5:       +1.58 V  (min =  +1.42 V, max =  +1.58 V)
    VCore:      +1.25 V  (min =  +1.76 V, max =  +1.95 V)   ALARM
    V3.3:       +3.33 V  (min =  +3.13 V, max =  +3.47 V)
    V5:        +5.10 V  (min =  +4.74 V, max =  +5.26 V)
    V12:      +12.19 V  (min = +11.38 V, max = +12.62 V)
    CPU_Fan:   5268 RPM  (min = 1000 RPM)
    fan2:         0 RPM  (min =    0 RPM)
    fan3:         0 RPM  (min =    0 RPM)
    fan4:         0 RPM  (min =    0 RPM)
    CPU:         +39°C  (low  =   +10°C, high =   +60°C)
    Board:       +30°C  (low  =   +10°C, high =   +35°C)
    Remote:      +34°C  (low  =   +10°C, high =   +35°C)
    CPU_PWM:   255
    Fan2_PWM:  255
    Fan3_PWM:  255
    vid:      +1.850 V  (VRM Version 9.1)
    I've tried following through the explanation here but haven't had any success. In particular, when I try to add

    Code:
    set fan1_div 4
    as specified, I get

    Code:
    ~$ sudo sensors -s
    Error: Line 2196: Unknown feature name
    lm85-i2c-0-2e: No such feature known
    I understand there are situations where my fan would need to run near 5300 RPM, but the baby in the next room does need to sleep.

    Anyone have any ideas?

    ~Tony David Potter

  5. #25
    Join Date
    Jan 2005
    Beans
    65

    Re: HOWTO: Fancontrol

    For starters: do not try to patch the pwmconfig thing if you are running dapper. It's been fixed, you no longer need to patch the script.

    mistapotta: It looks like your fan is being picked up correctly by lm_sensors. The speed is being reported, so you won't have to change the fan's divisor. You only need to do this if the fan is running so slowly that lm_sensors thinks it's turned off. Looks like this is not the case.
    Also, fan1_div would point to a fan named fan1. Looking at your output, the CPU fan is actually called CPU_Fan (conveniently!) so it would be CPU_Fan_div, I guess.

    You're now ready to run pwmconfig! Good luck!

    If you want to silence your computer even more, I suggest getting a larger fan. I have a 12" one made by Zalman, and it's very quiet with the rotations turned down. With my CPU (amd athlon 64 3000+), it sometimes even turns off alltogether. I don't know how hot your Pentium runs though, could be a lot hotter. Anyway, try the pwmconfig and if it's still too loud after that you can always look at a larger fan.

  6. #26
    Join Date
    Jul 2006
    Beans
    9

    Re: HOWTO: Fancontrol

    The CPU_Fan is just a label set in my sensors.conf.
    Code:
    # Fan inputs
       label fan1   "CPU_Fan"
    and changing CPU_Fan_div still gives "unknown feature name" error

    When I tried to run pwnconfig, this was the output:


    Code:
    ~$ sudo 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-002e/pwm1
    /usr/sbin/pwmconfig: line 102: 0-002e/pwm1_enable: Permission denied
       0-002e/pwm2
    /usr/sbin/pwmconfig: line 102: 0-002e/pwm2_enable: Permission denied
       0-002e/pwm3
    /usr/sbin/pwmconfig: line 102: 0-002e/pwm3_enable: Permission denied
    
    Found the following fan sensors:
       0-002e/fan1_input     current speed: 5227 RPM
       0-002e/fan2_input     current speed: 0 ... skipping!
       0-002e/fan3_input     current speed: 0 ... skipping!
       0-002e/fan4_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-002e/pwm1 ...
    /usr/sbin/pwmconfig: line 117: 0-002e/pwm1_enable: Permission denied
      0-002e/fan1_input ... speed was 5227 now 5227
    /usr/sbin/pwmconfig: line 102: 0-002e/pwm1_enable: Permission denied
        no correlation
    
    No correlations were detected.
    There is either no fan connected to the output of 0-002e/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)?
    
    Testing pwm control 0-002e/pwm2 ...
    /usr/sbin/pwmconfig: line 117: 0-002e/pwm2_enable: Permission denied
      0-002e/fan1_input ... speed was 5227 now 5227
    /usr/sbin/pwmconfig: line 102: 0-002e/pwm2_enable: Permission denied
        no correlation
    
    No correlations were detected.
    There is either no fan connected to the output of 0-002e/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)?
    
    Testing pwm control 0-002e/pwm3 ...
    /usr/sbin/pwmconfig: line 117: 0-002e/pwm3_enable: Permission denied
      0-002e/fan1_input ... speed was 5227 now 5232
    /usr/sbin/pwmconfig: line 102: 0-002e/pwm3_enable: Permission denied
        no correlation
    
    No correlations were detected.
    There is either no fan connected to the output of 0-002e/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)?
    
    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)?
    What should be the path to your fancontrol config file (/etc/fancontrol)?
    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
    Any idea how I can change the permission denied when accessing pwmX_enable (X=1,2,3)?

    Thanks again for your prompt reply!

    Tony David Potter

  7. #27
    Join Date
    Jan 2005
    Beans
    65

    Re: HOWTO: Fancontrol

    http://www.lm-sensors.org/ticket/2071

    That's not your exact motherboard, but it looks like the same error...

    Tried "chmod 644 /sys/bus/i2c/devices/0-002e/*enable*" and pwmconfig ran without complaint, but to no effect (fans did not appear to stop/start when tested). Fan speed is still constant.

    According to http://lists.debian.org/debian-user/.../msg03283.html the lm85 kernel module needs to be patched to correct an Intel BIOS misfeature. I haven't tried this.
    I'm sorry I can't help you more than this..

  8. #28
    Join Date
    Sep 2005
    Location
    Austin, TX
    Beans
    925
    Distro
    Ubuntu 7.04 Feisty Fawn

    Exclamation Re: HOWTO: Fancontrol

    Hackers who know about changing fan speed could be a dangerous and expensive thing. Window's XP is easily hacked through trojans, and if the people who got into a Window's XP computer were able to change the fans' speeds, BYE BYE cpu. Those things would be smoking without a fan. They can get hot.
    Last edited by fakie_flip; August 7th, 2006 at 01:56 PM.

  9. #29
    Join Date
    Sep 2005
    Location
    Austin, TX
    Beans
    925
    Distro
    Ubuntu 7.04 Feisty Fawn

    Question Re: HOWTO: Fancontrol

    why is my cpu fan speed not being shown? i followed the directions.
    Code:
     You do not need any special privileges for this.
     Do you want to probe now? (YES/no):
    Probing for PCI bus adapters...
    Use driver `rivatv' for device 01:00.0: RIVA UVTNT2
    Use driver `i2c-sis96x' for device 00:02.1: Silicon Integrated Systems SMBus Con troller
    Probe succesfully concluded.
    
    As you are not root, we can't load adapter modules. We will only scan
    already loaded adapters.
    If you have undetectable or unsupported adapters, you can have them
    scanned by manually loading the modules before running this script.
    
     To continue, we need module `i2c-dev' to be loaded.
     If it is built-in into your kernel, you can safely skip this.
     i2c-dev is not loaded. As you are not root, we will just hope you edited
     `/etc/modules.conf' for automatic loading of
     this module. If not, you won't be able to open any /dev/i2c-* file.
    
     We are now going to do the adapter probings. Some adapters may hang halfway
     through; we can't really help that. Also, some chips will be double detected;
     we choose the one with the highest confidence value in that case.
     If you found that the adapter hung after probing a certain address, you can
     specify that address to remain unprobed. That often
     includes address 0x69 (clock chip).
    
    Some chips are also accessible through the ISA bus. ISA probes are
    typically a bit more dangerous, as we have to write to I/O ports to do
    this. This is usually safe though.
    
    As you are not root, we shall skip this step.
    
    Some Super I/O chips may also contain sensors. Super I/O probes are
    typically a bit more dangerous, as we have to write to I/O ports to do
    this. This is usually safe though.
    
    As you are not root, we shall skip this step.
    
     Sorry, no chips were detected.
     Either your sensors are not supported, or they are
     connected to an I2C bus adapter that we do not support.
     See doc/FAQ, doc/lm_sensors-FAQ.html, or
     http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
     (FAQ #4.24.3) for further information.
     If you find out what chips are on your board, see
     http://secure.netroedge.com/~lm78/newdrivers.html for driver status.
    ubuntu@ubuntu:~$ sudo sensors-detect
    # sensors-detect revision 1.393 (2005/08/30 18:51:18)
    
    This program will help you determine which I2C/SMBus modules you need to
    load to use lm_sensors most effectively. You need to have i2c and
    lm_sensors installed before running this program.
    Also, you need to be `root', or at least have access to the /dev/i2c-*
    files, for most things.
    If you have patched your kernel and have some drivers built in, you can
    safely answer NO if asked to load some modules. In this case, things may
    seem a bit confusing, but they will still work.
    
    It is generally safe and recommended to accept the default answers to all
    questions, unless you know what you're doing.
    
     We can start with probing for (PCI) I2C or SMBus adapters.
     You do not need any special privileges for this.
     Do you want to probe now? (YES/no):
    Probing for PCI bus adapters...
    Use driver `rivatv' for device 01:00.0: RIVA UVTNT2
    Use driver `i2c-sis96x' for device 00:02.1: Silicon Integrated Systems SMBus Con troller
    Probe succesfully concluded.
    
    We will now try to load each adapter module in turn.
    Load `rivatv' (say NO if built into your kernel)? (YES/no):
    FATAL: Module rivatv not found.
    Loading failed... skipping.
    ** Note: rivatv module is available at http://rivatv.sourceforge.net/
    Module `i2c-sis96x' already loaded.
    If you have undetectable or unsupported adapters, you can have them
    scanned by manually loading the modules before running this script.
    
     To continue, we need module `i2c-dev' to be loaded.
     If it is built-in into your kernel, you can safely skip this.
     i2c-dev is not loaded. Do you want to load it now? (YES/no):
     Module loaded succesfully.
    
     We are now going to do the adapter probings. Some adapters may hang halfway
     through; we can't really help that. Also, some chips will be double detected;
     we choose the one with the highest confidence value in that case.
     If you found that the adapter hung after probing a certain address, you can
     specify that address to remain unprobed. That often
     includes address 0x69 (clock chip).
    
    Next adapter: SiS96x SMBus adapter at 0x0c00
    Do you want to scan it? (YES/no/selectively):
    Client found at address 0x50
    Probing for `SPD EEPROM'... Success!
        (confidence 8, driver `eeprom')
    Probing for `DDC monitor'... Failed!
    Probing for `Maxim MAX6900'... Failed!
    Client found at address 0x51
    Probing for `SPD EEPROM'... Success!
        (confidence 8, driver `eeprom')
    Client found at address 0x69
    Client found at address 0x6a
    
    Some chips are also accessible through the ISA bus. ISA probes are
    typically a bit more dangerous, as we have to write to I/O ports to do
    this. This is usually safe though.
    
    Do you want to scan the ISA bus? (YES/no):
    Probing for `National Semiconductor LM78'
      Trying address 0x0290... Failed!
    Probing for `National Semiconductor LM78-J'
      Trying address 0x0290... Failed!
    Probing for `National Semiconductor LM79'
      Trying address 0x0290... Failed!
    Probing for `Winbond W83781D'
      Trying address 0x0290... Failed!
    Probing for `Winbond W83782D'
      Trying address 0x0290... Failed!
    Probing for `Winbond W83627HF'
      Trying address 0x0290... Failed!
    Probing for `Winbond W83627EHF'
      Trying address 0x0290... Failed!
    Probing for `Winbond W83697HF'
      Trying address 0x0290... Failed!
    Probing for `Silicon Integrated Systems SIS5595'
      Trying general detect... Failed!
    Probing for `VIA Technologies VT82C686 Integrated Sensors'
      Trying general detect... Failed!
    Probing for `VIA Technologies VT8231 Integrated Sensors'
      Trying general detect... Failed!
    Probing for `ITE IT8712F'
      Trying address 0x0290... Failed!
    Probing for `ITE IT8705F / SiS 950'
      Trying address 0x0290... Success!
        (confidence 7, driver `it87')
    Probing for `IPMI BMC KCS'
      Trying address 0x0ca0... Failed!
    Probing for `IPMI BMC SMIC'
      Trying address 0x0ca8... Failed!
    
    Some Super I/O chips may also contain sensors. Super I/O probes are
    typically a bit more dangerous, as we have to write to I/O ports to do
    this. This is usually safe though.
    
    Do you want to scan for Super I/O sensors? (YES/no):
    Probing for `ITE 8702F Super IO Sensors'
      Failed! (0x8705)
    Probing for `ITE 8705F Super IO Sensors'
      Success... found at address 0x0290
    Probing for `ITE 8712F Super IO Sensors'
      Failed! (0x8705)
    Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
      Failed! (skipping family)
    Probing for `SMSC 47B27x Super IO Fan Sensors'
      Failed! (skipping family)
    Probing for `VT1211 Super IO Sensors'
      Failed! (skipping family)
    Probing for `Winbond W83627EHF/EHG Super IO Sensors'
      Failed! (skipping family)
    
    Do you want to scan for secondary Super I/O sensors? (YES/no):
    Probing for `ITE 8702F Super IO Sensors'
      Failed! (0x8705)
    Probing for `ITE 8705F Super IO Sensors'
      Success... found at address 0x0290
    Probing for `ITE 8712F Super IO Sensors'
      Failed! (0x8705)
    Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
      Failed! (skipping family)
    Probing for `SMSC 47B27x Super IO Fan Sensors'
      Failed! (skipping family)
    Probing for `VT1211 Super IO Sensors'
      Failed! (skipping family)
    Probing for `Winbond W83627EHF/EHG Super IO Sensors'
      Failed! (skipping family)
    
     Now follows a summary of the probes I have just done.
     Just press ENTER to continue:
    
    Driver `eeprom' (should be inserted):
      Detects correctly:
      * Bus `SiS96x SMBus adapter at 0x0c00'
        Busdriver `i2c-sis96x', I2C address 0x50
        Chip `SPD EEPROM' (confidence: 8)
      * Bus `SiS96x SMBus adapter at 0x0c00'
        Busdriver `i2c-sis96x', I2C address 0x51
        Chip `SPD EEPROM' (confidence: 8)
    
    Driver `it87' (should be inserted):
      Detects correctly:
      * ISA bus address 0x0290 (Busdriver `i2c-isa')
        Chip `ITE 8705F Super IO Sensors' (confidence: 9)
    
    
     I will now generate the commands needed to load the I2C modules.
     Sometimes, a chip is available both through the ISA bus and an I2C bus.
     ISA bus access is faster, but you need to load an additional driver module
     for it. If you have the choice, do you want to use the ISA bus or the
     I2C/SMBus (ISA/smbus)?
    
    To make the sensors modules behave correctly, add these lines to
    /etc/modules:
    
    #----cut here----
    # I2C adapter drivers
    i2c-sis96x
    i2c-isa
    # I2C chip drivers
    eeprom
    it87
    #----cut here----
    
    Do you want to add these lines to /etc/modules automatically? (yes/NO)yes
    
    ubuntu@ubuntu:~$ sudo modprobe i2c-sensor
    FATAL: Module i2c_sensor not found.
    ubuntu@ubuntu:~$ sudo modprobe i2c-viapro
    ubuntu@ubuntu:~$ sudo modprobe i2c-isa
    ubuntu@ubuntu:~$ sudo modprobe it87
    ubuntu@ubuntu:~$ sudo depmod -a ( I canceled this because it didnt do anything)
    
    ubuntu@ubuntu:~$
    ubuntu@ubuntu:~$ sudo update-modules
    ubuntu@ubuntu:~$ sensors
    it87-isa-0290
    Adapter: ISA adapter
    VCore 1:   +1.65 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
    VCore 2:   +2.50 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
    +3.3V:     +6.40 V  (min =  +8.16 V, max =  +8.16 V)   ALARM
    +5V:       +4.78 V  (min =  +6.85 V, max =  +6.85 V)   ALARM
    +12V:     +12.22 V  (min = +16.32 V, max = +16.32 V)   ALARM
    -12V:      -1.71 V  (min =  +3.93 V, max =  +3.93 V)   ALARM
    -5V:       +2.36 V  (min =  +4.03 V, max =  +4.03 V)   ALARM
    Stdby:     +4.95 V  (min =  +6.85 V, max =  +6.85 V)   ALARM
    VBat:      +2.03 V
    fan1:     3515 RPM  (min =    0 RPM, div = 8)
    fan2:        0 RPM  (min =    0 RPM, div = 8)
    fan3:        0 RPM  (min =    0 RPM, div = 2)
    M/B Temp:    +36C  (low  =    -1C, high =    -1C)   sensor = thermistor
    CPU Temp:    +43C  (low  =    -1C, high =    -1C)   sensor = thermistor
    Temp3:       +44C  (low  =    -1C, high =    -1C)   sensor = thermistor
    
    ubuntu@ubuntu:~$

  10. #30
    Join Date
    Jan 2005
    Beans
    65

    Re: HOWTO: Fancontrol

    Try sudo.

Page 3 of 12 FirstFirst 12345 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •