From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Loaded Modules but 'No sensors found'
Date: Fri, 13 Jan 2006 22:29:35 +0000 [thread overview]
Message-ID: <20060113232935.26f080f5.khali@linux-fr.org> (raw)
In-Reply-To: <W5422813796241071136954279@webmail2>
Hi Kevin,
> > > I've followed all instructions I could find. It seems as if all modules get
> > > detected and load fine. Yet running 'sensors returns 'No sensors found'. Any
> > > thoughts?????
> >
> > I guess: unload eeprom, i2c-amd756, and i2c-amd8111; then try again. Your
> > hardware monitor (w83627hf or some such) is probably visible through i2c-isa
> > alone. If that doesn't work, please send the output from sensors-detect.
>
> I haven't had the chance yet to try this but I did try a new kernel and
> that worked.
> I tried kernel 2.6.15 w/ gentoo and ck patches. I will try you above
> suggestion and also vanilla kernel 2.6.15 for comparison.
My own guess is the conflict between PNPACPI and the w83627hf driver,
which is known to have affected the Linux kernels from 2.6.10 to 2.6.14:
http://bugzilla.kernel.org/show_bug.cgi?id@14
If I am right, the only way to get it to work on a 2.6.14.x kernel
would be to disable the PNPACPI configuration option (pnpacpi=off on
the bootloader command line will do too.)
2.6.15 vanilla should work just fine too.
Hope that helps,
--
Jean Delvare
next prev parent reply other threads:[~2006-01-13 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 4:37 [lm-sensors] Loaded Modules but 'No sensors found' embree
2006-01-13 3:58 ` Mark M. Hoffman
2006-01-13 19:43 ` Kevin Embree
2006-01-13 22:22 ` Jean Delvare
2006-01-13 22:29 ` Jean Delvare [this message]
2006-01-14 4:09 ` Mark M. Hoffman
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=20060113232935.26f080f5.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.