lm-sensors: seltsame werte, scheint nicht richtig zu funktionieren

[stefan-tiger]

hallo, folgendes:

ich hab lm-sensors installiert und wollte es benutzen.
wenn ich jetzt "sensors" eingebe kommt folgendes:

bash-2.05b$ sensors
lm80-i2c-1-2d
Adapter: SMBus Via Pro adapter at 5000
Algorithm: Non-I2C SMBus adapter
+5V: +4.55 V (min = +4.50 V, max = +0.00 V) ALARM
VTT: +1.65 V (min = +1.71 V, max = +2.09 V) ALARM
+3.3V: +2.61 V (min = +2.97 V, max = +3.63 V) ALARM
+Vcore: +1.84 V (min = +2.52 V, max = +3.08 V) ALARM
+12V: +13.20 V (min = +10.80 V, max = +13.20 V) ALARM
-12V: -9.61 V (min = -11.04 V, max = -8.96 V)
-5V: -3.64 V (min = -4.61 V, max = -3.39 V) ALARM
fan1: 10546 RPM (min = 6000 RPM, div = 1)
fan2: 10629 RPM (min = 6000 RPM, div = 1)
temp: -128.00 °C (hot:limit = +6°C, hysteresis = +5°C) ALARM
(os: limit = +6°C, hysteresis = +5°C) ALARM
alarms: Board temperature input (LM75) ALARM
alarms: Chassis intrusion detection ALARM

diese werte sind teilweise ziemlich unrealistisch bzw. falsch.

hab ich was falsch gemacht??
ich habe ein via kt133a mainboard und bin folgendermaßen vorgegangen:

