{5} Assigned, Active Tickets by Owner (Full Description) (21 matches)

Many linux 2.6 hwmon drivers still don't create the individual alarm files libsensors4 needs. This will cause a regression when users upgrade to lm-sensors 3. All the drivers that are still missing the individual alarm files need to be updated.

On my system running linux 2.6.24-11 on an Asus A8V-E SE motherboard with a w83627ehf sensor chip, I see "hwmon1/device/pwmN stuck to 0" for N=1 to 3 when I run pwmconfig from lm_sensors-3.0.1. However, I have no problem setting /sys/class/hwmon/hwmon1/device/pwm1 to any value from 0 to 255 using echo and it stays there.

Even stranger, adding a single echo command to the pwmdisable function in the pwmconfig script causes it to work correctly. It does not seem to be a timing problem, since replacing the echo with "sleep 1" doesn't have the same effect. Adding the single echo to the fancontrol script's pwmdisable function allows it to reset the fan to full speed when it is killed.

I have no idea what is causing this problem or why adding a single echo to the script fixes it. I'm not even sure if it should be considered a bug in the scripts, the kernel driver, or what. I only discovered the fix because I added an echo line for debugging.

Most (all?) of the ADM and ADT series of chips by Analog Devices have been sold to ON Semiconductor. We need to update wiki/Devices to mention that change and to link to the right pages on the www.onsemi.com website.

Additionally, references in the driver code and documentation should be updated as well.

Sensors are detected and working, pwmconfig run (with some help), but fancontrol gives error and does not work on my Sun Ultra 20 Workstation. Main board is Tyan Tomcat K8e, S2865 (this Sun version is called S2864). Its told this board has a DME1737 chip. OS is FC5, kernel 2.17, with NVidia kernel module.

pwmconfig is able to control the fans (the one PWM-capable I have), however it gives the same Access Denied messages meanwhile that fancontrol does.

Thanks In Advance!

-- begin fancontrol output -- Loading configuration from /etc/fancontrol ...

Common settings:

INTERVAL=10

Settings for 0-002e/pwm3:

Depends on 0-002e/temp1_input Controls 0-002e/fan3_input MINTEMP=33 MAXTEMP=55 MINSTART=25 MINSTOP=25

Enabling PWM on fans... /usr/sbin/fancontrol: line 142: 0-002e/pwm3_enable: Permission denied Error enabling PWM on /sys/bus/i2c/devices/0-002e/pwm3 Aborting, restoring fans... /usr/sbin/fancontrol: line 127: 0-002e/pwm3_enable: Permission denied Verify fans have returned to full speed -- end fancontrol output -- -- begin sensors-detect output -- emc6d100-i2c-0-2e Adapter: SMBus nForce2 adapter at 1c00

Dimm Volt: +2.60 V (min = +0.00 V, max = +6.64 V) CPU Volt: +1.22 V (min = +0.00 V, max = +2.99 V) +3.3V: +3.35 V (min = +0.00 V, max = +4.38 V) +5V: +5.00 V (min = +0.00 V, max = +6.64 V) +12V: +12.12 V (min = +0.00 V, max = +15.94 V) ERROR: Can't get IN5 data! ERROR: Can't get IN6 data! ERROR: Can't get IN7 data! CPU Fan: 2588 RPM (min = 0 RPM) Fan3: 0 RPM (min = 0 RPM) Rear Case Fan:

2971 RPM (min = 0 RPM)

Front Case Fan:

1000 RPM (min = 0 RPM)

CPU Temp: +26°C (low = -127°C, high = +127°C) temp2: +29°C (low = -127°C, high = +127°C) System Temp:

+27°C (low = -127°C, high = +127°C)

vid: +1.550 V (VRM Version 2.4) -- end sensors-detect output -- -- begin modules.conf -- alias char-major-89 i2c-dev -- end modules.conf -- -- begin rc.local -- modprobe i2c-nforce2 modprobe lm85 force_emc6d100=0,0x2e modprobe eeprom sensors -s -- end rc.local -- -- begin sensors.conf -- chip "lm85c-*" "adm1027-*" "adt7463-*" "lm85-*" "lm85b-*"

set temp1_max 50

# Voltage inputs

label in0 "V1.5" # AGP on Intel S845WD1-E label in1 "VCore" label in2 "V3.3" label in3 "V5" label in4 "V12"

# Temperature inputs

label temp1 "CPU" label temp2 "Board" label temp3 "Remote"

# Fan inputs

label fan1 "CPU_Fan"

# label fan2 "Fan2" # label fan3 "Fan3" # label fan4 "Fan4"

# PWM Outputs

label pwm1 "CPU_PWM" label pwm2 "Fan2_PWM" label pwm3 "Fan3_PWM"

