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?rev=3075 > 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@xxxxxxxxxxxxxx > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
