SuSE 10.1 Intel Centrino M only uses about 1/2 of processor.
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well doesn't it matter if it runs below 600mhz? If it saves power, and performs without any lag, then it would make sense that it's less than 600.
It matters hugely that it runs at only 600MHZ. If I wanted 600MHZ, I would buy 600MHZ. If I am running on AC, I would like it if my computer ran at 1600MHZ, it would also help my performance of Video and VMWare greatly
Yeah, I think it's kernel compile time. I'm pretty sure that setting cpufreq to userspace in the kernel will allow you to be able to modprobe speedstep_centrino.
Yeah, I think it's kernel compile time. I'm pretty sure that setting cpufreq to userspace in the kernel will allow you to be able to modprobe speedstep_centrino.
I had an extra HDD that I installed SuSE 10.1 on (first tried FC4, and FC5 to verify both have the problem) and compiled the kernel without a bunch of the other modules in it, but now I am going to try with userspace as default gov.
For some reason I can't compile kernels on this computer, gives me a QT error (stupid.. QT is installed Doh!).
Mine as I posted runs perfectly - however I've switched ACPI off as it seems to get it's knickers in a twist -- my external mouse(usb) and network cards stop working.
With ACPI=OFF everything runs fine --of course when I shut down the system I have to switch the computer off manually at the end of the shutdown --but that's a very small inconvenience for a working system.
Mine as I posted runs perfectly - however I've switched ACPI off as it seems to get it's knickers in a twist -- my external mouse(usb) and network cards stop working.
With ACPI=OFF everything runs fine --of course when I shut down the system I have to switch the computer off manually at the end of the shutdown --but that's a very small inconvenience for a working system.
Cheers
-K
I have booted with acpi=off with the same results posted.
What kernel version are you running? Can you send me a copy of your lsmod, dmesg, speedstep_centrino.c and acpi_cpufreq.c
I want to compare them, and see if there is something different with some of the files, thanks.
After installing SUSE 10.1 a week ago, I discovered that I have the same problem;
the CPU never runs at any speeds higher than the lowest possible, 600KHz.
scaling_max_freq is equal to scaling_min_freq, at 600000, even though
cpuinfo_max_freq is 2000000. And whenever I do an
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
or
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
(under userspace governor), the change is overwritten or never picked up,
at least I am unable to change it.
I never had this problem with for example SUSE 10.0, and there is no settings in BIOS
to set specific frequencies, just to disable speedstep (which would leave the cpu
running at lowest speed, according to the BIOS info, so I haven't tried that). Admittedly,
I have the orignal A00 version of this BIOS.
I saw it was mentioned that there'd been a bug reported to Novell for this, but I
didn't see it in their bug system; has it been reported as a bug?
My system:
Dell Inspiron 9200
SUSE 10.1 2.6.16.21-0.13-default
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 2.00GHz
stepping : 6
cpu MHz : 600.000
cache size : 2048 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 mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe est tm2
bogomips : 1197.77
Distribution: Debian (ppc and x86) with Gnome CVS HEAD
Posts: 6
Rep:
If scaling_max_freq == scaling_min_freq, changing the governor will have no effect on the frequency. This is a problem with ACPI, where the (if my memory serves me right) _PPC gives an incorrect value for the maximum frequency in certain situations (I suspect it may be a race problem), and cpufreq becomes locked in this situation forever. It was fixed, I believe, by a patch that was included in the vanilla 2.6.17rc2. There is more information about it on the Ubuntu bug report about the issue, on launchpad. My attempts to backport the patch did not resolve the issue, unfortunately. If you are able, and are not already running it, upgrade your kernel to 2.6.17 or above, and see if this fixes the problem.
You can also try the other suggestion given there, about max_cstate. I haven't tried it myself.
Edit: I just noticed that you appear to be running 2.6.16. This is nearly certainly your problem, and 2.6.17 should nearly certainly fix the problem.
If scaling_max_freq == scaling_min_freq, changing the governor will have no effect on the frequency. This is a problem with ACPI, where the (if my memory serves me right) _PPC gives an incorrect value for the maximum frequency in certain situations (I suspect it may be a race problem), and cpufreq becomes locked in this situation forever. It was fixed, I believe, by a patch that was included in the vanilla 2.6.17rc2. There is more information about it on the Ubuntu bug report about the issue, on launchpad. My attempts to backport the patch did not resolve the issue, unfortunately. If you are able, and are not already running it, upgrade your kernel to 2.6.17 or above, and see if this fixes the problem.
You can also try the other suggestion given there, about max_cstate. I haven't tried it myself.
Edit: I just noticed that you appear to be running 2.6.16. This is nearly certainly your problem, and 2.6.17 should nearly certainly fix the problem.
I was able to get it running under 2.6.16 , I am sure when he posts results of commands above it'll show that CPUFREQ isn't running.
I've tried using cpufreq-set as well, both setting the performance governor -
which did update the corresponding scaling_governor /sys/devices-entry (I don't have the laptop
available right now, so I don't remember the exact name), but that of course doesn't help
since max-freq is fixed at 600000 - and by trying, with userspace governor running, to set
it explicitly with cpufreq-set -f 2000000.
By the way, I checked with modprobe to make sure the relevant (speedstep/centrino userspace/performance) modules were available, as well.
It never runs on more than this 600MHz, no matter how much I push it. And in addition yo this, my Kpowersave allways says that I'm running on batteries. Really don't know what to do.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.