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] ITE IT8721F, IT8758E it87 standalone driver report
Date: Sat, 09 Apr 2011 08:02:25 +0000	[thread overview]
Message-ID: <20110409100225.3abaf56e@endymion.delvare> (raw)
In-Reply-To: <2610648201.20110407001722@mail.ru>

On Fri, 8 Apr 2011 22:06:48 +0400, Rebel wrote:
> Hello, Jean.
> 
> You wrote:
> 
> >> +5.00V 4.988V
> >> +12.0V 11.816V
> 
> > For these two, we would need more values from the BIOS to conclude, as
> > we have 4 candidates (in0, in1, in2 and in6.)
> 
> More values? But there is no more values in my BIOS.

I mean more samples for a given values. Often monitored values
oscillate between two or three values. On some systems you have to
leave and re-enter the monitoring screen in the BIOS to get new values,
but most of them update the values every second automatically.

> > This is simply not possible. "sensors" reads the configuration files
> > again each time to run it.
> 
> I  don't know how it can be, but before running sensors3 at first time,
> /etc/sensors.d was an empty folder, but now there is it8721.conf wich
> holds data i put into /etc/sensors.conf

Either you live in the 4th dimension, or your distribution has extra
code doing that kind of magic. The code at lm-sensors.org doesn't do
anything like this.

> > Not sure what you did exactly, but /etc/sensors.conf is not used by
> > lm-sensors 3.x if /etc/sensors3.conf is present. /etc/sensors3.conf is
> > always checked first, to make it possible to have both lm-sensors 2 and
> > lm-sensors 3 installed on a given machine (although nobody should be
> > doing this any longer.)
> 
> Here is the log of my actions:
> -   i  have  removed   old   sensors2 (apt-get remove lm-sensors) but may be
> Ubuntu hasn't deleted the old config file.
> -  i  compiled  new sensors from sources and run it without parameters
> (the output was temp1 fan1 and so on)
> - in /etc/sensors.conf i put my chip and some labels
> -  run  newly  built sensors with config /etc/srnsors.conf
> "sensors  -c  /etc/sensors.conf"  and output was with correct labels i
> put in /etc/sensors.conf
> -  i  have  deleted my chip and labesls from /etc/srnsors.conf and run
> sensors again without config, output was correct with my labels
> 
> I  think,  when  i run sensors with edited config /etc/sensors.conf it
> creates file in /etc/sensors.d. Is it right?

Our code doesn't do this, no. Your Linux distribution, maybe, but this
is the first time I hear of this.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

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

      parent reply	other threads:[~2011-04-09  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 20:17 [lm-sensors] ITE IT8721F, IT8758E it87 standalone driver report atr_temp
2011-04-07  7:37 ` Jean Delvare
2011-04-07 20:58 ` Jean Delvare
2011-04-08 18:06 ` Rebel
2011-04-09  8:02 ` Jean Delvare [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=20110409100225.3abaf56e@endymion.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.