All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reinhard Nissl <rnissl@gmx.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] ASUS P6T, 2.6.31-14, no pwm devices
Date: Sun, 15 Nov 2009 20:23:10 +0000	[thread overview]
Message-ID: <4B00632E.3050002@gmx.de> (raw)
In-Reply-To: <8c4290000911141138v161593b0u785895e5a7960587@mail.gmail.com>

Hi,

Am 14.11.2009 20:38, schrieb Matt Sheumack:

> Been scanning the recent activity around how 2.6.31 has broken fan
> control on many m/boards, and am hoping to make a contribution so this
> problem can be fixed. Given that my coding skills are limited to Fortran
> 77, best I can do is help with data and test. I've not (yet) enabled the
> "lax" workaround, so I don't know if it works. Happy to follow
> instructions from here to provide H/W input.

I recently upgraded to openSUSE 11.2 which uses kernel 2.6.31.5
looking forward to using the new hwmon driver ATK0110. But
gkrellm doesn't show the sensors, though sensors does, just like
in your report.

I wonder which sysfs layout is correct as for example coretemp
works with gkrellm. coretemp provides its temperatures below
/sys/class/hwmon/hwmon1/device/ while ATK0110 provides it below
/sys/class/hwmon/hwmon0/.

I would be glad if this could be fixed in the 2.6.31 kernel tree.

Bye.
-- 
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@gmx.de

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

  reply	other threads:[~2009-11-15 20: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 [this message]
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
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=4B00632E.3050002@gmx.de \
    --to=rnissl@gmx.de \
    --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.