PDA

Visualizza versione completa : Error updating sensor dopo sostituzione mainboard



principe andry
08-08-10, 12: 29
ciao a tutti :hap

Ho cambiato la scheda madre, ed all'avvio mi segna appunto questo errore sui sensori termici.
I core sembrano giusti (51°) forse anche la scheda video (54° si è un pò alzata al cambio della scheda) mentre non segna quella del processore e scheda madre. Inoltre quella dell'HD è di -1° :tong2

Rimane in vista un avviso che recita:
Error updating sensor temp2 (anche temp1 e temp3).
An error occurred while trying to update the value of the sensor temp2 (temp1 o temp3) located at sensor://w83627ehf-isa-0290/56.

Cosa dovrei fare per far tornare tutto normale?
Ci sono altre operazioni da fare visto il cambio della scheda?

Per ora oltre questo non riscontro alcun problema...

grazie :bai

K.a.o.s.
08-08-10, 12: 48
Ciao, prova a dare
Only registered members can view code. e seguire la procedura. Probabilmente è perché tenta di usare i moduli vecchi con la nuova scheda.

principe andry
08-08-10, 12: 56
Grazie :hap

Ti posto il log:
andrea@andrea-desktop:~$ sudo sensors-detect
[sudo] password for andrea:
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: MICRO-STAR INTERNATIONAL CO.,LTD MS-7519

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): y
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... Success!
(driver `coretemp')
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): y
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'... Yes
Found `Fintek F71882FG/F71883FG Super IO Sensors' Success!
(address 0xa00, driver `f71882fg')

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): y
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

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): y
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): y
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.

Next adapter: NVIDIA i2c adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x4a
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x4b
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6650/MAX6651'... Success!
(confidence 2, driver `max6650')
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `Analog Devices ADT7481'... 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'... Yes
(confidence 8, not a hardware monitoring chip)

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

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

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

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

Next adapter: NVIDIA i2c adapter (i2c-5)
Do you want to scan it? (YES/no/selectively): y
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

Next adapter: SMBus I801 adapter at 0400 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x28
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... 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 `Analog Devices ADM1029'... No
Probing for `ITE IT8712F'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
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 `coretemp':
* Chip `Intel Core family thermal sensor' (confidence: 9)

Driver `max6650':
* Bus `NVIDIA i2c adapter '
Busdriver `nvidia', I2C address 0x4b
Chip `Maxim MAX6650/MAX6651' (confidence: 2)

Driver `f71882fg':
* ISA bus, address 0xa00
Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
f71882fg
max6650
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.

Unloading i2c-dev... OK
Unloading i2c-i801... OK

andrea@andrea-desktop:~$

Per ora non è cambiato nulla.
Se non ho capito male devo eseguire /etc/init.d/module-init-tools start. Il file l'ho trovato. Basta farci doppio click sopra? Meglio chiedere prima :tong2

Grazie :bai

K.a.o.s.
08-08-10, 13: 02
Basta farci doppio click sopra? Meglio chiedere prima
No per 2 motivi: è un servizio che devi avviare quindi con il parametro start e dev'essere lanciato da root :hap.

Only registered members can view code.

principe andry
08-08-10, 14: 01
Ah ok :ehmm

Fatto ed ecco il report:

andrea@andrea-desktop:~$ sudo /etc/init.d/module-init-tools start
[sudo] password for andrea:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service module-init-tools start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start module-init-tools
module-init-tools stop/waiting

Attendo altre istruzioni :bgg2

Grazie :bai

K.a.o.s.
08-08-10, 14: 26
Attendo altre istruzioni
Che stress Ubuntu... ditemi se questo è semplificare... vabbé:
Fallo partire, sperando che finalmente gli vada bene, con

Only registered members can view code.
Altrimenti, soluzione più rapida, dovrebbe bastare riavviare :ghgh (brutta cosa lo so).

principe andry
08-08-10, 14: 42
Provando il comando ottengo:

module-init-tools stop/waiting

Non cambia nulla :triste
Ora non vorrei riavviare perchè finalmente Trasmission stà scaricando decentemente :ghgh

Se basta solo riavviare, allora ti farò sapere appena possibile :eye

Grazie :bai

EDIT: ho aggiunto di nuovo Hardware sensors nella barra, e questo mi segna valori che prima non dava. Anche se non mi vengono notificati (rimangono come temp1 e temp2) immagino si tratti del processore (34°) e scheda madre (37°).
L'HD è normale ora (39°). Quindi tutto ok :eye

Grazie K.a.o.s. :hap

pierino_89
08-08-10, 22: 12
@ Kaos: il comando vecchio funziona benissimo, si limita a dirti che puoi usare l'alternativa (anche se mi hanno riportato casi di servizi impazziti con lo script standard).

In ogni caso il comando giusto sarebbe stato sudo /etc/init.d/module-init-tools restart, dato che il servizio era già attivo, quindi un nuovo start sarebbe giustamente stato ignorato.

K.a.o.s.
08-08-10, 22: 21
In ogni caso il comando giusto sarebbe stato sudo /etc/init.d/module-init-tools restart, dato che il servizio era già attivo, quindi un nuovo start sarebbe giustamente stato ignorato.Sono completamente fuori "allenamento" :bgg2, non restarto più un servizio da 8 mesi:ghgh

(anche se mi hanno riportato casi di servizi impazziti con lo script standard)Ma se non sbaglio lo standard per i servizi non rileva i kill -9 :hap.

pierino_89
08-08-10, 22: 24
Il sistema standard non rileva niente, in genere si basa su dei lockfile con dentro il pid. Figurati che per squid (che lancia più processi) lo stop ne lascia sempre appeso uno.