lm_sensors

jaykup · 03-23-2006, 11:00 PM

I enabled i2c support in the 2.6 Kernel, and installed the user tools.

root@digital:~# lsmod
Module Size Used by
i2c_dev 7872 0
nvidia 4084240 12
snd_pcm_oss 48288 0
snd_mixer_oss 17024 1 snd_pcm_oss
yealink 10944 0
i2c_amd756 5572 0
ohci_hcd 16324 0
eepro100 26768 0
3c59x 39784 0
root@digital:~# sensors
No sensors found!

root@digital:~# lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] System Controller (rev 20)
00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] AGP Bridge
00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ISA (rev 05)
00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE (rev 04)
00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI (rev 03)
00:07.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-768 [Opus] Audio (rev 03)
00:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] PCI (rev 05)
01:05.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4600] (rev a3)
02:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-768 [Opus] USB (rev 07)
02:05.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 0c)
02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 0d)

I'm running a GA-7dpxdw-p dual AMD motherboard, it loaded the correct module, why does it say no sensors detected?

Bruce Hill · 03-24-2006, 04:54 AM

Have you built and installed the lm_sensors package?
After doing that, have you run "sensors-detect" as root?
If so, did you follow the instructions and modprobe them?
If so, perhaps you can give some more information. Looks
like you have no ISA or I2C SMBus there.

These are my modules:

Code:

bruce@silas:~$ lsmod
Module                  Size  Used by
snd_pcm_oss            40992  0 
snd_mixer_oss          14080  1 snd_pcm_oss
sk98lin               134112  0 
usbhid                 25092  0 
snd_emu10k1            93796  1 
snd_rawmidi            17056  1 snd_emu10k1
snd_ac97_codec         79328  1 snd_emu10k1
snd_ac97_bus            1792  1 snd_ac97_codec
snd_pcm                66120  3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer              17604  2 snd_emu10k1,snd_pcm
snd_page_alloc          7560  2 snd_emu10k1,snd_pcm
snd_util_mem            3136  1 snd_emu10k1
snd_hwdep               6532  1 snd_emu10k1
snd                    39268  10 snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
soundcore               6432  1 snd
usblp                  10176  0 
wlan_scan_sta          10688  1 
ath_pci                72100  0 
ath_rate_sample         9216  1 ath_pci
wlan                  145948  4 wlan_scan_sta,ath_pci,ath_rate_sample
ath_hal               196624  3 ath_pci,ath_rate_sample
uhci_hcd               25680  0 
ehci_hcd               25160  0 
nvidia               4081296  12 
vfat                    9280  3 
ntfs                   85172  1 
w83627hf               21200  0 
hwmon_vid               2048  1 w83627hf
hwmon                   2004  1 w83627hf
eeprom                  5136  0 
i2c_isa                 3136  1 w83627hf
i2c_viapro              6612  0 
i2c_core               15120  4 w83627hf,eeprom,i2c_isa,i2c_viapro

jaykup · 03-24-2006, 08:08 AM

Thanks, I overlooked loading the modules, Everything is working as it should.

Code:

root@digital:~# sensors-detect

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 `i2c-amd756' for device 00:07.3: AMD-768 System Management
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-amd756' 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 already loaded.

 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: SMBus AMD768 adapter at 50e0
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x30
Client found at address 0x31
Client found at address 0x33
Client at address 0x4c can not be probed - unload all client drivers first!
Client at address 0x50 can not be probed - unload all client drivers first!
Client at address 0x51 can not be probed - unload all client drivers first!
Client at address 0x52 can not be probed - unload all client drivers first!
Client at address 0x53 can not be probed - unload all client drivers first!
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
    (confidence 1, driver `smbus-arp')
