great tutorial....
I will try it
great tutorial....
I will try it
I give up. Been at it for sometime now. I could pay for anyone to fix this mess. I need my workstation to shut the hell up before it drives me crazy. With windows it runs super silent. The minute I reboot Ubuntu it gets really loud. I've followed several tutorials & methods but no use. Attached is screen shot of my xsensor readings & lm-sensor info.
It seems like you're reading your motherboard sensor twice, though that is not necessarily the cause of the fan noise.
Post the contents of your /etc/modules file and the full output when you run sensors-detect.
And post it in code boxes please, instead of using screenshots.
Code:code box
thanks for reply
this is when I run sensors
then i run sudo sensors-detectCode:w83627hf-isa-0290 Adapter: ISA adapter in0: +3.49 V (min = +0.00 V, max = +4.08 V) in1: +3.50 V (min = +0.00 V, max = +4.08 V) in2: +3.49 V (min = +2.82 V, max = +3.79 V) in3: +3.02 V (min = +0.77 V, max = +0.59 V) ALARM in4: +3.02 V (min = +1.17 V, max = +3.38 V) in5: +3.04 V (min = +1.34 V, max = +0.61 V) ALARM in6: +3.06 V (min = +0.58 V, max = +3.58 V) in7: +3.36 V (min = +0.06 V, max = +2.74 V) ALARM in8: +3.30 V (min = +3.12 V, max = +2.05 V) ALARM fan1: 4326 RPM (min = 712 RPM, div = 8) fan2: 4326 RPM (min = 712 RPM, div = 8) fan3: 0 RPM (min = 2960 RPM, div = 8) ALARM temp1: -43.0°C (high = +27.0°C, hyst = +24.0°C) sensor = thermistor temp2: -43.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor temp3: -43.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor cpu0_vid: +0.000 V beep_enable:enabled w83792d-i2c-0-2f Adapter: SMBus I801 adapter at 1100 VcoreA: +1.27 V (min = +0.00 V, max = +2.04 V) VcoreB: +1.32 V (min = +0.00 V, max = +2.04 V) in2: +3.28 V (min = +2.96 V, max = +3.62 V) in3: +2.92 V (min = +2.69 V, max = +3.30 V) in4: +0.52 V (min = +0.30 V, max = +0.75 V) in5: +3.05 V (min = +2.83 V, max = +3.47 V) +5V: +4.85 V (min = +4.49 V, max = +5.50 V) 5VSB: +4.87 V (min = +4.49 V, max = +5.50 V) Vbat: +3.17 V (min = +2.69 V, max = +3.30 V) fan1: 0 RPM (min = 712 RPM, div = 8) ALARM fan2: 0 RPM (min = 712 RPM, div = 8) ALARM fan3: 0 RPM (min = 712 RPM, div = 8) ALARM fan4: 0 RPM (min = 712 RPM, div = 8) ALARM fan5: 2445 RPM (min = 712 RPM, div = 8) fan6: 2678 RPM (min = 712 RPM, div = 8) temp1: +35.0°C (high = +75.0°C, hyst = +70.0°C) temp2: +37.5°C (high = +75.0°C, hyst = +70.0°C) temp3: +32.0°C (high = +80.0°C, hyst = +75.0°C)
i enter my password
answer yes to all questions
plz check the output /etc/modules
Code:# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. lp # Generated by sensors-detect on Sat May 28 14:10:42 2011 # Adapter drivers i2c_i801 ipmi-si # Chip drivers lm90 w83627hf w83792d # Generated by sensors-detect on Sat May 28 14:16:00 2011 # Adapter drivers i2c_i801 ipmi-si # Chip drivers lm90 w83627hf w83792d # Generated by sensors-detect on Sun May 29 17:51:57 2011 # Adapter drivers i2c_i801 ipmi-si # Chip drivers lm90 w83627hf w83792d
1st of all, your /etc/modules file is a bit of a mess. Each time you answer YES to the last question of sensors-detect the found sensors will be added to the /etc/modules file, even if the sensor is listed in the file already.
The second thing that doesn't seem to be right is that sensors-detect found 2 motherboard sensors, w83627hf and w83792d. Probably only 1 of the 2 found sensors is the right one.
When you run sensors-detect, after the detection process, you get a summary of the sensors that where found. Every sensor gets a "confidence" value (higher number == higher confidence). This can help you determine which of the 2 motherboard sensors sensors-detect found is the correct one. See example below.
To fix your /etc/modules file open it in an editor as root:Code:... cut ... 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 #----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) Unloading i2c-dev... OK Unloading cpuid... OK
and change it to something like:Code:gksudo gedit /etc/modules
I omitted the w83627hf sensor assuming the w83792d is the correct sensor.Code:# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. lp # Inspired by sensors-detect on Sun May 29 2011 # Adapter drivers i2c_i801 ipmi-si # Chip drivers lm90 w83792d
That said, after cleaning up your /etc/modules file you still might have fan noise issues. After all lm-sensors only reads the sensors and doesn't change the fan speed. There are fan controlling programs mentioned in this thread, but I've never had to use them and can't help you with those programs. Personally I control my fans from the BIOS.
One last point: Linux often lags behind windows a little when it comes to supporting brand new hardware. If your motherboard/PC/laptop was introduced to the market less than 6 months ago it is likely that devs and bug-reporters are still working on making the hardware work as you would expect it to. My hot-from-the-factory laptop and linux didn't fall in love at first sight, their love grew a little every month and now they are inseparable.
Last edited by miegiel; May 29th, 2011 at 06:53 PM.
Dear miegiel, thanx alot for the info. am fairly new to Ubuntu world. Owe You 1 .. I've fixed my output/etc/modules & you were right, noise/fan issue is still on going. My machine is a 2006 BoxxTech. I'd assume it's not new. Bios already set to run (super quiet) but nothing it's certainly not when booting Ubuntu. Oh well I guess I have to live with this. thanx again.
I kinda got lm-senosors working. I can't find my chipset in /etc/sensors3.conf. I think it's Intel HM55. I have an Inspiron 1564. Here is the output from sensors.
I'd like to get lm-sensors working correctly/fully.Code:acpitz-virtual-0 Adapter: Virtual device temp1: +26.8°C (crit = +100.0°C) temp2: +0.0°C (crit = +100.0°C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +62.0°C (high = +80.0°C, crit = +90.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 2: +64.0°C (high = +80.0°C, crit = +90.0°C)
@akernan Did you runin a terminal?Code:sudo sensors-detect
It should help you detect the correct sensor (pay attention to the confidence value when in doubt).
Hi, I recently installed a few updates on my lucid LTS box and now lm-sensors no longer works. I had a lot of trouble getting it working to begin with and now I'm extremely lost.
This is the output of sensors-detect using the default options:
I have copied files around as suggested as I would like to to start at boot. When a reboot didn't get things working I then tried to start the service manually, service lm-sensors start, but I get this error message: .: 39: Can't open /etc/init.d/functions. Looking in my /etc/init.d directory, there is no functions file!Code:# sensors-detect revision 5946 (2011-03-23 11:54:44 +0100) # System: Packard Bell ixtreme M5800 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 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'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8721F/IT8758E Super IO Sensors' Success! (address 0xa10, 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): 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): 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 3400/5 Series (PCH) 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): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `it87': * ISA bus, address 0xa10 Chip `ITE IT8721F/IT8758E Super IO Sensors' (confidence: 9) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK Unloading i2c-i801... OK Unloading cpuid... OK
sensors just gives
which is a far cry from what it used to produce. I don't actually know what its attempting to measure there but it doesn't tally up with what the bios measurements are, whatever it is...Code:acpitz-virtual-0 Adapter: Virtual device temp1: +30.0°C (crit = +110.0°C)
/etc/modules contains
I've been looking around and other scripts that have issues with a missing functions file tend to just comment an offending line out. Other times I've seen it get replaced with /lib/lsb/init-functions, which I do have. Is this the safest thing to do or is there some unmet dependency that hasn't been met / did I miss something?Code:# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. lp modprobe modprobe # For temperature sensing coretemp it87
Any help's appreciated, and if anyone needs any more info please let me know!
Cheers!
Yes, I did. Here's the output from sudo sensors-detect.
Here's my /etc/moduleCode:tony@tony-Inspiron-1564:~$ sudo sensors-detect [sudo] password for tony: # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200) # System: Dell Inc. Inspiron 1564 (laptop) # Board: Dell Inc. 08CNC9 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): 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'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... Yes Found unknown chip with ID 0x8502 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): 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 3400/5 Series (PCH) Next adapter: intel drm CRTDDC_A (i2c-0) Do you want to scan it? (YES/no/selectively): Next adapter: intel drm LVDSDDC_C (i2c-1) Do you want to scan it? (YES/no/selectively): Client found at address 0x28 Probing for `National Semiconductor LM78'... No Probing for `National Semiconductor LM79'... No Probing for `National Semiconductor LM80'... No Probing for `Winbond W83781D'... No Probing for `Winbond W83782D'... No Probing for `Winbond W83627HF'... No Probing for `Winbond W83627EHF'... No Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No Probing for `Asus AS99127F (rev.1)'... No Probing for `Asus AS99127F (rev.2)'... No Probing for `Asus ASB100 Bach'... No Probing for `Analog Devices ADM1029'... No Probing for `ITE IT8712F'... No 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: intel drm HDMIB (i2c-2) Do you want to scan it? (YES/no/selectively): Next adapter: DPDDC-B (i2c-3) Do you want to scan it? (YES/no/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): n To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp /usr/bin/sensors -s #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. tony@tony-Inspiron-1564:~$ sudo modprobe coretemp tony@tony-Inspiron-1564:~$ sensors -s tony@tony-Inspiron-1564:~$ sensors acpitz-virtual-0 Adapter: Virtual device temp1: +26.8°C (crit = +100.0°C) temp2: +0.0°C (crit = +100.0°C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +60.0°C (high = +80.0°C, crit = +90.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 2: +62.0°C (high = +80.0°C, crit = +90.0°C)
Code:# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. lp rtc #lm-sensors & i2c cpuid i2c-i801 i2c-dev coretemp
Last edited by akernan; October 12th, 2011 at 03:18 AM.
Bookmarks