Bug 8898 - fedora-loadmodules.service fails because of powernow-k8
Summary: fedora-loadmodules.service fails because of powernow-k8
Status: RESOLVED DUPLICATE of bug 8621
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-30 07:35 CET by Simon Putt
Modified: 2013-02-01 01:24 CET (History)
3 users (show)

See Also:
Source RPM: drakxtools
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Simon Putt 2013-01-30 07:35:57 CET 
This service is failing because it is trying to insert the powernow-k8 module on AMD K10 systems

This is failing because these chips are now using the acpi-cpufreq module for cpu frequency scaling (for power saving) now as can be seen here

the only chips now using this module are the original AMD K8 (socket 754/939 Athlons/Opterons) 

For example on my Phenom II system

[    6.042931] powernow-k8: this CPU is not supported anymore, using acpi-cpufreq instead.
[    6.044785] acpi-cpufreq: overriding BIOS provided _PSD data

this can be fixed by replacing powernow-k8 with acpi-cpufreq in the following file

/etc/modprobe.preload.d/cpufreq
Comment 1 Simon Putt 2013-01-30 07:45:58 CET 
error message

Jan 27 06:22:51 electronicbox fedora-loadmodules[490]: Loading modules: snd-hrtimer xpad evdev powernow-k8 cpufreq_powersave cpufreq_conservative cpufreq_ondemand cuse
Jan 27 06:22:51 electronicbox fedora-loadmodules[490]: modprobe: ERROR: could not insert 'powernow_k8': No such device
Sander Lepik 2013-01-30 09:08:56 CET

Priority: Normal => release_blocker
CC: (none) => sander.lepik, tmb
Component: Release (media or process) => RPM Packages
Hardware: i586 => All
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakxtools

Comment 2 Manuel Hiebel 2013-02-01 01:24:35 CET 
(drakxtools ? )

*** This bug has been marked as a duplicate of bug 8621 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.