First thing, the mere length of this discussion for such a simple (and well described!) issue is dismaying. What's going on here? I guess it is just too easy to add an opinion...
Now, how come "powernowd" init script tries to run "ondemand" INSTEAD of "powernowd"? THIS IS THE ISSUE. I don't really want powernowd, I DON'T moinstall it in the first place... Excuse the capitals, but I thought this discussion needs some clarity. We just need to fix powernowd init script by removing every reference to "ondemand", actually to every other scaling governor which powernowd does NOT use. Let some ondemand lover go and write an ondemand package, instead of messing this one. In other words, we want an init script that does this: 1.- Load "userspace" governor if necessary, as it is the one REQUIRED by powernowd (just read the README). 2.- Run "powernowd" daemon. It can't be as complicated as the current script appears. I mean the current two-script system... Who was the genious around? Now this is the script as I think it should be: simple and direct. And working! Regards, gatopeich.- ** Attachment added: "/etc/init.d/powernowd as it should be" http://launchpadlibrarian.net/16210339/powernowd -- [hardy] Regression: powernowd no longer works with some chipsets https://bugs.launchpad.net/bugs/223812 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
