linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McFarland <diablod3@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: Thomas Meyer <thomas.mey@web.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc1-g3ee68c4: powernow-k7: -ENODEV
Date: Sun, 22 Jan 2006 18:12:30 -0500	[thread overview]
Message-ID: <200601221812.30580.diablod3@gmail.com> (raw)
In-Reply-To: <20060122051929.GA6093@redhat.com>

On Sunday 22 January 2006 00:19, Dave Jones wrote:
> On Sat, Jan 21, 2006 at 05:57:25PM +0100, Thomas Meyer wrote:
>  > I switched my config from up to smp support with 2 processors.
>  >
>  > trying to modprobe powernow-k7 gives me now:
>  > "
>  > cpufreq-core: trying to register driver powernow-k7
>  > cpufreq-core: adding CPU 0
>  > cpufreq-core: initialization failed
>  > cpufreq-core: no CPU initialized for driver powernow-k7
>  > cpufreq-core: unregistering CPU 0
>  > "
>
> powernow-k7 doesn't support SMP.
> The ubuntu folks tried to make single CPUs work with a SMP kernel,
> but it still didn't work out aparently.  The only K7's with powernow
> aren't SMP capable anyway iirc.

ATM, theres a work around for that. -386 kernels don't have smp enabled, and 
powernow-k7 works fine for them. So if you're using Ubuntu, and absolutely 
need powernow-k7 to work, don't use the -k7 kernel, use the -386 kernel.

https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/26713

-- 
Patrick "Diablo-D3" McFarland || diablod3@gmail.com
"Computer games don't affect kids; I mean if Pac-Man affected us as kids,
we'd all be running around in darkened rooms, munching magic pills and
listening to repetitive electronic music." -- Kristian Wilson, Nintendo,
Inc, 1989


      reply	other threads:[~2006-01-22 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 16:57 2.6.16-rc1-g3ee68c4: powernow-k7: -ENODEV Thomas Meyer
2006-01-22  5:19 ` Dave Jones
2006-01-22 23:12   ` Patrick McFarland [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=200601221812.30580.diablod3@gmail.com \
    --to=diablod3@gmail.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.mey@web.de \
    /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;
as well as URLs for NNTP newsgroup(s).