From: Owl <owl@umail.ru>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] coretemp output changed after loading acpi_cpufreq
Date: Wed, 09 Feb 2011 17:12:00 +0000 [thread overview]
Message-ID: <4D52CAE0.30002@umail.ru> (raw)
In-Reply-To: <4D526303.6060506@umail.ru>
09.02.2011 19:06, Philip Pokorny пишет:
> Can you also read fan speeds? Is there a fan on the CPU? Some Atom
> systems have a fan on the northbridge but not on the CPU itself.
>
> Are there any other temperature sensors in the system for comparison?
At this time - no. We wait adding support of Fintek F71869FG chip (which
is in Hans TODO list).
Anyway, I think it is not root of problem, because my system is fanless.
MB - Jetway NC9C-550-LF - http://www.jetwaycomputer.com/NC9C.html
> > gentoo ~ # modprobe acpi_cpufreq
> > gentoo ~ # sensors
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Core 0: +37.0°C (crit = +100.0°C)
> >
> > coretemp-isa-0001
> > Adapter: ISA adapter
> > Core 1: +41.0°C (crit = +100.0°C)
> >
> > It's normal?
> > I think, second output is much closer to BIOS values.
>
> Again, if we knew more about other sensors or fans in the system, this
> might be explained by acpi also stopping the fan when the CPU is idle
> because CPU power is known to be so low and without a fan, thermal
> margins are stil met (100degC)
If I run (after reboot), for example, cpuburn - and run commands, liste
above, I have got same results - coretemp get values, that about 2 time
more.
> If you don't have sensors, can you simply look or listen to the system
> when you load the acpi-cpufreq module? Does anything change?
No.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2011-02-09 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 9:48 [lm-sensors] coretemp output changed after loading acpi_cpufreq Owl
2011-02-09 10:19 ` Jean Delvare
2011-02-09 14:04 ` Owl
2011-02-09 16:06 ` Philip Pokorny
2011-02-09 17:12 ` Owl [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=4D52CAE0.30002@umail.ru \
--to=owl@umail.ru \
--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.