From: npfdd@gmx.ch (Daniel Schregenberger)
To: lm-sensors@vger.kernel.org
Subject: lmsensors-CVS on 2.6.0-test10
Date: Thu, 19 May 2005 06:24:27 +0000 [thread overview]
Message-ID: <1070143270.4320.20.camel@localhost> (raw)
In-Reply-To: <20031126190459.724240ad.npfdd@gmx.net>
On Sat, 2003-11-29 at 22:39, Jean Delvare wrote:
> > I got it working!
> > All I had to do was to include ISA support in the kernel. (in the
> > meantime I switched to test11)
>
> You are also invited to update your local lm_sensors2 CVS repository.
> We've been fixing a couple of problems these last few days.
I did this right before I started. On the last try sensors gave me
segfaults no matter what modules were loaded, but now it's ok.
> > Now I load the following modules:
> > w83781d, i2c_sensor, i2c_dev, i2c_isa, i2c_i801, i2c_core
> > and get these results from sensors:
[...]
> > Now I'll have to find the proper settings in the conf file for my
> > board.
>
> That's the least to say. Looks like you don't have a config file at all.
> Make sure you have /etc/sensors.conf. If not, copy it from
> lm_sensors2/etc/sensors.conf.eg. It should be a lot better (both labels
> and values).
You're right, I don't have one. :)
I remember seeing a post on the web by someone with the same board as
me. I think I'll search my history and use this as a starting
configuration.
> > Some strange things in the above listing are: fan3 is the power
> > supply and corresponds exactly with the real values but the processor
> > fan is not listed. Maybe because my BIOS always complains it "failed"?
> > It rotates very slow since I exchanged the Intel boxed for a more
> > silent one. But it definately rotates. :)
>
> Then you want to play with divisors. Slower fans need increased
> divisors. If it's very slow, you need a very big divisor. In this case
> it would be fan2 (since fan1 already as max divisor and still doesn't
> show any value).
OK. Thanks for the hint. I'll try this.
> > And I don't know what temperature belongs to CPU or mainboard and
> > what's the third?
>
> Usually, temp1 is the chipset internal temperature, which is considered
> to be your motherboard temperature. temp2 would be your CPU here, you
> can run some compilation job or even cpuburn to make sure (the CPU
> temperature will raise quickly). temp3 is probably not wired to
> anything, 208 is a common value in this case.
OK. Thanks. I think this conforms with my BIOS, there are also onyl 2
temperatures as far as I remember. And yes, I tried it: temp2 is my
CPU...it's also indicated in the output but I didn't realize it at
first.
-- Daniel
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 lmsensors-CVS on 2.6.0-test10 Daniel Schregenberger
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Daniel Schregenberger
2005-05-19 6:24 ` Daniel Schregenberger [this message]
2005-05-19 6:24 ` Daniel Schregenberger
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=1070143270.4320.20.camel@localhost \
--to=npfdd@gmx.ch \
--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.