From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Lm92 fails to read temperature
Date: Fri, 11 Aug 2006 12:14:11 +0000 [thread overview]
Message-ID: <20060811141411.5d6902b4.khali@linux-fr.org> (raw)
In-Reply-To: <4be0d0b30608100501w67f6f43dy98b42e45daca06b5@mail.gmail.com>
Hi John,
> I've been having a problem with lm92 not reading the temperature of my
> cpu. This module was suggested by sensors-detect, but I tired
> modprobing all the lm* sensors ans still no temp. Lm92 loads fine as
> does lm_sensors, but reads a temperature of zero degrees. I know the
> problem does not lie with acpi because I've talked to devs on their
> mailing list and they explained the new way to build a dsdt file and
> that one compiled fine.
>
> There are some missing modules, but before I spend time patching the
> kernel I want to find out why I can't get a temperature.
>
> Code:
> * Loading lm_sensors modules...
> * Loading i2c-i801 ... [ ok ]
> * Loading eeprom ... [ ok ]
> * Loading smbus-arp ... [ !! ]
> * Loading smartbatt ... [ !! ]
> * Loading saa1064 ... [ !! ]
> * Loading lm92 ... [ ok ]
> * Loading pca9540 ... [ !! ]
> * Loading max6650 ... [ ok ]
These are all the most difficult chips to detect, and as a consequence,
the most frequently misdetect chips. I am fairly certain you don't have
any of these chips.
> * Initializing sensors ... [ ok
>
> Max6650 so far is the only module I've added by hand, but I've tried
> with pca9540 (pca954x) but the patch floating around isn't working.
> I've read through the documentation, but it's a little over my head.
> It seems like they are for nonthermal things.
It is, indeed, but you don't need any of these drivers anyway.
> Also, smbus seems to be going nuts in my dmesg:
>
> Code:
> i2c_adapter i2c-0: smbus word data - addr 0x4f, read 0x0000 at 0x02.
I suspect that one of the i2c busses on your system is broken, causing
sensors-detect to misdetect lots of chips. Please provide the output of:
i2cdetect -l
And then for every bus listed,
i2cdetect N
where N is a bus number (0, 1, etc...)
> It reads alll of the sys bus files over and over again. So whenever I
> access dmeg all I get is a page of these.
What is "it"?
> I've also tried editing the config file so that only those that
> succeed load, but that doesn't work either.
Your problem lies well before the configuration step.
> My computer is a Dell Dimension 8250.
What makes you think this model has a thermal sensor chip lm_sensors
can use? Most laptops don't.
--
Jean Delvare
next prev parent reply other threads:[~2006-08-11 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 12:01 [lm-sensors] Lm92 fails to read temperature John Altobelli
2006-08-11 12:14 ` Jean Delvare [this message]
2006-08-12 0:41 ` John Altobelli
2006-08-12 10:21 ` Jean Delvare
2006-08-15 1:46 ` John Altobelli
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=20060811141411.5d6902b4.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.