public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Steven A. DuChene" <linux-clusters@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: no config opt for k8temp in 3.6.11
Date: Fri, 4 Jan 2013 21:35:26 +0100	[thread overview]
Message-ID: <20130104203525.GA24247@x1.alien8.de> (raw)
In-Reply-To: <19235668.1357309514415.JavaMail.root@mswamui-valley.atl.sa.earthlink.net>

On Fri, Jan 04, 2013 at 09:25:14AM -0500, Steven A. DuChene wrote:
> I have a few systems with AMD processors. One is a AMD Phenom II based
> system which uses a k10temp kernel module to get the CPU temperature.
> Another system has an Athlon64 processor which apparently is supposed
> to use a k8temp module to do the same thing. I have built a 3.6.11
> kernel for each system that otherwise runs OpenSuSE-11.X. On the
> Phenom system the k10temp module is gets built and performs as
> expected. However on the Atlnon system even though I see the k8temp.c
> source file in the drivers/hwmon directory there does not seem to be
> a way in the kernel config files available from the 3.6.11 kernel
> sources to actually select that the k8temp module should be built. Is
> this some oversight in the makeup of the kernel config files or am I
> missing something obvious?

That's strange, I can select all the AMD power drivers on 3.6.11:

$ grep -E "^CONFIG_SENSORS" .config
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m

Can you do 'make mrproper' and try regenerating your config? But
remember, mrproper will remove your .config so you might want to save
that upfront in case you need it.

HTH.

-- 
Regards/Gruss,
Boris.

  reply	other threads:[~2013-01-04 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 14:25 no config opt for k8temp in 3.6.11 Steven A. DuChene
2013-01-04 20:35 ` Borislav Petkov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-05  4:15 Steven A. DuChene

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=20130104203525.GA24247@x1.alien8.de \
    --to=bp@alien8.de \
    --cc=linux-clusters@mindspring.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox