It's very easy to install. Just follow this guide.
Anyway, is there a way to monitor the sensors remotely, like a widget for Gnome or Android?
It's very easy to install. Just follow this guide.
Anyway, is there a way to monitor the sensors remotely, like a widget for Gnome or Android?
Okay, I'm getting real tired of Windows 7 on my machine. The OS is a great improvement but it is so slow when several applications are running, that I want to switch to Ubuntu once and for all. But....my computer is so noisy that it is barely usable without a software like speedfan that can easily regulate the CPU fanspeed.
Therefore, before I dive into this :
will lm-sensors will let me regulate the CPU speed fan whenever I want ? I don't want to go back in the console every time I want to decrease or increase the speed.
Is there a script or a interface making the operation easier ?
Thank you. If the question has already been asked, don't hesitate to answer me with a link...
Hi guys
I've got lm-sensors installed and working and I'm now trying to figure out what it all means. I'm trying to wade through the 42 pages of this post as well as the lm-sensors documentation on their website, but I think I'm a little out of my depth here! Here's my output:
it8718-isa-0228
Adapter: ISA adapter
in0: +1.07 V (min = +0.00 V, max = +4.08 V)
in1: +1.60 V (min = +0.00 V, max = +4.08 V)
in2: +3.38 V (min = +0.00 V, max = +4.08 V)
in3: +3.04 V (min = +0.00 V, max = +4.08 V)
in4: +3.09 V (min = +0.00 V, max = +4.08 V)
in5: +3.38 V (min = +0.00 V, max = +4.08 V)
in6: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
in7: +2.30 V (min = +0.00 V, max = +4.08 V)
Vbat: +3.18 V
fan1: 3214 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: +42.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp2: +42.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode
temp3: +44.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
cpu0_vid: +1.050 V
So now I'm trying to figure out what in6 is, why it's so high and if this means I need to re-evaluate my hardware setup?
Thanks,
Tass
Okay, coming back here with more precise questions...
I just installed Ubuntu to test lm-sensors. First off, I'm impressed with the lower CPU fan speed that the system offers compared to Windows. It does get noisy when heavier applications are launched but it's almost tolerable in "surf mode".
Now, I just typed the "sudo sensors-detect" command in the terminal and this is what I got :
Code:# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100) # System: ASUSTeK Computer INC. ATI-Xpress200 # Board: ASUSTeK Computer INC. P5R8L 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): y 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 Intel Core family thermal sensor... No Intel Atom thermal sensor... No 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): y Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8712F Super IO Sensors' Success! (address 0x228, driver `it87') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... 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): y 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): y 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): y Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc IXP SB400 SMBus Controller Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0) Do you want to scan it? (YES/no/selectively): y 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) Next adapter: (i2c-1) Do you want to scan it? (YES/no/selectively): y Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Probing for `EDID EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: (i2c-2) Do you want to scan it? (YES/no/selectively): y Next adapter: (i2c-3) Do you want to scan it? (YES/no/selectively): y Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `it87': * ISA bus, address 0x228 Chip `ITE IT8712F Super IO Sensors' (confidence: 9) To load everything that is needed, add this to /etc/modules: #----cut here---- # Chip drivers it87 #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! Do you want to add these lines automatically to /etc/modules? (yes/NO)y Successful! Monitoring programs won't work until the needed modules are loaded. You may want to run '/etc/init.d/module-init-tools start' to load them. Unloading i2c-dev... OK
And when typing sudo pwmconfig
Code:# pwmconfig revision 5770 (2009-09-16) 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. /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
It doesn't seem to identify my CPU fan at all. Beside, when installing the sensors applet for the Gnome Panel, most of the sensors seems undetected (temperature stays at 40° while SpeedFan in Windows has a 55-65° average), no fanspeed, etc. The thing is : it did work in previous versions of Ubuntu (9.10, I'm pretty sure), with the exact same machine (nothing was changed since then). Why isn't it working now ?
I just want to be able to easily decrease or increase the CPU fan speed depending on the system's temperatures. That's the two variables I would like to see working !
I have an Asus Pundit P1-PH1, Intel Pentium D 2,66 GHZ, AsusTek P5RL8 motherboard, Ati Xpress 200 graphic card and a Western Digital Eco Green 1 To hard drive.
Thank you !
Last edited by DannyBiker; June 8th, 2010 at 07:37 AM.
I desactived the Q-Fan Control in the BIOS. Now, the sensors applet gives me the right variables (including the Fan). But sensors-detect and pwnconfig still gives me nothing...
Okay, I'm back with my questions after a fresh install.
I managed to have my CPU fan detected, the one I want to be able to switch the speed depending on my computer temperature.
This is what I get with pwnconfig :
What should I do now to get speed fan control ? I don't understand how can I obtain that.Code:sudo pwmconfig # pwmconfig revision 5770 (2009-09-16) 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 it8712 Found the following PWM controls: hwmon1/device/pwm1 hwmon1/device/pwm2 hwmon1/device/pwm3 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon1/device/fan1_input current speed: 4326 RPM 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 hwmon1/device/pwm1 ... hwmon1/device/fan1_input ... speed was 4326 now 0 It appears that fan hwmon1/device/fan1_input is controlled by pwm hwmon1/device/pwm1 Would you like to generate a detailed correlation (y)? y Note: If you had gnuplot installed, I could generate a graphical plot. PWM 255 FAN 4218 PWM 240 FAN 4218 PWM 225 FAN 4218 PWM 210 FAN 4017 PWM 195 FAN 3668 PWM 180 FAN 3443 PWM 165 FAN 3125 PWM 150 FAN 2909 PWM 135 FAN 2556 PWM 120 FAN 2280 PWM 105 FAN 1985 PWM 90 FAN 1670 PWM 75 FAN 1350 PWM 60 FAN 986 PWM 45 FAN 0 Fan Stopped at PWM = 45 Testing pwm control hwmon1/device/pwm2 ... hwmon1/device/fan1_input ... speed was 4326 now 4326 no correlation No correlations were detected. There is either no fan connected to the output of hwmon1/device/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 Testing pwm control hwmon1/device/pwm3 ... hwmon1/device/fan1_input ... speed was 4326 now 4218 no correlation No correlations were detected. There is either no fan connected to the output of hwmon1/device/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 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)? y Select fan output to configure, or other action: 1) hwmon1/device/pwm1 3) Just quit 5) Show configuration 2) Change INTERVAL 4) Save and quit
Thank you !
I have a simillar out put so I'm thinking I did something wrong in the setup. Myne is:
sensors
w83627thf-isa-0290
Adapter: ISA adapter
in0: +1.57 V (min = +0.00 V, max = +3.84 V)
in1: +3.15 V (min = +0.69 V, max = +0.38 V) ALARM
in2: +3.25 V (min = +0.10 V, max = +0.54 V) ALARM
in3: +2.99 V (min = +2.38 V, max = +0.00 V) ALARM
in4: +2.51 V (min = +0.06 V, max = +0.45 V) ALARM
in7: +2.96 V (min = +1.44 V, max = +1.34 V) ALARM
in8: +3.20 V (min = +0.51 V, max = +2.30 V) ALARM
fan1: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan2: 3183 RPM (min = 21093 RPM, div = 2) ALARM
fan3: 0 RPM (min = 2109 RPM, div = 128) ALARM
temp1: +41.0°C (high = -125.0°C, hyst = +40.0°C) ALARM sensor = thermistor
temp2: +40.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
temp3: +5.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
beep_enable:enabled
Any way someone can point me in the re=ight direction as to identefying what's what?
Well, seeing as I already had lm-sensors installed by default, I tried to run it, thinking all the stuff was configured already and that I just had to run the YES/no stuff once. That didn't work, so then I tried to do the walkthrough. I obtained the following output:
I seem to have borked something here, since step 3 isn't supposed to spew this out when I run sensors-detect. Is there some way to undo any changes or delete any files created by running "mkdev.sh", as well as delete anything made by running the YES/no sequence? In effect, I want to totally undo any changes made by running this walkthrough.Code:# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100) # System: Dell Inc. Inspiron 1501 # Board: Dell Inc. 0UW744 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): yes Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... Success! (driver `k8temp') AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No Intel Core family thermal sensor... No Intel Atom thermal sensor... No 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): yes Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... Yes Found `Nat. Semi. PC87591 Super IO' (address 0x200, but not activated) Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... 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): yes 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): no Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `k8temp' (autoloaded): * Chip `AMD K8 thermal sensors' (confidence: 9) No modules to load, skipping modules configuration.
Last edited by Vimmander; August 3rd, 2010 at 12:31 PM.
Dell Inspiron 1501, AMD Athlon(tm) 64 X2 Dual-Core Processor TK-53, ATI Radeon Xpress 200M, Broadcom BCM4311 802.11b/g WLAN, 120GB SATA (Windows 7/Ubuntu Precise dual boot), 2GB DIMM DRAM, SBx00 Azalia (Intel HDA)
Install lm-sensors and run sensors-detect. No sensors were detected.Code:# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100) # System: TOSHIBA Satellite L500 (laptop) # Board: TOSHIBA NSWAA 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): yes 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 Intel Core family thermal sensor... No Intel Atom thermal sensor... No 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): yes Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... 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): yes Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3. Sorry, no supported PCI bus adapters found. Sorry, no sensors were detected. This is relatively common on laptops, where thermal management is handled by ACPI rather than the OS.
What can i do?
Last edited by amishaa; August 31st, 2010 at 02:14 AM. Reason: misprint
Bookmarks