From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Sensors-dectect ,
Date: Mon, 19 Oct 2009 07:14:08 +0000 [thread overview]
Message-ID: <20091019091408.77040ccc@hyperion.delvare> (raw)
In-Reply-To: <alpine.DEB.2.00.0910160554380.2841@p34.internal.lan>
Hi Lars,
On Fri, 16 Oct 2009 20:35:07 +0200, Lars Lindquist wrote:
> output from sensors-detect
> # sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
> # System: System manufacturer System Product Name
> # Board: ASUSTeK Computer INC. P7P55D
>
> 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 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'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Fintek'... Yes
> Found unknown chip with ID 0xb353
> (logical device B has address 0x290, could be sensors)
I've added detection of some new chips, please try the latest version
of sensors-detect:
http://dl.lm-sensors.org/lm-sensors/files/sensors-detect
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-10-19 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 9:54 [lm-sensors] Sensors-dectect , Justin Piszcz
2009-10-16 18:35 ` Lars Lindquist
2009-10-16 21:15 ` Justin Piszcz
2009-10-19 7:14 ` Jean Delvare [this message]
2009-11-11 18:02 ` Lars Lindquist
2009-12-02 17:01 ` Mariano Iglesias
2009-12-03 10:04 ` X3lectric
2010-01-03 10:15 ` draco
2010-02-10 19:30 ` Lars Lindquist
2010-03-11 1:06 ` ghoztdog
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=20091019091408.77040ccc@hyperion.delvare \
--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.