All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Kevan <ben.kevan@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk, linux@brodo.de
Subject: Re: 2.6.16.x CPUFREQ / SpeedStep-Centrino: couldn't enable Enchanced SpeedStep
Date: Mon, 19 Jun 2006 18:07:13 -0700	[thread overview]
Message-ID: <200606191807.14091.ben.kevan@gmail.com> (raw)
In-Reply-To: <20060619231323.GC17134@redhat.com>

Hi Dave, 

Thanks for the awesome speed reply. I have not yet tried with 2.6.17, I will 
have to find the SuSE Kernel Patches to see if I can install vanilla kernel 
then SuSE patch it, and log on. 

You wouldn't happen to know where they are located off the top of your head 
would you? If not, no worries, I can find them. Is there a known broken 
cpufreq issue in 2.6.16.x ? that would possibly cause this speedstep issue? 

I'll try to get back to you tomorrow with the results of 2.6.17 if I can 
figure out how to install the Vanilla Kernel into SuSE10.1

Ben

On Monday 19 June 2006 16:13, Dave Jones wrote:
> On Mon, Jun 19, 2006 at 04:10:40PM -0700, Ben Kevan wrote:
>  > Hi,
>  >
>  > I copied both on this because I thought you both may be interested. My
>  > problem is, my Toshiba Tecra M1 will only run at 598Mhz, and I can not
>  > use toshutils or anything else to configure speedstep to run higher. Or
>  > in any other way can I use it to run higher.
>  >
>  > Below are a bunch of commands to give you an idea of what's going on. Is
>  > this a bug with the 2.6.16.x build? Or is it something else that I am
>  > just oblivious too (ACPI?).
>  >
>  > Any information would be greatly appreciated.
>  >
>  > LSHESU01004839:/home/bkevan # dmesg | grep speedstep
>  > speedstep-centrino: couldn't enable Enhanced SpeedStep
>  > speedstep-centrino: couldn't enable Enhanced SpeedStep
>  > speedstep-centrino: couldn't enable Enhanced SpeedStep
>  > speedstep-centrino: couldn't enable Enhanced SpeedStep
>  >
>  > LSHESU01004839:/home/bkevan # modprobe speedstep_centrino
>  > FATAL: Error inserting speedstep_centrino
>  > (/lib/modules/2.6.16.13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/sp
>  >eedstep-centrino.ko): No such device
>  > LSHESU01004839:/home/bkevan # modprobe acpi_cpufreq
>  > FATAL: Error inserting acpi_cpufreq
>  > (/lib/modules/2.6.16.13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/ac
>  >pi-cpufreq.ko): No such device
>
> Does this still happen in 2.6.17 ?
> If so, can you boot with cpufreq.debug=7 and post the output of dmesg here
> ?
>
> Thanks,
>
> 		Dave

  reply	other threads:[~2006-06-20  1:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 23:10 2.6.16.x CPUFREQ / SpeedStep-Centrino: couldn't enable Enchanced SpeedStep Ben Kevan
2006-06-19 23:13 ` Dave Jones
2006-06-20  1:07   ` Ben Kevan [this message]
2006-06-20  5:24     ` Ben Kevan
2006-06-20  5:33       ` Dave Jones
2006-06-20  9:43 ` Bruno Ducrot
2006-06-20 10:16   ` Bruno Ducrot
2006-06-20 18:07   ` Jeremy Fitzhardinge
2006-06-20 20:32     ` Ben Kevan
2006-06-20 20:37       ` Jeremy Fitzhardinge
2006-06-20 21:09         ` Ben Kevan
2006-06-22 17:59       ` Dominik Brodowski
2006-06-24 18:03         ` Ben Kevan
2006-06-21 10:01     ` Bruno Ducrot

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=200606191807.14091.ben.kevan@gmail.com \
    --to=ben.kevan@gmail.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux@brodo.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 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.