* [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution
2006-01-27 21:50 [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution Rudolf Marek
@ 2006-01-28 8:52 ` Jean Delvare
2006-01-28 14:05 ` Rudolf Marek
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2006-01-28 8:52 UTC (permalink / raw)
To: lm-sensors
Hi Rudolf, Alexander,
> I think I know what happen. The chip is not used at all.
> You should have there W83792AD on board. Can you check?
> It should be square with like total 48legs. If yes I will
> contact Asus and ask them how to unhide it.
Indeed, the manual for the Asus P5MT-M mentions a Winbond W83792D chip
for voltage and fan monitoring. They don't mention temperature, but
they do mention the existence of a multiplexer in front of the SMBus.
Without additional information regarding this multiplexer, there's
nothing we can do.
That being said, I don't think Alexander ever provided the full output
of sensors-detect nor any output of i2cdetect, so we don't even know
for sure is the W83792D/AD chip is visible on the bus or not. But we
know that the SPD EEPROMs were.
Alexander, can you please provide the full output of sensors-detect?
--
Jean Delvare
^ permalink raw reply [flat|nested] 6+ messages in thread* [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution
2006-01-27 21:50 [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution Rudolf Marek
2006-01-28 8:52 ` Jean Delvare
@ 2006-01-28 14:05 ` Rudolf Marek
2006-01-31 4:10 ` Alexander Dobin
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Rudolf Marek @ 2006-01-28 14:05 UTC (permalink / raw)
To: lm-sensors
Jean Delvare wrote:
> Hi Rudolf, Alexander,
>
>
>>I think I know what happen. The chip is not used at all.
>>You should have there W83792AD on board. Can you check?
>>It should be square with like total 48legs. If yes I will
>>contact Asus and ask them how to unhide it.
>
>
> Indeed, the manual for the Asus P5MT-M mentions a Winbond W83792D chip
> for voltage and fan monitoring. They don't mention temperature, but
> they do mention the existence of a multiplexer in front of the SMBus.
> Without additional information regarding this multiplexer, there's
> nothing we can do.
Maybe it can be "fixed" by BIOS update?
Alexander if it is possible can you try that? (And if it is not too much work)
Thanks,
regards
Rudolf
^ permalink raw reply [flat|nested] 6+ messages in thread* [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution
2006-01-27 21:50 [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution Rudolf Marek
2006-01-28 8:52 ` Jean Delvare
2006-01-28 14:05 ` Rudolf Marek
@ 2006-01-31 4:10 ` Alexander Dobin
2006-01-31 21:03 ` Jean Delvare
2006-02-01 0:12 ` [lm-sensors] wrong readings for w83627ehf on p5mt-m - SUCCESS Alexander Dobin
4 siblings, 0 replies; 6+ messages in thread
From: Alexander Dobin @ 2006-01-31 4:10 UTC (permalink / raw)
To: lm-sensors
Hello, Rudolf and Jean,
you are right - there is w83792ad chip on board.
I am sorry I did not see it - but the lm_sensors did not even probe
for it (see below). Please let me know if I am doing something wrong.
I have just re-installed Windows, will send the SpeedFan
and Asus info tomorrow.
Thanks a lot,
Alex
------------------------------------------------------------------
i2cdetect -l
i2c-0 unknown SMBus I801 adapter at 0400 Algorithm
unavailable
---------------------------------------------------------------------
i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX 08 XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: 30 XX XX XX 34 XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX 44 XX XX XX XX XX XX XX XX XX XX XX
50: 50 XX XX XX 54 XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX
-------------------------------------------------------------
# sensors-detect revision 1.393 (2005/08/30 18:51:18)
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):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel ICH7
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-i801' 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 not loaded. Do you want to load it now? (YES/no):
Module loaded succesfully.
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: SMBus I801 adapter at 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x30
Client found at address 0x34
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x54
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
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):
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 `Winbond W83697HF'
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... Failed!
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):
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! (0x88)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83687THF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x88)
Probing for `Winbond W83L517D Super IO'
Failed! (0x88)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Success... found at address 0x0290
Do you want to scan for secondary Super I/O sensors? (YES/no):
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 `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus I801 adapter at 0400'
Busdriver `i2c-i801', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus I801 adapter at 0400'
Busdriver `i2c-i801', I2C address 0x54
Chip `SPD EEPROM' (confidence: 8)
Driver `w83627ehf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627EHF/EHG Super IO Sensors' (confidence: 9)
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)?
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
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-i801
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
modprobe w83627ehf
# 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):
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
On 1/28/06, Rudolf Marek <r.marek at sh.cvut.cz> wrote:
>
> Jean Delvare wrote:
> > Hi Rudolf, Alexander,
> >
> >
> >>I think I know what happen. The chip is not used at all.
> >>You should have there W83792AD on board. Can you check?
> >>It should be square with like total 48legs. If yes I will
> >>contact Asus and ask them how to unhide it.
> >
> >
> > Indeed, the manual for the Asus P5MT-M mentions a Winbond W83792D chip
> > for voltage and fan monitoring. They don't mention temperature, but
> > they do mention the existence of a multiplexer in front of the SMBus.
> > Without additional information regarding this multiplexer, there's
> > nothing we can do.
>
> Maybe it can be "fixed" by BIOS update?
>
> Alexander if it is possible can you try that? (And if it is not too much
> work)
> Thanks,
>
> regards
> Rudolf
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060131/cce3ae2a/attachment.html
^ permalink raw reply [flat|nested] 6+ messages in thread* [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution
2006-01-27 21:50 [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution Rudolf Marek
` (2 preceding siblings ...)
2006-01-31 4:10 ` Alexander Dobin
@ 2006-01-31 21:03 ` Jean Delvare
2006-02-01 0:12 ` [lm-sensors] wrong readings for w83627ehf on p5mt-m - SUCCESS Alexander Dobin
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2006-01-31 21:03 UTC (permalink / raw)
To: lm-sensors
Hi Alexander,
> you are right - there is w83792ad chip on board.
> I am sorry I did not see it - but the lm_sensors did not even probe
> for it (see below). Please let me know if I am doing something wrong.
Asus has the habit to hide the W83792D/AD chip on their boards by
multiplexing the SMBus using arbitrary GPIO pins. This is why
sensors-detect fails to even see the chip.
We need additional information from Asus to work it out. They helped
Rudolf Marek a few times before already, so hopefully they'll help
again.
Thanks,
--
Jean Delvare
^ permalink raw reply [flat|nested] 6+ messages in thread* [lm-sensors] wrong readings for w83627ehf on p5mt-m - SUCCESS
2006-01-27 21:50 [lm-sensors] wrong readings for w83627ehf on p5mt-m - solution Rudolf Marek
` (3 preceding siblings ...)
2006-01-31 21:03 ` Jean Delvare
@ 2006-02-01 0:12 ` Alexander Dobin
4 siblings, 0 replies; 6+ messages in thread
From: Alexander Dobin @ 2006-02-01 0:12 UTC (permalink / raw)
To: lm-sensors
Hello, Jean and Rudolf,
I have flashed the BIOS with most recent ASUS update 0204
(of Jan 25) and lm_sensors immediatly detected the w83792d chip,
and I am getting out good numbers!
Thank you very much for this solution!
I am sorry I had you spend time on the EHF chip which apparently
does not work.
I actually had my BIOS flashed before I started this work (it was 0203), but
it looks like ASUS just put in the right updates. What are the chances of
that?
I am very happy with the results, but
please let me know if you need me to do anything else,
Again, thanks a lot for your help,
Alex
From sensors:
w83792d-i2c-0-2f
Adapter: SMBus I801 adapter at 0400
VCoreA: +1.24 V (min = +1.40 V, max = +1.60 V) ALARM
VCoreB: +1.24 V (min = +1.40 V, max = +1.60 V) ALARM
VIN0: +3.39 V (min = +3.20 V, max = +3.39 V)
VIN1: +3.14 V (min = +3.09 V, max = +3.30 V)
VIN2: +1.48 V (min = +1.39 V, max = +1.49 V)
VIN3: +1.79 V (min = +2.59 V, max = +2.64 V) ALARM
5VCC: +5.12 V (min = +4.73 V, max = +5.23 V)
5VSB: +4.99 V (min = +4.73 V, max = +5.23 V)
VBAT: +3.04 V (min = +2.85 V, max = +3.14 V)
Fan1: 0 RPM (min = 0 RPM, div = 32)
Fan2: 2678 RPM (min = 0 RPM, div = 4)
Fan3: 2280 RPM (min = 0 RPM, div = 4)
Fan4: 0 RPM (min = 0 RPM, div = 32)
Fan5: 0 RPM (min = 0 RPM, div = 32)
Fan6: 0 RPM (min = 0 RPM, div = 2)
Fan7: 0 RPM (min = 0 RPM, div = 32)
Temp1: +30.0?C (high = +127.0?C, hyst = +0.0?C)
Temp2: +32.5?C (high = +80.0?C, hyst = +75.0?C)
Temp3: +127.0?C (high = +80.0?C, hyst = +75.0?C) ALARM
chassis: Chassis intrusion detection ALARM
From sensors-detect:
Next adapter: SMBus I801 adapter at 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Success!
(confidence 7, driver `w83792d'), other addresses: 0x4b 0x4f
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8712F'... Failed!
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4b
Probing for `National Semiconductor LM75'... Failed!
Probing for `National Semiconductor LM77'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Probing for `National Semiconductor LM92'... Failed!
Probing for `National Semiconductor LM76'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4f
Probing for `National Semiconductor LM75'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
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 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
(confidence 1, driver `smbus-arp')
Client found at address 0x71
On 1/31/06, Jean Delvare <khali at linux-fr.org> wrote:
>
> Hi Alexander,
>
> > you are right - there is w83792ad chip on board.
> > I am sorry I did not see it - but the lm_sensors did not even probe
> > for it (see below). Please let me know if I am doing something wrong.
>
> Asus has the habit to hide the W83792D/AD chip on their boards by
> multiplexing the SMBus using arbitrary GPIO pins. This is why
> sensors-detect fails to even see the chip.
>
> We need additional information from Asus to work it out. They helped
> Rudolf Marek a few times before already, so hopefully they'll help
> again.
>
> Thanks,
> --
> Jean Delvare
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060201/b1cc115e/attachment.html
^ permalink raw reply [flat|nested] 6+ messages in thread