Description of problem: powernow-k8 module is not loaded automatically after kernel is updated to 3.11. Version-Release number of selected component (if applicable): kernel-3.11.4-101.fc18.x86_64 systemd-201-2.fc18.8.x86_64 How reproducible: Steps to Reproduce: 1. update kernel to 3.11 2. reboot Actual results: powernow-k8 is not loaded automatically, and cpufreq is disabled. Expected results: powernow-k8 is auto-loaded and cpufreq is enabled. Additional info: This bug is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1004456 By creating /etc/udev/rules.d/80-drivers-cpufreq.rules with the following single line, ------------ ENV{MODALIAS}=="?*", RUN{builtin}="kmod load $env{MODALIAS}" ------------ the module powernow-k8 is automatically loaded after system reboot. Please pick up http://cgit.freedesktop.org/systemd/systemd/commit?id=bf7f800f2b3e93ccd1229d4717166f3a4d3af72f to systemd for fedora 18.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This should be fixed by the last (or previous) update.
Yes. Thank you!