public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] LMSENSORS: 2.6.26-rc,	enabling ACPI Termal Zone support costs sensors
Date: Sun, 22 Jun 2008 09:30:09 +0200	[thread overview]
Message-ID: <485DFF81.9080707@hhs.nl> (raw)
In-Reply-To: <485DA11C.7050906@keyaccess.nl>

Rene Herman wrote:
> Good day.
> 
> On 2.6.26-rc and perhaps earlier, when I enable the ACPI Thermal Zone 
> support (CONFIG_ACPI_THERMAL) I see in dmesg:
> 
> ACPI: LNXTHERM:01 is registered as thermal_zone0
> ACPI: Thermal Zone [THRM] (56 C)
> 
> My /sys/class/hwmon/hwmon0 (a W83782D chip) becomes hwmon1, there's a 
> new /sys/class/hwmon/hwmon0 and "sensors -s" craps out with:
> 
> # sensors -s
> Can't access procfs/sysfs file
> Kernel interface access error
> For 2.6 kernels, make sure you have mounted sysfs and libsensors
> was compiled with sysfs support!
> 
> # sensors --version
> sensors version 2.10.6 with libsensors version 2.10.6
> 
> This is the slackware 12.1 (recent) standard version. What's wrong?
> 
> In case it's useful, my /etc/sensors.conf is at:
> 
> http://members.home.nl/rene.herman/sensors.conf
> 

I'm pretty sure this caused by your lm_sensors using space being too old to
support the new thermalzone stuff.

<Correction that should ofcourse read "userspace" not "using space", so the 
correct reply I was trying to send is>:

I'm pretty sure this caused by your lm_sensors using space being too old to
support the new thermalzone stuff. You need atleast 3.0.2 to support the
thermalzone driver.

Regards,

Hans


      parent reply	other threads:[~2008-06-22  7:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22  0:47 LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors Rene Herman
2008-06-22  7:28 ` [lm-sensors] " Hans de Goede
2008-06-22 13:15   ` [REGRESSION, ABI] " Rene Herman
2008-06-22 13:23     ` Rene Herman
2008-06-22 14:29     ` [lm-sensors] [REGRESSION, ABI] " Hans de Goede
2008-06-22 15:26       ` Rene Herman
2008-06-22 18:07         ` Hans de Goede
2008-06-22 18:25           ` Rene Herman
2008-06-22 21:58             ` Rene Herman
2008-06-23  1:44               ` Zhang Rui
2008-06-23  5:21                 ` Hans de Goede
2008-06-23 10:40                 ` Rene Herman
2008-06-23 11:06                 ` Jean Delvare
2008-06-23 10:56             ` Jean Delvare
2008-06-23 17:54         ` [lm-sensors] [REGRESSION, ABI] " Len Brown
2008-06-23 19:54           ` Jean Delvare
2008-06-23 20:07           ` [lm-sensors] [REGRESSION, ABI] " Rene Herman
2008-06-23 20:24             ` Rene Herman
2008-06-22 15:43       ` Rene Herman
2008-06-23 10:08       ` Jean Delvare
2008-06-23 10:24         ` Rene Herman
2008-06-23 11:57           ` Jean Delvare
2008-06-23 12:35             ` Rene Herman
2008-06-23 13:47               ` Jean Delvare
2008-06-23 14:06                 ` Rene Herman
2008-06-23 14:31               ` Matthew Garrett
2008-06-23 17:10                 ` Rene Herman
2008-06-23 13:51             ` Hans de Goede
2008-06-22  7:30 ` Hans de Goede [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=485DFF81.9080707@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=mhoffman@lightlink.com \
    --cc=rene.herman@keyaccess.nl \
    /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