UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I recently upgraded to Kubuntu Gutsy from Feisty and CPU scaling no longer works. I have a Pentium M 1.60 gHz processor on a Dell 9300 laptop and it's currently stuck at 800 mHz at all times. Speedstep is enabled in the BIOS and I've tried manually editing the scaling files, following numerous CPU scaling HOWTOS, loading/unloading modules by hand, and cpufrequtils... nada. The min and max freq are the same, no matter what I do.
This seems to be an often posted problem, but I've yet to find anything that works to solve it. I know this is a known bug in the Gutsy kernel, but has anyone found a workaround? Some people ound a temporary solution which only works until the next reboot, but even I haven't had that much success.
Will rolling back to an older kernel fix this until a solution is found, or just muck me up further?
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to email@example.com, please.
analyzing CPU 0:
CPUs which need to switch frequency at the same time: 0
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
# /etc/modules: kernel modules to load at boot time.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
NOTE: Never needed anything after i8k in Feisty, but I added those just in case.
I'm running Gutsy 2.6.22-14 kernel. This works for me (at least temporarily) - it won't normally let me write to anything in the /sys/devices/system/cpu/cpu0/cpufreq path unless I'm *actually* root, not just 'sudo'. I have a 2GHz T7300 Centrino Duo, which 'ondemand' likes to run at 800MHz most of the time!