From: rhp.lpt@gmail.com (rhp)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] no sensors found beyond eeproms - OEM laptop -
Date: Fri, 16 Sep 2005 09:48:32 +0000 [thread overview]
Message-ID: <a2967b6d0509160047501715a8@mail.gmail.com> (raw)
In-Reply-To: <a2967b6d05090101374c7f1294@mail.gmail.com>
16-sep-05
Hello Jean:
I guess that settles it. I'll just have to live with what ACPI offers.
Many thanks for your help.
Brgds
Bob
On 9/15/05, Jean Delvare <khali@linux-fr.org> wrote:
>
> Hi Bob,
>
> > I already have the thermal_zone:
> > ls /proc/acpi/thermal_zone/THM0/
> > cooling_mode polling_frequency state temperature trip_points
> >
> > Additionally, GKRELLM recognizes and displays the cpu temperature.
>
> Most likely it reads it straight from
> /proc/acpi/thermal_zone/THM0/temperature.
>
> > However, I tried your suggestion:
> >
> > 45 torus:~> sudo modprobe thermal
> > FATAL: Module thermal not found.
> >
> > (So I guess the thermal zone is set up on this machine using a different
> > module?).
>
> No, it simply means that you have it built into your kernel. If not, you
> wouldn't have a /proc/acpi/thermal_zone/THM0 directory.
>
> > 49 torus:~> sudo i2cdump 0 0x6a
> > (...)
> > 50 torus:~> sudo i2cdump 0 0x10
>
> No chances these were hardware monitoring chips with such addresses.
>
> > In reviewing the previous 'sensors-detect' output I noticed that it found
> > a "sensor" but that it is flagged 'no hardware monitoring capabilites':
>
> It found a Super-I/O chip rather than a sensor. We have sensors-detect
> list these even when they do not include sensors so that we don't have
> to continuously check whether unrecognized Super-I/O chips fall into
> that category when people report about them.
>
> > There is no 'Hardware Monitor' section in the BIOS.
>
> This is well in line with the lack of lm_sensors-supported chip.
>
> I don't think there is anything more to be tried on this system, ACPI
> seems to be your only monitoring information source. It's not as
> powerful as what lm_sensors usually offers, but still better than
> nothing at all.
>
> --
> Jean Delvare
>
--
rhp.lpt@gmail.com
prev parent reply other threads:[~2005-09-16 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 10:37 [lm-sensors] no sensors found beyond eeproms - OEM laptop - rhp
2005-09-13 19:12 ` [lm-sensors] no sensors found beyond eeproms - OEM laptop Rudolf Marek
2005-09-15 7:26 ` [lm-sensors] no sensors found beyond eeproms - OEM laptop - rhp
2005-09-15 14:16 ` Jean Delvare
2005-09-16 9:48 ` rhp [this message]
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=a2967b6d0509160047501715a8@mail.gmail.com \
--to=rhp.lpt@gmail.com \
--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.