From: Matthew <jackdachef@gmail.com>
To: "Bart Van Assche" <bart.vanassche@gmail.com>
Cc: torvalds@linux-foundation.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Rudolf Marek" <r.marek@assembler.cz>,
"Gene Heskett" <gene.heskett@gmail.com>,
"Len Brown" <lenb@kernel.org>
Subject: Re: Linux 2.6.25
Date: Sun, 20 Apr 2008 14:02:50 +0200 [thread overview]
Message-ID: <e85b9d30804200502p25842ec2i712da9e388c08e87@mail.gmail.com> (raw)
In-Reply-To: <e85b9d30804190322o703d3b20se22eb6b5e82bae39@mail.gmail.com>
> sure, I'll test-drive the vanilla-kernel, too>> thanks
ok, tested the vanilla-kernel this morning and it shows the exact hightemperatures (with CONFIG_THERMAL=y)
I've got a question:
when trying to disable thermal it just sits there & won't change:<*> Hardware Monitoring support ---> -*- Generic Thermal sysfs driver --->
it seemingly depends on other things:Selected by: ACPI_THERMAL && !X86_VOYAGER && ACPI && ACPI_PROCESSOR
is it safe to disable acpi_processor and acpi or CONFIG_THERMAL ingeneral ? or will it burn down my box ? ;)
I'm asking this because it says/writes:CONFIG_ACPI_THERMAL: │ │ │ │ This driver adds support for ACPI thermal zones. Most mobile and │ │ some desktop systems support ACPI thermal zones. It is HIGHLY │ │ recommended that this option be enabled, as your processor(s) │ │ may be damaged without it.
thanks
MatЪТХ╨{.nг+┴╥÷╝┴╜├+%┼кЪ╠Ищ╤\x17╔┼wЪ╨{.nг+┴╥╔┼{╠ЧG╚²ИЪ┼{ay╨\x1dй┤з≥К,j\a╜╒fё╒╥h ▐О│ЙЪ▒ЙГz_Х╝\x03(╜И ▌┼щ╒j"²З\x1a╤^[m╖ЪЪ╬\a╚ЧG╚²ИЪ╒╦?≥╗Х╜з&ёЬ╖~▐А╤iO∙Ф╛z╥ vь^\x14\x04\x1a╤^[m╖ЪЪц\fЪ╤ЛЪ╒╦?√I╔
next prev parent reply other threads:[~2008-04-20 12:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 15:37 Matthew
2008-04-18 15:43 ` Linus Torvalds
2008-04-18 16:02 ` Matthew
2008-04-18 19:38 ` Cyrill Gorcunov
2008-04-18 20:03 ` Cyrill Gorcunov
2008-04-19 3:05 ` Rene Herman
2008-04-19 3:20 ` Rene Herman
2008-04-19 6:17 ` Cyrill Gorcunov
2008-04-19 10:18 ` Matthew
2008-04-19 10:22 ` Matthew
2008-04-20 12:02 ` Matthew [this message]
2008-04-24 3:36 ` Len Brown
2008-04-18 16:24 ` Gene Heskett
2008-04-18 16:27 ` Gene Heskett
2008-04-18 19:18 ` Bart Van Assche
2008-04-18 20:24 ` Jiri Slaby
2008-04-18 20:50 ` Rudolf Marek
2008-04-19 1:51 ` Linux 2.6.25 (coretemp reads high temperatures) Len Brown
2008-04-21 16:10 ` Thomas Bächler
2008-04-21 16:28 ` Matthew
2008-04-21 17:07 ` Fwd: " Matthew
2008-04-22 9:26 ` Matthew
2008-04-23 8:43 ` Maxim Levitsky
2008-04-28 18:19 ` Kasper Sandberg
2008-04-29 13:07 ` Thomas Renninger
2008-04-29 15:08 ` Jean Delvare
2008-04-29 22:14 ` Rudolf Marek
2008-04-29 22:58 ` Matthew
2008-04-30 6:10 ` Jean Delvare
2008-04-30 14:46 ` Henrique de Moraes Holschuh
2008-04-30 14:50 ` Rudolf Marek
2008-04-30 15:18 ` Jean Delvare
2008-05-02 20:35 ` Pavel Machek
2008-04-30 0:11 ` Kasper Sandberg
2008-04-30 6:20 ` Jean Delvare
2008-04-30 14:51 ` Henrique de Moraes Holschuh
2008-04-30 15:28 ` Jean Delvare
2008-05-02 20:36 ` Pavel Machek
2008-05-04 17:42 ` Henrique de Moraes Holschuh
2008-05-05 13:45 ` Pavel Machek
2008-05-02 20:35 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-04-17 3:32 Linux 2.6.25 Linus Torvalds
2008-04-17 4:22 ` david
2008-04-17 18:56 ` Rafael J. Wysocki
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=e85b9d30804200502p25842ec2i712da9e388c08e87@mail.gmail.com \
--to=jackdachef@gmail.com \
--cc=bart.vanassche@gmail.com \
--cc=gene.heskett@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.marek@assembler.cz \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®