bash-2.05b# sensors-detect
This program will help you to determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively.
You need to have done a `make install', issued a `depmod -a' and made sure
`/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate
module path before you can use some functions of this utility. Read
doc/modules for more information.
Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files
for some things. You can use prog/mkdev/mkdev.sh to create these /dev files
if you do not have them already.
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.

System vendor (DMI): VIA Technologies, Inc.
BIOS version (DMI): 6.00 PG
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-viapro' for device 00:07.4: VIA Technologies VT82C686 Apollo ACPI
Use driver `i2c-matroxfb' for device 00:0c.0: MGA 1064SG [Mystique]
Use driver `i2c-riva' for device 01:00.0: GeForce DDR
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
Load `i2c-matroxfb' (say NO if built into your kernel)? (YES/no): no
Load `i2c-riva' (say NO if built into your kernel)? (YES/no): no
Do you now want to be prompted for non-detectable adapters? (yes/NO):
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: bt848 #0 (Bit-shift algorithm)
Do you want to scan it? (YES/no/selectively): no

Next adapter: SMBus Via Pro adapter at 5000 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x18
Probing for `Analog Devices ADM1021'... 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'... Success!
(confidence 6, driver `adm1021')
Probing for `Genesys Logic GL523SM'... Failed!
Probing for `Onsemi MC1066'... Failed!
Client found at address 0x19
Probing for `Analog Devices ADM1021'... 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'... Success!
(confidence 6, driver `adm1021')
Probing for `Genesys Logic GL523SM'... Failed!
Probing for `Onsemi MC1066'... Failed!
Client found at address 0x2d
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Success!
(confidence 3, driver `lm80')
Probing for `National Semiconductor LM85'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x30
Client found at address 0x31
Client found at address 0x32
Client found at address 0x50
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Client found at address 0x51
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x52
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x69

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. Do you want to scan the ISA bus? (YES/no): no

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

Driver `adm1021' (should be inserted but causes problems):
Detects correctly:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x18
Chip `National Semiconductor LM84' (confidence: 6)
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x19
Chip `National Semiconductor LM84' (confidence: 6)
Misdetects:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x18
Chip `Maxim MAX1617' (confidence: 3)
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x19
Chip `Maxim MAX1617' (confidence: 3)

Driver `lm80' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x2d
Chip `National Semiconductor LM80' (confidence: 3)

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x50
Chip `Serial EEPROM' (confidence: 8)
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x51
Chip `Serial EEPROM' (confidence: 8)
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x52
Chip `Serial EEPROM' (confidence: 8)


I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? ISA

WARNING! If you have some things built into your kernel, the
below list will contain too many modules. Skip the appropriate ones!
To load everything that is needed, execute these commands:

#----cut here----
# I2C adapter drivers
# modprobe unknown adapter bt848 #0 using Bit-shift algorithm
modprobe i2c-viapro
# I2C chip drivers
modprobe adm1021
modprobe lm80
modprobe eeprom
#----cut here----

If you want to load the modules at startup, generate a config file
below and make sure lm_sensors get started (eg. rc-update add lm_sensors default).

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
options adm1021 ignore=0,0x18,0,0x19
#----cut here----

Do you want to overwrite /etc/conf.d/lm_sensors? Enter s to specify other file name?
(yes/NO/s): yes
Done.
bash-2.05b# modprobe adm1021
Note: /etc/modules.conf is more recent than /lib/modules/2.4.20-gentoo-r5/modules.dep
bash-2.05b# modprobe lm80
Note: /etc/modules.conf is more recent than /lib/modules/2.4.20-gentoo-r5/modules.dep
bash-2.05b# modprobe eeprom
Note: /etc/modules.conf is more recent than /lib/modules/2.4.20-gentoo-r5/modules.dep
modprobe i2c-viapro
bash-2.05b# lsmod
Module Size Used by Tainted: P
lm80 5660 0 (unused)
adm1021 6712 0 (unused)
i2c-philips-par 2268 0 (unused)
i2c-dev 4772 0
i2c-viapro 3984 0
i2c-proc 7376 0 [lm80 adm1021]
usb-storage 24112 0
rtc 7644 0 (autoclean)
printer 7712 0
hid 19492 0 (unused)
input 3424 0 [hid]
uhci 27216 0 (unused)
usbcore 39904 0 [usb-storage printer hid uhci]
es1371 29352 1
lp 6368 0
parport_pc 17032 1
parport 14144 1 [i2c-philips-par lp parport_pc]
tvaudio 14236 0 (autoclean) (unused)
bttv 78592 0
i2c-algo-bit 8328 1 [i2c-philips-par bttv]
videodev 6240 2 [bttv]
tuner 10912 1
i2c-core 15208 0 [lm80 adm1021 i2c-dev i2c-viapro i2c-proc tvaudio bttv i2c-algo-bit tuner]
via82cxxx_audio 20952 2
ac97_codec 11016 0 [es1371 via82cxxx_audio]
uart401 6692 0 [via82cxxx_audio]
sound 58708 0 [via82cxxx_audio uart401]
sr_mod 18264 6
sg 29356 0 (unused)
ide-scsi 8880 3
nvidia 1631680 11
sis900 14412 1
ne2k-pci 5792 0 (unused)
8390 6832 0 [ne2k-pci]

[stefan-tiger]

so soll es aussehen von den werten her (MBM unter win)

[stefan-tiger]

mittlerweile bin ich einen kleinen schritt weiter:

bash-2.05b$ sensors
lm84-i2c-1-18
Adapter: SMBus Via Pro adapter at 5000
Algorithm: Non-I2C SMBus adapter
Board: +8°C (min = -1°C, max = -88°C)
CPU: +10°C (min = +52°C, max = -1°C)

lm84-i2c-1-19
Adapter: SMBus Via Pro adapter at 5000
Algorithm: Non-I2C SMBus adapter
Board: +42°C (min = -1°C, max = +103°C)
CPU: +40°C (min = +60°C, max = -1°C)

lm80-i2c-1-2d
Adapter: SMBus Via Pro adapter at 5000
Algorithm: Non-I2C SMBus adapter
+5V: +4.42 V (min = +4.50 V, max = +0.00 V) ALARM
VTT: +1.64 V (min = +1.71 V, max = +2.09 V) ALARM
+3.3V: +2.61 V (min = +2.97 V, max = +3.63 V) ALARM
+Vcore: +1.84 V (min = +2.52 V, max = +3.08 V) ALARM
+12V: +13.20 V (min = +10.80 V, max = +13.20 V) ALARM
-12V: -9.02 V (min = -10.45 V, max = -8.37 V)
-5V: -3.38 V (min = -4.32 V, max = -3.09 V) ALARM
fan1: 10546 RPM (min = 6000 RPM, div = 1)
fan2: 10465 RPM (min = 6000 RPM, div = 1)
temp: -128.00 °C (hot:limit = +6°C, hysteresis = +5°C) ALARM
(os: limit = +6°C, hysteresis = +5°C) ALARM
alarms: Board temperature input (LM75) ALARM
alarms: Chassis intrusion detection ALARM


1. irgendiwe ist das immernoch sehr konfus
2. es fehlt immernoch die lüfterdrehzahl
3. ksensors kann mir den ZWEI lm84 dinger nicht richtig umgehn z.b. statt wir oben stehend wir in ksensors angezeigt 40V statt 40°C (ksensors verwechselt temperatur und spannungen)
4. was sollen die temperaturen 8° und 10°C bedeuten?

irgendwie macht das noch kein spass. kann mir jemand helfen die "fehler" zu beheben?

danke schonmal gruß

[stefan-tiger]

im anhang bilder von meinem konfusen ksensors

[Hitman]

Hi stefan-tiger,

schon mal in der /etc/sensors.conf nach deinem Chip geschaut und die Lüfterdrehzahlwerte geändert?

Bsp:
set fan1_div 4
set fan2_div 4

Gruß

Bernd

[stefan-tiger]

Original geschrieben von Hitman
Hi stefan-tiger,

schon mal in der /etc/sensors.conf nach deinem Chip geschaut und die Lüfterdrehzahlwerte geändert?

Bsp:
set fan1_div 4
set fan2_div 4

Gruß

Bernd

hm, tut sich nix. die richtige sektion hab ich aber gefunden weil das um labeln von fan1 und fan2 hat geklappt.

gruß

[Hitman]

Probier zuerst mal "sensors -s" bevor du mit "sensors" die Daten ausliest.

[stefan-tiger]

ich hab jetzt die /etc/sensors.conf abgeändert:

chip "lm80-*"

label in0 "+5V"
label in1 "VTT"
label in2 "+3.3V"
label in3 "+Vcore"
label in4 "+12V"
label in5 "-12V"
label in6 "-5V"

label fan1 "CPU-Fan"
label fan2 "Board-Fan"

label temp "Temperature"

compute in0 (24/14.7 + 1) * @ , @ / (24/14.7 + 1)
compute in2 (22.1/30 + 1) * @ , @ / (22.1/30 + 1)
compute in3 (2.8/1.9) * @, @ * 1.9/2.8
compute in4 (160/30.1 + 1) * @, @ / (160/30.1 + 1)
compute in5 (160/35.7)*(@ - in0) + @, (@ + in0 * 160/35.7)/ (1 + 160/35.7)
compute in6 (36/16.2)*(@ - in0) + @, (@ + in0 * 36/16.2) / (1 + 36/16.2)

compute fan1 0.5 * @ , @ / 0.5
compute fan2 0.5 * @ , @ / 0.5

set in0_min 5 * 0.95
set in0_max 5 * 0.95
# What is your VTT? It is probably not this value...
set in1_min 2*0.95
set in1_max 2*1.05
set in2_min 3.3 * 0.95
set in2_max 3.3 * 1.05
# What is your VCore? It is probably not this value...
set in3_min 1.9 * 0.95
set in3_max 1.9 * 1.05
set in4_min 12 * 0.95
set in4_max 12 * 1.05
set in5_min -12 * 1.05
set in5_max -12 * 0.95
set in6_min -5 * 1.05
set in6_max -5 * 0.95


und erhalte nun folgende ausgabe:

bash-2.05b$ sensors
lm84-i2c-1-18
Adapter: SMBus Via Pro adapter at 5000
Algorithm: Non-I2C SMBus adapter
Board: +8°C (min = -1°C, max = -88°C)
CPU: +10°C (min = +52°C, max = -1°C)

lm84-i2c-1-19
Adapter: SMBus Via Pro adapter at 5000
Algorithm: Non-I2C SMBus adapter
Board: +42°C (min = -1°C, max = +103°C)
CPU: +40°C (min = +60°C, max = -1°C)

lm80-i2c-1-2d
Adapter: SMBus Via Pro adapter at 5000
Algorithm: Non-I2C SMBus adapter
+5V: +4.40 V (min = +4.50 V, max = +0.00 V) ALARM
VTT: +1.64 V (min = +1.71 V, max = +2.09 V) ALARM
+3.3V: +2.61 V (min = +2.97 V, max = +3.63 V) ALARM
+Vcore: +1.84 V (min = +2.52 V, max = +3.08 V) ALARM
+12V: +13.20 V (min = +10.80 V, max = +13.20 V) ALARM
-12V: -8.91 V (min = -10.33 V, max = -8.25 V)
-5V: -3.33 V (min = -4.26 V, max = -3.04 V) ALARM
CPU-Fan: 5273 RPM (min = 6000 RPM, div = 1)
Board-Fan:5273 RPM (min = 6000 RPM, div = 1)
Temperature:
-128.00 °C (hot:limit = +6°C, hysteresis = +5°C) ALARM
(os: limit = +6°C, hysteresis = +5°C) ALARM
alarms: Board temperature input (LM75) ALARM
alarms: Chassis intrusion detection ALARM



die beiden compute zeile für die fans habe ich gemacht. nur was bringt das eigentlich den wert durch mathematik zu verändern bis das wunschergebnis herauskommt???

es muss doch irgendwo ne festlegung geben wie lm_sensors meine sensoren auszulesen hat.

warum hab ich zweimal die selbe drehzahl?
warum steht oben was von 8 und 10°C ??
warum gibt mir der temperatursensor von lm80 einen wert von -128°C ???
woher weiss ich ob die werte stimmen wenn sie doch per comute verändert werden können???

leider blick ich hier noch nicht ganz durch. :(

wieso kann ich nicht einfach, wie bei MBM, mein board auswähren und es geht einfach?

gruß

[stefan-tiger]

Original geschrieben von Hitman
Probier zuerst mal "sensors -s" bevor du mit "sensors" die Daten ausliest.

bash-2.05b# whoami
root
bash-2.05b# sensors -s
lm80-i2c-1-2d: Can't access /proc file for writing;
Run as root?
bash-2.05b# ls / -l | grep proc
dr-xr-xr-x 107 root root 0 Jan 2 09:42 proc
bash-2.05b# mount | grep proc
none on /proc type proc (rw)

geht irgendwie nicht!?

-s, --set Execute `set' statements too (root only)

was macht das wenn ich fragen darf?

gruß

[Hitman]

Ich habe mir deine Daten von "sensors-detect" noch mal angeschaut. Da steht was von "Use driver `i2c-viapro' for device 00:07.4: VIA Technologies VT82C686 Apollo ACPI". Du benutzt aber den "lm80"-Treiber. Versuch es mal mit dem Modul "via686a"!

sensors -s, --set Execute `set' statements too (root only)
Es wendet die Einstellungen der sensors.conf an und ist nur als root ausführbar.

[stefan-tiger]

ok, hab die lm80 mal rausgeschmissen und alles andere auch, dann i2c-isa und via686a geladen, dann ein sensors-detect gemacht und siehe da:

bash-2.05b# sensors
via686a-isa-6000
Adapter: ISA adapter
Algorithm: ISA algorithm
CPU core: +1.78 V (min = +1.79 V, max = +2.18 V) ALARM
+2.5V: +1.48 V (min = +2.24 V, max = +2.74 V) ALARM
I/O: +3.32 V (min = +2.95 V, max = +3.62 V)
+5V: +4.87 V (min = +4.47 V, max = +5.49 V)
+12V: +11.98 V (min = +10.79 V, max = +13.18 V)
CPU Fan: 5232 RPM (min = 3000 RPM, div = 2)
P/S Fan: 0 RPM (min = 3000 RPM, div = 2)
SYS Temp: +41.8°C (limit = +60°C, hysteresis = +50°C)
CPU Temp: +39.9°C (limit = +60°C, hysteresis = +50°C)
SBr Temp: +26.1°C (limit = +60°C, hysteresis = +50°C)

die werte scheinen zu stimmen.
nur warum jetzt ISA??
und warum wurde zuvor auch "irgendwas" angezeigt?

es geht jedenfalls jetzt *juhu*

vielen dank

gruß

[ml]

Original geschrieben von stefan-tiger

nur warum jetzt ISA??



Das würd mich auch interessieren, ist bei mir auch so:

[markus@Markus markus]$ sensors
w83627hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +3.02 V (min = +0.00 V, max = +0.00 V)
VCore 2: +3.16 V (min = +0.00 V, max = +0.00 V)
+3.3V: +3.31 V (min = +3.13 V, max = +3.45 V)
+5V: +5.16 V (min = +4.72 V, max = +5.24 V)
+12V: +15.50 V (min = +10.79 V, max = +13.19 V)
-12V: -4.42 V (min = -13.21 V, max = -10.90 V)
-5V: -7.71 V (min = -5.26 V, max = -4.76 V)
V5SB: +4.89 V (min = +4.72 V, max = +5.24 V)
VBat: +3.23 V (min = +2.40 V, max = +3.60 V)
fan1: 0 RPM (min = 187 RPM, div = 32)
fan2: 2800 RPM (min = 3000 RPM, div = 2)
fan3: 0 RPM (min = 46 RPM, div = 128)
temp1: +39°C (limit = +60°C) sensor = thermistor
temp2: +38.5°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
temp3: +208.0°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
vid: +0.000 V
alarms:
beep_enable:
Sound alarm enabled

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0400
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 256

eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 0400
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 256

[markus@Markus markus]$

mfg

ml

[Hitman]

Ich möchte ja nicht sagen "rtfm", aber ein wenig selber lesen kann man schon: http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html#Section%202.3

[ml]

Okay, danke.

[stefan-tiger]

Original geschrieben von ml



+12V: +15.50 V (min = +10.79 V, max = +13.19 V)
-12V: -4.42 V (min = -13.21 V, max = -10.90 V)
-5V: -7.71 V (min = -5.26 V, max = -4.76 V)

temp3: +208.0°C (limit = +60°C, hysteresis = +50°C) sensor =

eeprom-i2c-0-50

Memory type: DDR SDRAM DIMM SPD


eeprom-i2c-0-52

Memory type: DDR SDRAM DIMM SPD






bei dir scheint auch nix alles ganz astrein zu sein.

und kann man sich das modul eeprom nicht sparen bei mir findet der damit auch "nur" die arbeitsspecihermodule (kann man da was üebrwachen???)


@Hitman: sorry

gruß

[Hitman]

Soweit mir bekannt ist, kann man bei Speichermodulen nichts auslesen. Bei Festplatten welche S.M.A.R.T.-fähig sind, kann man die Temperatur abfragen.


temp3: +208.0°C

Vielleicht hat das Board nur 2 Temperatursensoren und spackt da rum.



+12V: +15.50 V (min = +10.79 V, max = +13.19 V)
-12V: -4.42 V (min = -13.21 V, max = -10.90 V)
-5V: -7.71 V (min = -5.26 V, max = -4.76 V)


In der Doku zum Chiptreiber steht, daß die Spannungen nur zwischen 0 und 4,08 V mit 0,016 Volt Schritten gemessen werden. Es scheint dann wohl ein Berechnungsproblem zu sein. Wurde was in der sensors.conf verändert? (Und richtigen Chip ausgewählt? http://secure.netroedge.com/~lm78/supported.html ).

[ml]

Ja, ich weiß dass der temp3-Wert nicht passt, ich wüsste auch nicht was für ein Sensor das ist.

temp1 ist niedriger daher nehm ich mal an dass das die MoBo-Temp ist und temp2 daher die CPU-Temp.

Meine HD kann S.M.A.R.T., die temp les ich nicht mir sensors aus sondern mit hddtemp und ksensors, siehe auch http://www.linuxforen.de/forums/showthread.php?s=&threadid=116146

Was kann kann ich machen damit die Spannungswerte passen?
In der /etc/sensors.conf herumpfuschen? Wüsste nicht was ich da machen kann.

mfg

ml

[zyklop]

Hallo Freaks !!

Hab hier meinen Debian Server mit 2.6.8 Kernel am rennen, Chip ist ein SIS96x
lief auch alles mit der ISA Konfig gut, hab dann unter KSENSORS meine Email eingetragen zum melden bei ausfall...... (Aktion: mail adresse@server.de -s Lüfter-zu-langsam)
Test=Lüfter mit Finger kurz angehalten !!!
Klappte auch prima !!!

Jetzt zeigt mir weder "sensor" auf der Konsole, noch KSENSORS die Lüfterdrehzahl an !

Die steht immer auf null, im Bios hingegen zeigt er sie richtig mit ca 2400 rpm....

Wasn das fürn mist ???

Ging doch vor der Aktion einwandfrei !!

schreibt der die Konfig in irgendeine Datei, die er nicht mehr überschreiben kann ?? (hatte das mit 2 usern getestet.....)

Grüße

ZYKLOP

Werd da mal einen neuen Thread öffnen !!