Client found at address 0x69
Client found at address 0x70
Probing for `Philips Semiconductors PCA9540'... Success!
    (confidence 1, driver `pca9540')

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... Success!
    (confidence 8, driver `w83781d')
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... Failed!
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! (skipping family)
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! (0x52)
Probing for `Winbond W83627HF Super IO Sensors'
  Success... found at address 0x0290
Probing for `Winbond W83627THF Super IO Sensors'
  Failed! (0x52)
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x52)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x52)
Probing for `Winbond W83697SF/UF Super IO PWM'
  Failed! (0x52)
Probing for `Winbond W83L517D Super IO'
  Failed! (0x52)
Probing for `Winbond W83627EHF Super IO Sensors'
  Failed! (0x5217)

Do you want to scan for secondary Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
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 Super IO Sensors'
  Failed! (skipping family)

 Now follows a summary of the probes I have just done.
 Just press ENTER to continue:

Driver `smbus-arp' (should be inserted):
  Detects correctly:
  * Bus `SMBus AMD768 adapter at 50e0'
    Busdriver `i2c-amd756', I2C address 0x61
    Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

Driver `pca9540' (should be inserted):
  Detects correctly:
  * Bus `SMBus AMD768 adapter at 50e0'
    Busdriver `i2c-amd756', I2C address 0x70
    Chip `Philips Semiconductors PCA9540' (confidence: 1)

Driver `w83781d' (may not be inserted):
  Misdetects:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627HF' (confidence: 8)

Driver `w83627hf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627HF 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.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-amd756
modprobe i2c-isa
# I2C chip drivers
# Warning: the required module smbus-arp is not currently installed on your system.
# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the following line.
modprobe smbus-arp
# Warning: the required module pca9540 is not currently installed on your system.
# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the following line.
modprobe pca9540
modprobe w83627hf
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things 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 it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.

root@digital:~# modprobe lm90
root@digital:~# modprobe eeprom
root@digital:~# modprobe smbus-arp
FATAL: Module smbus_arp not found.
root@digital:~# modprobe pca9540
FATAL: Module pca9540 not found.
root@digital:~# modprobe w83781d
root@digital:~# modprobe w83627hf

Code:

root@digital:~# sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1:   +1.74 V  (min =  +0.00 V, max =  +4.08 V)
VCore 2:   +1.73 V  (min =  +0.00 V, max =  +4.08 V)
+3.3V:     +3.25 V  (min =  +0.00 V, max =  +4.08 V)
+5V:       +4.95 V  (min =  +0.00 V, max =  +6.85 V)
+12V:     +12.46 V  (min =  +0.00 V, max = +15.50 V)
-12V:     -13.18 V  (min = -14.91 V, max =  +6.06 V)
-5V:       -5.35 V  (min =  -7.71 V, max =  +5.10 V)
V5SB:      +5.51 V  (min =  +0.00 V, max =  +6.85 V)
VBat:      +2.69 V  (min =  +0.00 V, max =  +4.08 V)
fan1:     5443 RPM  (min =    0 RPM, div = 2)
fan2:     4720 RPM  (min =    0 RPM, div = 2)
fan3:        0 RPM  (min =    0 RPM, div = 2)
temp1:       -41°C  (high =  +127°C)                     sensor = thermistor
temp2:     -42.0°C  (high =  +127°C, hyst =  +128°C)   sensor = thermistor
temp3:     -43.0°C  (high =  +127°C, hyst =  +128°C)   sensor = thermistor
vid:      +1.775 V  (VRM Version 9.0)
alarms:   Chassis intrusion detection                      ALARM
beep_enable:
          Sound alarm disabled

eeprom-i2c-0-53
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       1024

eeprom-i2c-0-52
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-51
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-50
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

lm90-i2c-0-4c
Adapter: SMBus AMD768 adapter at 50e0
M/B Temp:    +54°C  (low  =    +0°C, high =   +70°C)
CPU Temp:  +75.2°C  (low  =  +0.0°C, high = +70.0°C)   ALARM
M/B Crit:    +85°C  (hyst =   +75°C)
CPU Crit:    +85°C  (hyst =   +75°C)

Still needs a little fine tuning.

Bruce Hill · 03-24-2006, 08:19 AM

Yeah, your temps are all wrong. If I'm reading it correct,
the ISA bus says ~ -40C and the SMBus says 85C; neither of
which can possibly be correct. I might not have as many
sensors as you, but they're reporting correct temps.

Code:

bruce@silas:~/kernel/linux-2.6.16$ sensors
w83697hf-isa-0290
Adapter: ISA adapter
VCore:     +1.49 V  (min =  +1.71 V, max =  +1.89 V)       ALARM  
+3.3V:     +3.28 V  (min =  +3.14 V, max =  +3.47 V)              
+5V:       +5.08 V  (min =  +4.76 V, max =  +5.24 V)              
+12V:     +11.31 V  (min = +10.82 V, max = +13.19 V)              
-12V:      +1.21 V  (min = -13.18 V, max = -10.80 V)       ALARM  
-5V:       +5.10 V  (min =  -5.25 V, max =  -4.75 V)       ALARM  
V5SB:      +5.51 V  (min =  +4.76 V, max =  +5.24 V)       ALARM  
VBat:      +0.00 V  (min =  +2.40 V, max =  +3.60 V)       ALARM  
fan1:     3590 RPM  (min = 21774 RPM, div = 2)              ALARM  
fan2:     3708 RPM  (min = 2812 RPM, div = 2)                     
temp1:       +28°C  (high =  -124°C, hyst =   +30°C)   sensor = thermistor           
temp2:     +32.0°C  (high =   +80°C, hyst =   +75°C)   sensor = thermistor           
alarms:   Chassis intrusion detection                      ALARM
beep_enable:
          Sound alarm enabled

eeprom-i2c-0-51
Adapter: SMBus Via Pro adapter at 0400
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 0400
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

MY lm_sensors experience is going on 2 days, so I can't
help much. But from all I've read, I'd use just the ISA
bus if you have that option.

jaykup · 03-24-2006, 08:35 AM

Yeah, I've always had whack temperatures..

My bios does record the CPU at around 77C so at least that part is correct :\

They are Barton Mobiles running at 140 x 16 - 2240Mhz each on stock fans ...

Seems its only detecting one of those temperature sensors too .. bah

Bruce Hill · 03-24-2006, 10:06 AM

I didn't pay much attention before. Are they Athlon™ MP Processors ?
If so, I'd definitely put a better fan on top of them. I kept my Bartons
running with the AMD fan until the warranty expired, then loaded a nice
Thermaltake on top. But I never ran over 50C, even overclocking. I'd get
those guys cooled down. Heat will significantly decrease their lifecycle.

I put those commands in /etc/rc.d/rc.modules like this:

Code:

# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended

right at the bottom of the file. And notice I've changed the path of
/usr/local/bin/sensors -s
to
/usr/bin/sensors -s
to reflect the correct Slackware path.

I did this rather than generating that file it suggested.
Slackware uses /etc/rc.d/rc.modules for this rather than
/etc/rc.d/init.d/ as suggested there. Must be for Debian?

jaykup · 03-24-2006, 11:32 AM

Quote:

Originally Posted by Chinaman

I didn't pay much attention before. Are they Athlon™ MP Processors ?
If so, I'd definitely put a better fan on top of them. I kept my Bartons
running with the AMD fan until the warranty expired, then loaded a nice
Thermaltake on top. But I never ran over 50C, even overclocking. I'd get
those guys cooled down. Heat will significantly decrease their lifecycle.

I put those commands in /etc/rc.d/rc.modules like this:

Code:

# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended

right at the bottom of the file. And notice I've changed the path of
/usr/local/bin/sensors -s
to
/usr/bin/sensors -s
to reflect the correct Slackware path.

I did this rather than generating that file it suggested.
Slackware uses /etc/rc.d/rc.modules for this rather than
/etc/rc.d/init.d/ as suggested there. Must be for Debian?

I made that file as it recommended in the sensors-detect command, and changed the path because i used a slackware package to install lm_sensors

The processors are XP-M's with the L5 bridge mod to make them work as MP's

They are running at 140x16 @ 1.79v running 2240Mhz , perhaps the voltage is too high? I had to do the pin mod so changing the voltage and multiplier is a pain.. The FSB is now controlled through the bios, due to a new motherboard (old tyan 2460's power connector burned out, common on those boards).

Can you suggest a good fan that I could keep them around 50C? Remember it has to be able to fit on a dual processor motherboard. 50C is almost unheard of to me with the temps ive been running for years

right now they are pushing 78C

Bruce Hill · 03-24-2006, 11:50 AM

Never ran dual-procs, so don't know about that fan situation.
I'd check with AMD if you can't find something elsewhere, for
a recommendation. They have docs for such, but it's a pain to
wade through them, and your situation is special.

jaykup · 03-24-2006, 12:02 PM

I think I'm going to go with this

http://www.overclockercafe.com/Revie.../Tt_Volcano12/

It only looks wider where it doesnt connect to the motherboard, and I have plenty of room that way, so it looks like it would fit OK. The fans are 80MM @ 72CFM's total, which is much better than mine at what, 20? If that?

Bruce Hill · 03-24-2006, 12:08 PM

Another cooling thing that some guys overlook, but I doubt you have.
Still ... make sure you have a front case fan pushing in, and a rear
case fan pushing out. I use the 120mm rear fans. They'll fit on most
of the smaller cases even. A good PS with a fan on the bottom and one
on the rear pulls air from the CPU out of the case, also.

jaykup · 03-24-2006, 12:20 PM

Yeah, I've got an X-Connect PSU with dual 80MM fans, and another 80MM fan in the back pushing air out. It has holes for a 120MM fan as well. I have a fan at the top also blowing out, and the case fan on the side blowing in, sadly enough the excellent design of my case doesn't allow for a fan in the front at all, unless i mounted one in the CDROM slot or something.