public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: dual_bereta_r0x <dual_bereta_r0x@arenanetwork.com.br>
To: linux-kernel@vger.kernel.org
Subject: 2.6.2: P4 ClockMod speed
Date: Mon, 16 Feb 2004 16:23:15 -0300	[thread overview]
Message-ID: <403118A3.6010300@arenanetwork.com.br> (raw)

Hello all.

I have a P4 2.4 running @ 3.12GHz. In 2.6.0, i could change it frequency 
via speedfreqd(8) up to its actual speed. Since 2.6.1, its max speed is 
locked on cpu *real* speed.

Is there anything to do so i can reuse old fashioned way?

Please c/c me as i'm not on list.

TIA.

hquest@phoenix:/proc$ more cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 2.40GHz
stepping        : 9
cpu MHz         : 3124.376
cache size      : 512 KB
physical id     : 0
siblings        : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 6176.76

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 2.40GHz
stepping        : 9
cpu MHz         : 3124.376
cache size      : 512 KB
physical id     : 0
siblings        : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 6242.30

hquest@phoenix:/proc$ speedfreq
Current policy is performance
hquest@phoenix:/proc$ speedfreq -c
CPU speed: min 300MHz, max 2400MHZ, current 2400MHz; 0.00% idle
hquest@phoenix:/proc$ cd /sys/devices/system/cpu/cpu0/cpufreq
hquest@phoenix:/sys/devices/system/cpu/cpu0/cpufreq$ more *
::::::::::::::
cpuinfo_max_freq
::::::::::::::
2400000
::::::::::::::
cpuinfo_min_freq
::::::::::::::
300000
::::::::::::::
scaling_available_frequencies
::::::::::::::
300000 600000 900000 1200000 1500000 1800000 2100000 2400000
::::::::::::::
scaling_available_governors
::::::::::::::
userspace performance
::::::::::::::
scaling_driver
::::::::::::::
p4-clockmod
::::::::::::::
scaling_governor
::::::::::::::
performance
::::::::::::::
scaling_max_freq
::::::::::::::
2400000
::::::::::::::
scaling_min_freq
::::::::::::::
300000
hquest@phoenix:/sys/devices/system/cpu/cpu0/cpufreq$ _

-- 
dual_bereta_r0x -- Alexandre Hautequest
ArenaNetwork Lan House & Cyber -- www.arenanetwork.com.br

             reply	other threads:[~2004-02-16 19:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 19:23 dual_bereta_r0x [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-16 21:34 2.6.2: P4 ClockMod speed Dominik Brodowski
2004-02-16 21:48 ` dual_bereta_r0x
2004-02-16 21:57   ` Bruno Ducrot
2004-02-17  9:09   ` Dominik Brodowski
2004-02-26  1:28     ` dual_bereta_r0x
2004-03-03 19:12       ` Bruno Ducrot
2004-02-25 17:43 ` Pavel Machek

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=403118A3.6010300@arenanetwork.com.br \
    --to=dual_bereta_r0x@arenanetwork.com.br \
    --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