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
seems to be valid: https://forums.mageia.org/en/viewtopic.php?f=15&t=4281&sid=a8befc89668b43051c6b7b237175e1f1
Assignee: bugsquad => tmb
is acpi-cpufreq loaded ? does it load ?
(In reply to comment #2) > does it load ? meaning: modprobe acpi-cpufreq and check dmesg output
(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.
*** Bug 8898 has been marked as a duplicate of this bug. ***
CC: (none) => lemonzest
Please see bug #8898 for details, it seems that drakxtools is assigning wrong module in /etc/modprobe.preload.d/cpufreq.
Priority: Normal => release_blockerCC: (none) => sander.lepik, tmbHardware: x86_64 => AllAssignee: tmb => thierry.vignaudSource RPM: kernel-3.7.1-1.mga3.src.rpm => drakxtools
Thierry any proposal on this bug?
CC: (none) => ennael1
is this still valid after the udev/ldetect fixes in the installer?
CC: (none) => alien
(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?
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.
@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.
(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.
Priority: release_blocker => Normal
CC: (none) => junknospam
no error on 5 RC.
Status: NEW => RESOLVEDResolution: (none) => FIXED