From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: W83627HF SuperIO support in lm_sensors
Date: Thu, 19 May 2005 06:24:20 +0000 [thread overview]
Message-ID: <20030929214248.5c0c86bc.khali@linux-fr.org> (raw)
In-Reply-To: <20030929180436.GB1779@pua.nirvana>
> On Mon, Sep 29, 2003 at 05:49:47PM +0200, Alfredo Milani-Comparetti
> wrote:
> > The main problem is that the W83627HF module is not included amongst
> > the loadable modules that can be MODPROBEd with your latest kernel
> > for RH9. This leads to a SENSORS-DETECT routine that suggests to
> > load W83627HF, which, in turn, is actually unavailable.
> > At present I've reverted to the original kernel from RH9 and written
> > by hand a PERL script which enables some bits in the SuperIO chip in
> > order to let it be found on the SMBus, but I think it would be nice
> > to be able to find all available modules for all known chips :-)
>
> I used the kernel-patching method described in the lm_sensors 2.8.0
> documentation. Could you try to do the same, to reproduce whether the
> problem is in the packaging or in the upstream sources?
Known "problem" (much more of a feature actually). Our patching script
does only include the more stable drivers. Other drivers are only
available when you compile modules outside of the kernel tree. Our
sensors-detect script doesn't know about that of course, and detects
whatever it can.
If you want more drivers, either tweak the FILES and Config.in files in
mkpatch, or build the modules directly in the lm_sensors directory
instead of patching the kernel.
Hope that helps.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 W83627HF SuperIO support in lm_sensors Axel Thimm
2005-05-19 6:24 ` Axel Thimm
2005-05-19 6:24 ` Alfredo Milani-Comparetti
2005-05-19 6:24 ` Jean Delvare [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Axel Thimm
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=20030929214248.5c0c86bc.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.