SuSE 10.1 - CPU-Temperatur auslesen

[raver2]

hi,

ich möchte gerne für Superkaramba CPU-Temperatur und RPM ausgelesen haben , allerdings zeigt der mir nix an ... und die Temperatur steht ständig auf 40°C

welche Module muss ich aktivieren (usw.)

Mainboard war irgendwas mit ASUS (nforce 2 oder 3 chipsatz) - ist das alte von meinem Vater

[kreol]

Ist lmsensors installiert? Dann versuch mal ein "sensors-detect"


Kreol

[raver2]

linux:/home/Hendrik # 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): y
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce2 SMBus (MCP)
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-nforce2' 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 already loaded.

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: NVIDIA I2C Device
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x21
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Client found at address 0x4c
Probing for `National Semiconductor LM75'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Analog Devices ADM1021'... Failed!
Probing for `Analog Devices ADM1021A/ADM1023'... Failed!
Probing for `Maxim MAX1617'... Success!
(confidence 3, driver `adm1021')
Probing for `Maxim MAX1617A'... Failed!
Probing for `TI THMC10'... Failed!
Probing for `National Semiconductor LM84'... Failed!
Probing for `Genesys Logic GL523SM'... Failed!
Probing for `Onsemi MC1066'... Failed!
Probing for `Maxim MAX1619'... Failed!
Probing for `National Semiconductor LM82/LM83'... Failed!
Probing for `National Semiconductor LM90'... Failed!
Probing for `National Semiconductor LM89/LM99'... Success!
(confidence 8, driver `lm90')
Probing for `National Semiconductor LM86'... Failed!
Probing for `Analog Devices ADM1032'... Failed!
Probing for `Maxim MAX6657/MAX6658/MAX6659'... Failed!
Probing for `National Semiconductor LM63'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Probing for `Analog Devices ADT7461'... Failed!

Next adapter: NVIDIA I2C Device
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA I2C Device
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x52
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x53
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
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 0x56
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x57
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `Sony Vaio EEPROM'... Failed!

Next adapter: saa7133[0]
Do you want to scan it? (YES/no/selectively): n

Next adapter: SMBus nForce2 adapter at 5100
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x37

Next adapter: SMBus nForce2 adapter at 5000
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x31
Client found at address 0x32
Client at address 0x51 can not be probed - unload all client drivers first!
Client at address 0x52 can not be probed - unload all client drivers first!
Client at address 0x53 can not be probed - unload all client drivers first!

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): y
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... Success!
(confidence 8, driver `it87')
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): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x8712)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x8712)
Probing for `ITE 8712F Super IO Sensors'
Success... found at address 0x0290
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)

Do you want to scan for secondary Super I/O sensors? (YES/no): y
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 `adm1021' (may not be inserted):
Misdetects:
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x4c
Chip `Maxim MAX1617' (confidence: 3)

Driver `lm90' (should be inserted):
Detects correctly:
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x4c
Chip `National Semiconductor LM89/LM99' (confidence: 8)

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x50
Chip `SPD EEPROM' (confidence: 1)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x51
Chip `SPD EEPROM' (confidence: 1)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x52
Chip `SPD EEPROM' (confidence: 1)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x53
Chip `SPD EEPROM' (confidence: 1)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x54
Chip `SPD EEPROM' (confidence: 1)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x55
Chip `SPD EEPROM' (confidence: 1)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x56
Chip `SPD EEPROM' (confidence: 1)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x57
Chip `SPD EEPROM' (confidence: 1)

Driver `it87' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `ITE 8712F Super IO Sensors' (confidence: 9)


I will now generate the commands needed to load the I2C modules.
Use of uninitialized value in numeric eq (==) at /usr/sbin/sensors-detect line 4924.
Use of uninitialized value in numeric eq (==) at /usr/sbin/sensors-detect line 4924.
Use of uninitialized value in numeric eq (==) at /usr/sbin/sensors-detect line 4924.
Use of uninitialized value in numeric eq (==) at /usr/sbin/sensors-detect line 4924.
Use of uninitialized value in numeric eq (==) at /usr/sbin/sensors-detect line 4924.
Use of uninitialized value in numeric eq (==) at /usr/sbin/sensors-detect line 4924.
Use of uninitialized value in numeric eq (==) at /usr/sbin/sensors-detect line 4924.

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-nforce2
# modprobe unknown adapter NVIDIA I2C Device
# modprobe unknown adapter NVIDIA I2C Device
# modprobe unknown adapter NVIDIA I2C Device
modprobe i2c-isa
# I2C chip drivers
modprobe lm90
modprobe eeprom
modprobe it87
# 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): y
linux:/home/Hendrik #




linux:/home/Hendrik # sensors -s
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
linux:/home/Hendrik #

[kreol]

Log Dich mal aus und wieder ein und führe dann "sensors" ohne alles aus.


Kreol

[raver2]

Hendrik@linux:~> sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Hendrik@linux:~>

Hendrik@linux:~> sensors --version
sensors version 2.10.0 with libsensors version 2.10.0
Hendrik@linux:~>

[kreol]

Hm, sehe jetzt auch nur
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!Was sagt "mount" und "lsmod | grep i2c"?

Evtl. reicht ausloggen auch nicht. Versuch es ggf. mal mit einem reboot.


Kreol

[raver2]

linux:/home/Hendrik # mount
/dev/hda2 on / type reiserfs (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hda3 on /home type reiserfs (rw,acl,user_xattr)
/dev/hdc1 on /c_windows type ntfs (ro,noexec,nosuid,nodev,gid=100,umask=0002,nls=utf 8)
/dev/hdb1 on /home/Hendrik/Dokumente/Daten type vfat (rw,noexec,nosuid,nodev,utf8,uid=1000,gid=1000)
securityfs on /sys/kernel/security type securityfs (rw)
linux:/home/Hendrik # lsmod | grep i2c
i2c_dev 8068 0
ir_kbd_i2c 7820 1 saa7134
i2c_nforce2 6272 0
ir_common 9220 2 saa7134,ir_kbd_i2c
i2c_core 19728 8 i2c_dev,eeprom,lm90,tuner,saa7134,ir_kbd_i2c,i2c_n force2,nvidia
linux:/home/Hendrik #


EDIT: Der Neustart reichte aus


Hendrik@linux:~> sensors
it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.65 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +1.52 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +3.26 V (min = +3.14 V, max = +3.47 V)
+5V: +5.00 V (min = +4.76 V, max = +5.24 V)
+12V: +11.84 V (min = +11.39 V, max = +12.61 V)
-12V: -19.63 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -6.37 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +4.95 V (min = +4.76 V, max = +5.24 V)
VBat: +4.08 V
fan1: 1896 RPM (min = 0 RPM, div = 8)
fan2: 0 RPM (min = 3013 RPM, div = 8) ALARM
fan3: 0 RPM (min = 3013 RPM, div = 8) ALARM
M/B Temp: +49°C (low = +15°C, high = +40°C) sensor = thermistor
CPU Temp: +53°C (low = +15°C, high = +45°C) sensor = thermistor
Temp3: +52°C (low = +15°C, high = +45°C) sensor = thermistor

Hendrik@linux:~>