# Voltage scaling is done on-chip. No 'compute' directive # should be necessary. If in0 has external scaling set # it here.

# compute in0 @ * 2.5, @ / 2.5

# Adjust fans speeds for actual pulses per rev # compute fan1 @ * 2, @ / 2 # 1 pulse per rev # set fan1_ppr 1 # ADM1027 or ADT7463 # compute fan2 @ / 2, @ * 2 # 4 pulse per rev # set fan2_ppr 4 # ADM1027 or ADT7463

# Ignore fans you (or your motherboard) don't have # ignore fan2 # ignore fan3 # ignore fan4

# Set VRM version # adjust this if your vid is wrong; see doc/vid # set vrm 9.1 # Pentium 4

# Set voltage limits

set in0_min 1.5 * 0.95 set in0_max 1.5 * 1.05 set in1_min vid * 0.95 set in1_max vid * 1.05 set in2_min 3.3 * 0.95 set in2_max 3.3 * 1.05 set in3_min 5.0 * 0.95 set in3_max 5.0 * 1.05 set in4_min 12 * 0.95 set in4_max 12 * 1.05

# Set Fan limits

set fan1_min 4000

# Set Temp Limits

set temp1_min 10 set temp1_max 50 set temp2_min 10 set temp2_max 35 set temp3_min 10 set temp3_max 35

chip "emc6d100-*"

ignore pwm1 ignore pwm2 ignore pwm3 ignore in5 ignore in6 ignore in7

# ignore temp2

label in0 "Dimm Volt" label in1 "CPU Volt" label in2 "+3.3V" label in3 "+5V" label in4 "+12V"

label fan1 "CPU Fan" label fan2 "Fan3" label fan4 "Front Case Fan" label fan3 "Rear Case Fan"

label temp1 "CPU Temp" label temp3 "System Temp"

set temp1_max 55

compute in0 2*@, @/2

set in0_min 2.6 * 0.95 set in0_max 2.6 * 1.05 set in1_min 1.35 * 0.95 set in1_max 1.35 * 1.05 set in2_min 3.3 * 0.95 set in2_max 3.3 * 1.05 set in3_min 5.0 * 0.95 set in3_max 5.0 * 1.05 set in4_min 12.0 * 0.95 set in4_max 12.0 * 1.05

set vrm 9.1

-- end sensors.conf --

I have a new Asus DSBF mobo which includes both motherboard sensors AND memory (FB-DIMM) sensors. I downloaded the latest lm_sensors but can't detect the hardware sensors. (The output of sensors-detect is below).

Has anyone been able to get lm_sensors working on this mobo? Can anyone offer advice?

Thanks, MD

----------------------------------------------------------------

'''[root@vmhost1 src]# sensors-detect
# sensors-detect revision 1.413 (2006/01/19 20:28:00)

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

 We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no): 
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel Enterprise Southbridge - ESB2
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
 i2c-dev is not loaded. Do you want to load it now? (YES/no): 
 Module loaded succesfully.

 We are now going to do the adapter probings. Some adapters may hang halfway
 through; we can't really help that. Also, some chips will be double detected;
 we choose the one with the highest confidence value in that case.
 If you found that the adapter hung after probing a certain address, you can
 specify that address to remain unprobed. That often
 includes address 0x69 (clock chip).

Next adapter: SMBus I801 adapter at 1100
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x08
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8712F'... Failed!
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4b
Probing for `National Semiconductor LM75'... Failed!
Probing for `National Semiconductor LM77'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Probing for `National Semiconductor LM92'... Failed!
Probing for `National Semiconductor LM76'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4f
Probing for `National Semiconductor LM75'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x54
Probing for `SPD EEPROM'... Success!
    (confidence 1, driver `eeprom')
Client found at address 0x55
Probing for `SPD EEPROM'... Success!
    (confidence 1, driver `eeprom')
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
    (confidence 1, driver `smbus-arp')
Client found at address 0x71

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): 
Probing for `National Semiconductor LM78'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
  Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
  Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
  Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
  Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8712F'
  Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
  Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
  Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
  Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): 
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83627HF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83627THF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83687THF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83697SF/UF Super IO PWM'
  Failed! (0x88)
Probing for `Winbond W83L517D Super IO'
  Failed! (0x88)
Probing for `Fintek F71805F/FG Super IO Sensors'
  Failed! (0x8863)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Success... but not activated

Do you want to scan for secondary Super I/O sensors? (YES/no): 
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Failed! (skipping family)

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

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 1100'
    Busdriver `i2c-i801', I2C address 0x54
    Chip `SPD EEPROM' (confidence: 1)
  * Bus `SMBus I801 adapter at 1100'
    Busdriver `i2c-i801', I2C address 0x55
    Chip `SPD EEPROM' (confidence: 1)

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


I will now generate the commands needed to load the I2C modules.

To make the sensors modules behave correctly, add these lines to
/etc/modprobe.conf:

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

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

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

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): 
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
[root@vmhost1 src]'''

