Results 1 to 5 of 5

Thread: Cannot control CPU fan speed on ASUS Rampage II Gene Mobo

  1. #1
    Join Date
    May 2009
    Beans
    143

    Cannot control CPU fan speed on ASUS Rampage II Gene Mobo

    EDIT3: After some bickering and a lot of off-topic posts, allow me to clarify: I'm not seeking advice on how to keep my system cool, what's the correct temperature for a processor, etc. The question, I hope, should be fairly precisely worded below. Please don't respond with suggestions on how to overclock/BIOS control/use Windows etc. for this. This question is about lmsensors and fancontrol, nothing else. If you feel like you know something other than this, PM me, please don't reply to this thread. Thanks

    ---------------

    Hey

    I'm trying to control the CPU fan using lmsensors and fancontrol. The motherboard is an ASUS Rampage II Gene. In Winblahblah I have no problems controlling the fan using the horrible ASUS utility.

    In Kubuntu (12.04), however, the story's a bit different. At first, I couldn't even detect the sensors properly, but http://forums.opensuse.org/english/g...dules-run.html made me add "acpi_enforce_resources=lax" to the kernel boot options. This made sensors-detect detect a whole lot more.

    The pwmconfig doesn't succeed in actually turning off or on any of the fans (actually, there's just one attached to the mobo, the CPU one, "fan2"). It reads the current RPM correctly, but fails to change it. The fan is a four-pin one, btw. Remember it works in Winblows. It also fails to write a usable /etc/fancontrol file.

    I can get the RPM by doing
    $ cat /sys/class/hwmon/hwmon1/device/fan2_input

    But I can't change it by doing (as root)
    $ echo "<some number>" > /sys/class/hwmon/hwmon1/device/pwm2

    Any ideas? I'm stomped, and pretty tired of listening to this monster CPU fan. It should be running at 300 RPM until 74° C, and then start accelerating, but it's idling at around 1700 RPM (and, as mentioned, it's a monster).

    Thanks in advance,
    Daniel

    EDIT: Adding sensors-detect output:
    Code:
    daniel@rogx:~$ sudo sensors-detect 
    [sudo] password for daniel: 
    # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
    # System: System manufacturer System Product Name
    # Board: ASUSTeK Computer INC. Rampage II GENE
    
    This program will help you determine which kernel modules you need
    to load to use lm_sensors most effectively. It is generally safe
    and recommended to accept the default answers to all questions,
    unless you know what you're doing.
    
    Some south bridges, CPUs or memory controllers contain embedded sensors.
    Do you want to scan for them? This is totally safe. (YES/no): 
    Module cpuid loaded successfully.
    Silicon Integrated Systems SIS5595...                       No
    VIA VT82C686 Integrated Sensors...                          No
    VIA VT8231 Integrated Sensors...                            No
    AMD K8 thermal sensors...                                   No
    AMD Family 10h thermal sensors...                           No
    AMD Family 11h thermal sensors...                           No
    AMD Family 12h and 14h thermal sensors...                   No
    AMD Family 15h thermal sensors...                           No
    AMD Family 15h power sensors...                             No
    Intel digital thermal sensor...                             Success!
        (driver `coretemp')
    Intel AMB FB-DIMM thermal sensor...                         No
    VIA C7 thermal sensor...                                    No
    VIA Nano thermal sensor...                                  No
    
    Some Super I/O chips contain embedded sensors. We have to write to
    standard I/O ports to probe them. This is usually safe.
    Do you want to scan for Super I/O sensors? (YES/no): 
    Probing for Super-I/O at 0x2e/0x2f
    Trying family `National Semiconductor/ITE'...               No
    Trying family `SMSC'...                                     No
    Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
    Found `Winbond W83667HG Super IO Sensors'                   Success!
        (address 0x290, driver `w83627ehf')
    Probing for Super-I/O at 0x4e/0x4f
    Trying family `National Semiconductor/ITE'...               No
    Trying family `SMSC'...                                     No
    Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
    Trying family `ITE'...                                      No
    
    Some systems (mainly servers) implement IPMI, a set of common interfaces
    through which system health data may be retrieved, amongst other things.
    We first try to get the information from SMBIOS. If we don't find it
    there, we have to read from arbitrary I/O ports to probe for such
    interfaces. This is normally safe. Do you want to scan for IPMI
    interfaces? (YES/no): 
    Probing for `IPMI BMC KCS' at 0xca0...                      No
    Probing for `IPMI BMC SMIC' at 0xca8...                     No
    
    Some hardware monitoring chips are accessible through the ISA I/O ports.
    We have to write to arbitrary I/O ports to probe them. This is usually
    safe though. Yes, you do have ISA I/O ports even if you do not have any
    ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
    Probing for `National Semiconductor LM78' at 0x290...       No
    Probing for `National Semiconductor LM79' at 0x290...       No
    Probing for `Winbond W83781D' at 0x290...                   No
    Probing for `Winbond W83782D' at 0x290...                   No
    
    Lastly, we can probe the I2C/SMBus adapters for connected hardware
    monitoring devices. This is the most risky part, and while it works
    reasonably well on most systems, it has been reported to cause trouble
    on some systems.
    Do you want to probe the I2C/SMBus adapters now? (YES/no): 
    Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
    Module i2c-i801 loaded successfully.
    Module i2c-dev loaded successfully.
    
    Next adapter: SMBus I801 adapter at 0400 (i2c-0)
    Do you want to scan it? (YES/no/selectively): 
    Client found at address 0x4e
    Probing for `National Semiconductor LM75'...                No
    Probing for `National Semiconductor LM75A'...               No
    Probing for `Dallas Semiconductor DS75'...                  No
    Probing for `Dallas Semiconductor DS1621/DS1631'...         No
    Probing for `Analog Devices ADM1021'...                     No
    Probing for `Analog Devices ADM1021A/ADM1023'...            No
    Probing for `Maxim MAX1617'...                              No
    Probing for `Maxim MAX1617A'...                             No
    Probing for `Maxim MAX1668'...                              No
    Probing for `Maxim MAX1805'...                              No
    Probing for `Maxim MAX1989'...                              No
    Probing for `Maxim MAX6642'...                              No
    Probing for `Maxim MAX6655/MAX6656'...                      No
    Probing for `TI THMC10'...                                  No
    Probing for `National Semiconductor LM84'...                No
    Probing for `Genesys Logic GL523SM'...                      No
    Probing for `Onsemi MC1066'...                              No
    Probing for `Maxim MAX1618'...                              No
    Probing for `Maxim MAX1619'...                              No
    Probing for `National Semiconductor LM82/LM83'...           No
    Probing for `Maxim MAX6654'...                              No
    Probing for `Maxim MAX6690'...                              No
    Probing for `Maxim MAX6659'...                              No
    Probing for `Maxim MAX6647'...                              No
    Probing for `Maxim MAX6680/MAX6681'...                      No
    Probing for `Maxim MAX6695/MAX6696'...                      No
    Probing for `Texas Instruments TMP411'...                   No
    Probing for `Texas Instruments TMP421'...                   No
    Probing for `Texas Instruments TMP422'...                   No
    Probing for `Texas Instruments AMC6821'...                  No
    Probing for `National Semiconductor LM64'...                No
    Probing for `National Semiconductor LM73'...                No
    Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
    Probing for `NXP/Philips SA56004'...                        No
    Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'...       No
    Probing for `Fintek F75111R/RG/N (GPIO)'...                 No
    Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'...        Yes
        (confidence 6, not a hardware monitoring chip)
    Client found at address 0x50
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 Yes
        (confidence 8, not a hardware monitoring chip)
    Probing for `EDID EEPROM'...                                No
    Client found at address 0x51
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 Yes
        (confidence 8, not a hardware monitoring chip)
    Client found at address 0x52
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 Yes
        (confidence 8, not a hardware monitoring chip)
    Client found at address 0x53
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 Yes
        (confidence 8, not a hardware monitoring chip)
    
    Now follows a summary of the probes I have just done.
    Just press ENTER to continue: 
    
    Driver `w83627ehf':
      * ISA bus, address 0x290
        Chip `Winbond W83667HG Super IO Sensors' (confidence: 9)
    
    Driver `coretemp':
      * Chip `Intel digital thermal sensor' (confidence: 9)
    
    To load everything that is needed, add this to /etc/modules:
    #----cut here----
    # Chip drivers
    coretemp
    w83627ehf
    #----cut here----

    EDIT 2: I can switch between full throttle and dynamic fan speed by echoing 0 or 1 respectively to /sys/class/hwmon/hwmon1/device/pwm2_mode. Neither mode allows me to change the speed, though.
    Last edited by DanielBuus; August 2nd, 2012 at 10:45 AM.

  2. #2
    Join Date
    May 2007
    Location
    Virginia, USA
    Beans
    13,250
    Distro
    Ubuntu Mate Development Release

    Re: Cannot control CPU fan speed on ASUS Rampage II Gene Mobo

    Your fan is running fast in Ubuntu because the CPU is running hot. It you just slow down the fan, you risk burning up the CPU. Your better approach would be to see if you can throttle back the CPU. That will slow down the fan accordingly.

    See if the Jupiter applet provides this capability:

    http://ubuntuforums.org/showthread.php?t=1854019
    Ubuntu 17.04 Mate, Mint 18.1 Mate; MS Win 8.1, MS Win10 Pro.
    Will not respond to PM requests for support -- use the forums.

  3. #3
    Join Date
    May 2009
    Beans
    143

    Re: Cannot control CPU fan speed on ASUS Rampage II Gene Mobo

    Quote Originally Posted by Mark Phelps View Post
    Your fan is running fast in Ubuntu because the CPU is running hot. It you just slow down the fan, you risk burning up the CPU. Your better approach would be to see if you can throttle back the CPU. That will slow down the fan accordingly.

    See if the Jupiter applet provides this capability:

    http://ubuntuforums.org/showthread.php?t=1854019
    Hi Mark, I'm not asking why fans change speeds, I'm asking for help on how to control my fan speed using fancontrol.

    Thank you for participating.

  4. #4
    Join Date
    Jul 2012
    Beans
    34

    Re: Cannot control CPU fan speed on ASUS Rampage II Gene Mobo

    You should try changing it via the BIOS.

  5. #5
    Join Date
    May 2009
    Beans
    143

    Re: Cannot control CPU fan speed on ASUS Rampage II Gene Mobo

    There's no option in the BIOS to make fancontrol/lm-sensors work, sorry.

Tags for this Thread

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
  •