ROSA Forum

Hi,

Like with many others distribution, I needs to have the frequency scaling working for my CPU

With ROSA 2012 LTS, the frequency scaling isn't enabled, what should I do to make it work ?

[root@rosa2012lts ~]# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Veuillez rapportez les erreurs et les bogues à cpufreq@vger.kernel.org, s'il vous plait.
analyse du CPU 0 :
pas de pilotes cpufreq reconnu pour ce CPU
maximum transition latency: 4294.55 ms.
analyse du CPU 1 :
pas de pilotes cpufreq reconnu pour ce CPU
maximum transition latency: 4294.55 ms.
analyse du CPU 2 :
pas de pilotes cpufreq reconnu pour ce CPU
maximum transition latency: 4294.55 ms.

[root@rosa2012lts ~]# inxi -F
System: Host: rosa2012lts Kernel: 3.0.28-nrj-desktop-2rosa.lts x86_64 (64 bit) Desktop: N/A Distro: ROSALinux 2012 turtle
Machine: Mobo: ASRock model: N68C-S UCC Bios: American Megatrends version: P1.60 date: 09/19/2011
CPU: Triple core AMD Athlon II X3 460 (-MCP-) cache: 1536 KB flags: (lm nx sse sse2 sse3 sse4a svm)
Clock Speeds: 1: 3415.215 MHz 2: 3415.215 MHz 3: 3415.215 MHz
Graphics: Card: nVidia G94 [GeForce 9600 GT] X.org: 1.10.3 drivers: v4l,nvidia tty size: 156x55 Advanced Data: N/A for root
Audio: Card: nVidia MCP61 High Definition Audio driver: HDA Intel Sound: ALSA ver: 1.0.24
Network: Card: nVidia MCP61 Ethernet driver: forcedeth
IF: eth0 state: up speed: 100 Mbps duplex: full mac: bc:5f:f4:07:a7:84
Drives: HDD Total Size: 544.1GB (147.8% used) 1: id: /dev/sda model: KINGSTON_SV100S2 size: 64.0GB
2: id: /dev/sdb model: WDC_WD3200KS size: 320.1GB 3: id: /dev/sde model: 1600BEV_External size: 160.0GB
Partition: ID: / size: 12G used: 5.8G (53%) fs: ext4 ID: /home size: 20G used: 11G (56%) fs: ext4
ID: /home size: 20G used: 11G (56%) fs: ext4 ID: /home size: 20G used: 11G (56%) fs: ext4
ID: swap-1 size: 4.19GB used: 0.00GB (0%) fs: swap
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: System Temperatures: cpu: 41.1C mobo: N/A gpu: 44C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 220 Uptime: 3 min Memory: 1464.3/3964.0MB Client: Shell inxi: 1.8.11
[root@rosa2012lts ~]#

This bug in Bugzilla http://bugs.rosalinux.ru/show_bug.cgi?id=245

Yes !!!

I forgot that I had already reported this problem during my first tests with ROSA

Now ROSA LTS is the main distribution on my desktop but unfortunately, this problem is still here

it's an old pb.
amd athlon x2 64

with mandriva 2010.2 32 bit with kernel desktop 2.6.33.7 no pb. the profile list is powersave,ondemand,conservative,users,performance
but
if you use kernel server 2.6.33.7 because you have 6 GB ram then the profile is users,perfomance.

same pb with all mib kernels nrj pae desktop

same pb with mageia kernels

Currently, I use this workaround which works with my CPU~Triple core AMD Athlon II X3 460

Under root, I've created a script called script-frequence-cpu.sh Then I've added it in crontab system

to simply launch a driver (a module)

put a statement "powernow-k8"
in /etc/modprobe.preload file

the contents of my modeprobe.preload file for 2010.2
becareful the name powernow_k8 or powernow-k8 changes with mandriva version
*************************************************************************************
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules

powernow_k8
******************************************************************************************

yes the powernow_k8 not launched by default is a pb since 2010.2 !

Yes, I'm so in Bagzille and writing.
Iam tested in AMD k8-k9-k10 series processors. All OK in kernel-3.0.38.

philippe.roubach писал(а):to simply launch a driver (a module)
put a statement "powernow-k8"
in /etc/modprobe.preload file

Thank you Philippe, it works by this way and it's easier than my workaround with crontab