All of lore.kernel.org
 help / color / mirror / Atom feed
* [lm-sensors] lmsensors doesn't detect core-i7 sensors
@ 2010-09-01  6:38 Mahmood Naderan
  2010-09-01  7:19 ` Nikola Pajkovsky
                   ` (24 more replies)
  0 siblings, 25 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-01  6:38 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 5491 bytes --]

Dear all,
I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them. 
Here is the output of sensors-detect:

mahmood@localhost:~$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Gigabyte Technology Co., Ltd. P55-USB3
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 IT8720F Super IO Sensors'                        Success!
    (address 0x290, 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
Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
  * ISA bus, address 0x290
    Chip `ITE IT8720F 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)yes
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

Then I ran sensors:

mahmood@localhost:~$sudo sensors
it8720-isa-0290
Adapter: ISA adapter
in0:         +0.86 V  (min =  +0.00 V, max =  +4.08 V)
in1:         +1.58 V  (min =  +0.00 V, max =  +4.08 V)
in2:         +3.39 V  (min =  +0.00 V, max =  +4.08 V)
in3:         +3.02 V  (min =  +0.00 V, max =  +4.08 V)
in4:         +0.05 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in5:         +3.12 V  (min =  +0.00 V, max =  +4.08 V)
in6:         +0.02 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in7:         +2.16 V  (min =  +0.00 V, max =  +4.08 V)
Vbat:        +3.10 V
fan1:       1679 RPM  (min =   10 RPM)
fan2:        644 RPM  (min =    0 RPM)
fan3:       1278 RPM  (min =   10 RPM)
fan4:       1205 RPM  (min =    0 RPM)
temp1:       +36.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:       +25.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:       +33.0°C  (low  = +127.0°C, high = +90.0°C)  sensor = thermistor
cpu0_vid:   +0.313 V

What can I do then? currently I have kubuntu 10.04
 
// Naderan *Mahmood;


      

[-- Attachment #1.2: Type: text/html, Size: 11440 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
@ 2010-09-01  7:19 ` Nikola Pajkovsky
  2010-09-01  7:30 ` Mahmood Naderan
                   ` (23 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Nikola Pajkovsky @ 2010-09-01  7:19 UTC (permalink / raw)
  To: lm-sensors

On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
> Dear all,
>
> I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them. Here is the output of sensors-detect:
>
>
> mahmood@localhost:~$ sudo sensors-detect
> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> # System: Gigabyte Technology Co., Ltd. P55-USB3
>
> 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 IT8720F Super IO Sensors' Success!
> (address 0x290, 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
> Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> Sorry, no supported PCI bus adapters found.
> Module i2c-dev loaded successfully.
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `it87':
> * ISA bus, address 0x290
> Chip `ITE IT8720F 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)yes
> 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
>
>
> Then I ran sensors:
>
> mahmood@localhost:~$ sudo sensors
> it8720-isa-0290
> Adapter: ISA adapter
> in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> Vbat: +3.10 V
> fan1: 1679 RPM (min = 10 RPM)
> fan2: 644 RPM (min = 0 RPM)
> fan3: 1278 RPM (min = 10 RPM)
> fan4: 1205 RPM (min = 0 RPM)
> temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> cpu0_vid: +0.313 V
>
>
> What can I do then? currently I have kubuntu 10.04
>
> *// Naderan *Mahmood;*
>
>

Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and maintainer(if he is nice) update lm-sensors.

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
  2010-09-01  7:19 ` Nikola Pajkovsky
@ 2010-09-01  7:30 ` Mahmood Naderan
  2010-09-01  7:38 ` Nikola Pajkovsky
                   ` (22 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-01  7:30 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 5918 bytes --]

Here is what I did:
mahmood@localhost:~$ svn checkout http://lm-sensors.org/svn/lm-sensors/trunk 
lm-sensors
...
Checked out revision 5857.
 
mahmood@localhost:~$ svn update http://lm-sensors.org/svn/lm-sensors/trunk 
lm-sensors
Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
At revision 5857.
Summary of conflicts:
  Skipped paths: 1

Is that what you meant?
// Naderan *Mahmood;




________________________________
From: Nikola Pajkovsky <npajkovs@redhat.com>
To: lm-sensors@lm-sensors.org
Sent: Wed, September 1, 2010 11:49:03 AM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
> Dear all,
>
> I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them. 
>Here is the output of sensors-detect:
>
>
> mahmood@localhost:~$ sudo sensors-detect
> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> # System: Gigabyte Technology Co., Ltd. P55-USB3
>
> 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 IT8720F Super IO Sensors' Success!
> (address 0x290, 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
> Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> Sorry, no supported PCI bus adapters found.
> Module i2c-dev loaded successfully.
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `it87':
> * ISA bus, address 0x290
> Chip `ITE IT8720F 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)yes
> 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
>
>
> Then I ran sensors:
>
> mahmood@localhost:~$ sudo sensors
> it8720-isa-0290
> Adapter: ISA adapter
> in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> Vbat: +3.10 V
> fan1: 1679 RPM (min = 10 RPM)
> fan2: 644 RPM (min = 0 RPM)
> fan3: 1278 RPM (min = 10 RPM)
> fan4: 1205 RPM (min = 0 RPM)
> temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> cpu0_vid: +0.313 V
>
>
> What can I do then? currently I have kubuntu 10.04
>
> *// Naderan *Mahmood;*
>
>

Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and 
maintainer(if he is nice) update lm-sensors.

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



      

[-- Attachment #1.2: Type: text/html, Size: 7820 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
  2010-09-01  7:19 ` Nikola Pajkovsky
  2010-09-01  7:30 ` Mahmood Naderan
@ 2010-09-01  7:38 ` Nikola Pajkovsky
  2010-09-01  7:46 ` Mahmood Naderan
                   ` (21 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Nikola Pajkovsky @ 2010-09-01  7:38 UTC (permalink / raw)
  To: lm-sensors

On 09/01/2010 09:30 AM, Mahmood Naderan wrote:
> Here is what I did:
> mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn checkout http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
> ...
> Checked out revision 5857.
Yes

> mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> svn update http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
> Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
> At revision 5857.
> Summary of conflicts:
> Skipped paths: 1
> Is that what you meant?
> *// Naderan *Mahmood;*
just svn update # not needed if you have fresh checkout

in lm-sensors/prog/detect run sensors-detect and it should find your core-i7

>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--
> *From:* Nikola Pajkovsky <npajkovs@redhat.com>
> *To:* lm-sensors@lm-sensors.org
> *Sent:* Wed, September 1, 2010 11:49:03 AM
> *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
>  > Dear all,
>  >
>  > I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them. Here is the output of sensors-detect:
>  >
>  >
>  > mahmood@localhost:~$ sudo sensors-detect
>  > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  >
>  > 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 IT8720F Super IO Sensors' Success!
>  > (address 0x290, 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
>  > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > Sorry, no supported PCI bus adapters found.
>  > Module i2c-dev loaded successfully.
>  >
>  > Now follows a summary of the probes I have just done.
>  > Just press ENTER to continue:
>  >
>  > Driver `it87':
>  > * ISA bus, address 0x290
>  > Chip `ITE IT8720F 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)yes
>  > 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
>  >
>  >
>  > Then I ran sensors:
>  >
>  > mahmood@localhost:~$ sudo sensors
>  > it8720-isa-0290
>  > Adapter: ISA adapter
>  > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > Vbat: +3.10 V
>  > fan1: 1679 RPM (min = 10 RPM)
>  > fan2: 644 RPM (min = 0 RPM)
>  > fan3: 1278 RPM (min = 10 RPM)
>  > fan4: 1205 RPM (min = 0 RPM)
>  > temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > cpu0_vid: +0.313 V
>  >
>  >
>  > What can I do then? currently I have kubuntu 10.04
>  >
>  > *// Naderan *Mahmood;*
>  >
>  >
>
> Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and maintainer(if he is nice) update lm-sensors.
>

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (2 preceding siblings ...)
  2010-09-01  7:38 ` Nikola Pajkovsky
@ 2010-09-01  7:46 ` Mahmood Naderan
  2010-09-01  7:53 ` Nikola Pajkovsky
                   ` (20 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-01  7:46 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 13385 bytes --]

>just svn update # not needed if you have fresh checkout
To double check and be sure again:

mahmood@localhost:~$svn update 5857
Skipped '5857'
 
Then:mahmood@localhost:~$cd lm-sensors/prog/detect/
mahmood@localhost:~/lm-sensors/prog/detect$sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Gigabyte Technology Co., Ltd. P55-USB3

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 IT8720F Super IO Sensors'                        Success!
    (address 0x290, 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
Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
  * ISA bus, address 0x290
    Chip `ITE IT8720F 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)yes
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
 
But that didn't help. See the sensors output:
 
mahmood@localhost:~/lm-sensors/prog/detect$sudo sensors
it8720-isa-0290
Adapter: ISA adapter
in0:         +0.86 V  (min =  +0.00 V, max =  +4.08 V)
in1:         +1.58 V  (min =  +0.00 V, max =  +4.08 V)
in2:         +3.39 V  (min =  +0.00 V, max =  +4.08 V)
in3:         +3.02 V  (min =  +0.00 V, max =  +4.08 V)
in4:         +0.05 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in5:         +3.12 V  (min =  +0.00 V, max =  +4.08 V)
in6:         +0.02 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in7:         +2.16 V  (min =  +0.00 V, max =  +4.08 V)
Vbat:        +3.10 V
fan1:       1683 RPM  (min =   10 RPM)
fan2:        644 RPM  (min =    0 RPM)
fan3:       1280 RPM  (min =   10 RPM)
fan4:       1203 RPM  (min =    0 RPM)
temp1:       +35.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:       +25.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:       +33.0°C  (low  = +127.0°C, high = +90.0°C)  sensor = thermistor
cpu0_vid:   +0.313 V

Any idea? Thanks,


// Naderan *Mahmood;




________________________________
From: Nikola Pajkovsky <npajkovs@redhat.com>
To: lm-sensors@lm-sensors.org
Sent: Wed, September 1, 2010 12:08:07 PM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

On 09/01/2010 09:30 AM, Mahmood Naderan wrote:
> Here is what I did:
> mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn checkout 
>http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
> ...
> Checked out revision 5857.
Yes

> mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> svn update 
>http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
> Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
> At revision 5857.
> Summary of conflicts:
> Skipped paths: 1
> Is that what you meant?
> *// Naderan *Mahmood;*
just svn update # not needed if you have fresh checkout

in lm-sensors/prog/detect run sensors-detect and it should find your core-i7

>
>
>------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------
>-
--
> *From:* Nikola Pajkovsky <npajkovs@redhat.com>
> *To:* lm-sensors@lm-sensors.org
> *Sent:* Wed, September 1, 2010 11:49:03 AM
> *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
>  > Dear all,
>  >
>  > I ran sensors-detect to detect Core-i7 temperatures but it doesn't show 
>them. Here is the output of sensors-detect:
>  >
>  >
>  > mahmood@localhost:~$ sudo sensors-detect
>  > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  >
>  > 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 IT8720F Super IO Sensors' Success!
>  > (address 0x290, 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
>  > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > Sorry, no supported PCI bus adapters found.
>  > Module i2c-dev loaded successfully.
>  >
>  > Now follows a summary of the probes I have just done.
>  > Just press ENTER to continue:
>  >
>  > Driver `it87':
>  > * ISA bus, address 0x290
>  > Chip `ITE IT8720F 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)yes
>  > 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
>  >
>  >
>  > Then I ran sensors:
>  >
>  > mahmood@localhost:~$ sudo sensors
>  > it8720-isa-0290
>  > Adapter: ISA adapter
>  > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > Vbat: +3.10 V
>  > fan1: 1679 RPM (min = 10 RPM)
>  > fan2: 644 RPM (min = 0 RPM)
>  > fan3: 1278 RPM (min = 10 RPM)
>  > fan4: 1205 RPM (min = 0 RPM)
>  > temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > cpu0_vid: +0.313 V
>  >
>  >
>  > What can I do then? currently I have kubuntu 10.04
>  >
>  > *// Naderan *Mahmood;*
>  >
>  >
>
> Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and 
>maintainer(if he is nice) update lm-sensors.
>

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



      

[-- Attachment #1.2: Type: text/html, Size: 22715 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (3 preceding siblings ...)
  2010-09-01  7:46 ` Mahmood Naderan
@ 2010-09-01  7:53 ` Nikola Pajkovsky
  2010-09-01  8:03 ` Mahmood Naderan
                   ` (19 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Nikola Pajkovsky @ 2010-09-01  7:53 UTC (permalink / raw)
  To: lm-sensors

sudo ./sensors-detect

On 09/01/2010 09:46 AM, Mahmood Naderan wrote:
>  >just svn update # not needed if you have fresh checkout
> To double check and be sure again:
> mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn update 5857
> Skipped '5857'
>
> Then:
>
>
> mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> cd lm-sensors/prog/detect/
> mahmood@localhost:~/lm-sensors/prog/detect$ <mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors-detect
> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> # System: Gigabyte Technology Co., Ltd. P55-USB3
> 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 IT8720F Super IO Sensors' Success!
> (address 0x290, 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
> Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> Sorry, no supported PCI bus adapters found.
> Module i2c-dev loaded successfully.
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
> Driver `it87':
> * ISA bus, address 0x290
> Chip `ITE IT8720F 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)yes
> 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
>
> But that didn't help. See the sensors output:
>
> mahmood@localhost:~/lm-sensors/prog/detect$ <mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors
> it8720-isa-0290
> Adapter: ISA adapter
> in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> Vbat: +3.10 V
> fan1: 1683 RPM (min = 10 RPM)
> fan2: 644 RPM (min = 0 RPM)
> fan3: 1280 RPM (min = 10 RPM)
> fan4: 1203 RPM (min = 0 RPM)
> temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> cpu0_vid: +0.313 V
>
> Any idea? Thanks,
> *// Naderan *Mahmood;*
>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--
> *From:* Nikola Pajkovsky <npajkovs@redhat.com>
> *To:* lm-sensors@lm-sensors.org
> *Sent:* Wed, September 1, 2010 12:08:07 PM
> *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> On 09/01/2010 09:30 AM, Mahmood Naderan wrote:
>  > Here is what I did:
>  > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn checkout http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > ...
>  > Checked out revision 5857.
> Yes
>
>  > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> svn update http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
>  > At revision 5857.
>  > Summary of conflicts:
>  > Skipped paths: 1
>  > Is that what you meant?
>  > *// Naderan *Mahmood;*
> just svn update # not needed if you have fresh checkout
>
> in lm-sensors/prog/detect run sensors-detect and it should find your core-i7
>
>  >
>  >
>  > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ------------------
----
> --
>  > *From:* Nikola Pajkovsky <npajkovs@redhat.com <mailto:npajkovs@redhat.com>>
>  > *To:* lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>
>  > *Sent:* Wed, September 1, 2010 11:49:03 AM
>  > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>  >
>  > On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
>  > > Dear all,
>  > >
>  > > I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them. Here is the output of sensors-detect:
>  > >
>  > >
>  > > mahmood@localhost:~$ sudo sensors-detect
>  > > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  > >
>  > > 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 IT8720F Super IO Sensors' Success!
>  > > (address 0x290, 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
>  > > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > > Sorry, no supported PCI bus adapters found.
>  > > Module i2c-dev loaded successfully.
>  > >
>  > > Now follows a summary of the probes I have just done.
>  > > Just press ENTER to continue:
>  > >
>  > > Driver `it87':
>  > > * ISA bus, address 0x290
>  > > Chip `ITE IT8720F 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)yes
>  > > 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
>  > >
>  > >
>  > > Then I ran sensors:
>  > >
>  > > mahmood@localhost:~$ sudo sensors
>  > > it8720-isa-0290
>  > > Adapter: ISA adapter
>  > > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > > Vbat: +3.10 V
>  > > fan1: 1679 RPM (min = 10 RPM)
>  > > fan2: 644 RPM (min = 0 RPM)
>  > > fan3: 1278 RPM (min = 10 RPM)
>  > > fan4: 1205 RPM (min = 0 RPM)
>  > > temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > > cpu0_vid: +0.313 V
>  > >
>  > >
>  > > What can I do then? currently I have kubuntu 10.04
>  > >
>  > > *// Naderan *Mahmood;*
>  > >
>  > >
>  >
>  > Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and maintainer(if he is nice) update lm-sensors.
>  >
>


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (4 preceding siblings ...)
  2010-09-01  7:53 ` Nikola Pajkovsky
@ 2010-09-01  8:03 ` Mahmood Naderan
  2010-09-01  8:11 ` Nikola Pajkovsky
                   ` (18 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-01  8:03 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 16464 bytes --]

>sudo ./sensors-detect
Yes
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
...
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
  * ISA bus, address 0x290
    Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
Driver `coretemp':
  * Chip `Intel Core family thermal sensor' (confidence: 9)
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): y
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.

I then copy that file and restart
mahmood@localhost:~$ls /etc/init.d/lm*
/etc/init.d/lm-sensors

However this is what I see again
mahmood@localhost:~$sudo sensors
it8720-isa-0290
Adapter: ISA adapter
in0:         +0.86 V  (min =  +0.00 V, max =  +4.08 V)
in1:         +1.58 V  (min =  +0.00 V, max =  +4.08 V)
in2:         +3.39 V  (min =  +0.00 V, max =  +4.08 V)
in3:         +3.02 V  (min =  +0.00 V, max =  +4.08 V)
in4:         +0.05 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in5:         +3.12 V  (min =  +0.00 V, max =  +4.08 V)
in6:         +0.02 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in7:         +2.16 V  (min =  +0.00 V, max =  +4.08 V)
Vbat:        +3.10 V
fan1:       1638 RPM  (min =   10 RPM)
fan2:        618 RPM  (min =    0 RPM)
fan3:       1278 RPM  (min =   10 RPM)
fan4:       1203 RPM  (min =    0 RPM)
temp1:       +35.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:       +25.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:       +33.0°C  (low  = +127.0°C, high = +90.0°C)  sensor = thermistor
cpu0_vid:   +0.313 V

No core-i7.... :(
// Naderan *Mahmood;




________________________________
From: Nikola Pajkovsky <npajkovs@redhat.com>
To: lm-sensors@lm-sensors.org
Sent: Wed, September 1, 2010 12:23:10 PM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

sudo ./sensors-detect

On 09/01/2010 09:46 AM, Mahmood Naderan wrote:
>  >just svn update # not needed if you have fresh checkout
> To double check and be sure again:
> mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn update 5857
> Skipped '5857'
>
> Then:
>
>
> mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> cd lm-sensors/prog/detect/
> mahmood@localhost:~/lm-sensors/prog/detect$ 
><mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors-detect
> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> # System: Gigabyte Technology Co., Ltd. P55-USB3
> 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 IT8720F Super IO Sensors' Success!
> (address 0x290, 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
> Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> Sorry, no supported PCI bus adapters found.
> Module i2c-dev loaded successfully.
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
> Driver `it87':
> * ISA bus, address 0x290
> Chip `ITE IT8720F 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)yes
> 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
>
> But that didn't help. See the sensors output:
>
> mahmood@localhost:~/lm-sensors/prog/detect$ 
><mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors
> it8720-isa-0290
> Adapter: ISA adapter
> in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> Vbat: +3.10 V
> fan1: 1683 RPM (min = 10 RPM)
> fan2: 644 RPM (min = 0 RPM)
> fan3: 1280 RPM (min = 10 RPM)
> fan4: 1203 RPM (min = 0 RPM)
> temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> cpu0_vid: +0.313 V
>
> Any idea? Thanks,
> *// Naderan *Mahmood;*
>
>
>------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------
>-
--
> *From:* Nikola Pajkovsky <npajkovs@redhat.com>
> *To:* lm-sensors@lm-sensors.org
> *Sent:* Wed, September 1, 2010 12:08:07 PM
> *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> On 09/01/2010 09:30 AM, Mahmood Naderan wrote:
>  > Here is what I did:
>  > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn checkout 
>http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > ...
>  > Checked out revision 5857.
> Yes
>
>  > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> svn update 
>http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
>  > At revision 5857.
>  > Summary of conflicts:
>  > Skipped paths: 1
>  > Is that what you meant?
>  > *// Naderan *Mahmood;*
> just svn update # not needed if you have fresh checkout
>
> in lm-sensors/prog/detect run sensors-detect and it should find your core-i7
>
>  >
>  >
>  > 
>------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ------------------
----
> --
>  > *From:* Nikola Pajkovsky <npajkovs@redhat.com <mailto:npajkovs@redhat.com>>
>  > *To:* lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>
>  > *Sent:* Wed, September 1, 2010 11:49:03 AM
>  > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>  >
>  > On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
>  > > Dear all,
>  > >
>  > > I ran sensors-detect to detect Core-i7 temperatures but it doesn't show 
>them. Here is the output of sensors-detect:
>  > >
>  > >
>  > > mahmood@localhost:~$ sudo sensors-detect
>  > > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  > >
>  > > 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 IT8720F Super IO Sensors' Success!
>  > > (address 0x290, 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
>  > > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > > Sorry, no supported PCI bus adapters found.
>  > > Module i2c-dev loaded successfully.
>  > >
>  > > Now follows a summary of the probes I have just done.
>  > > Just press ENTER to continue:
>  > >
>  > > Driver `it87':
>  > > * ISA bus, address 0x290
>  > > Chip `ITE IT8720F 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)yes
>  > > 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
>  > >
>  > >
>  > > Then I ran sensors:
>  > >
>  > > mahmood@localhost:~$ sudo sensors
>  > > it8720-isa-0290
>  > > Adapter: ISA adapter
>  > > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > > Vbat: +3.10 V
>  > > fan1: 1679 RPM (min = 10 RPM)
>  > > fan2: 644 RPM (min = 0 RPM)
>  > > fan3: 1278 RPM (min = 10 RPM)
>  > > fan4: 1205 RPM (min = 0 RPM)
>  > > temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > > cpu0_vid: +0.313 V
>  > >
>  > >
>  > > What can I do then? currently I have kubuntu 10.04
>  > >
>  > > *// Naderan *Mahmood;*
>  > >
>  > >
>  >
>  > Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and 
>maintainer(if he is nice) update lm-sensors.
>  >
>


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



      

[-- Attachment #1.2: Type: text/html, Size: 22974 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (5 preceding siblings ...)
  2010-09-01  8:03 ` Mahmood Naderan
@ 2010-09-01  8:11 ` Nikola Pajkovsky
  2010-09-01  8:16 ` Mahmood Naderan
                   ` (17 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Nikola Pajkovsky @ 2010-09-01  8:11 UTC (permalink / raw)
  To: lm-sensors

On 09/01/2010 10:03 AM, Mahmood Naderan wrote:
>  >sudo ./sensors-detect
> Yes
> Intel Core family thermal sensor... Success!
> (driver `coretemp')
> ...
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
> Driver `it87':
> * ISA bus, address 0x290
> Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
> Driver `coretemp':
> * Chip `Intel Core family thermal sensor' (confidence: 9)
> Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): y
> 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.
> I then copy that file and restart
> mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> ls /etc/init.d/lm*
> /etc/init.d/lm-sensors
> However this is what I see again
> mahmood@localhost:~$ <mailto:mahmood@localhost:~$> sudo sensors
> it8720-isa-0290
> Adapter: ISA adapter
> in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> Vbat: +3.10 V
> fan1: 1638 RPM (min = 10 RPM)
> fan2: 618 RPM (min = 0 RPM)
> fan3: 1278 RPM (min = 10 RPM)
> fan4: 1203 RPM (min = 0 RPM)
> temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> cpu0_vid: +0.313 V
> No core-i7.... :(
> *// Naderan *Mahmood;*
>
sudo /etc/init.d/lm_sensors restart


>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--
> *From:* Nikola Pajkovsky <npajkovs@redhat.com>
> *To:* lm-sensors@lm-sensors.org
> *Sent:* Wed, September 1, 2010 12:23:10 PM
> *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> sudo ./sensors-detect
>
> On 09/01/2010 09:46 AM, Mahmood Naderan wrote:
>  > >just svn update # not needed if you have fresh checkout
>  > To double check and be sure again:
>  > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn update 5857
>  > Skipped '5857'
>  >
>  > Then:
>  >
>  >
>  > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> cd lm-sensors/prog/detect/
>  > mahmood@localhost:~/lm-sensors/prog/detect$ <mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors-detect
>  > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  > 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 IT8720F Super IO Sensors' Success!
>  > (address 0x290, 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
>  > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > Sorry, no supported PCI bus adapters found.
>  > Module i2c-dev loaded successfully.
>  > Now follows a summary of the probes I have just done.
>  > Just press ENTER to continue:
>  > Driver `it87':
>  > * ISA bus, address 0x290
>  > Chip `ITE IT8720F 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)yes
>  > 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
>  >
>  > But that didn't help. See the sensors output:
>  >
>  > mahmood@localhost:~/lm-sensors/prog/detect$ <mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors
>  > it8720-isa-0290
>  > Adapter: ISA adapter
>  > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > Vbat: +3.10 V
>  > fan1: 1683 RPM (min = 10 RPM)
>  > fan2: 644 RPM (min = 0 RPM)
>  > fan3: 1280 RPM (min = 10 RPM)
>  > fan4: 1203 RPM (min = 0 RPM)
>  > temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > cpu0_vid: +0.313 V
>  >
>  > Any idea? Thanks,
>  > *// Naderan *Mahmood;*
>  >
>  >
>  > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ------------------
----
> --
>  > *From:* Nikola Pajkovsky <npajkovs@redhat.com <mailto:npajkovs@redhat.com>>
>  > *To:* lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>
>  > *Sent:* Wed, September 1, 2010 12:08:07 PM
>  > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>  >
>  > On 09/01/2010 09:30 AM, Mahmood Naderan wrote:
>  > > Here is what I did:
>  > > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn checkout http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > > ...
>  > > Checked out revision 5857.
>  > Yes
>  >
>  > > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> svn update http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > > Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
>  > > At revision 5857.
>  > > Summary of conflicts:
>  > > Skipped paths: 1
>  > > Is that what you meant?
>  > > *// Naderan *Mahmood;*
>  > just svn update # not needed if you have fresh checkout
>  >
>  > in lm-sensors/prog/detect run sensors-detect and it should find your core-i7
>  >
>  > >
>  > >
>  > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ----------------
--
> ----
>  > --
>  > > *From:* Nikola Pajkovsky <npajkovs@redhat.com <mailto:npajkovs@redhat.com> <mailto:npajkovs@redhat.com <mailto:npajkovs@redhat.com>>>
>  > > *To:* lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org> <mailto:lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>>
>  > > *Sent:* Wed, September 1, 2010 11:49:03 AM
>  > > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>  > >
>  > > On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
>  > > > Dear all,
>  > > >
>  > > > I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them. Here is the output of sensors-detect:
>  > > >
>  > > >
>  > > > mahmood@localhost:~$ sudo sensors-detect
>  > > > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > > > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  > > >
>  > > > 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 IT8720F Super IO Sensors' Success!
>  > > > (address 0x290, 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
>  > > > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > > > Sorry, no supported PCI bus adapters found.
>  > > > Module i2c-dev loaded successfully.
>  > > >
>  > > > Now follows a summary of the probes I have just done.
>  > > > Just press ENTER to continue:
>  > > >
>  > > > Driver `it87':
>  > > > * ISA bus, address 0x290
>  > > > Chip `ITE IT8720F 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)yes
>  > > > 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
>  > > >
>  > > >
>  > > > Then I ran sensors:
>  > > >
>  > > > mahmood@localhost:~$ sudo sensors
>  > > > it8720-isa-0290
>  > > > Adapter: ISA adapter
>  > > > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > > > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > > > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > > > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > > > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > > > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > > > Vbat: +3.10 V
>  > > > fan1: 1679 RPM (min = 10 RPM)
>  > > > fan2: 644 RPM (min = 0 RPM)
>  > > > fan3: 1278 RPM (min = 10 RPM)
>  > > > fan4: 1205 RPM (min = 0 RPM)
>  > > > temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > > > cpu0_vid: +0.313 V
>  > > >
>  > > >
>  > > > What can I do then? currently I have kubuntu 10.04
>  > > >
>  > > > *// Naderan *Mahmood;*
>  > > >
>  > > >
>  > >
>  > > Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and maintainer(if he is nice) update lm-sensors.
>  > >
>  >
>


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (6 preceding siblings ...)
  2010-09-01  8:11 ` Nikola Pajkovsky
@ 2010-09-01  8:16 ` Mahmood Naderan
  2010-09-01 13:26 ` Guenter Roeck
                   ` (16 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-01  8:16 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 18837 bytes --]

>sudo /etc/init.d/lm_sensors restart
 
mahmood@localhost:~$ sudo /etc/init.d/lm-sensors restart
.: 39: Can't open /etc/init.d/functions

Note there is no lm_sensors. I have lm-sensors
 
// Naderan *Mahmood;




________________________________
From: Nikola Pajkovsky <npajkovs@redhat.com>
To: lm-sensors@lm-sensors.org
Sent: Wed, September 1, 2010 12:41:56 PM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

On 09/01/2010 10:03 AM, Mahmood Naderan wrote:
>  >sudo ./sensors-detect
> Yes
> Intel Core family thermal sensor... Success!
> (driver `coretemp')
> ...
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
> Driver `it87':
> * ISA bus, address 0x290
> Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
> Driver `coretemp':
> * Chip `Intel Core family thermal sensor' (confidence: 9)
> Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): y
> 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.
> I then copy that file and restart
> mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> ls /etc/init.d/lm*
> /etc/init.d/lm-sensors
> However this is what I see again
> mahmood@localhost:~$ <mailto:mahmood@localhost:~$> sudo sensors
> it8720-isa-0290
> Adapter: ISA adapter
> in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> Vbat: +3.10 V
> fan1: 1638 RPM (min = 10 RPM)
> fan2: 618 RPM (min = 0 RPM)
> fan3: 1278 RPM (min = 10 RPM)
> fan4: 1203 RPM (min = 0 RPM)
> temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> cpu0_vid: +0.313 V
> No core-i7.... :(
> *// Naderan *Mahmood;*
>
sudo /etc/init.d/lm_sensors restart


>
>------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------
>-
--
> *From:* Nikola Pajkovsky <npajkovs@redhat.com>
> *To:* lm-sensors@lm-sensors.org
> *Sent:* Wed, September 1, 2010 12:23:10 PM
> *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> sudo ./sensors-detect
>
> On 09/01/2010 09:46 AM, Mahmood Naderan wrote:
>  > >just svn update # not needed if you have fresh checkout
>  > To double check and be sure again:
>  > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn update 5857
>  > Skipped '5857'
>  >
>  > Then:
>  >
>  >
>  > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> cd 
>lm-sensors/prog/detect/
>  > mahmood@localhost:~/lm-sensors/prog/detect$ 
><mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors-detect
>  > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  > 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 IT8720F Super IO Sensors' Success!
>  > (address 0x290, 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
>  > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > Sorry, no supported PCI bus adapters found.
>  > Module i2c-dev loaded successfully.
>  > Now follows a summary of the probes I have just done.
>  > Just press ENTER to continue:
>  > Driver `it87':
>  > * ISA bus, address 0x290
>  > Chip `ITE IT8720F 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)yes
>  > 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
>  >
>  > But that didn't help. See the sensors output:
>  >
>  > mahmood@localhost:~/lm-sensors/prog/detect$ 
><mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors
>  > it8720-isa-0290
>  > Adapter: ISA adapter
>  > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > Vbat: +3.10 V
>  > fan1: 1683 RPM (min = 10 RPM)
>  > fan2: 644 RPM (min = 0 RPM)
>  > fan3: 1280 RPM (min = 10 RPM)
>  > fan4: 1203 RPM (min = 0 RPM)
>  > temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > cpu0_vid: +0.313 V
>  >
>  > Any idea? Thanks,
>  > *// Naderan *Mahmood;*
>  >
>  >
>  > 
>------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ------------------
----
> --
>  > *From:* Nikola Pajkovsky <npajkovs@redhat.com <mailto:npajkovs@redhat.com>>
>  > *To:* lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>
>  > *Sent:* Wed, September 1, 2010 12:08:07 PM
>  > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>  >
>  > On 09/01/2010 09:30 AM, Mahmood Naderan wrote:
>  > > Here is what I did:
>  > > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn checkout 
>http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > > ...
>  > > Checked out revision 5857.
>  > Yes
>  >
>  > > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> svn update 
>http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
>  > > Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
>  > > At revision 5857.
>  > > Summary of conflicts:
>  > > Skipped paths: 1
>  > > Is that what you meant?
>  > > *// Naderan *Mahmood;*
>  > just svn update # not needed if you have fresh checkout
>  >
>  > in lm-sensors/prog/detect run sensors-detect and it should find your 
core-i7
>  >
>  > >
>  > >
>  > > 
>------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ----------------
--
> ----
>  > --
>  > > *From:* Nikola Pajkovsky <npajkovs@redhat.com <mailto:npajkovs@redhat.com> 
><mailto:npajkovs@redhat.com <mailto:npajkovs@redhat.com>>>
>  > > *To:* lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org> 
><mailto:lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>>
>  > > *Sent:* Wed, September 1, 2010 11:49:03 AM
>  > > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>  > >
>  > > On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
>  > > > Dear all,
>  > > >
>  > > > I ran sensors-detect to detect Core-i7 temperatures but it doesn't show 
>them. Here is the output of sensors-detect:
>  > > >
>  > > >
>  > > > mahmood@localhost:~$ sudo sensors-detect
>  > > > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>  > > > # System: Gigabyte Technology Co., Ltd. P55-USB3
>  > > >
>  > > > 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 IT8720F Super IO Sensors' Success!
>  > > > (address 0x290, 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
>  > > > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
>  > > > Sorry, no supported PCI bus adapters found.
>  > > > Module i2c-dev loaded successfully.
>  > > >
>  > > > Now follows a summary of the probes I have just done.
>  > > > Just press ENTER to continue:
>  > > >
>  > > > Driver `it87':
>  > > > * ISA bus, address 0x290
>  > > > Chip `ITE IT8720F 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)yes
>  > > > 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
>  > > >
>  > > >
>  > > > Then I ran sensors:
>  > > >
>  > > > mahmood@localhost:~$ sudo sensors
>  > > > it8720-isa-0290
>  > > > Adapter: ISA adapter
>  > > > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
>  > > > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
>  > > > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
>  > > > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
>  > > > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
>  > > > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
>  > > > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
>  > > > Vbat: +3.10 V
>  > > > fan1: 1679 RPM (min = 10 RPM)
>  > > > fan2: 644 RPM (min = 0 RPM)
>  > > > fan3: 1278 RPM (min = 10 RPM)
>  > > > fan4: 1205 RPM (min = 0 RPM)
>  > > > temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
>  > > > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
>  > > > cpu0_vid: +0.313 V
>  > > >
>  > > >
>  > > > What can I do then? currently I have kubuntu 10.04
>  > > >
>  > > > *// Naderan *Mahmood;*
>  > > >
>  > > >
>  > >
>  > > Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and 
>maintainer(if he is nice) update lm-sensors.
>  > >
>  >
>


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



      

[-- Attachment #1.2: Type: text/html, Size: 26058 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (7 preceding siblings ...)
  2010-09-01  8:16 ` Mahmood Naderan
@ 2010-09-01 13:26 ` Guenter Roeck
  2010-09-01 13:56 ` Jean Delvare
                   ` (15 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-01 13:26 UTC (permalink / raw)
  To: lm-sensors

On Wed, Sep 01, 2010 at 04:16:41AM -0400, Mahmood Naderan wrote:
> >sudo /etc/init.d/lm_sensors restart
> 
> mahmood@localhost:~$<mailto:mahmood@localhost:~$> sudo /etc/init.d/lm-sensors restart
> .: 39: Can't open /etc/init.d/functions
> 
> Note there is no lm_sensors. I have lm-sensors
> 

I tried /etc/init.d/lm-sensors on a lucid (10.04) system and it works for me. It looks like
you overwrote the original version of /etc/init.d/lm-sensors with prog/init.d/lm_sensors.
That won't work - prog/init.d/lm_sensors does not work with lucid. You'll need to reinstall
the original version of /etc/init.d/lm-sensors and try again.

Guenter

> // Naderan *Mahmood;
> 
> 
> ________________________________
> From: Nikola Pajkovsky <npajkovs@redhat.com>
> To: lm-sensors@lm-sensors.org
> Sent: Wed, September 1, 2010 12:41:56 PM
> Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
> 
> On 09/01/2010 10:03 AM, Mahmood Naderan wrote:
> >  >sudo ./sensors-detect
> > Yes
> > Intel Core family thermal sensor... Success!
> > (driver `coretemp')
> > ...
> > Now follows a summary of the probes I have just done.
> > Just press ENTER to continue:
> > Driver `it87':
> > * ISA bus, address 0x290
> > Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
> > Driver `coretemp':
> > * Chip `Intel Core family thermal sensor' (confidence: 9)
> > Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): y
> > 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.
> > I then copy that file and restart
> > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> ls /etc/init.d/lm*
> > /etc/init.d/lm-sensors
> > However this is what I see again
> > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> sudo sensors
> > it8720-isa-0290
> > Adapter: ISA adapter
> > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> > Vbat: +3.10 V
> > fan1: 1638 RPM (min = 10 RPM)
> > fan2: 618 RPM (min = 0 RPM)
> > fan3: 1278 RPM (min = 10 RPM)
> > fan4: 1203 RPM (min = 0 RPM)
> > temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> > cpu0_vid: +0.313 V
> > No core-i7.... :(
> > *// Naderan *Mahmood;*
> >
> sudo /etc/init.d/lm_sensors restart
> 
> 
> >
> > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ----------------------
> --
> > *From:* Nikola Pajkovsky <npajkovs@redhat.com<mailto:npajkovs@redhat.com>>
> > *To:* lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org>
> > *Sent:* Wed, September 1, 2010 12:23:10 PM
> > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
> >
> > sudo ./sensors-detect
> >
> > On 09/01/2010 09:46 AM, Mahmood Naderan wrote:
> >  > >just svn update # not needed if you have fresh checkout
> >  > To double check and be sure again:
> >  > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn update 5857
> >  > Skipped '5857'
> >  >
> >  > Then:
> >  >
> >  >
> >  > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> cd lm-sensors/prog/detect/
> >  > mahmood@localhost:~/lm-sensors/prog/detect$ <mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors-detect
> >  > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> >  > # System: Gigabyte Technology Co., Ltd. P55-USB3
> >  > 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 IT8720F Super IO Sensors' Success!
> >  > (address 0x290, 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
> >  > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> >  > Sorry, no supported PCI bus adapters found.
> >  > Module i2c-dev loaded successfully.
> >  > Now follows a summary of the probes I have just done.
> >  > Just press ENTER to continue:
> >  > Driver `it87':
> >  > * ISA bus, address 0x290
> >  > Chip `ITE IT8720F 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)yes
> >  > 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
> >  >
> >  > But that didn't help. See the sensors output:
> >  >
> >  > mahmood@localhost:~/lm-sensors/prog/detect$ <mailto:mahmood@blackfish:~/lm-sensors/prog/detect$> sudo sensors
> >  > it8720-isa-0290
> >  > Adapter: ISA adapter
> >  > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> >  > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> >  > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> >  > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> >  > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> >  > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> >  > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> >  > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> >  > Vbat: +3.10 V
> >  > fan1: 1683 RPM (min = 10 RPM)
> >  > fan2: 644 RPM (min = 0 RPM)
> >  > fan3: 1280 RPM (min = 10 RPM)
> >  > fan4: 1203 RPM (min = 0 RPM)
> >  > temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> >  > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> >  > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> >  > cpu0_vid: +0.313 V
> >  >
> >  > Any idea? Thanks,
> >  > *// Naderan *Mahmood;*
> >  >
> >  >
> >  > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ------------------
> ----
> > --
> >  > *From:* Nikola Pajkovsky <npajkovs@redhat.com<mailto:npajkovs@redhat.com> <mailto:npajkovs@redhat.com<mailto:npajkovs@redhat.com>>>
> >  > *To:* lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org> <mailto:lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org>>
> >  > *Sent:* Wed, September 1, 2010 12:08:07 PM
> >  > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
> >  >
> >  > On 09/01/2010 09:30 AM, Mahmood Naderan wrote:
> >  > > Here is what I did:
> >  > > mahmood@localhost:~$ <mailto:mahmood@localhost:~$> svn checkout http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
> >  > > ...
> >  > > Checked out revision 5857.
> >  > Yes
> >  >
> >  > > mahmood@localhost:~$ <mailto:mahmood@blackfish:~$> svn update http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
> >  > > Skipped 'http://lm-sensors.org/svn/lm-sensors/trunk'
> >  > > At revision 5857.
> >  > > Summary of conflicts:
> >  > > Skipped paths: 1
> >  > > Is that what you meant?
> >  > > *// Naderan *Mahmood;*
> >  > just svn update # not needed if you have fresh checkout
> >  >
> >  > in lm-sensors/prog/detect run sensors-detect and it should find your core-i7
> >  >
> >  > >
> >  > >
> >  > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ----------------
> --
> > ----
> >  > --
> >  > > *From:* Nikola Pajkovsky <npajkovs@redhat.com<mailto:npajkovs@redhat.com> <mailto:npajkovs@redhat.com<mailto:npajkovs@redhat.com>> <mailto:npajkovs@redhat.com<mailto:npajkovs@redhat.com> <mailto:npajkovs@redhat.com<mailto:npajkovs@redhat.com>>>>
> >  > > *To:* lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org> <mailto:lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org>> <mailto:lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org> <mailto:lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org>>>
> >  > > *Sent:* Wed, September 1, 2010 11:49:03 AM
> >  > > *Subject:* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
> >  > >
> >  > > On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
> >  > > > Dear all,
> >  > > >
> >  > > > I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them. Here is the output of sensors-detect:
> >  > > >
> >  > > >
> >  > > > mahmood@localhost:~$ sudo sensors-detect
> >  > > > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> >  > > > # System: Gigabyte Technology Co., Ltd. P55-USB3
> >  > > >
> >  > > > 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 IT8720F Super IO Sensors' Success!
> >  > > > (address 0x290, 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
> >  > > > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> >  > > > Sorry, no supported PCI bus adapters found.
> >  > > > Module i2c-dev loaded successfully.
> >  > > >
> >  > > > Now follows a summary of the probes I have just done.
> >  > > > Just press ENTER to continue:
> >  > > >
> >  > > > Driver `it87':
> >  > > > * ISA bus, address 0x290
> >  > > > Chip `ITE IT8720F 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)yes
> >  > > > 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
> >  > > >
> >  > > >
> >  > > > Then I ran sensors:
> >  > > >
> >  > > > mahmood@localhost:~$ sudo sensors
> >  > > > it8720-isa-0290
> >  > > > Adapter: ISA adapter
> >  > > > in0: +0.86 V (min = +0.00 V, max = +4.08 V)
> >  > > > in1: +1.58 V (min = +0.00 V, max = +4.08 V)
> >  > > > in2: +3.39 V (min = +0.00 V, max = +4.08 V)
> >  > > > in3: +3.02 V (min = +0.00 V, max = +4.08 V)
> >  > > > in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
> >  > > > in5: +3.12 V (min = +0.00 V, max = +4.08 V)
> >  > > > in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
> >  > > > in7: +2.16 V (min = +0.00 V, max = +4.08 V)
> >  > > > Vbat: +3.10 V
> >  > > > fan1: 1679 RPM (min = 10 RPM)
> >  > > > fan2: 644 RPM (min = 0 RPM)
> >  > > > fan3: 1278 RPM (min = 10 RPM)
> >  > > > fan4: 1205 RPM (min = 0 RPM)
> >  > > > temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> >  > > > temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
> >  > > > temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
> >  > > > cpu0_vid: +0.313 V
> >  > > >
> >  > > >
> >  > > > What can I do then? currently I have kubuntu 10.04
> >  > > >
> >  > > > *// Naderan *Mahmood;*
> >  > > >
> >  > > >
> >  > >
> >  > > Pick sensors-detect from svn or file bug against lm-sensors in ubuntu and maintainer(if he is nice) update lm-sensors.
> >  > >
> >  >
> >
> 
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org<mailto:lm-sensors@lm-sensors.org>
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> 

> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (8 preceding siblings ...)
  2010-09-01 13:26 ` Guenter Roeck
@ 2010-09-01 13:56 ` Jean Delvare
  2010-09-01 14:32 ` Guenter Roeck
                   ` (14 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Jean Delvare @ 2010-09-01 13:56 UTC (permalink / raw)
  To: lm-sensors

On Wed, 1 Sep 2010 06:26:34 -0700, Guenter Roeck wrote:
> On Wed, Sep 01, 2010 at 04:16:41AM -0400, Mahmood Naderan wrote:
> > >sudo /etc/init.d/lm_sensors restart
> > 
> > mahmood@localhost:~$<mailto:mahmood@localhost:~$> sudo /etc/init.d/lm-sensors restart
> > .: 39: Can't open /etc/init.d/functions
> > 
> > Note there is no lm_sensors. I have lm-sensors
> > 
> 
> I tried /etc/init.d/lm-sensors on a lucid (10.04) system and it works for me. It looks like
> you overwrote the original version of /etc/init.d/lm-sensors with prog/init.d/lm_sensors.
> That won't work - prog/init.d/lm_sensors does not work with lucid. You'll need to reinstall
> the original version of /etc/init.d/lm-sensors and try again.

I proposed once to delete these initialization scripts from our
repository as they are quite distribution specific, but the few votes
were not in my favor.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (9 preceding siblings ...)
  2010-09-01 13:56 ` Jean Delvare
@ 2010-09-01 14:32 ` Guenter Roeck
  2010-09-01 14:58 ` Mahmood Naderan
                   ` (13 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-01 14:32 UTC (permalink / raw)
  To: lm-sensors

On Wed, Sep 01, 2010 at 09:56:01AM -0400, Jean Delvare wrote:
> On Wed, 1 Sep 2010 06:26:34 -0700, Guenter Roeck wrote:
> > On Wed, Sep 01, 2010 at 04:16:41AM -0400, Mahmood Naderan wrote:
> > > >sudo /etc/init.d/lm_sensors restart
> > > 
> > > mahmood@localhost:~$<mailto:mahmood@localhost:~$> sudo /etc/init.d/lm-sensors restart
> > > .: 39: Can't open /etc/init.d/functions
> > > 
> > > Note there is no lm_sensors. I have lm-sensors
> > > 
> > 
> > I tried /etc/init.d/lm-sensors on a lucid (10.04) system and it works for me. It looks like
> > you overwrote the original version of /etc/init.d/lm-sensors with prog/init.d/lm_sensors.
> > That won't work - prog/init.d/lm_sensors does not work with lucid. You'll need to reinstall
> > the original version of /etc/init.d/lm-sensors and try again.
> 
> I proposed once to delete these initialization scripts from our
> repository as they are quite distribution specific, but the few votes
> were not in my favor.
> 
How about some kind of warning, or at least use different wording in sensors-detect ?

The current text is quite absolute ("Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors")
and really invites users to overwrite the distribution specific scripts.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (10 preceding siblings ...)
  2010-09-01 14:32 ` Guenter Roeck
@ 2010-09-01 14:58 ` Mahmood Naderan
  2010-09-01 15:52 ` Guenter Roeck
                   ` (12 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-01 14:58 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 5572 bytes --]

>The current text is quite absolute ("Copy prog/init/lm_sensors.init to 
>/etc/init.d/lm_sensors")
>and really invites users to overwrite the distribution specific scripts.
 
I really did that. See:
mahmood@localhost:~$cat /etc/init.d/lm-sensors
#!/bin/sh
#
# chkconfig: - 26 74
# description: sensors is used for monitoring motherboard sensor values.
# config: /etc/sysconfig/lm_sensors
#
#    This program is free software; you can redistribute it and/or modify
#    it under the terms of the GNU General Public License as published by
#    the Free Software Foundation; either version 2 of the License, or
#    (at your option) any later version.
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#    You should have received a copy of the GNU General Public License
#    along with this program; if not, write to the Free Software
#    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
#    MA 02110-1301 USA.
# See also the lm_sensors homepage at:
#     http://www.lm-sensors.org
# It uses a config file /etc/sysconfig/lm_sensors that contains the modules
# to be loaded/unloaded. That file is sourced into this one.
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).
PSENSORS=/usr/local/bin/sensors
if [ ! -x $PSENSORS ]; then
        PSENSORS=/usr/bin/sensors
fi
# Source function library.
. /etc/init.d/functions
RETVAL=0
prog="lm_sensors"
# This functions checks if sensor support is compiled into the kernel, if
# sensors are configured, and loads the config file
check_sensors() {
        CONFIG=/etc/sysconfig/lm_sensors
        if ! [ -r "$CONFIG" ] || ! grep '^HWMON_MODULES' $CONFIG >/dev/null 
2>&1; then
                echo -n "$1 $prog: not configured, run sensors-detect"
                echo_warning
                echo
                exit 6
        fi
        # Load config file
        . "$CONFIG"
}
start() {
        check_sensors "Starting"
        echo -n "Starting $prog: loading module "
        for module in $BUS_MODULES $HWMON_MODULES ; do
                echo -n "${module} "
                /sbin/modprobe $module >/dev/null 2>&1
        done
        $PSENSORS -s
        RETVAL=$?
        if [ $RETVAL -eq 0 ] && touch /var/lock/subsys/lm_sensors ; then
                echo_success
                echo
        else
                echo_failure
                echo
        fi
}
stop() {
        check_sensors "Stopping"
        echo -n "Stopping $prog: "
        for module in $HWMON_MODULES $BUS_MODULES ; do
                /sbin/modprobe -r $module >/dev/null 2>&1
        done
        RETVAL=$?
        if [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/lm_sensors ; then
                echo_success
                echo
        else
                echo_failure
                echo
        fi
}
dostatus() {
        $PSENSORS
        RETVAL=$?
        if [ $RETVAL -ne 0 ]; then
                RETVAL=3
        fi
}
restart() {
        stop
        start
}
condrestart() {
        [ -e /var/lock/subsys/lm_sensors ] && restart || :
}
# See how we were called.
case "$1" in
  start)
        start
        ;;
  stop)
        stop
        ;;
  status)
        dostatus
        ;;
  restart|reload)
        restart
        ;;
  condrestart)
        condrestart
        ;;
  *)
        echo "Usage: $0 {start|stop|status|restart|reload|condrestart}"
        exit 3
esac
exit $RETVAL

Do you confirm that? What should I do in order to remove lm-sensor and reinstall 
it again?
 
// Naderan *Mahmood;




________________________________
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Mahmood Naderan <nt_mahmood@yahoo.com>; lm-sensors 
<lm-sensors@lm-sensors.org>
Sent: Wed, September 1, 2010 7:02:25 PM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

On Wed, Sep 01, 2010 at 09:56:01AM -0400, Jean Delvare wrote:
> On Wed, 1 Sep 2010 06:26:34 -0700, Guenter Roeck wrote:
> > On Wed, Sep 01, 2010 at 04:16:41AM -0400, Mahmood Naderan wrote:
> > > >sudo /etc/init.d/lm_sensors restart
> > > 
> > > mahmood@localhost:~$<mailto:mahmood@localhost:~$> sudo 
>/etc/init.d/lm-sensors restart
> > > .: 39: Can't open /etc/init.d/functions
> > > 
> > > Note there is no lm_sensors. I have lm-sensors
> > > 
> > 
> > I tried /etc/init.d/lm-sensors on a lucid (10.04) system and it works for me. 
>It looks like
> > you overwrote the original version of /etc/init.d/lm-sensors with 
>prog/init.d/lm_sensors.
> > That won't work - prog/init.d/lm_sensors does not work with lucid. You'll 
>need to reinstall
> > the original version of /etc/init.d/lm-sensors and try again.
> 
> I proposed once to delete these initialization scripts from our
> repository as they are quite distribution specific, but the few votes
> were not in my favor.
> 
How about some kind of warning, or at least use different wording in 
sensors-detect ?

The current text is quite absolute ("Copy prog/init/lm_sensors.init to 
/etc/init.d/lm_sensors")
and really invites users to overwrite the distribution specific scripts.

Guenter



      

[-- Attachment #1.2: Type: text/html, Size: 11921 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (11 preceding siblings ...)
  2010-09-01 14:58 ` Mahmood Naderan
@ 2010-09-01 15:52 ` Guenter Roeck
  2010-09-01 16:57 ` Mahmood Naderan
                   ` (11 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-01 15:52 UTC (permalink / raw)
  To: lm-sensors

On Wed, Sep 01, 2010 at 10:58:47AM -0400, Mahmood Naderan wrote:
> >The current text is quite absolute ("Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors")
> >and really invites users to overwrite the distribution specific scripts.
> 
> I really did that. See:
> 
[...]

> Do you confirm that? What should I do in order to remove lm-sensor and reinstall it again?
> 
Try

	sudo aptitude reinstall lm-sensors

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (12 preceding siblings ...)
  2010-09-01 15:52 ` Guenter Roeck
@ 2010-09-01 16:57 ` Mahmood Naderan
  2010-09-03 14:31 ` Guenter Roeck
                   ` (10 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-01 16:57 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 9807 bytes --]

>  sudo aptitude reinstall lm-sensors
That didn't work. So I managed to completely remove lm-sensors with "sudo 
apt-get --purge remove lm-sensors".
After that I enterd progs/detect and ran "sudo ./sensors-detect":

mahmood@localhost:detect$ sudo ./sensors-detect
# sensors-detect revision 5853 (2010-08-13 02:00:13 +0430)
# System: Gigabyte Technology Co., Ltd. P55-USB3
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...                         Success!
    (driver `coretemp')
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 IT8720F Super IO Sensors'                        Success!
    (address 0x290, 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-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.
Next adapter: NVIDIA i2c adapter  (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter  (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x49
Probing for `National Semiconductor LM75'...                No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Dallas Semiconductor DS1621/DS1631'...         No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              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: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter  (i2c-3)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter  (i2c-4)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter  (i2c-5)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter  (i2c-6)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter  (i2c-7)
Do you want to scan it? (YES/no/selectively): y
Next adapter: SMBus I801 adapter at 0500 (i2c-8)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x4e
Probing for `National Semiconductor LM75'...                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 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 `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 `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 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
  * ISA bus, address 0x290
    Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
Driver `coretemp':
  * Chip `Intel Core family thermal sensor' (confidence: 9)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): yes
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
 
As you see, core-i7 is detected. Also it says: "Copy prog/init/lm_sensors.init 
to /etc/init.d/lm_sensors
for initialization at boot time." I did that. 
 
Now shat should I do in the next step? I don't want to reboot. What is the 
command to restart the service?
 
// Naderan *Mahmood;




________________________________
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Mahmood Naderan <nt_mahmood@yahoo.com>
Cc: lm-sensors <lm-sensors@lm-sensors.org>
Sent: Wed, September 1, 2010 8:22:03 PM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

On Wed, Sep 01, 2010 at 10:58:47AM -0400, Mahmood Naderan wrote:
> >The current text is quite absolute ("Copy prog/init/lm_sensors.init to 
>/etc/init.d/lm_sensors")
> >and really invites users to overwrite the distribution specific scripts.
> 
> I really did that. See:
> 
[...]

> Do you confirm that? What should I do in order to remove lm-sensor and 
>reinstall it again?
> 
Try

    sudo aptitude reinstall lm-sensors

Guenter



      

[-- Attachment #1.2: Type: text/html, Size: 20225 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (13 preceding siblings ...)
  2010-09-01 16:57 ` Mahmood Naderan
@ 2010-09-03 14:31 ` Guenter Roeck
  2010-09-04 13:49 ` Jean Delvare
                   ` (9 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-03 14:31 UTC (permalink / raw)
  To: lm-sensors

On Wed, 2010-09-01 at 12:57 -0400, Mahmood Naderan wrote:
> >  sudo aptitude reinstall lm-sensors
> 
> That didn't work. So I managed to completely remove lm-sensors with
> "sudo apt-get --purge remove lm-sensors".
> 
Did you re-install it afterwards ?

[...]

> 
> As you see, core-i7 is detected. Also it says: "Copy
> prog/init/lm_sensors.init to /etc/init.d/lm_sensors
> for initialization at boot time." I did that. 

It would have been better to stick with the script from the Ubuntu
distribution (/etc/init.d/lm-sensors). The one you copied likely won't
work.

sudo /etc/init.d/lm-sensors restart would then restart the service.

Guenter




_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (14 preceding siblings ...)
  2010-09-03 14:31 ` Guenter Roeck
@ 2010-09-04 13:49 ` Jean Delvare
  2010-09-04 14:25 ` Guenter Roeck
                   ` (8 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Jean Delvare @ 2010-09-04 13:49 UTC (permalink / raw)
  To: lm-sensors

Guenter,

On Wed, 1 Sep 2010 07:32:25 -0700, Guenter Roeck wrote:
> On Wed, Sep 01, 2010 at 09:56:01AM -0400, Jean Delvare wrote:
> > On Wed, 1 Sep 2010 06:26:34 -0700, Guenter Roeck wrote:
> > > On Wed, Sep 01, 2010 at 04:16:41AM -0400, Mahmood Naderan wrote:
> > > > >sudo /etc/init.d/lm_sensors restart
> > > > 
> > > > mahmood@localhost:~$<mailto:mahmood@localhost:~$> sudo /etc/init.d/lm-sensors restart
> > > > .: 39: Can't open /etc/init.d/functions
> > > > 
> > > > Note there is no lm_sensors. I have lm-sensors
> > > > 
> > > 
> > > I tried /etc/init.d/lm-sensors on a lucid (10.04) system and it works for me. It looks like
> > > you overwrote the original version of /etc/init.d/lm-sensors with prog/init.d/lm_sensors.
> > > That won't work - prog/init.d/lm_sensors does not work with lucid. You'll need to reinstall
> > > the original version of /etc/init.d/lm-sensors and try again.
> > 
> > I proposed once to delete these initialization scripts from our
> > repository as they are quite distribution specific, but the few votes
> > were not in my favor.
> > 
> How about some kind of warning, or at least use different wording in sensors-detect ?
> 
> The current text is quite absolute ("Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors")
> and really invites users to overwrite the distribution specific scripts.

Actually it doesn't:

		print "Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors\n".
		      "for initialization at boot time.\n"
			unless -f "/etc/init.d/lm_sensors";

So the message isn't printed if there is already a script there.

In Mahmood's case, the script is named /etc/init.d/lm-sensors instead,
so the message would be printed, but running the suggested command
would _not_ overwrite the file. Not sure what happens where both
scripts are present though...

So I would suggest that we simply extend the test to:

			unless -f "/etc/init.d/lm_sensors"
			    or -f "/etc/init.d/lm-sensors";

Would that be OK with you?

If you have a better proposal, I'm listening. The only alternative I
have in mind is to get rid of the message altogether and delete the
init script from our repository, leaving integration up to each
distribution (which at least openSUSE and derivatives already do.)

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (15 preceding siblings ...)
  2010-09-04 13:49 ` Jean Delvare
@ 2010-09-04 14:25 ` Guenter Roeck
  2010-09-04 14:31 ` Mahmood Naderan
                   ` (7 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-04 14:25 UTC (permalink / raw)
  To: lm-sensors

Jean,

On Sat, Sep 04, 2010 at 09:49:42AM -0400, Jean Delvare wrote:
> Guenter,
> 
> On Wed, 1 Sep 2010 07:32:25 -0700, Guenter Roeck wrote:
> > On Wed, Sep 01, 2010 at 09:56:01AM -0400, Jean Delvare wrote:
> > > On Wed, 1 Sep 2010 06:26:34 -0700, Guenter Roeck wrote:
> > > > On Wed, Sep 01, 2010 at 04:16:41AM -0400, Mahmood Naderan wrote:
> > > > > >sudo /etc/init.d/lm_sensors restart
> > > > > 
> > > > > mahmood@localhost:~$<mailto:mahmood@localhost:~$> sudo /etc/init.d/lm-sensors restart
> > > > > .: 39: Can't open /etc/init.d/functions
> > > > > 
> > > > > Note there is no lm_sensors. I have lm-sensors
> > > > > 
> > > > 
> > > > I tried /etc/init.d/lm-sensors on a lucid (10.04) system and it works for me. It looks like
> > > > you overwrote the original version of /etc/init.d/lm-sensors with prog/init.d/lm_sensors.
> > > > That won't work - prog/init.d/lm_sensors does not work with lucid. You'll need to reinstall
> > > > the original version of /etc/init.d/lm-sensors and try again.
> > > 
> > > I proposed once to delete these initialization scripts from our
> > > repository as they are quite distribution specific, but the few votes
> > > were not in my favor.
> > > 
> > How about some kind of warning, or at least use different wording in sensors-detect ?
> > 
> > The current text is quite absolute ("Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors")
> > and really invites users to overwrite the distribution specific scripts.
> 
> Actually it doesn't:
> 
> 		print "Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors\n".
> 		      "for initialization at boot time.\n"
> 			unless -f "/etc/init.d/lm_sensors";
> 
> So the message isn't printed if there is already a script there.
> 
> In Mahmood's case, the script is named /etc/init.d/lm-sensors instead,
> so the message would be printed, but running the suggested command
> would _not_ overwrite the file. Not sure what happens where both
> scripts are present though...
> 
Problem is two-fold: 
1) People will/may remove lm-sensors anyway, being intelligent and assuming
   this is what they should do.
2) lm_sensors doesn't work with Ubuntu anyway, since /etc/init.d/functions
   does not exist.

> So I would suggest that we simply extend the test to:
> 
> 			unless -f "/etc/init.d/lm_sensors"
> 			    or -f "/etc/init.d/lm-sensors";
> 
> Would that be OK with you?
> 
Yes.

Another question is if we can get rid of the inclusion of /etc/init.d/functions.
I browsed through the code, but don't immediately see which functions
are used from it, and if they can be replaced. What do you think ?

> If you have a better proposal, I'm listening. The only alternative I
> have in mind is to get rid of the message altogether and delete the
> init script from our repository, leaving integration up to each
> distribution (which at least openSUSE and derivatives already do.)
> 
Removing it sounds like overkill to me. After all, it _does_
provide value (when it works). Maybe we should do the above,
and spend some time getting it to work w/ Ubuntu given its
distribution. I should be able to do that.

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (16 preceding siblings ...)
  2010-09-04 14:25 ` Guenter Roeck
@ 2010-09-04 14:31 ` Mahmood Naderan
  2010-09-04 15:55 ` Jean Delvare
                   ` (6 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-04 14:31 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 7384 bytes --]

>2) lm_sensors doesn't work with Ubuntu anyway, since /etc/init.d/functions
>  does not exist.

Agree with that. Another thing I found is that the default locations are 
different for "installing via synaptic" and "installing from source". See this 
log:

mahmood@lcoalhost:lm-sensors$sudo make install
mkdir -p /usr/local/lib /usr/local/include/sensors /usr/local/man/man3 
/usr/local/man/man5
******************************************************************************
Warning: This is the first installation of the libsensors.so.4*
         library files in /usr/local/lib!
         You must update the library cache or the userspace tools may fail
         or have unpredictable results!
         Run the following command: /sbin/ldconfig
******************************************************************************
install -m 644 lib/libsensors.a /usr/local/lib
install -m 755 lib/libsensors.so.4.2.1 /usr/local/lib
ln -sf libsensors.so.4.2.1 /usr/local/lib/libsensors.so.4
ln -sf libsensors.so.4 /usr/local/lib/libsensors.so
******************************************************************************
Warning: Library directory /usr/local/lib is not in /etc/ld.so.conf!
         Add it and run /sbin/ldconfig for the userspace tools to work.
******************************************************************************
install -m 644 lib/error.h lib/sensors.h /usr/local/include/sensors
install -m 644 lib/libsensors.3 /usr/local/man/man3
install -m 644 lib/sensors.conf.5 /usr/local/man/man5
ln -sf sensors.conf.5 /usr/local/man/man5/sensors3.conf.5
mkdir -p /usr/local/sbin /usr/local/man/man8
install -m 755 prog/detect/sensors-detect /usr/local/sbin
install -m 644 prog/detect/sensors-detect.8 /usr/local/man/man8
mkdir -p /usr/local/sbin /usr/local/man/man8
install -m 755 prog/pwm/fancontrol prog/pwm/pwmconfig /usr/local/sbin
install -m 644 prog/pwm/fancontrol.8 prog/pwm/pwmconfig.8 /usr/local/man/man8
mkdir -p /usr/local/bin /usr/local/man/man1
install -m 755 prog/sensors/sensors /usr/local/bin
install -m 644 prog/sensors/sensors.1 /usr/local/man/man1
mkdir -p /etc /etc/sensors.d
if [ ! -e /etc/sensors3.conf ] ; then \
          install -m 644 etc/sensors.conf.default /etc/sensors3.conf ; \
        fi
mkdir -p /usr/local/bin
install -m 755 etc/sensors-conf-convert /usr/local/bin
if [ -e /etc/modprobe.d/lm_sensors \
             -a ! -e /etc/modprobe.d/lm_sensors.conf ] ; then \
          mv -f /etc/modprobe.d/lm_sensors /etc/modprobe.d/lm_sensors.conf ; \
        fi
mkdir -p /usr/local/sbin /usr/local/man/man8
install -m 755 prog/dump/isadump prog/dump/isaset /usr/local/sbin
install -m 644 prog/dump/isadump.8 prog/dump/isaset.8 /usr/local/man/man8
*** Important notes:
***  * The libsensors configuration file (/etc/sensors3.conf) is never
***    overwritten by our installation process, so that you won't lose
***    your personal settings in that file. You still can get our latest
***    default config file in etc/sensors.conf.default and manually copy
***    it to /etc/sensors3.conf if you want. You will then want to
***    edit it to fit your needs again.
***  * The format of /etc/sensors3.conf changed with lm-sensors 3.0.0.
***    If you have a custom configuration file using the old format, you
***    can convert it using the sensors-conf-convert script. Otherwise just
***    overwrite your old configuration file with the new default one.
***  * As off lm-sensors 3.1.0, the default configuration file only
***    contains statements which do not depend on how chips are wired.
***    If you miss parts of the bigger configuration file that used to be
***    the default, copy the relevant parts from etc/sensors.conf.eg to
***    /etc/sensors3.conf.

 
// Naderan *Mahmood;




________________________________
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Mahmood Naderan <nt_mahmood@yahoo.com>; lm-sensors 
<lm-sensors@lm-sensors.org>
Sent: Sat, September 4, 2010 6:55:34 PM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

Jean,

On Sat, Sep 04, 2010 at 09:49:42AM -0400, Jean Delvare wrote:
> Guenter,
> 
> On Wed, 1 Sep 2010 07:32:25 -0700, Guenter Roeck wrote:
> > On Wed, Sep 01, 2010 at 09:56:01AM -0400, Jean Delvare wrote:
> > > On Wed, 1 Sep 2010 06:26:34 -0700, Guenter Roeck wrote:
> > > > On Wed, Sep 01, 2010 at 04:16:41AM -0400, Mahmood Naderan wrote:
> > > > > >sudo /etc/init.d/lm_sensors restart
> > > > > 
> > > > > mahmood@localhost:~$<mailto:mahmood@localhost:~$> sudo 
>/etc/init.d/lm-sensors restart
> > > > > .: 39: Can't open /etc/init.d/functions
> > > > > 
> > > > > Note there is no lm_sensors. I have lm-sensors
> > > > > 
> > > > 
> > > > I tried /etc/init.d/lm-sensors on a lucid (10.04) system and it works for 
>me. It looks like
> > > > you overwrote the original version of /etc/init.d/lm-sensors with 
>prog/init.d/lm_sensors.
> > > > That won't work - prog/init.d/lm_sensors does not work with lucid. You'll 
>need to reinstall
> > > > the original version of /etc/init.d/lm-sensors and try again.
> > > 
> > > I proposed once to delete these initialization scripts from our
> > > repository as they are quite distribution specific, but the few votes
> > > were not in my favor.
> > > 
> > How about some kind of warning, or at least use different wording in 
>sensors-detect ?
> > 
> > The current text is quite absolute ("Copy prog/init/lm_sensors.init to 
>/etc/init.d/lm_sensors")
> > and really invites users to overwrite the distribution specific scripts.
> 
> Actually it doesn't:
> 
>         print "Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors\n".
>               "for initialization at boot time.\n"
>             unless -f "/etc/init.d/lm_sensors";
> 
> So the message isn't printed if there is already a script there.
> 
> In Mahmood's case, the script is named /etc/init.d/lm-sensors instead,
> so the message would be printed, but running the suggested command
> would _not_ overwrite the file. Not sure what happens where both
> scripts are present though...
> 
Problem is two-fold: 
1) People will/may remove lm-sensors anyway, being intelligent and assuming
  this is what they should do.
2) lm_sensors doesn't work with Ubuntu anyway, since /etc/init.d/functions
  does not exist.

> So I would suggest that we simply extend the test to:
> 
>             unless -f "/etc/init.d/lm_sensors"
>                 or -f "/etc/init.d/lm-sensors";
> 
> Would that be OK with you?
> 
Yes.

Another question is if we can get rid of the inclusion of /etc/init.d/functions.
I browsed through the code, but don't immediately see which functions
are used from it, and if they can be replaced. What do you think ?

> If you have a better proposal, I'm listening. The only alternative I
> have in mind is to get rid of the message altogether and delete the
> init script from our repository, leaving integration up to each
> distribution (which at least openSUSE and derivatives already do.)
> 
Removing it sounds like overkill to me. After all, it _does_
provide value (when it works). Maybe we should do the above,
and spend some time getting it to work w/ Ubuntu given its
distribution. I should be able to do that.

Thanks,
Guenter



      

[-- Attachment #1.2: Type: text/html, Size: 9925 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (17 preceding siblings ...)
  2010-09-04 14:31 ` Mahmood Naderan
@ 2010-09-04 15:55 ` Jean Delvare
  2010-09-04 17:28 ` Guenter Roeck
                   ` (5 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Jean Delvare @ 2010-09-04 15:55 UTC (permalink / raw)
  To: lm-sensors

On Sat, 4 Sep 2010 07:25:34 -0700, Guenter Roeck wrote:
> Jean,
> 
> On Sat, Sep 04, 2010 at 09:49:42AM -0400, Jean Delvare wrote:
> > Guenter,
> > 
> > On Wed, 1 Sep 2010 07:32:25 -0700, Guenter Roeck wrote:
> > > How about some kind of warning, or at least use different wording in sensors-detect ?
> > > 
> > > The current text is quite absolute ("Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors")
> > > and really invites users to overwrite the distribution specific scripts.
> > 
> > Actually it doesn't:
> > 
> > 		print "Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors\n".
> > 		      "for initialization at boot time.\n"
> > 			unless -f "/etc/init.d/lm_sensors";
> > 
> > So the message isn't printed if there is already a script there.
> > 
> > In Mahmood's case, the script is named /etc/init.d/lm-sensors instead,
> > so the message would be printed, but running the suggested command
> > would _not_ overwrite the file. Not sure what happens where both
> > scripts are present though...
> > 
> Problem is two-fold: 
> 1) People will/may remove lm-sensors anyway, being intelligent and assuming
>    this is what they should do.
> 2) lm_sensors doesn't work with Ubuntu anyway, since /etc/init.d/functions
>    does not exist.
> 
> > So I would suggest that we simply extend the test to:
> > 
> > 			unless -f "/etc/init.d/lm_sensors"
> > 			    or -f "/etc/init.d/lm-sensors";
> > 
> > Would that be OK with you?
> > 
> Yes.

Hmmm. The problem is that there's more than /etc/init.d/lm_sensors. We
also have /etc/modprobe.d/lm_sensors.conf and /etc/sysconfig/lm_sensors.
More generally, "lm_sensors" is the service name here, if a
distribution changes /etc/init.d/lm_sensors to /etc/init.d/lm-sensors,
I expect them to be consistent and change to "lm-sensors" everywhere.

Debian uses "lm-sensors" for the service name for some time now, but
they don't use sysconfig, so we didn't care. If we now have
distributions using sysconfig _and_ not using the standard "lm_sensors"
name for the service, sensors-detect would have to be a lot smarter.

Or we can see it the other way around: sensors-detect assumes that the
service is named "lm_sensors", if distributions can't stick to that,
it's their pain, not ours. What's the point of diverging from us on the
service name after all?

Note that the lm_sensors.init script we ship _does_ assume that the
service is named "lm_sensors". So just updating sensors-detect wouldn't
be enough.

> Another question is if we can get rid of the inclusion of /etc/init.d/functions.
> I browsed through the code, but don't immediately see which functions
> are used from it, and if they can be replaced. What do you think ?

openSUSE doesn't have this file either. I presume it is included for
echo_warning, echo_success and echo_failure.

Do what you want with the script. Me, I don't want to spend one single
minute on it.

> > If you have a better proposal, I'm listening. The only alternative I
> > have in mind is to get rid of the message altogether and delete the
> > init script from our repository, leaving integration up to each
> > distribution (which at least openSUSE and derivatives already do.)
> > 
> Removing it sounds like overkill to me. After all, it _does_
> provide value (when it works). Maybe we should do the above,
> and spend some time getting it to work w/ Ubuntu given its
> distribution. I should be able to do that.

Where does it work? All distributions I know of, ship their own
initialization script. There are so many dependencies (as you just
found out) and conventions (e.g. service naming, as you just found out
as well) involved, we can't make everyone happy.

The initialization script is only useful to people installing
lm-sensors from the sources on distributions which do not have
it already installed via a package. There aren't many doing that these
days, I think. And these can probably just add a couple modprobe lines
in a custom init script, as sensors-detect suggests. lm_sensors isn't
really a service, there's no daemon running (unless you throw sensord
into the game) so stopping it is totally optional.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (18 preceding siblings ...)
  2010-09-04 15:55 ` Jean Delvare
@ 2010-09-04 17:28 ` Guenter Roeck
  2010-09-06 16:18 ` Jean Delvare
                   ` (4 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-04 17:28 UTC (permalink / raw)
  To: lm-sensors

On Sat, Sep 04, 2010 at 11:55:29AM -0400, Jean Delvare wrote:
> On Sat, 4 Sep 2010 07:25:34 -0700, Guenter Roeck wrote:
> > Jean,
> > 
> > On Sat, Sep 04, 2010 at 09:49:42AM -0400, Jean Delvare wrote:
> > > Guenter,
> > > 
> > > On Wed, 1 Sep 2010 07:32:25 -0700, Guenter Roeck wrote:
> > > > How about some kind of warning, or at least use different wording in sensors-detect ?
> > > > 
> > > > The current text is quite absolute ("Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors")
> > > > and really invites users to overwrite the distribution specific scripts.
> > > 
> > > Actually it doesn't:
> > > 
> > > 		print "Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors\n".
> > > 		      "for initialization at boot time.\n"
> > > 			unless -f "/etc/init.d/lm_sensors";
> > > 
> > > So the message isn't printed if there is already a script there.
> > > 
> > > In Mahmood's case, the script is named /etc/init.d/lm-sensors instead,
> > > so the message would be printed, but running the suggested command
> > > would _not_ overwrite the file. Not sure what happens where both
> > > scripts are present though...
> > > 
> > Problem is two-fold: 
> > 1) People will/may remove lm-sensors anyway, being intelligent and assuming
> >    this is what they should do.
> > 2) lm_sensors doesn't work with Ubuntu anyway, since /etc/init.d/functions
> >    does not exist.
> > 
> > > So I would suggest that we simply extend the test to:
> > > 
> > > 			unless -f "/etc/init.d/lm_sensors"
> > > 			    or -f "/etc/init.d/lm-sensors";
> > > 
> > > Would that be OK with you?
> > > 
> > Yes.
> 
> Hmmm. The problem is that there's more than /etc/init.d/lm_sensors. We
> also have /etc/modprobe.d/lm_sensors.conf and /etc/sysconfig/lm_sensors.
> More generally, "lm_sensors" is the service name here, if a
> distribution changes /etc/init.d/lm_sensors to /etc/init.d/lm-sensors,
> I expect them to be consistent and change to "lm-sensors" everywhere.
> 
> Debian uses "lm-sensors" for the service name for some time now, but
> they don't use sysconfig, so we didn't care. If we now have
> distributions using sysconfig _and_ not using the standard "lm_sensors"
> name for the service, sensors-detect would have to be a lot smarter.
> 
> Or we can see it the other way around: sensors-detect assumes that the
> service is named "lm_sensors", if distributions can't stick to that,
> it's their pain, not ours. What's the point of diverging from us on the
> service name after all?
> 
> Note that the lm_sensors.init script we ship _does_ assume that the
> service is named "lm_sensors". So just updating sensors-detect wouldn't
> be enough.
> 
> > Another question is if we can get rid of the inclusion of /etc/init.d/functions.
> > I browsed through the code, but don't immediately see which functions
> > are used from it, and if they can be replaced. What do you think ?
> 
> openSUSE doesn't have this file either. I presume it is included for
> echo_warning, echo_success and echo_failure.
> 
> Do what you want with the script. Me, I don't want to spend one single
> minute on it.
> 
Having second thoughts there, given all the complexity involved.

> > > If you have a better proposal, I'm listening. The only alternative I
> > > have in mind is to get rid of the message altogether and delete the
> > > init script from our repository, leaving integration up to each
> > > distribution (which at least openSUSE and derivatives already do.)
> > > 
> > Removing it sounds like overkill to me. After all, it _does_
> > provide value (when it works). Maybe we should do the above,
> > and spend some time getting it to work w/ Ubuntu given its
> > distribution. I should be able to do that.
> 
> Where does it work? All distributions I know of, ship their own

Good question ...

> initialization script. There are so many dependencies (as you just
> found out) and conventions (e.g. service naming, as you just found out
> as well) involved, we can't make everyone happy.
> 
> The initialization script is only useful to people installing
> lm-sensors from the sources on distributions which do not have
> it already installed via a package. There aren't many doing that these
> days, I think. And these can probably just add a couple modprobe lines
> in a custom init script, as sensors-detect suggests. lm_sensors isn't
> really a service, there's no daemon running (unless you throw sensord
> into the game) so stopping it is totally optional.
> 
Maybe the best approach is to not (try to) install it at all, but just provide
it as hint. Or maybe check if /etc/init.d/lm-sensors exists, and if it does
don't install anything at all.

The shared library locations are yet another problem. Not sure how to address
that either.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (19 preceding siblings ...)
  2010-09-04 17:28 ` Guenter Roeck
@ 2010-09-06 16:18 ` Jean Delvare
  2010-09-07  1:32 ` Guenter Roeck
                   ` (3 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Jean Delvare @ 2010-09-06 16:18 UTC (permalink / raw)
  To: lm-sensors

On Sat, 4 Sep 2010 10:28:32 -0700, Guenter Roeck wrote:
> On Sat, Sep 04, 2010 at 11:55:29AM -0400, Jean Delvare wrote:
> > On Sat, 4 Sep 2010 07:25:34 -0700, Guenter Roeck wrote:
> > > Removing it sounds like overkill to me. After all, it _does_
> > > provide value (when it works). Maybe we should do the above,
> > > and spend some time getting it to work w/ Ubuntu given its
> > > distribution. I should be able to do that.
> > 
> > Where does it work? All distributions I know of, ship their own
> 
> Good question ...
> 
> > initialization script. There are so many dependencies (as you just
> > found out) and conventions (e.g. service naming, as you just found out
> > as well) involved, we can't make everyone happy.
> > 
> > The initialization script is only useful to people installing
> > lm-sensors from the sources on distributions which do not have
> > it already installed via a package. There aren't many doing that these
> > days, I think. And these can probably just add a couple modprobe lines
> > in a custom init script, as sensors-detect suggests. lm_sensors isn't
> > really a service, there's no daemon running (unless you throw sensord
> > into the game) so stopping it is totally optional.
>
> Maybe the best approach is to not (try to) install it at all, but just provide
> it as hint.

Isn't it exactly what we're doing today?

> Or maybe check if /etc/init.d/lm-sensors exists, and if it does
> don't install anything at all.

We could do that, but that's an invitation for distribution to use
lm-sensors instead of lm_sensors as the service name. I'd rather push
all distributions to stick to lm_sensors.

> The shared library locations are yet another problem. Not sure how to address
> that either.

I have no idea what you're talking about, sorry.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (20 preceding siblings ...)
  2010-09-06 16:18 ` Jean Delvare
@ 2010-09-07  1:32 ` Guenter Roeck
  2010-09-07  8:00 ` Jean Delvare
                   ` (2 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-07  1:32 UTC (permalink / raw)
  To: lm-sensors

On Mon, Sep 06, 2010 at 12:18:58PM -0400, Jean Delvare wrote:
> On Sat, 4 Sep 2010 10:28:32 -0700, Guenter Roeck wrote:
> > On Sat, Sep 04, 2010 at 11:55:29AM -0400, Jean Delvare wrote:
> > > On Sat, 4 Sep 2010 07:25:34 -0700, Guenter Roeck wrote:
> > > > Removing it sounds like overkill to me. After all, it _does_
> > > > provide value (when it works). Maybe we should do the above,
> > > > and spend some time getting it to work w/ Ubuntu given its
> > > > distribution. I should be able to do that.
> > > 
> > > Where does it work? All distributions I know of, ship their own
> > 
> > Good question ...
> > 
> > > initialization script. There are so many dependencies (as you just
> > > found out) and conventions (e.g. service naming, as you just found out
> > > as well) involved, we can't make everyone happy.
> > > 
> > > The initialization script is only useful to people installing
> > > lm-sensors from the sources on distributions which do not have
> > > it already installed via a package. There aren't many doing that these
> > > days, I think. And these can probably just add a couple modprobe lines
> > > in a custom init script, as sensors-detect suggests. lm_sensors isn't
> > > really a service, there's no daemon running (unless you throw sensord
> > > into the game) so stopping it is totally optional.
> >
> > Maybe the best approach is to not (try to) install it at all, but just provide
> > it as hint.
> 
> Isn't it exactly what we're doing today?
> 
Yes, sorry, I meant rewording the text.

> > Or maybe check if /etc/init.d/lm-sensors exists, and if it does
> > don't install anything at all.
> 
> We could do that, but that's an invitation for distribution to use
> lm-sensors instead of lm_sensors as the service name. I'd rather push
> all distributions to stick to lm_sensors.
> 
> > The shared library locations are yet another problem. Not sure how to address
> > that either.
> 
> I have no idea what you're talking about, sorry.
> 
I meant that Ubuntu doesnm't use /usr/local/lib. Maybe that isn't really a problem, though.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (21 preceding siblings ...)
  2010-09-07  1:32 ` Guenter Roeck
@ 2010-09-07  8:00 ` Jean Delvare
  2010-09-13  8:04 ` Mahmood Naderan
  2010-09-14 16:20 ` Guenter Roeck
  24 siblings, 0 replies; 26+ messages in thread
From: Jean Delvare @ 2010-09-07  8:00 UTC (permalink / raw)
  To: lm-sensors

On Mon, 6 Sep 2010 18:32:56 -0700, Guenter Roeck wrote:
> On Mon, Sep 06, 2010 at 12:18:58PM -0400, Jean Delvare wrote:
> > On Sat, 4 Sep 2010 10:28:32 -0700, Guenter Roeck wrote:
> > > Maybe the best approach is to not (try to) install it at all, but just provide
> > > it as hint.
> > 
> > Isn't it exactly what we're doing today?
> > 
> Yes, sorry, I meant rewording the text.

Oh, OK. Feel free to update sensors-detect with a better text, no
problem.

> > > (...)
> > > The shared library locations are yet another problem. Not sure how to address
> > > that either.
> > 
> > I have no idea what you're talking about, sorry.
>
> I meant that Ubuntu doesnm't use /usr/local/lib. Maybe that isn't really a problem, though.

Should be easy enough to check whether /usr/local/lib is
in /etc/ld.so.conf, and warn the user if it isn't. Again, feel tree to
do that if you think it's helpful.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (22 preceding siblings ...)
  2010-09-07  8:00 ` Jean Delvare
@ 2010-09-13  8:04 ` Mahmood Naderan
  2010-09-14 16:20 ` Guenter Roeck
  24 siblings, 0 replies; 26+ messages in thread
From: Mahmood Naderan @ 2010-09-13  8:04 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 1593 bytes --]

What is the conclusion then? I read this thread but didn't end up with a clear 
solution. Is it related to the distro or lm-sensors?

I need to see core temps in my kubuntu/ubuntu 10.04 with 2.6.32-24-generic 
kernel. Some one please answer step byt step from scratch.

Thanks, 
// Naderan *Mahmood;




________________________________
From: Jean Delvare <khali@linux-fr.org>
To: Guenter Roeck <guenter.roeck@ericsson.com>
Cc: Mahmood Naderan <nt_mahmood@yahoo.com>; lm-sensors 
<lm-sensors@lm-sensors.org>
Sent: Tue, September 7, 2010 12:30:03 PM
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors

On Mon, 6 Sep 2010 18:32:56 -0700, Guenter Roeck wrote:
> On Mon, Sep 06, 2010 at 12:18:58PM -0400, Jean Delvare wrote:
> > On Sat, 4 Sep 2010 10:28:32 -0700, Guenter Roeck wrote:
> > > Maybe the best approach is to not (try to) install it at all, but just 
>provide
> > > it as hint.
> > 
> > Isn't it exactly what we're doing today?
> > 
> Yes, sorry, I meant rewording the text.

Oh, OK. Feel free to update sensors-detect with a better text, no
problem.

> > > (...)
> > > The shared library locations are yet another problem. Not sure how to 
>address
> > > that either.
> > 
> > I have no idea what you're talking about, sorry.
>
> I meant that Ubuntu doesnm't use /usr/local/lib. Maybe that isn't really a 
>problem, though.

Should be easy enough to check whether /usr/local/lib is
in /etc/ld.so.conf, and warn the user if it isn't. Again, feel tree to
do that if you think it's helpful.

-- 
Jean Delvare



      

[-- Attachment #1.2: Type: text/html, Size: 2618 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
  2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
                   ` (23 preceding siblings ...)
  2010-09-13  8:04 ` Mahmood Naderan
@ 2010-09-14 16:20 ` Guenter Roeck
  24 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2010-09-14 16:20 UTC (permalink / raw)
  To: lm-sensors

On Mon, Sep 13, 2010 at 04:04:40AM -0400, Mahmood Naderan wrote:
> What is the conclusion then? I read this thread but didn't end up with a clear solution. Is it related to the distro or lm-sensors?
> 
> I need to see core temps in my kubuntu/ubuntu 10.04 with 2.6.32-24-generic kernel. Some one please answer step byt step from scratch.
> 
Stick with your distribution.

Run "sudo modprobe coretemp", then check if the core sensors show up.
If yes, add the required modules (probably it87 and coretemp) into /etc/modules.

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 26+ messages in thread

end of thread, other threads:[~2010-09-14 16:20 UTC | newest]

Thread overview: 26+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
2010-09-01  7:19 ` Nikola Pajkovsky
2010-09-01  7:30 ` Mahmood Naderan
2010-09-01  7:38 ` Nikola Pajkovsky
2010-09-01  7:46 ` Mahmood Naderan
2010-09-01  7:53 ` Nikola Pajkovsky
2010-09-01  8:03 ` Mahmood Naderan
2010-09-01  8:11 ` Nikola Pajkovsky
2010-09-01  8:16 ` Mahmood Naderan
2010-09-01 13:26 ` Guenter Roeck
2010-09-01 13:56 ` Jean Delvare
2010-09-01 14:32 ` Guenter Roeck
2010-09-01 14:58 ` Mahmood Naderan
2010-09-01 15:52 ` Guenter Roeck
2010-09-01 16:57 ` Mahmood Naderan
2010-09-03 14:31 ` Guenter Roeck
2010-09-04 13:49 ` Jean Delvare
2010-09-04 14:25 ` Guenter Roeck
2010-09-04 14:31 ` Mahmood Naderan
2010-09-04 15:55 ` Jean Delvare
2010-09-04 17:28 ` Guenter Roeck
2010-09-06 16:18 ` Jean Delvare
2010-09-07  1:32 ` Guenter Roeck
2010-09-07  8:00 ` Jean Delvare
2010-09-13  8:04 ` Mahmood Naderan
2010-09-14 16:20 ` Guenter Roeck

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.