I see from the Wiki that you're looking for users to test Phenom (K10) support. I have a system based on an Asus M3A32-MVP motherboard with an AMD Phenom 9600 processor. I'm currently running Ubuntu 7.10. I can rebuild a custom kernel and do basic debugging if it will help.

Currently, the fan runs full speed unless toggled back with "fancontrol". I'm looking for a more integrated solution.

Hi

on my Laptop (Suse 10.2) sensors-detect (2.10.1 RPM and latest trunk) tells me:

 perl "sensors-detect?format=txt"
# sensors-detect revision $Revision$

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.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no): y
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-3)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x4c
Probing for `National Semiconductor LM75'...                No
Probing for `Analog Devices ADT7466'...                     No
Probing for `Andigilog aSC7511'...                          No
Probing for `Dallas Semiconductor DS1621'...                No
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 `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `National Semiconductor LM90'...                No
Probing for `National Semiconductor LM89/LM99'...           No
Probing for `National Semiconductor LM86'...                No
Probing for `Analog Devices ADM1032'...                     No
Probing for `Maxim MAX6657/MAX6658/MAX6659'...              No
Probing for `Maxim MAX6648/MAX6692'...                      Success!
    (confidence 8, driver `to-be-written')
Probing for `National Semiconductor LM63'...                No
Probing for `Fintek F75363SG'...                            No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `Analog Devices ADT7461'...                     No
Probing for `Fintek F75383S/M'...                           No
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'

Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-2)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-1)
Do you want to scan it? (YES/no/selectively): y

Next adapter: SMBus I801 adapter at 18c0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x69

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' 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
Probing for `Winbond W83627HF' at 0x290...                  No
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0xec11
Trying family `National Semiconductor'...                   Yes
Found `Nat. Semi. PC87591 Super IO'
    (but not activated)
Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0xec11
Trying family `VIA/Winbond/Fintek'...                       Yes
Found unknown chip with ID 0xec11
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no): y
AMD K8 thermal sensors...                                   No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No

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

Driver `adm1021' (may not be inserted):
  Misdetects:
  * Bus `NVIDIA i2c adapter 2 at 1:00.0'
    Busdriver `UNKNOWN', I2C address 0x4c
    Chip `Maxim MAX1617' (confidence: 3)

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * Bus `NVIDIA i2c adapter 2 at 1:00.0'
    Busdriver `UNKNOWN', I2C address 0x4c
    Chip `Maxim MAX6648/MAX6692' (confidence: 8)

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `NVIDIA i2c adapter 2 at 1:00.0'
    Busdriver `UNKNOWN', I2C address 0x50
    Chip `eeprom' (confidence: 6)
  * Bus `SMBus I801 adapter at 18c0'
    Busdriver `i2c-i801', I2C address 0x50
    Chip `eeprom' (confidence: 6)

  EEPROMs are *NOT* sensors! They are data storage chips commonly
  found on memory modules (SPD), in monitors (EDID), or in some
  laptops, for example.

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

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

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

#----cut here----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA i2c adapter 0 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 1:00.0
modprobe i2c-i801
# Chip drivers
# no driver for Maxim MAX6648/MAX6692 yet
modprobe eeprom
# Warning: the required module coretemp is not currently installed
# on your system. For status of 2.6 kernel ports check
# http://www.lm-sensors.org/wiki/Devices. If driver is built
# into the kernel, or unavailable, comment out the following line.
modprobe coretemp
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.

