All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] ASUS P6T, 2.6.31-14, no pwm devices
Date: Mon, 16 Nov 2009 09:23:55 +0000	[thread overview]
Message-ID: <20091116102355.7833ef3a@hyperion.delvare> (raw)
In-Reply-To: <8c4290000911141138v161593b0u785895e5a7960587@mail.gmail.com>

On Sun, 15 Nov 2009 23:08:01 +0100, Reinhard Nissl wrote:
> Hi,
> 
> Am 15.11.2009 22:53, schrieb Jean Delvare:
> 
> >> Looks like gkrellm doesn't use libsensors so the location matters
> >> until it supports both locations too.
> > 
> > Recent versions of gkrellm (2.3.1 and later) do support libsensors, if
> > built properly.
> 
> openSUSE 11.2 provides 2.3.1. Changelog says, they upgraded to
> 2.3.1 about 2 years ago. But ldd /usr/gkrellm doesn't mention
> libsensors, although openSUSE 11.2 provides both v3 and v4.
> 
> So, looks like poor me is using a gkrellm without libsensors support.

Indeed. I've just tested with openSUSE 11.1 and I see the same, ldd
doesn't list libsensors and the sensor labels suggest libsensors isn't
used. It is odd that nobody noticed so far.

Would you please report this bug on bugzilla.novell.com?

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2009-11-16  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-14 19:38 [lm-sensors] ASUS P6T, 2.6.31-14, no pwm devices Matt Sheumack
2009-11-15 20:23 ` Reinhard Nissl
2009-11-15 21:26 ` Jean Delvare
2009-11-15 21:33 ` Reinhard Nissl
2009-11-15 21:53 ` Jean Delvare
2009-11-15 22:08 ` Reinhard Nissl
2009-11-16  9:23 ` Jean Delvare [this message]
2009-11-16 16:02 ` Luca Tettamanti
2009-11-24  8:25 ` 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=20091116102355.7833ef3a@hyperion.delvare \
    --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.