All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Sauthoff <g_sauthoff@web.de>
To: Dominik Brodowski <linux@brodo.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Pentium M and 2.4. kernel: does not work
Date: Mon, 18 Aug 2003 20:51:41 +0200	[thread overview]
Message-ID: <200308182051.41707.g_sauthoff@web.de> (raw)
In-Reply-To: <20030818175051.GA1570@brodo.de>

On Monday 18 August 2003 19:50, you wrote:

> Yes it did. Indeed no cpufreq driver got properly loaded -- a bug in
> speedstep-centrino prevented this. Can you try the attached version,
> please?

Sure, no problem:

# /proc/cpufreq
          minimum CPU frequency  -  maximum CPU frequency  -  policy
CPU  0       600000 kHz ( 46 %)  -    1300000 kHz (100 %)  -  performance
# echo -n "0%0%100%userspace" > /proc/cpufreq
# cat /proc/cpufreq
          minimum CPU frequency  -  maximum CPU frequency  -  policy
CPU  0       600000 kHz ( 46 %)  -    1300000 kHz (100 %)  -  userspace
# cat /proc/sys/cpu/0/speed
1300000
# cat /proc/sys/cpu/0/speed-min
600000
# cat /proc/sys/cpu/0/speed-min > /proc/sys/cpu/0/speed
# cat /proc/sys/cpu/0/speed
600000

So it seems to work now.

A 'speed rsa' in openssl is nearly perfectly about a factor of 2 slower in 
min-speed in comparison to max-speed. Like it should be! At max-speed the fan 
turns on and and min-speed not (while openssl ist testing).

Great.

Regards
Georg Sauthoff

      parent reply	other threads:[~2003-08-18 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 22:43 Pentium M and 2.4. kernel: does not work Georg Sauthoff
2003-08-15 21:30 ` Dominik Brodowski
2003-08-16  7:34   ` Jeremy Fitzhardinge
2003-08-16 18:54     ` Dominik Brodowski
2003-08-16  8:28   ` Georg Sauthoff
2003-08-16 18:53     ` Dominik Brodowski
2003-08-16 19:57       ` Georg Sauthoff
2003-08-17 21:09         ` Georg Sauthoff
     [not found]           ` <20030818175051.GA1570@brodo.de>
2003-08-18 18:51             ` Georg Sauthoff [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=200308182051.41707.g_sauthoff@web.de \
    --to=g_sauthoff@web.de \
    --cc=cpufreq@www.linux.org.uk \
    --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.