All lines were added as shown above (module coretemp is not installed, modules were loaded tells lsmod, but sensors said just "No sensors detected".

What can I do to get more Information to help you helping me?

hi,

i get this of sensors on my asus m2n-e:

k8temp-pci-00c3
Adapter: PCI adapter
temp1:       +18 C
temp3:       +17 C

it8716-isa-0290
Adapter: ISA adapter
VCore:     +0.96 V  (min =  +0.00 V, max =  +4.08 V)
VDDR:      +3.20 V  (min =  +0.00 V, max =  +4.08 V)
+3.3V:     +0.00 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
+5V:       +4.89 V  (min =  +0.00 V, max =  +6.85 V)
+12V:     +11.71 V  (min =  +0.00 V, max = +16.32 V)
in5:       +0.00 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in6:       +0.00 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
5VSB:      +4.81 V  (min =  +0.00 V, max =  +6.85 V)
VBat:      +2.93 V
CPU Fan:  2272 RPM  (min =    0 RPM)
fan2:        0 RPM  (min =    0 RPM)
CPU Temp:    +78 C  (low  =    -1 C, high =  +127 C)   sensor = thermistor
M/B Temp:    +33 C  (low  =    -1 C, high =  +127 C)   sensor = thermistor
vid:      +1.100 V

so the 18 / 17 C are way too cool imo...

some more info:

sensors version 2.10.1 with libsensors version 2.10.1
Linux d-partment 2.6.19-gentoo-r1 #4 SMP PREEMPT Wed Dec 6 17:13:36 CET 2006
x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux

any hints?

Email address is simon at simonandkate.net.

Using 2.10.1 on a HP d530 running Suse 10.2 (upgraded PC from ticket 2154). Latest BIOS from HP for d530 has a setting in BIOS to enable unhiding the SMBus. Sensors detects and loads fine:

p2000:/usr/bin # sensors-detect
# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)

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.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801EB ICH5

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: NVIDIA i2c adapter 2 at 1:00.0
Do you want to scan it? (YES/no/selectively):
Adapter cannot be probed, skipping.

Next adapter: NVIDIA i2c adapter 1 at 1:00.0
Do you want to scan it? (YES/no/selectively):
Adapter cannot be probed, skipping.

Next adapter: NVIDIA i2c adapter 0 at 1:00.0
Do you want to scan it? (YES/no/selectively):
Adapter cannot be probed, skipping.

Next adapter: SMBus I801 adapter at fc00
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x2e
Handled by driver `lm85' (already loaded), chip type `adt7463'
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x51
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x52
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x69

Some chips are also 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 LM78-J' 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
Probing for `Winbond W83627HF' at 0x290...                  No
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `AMD K8 thermal sensors'...                     No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain 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 `ITE'...                                      Yes
Found unknown chip with ID 0x6e00
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0x6e00
Trying family `VIA/Winbond/Fintek'...                       No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No

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

Driver `lm85' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at fc00'
    Busdriver `i2c-i801', I2C address 0x2e
    Chip `adt7463' (confidence: 6)

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at fc00'
    Busdriver `i2c-i801', I2C address 0x50
    Chip `eeprom' (confidence: 6)
  * Bus `SMBus I801 adapter at fc00'
    Busdriver `i2c-i801', I2C address 0x51
    Chip `eeprom' (confidence: 6)
  * Bus `SMBus I801 adapter at fc00'
    Busdriver `i2c-i801', I2C address 0x52
    Chip `eeprom' (confidence: 6)

  EEPROMs are *NOT* sensors! They are data storage chips commonly
  found on memory modules (SPD), in monitors (EDID), or in some
  laptops, for example.

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to
/etc/modprobe.conf:

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

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

#----cut here----
# I2C adapter drivers
modprobe i2c-i801
# Chip drivers
modprobe lm85
modprobe eeprom
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):

Sensors output is:

p2000:/usr/bin # /usr/bin/sensors
adt7463-i2c-0-2e
Adapter: SMBus I801 adapter at fc00
V1.5:      +0.003 V  (min =  +0.00 V, max =  +3.32 V)   ALARM
VCore:     +1.497 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:      +3.347 V  (min =  +0.00 V, max =  +4.38 V)
V5:       +5.163 V  (min =  +0.00 V, max =  +6.64 V)
V12:      +3.313 V  (min =  +0.00 V, max = +15.94 V)
CPU_Fan:      0 RPM  (min = 4000 RPM)                     ALARM
Fan2:         0 RPM  (min =    0 RPM)
Fan3:         0 RPM  (min =    0 RPM)
Fan4:         0 RPM  (min =    0 RPM)
CPU Temp: +37.50°C  (low  =  -127°C, high =  +127°C)
Board Temp:
          +40.25°C  (low  =  -127°C, high =  +127°C)
Remote Temp:
          +43.75°C  (low  =  -127°C, high =  +127°C)
CPU_PWM:     1
Fan2_PWM:  255
Fan3_PWM:  255
vid:      +1.525 V  (VRM Version 9.0)

None of the fans read anything - and they won't accept any divisor settings - when I try and use "set fan1_div 4" or anything else I just get:

p2000:/usr/bin # /usr/bin/sensors -s
Error: Line 2440: Unknown feature name
adt7463-i2c-0-2e: No such feature known

CPU_PWM always reads 1, the other PWMs all read 255.

V12 (in4) is reading 3.3V, so seems to be reading a 3.3V not a 12V, and in0(V1.5) is only ever at 0.003V.

I have searched on the fan issue and found Ticket 1837 that said it was resolved in 2.8.8 - I am on 2.10.1 and have tried 2.10.2 and it does the same (went back to 2.10.1 as it is the version that Yast2 installs and manages).

Any ideas?

Is nForce5 supported? If not, does someone know when it may be?