* [lm-sensors] user question about how to load xeontemp
@ 2011-01-19 1:57 Jerry Lin
2011-01-19 2:22 ` Guenter Roeck
` (12 more replies)
0 siblings, 13 replies; 14+ messages in thread
From: Jerry Lin @ 2011-01-19 1:57 UTC (permalink / raw)
To: lm-sensors
Hi,
I have a quad-core Xeon L5630 processor on an Intel S5500HCV
motherboard that's not getting its temperature(s) detected correctly.
I've read from documentation at
http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/chips/xeontemp?rev075
and http://lm-sensors.org/wiki/Devices that I should try out the
xeontemp module. What command lines do I need to issue in order to do
that? (This is totally new to me, and I don't even have a sense of
what to put in for the BUS and ADDRESS arguments.)
Thanks,
Jerry
===========
sensors-detect outputs:
# Generated by sensors-detect on Tue Jan 18 16:57:19 2011
# Adapter drivers
i2c_i801
ipmi-si
# Chip drivers
adm1021
============
sensors output:
max1617-i2c-0-18
Adapter: SMBus I801 adapter at 2000
temp1: +0.0°C (low = +16.0°C, high = +67.0°C)
temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
max1617-i2c-0-19
Adapter: SMBus I801 adapter at 2000
temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
max1617-i2c-0-1a
Adapter: SMBus I801 adapter at 2000
temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
========
lsmod outputs:
Module Size Used by
xt_multiport 2794 1
iptable_filter 2791 1
ip_tables 18390 1 iptable_filter
x_tables 22461 2 xt_multiport,ip_tables
binfmt_misc 7960 1
ppdev 6375 0
adm1021 11699 0
ipmi_si 41129 0
ipmi_msghandler 37083 1 ipmi_si
fbcon 39270 71
tileblit 2487 1 fbcon
font 8053 1 fbcon
bitblit 5811 1 fbcon
softcursor 1565 1 bitblit
joydev 11104 0
i2c_i801 9306 0
vga16fb 12757 1
vgastate 9857 1 vga16fb
ioatdma 42737 24
lp 9336 0
parport 37160 2 ppdev,lp
usbhid 41116 0
hid 83472 1 usbhid
igb 98886 0
dca 6637 2 ioatdma,igb
=======
sensors-detect outputs:
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Intel Corporation S5520HC
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some 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):
Found `IPMI BMC KCS' at 0xca2... Success!
(confidence 8, driver `ipmisensors')
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 2000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x18
Handled by driver `adm1021' (already loaded), chip type `max1617'
Client found at address 0x19
Handled by driver `adm1021' (already loaded), chip type `max1617'
Client found at address 0x1a
Handled by driver `adm1021' (already loaded), chip type `max1617'
Client found at address 0x1b
Probing for `Maxim MAX6650/MAX6651'... No
Client found at address 0x2e
Probing for `Myson MTP008'... No
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `National Semiconductor LM85'... No
Probing for `National Semiconductor LM96000 or PC8374L'... No
Probing for `Analog Devices ADM1027'... No
Probing for `Analog Devices ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100 or EMC6D101'... No
Probing for `SMSC EMC6D102'... No
Probing for `SMSC EMC6D103'... No
Probing for `Winbond WPCD377I'... No
Probing for `Analog Devices ADT7467 or ADT7468'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Analog Devices ADT7473'... No
Probing for `Analog Devices ADT7475'... No
Probing for `Analog Devices ADT7476'... No
Probing for `Analog Devices ADT7490'... No
Probing for `Andigilog aSC7611'... No
Probing for `Andigilog aSC7621'... No
Probing for `National Semiconductor LM87'... No
Probing for `Analog Devices ADM1024'... No
Probing for `National Semiconductor LM93'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83791D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Nuvoton W83795G/ADG'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L786NR/NG/R/G'... No
Probing for `Winbond W83L785TS-S'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1026'... No
Probing for `Analog Devices ADM1025'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `Analog Devices ADM1029'... No
Probing for `Analog Devices ADM1030'... No
Probing for `Analog Devices ADM1031'... No
Probing for `Analog Devices ADM1022'... No
Probing for `Texas Instruments THMC50'... No
Probing for `Analog Devices ADM1028'... No
Probing for `Texas Instruments THMC51'... No
Probing for `ITE IT8712F'... No
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `Fintek F75373S/SG'... No
Probing for `Fintek F75375S/SP'... No
Probing for `Fintek F75387SG/RG'... No
Probing for `Winbond W83791SD'... 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'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
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 `adm1021':
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x18
Chip `max1617' (confidence: 6)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x19
Chip `max1617' (confidence: 6)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x1a
Chip `max1617' (confidence: 6)
Driver `ipmisensors':
* ISA bus, address 0xca2
Chip `IPMI BMC KCS' (confidence: 8)
Warning: the required module ipmisensors is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
i2c_i801
ipmi-si
# Chip drivers
adm1021
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
@ 2011-01-19 2:22 ` Guenter Roeck
2011-01-19 5:16 ` Jerry Lin
` (11 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Guenter Roeck @ 2011-01-19 2:22 UTC (permalink / raw)
To: lm-sensors
On Tue, Jan 18, 2011 at 08:57:30PM -0500, Jerry Lin wrote:
> Hi,
>
> I have a quad-core Xeon L5630 processor on an Intel S5500HCV
> motherboard that's not getting its temperature(s) detected correctly.
> I've read from documentation at
> http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/chips/xeontemp?rev075
> and http://lm-sensors.org/wiki/Devices that I should try out the
> xeontemp module. What command lines do I need to issue in order to do
> that? (This is totally new to me, and I don't even have a sense of
> what to put in for the BUS and ADDRESS arguments.)
>
I don't know what is wrong with the max1617 output (are you sure those sensors
are max1617 ? I suspect it may be something else), but try "modprobe coretemp".
The xeontemp module is really old, the driver is not even supported in 2.6,
and the information only applies to very old xeon chips. Modern xeon chips
have on-core temperature sensors which are supported with the coretemp module.
Guenter
> Thanks,
> Jerry
>
> ===========>
> sensors-detect outputs:
>
> # Generated by sensors-detect on Tue Jan 18 16:57:19 2011
> # Adapter drivers
> i2c_i801
> ipmi-si
> # Chip drivers
> adm1021
>
> ============
>
> sensors output:
> max1617-i2c-0-18
> Adapter: SMBus I801 adapter at 2000
> temp1: +0.0°C (low = +16.0°C, high = +67.0°C)
> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
>
> max1617-i2c-0-19
> Adapter: SMBus I801 adapter at 2000
> temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
>
> max1617-i2c-0-1a
> Adapter: SMBus I801 adapter at 2000
> temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
>
> ========>
> lsmod outputs:
>
> Module Size Used by
> xt_multiport 2794 1
> iptable_filter 2791 1
> ip_tables 18390 1 iptable_filter
> x_tables 22461 2 xt_multiport,ip_tables
> binfmt_misc 7960 1
> ppdev 6375 0
> adm1021 11699 0
> ipmi_si 41129 0
> ipmi_msghandler 37083 1 ipmi_si
> fbcon 39270 71
> tileblit 2487 1 fbcon
> font 8053 1 fbcon
> bitblit 5811 1 fbcon
> softcursor 1565 1 bitblit
> joydev 11104 0
> i2c_i801 9306 0
> vga16fb 12757 1
> vgastate 9857 1 vga16fb
> ioatdma 42737 24
> lp 9336 0
> parport 37160 2 ppdev,lp
> usbhid 41116 0
> hid 83472 1 usbhid
> igb 98886 0
> dca 6637 2 ioatdma,igb
>
> =======
>
> sensors-detect outputs:
>
> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> # System: Intel Corporation S5520HC
>
> This program will help you determine which kernel modules you need
> to load to use lm_sensors most effectively. It is generally safe
> and recommended to accept the default answers to all questions,
> unless you know what you're doing.
>
> Some south bridges, CPUs or memory controllers contain embedded sensors.
> Do you want to scan for them? This is totally safe. (YES/no):
> Silicon Integrated Systems SIS5595... No
> VIA VT82C686 Integrated Sensors... No
> VIA VT8231 Integrated Sensors... No
> AMD K8 thermal sensors... No
> AMD Family 10h thermal sensors... No
>
> AMD Family 11h thermal sensors... No
> 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):
>
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> Trying family `ITE'... No
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> Trying family `ITE'... No
>
> Some 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):
> Found `IPMI BMC KCS' at 0xca2... Success!
> (confidence 8, driver `ipmisensors')
>
> Some hardware monitoring chips are accessible through the ISA I/O ports.
> We have to write to arbitrary I/O ports to probe them. This is usually
> safe though. Yes, you do have ISA I/O ports even if you do not have any
> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
> Probing for `National Semiconductor LM78' at 0x290... No
> Probing for `National Semiconductor LM79' at 0x290... No
> Probing for `Winbond W83781D' at 0x290... No
> Probing for `Winbond W83782D' at 0x290... No
>
> Lastly, we can probe the I2C/SMBus adapters for connected hardware
> monitoring devices. This is the most risky part, and while it works
> reasonably well on most systems, it has been reported to cause trouble
> on some systems.
> Do you want to probe the I2C/SMBus adapters now? (YES/no):
> Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
> Module i2c-dev loaded successfully.
>
> Next adapter: SMBus I801 adapter at 2000 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x18
> Handled by driver `adm1021' (already loaded), chip type `max1617'
> Client found at address 0x19
> Handled by driver `adm1021' (already loaded), chip type `max1617'
> Client found at address 0x1a
> Handled by driver `adm1021' (already loaded), chip type `max1617'
> Client found at address 0x1b
> Probing for `Maxim MAX6650/MAX6651'... No
> Client found at address 0x2e
> Probing for `Myson MTP008'... No
> Probing for `National Semiconductor LM78'... No
>
> Probing for `National Semiconductor LM79'... No
> Probing for `National Semiconductor LM80'... No
> Probing for `National Semiconductor LM85'... No
> Probing for `National Semiconductor LM96000 or PC8374L'... No
> Probing for `Analog Devices ADM1027'... No
> Probing for `Analog Devices ADT7460 or ADT7463'... No
> Probing for `SMSC EMC6D100 or EMC6D101'... No
> Probing for `SMSC EMC6D102'... No
> Probing for `SMSC EMC6D103'... No
> Probing for `Winbond WPCD377I'... No
> Probing for `Analog Devices ADT7467 or ADT7468'... No
> Probing for `Analog Devices ADT7470'... No
> Probing for `Analog Devices ADT7473'... No
> Probing for `Analog Devices ADT7475'... No
> Probing for `Analog Devices ADT7476'... No
> Probing for `Analog Devices ADT7490'... No
> Probing for `Andigilog aSC7611'... No
> Probing for `Andigilog aSC7621'... No
> Probing for `National Semiconductor LM87'... No
> Probing for `Analog Devices ADM1024'... No
>
> Probing for `National Semiconductor LM93'... No
> Probing for `Winbond W83781D'... No
> Probing for `Winbond W83782D'... No
> Probing for `Winbond W83791D'... No
> Probing for `Winbond W83792D'... No
> Probing for `Winbond W83793R/G'... No
> Probing for `Nuvoton W83795G/ADG'... No
> Probing for `Winbond W83627HF'... No
> Probing for `Winbond W83627EHF'... No
> Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No
> Probing for `Asus AS99127F (rev.1)'... No
> Probing for `Asus AS99127F (rev.2)'... No
> Probing for `Asus ASB100 Bach'... No
> Probing for `Winbond W83L786NR/NG/R/G'... No
> Probing for `Winbond W83L785TS-S'... No
> Probing for `Analog Devices ADM9240'... No
> Probing for `Dallas Semiconductor DS1780'... No
> Probing for `National Semiconductor LM81'... No
> Probing for `Analog Devices ADM1026'... No
> Probing for `Analog Devices ADM1025'... No
>
> Probing for `Texas Instruments AMC6821'... No
> Probing for `Analog Devices ADM1029'... No
> Probing for `Analog Devices ADM1030'... No
> Probing for `Analog Devices ADM1031'... No
> Probing for `Analog Devices ADM1022'... No
> Probing for `Texas Instruments THMC50'... No
> Probing for `Analog Devices ADM1028'... No
> Probing for `Texas Instruments THMC51'... No
> Probing for `ITE IT8712F'... No
> Probing for `SMSC DME1737'... No
> Probing for `SMSC SCH5027D-NW'... No
> Probing for `Fintek F75373S/SG'... No
> Probing for `Fintek F75375S/SP'... No
> Probing for `Fintek F75387SG/RG'... No
> Probing for `Winbond W83791SD'... 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'... No
>
> Client found at address 0x51
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
> 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 `adm1021':
> * Bus `SMBus I801 adapter at 2000'
> Busdriver `i2c_i801', I2C address 0x18
> Chip `max1617' (confidence: 6)
>
> * Bus `SMBus I801 adapter at 2000'
> Busdriver `i2c_i801', I2C address 0x19
> Chip `max1617' (confidence: 6)
> * Bus `SMBus I801 adapter at 2000'
> Busdriver `i2c_i801', I2C address 0x1a
> Chip `max1617' (confidence: 6)
>
> Driver `ipmisensors':
> * ISA bus, address 0xca2
> Chip `IPMI BMC KCS' (confidence: 8)
>
> Warning: the required module ipmisensors is not currently installed
> on your system. If it is built into the kernel then it's OK.
> Otherwise, check http://www.lm-sensors.org/wiki/Devices for
> driver availability.
>
> To load everything that is needed, add this to /etc/modules:
> #----cut here----
> # Adapter drivers
> i2c_i801
>
> ipmi-si
> # Chip drivers
> adm1021
> #----cut here----
> If you have some drivers built into your kernel, the list above will
> contain too many modules. Skip the appropriate ones!
>
> _______________________________________________
> 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] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
2011-01-19 2:22 ` Guenter Roeck
@ 2011-01-19 5:16 ` Jerry Lin
2011-01-19 5:51 ` Guenter Roeck
` (10 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Jerry Lin @ 2011-01-19 5:16 UTC (permalink / raw)
To: lm-sensors
Thanks for the quick response. As far as I know, max1617 was suggested
by sensors-detect (or something else suggested it -- I didn't type it
in myself).
Unfortunately, "sudo modprobe coretemp" yields "FATAL: Error inserting
coretemp (/lib/modules/2.6.32-27-generic/kernel/drivers/hwmon/coretemp.ko):
No such device"
Is the coretemp module supposed to be part of lm-sensors? What's the
easiest way of getting it?
"uname -r" yields "2.6.32-27-generic"
and "lsb_release -a" yields "No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid"
Thanks,
Jerry
On Tue, Jan 18, 2011 at 6:22 PM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> On Tue, Jan 18, 2011 at 08:57:30PM -0500, Jerry Lin wrote:
>> Hi,
>>
>> I have a quad-core Xeon L5630 processor on an Intel S5500HCV
>> motherboard that's not getting its temperature(s) detected correctly.
>> I've read from documentation at
>> http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/chips/xeontemp?rev075
>> and http://lm-sensors.org/wiki/Devices that I should try out the
>> xeontemp module. What command lines do I need to issue in order to do
>> that? (This is totally new to me, and I don't even have a sense of
>> what to put in for the BUS and ADDRESS arguments.)
>>
> I don't know what is wrong with the max1617 output (are you sure those sensors
> are max1617 ? I suspect it may be something else), but try "modprobe coretemp".
>
> The xeontemp module is really old, the driver is not even supported in 2.6,
> and the information only applies to very old xeon chips. Modern xeon chips
> have on-core temperature sensors which are supported with the coretemp module.
>
> Guenter
>
>> Thanks,
>> Jerry
>>
>> ===========>>
>> sensors-detect outputs:
>>
>> # Generated by sensors-detect on Tue Jan 18 16:57:19 2011
>> # Adapter drivers
>> i2c_i801
>> ipmi-si
>> # Chip drivers
>> adm1021
>>
>> ============
>>
>> sensors output:
>> max1617-i2c-0-18
>> Adapter: SMBus I801 adapter at 2000
>> temp1: +0.0°C (low = +16.0°C, high = +67.0°C)
>> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
>>
>> max1617-i2c-0-19
>> Adapter: SMBus I801 adapter at 2000
>> temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
>> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
>>
>> max1617-i2c-0-1a
>> Adapter: SMBus I801 adapter at 2000
>> temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
>> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
>>
>> ========>>
>> lsmod outputs:
>>
>> Module Size Used by
>> xt_multiport 2794 1
>> iptable_filter 2791 1
>> ip_tables 18390 1 iptable_filter
>> x_tables 22461 2 xt_multiport,ip_tables
>> binfmt_misc 7960 1
>> ppdev 6375 0
>> adm1021 11699 0
>> ipmi_si 41129 0
>> ipmi_msghandler 37083 1 ipmi_si
>> fbcon 39270 71
>> tileblit 2487 1 fbcon
>> font 8053 1 fbcon
>> bitblit 5811 1 fbcon
>> softcursor 1565 1 bitblit
>> joydev 11104 0
>> i2c_i801 9306 0
>> vga16fb 12757 1
>> vgastate 9857 1 vga16fb
>> ioatdma 42737 24
>> lp 9336 0
>> parport 37160 2 ppdev,lp
>> usbhid 41116 0
>> hid 83472 1 usbhid
>> igb 98886 0
>> dca 6637 2 ioatdma,igb
>>
>> =======
>>
>> sensors-detect outputs:
>>
>> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>> # System: Intel Corporation S5520HC
>>
>> This program will help you determine which kernel modules you need
>> to load to use lm_sensors most effectively. It is generally safe
>> and recommended to accept the default answers to all questions,
>> unless you know what you're doing.
>>
>> Some south bridges, CPUs or memory controllers contain embedded sensors.
>> Do you want to scan for them? This is totally safe. (YES/no):
>> Silicon Integrated Systems SIS5595... No
>> VIA VT82C686 Integrated Sensors... No
>> VIA VT8231 Integrated Sensors... No
>> AMD K8 thermal sensors... No
>> AMD Family 10h thermal sensors... No
>>
>> AMD Family 11h thermal sensors... No
>> 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):
>>
>> Probing for Super-I/O at 0x2e/0x2f
>> Trying family `National Semiconductor'... No
>> Trying family `SMSC'... No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
>> Trying family `ITE'... No
>> Probing for Super-I/O at 0x4e/0x4f
>> Trying family `National Semiconductor'... No
>> Trying family `SMSC'... No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
>> Trying family `ITE'... No
>>
>> Some 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):
>> Found `IPMI BMC KCS' at 0xca2... Success!
>> (confidence 8, driver `ipmisensors')
>>
>> Some hardware monitoring chips are accessible through the ISA I/O ports.
>> We have to write to arbitrary I/O ports to probe them. This is usually
>> safe though. Yes, you do have ISA I/O ports even if you do not have any
>> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
>> Probing for `National Semiconductor LM78' at 0x290... No
>> Probing for `National Semiconductor LM79' at 0x290... No
>> Probing for `Winbond W83781D' at 0x290... No
>> Probing for `Winbond W83782D' at 0x290... No
>>
>> Lastly, we can probe the I2C/SMBus adapters for connected hardware
>> monitoring devices. This is the most risky part, and while it works
>> reasonably well on most systems, it has been reported to cause trouble
>> on some systems.
>> Do you want to probe the I2C/SMBus adapters now? (YES/no):
>> Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
>> Module i2c-dev loaded successfully.
>>
>> Next adapter: SMBus I801 adapter at 2000 (i2c-0)
>> Do you want to scan it? (YES/no/selectively):
>> Client found at address 0x18
>> Handled by driver `adm1021' (already loaded), chip type `max1617'
>> Client found at address 0x19
>> Handled by driver `adm1021' (already loaded), chip type `max1617'
>> Client found at address 0x1a
>> Handled by driver `adm1021' (already loaded), chip type `max1617'
>> Client found at address 0x1b
>> Probing for `Maxim MAX6650/MAX6651'... No
>> Client found at address 0x2e
>> Probing for `Myson MTP008'... No
>> Probing for `National Semiconductor LM78'... No
>>
>> Probing for `National Semiconductor LM79'... No
>> Probing for `National Semiconductor LM80'... No
>> Probing for `National Semiconductor LM85'... No
>> Probing for `National Semiconductor LM96000 or PC8374L'... No
>> Probing for `Analog Devices ADM1027'... No
>> Probing for `Analog Devices ADT7460 or ADT7463'... No
>> Probing for `SMSC EMC6D100 or EMC6D101'... No
>> Probing for `SMSC EMC6D102'... No
>> Probing for `SMSC EMC6D103'... No
>> Probing for `Winbond WPCD377I'... No
>> Probing for `Analog Devices ADT7467 or ADT7468'... No
>> Probing for `Analog Devices ADT7470'... No
>> Probing for `Analog Devices ADT7473'... No
>> Probing for `Analog Devices ADT7475'... No
>> Probing for `Analog Devices ADT7476'... No
>> Probing for `Analog Devices ADT7490'... No
>> Probing for `Andigilog aSC7611'... No
>> Probing for `Andigilog aSC7621'... No
>> Probing for `National Semiconductor LM87'... No
>> Probing for `Analog Devices ADM1024'... No
>>
>> Probing for `National Semiconductor LM93'... No
>> Probing for `Winbond W83781D'... No
>> Probing for `Winbond W83782D'... No
>> Probing for `Winbond W83791D'... No
>> Probing for `Winbond W83792D'... No
>> Probing for `Winbond W83793R/G'... No
>> Probing for `Nuvoton W83795G/ADG'... No
>> Probing for `Winbond W83627HF'... No
>> Probing for `Winbond W83627EHF'... No
>> Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No
>> Probing for `Asus AS99127F (rev.1)'... No
>> Probing for `Asus AS99127F (rev.2)'... No
>> Probing for `Asus ASB100 Bach'... No
>> Probing for `Winbond W83L786NR/NG/R/G'... No
>> Probing for `Winbond W83L785TS-S'... No
>> Probing for `Analog Devices ADM9240'... No
>> Probing for `Dallas Semiconductor DS1780'... No
>> Probing for `National Semiconductor LM81'... No
>> Probing for `Analog Devices ADM1026'... No
>> Probing for `Analog Devices ADM1025'... No
>>
>> Probing for `Texas Instruments AMC6821'... No
>> Probing for `Analog Devices ADM1029'... No
>> Probing for `Analog Devices ADM1030'... No
>> Probing for `Analog Devices ADM1031'... No
>> Probing for `Analog Devices ADM1022'... No
>> Probing for `Texas Instruments THMC50'... No
>> Probing for `Analog Devices ADM1028'... No
>> Probing for `Texas Instruments THMC51'... No
>> Probing for `ITE IT8712F'... No
>> Probing for `SMSC DME1737'... No
>> Probing for `SMSC SCH5027D-NW'... No
>> Probing for `Fintek F75373S/SG'... No
>> Probing for `Fintek F75375S/SP'... No
>> Probing for `Fintek F75387SG/RG'... No
>> Probing for `Winbond W83791SD'... 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'... No
>>
>> Client found at address 0x51
>> Probing for `Analog Devices ADM1033'... No
>> Probing for `Analog Devices ADM1034'... No
>> Probing for `SPD EEPROM'... No
>> 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 `adm1021':
>> * Bus `SMBus I801 adapter at 2000'
>> Busdriver `i2c_i801', I2C address 0x18
>> Chip `max1617' (confidence: 6)
>>
>> * Bus `SMBus I801 adapter at 2000'
>> Busdriver `i2c_i801', I2C address 0x19
>> Chip `max1617' (confidence: 6)
>> * Bus `SMBus I801 adapter at 2000'
>> Busdriver `i2c_i801', I2C address 0x1a
>> Chip `max1617' (confidence: 6)
>>
>> Driver `ipmisensors':
>> * ISA bus, address 0xca2
>> Chip `IPMI BMC KCS' (confidence: 8)
>>
>> Warning: the required module ipmisensors is not currently installed
>> on your system. If it is built into the kernel then it's OK.
>> Otherwise, check http://www.lm-sensors.org/wiki/Devices for
>> driver availability.
>>
>> To load everything that is needed, add this to /etc/modules:
>> #----cut here----
>> # Adapter drivers
>> i2c_i801
>>
>> ipmi-si
>> # Chip drivers
>> adm1021
>> #----cut here----
>> If you have some drivers built into your kernel, the list above will
>> contain too many modules. Skip the appropriate ones!
>>
>> _______________________________________________
>> 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] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
2011-01-19 2:22 ` Guenter Roeck
2011-01-19 5:16 ` Jerry Lin
@ 2011-01-19 5:51 ` Guenter Roeck
2011-01-19 6:29 ` Jerry Lin
` (9 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Guenter Roeck @ 2011-01-19 5:51 UTC (permalink / raw)
To: lm-sensors
On Wed, Jan 19, 2011 at 12:16:12AM -0500, Jerry Lin wrote:
Please don't top-post.
> Thanks for the quick response. As far as I know, max1617 was suggested
> by sensors-detect (or something else suggested it -- I didn't type it
> in myself).
>
S5500HCV board spec shows a TMP75 sensor. Can you try to load the lm75 module instead?
> Unfortunately, "sudo modprobe coretemp" yields "FATAL: Error inserting
> coretemp (/lib/modules/2.6.32-27-generic/kernel/drivers/hwmon/coretemp.ko):
> No such device"
>
"No such device" indicates that the driver failed to load, typically because
the core does not support built-in temperature sensors.
Odd - I thought that all recent Intel CPUs support core temperature sensors.
Looks like this one doesn't.
Guenter
> Is the coretemp module supposed to be part of lm-sensors? What's the
> easiest way of getting it?
>
> "uname -r" yields "2.6.32-27-generic"
>
> and "lsb_release -a" yields "No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 10.04.1 LTS
> Release: 10.04
> Codename: lucid"
>
> Thanks,
> Jerry
>
>
> On Tue, Jan 18, 2011 at 6:22 PM, Guenter Roeck
> <guenter.roeck@ericsson.com> wrote:
> > On Tue, Jan 18, 2011 at 08:57:30PM -0500, Jerry Lin wrote:
> >> Hi,
> >>
> >> I have a quad-core Xeon L5630 processor on an Intel S5500HCV
> >> motherboard that's not getting its temperature(s) detected correctly.
> >> I've read from documentation at
> >> http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/chips/xeontemp?rev075
> >> and http://lm-sensors.org/wiki/Devices that I should try out the
> >> xeontemp module. What command lines do I need to issue in order to do
> >> that? (This is totally new to me, and I don't even have a sense of
> >> what to put in for the BUS and ADDRESS arguments.)
> >>
> > I don't know what is wrong with the max1617 output (are you sure those sensors
> > are max1617 ? I suspect it may be something else), but try "modprobe coretemp".
> >
> > The xeontemp module is really old, the driver is not even supported in 2.6,
> > and the information only applies to very old xeon chips. Modern xeon chips
> > have on-core temperature sensors which are supported with the coretemp module.
> >
> > Guenter
> >
> >> Thanks,
> >> Jerry
> >>
> >> ===========> >>
> >> sensors-detect outputs:
> >>
> >> # Generated by sensors-detect on Tue Jan 18 16:57:19 2011
> >> # Adapter drivers
> >> i2c_i801
> >> ipmi-si
> >> # Chip drivers
> >> adm1021
> >>
> >> ============
> >>
> >> sensors output:
> >> max1617-i2c-0-18
> >> Adapter: SMBus I801 adapter at 2000
> >> temp1: +0.0°C (low = +16.0°C, high = +67.0°C)
> >> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
> >>
> >> max1617-i2c-0-19
> >> Adapter: SMBus I801 adapter at 2000
> >> temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
> >> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
> >>
> >> max1617-i2c-0-1a
> >> Adapter: SMBus I801 adapter at 2000
> >> temp1: +0.0°C (low = +16.0°C, high = +66.0°C)
> >> temp2: +4.0°C (low = +0.0°C, high = +0.0°C)
> >>
> >> ========> >>
> >> lsmod outputs:
> >>
> >> Module Size Used by
> >> xt_multiport 2794 1
> >> iptable_filter 2791 1
> >> ip_tables 18390 1 iptable_filter
> >> x_tables 22461 2 xt_multiport,ip_tables
> >> binfmt_misc 7960 1
> >> ppdev 6375 0
> >> adm1021 11699 0
> >> ipmi_si 41129 0
> >> ipmi_msghandler 37083 1 ipmi_si
> >> fbcon 39270 71
> >> tileblit 2487 1 fbcon
> >> font 8053 1 fbcon
> >> bitblit 5811 1 fbcon
> >> softcursor 1565 1 bitblit
> >> joydev 11104 0
> >> i2c_i801 9306 0
> >> vga16fb 12757 1
> >> vgastate 9857 1 vga16fb
> >> ioatdma 42737 24
> >> lp 9336 0
> >> parport 37160 2 ppdev,lp
> >> usbhid 41116 0
> >> hid 83472 1 usbhid
> >> igb 98886 0
> >> dca 6637 2 ioatdma,igb
> >>
> >> =======
> >>
> >> sensors-detect outputs:
> >>
> >> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> >> # System: Intel Corporation S5520HC
> >>
> >> This program will help you determine which kernel modules you need
> >> to load to use lm_sensors most effectively. It is generally safe
> >> and recommended to accept the default answers to all questions,
> >> unless you know what you're doing.
> >>
> >> Some south bridges, CPUs or memory controllers contain embedded sensors.
> >> Do you want to scan for them? This is totally safe. (YES/no):
> >> Silicon Integrated Systems SIS5595... No
> >> VIA VT82C686 Integrated Sensors... No
> >> VIA VT8231 Integrated Sensors... No
> >> AMD K8 thermal sensors... No
> >> AMD Family 10h thermal sensors... No
> >>
> >> AMD Family 11h thermal sensors... No
> >> 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):
> >>
> >> Probing for Super-I/O at 0x2e/0x2f
> >> Trying family `National Semiconductor'... No
> >> Trying family `SMSC'... No
> >> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> >> Trying family `ITE'... No
> >> Probing for Super-I/O at 0x4e/0x4f
> >> Trying family `National Semiconductor'... No
> >> Trying family `SMSC'... No
> >> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> >> Trying family `ITE'... No
> >>
> >> Some 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):
> >> Found `IPMI BMC KCS' at 0xca2... Success!
> >> (confidence 8, driver `ipmisensors')
> >>
> >> Some hardware monitoring chips are accessible through the ISA I/O ports.
> >> We have to write to arbitrary I/O ports to probe them. This is usually
> >> safe though. Yes, you do have ISA I/O ports even if you do not have any
> >> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
> >> Probing for `National Semiconductor LM78' at 0x290... No
> >> Probing for `National Semiconductor LM79' at 0x290... No
> >> Probing for `Winbond W83781D' at 0x290... No
> >> Probing for `Winbond W83782D' at 0x290... No
> >>
> >> Lastly, we can probe the I2C/SMBus adapters for connected hardware
> >> monitoring devices. This is the most risky part, and while it works
> >> reasonably well on most systems, it has been reported to cause trouble
> >> on some systems.
> >> Do you want to probe the I2C/SMBus adapters now? (YES/no):
> >> Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
> >> Module i2c-dev loaded successfully.
> >>
> >> Next adapter: SMBus I801 adapter at 2000 (i2c-0)
> >> Do you want to scan it? (YES/no/selectively):
> >> Client found at address 0x18
> >> Handled by driver `adm1021' (already loaded), chip type `max1617'
> >> Client found at address 0x19
> >> Handled by driver `adm1021' (already loaded), chip type `max1617'
> >> Client found at address 0x1a
> >> Handled by driver `adm1021' (already loaded), chip type `max1617'
> >> Client found at address 0x1b
> >> Probing for `Maxim MAX6650/MAX6651'... No
> >> Client found at address 0x2e
> >> Probing for `Myson MTP008'... No
> >> Probing for `National Semiconductor LM78'... No
> >>
> >> Probing for `National Semiconductor LM79'... No
> >> Probing for `National Semiconductor LM80'... No
> >> Probing for `National Semiconductor LM85'... No
> >> Probing for `National Semiconductor LM96000 or PC8374L'... No
> >> Probing for `Analog Devices ADM1027'... No
> >> Probing for `Analog Devices ADT7460 or ADT7463'... No
> >> Probing for `SMSC EMC6D100 or EMC6D101'... No
> >> Probing for `SMSC EMC6D102'... No
> >> Probing for `SMSC EMC6D103'... No
> >> Probing for `Winbond WPCD377I'... No
> >> Probing for `Analog Devices ADT7467 or ADT7468'... No
> >> Probing for `Analog Devices ADT7470'... No
> >> Probing for `Analog Devices ADT7473'... No
> >> Probing for `Analog Devices ADT7475'... No
> >> Probing for `Analog Devices ADT7476'... No
> >> Probing for `Analog Devices ADT7490'... No
> >> Probing for `Andigilog aSC7611'... No
> >> Probing for `Andigilog aSC7621'... No
> >> Probing for `National Semiconductor LM87'... No
> >> Probing for `Analog Devices ADM1024'... No
> >>
> >> Probing for `National Semiconductor LM93'... No
> >> Probing for `Winbond W83781D'... No
> >> Probing for `Winbond W83782D'... No
> >> Probing for `Winbond W83791D'... No
> >> Probing for `Winbond W83792D'... No
> >> Probing for `Winbond W83793R/G'... No
> >> Probing for `Nuvoton W83795G/ADG'... No
> >> Probing for `Winbond W83627HF'... No
> >> Probing for `Winbond W83627EHF'... No
> >> Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No
> >> Probing for `Asus AS99127F (rev.1)'... No
> >> Probing for `Asus AS99127F (rev.2)'... No
> >> Probing for `Asus ASB100 Bach'... No
> >> Probing for `Winbond W83L786NR/NG/R/G'... No
> >> Probing for `Winbond W83L785TS-S'... No
> >> Probing for `Analog Devices ADM9240'... No
> >> Probing for `Dallas Semiconductor DS1780'... No
> >> Probing for `National Semiconductor LM81'... No
> >> Probing for `Analog Devices ADM1026'... No
> >> Probing for `Analog Devices ADM1025'... No
> >>
> >> Probing for `Texas Instruments AMC6821'... No
> >> Probing for `Analog Devices ADM1029'... No
> >> Probing for `Analog Devices ADM1030'... No
> >> Probing for `Analog Devices ADM1031'... No
> >> Probing for `Analog Devices ADM1022'... No
> >> Probing for `Texas Instruments THMC50'... No
> >> Probing for `Analog Devices ADM1028'... No
> >> Probing for `Texas Instruments THMC51'... No
> >> Probing for `ITE IT8712F'... No
> >> Probing for `SMSC DME1737'... No
> >> Probing for `SMSC SCH5027D-NW'... No
> >> Probing for `Fintek F75373S/SG'... No
> >> Probing for `Fintek F75375S/SP'... No
> >> Probing for `Fintek F75387SG/RG'... No
> >> Probing for `Winbond W83791SD'... 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'... No
> >>
> >> Client found at address 0x51
> >> Probing for `Analog Devices ADM1033'... No
> >> Probing for `Analog Devices ADM1034'... No
> >> Probing for `SPD EEPROM'... No
> >> 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 `adm1021':
> >> * Bus `SMBus I801 adapter at 2000'
> >> Busdriver `i2c_i801', I2C address 0x18
> >> Chip `max1617' (confidence: 6)
> >>
> >> * Bus `SMBus I801 adapter at 2000'
> >> Busdriver `i2c_i801', I2C address 0x19
> >> Chip `max1617' (confidence: 6)
> >> * Bus `SMBus I801 adapter at 2000'
> >> Busdriver `i2c_i801', I2C address 0x1a
> >> Chip `max1617' (confidence: 6)
> >>
> >> Driver `ipmisensors':
> >> * ISA bus, address 0xca2
> >> Chip `IPMI BMC KCS' (confidence: 8)
> >>
> >> Warning: the required module ipmisensors is not currently installed
> >> on your system. If it is built into the kernel then it's OK.
> >> Otherwise, check http://www.lm-sensors.org/wiki/Devices for
> >> driver availability.
> >>
> >> To load everything that is needed, add this to /etc/modules:
> >> #----cut here----
> >> # Adapter drivers
> >> i2c_i801
> >>
> >> ipmi-si
> >> # Chip drivers
> >> adm1021
> >> #----cut here----
> >> If you have some drivers built into your kernel, the list above will
> >> contain too many modules. Skip the appropriate ones!
> >>
> >> _______________________________________________
> >> 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
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (2 preceding siblings ...)
2011-01-19 5:51 ` Guenter Roeck
@ 2011-01-19 6:29 ` Jerry Lin
2011-01-19 7:33 ` Guenter Roeck
` (8 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Jerry Lin @ 2011-01-19 6:29 UTC (permalink / raw)
To: lm-sensors
> S5500HCV board spec shows a TMP75 sensor. Can you try to load the lm75 module instead?
"sudo modprobe lm75" yields no error message, but "sudo
sensors-detect" yields the same result. ("modprobe -l | grep lm75"
yields "kernel/drivers/hwmon/lm75.ko"). I'm not totally sure that I'm
doing this correctly:
sudo modprobe lm75
[and then]
sudo sensors-detect
which yields the following output (shouldn't I see something like
"Probing for `National Semiconductor LM75' at ..."?):
"# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Intel Corporation S5520HC
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some 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):
Found `IPMI BMC KCS' at 0xca2... Success!
(confidence 8, driver `ipmisensors')
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 2000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x18
Handled by driver `adm1021' (already loaded), chip type `max1617'
Client found at address 0x19
Handled by driver `adm1021' (already loaded), chip type `max1617'
Client found at address 0x1a
Handled by driver `adm1021' (already loaded), chip type `max1617'
Client found at address 0x1b
Probing for `Maxim MAX6650/MAX6651'... No
Client found at address 0x2e
Probing for `Myson MTP008'... No
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `National Semiconductor LM85'... No
Probing for `National Semiconductor LM96000 or PC8374L'... No
Probing for `Analog Devices ADM1027'... No
Probing for `Analog Devices ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100 or EMC6D101'... No
Probing for `SMSC EMC6D102'... No
Probing for `SMSC EMC6D103'... No
Probing for `Winbond WPCD377I'... No
Probing for `Analog Devices ADT7467 or ADT7468'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Analog Devices ADT7473'... No
Probing for `Analog Devices ADT7475'... No
Probing for `Analog Devices ADT7476'... No
Probing for `Analog Devices ADT7490'... No
Probing for `Andigilog aSC7611'... No
Probing for `Andigilog aSC7621'... No
Probing for `National Semiconductor LM87'... No
Probing for `Analog Devices ADM1024'... No
Probing for `National Semiconductor LM93'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83791D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Nuvoton W83795G/ADG'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L786NR/NG/R/G'... No
Probing for `Winbond W83L785TS-S'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1026'... No
Probing for `Analog Devices ADM1025'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `Analog Devices ADM1029'... No
Probing for `Analog Devices ADM1030'... No
Probing for `Analog Devices ADM1031'... No
Probing for `Analog Devices ADM1022'... No
Probing for `Texas Instruments THMC50'... No
Probing for `Analog Devices ADM1028'... No
Probing for `Texas Instruments THMC51'... No
Probing for `ITE IT8712F'... No
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `Fintek F75373S/SG'... No
Probing for `Fintek F75375S/SP'... No
Probing for `Fintek F75387SG/RG'... No
Probing for `Winbond W83791SD'... 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'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
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 `adm1021':
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x18
Chip `max1617' (confidence: 6)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x19
Chip `max1617' (confidence: 6)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x1a
Chip `max1617' (confidence: 6)
Driver `ipmisensors':
* ISA bus, address 0xca2
Chip `IPMI BMC KCS' (confidence: 8)
Warning: the required module ipmisensors is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
i2c_i801
ipmi-si
# Chip drivers
adm1021
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!"
Thanks for your help,
Jerry
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (3 preceding siblings ...)
2011-01-19 6:29 ` Jerry Lin
@ 2011-01-19 7:33 ` Guenter Roeck
2011-01-19 8:50 ` Jean Delvare
` (7 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Guenter Roeck @ 2011-01-19 7:33 UTC (permalink / raw)
To: lm-sensors
On Wed, Jan 19, 2011 at 01:29:28AM -0500, Jerry Lin wrote:
> > S5500HCV board spec shows a TMP75 sensor. Can you try to load the lm75 module instead?
>
> "sudo modprobe lm75" yields no error message, but "sudo
> sensors-detect" yields the same result. ("modprobe -l | grep lm75"
> yields "kernel/drivers/hwmon/lm75.ko"). I'm not totally sure that I'm
> doing this correctly:
>
You would have to run "modprobe -r adm1021" first.
Anyway, the board supports DDR3, and DDR3 has JC42 compliant temperature sensors
which are usually at i2c address 0x18..0x1f. So, especially if you have four DDR3
DIMMs installed, that is probably what you have there.
Anyway, please load
http://khali.linux-fr.org/devel/misc/sensors-detect
and run it. This is the latest version of sensors-detect. It should detect
if the CPU supports sensors or not, and if the sensors at 0x18.. are jc42 sensors.
Make sure you remove the adm1021 driver before you run sensors-detect.
> sudo modprobe lm75
> [and then]
> sudo sensors-detect
>
sensors-detect can only detect a sensor if the driver for it isn't loaded yet.
Also, you might want to run "modprobe ipmi-si" as suggested by the sensors-detect
output.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (4 preceding siblings ...)
2011-01-19 7:33 ` Guenter Roeck
@ 2011-01-19 8:50 ` Jean Delvare
2011-01-19 18:52 ` Jerry Lin
` (6 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Jean Delvare @ 2011-01-19 8:50 UTC (permalink / raw)
To: lm-sensors
On Tue, 18 Jan 2011 21:51:23 -0800, Guenter Roeck wrote:
> On Wed, Jan 19, 2011 at 12:16:12AM -0500, Jerry Lin wrote:
>
> Please don't top-post.
>
> > Thanks for the quick response. As far as I know, max1617 was suggested
> > by sensors-detect (or something else suggested it -- I didn't type it
> > in myself).
This is entirely possible, the max1617 has very bad detection (no
device nor manufacturer ID) so false positives are frequent. We should
probably drop detection altogether.
> S5500HCV board spec shows a TMP75 sensor. Can you try to load the lm75 module instead?
Note that the lm75 driver only detects the original LM75 devices. Other
supported devices such as the TMP75 need to be instantiated explicitly.
> > Unfortunately, "sudo modprobe coretemp" yields "FATAL: Error inserting
> > coretemp (/lib/modules/2.6.32-27-generic/kernel/drivers/hwmon/coretemp.ko):
> > No such device"
> >
> "No such device" indicates that the driver failed to load, typically because
> the core does not support built-in temperature sensors.
> Odd - I thought that all recent Intel CPUs support core temperature sensors.
> Looks like this one doesn't.
Universal detection was only added to the coretemp driver in kernel
2.6.35, while Jerry runs kernel 2.6.32.
Jerry, please try the stand-alone coretemp driver at:
http://khali.linux-fr.org/devel/misc/coretemp/
This is basically the version from the latest kernel, with some
compatibility bits added so that it builds and runs on older kernels
too.
Installation instructions can be downloaded from:
http://khali.linux-fr.org/devel/misc/INSTALL
This is a document I just wrote, let me know if it contains errors or
can be improved in any way.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (5 preceding siblings ...)
2011-01-19 8:50 ` Jean Delvare
@ 2011-01-19 18:52 ` Jerry Lin
2011-01-19 19:09 ` Guenter Roeck
` (5 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Jerry Lin @ 2011-01-19 18:52 UTC (permalink / raw)
To: lm-sensors
On Tue, Jan 18, 2011 at 11:33 PM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> On Wed, Jan 19, 2011 at 01:29:28AM -0500, Jerry Lin wrote:
>> > S5500HCV board spec shows a TMP75 sensor. Can you try to load the lm75 module instead?
>>
>> "sudo modprobe lm75" yields no error message, but "sudo
>> sensors-detect" yields the same result. ("modprobe -l | grep lm75"
>> yields "kernel/drivers/hwmon/lm75.ko"). I'm not totally sure that I'm
>> doing this correctly:
>>
> You would have to run "modprobe -r adm1021" first.
>
> Anyway, the board supports DDR3, and DDR3 has JC42 compliant temperature sensors
> which are usually at i2c address 0x18..0x1f. So, especially if you have four DDR3
> DIMMs installed, that is probably what you have there.
>
> Anyway, please load
> http://khali.linux-fr.org/devel/misc/sensors-detect
> and run it. This is the latest version of sensors-detect. It should detect
> if the CPU supports sensors or not, and if the sensors at 0x18.. are jc42 sensors.
> Make sure you remove the adm1021 driver before you run sensors-detect.
"sudo modprobe -r adm1021" yields no error message, and then
"sudo perl sensors-detect" yields a more promising result (I think the
detection worked correctly), but I think I'm missing drivers. First,
the output for sensors-detect:
"# sensors-detect revision 5904 (2011-01-18 18:20:42 +0100)
# System: Intel Corporation S5520HC
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some 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):
Found `IPMI BMC KCS' at 0xca2... Success!
(confidence 8, driver `ipmisensors')
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 2000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x18
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... Success!
(confidence 3, driver `adm1021')
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 MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `National Semiconductor LM64'... No
Probing for `SMSC EMC1403'... No
Probing for `SMSC EMC1404'... No
Probing for `SMSC EMC1423'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... Success!
(confidence 5, driver `jc42')
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x19
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... Success!
(confidence 3, driver `adm1021')
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 MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `National Semiconductor LM95231'... No
Probing for `National Semiconductor LM95241'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... Success!
(confidence 5, driver `jc42')
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x1a
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... Success!
(confidence 3, driver `adm1021')
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 MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... Success!
(confidence 5, driver `jc42')
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x1b
Probing for `Maxim MAX6650/MAX6651'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... Success!
(confidence 5, driver `jc42')
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x1c
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... Success!
(confidence 5, driver `jc42')
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x1d
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... Success!
(confidence 5, driver `jc42')
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x2e
Probing for `Myson MTP008'... No
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `National Semiconductor LM85'... No
Probing for `National Semiconductor LM96000 or PC8374L'... No
Probing for `Analog Devices ADM1027'... No
Probing for `Analog Devices ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100 or EMC6D101'... No
Probing for `SMSC EMC6D102'... No
Probing for `SMSC EMC6D103'... No
Probing for `Winbond WPCD377I'... No
Probing for `Analog Devices ADT7467 or ADT7468'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Analog Devices ADT7473'... No
Probing for `Analog Devices ADT7475'... No
Probing for `Analog Devices ADT7476'... No
Probing for `Analog Devices ADT7490'... No
Probing for `Andigilog aSC7611'... No
Probing for `Andigilog aSC7621'... No
Probing for `National Semiconductor LM87'... No
Probing for `Analog Devices ADM1024'... No
Probing for `National Semiconductor LM93'... No
Probing for `National Semiconductor LM94'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83791D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Nuvoton W83795G/ADG'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L786NR/NG/R/G'... No
Probing for `Winbond W83L785TS-S'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1026'... No
Probing for `Analog Devices ADM1025'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `Analog Devices ADM1029'... No
Probing for `Analog Devices ADM1030'... No
Probing for `Analog Devices ADM1031'... No
Probing for `Analog Devices ADM1022'... No
Probing for `Texas Instruments THMC50'... No
Probing for `Analog Devices ADM1028'... No
Probing for `Texas Instruments THMC51'... No
Probing for `ITE IT8712F'... No
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `SMSC EMC2103'... No
Probing for `Fintek F75373S/SG'... No
Probing for `Fintek F75375S/SP'... No
Probing for `Fintek F75387SG/RG'... No
Probing for `Winbond W83791SD'... 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'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
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 `jc42':
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x18
Chip `ST STTS424E' (confidence: 5)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x19
Chip `ST STTS424E' (confidence: 5)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x1a
Chip `ST STTS424E' (confidence: 5)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x1b
Chip `ST STTS424E' (confidence: 5)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x1c
Chip `ST STTS424E' (confidence: 5)
* Bus `SMBus I801 adapter at 2000'
Busdriver `i2c_i801', I2C address 0x1d
Chip `ST STTS424E' (confidence: 5)
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Driver `ipmisensors':
* ISA bus, address 0xca2
Chip `IPMI BMC KCS' (confidence: 8)
Warning: the required module jc42 is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.
Warning: the required module ipmisensors is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
Unloading cpuid... OK"
To test the result, "sensors" yields:
"No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are."
"sudo modprobe ipmi-si" yields no errors.
"sudo modprobe coretemp" yields
"FATAL: Error inserting coretemp
(/lib/modules/2.6.32-27-generic/kernel/drivers/hwmon/coretemp.ko): No
such device"
"sudo modprobe jc42" yields
"FATAL: Module jc42 not found."
Questions:
1) What's the name of the jc42 module that I would need to load via modprobe?
2a) sensors-detect mentions copying from "prog/init/lm_sensors.init"
-- where is that prog directory?
2b) Does doing that copy of lm_sensors.init take the place of
copying-and-pasting the module lines into the /etc/modules file in the
older version of the script?
3) Is "ipmisensors" the same as "ipmi-si" (as in "modprobe ipmi-si")?
4) Why is sensors-detect able to detect the sensor via the coretemp
driver, but modprobe not able to load it?
5) Is there something else that I should be doing?
In regards to Jean's response:
> Jerry, please try the stand-alone coretemp driver at:
> http://khali.linux-fr.org/devel/misc/coretemp/
> This is basically the version from the latest kernel, with some
> compatibility bits added so that it builds and runs on older kernels
> too.
>
> Installation instructions can be downloaded from:
> http://khali.linux-fr.org/devel/misc/INSTALL
> This is a document I just wrote, let me know if it contains errors or
> can be improved in any way.
Thanks for your instructions. I was able to follow your instructions
until the make step, at which point I got:
"Makefile:37: warning: overriding commands for target `modules_install'
Makefile:29: warning: ignoring old commands for target `modules_install'
/home/jerry/coretemp/Makefile:37: warning: overriding commands for
target `modules_install'
/home/jerry/coretemp/Makefile:29: warning: ignoring old commands for
target `modules_install'
CC [M] /home/jerry/coretemp/coretemp.o
/home/jerry/coretemp/coretemp.c:572: warning: data definition has no
type or storage class
/home/jerry/coretemp/coretemp.c:572: warning: type defaults to â in
declaration of â
/home/jerry/coretemp/coretemp.c:573: error: expected identifier or â
before â token
/home/jerry/coretemp/coretemp.c:574:2: error: #endif without #if
/home/jerry/coretemp/coretemp.c:576: error: expected declaration
specifiers or â before â token
/home/jerry/coretemp/coretemp.c:576: warning: data definition has no
type or storage class
/home/jerry/coretemp/coretemp.c:576: warning: type defaults to â in
declaration of â
/home/jerry/coretemp/coretemp.c:576: warning: function declaration
isnât a prototype
/home/jerry/coretemp/coretemp.c:577: error: expected identifier or â before â
/home/jerry/coretemp/coretemp.c:583: error: expected â, â, â, â or â
before â token
/home/jerry/coretemp/coretemp.c:585: error: expected identifier or â
before â token
/home/jerry/coretemp/coretemp.c:587: error: redefinition of â
/home/jerry/coretemp/coretemp.c:550: note: previous definition of â was here
/home/jerry/coretemp/coretemp.c:606: error: redefinition of â
/home/jerry/coretemp/coretemp.c:570: note: previous definition of â was here
/home/jerry/coretemp/coretemp.c:606: error: redefinition of â
/home/jerry/coretemp/coretemp.c:570: note: previous definition of â was here
/home/jerry/coretemp/coretemp.c:607: error: redefinition of â
/home/jerry/coretemp/coretemp.c:571: note: previous definition of â was here
/home/jerry/coretemp/coretemp.c:607: error: redefinition of â
/home/jerry/coretemp/coretemp.c:571: note: previous definition of â was here
make[2]: *** [/home/jerry/coretemp/coretemp.o] Error 1
make[1]: *** [_module_/home/jerry/coretemp] Error 2
make: *** [modules] Error 2"
When I view the source via less, I don't see the "â" characters (I
retrieved the source via wget).
"gcc -v" yields
"Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
4.4.3-4ubuntu5'
--with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--enable-shared --enable-multiarch --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4
--program-suffix=-4.4 --enable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-plugin --enable-objc-gc
--disable-werror --with-arch-32=i486 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) "
"make -v" yields
"GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for x86_64-pc-linux-gnu"
Questions:
1) Is there something I should do differently to get the module compiled?
2) If I upgraded the kernel to 2.6.35, would most of my problems go
away? (I can't easily do that right now because the machines are in
use, but I can try to do that at the next maintenance window.)
Thanks for your help!
Jerry
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (6 preceding siblings ...)
2011-01-19 18:52 ` Jerry Lin
@ 2011-01-19 19:09 ` Guenter Roeck
2011-01-21 17:07 ` Jerry Lin
` (4 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Guenter Roeck @ 2011-01-19 19:09 UTC (permalink / raw)
To: lm-sensors
On Wed, 2011-01-19 at 13:52 -0500, Jerry Lin wrote:
[ ... ]
> Questions:
> 1) What's the name of the jc42 module that I would need to load via modprobe?
jc42. Problem is that support for it was added in a later version of the
kernel.
> 2a) sensors-detect mentions copying from "prog/init/lm_sensors.init"
> -- where is that prog directory?
> 2b) Does doing that copy of lm_sensors.init take the place of
> copying-and-pasting the module lines into the /etc/modules file in the
> older version of the script?
> 3) Is "ipmisensors" the same as "ipmi-si" (as in "modprobe ipmi-si")?
I don't know the status of ipmi integration and ipmi module names. There
is the OpenIPMI project, and they have lots of patches to improve ipmi
support. Jean may know better than me if/when/how those patches will be
integrated into the mainline kernel.
> 4) Why is sensors-detect able to detect the sensor via the coretemp
> driver, but modprobe not able to load it?
Because your version of the coretemp driver is old and doesn't support
your CPU.
> 5) Is there something else that I should be doing?
>
Easiest would be if you could switch to a recent kernel (2.6.37 or at
least 2.6.36). Otherwise you'll have to backport the coretemp driver (as
Jean has tried) as well as the jc42 driver.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (7 preceding siblings ...)
2011-01-19 19:09 ` Guenter Roeck
@ 2011-01-21 17:07 ` Jerry Lin
2011-01-22 17:56 ` Jean Delvare
` (3 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Jerry Lin @ 2011-01-21 17:07 UTC (permalink / raw)
To: lm-sensors
Hi all,
I upgraded the kernel to 2.6.35 (which corresponds to Ubuntu 10.10),
and I can now get the temperature readings from the Xeon cores. (I
still needed to load the coretemp module, but I think that was because
the /etc/modules file was not configured properly.)
In any case, thanks a lot for your help -- I got much faster responses
from this list than I expected.
This project was tremendously helpful in confirming that there was a
hardware problem with the CPU overheating (my mistake in assembling
the components). Thanks for working on it!
Best,
Jerry
On Wed, Jan 19, 2011 at 11:09 AM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> On Wed, 2011-01-19 at 13:52 -0500, Jerry Lin wrote:
> [ ... ]
>
>> Questions:
>> 1) What's the name of the jc42 module that I would need to load via modprobe?
>
> jc42. Problem is that support for it was added in a later version of the
> kernel.
>
>> 2a) sensors-detect mentions copying from "prog/init/lm_sensors.init"
>> -- where is that prog directory?
>> 2b) Does doing that copy of lm_sensors.init take the place of
>> copying-and-pasting the module lines into the /etc/modules file in the
>> older version of the script?
>> 3) Is "ipmisensors" the same as "ipmi-si" (as in "modprobe ipmi-si")?
>
> I don't know the status of ipmi integration and ipmi module names. There
> is the OpenIPMI project, and they have lots of patches to improve ipmi
> support. Jean may know better than me if/when/how those patches will be
> integrated into the mainline kernel.
>
>> 4) Why is sensors-detect able to detect the sensor via the coretemp
>> driver, but modprobe not able to load it?
>
> Because your version of the coretemp driver is old and doesn't support
> your CPU.
>
>> 5) Is there something else that I should be doing?
>>
> Easiest would be if you could switch to a recent kernel (2.6.37 or at
> least 2.6.36). Otherwise you'll have to backport the coretemp driver (as
> Jean has tried) as well as the jc42 driver.
>
> Guenter
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (8 preceding siblings ...)
2011-01-21 17:07 ` Jerry Lin
@ 2011-01-22 17:56 ` Jean Delvare
2011-01-22 19:04 ` Jean Delvare
` (2 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: Jean Delvare @ 2011-01-22 17:56 UTC (permalink / raw)
To: lm-sensors
Hi Jerry,
On Wed, 19 Jan 2011 10:52:04 -0800, Jerry Lin wrote:
> > Jerry, please try the stand-alone coretemp driver at:
> > http://khali.linux-fr.org/devel/misc/coretemp/
> > This is basically the version from the latest kernel, with some
> > compatibility bits added so that it builds and runs on older kernels
> > too.
> >
> > Installation instructions can be downloaded from:
> > http://khali.linux-fr.org/devel/misc/INSTALL
> > This is a document I just wrote, let me know if it contains errors or
> > can be improved in any way.
>
> Thanks for your instructions. I was able to follow your instructions
> until the make step, at which point I got:
>
> "Makefile:37: warning: overriding commands for target `modules_install'
> Makefile:29: warning: ignoring old commands for target `modules_install'
> /home/jerry/coretemp/Makefile:37: warning: overriding commands for
> target `modules_install'
> /home/jerry/coretemp/Makefile:29: warning: ignoring old commands for
> target `modules_install'
> CC [M] /home/jerry/coretemp/coretemp.o
> /home/jerry/coretemp/coretemp.c:572: warning: data definition has no
> type or storage class
> /home/jerry/coretemp/coretemp.c:572: warning: type defaults to â in
> declaration of â
> /home/jerry/coretemp/coretemp.c:573: error: expected identifier or â
> before â token
> /home/jerry/coretemp/coretemp.c:574:2: error: #endif without #if
> /home/jerry/coretemp/coretemp.c:576: error: expected declaration
> specifiers or â before â token
> /home/jerry/coretemp/coretemp.c:576: warning: data definition has no
> type or storage class
> /home/jerry/coretemp/coretemp.c:576: warning: type defaults to â in
> declaration of â
>
> /home/jerry/coretemp/coretemp.c:576: warning: function declaration
> isnât a prototype
> /home/jerry/coretemp/coretemp.c:577: error: expected identifier or â before â
> /home/jerry/coretemp/coretemp.c:583: error: expected â, â, â, â or â
> before â token
> /home/jerry/coretemp/coretemp.c:585: error: expected identifier or â
> before â token
> /home/jerry/coretemp/coretemp.c:587: error: redefinition of â
> /home/jerry/coretemp/coretemp.c:550: note: previous definition of â was here
> /home/jerry/coretemp/coretemp.c:606: error: redefinition of â
> /home/jerry/coretemp/coretemp.c:570: note: previous definition of â was here
> /home/jerry/coretemp/coretemp.c:606: error: redefinition of â
> /home/jerry/coretemp/coretemp.c:570: note: previous definition of â was here
> /home/jerry/coretemp/coretemp.c:607: error: redefinition of â
> /home/jerry/coretemp/coretemp.c:571: note: previous definition of â was here
> /home/jerry/coretemp/coretemp.c:607: error: redefinition of â
> /home/jerry/coretemp/coretemp.c:571: note: previous definition of â was here
> make[2]: *** [/home/jerry/coretemp/coretemp.o] Error 1
> make[1]: *** [_module_/home/jerry/coretemp] Error 2
> make: *** [modules] Error 2"
>
> When I view the source via less, I don't see the "â" characters (I
> retrieved the source via wget).
There was apparently a data corruption, either over the network or on
the disk. I've uploaded the files again, they seem to have been
transferred properly this time, so please download them and try again.
> Questions:
> 1) Is there something I should do differently to get the module compiled?
No, you did the right thing but the source files were corrupted.
> 2) If I upgraded the kernel to 2.6.35, would most of my problems go
> away? (I can't easily do that right now because the machines are in
> use, but I can try to do that at the next maintenance window.)
Yes, it would help for the coretemp driver, which would work out of the
box. The jc42 driver only made it into kernel 2.6.36 though, so you
would still have to build that one out-of-tree. So overall I don't
think it's worth it.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (9 preceding siblings ...)
2011-01-22 17:56 ` Jean Delvare
@ 2011-01-22 19:04 ` Jean Delvare
2011-01-22 20:39 ` Guenter Roeck
2011-01-23 9:04 ` Jean Delvare
12 siblings, 0 replies; 14+ messages in thread
From: Jean Delvare @ 2011-01-22 19:04 UTC (permalink / raw)
To: lm-sensors
On Wed, 19 Jan 2011 11:09:51 -0800, Guenter Roeck wrote:
> On Wed, 2011-01-19 at 13:52 -0500, Jerry Lin wrote:
> [ ... ]
>
> > Questions:
> > 1) What's the name of the jc42 module that I would need to load via modprobe?
>
> jc42. Problem is that support for it was added in a later version of the
> kernel.
>
> > 2a) sensors-detect mentions copying from "prog/init/lm_sensors.init"
> > -- where is that prog directory?
> > 2b) Does doing that copy of lm_sensors.init take the place of
> > copying-and-pasting the module lines into the /etc/modules file in the
> > older version of the script?
> > 3) Is "ipmisensors" the same as "ipmi-si" (as in "modprobe ipmi-si")?
>
> I don't know the status of ipmi integration and ipmi module names. There
> is the OpenIPMI project, and they have lots of patches to improve ipmi
> support. Jean may know better than me if/when/how those patches will be
> integrated into the mainline kernel.
The impisensor driver is abandoned for years. I won't look into it as I
have many other drivers to work on and I don't have supported hardware.
In the meantime, my recommendation is to use ipmitool. It is _not_
integrated with libsensors, but other than that, it should report the
sensor values properly.
> > 4) Why is sensors-detect able to detect the sensor via the coretemp
> > driver, but modprobe not able to load it?
>
> Because your version of the coretemp driver is old and doesn't support
> your CPU.
>
> > 5) Is there something else that I should be doing?
> >
> Easiest would be if you could switch to a recent kernel (2.6.37 or at
> least 2.6.36). Otherwise you'll have to backport the coretemp driver (as
> Jean has tried) as well as the jc42 driver.
I already have it ready:
http://khali.linux-fr.org/devel/misc/jc42/
--
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] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (10 preceding siblings ...)
2011-01-22 19:04 ` Jean Delvare
@ 2011-01-22 20:39 ` Guenter Roeck
2011-01-23 9:04 ` Jean Delvare
12 siblings, 0 replies; 14+ messages in thread
From: Guenter Roeck @ 2011-01-22 20:39 UTC (permalink / raw)
To: lm-sensors
On Sat, Jan 22, 2011 at 02:04:21PM -0500, Jean Delvare wrote:
[ ... ]
> >
> > I don't know the status of ipmi integration and ipmi module names. There
> > is the OpenIPMI project, and they have lots of patches to improve ipmi
> > support. Jean may know better than me if/when/how those patches will be
> > integrated into the mainline kernel.
>
> The impisensor driver is abandoned for years. I won't look into it as I
> have many other drivers to work on and I don't have supported hardware.
>
> In the meantime, my recommendation is to use ipmitool. It is _not_
> integrated with libsensors, but other than that, it should report the
> sensor values properly.
>
How about OpenIPMI ? Any plans to integrate that code into the mainline,
or is that pretty much a parallel effort ?
Just trying to get an idea where IPMI kernel support is going. Looks like IPMI
is going to be used in a project here, so we may have to support it.
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] 14+ messages in thread
* Re: [lm-sensors] user question about how to load xeontemp
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
` (11 preceding siblings ...)
2011-01-22 20:39 ` Guenter Roeck
@ 2011-01-23 9:04 ` Jean Delvare
12 siblings, 0 replies; 14+ messages in thread
From: Jean Delvare @ 2011-01-23 9:04 UTC (permalink / raw)
To: lm-sensors
On Sat, 22 Jan 2011 12:39:33 -0800, Guenter Roeck wrote:
> On Sat, Jan 22, 2011 at 02:04:21PM -0500, Jean Delvare wrote:
> [ ... ]
> > >
> > > I don't know the status of ipmi integration and ipmi module names. There
> > > is the OpenIPMI project, and they have lots of patches to improve ipmi
> > > support. Jean may know better than me if/when/how those patches will be
> > > integrated into the mainline kernel.
> >
> > The impisensor driver is abandoned for years. I won't look into it as I
> > have many other drivers to work on and I don't have supported hardware.
> >
> > In the meantime, my recommendation is to use ipmitool. It is _not_
> > integrated with libsensors, but other than that, it should report the
> > sensor values properly.
> >
> How about OpenIPMI ? Any plans to integrate that code into the mainline,
> or is that pretty much a parallel effort ?
>
> Just trying to get an idea where IPMI kernel support is going. Looks like IPMI
> is going to be used in a project here, so we may have to support it.
I have no idea, 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] 14+ messages in thread
end of thread, other threads:[~2011-01-23 9:04 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-19 1:57 [lm-sensors] user question about how to load xeontemp Jerry Lin
2011-01-19 2:22 ` Guenter Roeck
2011-01-19 5:16 ` Jerry Lin
2011-01-19 5:51 ` Guenter Roeck
2011-01-19 6:29 ` Jerry Lin
2011-01-19 7:33 ` Guenter Roeck
2011-01-19 8:50 ` Jean Delvare
2011-01-19 18:52 ` Jerry Lin
2011-01-19 19:09 ` Guenter Roeck
2011-01-21 17:07 ` Jerry Lin
2011-01-22 17:56 ` Jean Delvare
2011-01-22 19:04 ` Jean Delvare
2011-01-22 20:39 ` Guenter Roeck
2011-01-23 9:04 ` Jean Delvare
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.