Bug 8621

Summary:	3_b1: modprobe: ERROR: could not insert 'powernow_k8'
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	alien, bittwister2, ennael1, lemonzest, mageia, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakxtools	CVE:
Status comment:

Description Bit Twister 2013-01-07 13:22:19 CET

Description of problem:

 modprobe: ERROR: could not insert 'powernow_k8': No such device

Version-Release number of selected component (if applicable):


How reproducible: Always

Steps to Reproduce:
Clean install of Mageia-3-beta1-x86_64-DVD.iso. Default runlevel: 3
Package Group Selection screen has all package groups selected except LSB
and Other Graphical Desktops. non-free and tainted media are enabled.
Followed with:
urpmi --downloader wget --auto --auto-update
urpme --auto-orphans and reboot. 
 
1. click up a terminal
2. su - root
3. journalctl -u fedora-loadmodules

Snippet of journal follows:
Logs begin at Mon, 2013-01-07 06:07:04 CST, end Mon, 2013-01-07 06:08:05 CST.
fedora-loadmodules Loading modules: evdev powernow-k8 cpufreq_powersave cpufreq_conservative cpufreq_ondemand
fedora-loadmodules modprobe: ERROR: could not insert 'powernow_k8': No such device
fedora-loadmodules Loading modules: evdev powernow-k8 cpufreq_powersave cpufreq_conservative cpufreq_ondemand
fedora-loadmodules modprobe: ERROR: could not insert 'powernow_k8': No such device

$ locate powernow-k8
/usr/lib/modules/3.7.1-desktop-1.mga3/kernel/drivers/cpufreq/powernow-k8.ko.xz

$ uname -r
3.7.1-desktop-1.mga3

Comment 1 Manuel Hiebel 2013-01-27 10:55:52 CET

seems to be valid: https://forums.mageia.org/en/viewtopic.php?f=15&t=4281&sid=a8befc89668b43051c6b7b237175e1f1

Assignee: bugsquad => tmb

Comment 2 Thomas Backlund 2013-01-27 11:21:08 CET

is acpi-cpufreq loaded ?

does it load ?

Comment 3 Thomas Backlund 2013-01-27 11:22:15 CET

(In reply to comment #2)

> does it load ?

meaning: 

modprobe acpi-cpufreq

and check dmesg output

Comment 4 Bit Twister 2013-01-27 12:13:34 CET

(In reply to comment #3)
> (In reply to comment #2)
> 
> > does it load ?
> 
> meaning: 
> 
> modprobe acpi-cpufreq
[root@wb ~]# modprobe acpi-cpufreq
[root@wb ~]# 


> and check dmesg output

Heheh, This is Mageia release 3, everything is in the journal.
I have a journalctl -fa running in an xterm.

journalctl showed no message when executed the command.

Comment 5 Manuel Hiebel 2013-02-01 01:24:35 CET

*** Bug 8898 has been marked as a duplicate of this bug. ***

CC: (none) => lemonzest

Comment 6 Sander Lepik 2013-02-01 10:11:44 CET

Please see bug #8898 for details, it seems that drakxtools is assigning wrong module in /etc/modprobe.preload.d/cpufreq.

Priority: Normal => release_blocker
CC: (none) => sander.lepik, tmb
Hardware: x86_64 => All
Assignee: tmb => thierry.vignaud
Source RPM: kernel-3.7.1-1.mga3.src.rpm => drakxtools

Comment 7 Anne Nicolas 2013-04-13 14:46:23 CEST

Thierry any proposal on this bug?

CC: (none) => ennael1

Comment 8 AL13N 2013-04-23 13:21:35 CEST

is this still valid after the udev/ldetect fixes in the installer?

CC: (none) => alien

Comment 9 Bit Twister 2013-04-23 15:00:38 CEST

(In reply to AL13N from comment #8)
> is this still valid after the udev/ldetect fixes in the installer?

Assuming you are talking to me, are those fixes already in the Mageia-3-RC-x86_64-DVD.iso?

Comment 10 Chris Denice 2013-04-23 15:11:41 CEST

Is that really a bug?

In my case, even though I got these messages, with powernow-k8 specified in /etc/modprobe.preload.d/cpufreq, the module acpi_cpufreq got automatically loaded instead and the cpufreq was working in ONDEMAND mode.

So, if drakxtools is fixed, the bug should be closed.

Cheers,
Chris.

Comment 11 AL13N 2013-04-23 16:40:18 CEST

@BitTwister: there have been changes that may (or may not) help after beta3 or beta4 release (i don't remember which).

@Chris: you may have a point.

Comment 12 Bit Twister 2013-04-23 22:11:44 CEST

(In reply to AL13N from comment #11)
> @BitTwister: there have been changes that may (or may not) help after beta3
> or beta4 release (i don't remember which).

Ok, back from a Mageia-3-RC-x86_64-DVD.iso clean install+updates/reboot of RC, problem still exists.

> @Chris: you may have a point.

I disagree with Chris. After a clean install+updates/reboot, there should be no problems from these commands
 grpck -r
 pwck -r
 symlinks -r / | grep dangling
 journalctl |  grep 'Failed to start'

The fedora-loadmodules problem should be corrected.

Manuel Hiebel 2013-05-28 22:30:55 CEST

Priority: release_blocker => Normal

Bit Twister 2014-01-18 16:40:20 CET

CC: (none) => junknospam

Comment 13 Bit Twister 2015-04-28 03:01:08 CEST

no error on 5 RC.

Status: NEW => RESOLVED
Resolution: (none) => FIXED