Someone told me to use lm83 instead of lm85. I tried. Now sensors simply doesn't show any info about my motherboard sensors hahaha
Take back lm85 to /proc/modules... but before, downloaded the new sensors-detect and ran:
# sensors-detect revision 5760 (2009-07-24 15:52:28 +0200)
# Board: Intel Corporation DG45ID
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 K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal and voltage sensors... 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'... Yes
Found `Nuvoton WPCD377I Super IO'
(no hardware monitoring capabilities)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/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):
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):
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 e000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
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'... Yes
(confidence 7, not a hardware monitoring chip)
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 `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'... 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 `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'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Next adapter: NVIDIA i2c adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
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-2)
Do you want to scan it? (YES/no/selectively):
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-3)
Do you want to scan it? (YES/no/selectively):
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)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
I tried running the /etc/init.d/lm-sensors (there's no underline, its an hyphen). Same results, sensors was just showing my CPU temps.
I'll try to restart and send another mail with any result.
I've read the bug report you linked me after the part where someone talks about my motherboard. Looks like they did some research and just ended on an empty point.
Everything that's possible I'll try to help you all.
Anything else I can do? I really wanna see this working and to collaborate with this =]
Thank you,
Programador Web
On Fri, Sep 11, 2009 at 03:56, Jean Delvare <khali@xxxxxxxxxxxx> wrote:
Looks very similar to:On Thu, 10 Sep 2009 19:20:55 -0300, Igor Santos wrote:
> Hello,
>
> I've been asking for help at superuser.com, but nobody could help me.
> I've tried the last version of sensors-detect script, but it just gives me
> the same modules to load up...
>
> This is my computer:
> Intel Core2duo e4700
> Motherboard Intel DG45ID
> GeForce 9800 GT
> 2 HD's, one SATA and one PATA with adapter
>
> It tolds me to load i2c-i801, lm85 and coretemp modules. And so I did.
>
> I can see properly my Videocard temp (I think it's provided by nvidia,
> right?) and both HD (but sometimes the IDE disk simply goes 0°). My CPU
> temps looks correct too.
>
> But all the temps from my motherboard are zeroed.
> Take a look at the full output:
>
> igoru[~]$ sensors
> > lm85-i2c-0-2e
> > Adapter: SMBus I801 adapter at e000
> > V1.5: +0.00 V (min = +0.00 V, max = +3.32 V)
> > VCore: +0.00 V (min = +0.00 V, max = +2.99 V)
> > V3.3: +0.00 V (min = +0.00 V, max = +4.38 V)
> > V5: +0.00 V (min = +0.00 V, max = +6.64 V)
> > V12: +0.00 V (min = +0.00 V, max = +15.94 V)
> > CPU_Fan: 0 RPM (min = 0 RPM) ALARM
> > fan2: 0 RPM (min = 0 RPM) ALARM
> > fan3: 0 RPM (min = 0 RPM) ALARM
> > fan4: 0 RPM (min = 0 RPM) ALARM
> > CPU Temp: +0.0°C (low = -127.0°C, high = +127.0°C)
> > Board Temp: +0.0°C (low = -127.0°C, high = +127.0°C)
> > Remote Temp: +0.0°C (low = -127.0°C, high = +127.0°C)
> > cpu0_vid: +2.050 V
http://www.lm-sensors.org/ticket/2182
Please post the output of the latest version of sensors-detect:
http://dl.lm-sensors.org/lm-sensors/files/sensors-detect
Don't forget to "rmmod lm85" before you run sensors-detect.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
