3.7 kernel upgrade and frequency driver issues

MutantJohn · 2013-01-21 22:32:25

Hello Arch Community,

Today I upgraded kernels and now I can't get a couple of things to work properly. Namely upon booting my frequency drivers fail to load and I have to modprobe them manually.

So I used https://wiki.archlinux.org/index.php/CP … _governors to help me out.

I have all my modules in /lib/modules/$(uname -r)/kernel/drivers/cpufreq/ and even though the page says "echo <module> >/etc/modules-load.d/<module>" works for booting, it doesn't for me.

I have an AMD Phenom II x4 955 Black Edition processor so I should be using powernow but it doesn't load, only the acpi-cpufreq will so I tried putting it in my modules-load.d but it doesn't do anything.

But once I do "sudo modprobe acpi-cpufreq", my ondemand governor begins working perfectly and I have the .8 - 3.2 GHz frequency spectrum.

So if what the Arch page said doesn't work then I basically need these commands to be run as root at boot:

cd /lib/modules/$(uname -r)/kernel/drivers/cpufreq/
modprobe acpi-cpufreq

So is there a way to write a script that will do that?

Lone_Wolf · 2013-01-21 23:40:05

you're not the only one with that problem : https://bugs.archlinux.org/task/33088 .

Note : the cd command is not needed, modprobe has it's own search path.

try creating /etc/modules-load.d/module.conf , that does work for me. (2 or 3 times a month i boot with systemd just to check if that boot option still works)

smudge · 2013-01-22 03:30:03

A bit more to read here: https://mailman.archlinux.org/pipermail … 32632.html

digirium · 2013-01-22 03:31:30

Same thing happened here after the 3.7.3 kernel upgrade AMD Phenom II X4 965 stopped scaling and was stuck @ 3415.394 MHz. Average temperature at idle climbed from 32.5°C to between 38-40°C. After inserting module acpi_cpufreq the CPU stepped between 800 - 3400 MHz and temperature was normal again.

Nepherte · 2013-01-22 19:16:19

It is now handled by acpi-cpufreq according to https://git.kernel.org/?p=linux/kernel/ … a262834ed1. You should not load powernow-k8 any more. Note that if you use cpupower, the native module should be loaded automatically (and it was the case over here with a phenom II).

MutantJohn · 2013-01-22 21:10:59

Well, I'm glad I'm not the only with issues and I'm also glad it's an officially recognized thing so there should be a fix coming pretty soon for this then, I'm assuming.

Nepherte · 2013-01-23 00:32:34

There's not going to be a fix as it it's not an issue. It's intentional (cfr. commit message). Just use acpi-freq instead of powernow-k8.

Lone_Wolf · 2013-01-23 11:38:15

Nepherte wrote:

There's not going to be a fix as it it's not an issue. It's intentional (cfr. commit message). Just use acpi-freq instead of powernow-k8.

Looks like you may have misunderstood what the issue is.

The switch from powernow-k8 module to acpi-cpufreq is NOT the issue, but the fact this broke autoloading for many processors.

Nepherte · 2013-01-23 19:31:59

Lone_Wolf wrote:

Nepherte wrote:
There's not going to be a fix as it it's not an issue. It's intentional (cfr. commit message). Just use acpi-freq instead of powernow-k8.
Looks like you may have misunderstood what the issue is.
The switch from powernow-k8 module to acpi-cpufreq is NOT the issue, but the fact this broke autoloading for many processors.

My bad. If putting it inside /etc/modules-load.d/ doesn't work, how about modprobing the module by putting it inside /etc/modprobe.d/<file>.conf

talleres · 2013-01-26 05:18:38

For the module to load automatically, simply create a file called "acpi-cpufreq.conf" in the directory "/etc/modules-load.d/" containing the name of the module itself "acpi-cpufreq" and that worked for me have scaled back on my Phenom X4 950.

MutantJohn · 2013-01-26 17:20:42

talleres, your suggest worked perfectly. Thank you for explaining it simply for a Linux newb.

PhotonX · 2013-01-27 11:25:20

I've run into the same problem, but the solution doesn't work:

$ cat /etc/modules-load.d/acpi_cpufreq 
acpi_cpufreq
$ lsmod |grep acpi
$

Manually modprobing acpi_cpufreq works fine.

msthev · 2013-01-27 11:53:27

PhotonX wrote:

the solution doesn't work

PhotonX wrote:

$ cat /etc/modules-load.d/acpi_cpufreq

talleres wrote:

create a file called "acpi-cpufreq.conf"

And of course:

$ man modules-load.d

Edit:
I didn't realize the Wiki was wrong. Sorry for too much RTFM-y tone of my post.

Last edited by msthev (2013-01-27 13:01:45)

PhotonX · 2013-01-27 12:47:11

Thanks, that was the mistake. As far as I know, earlier the filename didn't matter, something seems to be changed now.

edit: I corrected the cpupower Wiki page accordingly.

Last edited by PhotonX (2013-01-27 12:51:09)

Arch Linux

#1 2013-01-21 22:32:25

3.7 kernel upgrade and frequency driver issues

#2 2013-01-21 23:40:05

Re: 3.7 kernel upgrade and frequency driver issues

#3 2013-01-22 03:30:03

Re: 3.7 kernel upgrade and frequency driver issues

#4 2013-01-22 03:31:30

Re: 3.7 kernel upgrade and frequency driver issues

#5 2013-01-22 19:16:19

Re: 3.7 kernel upgrade and frequency driver issues

#6 2013-01-22 21:10:59

Re: 3.7 kernel upgrade and frequency driver issues

#7 2013-01-23 00:32:34

Re: 3.7 kernel upgrade and frequency driver issues

#8 2013-01-23 11:38:15

Re: 3.7 kernel upgrade and frequency driver issues

#9 2013-01-23 19:31:59

Re: 3.7 kernel upgrade and frequency driver issues

#10 2013-01-26 05:18:38

Re: 3.7 kernel upgrade and frequency driver issues

#11 2013-01-26 17:20:42

Re: 3.7 kernel upgrade and frequency driver issues

#12 2013-01-27 11:25:20

Re: 3.7 kernel upgrade and frequency driver issues

#13 2013-01-27 11:53:27

Re: 3.7 kernel upgrade and frequency driver issues

#14 2013-01-27 12:47:11

Re: 3.7 kernel upgrade and frequency driver issues

Board footer