All of lore.kernel.org
 help / color / mirror / Atom feed
From: support-squid@bfinance.fr (jonathan)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] wrong temperature values
Date: Wed, 10 Aug 2005 18:24:46 +0000	[thread overview]
Message-ID: <1123690987.4125.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1123669211.4125.7.camel@localhost.localdomain>

Is it normal that i2c-sensor module is used by anything ?

I have tried to recompile my kernel 2.6.10 selecting I2C option as
modules (i2c-core, i2c-dev) but the result it's the same...



# lsmod
Module                  Size  Used by
i2c_sensor              7680  0 
i2c_ipmi                8716  0 
bmcsensors             79012  0 
i2c_dev                14208  0 
i2c_piix4              12944  0 
ipmi_si                37884  1 
ipmi_poweroff          11164  0 
ipmi_devintf           11652  0 
ipmi_msghandler        49376  4
i2c_ipmi,ipmi_si,ipmi_poweroff,ipmi_devintf
i2c_isa                 6144  0 
i2c_core               26752  6
i2c_sensor,i2c_ipmi,bmcsensors,i2c_dev,i2c_piix4,i2c_isa


any idea ? I really need some help, please ;-)

jonathan


On Wed, 2005-08-10 at 12:20 +0200, jonathan wrote:
> hi ,
> I have installed lm-sensors with i2c, ipmi and bmcsensors modules but
> the sensors command give me wrong values :
> 
> # sensors -s     --> no output ?
> # sensors
> bmc-i2c-1-00
> Adapter: IPMI adapter
> in1:       +1.48 V  (min =  +1.56 V, max =  +1.73 V)   
> in2:       +1.90 V  (min =  +1.56 V, max =  +1.73 V)   
> in3:       +1.90 V  (min =  +1.56 V, max =  +1.73 V)   
> in4:       +1.48 V  (min =  +1.56 V, max =  +1.73 V)   
> in5:       +1.90 V  (min =  +4.79 V, max =  +5.21 V)   
> in6:       +5.08 V  (min = +11.39 V, max = +12.61 V)   
> in7:      +11.90 V  (min =  +3.16 V, max =  +3.44 V)   
> in8:       +3.27 V  (min =  +2.49 V, max =  +3.28 V)   
> in9:       +3.12 V  (min =  +2.42 V, max =  +2.58 V)   
> in10:      +2.55 V  (min =  +2.42 V, max =  +2.58 V)   
> fan1:     6240 RPM  (min = 1080 RPM)                  
> fan2:     6360 RPM  (min = 1080 RPM)                  
> fan3:     6240 RPM  (min = 1080 RPM)                  
> fan4:     6720 RPM  (min = 1080 RPM)                  
> fan5:     6360 RPM  (min = 1080 RPM)                  
> fan6:     6240 RPM  (min = 1080 RPM)                  
> fan7:     6480 RPM  (min = 1080 RPM)                  
> temp1:    -128.0 C  (high =   +80 C, hyst =  -127 C)   
> temp2:    -930.0 C  (high =   +80 C, hyst =  -127 C)   
> temp3:    -1280.0 C  (high =   +80 C, hyst =  -127 C)   
> temp4:    -930.0 C  (high =   +80 C, hyst =  -127 C)   
> temp5:    +320.0 C  (high =   +55 C, hyst =  -127 C)   
> temp6:    +190.0 C  (high =   +40 C, hyst =  -127 C)   
> temp7:    -750.0 C  (high =   +55 C, hyst =  -127 C)   
> temp8:    -760.0 C  (high =   +55 C, hyst =  -127 C)   
> temp9:    -750.0 C  (high =   +55 C, hyst =  -127 C)   
> temp10:   +270.0 C  (high =   +55 C, hyst =  -127 C)   
> 
> 
> My loaded modules : (somes i2c are included in kernel 2.6.10)
> 
> # lsmod
> Module                  Size  Used by
> bmcsensors             79012  0 
> i2c_sensor              8448  0 
> i2c_piix4              14096  0 
> i2c_ipmi                8716  0 
> ipmi_si                37884  1 
> ipmi_poweroff          11164  0 
> ipmi_devintf           11652  0 
> ipmi_msghandler        49376  4
> i2c_ipmi,ipmi_si,ipmi_poweroff,ipmi_devintf
> i2c_isa                 6144  0
> 
> my sensors-detect output :# 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-piix4' for device 00:0f.0: ServerWorks CSB5 South Bridge
> Probe succesfully concluded.
> 
> We will now try to load each adapter module in turn.
> Module `i2c-piix4' 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): 
> FATAL: Module i2c_dev not found.
>  Loading failed, expect problems later on.
> 
>  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: IPMI adapter
> Do you want to scan it? (YES/no/selectively): 
> 
> 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... Failed!
> Probing for `IPMI BMC KCS'
>   Trying address 0x0ca0... Success!
>     (confidence 4, driver `bmcsensors')
> 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! (0xee11)
> Probing for `ITE 8705F Super IO Sensors'
>   Failed! (0xee11)
> Probing for `ITE 8712F Super IO Sensors'
>   Failed! (0xee11)
> Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87591 Super IO'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC87371 Super IO'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC97371 Super IO'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC8739x Super IO'
>   Failed! (0xee)
> Probing for `Nat. Semi. PC8741x Super IO'
>  Success... (no hardware monitoring capabilities)
> Probing for `SMSC 47B27x Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `SMSC 47M14x Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `SMSC 47S42x Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `SMSC 47S45x Super IO Fan Sensors'
>   Failed! (0xee)
> Probing for `SMSC 47M172 Super IO'
>   Failed! (0xee)
> Probing for `SMSC LPC47B397-NC Super IO'
>   Failed! (0xee)
> Probing for `VT1211 Super IO Sensors'
>   Failed! (0xee)
> Probing for `Winbond W83627HF Super IO Sensors'
>   Failed! (0xee)
> Probing for `Winbond W83627THF Super IO Sensors'
>   Failed! (0xee)
> Probing for `Winbond W83637HF Super IO Sensors'
>   Failed! (0xee)
> Probing for `Winbond W83697HF Super IO Sensors'
>   Failed! (0xee)
> Probing for `Winbond W83697SF/UF Super IO PWM'
>   Failed! (0xee)
> Probing for `Winbond W83L517D Super IO'
>   Failed! (0xee)
> Probing for `Winbond W83627EHF Super IO Sensors'
>   Failed! (0xee11)
> 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 `bmcsensors' (should be inserted):
>   Detects correctly:
>   * ISA bus address 0x0ca0 (Busdriver `i2c-isa')
>     Chip `IPMI BMC KCS' (confidence: 4)
> 
> 
>  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-isa
> # You must also install and load the IPMI modules
> i2c-ipmi
> # I2C chip drivers
> bmcsensors
> #----cut here----
> 
> 
> well, I don't understand anything about theses sensors output values. Is
> ther a problem with the chip module ?
> what can I try to resolve it ?
> 
> thanks
> 
> 
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


  reply	other threads:[~2005-08-10 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 12:22 [lm-sensors] wrong temperature values jonathan
2005-08-10 18:24 ` jonathan [this message]
2005-08-10 19:25 ` Yani Ioannou
2005-08-11  9:24 ` jonathan
2005-08-13  7:17 ` Yani Ioannou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1123690987.4125.12.camel@localhost.localdomain \
    --to=support-squid@bfinance.fr \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.