From: Niels Borne <niels.borne@laposte.net>
To: cpufreq@lists.linux.org.uk
Subject: hardware limits
Date: Sun, 28 May 2006 09:37:11 +0200 [thread overview]
Message-ID: <44795327.5000809@laposte.net> (raw)
Hi there,
I am working on a vaio laptop pcg-fr415b, using fc5 (see result of cat
/proc/cpuinfo above).
Since it is quite noisy I allowed cpuspeed at startup and this improved
the situation a little bit.
Still cpufreq-info (see details above -in french, but you can guess) gives
hardware limits : 2.10 GHz - 2.80 GHz
Is there any hope to go below 2.10 GHz and if yes, how ?
Thanks,
Niels
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Celeron(R) CPU 2.80GHz
stepping : 9
cpu MHz : 2100.000
cache size : 128 KB
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 mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips : 5589.50
cpufreq-info
cpufrequtils 0.4: cpufreq-info (C) Dominik Brodowski 2004
Veuillez rapportez les erreurs et les bogues à linux@brodo.de, s'il vous
plait.
analyse du CPU 0 :
pilote : p4-clockmod
CPUs qui doivent changer de fréquences en même temps : 0
limitation matérielle : 2.10 GHz - 2.80 GHz
plage de fréquence : 2.10 GHz, 2.45 GHz, 2.80 GHz
régulateurs disponibles : userspace, performance
tactique actuelle : la fréquence doit être comprise entre 2.10 GHz et
2.80 GHz.
Le régulateur "userspace" est libre de choisir la vitesse
dans cette plage de fréquences.
la fréquence actuelle de ce CPU est 2.10 GHz.
next reply other threads:[~2006-05-28 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 7:37 Niels Borne [this message]
2006-05-29 14:47 ` hardware limits Dominik Brodowski
2006-06-03 14:47 ` Niels Borne
2006-06-04 17:15 ` Dominik Brodowski
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=44795327.5000809@laposte.net \
--to=niels.borne@laposte.net \
--cc=cpufreq@lists.linux.org.uk \
/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.