All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Dell Latitude D610 and 2.6.16
Date: Thu, 27 Apr 2006 18:37:07 +0000	[thread overview]
Message-ID: <20060427203707.925046cf.khali@linux-fr.org> (raw)
In-Reply-To: <20060421050124.GY14481@daedalus.andrew.net.au>

Andrew,

[Jean Delvare]
> > The result you have is consistent with the drivers you loaded (which in
> > turn sound OK for your hardware, I have a Dell Latitude D600 and I use
> > the same drivers.) The sensors program and libsensors library were
> > modified in lm_sensors 2.10.0 not to show non-sensors devices anymore
> > (at least for 2.6 kernels.) EEPROMs are not sensors so it didn't belong
> > there in the first place.

[Andrew Pollock]
> FWIW, the D600 is a vastly different beast to the D610. I made that mistake
> when I bought it.

Ah, didn't know that. I stupidly assumed that nearby numbering meant
nearby design.

[Andrew Pollock]
> So are you saying that given the drivers I've loaded, there's nothing to
> report on?

Yes, that's what I think, and said.

Your best chance for hardware monitoring on this laptop is ACPI
(fan, ec and thermal). Load all available acpi modules and see
in /proc/acpi/{embedded_controller,fan,thermal_zone} if there's any
interesting data to be found.

On my D600, embedded_controller and fan are empty directories, but
thermal_zone has some interesting files. I can get the system
temperature, a status flag and a critical temperature limit (which I can
also set). That's a bit cheap and inconvenient compared to what
lm_sensors can offer, but that's much better than nothing at all.

There's some documentation available about acpi/thermal_zone here:
http://acpi.sourceforge.net/documentation/thermal.html

Hope that helps,
-- 
Jean Delvare


  parent reply	other threads:[~2006-04-27 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  5:01 [lm-sensors] Dell Latitude D610 and 2.6.16 Andrew Pollock
2006-04-27  7:57 ` Jean Delvare
2006-04-27 15:51 ` Andrew Pollock
2006-04-27 18:37 ` Jean Delvare [this message]
2006-04-27 19:39 ` Andrew Pollock
2006-04-27 20:44 ` Jean Delvare

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=20060427203707.925046cf.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.