From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] 2.6.16-rc5: unreasonable temperature reported by
Date: Sat, 01 Apr 2006 12:48:26 +0000 [thread overview]
Message-ID: <20060401144826.239779e9.khali@linux-fr.org> (raw)
In-Reply-To: <44144A01.2050207@t-online.de>
Hi Harald,
> > I was about to say "No idea about this one", as it has very few
> > registers and no noticeable patterns, but that "19 34" at 0x5d reminds
> > me of the Fintek signature in my F71805F Super-I/O chip. Can you please
> > search your motherboard for a Fintek chip, presumably small?
>
> I found a small chip close to the socket for an additional fan.
> 16 pins. AFAICS it says F75387SG, but it was very hard to read
> even with a looking glass. Esp. the "S" looks suspicious.
>
> Using "fintek F75387SG" I found this on Google:
>
> http://www.fintek.com.tw/files/productfiles/F75387_025P%20datasheet.pdf
>
> BTW, my PC is an Aopen MZ915-M .
Good catch. This is, indeed, the chip that sensors-detect spotted at
address 0x2d. I just modified this script so that it now knows about
more Fintek chips. Please give it a try:
http://www2.lm-sensors.nu/%7Elm78/cvs/lm_sensors2/prog/detect/sensors-detect
It should properly identify your F75387SG/RG chip at 0x2d now.
I still don't know what is the other Fintek chip at 0x2f. Its it
doesn't match any ID I could find in the datasheets, but it's similar
enough to the F75121R and F75122R/RG ID that I'd bet for some VID
and/or GPIO chip. My contact at Fintek told me it was a "power
control", I hope to have additional information soon. Maybe you can
take a look at your motherboard again in the meantime.
So, the good news is that we now know what hardware monitoring chip you
have. This explains why the W83627THF chip was not reporting the values
you were expecting.
The bad news is that we have no driver for this chip at the moment.
I've added it to our "New drivers" page, together with a few other
Fintek chips. You'll have to wait for a driver to be written, or write
it yourself. Any amount of support (work, money, hardware...) you can
offer is likely to speed up the process.
--
Jean Delvare
next prev parent reply other threads:[~2006-04-01 12:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 16:19 [lm-sensors] 2.6.16-rc5: unreasonable temperature reported by Harald Dunkel
2006-03-12 16:40 ` Jean Delvare
2006-03-12 18:32 ` Harald Dunkel
2006-03-13 9:31 ` Jean Delvare
2006-03-18 5:14 ` Harald Dunkel
2006-03-26 9:43 ` Harald Dunkel
2006-03-31 12:35 ` Jean Delvare
2006-04-01 5:44 ` Harald Dunkel
2006-04-01 12:48 ` Jean Delvare [this message]
2006-04-01 13:59 ` Harald Dunkel
2006-04-04 18:07 ` Harald Dunkel
2006-04-04 19:49 ` Jean Delvare
2006-04-04 19:59 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 16:24 Harald Dunkel
2006-05-20 9:03 ` Jean Delvare
2006-05-26 10:46 ` Harald Dunkel
2006-05-26 12:10 ` Jean Delvare
2006-05-26 19:02 ` Harald Dunkel
2006-05-28 17:24 ` Harald Dunkel
2006-06-10 7:33 ` Harald Dunkel
2006-08-19 9:39 ` Rudolf Marek
2006-08-20 5:50 ` Harald Dunkel
2006-08-20 10:44 ` Rudolf Marek
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=20060401144826.239779e9.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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 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.