mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [lm-sensors] lm-sensors 3.1.1-3 not detecting sensors on Intel DP55KG motherboard? (chip ID: 0xb473)
Date: Fri, 16 Oct 2009 09:40:51 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0910160838500.31450@p34.internal.lan> (raw)
In-Reply-To: <20091016125353.1c8795f4@hyperion.delvare>



On Fri, 16 Oct 2009, Jean Delvare wrote:

> On Fri, 16 Oct 2009 05:54:10 -0400 (EDT), Justin Piszcz wrote:
>> # ./sensors-detect
>> # sensors-detect revision 5782 (2009-10-16 10:59:16 +0200)
>> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
>> Found `Nuvoton W83677HG-I Super IO Sensors'
>>      (but no address specified)
>
> So the LPC interface to the hardware monitoring chip is disabled.
>
>> Probing for `Winbond W83791SD'...                           No
>
> You have an unknown chip at 0x2c on the SMBus. It could be a hardware
> monitoring chip... or not.
Ok..

>
> If you want me to investigate this, you can provide an I2C dump of the
> chip. Get i2cdump from the i2c-tools package, and then:
>
> # i2cdump 0 0x2c b
>
> This might confuse the chip in question though, so only try it if you
> are ready to trigger a cold reboot.

Ok, luckily it does not appear to have caused any issues:

# i2cdump 0 0x2c b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x2c, mode byte
Continue? [Y/n] y
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 80 80 80 04 7e 10    ..........????~?
20: 75 51 c0 c3 c3 80 28 2d bd 0f de 0f 3b 1d a9 16    uQ????(-????;???
30: 33 4d 4d c2 81 00 c2 00 ff ff ff e6 7b fb 41 6f    3MM??.?....?{?Ao
40: 35 90 40 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    5?@...........??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 0a a2 a2 ca    ????........????
60: 8a 8a e0 aa 33 4c 4c 5a 2d 2d 64 41 41 04 42 00    ????3LLZ--dAA?B.
70: 00 00 00 00 00 00 6c 60 f0 00 00 55 01 00 00 00    ......l`?..U?...
80: 00 00 00 00 00 00 ff ff 00 00 fb 64 64 64 00 00    ..........?ddd..
90: 00 59 59 59 00 00 00 00 00 00 00 00 00 00 00 00    .YYY............
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
#


>
>> Client found at address 0x2d
>> (...)
>> Probing for `Winbond W83627DHG'...                          Success!
>>      (confidence 8, driver `use-isa-instead')
>
> This is the SMBus access to the W83677HG. We don't have support for
> that, because LPC access is faster and was always enabled on all
> motherboards we've seen so far.
Ok..

>
> I doubt we'll ever add SMBus access support, for both performance and
> source code readability reasons. If anything, we could forcibly enable
> the device on your motherboard. But please first look for BIOS options
> and/or a BIOS update to enable the LPC interface.
I am checking now...yes all HW monitoring/etc IS enabled.

>
> Do you see any hardware monitoring information in the BIOS?
Yep, see note above.  It is enabled.

>
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>

  reply	other threads:[~2009-10-16 13:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 21:49 lm-sensors 3.1.1-3 not detecting sensors on Intel DP55KG motherboard? Justin Piszcz
2009-10-14  8:04 ` Justin Piszcz
2009-10-14 12:57   ` [lm-sensors] lm-sensors 3.1.1-3 not detecting sensors on Intel DP55KG motherboard? (chip ID: 0xb473) Justin Piszcz
2009-10-15  8:05     ` Jean Delvare
2009-10-15  8:30       ` Justin Piszcz
2009-10-15  8:52         ` Jean Delvare
2009-10-16  9:15         ` Jean Delvare
2009-10-16  9:54           ` Justin Piszcz
2009-10-16 10:53             ` Jean Delvare
2009-10-16 13:40               ` Justin Piszcz [this message]
2009-10-16 18:41                 ` Jean Delvare
2009-10-16 19:58                   ` Jean Delvare
2009-10-16 20:25                     ` Justin Piszcz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.00.0910160838500.31450@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®