* [lm-sensors] MotherBoard Asus A55M-E
@ 2013-12-03 20:25 Luca Della Ghezza
2013-12-03 22:20 ` Rudolf Marek
2013-12-04 6:52 ` Jean Delvare
0 siblings, 2 replies; 3+ messages in thread
From: Luca Della Ghezza @ 2013-12-03 20:25 UTC (permalink / raw)
To: lm-sensors
Hi!
I recently bought a MB Asus A55M-E, sensors-detect is unable to find out
the thermal chip, below the output
luca@pc-sala:~$ sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: System manufacturer System Product Name
# Board: ASUSTeK COMPUTER INC. A55M-E
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):
Module cpuid loaded successfully.
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
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital 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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... Yes
Found unknown chip with ID 0x8603
(logical device 4 has address 0x290, could be sensors)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/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-piix4' for device 0000:00:14.0: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
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'... Yes
(confidence 8, not a hardware monitoring chip)
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'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: saa7134[0] (i2c-1)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-3)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x49
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6642'... 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
Probing for `NXP/Philips SA56004'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... 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 2 at 1:00.0 (i2c-4)
Do you want to scan it? (YES/no/selectively):
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-5)
Do you want to scan it? (YES/no/selectively):
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
luca@pc-sala:~$
*How can I find out the sensors chip?*
*Thanks a lot for your help.*
Luquino
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [lm-sensors] MotherBoard Asus A55M-E
2013-12-03 20:25 [lm-sensors] MotherBoard Asus A55M-E Luca Della Ghezza
@ 2013-12-03 22:20 ` Rudolf Marek
2013-12-04 6:52 ` Jean Delvare
1 sibling, 0 replies; 3+ messages in thread
From: Rudolf Marek @ 2013-12-03 22:20 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hi,
> Trying family `ITE'... Yes
> Found unknown chip with ID 0x8603
> (logical device 4 has address 0x290, could be sensors)
There is a preliminary patch supporting this driver:
> http://khali.linux-fr.org/devel/linux-3/jdelvare-hwmon/hwmon-it87-01-add-it8603e-support.patch
> Please let me know if I got anything wrong. Retesting would be
> appreciated, just in case.
>
> I have also made the support available as a standalone driver which
> builds at least down to kernel 3.0:
> http://khali.linux-fr.org/devel/lm-sensors/drivers/it87/
Please note there is a (small) problem which will be fixed soonish. If you like
to try it out, apply attached patch on above patch or on the standalone driver.
You can also wait until it is fixed and released in next kernel version.
Thanks
Rudolf
[-- Attachment #2: fixit.patch --]
[-- Type: text/x-diff, Size: 428 bytes --]
Index: linux-3.12/drivers/hwmon/it87.c
===================================================================
--- linux-3.12.orig/drivers/hwmon/it87.c 2013-11-22 21:57:37.454212898 +0100
+++ linux-3.12/drivers/hwmon/it87.c 2013-12-03 23:18:27.597718677 +0100
@@ -1568,6 +1568,7 @@
&sensor_dev_attr_in5_beep.dev_attr.attr,
&sensor_dev_attr_in6_beep.dev_attr.attr,
&sensor_dev_attr_in7_beep.dev_attr.attr,
+ NULL,
NULL
};
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [lm-sensors] MotherBoard Asus A55M-E
2013-12-03 20:25 [lm-sensors] MotherBoard Asus A55M-E Luca Della Ghezza
2013-12-03 22:20 ` Rudolf Marek
@ 2013-12-04 6:52 ` Jean Delvare
1 sibling, 0 replies; 3+ messages in thread
From: Jean Delvare @ 2013-12-04 6:52 UTC (permalink / raw)
To: lm-sensors
On Tue, 03 Dec 2013 23:20:36 +0100, Rudolf Marek wrote:
> > Trying family `ITE'... Yes
> > Found unknown chip with ID 0x8603
> > (logical device 4 has address 0x290, could be sensors)
>
> There is a preliminary patch supporting this driver:
>
> > http://khali.linux-fr.org/devel/linux-3/jdelvare-hwmon/hwmon-it87-01-add-it8603e-support.patch
> > Please let me know if I got anything wrong. Retesting would be
> > appreciated, just in case.
> >
> > I have also made the support available as a standalone driver which
> > builds at least down to kernel 3.0:
> > http://khali.linux-fr.org/devel/lm-sensors/drivers/it87/
>
> Please note there is a (small) problem which will be fixed soonish. If you like
> to try it out, apply attached patch on above patch or on the standalone driver.
Both the patch on in my queue and the standalone driver already include
the fix-up.
> You can also wait until it is fixed and released in next kernel version.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-12-04 6:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-03 20:25 [lm-sensors] MotherBoard Asus A55M-E Luca Della Ghezza
2013-12-03 22:20 ` Rudolf Marek
2013-12-04 6:52 ` Jean Delvare
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.