cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: cpufreq@lists.linux.org.uk, muskatnuss@gmx.at
Subject: RE: Amd Turion TL-52 X2 on Amilo PA 1510> No way to change Frequency!
Date: Wed, 30 May 2007 09:15:40 +0200	[thread overview]
Message-ID: <1180509340.16396.210.camel@queen.suse.de> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDF02076E15@SAUSEXMB1.amd.com>

On Tue, 2007-05-29 at 14:42 -0500, Langsdorf, Mark wrote:
> > my cpufreq directory says:
> > 
> > cpuinfo_max_freq
> > 1600000

> > scaling_max_freq
> > 800000
> > 
> > so but i've already tried to change the scaling_max_freq to 
> > 1600000 but nothing happens @ su mode.
> > if i add an line with 
> > echo 1600000 > /sys/devices...../cpufreq/scaling_max_freq
> > at booting before entering init 1 modus ... nothing happens 
> > or it says directory or file not found.
Have you tried manually at some later stage, e.g. in init 3.
You may want to use:
cat /dev/zero >/dev/null
to set the processor under load and check:
scaling_cur_freq or /proc/cpuinfo for freq changes.
> > 
> > so im not able to change this file. 
> 
> I'm not even sure how the scaling_max and the cpuinfo_max
> can be different values.  Anyone else have any ideas?
This is when the frequency got limited. AFAIK for x86 there are only two
possibilities:
  - thermal (check "watch -n1 
    cat /proc/acpi/thermal_zone/*/{trip_points,temperature}")
    If the passive cooling trip point got exceeded passive cooling
    gets enabled (also stated in /proc/acpi/thermal_zone/*/state)
  - _PPC BIOS freq limitation
    Some BIOSes limit freq e.g. when working on battery.
    In some BIOSes this is configurable (-> check BIOS)
    There was a bug, that if booted with limited freq (e.g. on some
    BIOSes when booted on battery), you will never be able to reach
    max_freq again. This has been fixed in 2.6.22-rc1 or -rc2.

    If it's _PPC it could also be some other general ACPI breakage.

> By the way, what governor are you using?

Best is you try with ondemand governor, like that you can't forget
anything to set up in userspace.


   Thomas

  reply	other threads:[~2007-05-30  7:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 19:12 Amd Turion TL-52 X2 on Amilo PA 1510> No way to change Frequency! Muskat Nuss
2007-05-29 17:51 ` Langsdorf, Mark
2007-05-29 19:15   ` Muskat Nuss
2007-05-29 19:42     ` Langsdorf, Mark
2007-05-30  7:15       ` Thomas Renninger [this message]
2007-05-30 16:42         ` Muskat Nuss
2007-05-30 17:05           ` Thomas Renninger
  -- strict thread matches above, loose matches on Subject: below --
2007-05-29 22:48 Muskat Nuss
2007-05-25 20:41 Muskat Nuss
2007-05-25 20:22 Muskat Nuss
2007-05-25  5:09 Patrick Oberdorfer
2007-05-25 15:19 ` Langsdorf, Mark
2007-05-24 22:14 Muskat Nuss

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=1180509340.16396.210.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=mark.langsdorf@amd.com \
    --cc=muskatnuss@gmx.at \
    /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