All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to
Date: Tue, 09 Mar 2010 08:48:47 +0000	[thread overview]
Message-ID: <20100309094847.2ae9bdb8@hyperion.delvare> (raw)
In-Reply-To: <20100305222015.GR11436@alpha.zimage.com>

Hi Phillip,

On Mon, 8 Mar 2010 13:43:14 -0800, Phillip Pi wrote:
> In older Kernels like v2.6.30, did this conflict happen too? I only 
> remember seeing inaccurate values like for voltages. Speaking of 
> voltages, which part is responsibile for voltages showing that I don't 
> have in 2.6.32, but did in 2.6.30?

Please be specific. What chip is it, which voltages are missing?

Remember that the output of sensors is influenced by the contents of
libsensors configuration files (/etc/sensors.conf, /etc/sensors3.conf
and/or /etc/sensors.d/* depending on your libsensors version and
distribution choices.)

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2010-03-09  8:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 22:20 [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to Phillip Pi
2010-03-06  0:02 ` Luca Tettamanti
2010-03-08 20:57 ` Luca Tettamanti
2010-03-08 21:10 ` Phillip Pi
2010-03-08 21:17 ` Jean Delvare
2010-03-08 21:28 ` Luca Tettamanti
2010-03-08 21:28 ` Phillip Pi
2010-03-08 21:31 ` Phillip Pi
2010-03-08 21:34 ` Luca Tettamanti
2010-03-08 21:38 ` Jean Delvare
2010-03-08 21:39 ` Phillip Pi
2010-03-08 21:43 ` Phillip Pi
2010-03-08 21:44 ` Luca Tettamanti
2010-03-09  8:40 ` Jean Delvare
2010-03-09  8:45 ` Jean Delvare
2010-03-09  8:48 ` Jean Delvare [this message]
2010-03-09  9:05 ` Phillip Pi
2010-03-09  9:30 ` Jean Delvare
2010-03-09 14:20 ` Phillip Pi
2010-03-09 16:35 ` 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=20100309094847.2ae9bdb8@hyperion.delvare \
    --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.