From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Flex Scanner Jammed Problem
Date: Wed, 23 Aug 2006 15:23:59 +0000 [thread overview]
Message-ID: <20060823172359.ea597600.khali@linux-fr.org> (raw)
In-Reply-To: <1064332995.5787.33.camel@nils>
Hi Anthony, Mark,
> * Calabro, Anthony <anthony.calabro at lmco.com> [2006-08-22 16:19:55 -0400]:
> > I guess Im going to try to start over with this thread. I have solved
> > the Flex Scanner Jammed problem by going back to sensors version 2.9.0.
> > When using 2.10.0 the best I could do is get label lines to parse
> > correctly, but I never had any luck with the compute lines. I also
>
> Did you install 2.9.0 from source? Looking back at the archives, you
> actually started with 2.8.7 - it probably came with the distro.
>
> If you were able to install 2.9.0 from source, but not 2.10.0... well
> that is very strange. The scanner didn't change between those versions.
>
> Anyway, if you're still interested in trying to debug the scanner error:
> please add the flag '-d' to the last line of the Makefile. It should
> look like this:
>
> $(FLEX) -Psensors_yy -t -d $< > $@
>
> Then 'make clean' && 'make' && 'make install'. That flag will cause the
> scanner to make a lot of noise about what it's doing. Send some results
> back to this list and I'll have a look.
Another approach would be to perform a bisection. If 2.9.0 actually
works, and 2.10.0 doesn't, then a change must have broken it - even
though I just can't think of any. 2.9.0 is r2809, 2.10.0 is r3256. You
will converge after 11 iterations, should be fast enough.
> > upgraded my linux kernel from 2.6.9-34 to 2.6.9-42. In this new version
> > there is an i2c sensors update.
What update is this?
--
Jean Delvare
next prev parent reply other threads:[~2006-08-23 15:23 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 ` Jean Delvare
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
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
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 [this message]
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=20060823172359.ea597600.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.