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] Flex Scanner Jammed Problem
Date: Thu, 10 Aug 2006 08:42:38 +0000	[thread overview]
Message-ID: <20060810104238.1976d0d5.khali@linux-fr.org> (raw)
In-Reply-To: <1064332995.5787.33.camel@nils>

> If I run sensors  v2.10.0 with the libsensors v2.8.7, the parser works
> correctly with the original sensors.conf input file.  I wonder if there
> is a problem with where it is being compiled...

All the parsing code is in the library, "sensors" itself only queries
for data and print it. So the version of "sensors" shouldn't matter at
all.

Indeed there seems to be a problem at compilation time, but I don't
have any idea on what could cause that much trouble, given that you use
the same version of flex everyone does. Unless your distribution has
some additional patch applied?

> So right now I have sensors 2.10.0 running with either libsensors 2.8.7
> or 2.10.0.  in either case I am getting weird sensors readings....  Most
> voltages read 4.08 V, and the fans and temps are not returning any
> values. 

Could be that your chip isn't properly wired, but I wouldn't trust
libsensors much given the trouble you have with the configuration file
parsing. Also, I suppose that the values reported were correct before
the kernel update? Please provide the output of:
  systool -c hwmon -v

-- 
Jean Delvare


  parent reply	other threads:[~2006-08-10  8:42 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 flex scanner jammed problem Emperor
2005-05-19  6:24 ` Emperor
2005-05-19  6:24 ` Emperor
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Emperor
2005-05-19  6:24 ` Emperor
2005-05-19  6:24 ` Jean Delvare
2006-08-02 14:48 ` [lm-sensors] Flex Scanner Jammed Problem Calabro, Anthony
2006-08-02 16:15 ` Jean Delvare
2006-08-02 16:38 ` Calabro, Anthony
2006-08-02 16:47 ` Calabro, Anthony
2006-08-02 17:35 ` Calabro, Anthony
2006-08-03  8:49 ` Jean Delvare
2006-08-03 13:56 ` Calabro, Anthony
2006-08-03 15:40 ` Jean Delvare
2006-08-03 16:28 ` Calabro, Anthony
2006-08-03 16:40 ` Mark M. Hoffman
2006-08-04  7:39 ` Jean Delvare
2006-08-09 14:14 ` Calabro, Anthony
2006-08-09 17:13 ` Jean Delvare
2006-08-09 17:26 ` Calabro, Anthony
2006-08-09 20:09 ` Calabro, Anthony
2006-08-10  8:35 ` Jean Delvare
2006-08-10  8:42 ` Jean Delvare [this message]
2006-08-10 13:15 ` Calabro, Anthony
2006-08-11 12:15 ` Jean Delvare
2006-08-22 17:38 ` Calabro, Anthony
2006-08-22 20:19 ` Calabro, Anthony
2006-08-23  7:21 ` Jean Delvare
2006-08-23 11:18 ` Mark M. Hoffman
2006-08-23 15:23 ` Jean Delvare
2006-08-23 15:28 ` Calabro, Anthony
2006-08-23 17:46 ` Calabro, Anthony
2006-08-23 21:04 ` Calabro, Anthony
2006-08-24  3:01 ` Mark M. Hoffman
2006-08-24  7:49 ` Jean Delvare
2006-08-24 14:52 ` Jean Delvare
2006-08-28 16:54 ` Calabro, Anthony
2006-08-28 18:42 ` Calabro, Anthony
2006-08-28 19:02 ` Jean Delvare
2006-08-28 19:17 ` 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=20060810104238.1976d0d5.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.