Hi, I see what you mean - I've just run both versions to compare what's displayed. Even looking at the html output it doesn't show the commands that are needed to optimise.
Tim On 15 February 2011 13:32, Keean Schupke <[email protected]> wrote: > Hi, > > That is what I currently do, but powertop-2.0 does not seem to give the > suggestions any more. > > Cheers, > Keean. > > > On 15 February 2011 12:16, Tim Barnett <[email protected]> wrote: > >> Would taking the suggested commands from PowerTop and adding them to your >> /etc/rc.local script be a good solution for you? >> This would save profiling your computer each time as the commands would be >> run immediately without running PowerTop. If you find a suggestion that >> doesn't work well with your computer then you wouldn't include it in >> /etc/rc.local >> >> A power saving feature that can be annoying is to set the audio module to >> powersave, as it makes an annoying "click" just before a sound is played; >> however this might be acceptable when running on battery. >> >> Therefore perhaps a better solution would be to have an interface with >> suggestions for saving power that has the options: >> Use/Try now >> Use always >> Use when on battery >> >> *Use Always* and *Use when on battery* would be scripted so that they >> happen automatically without PowerTop being run. >> >> On 15 February 2011 12:58, Keean Schupke <[email protected]> wrote: >> >>> >>> How about allowing adding an option to dump the current settings >>> (good/bad) to a JSON file. There could be another option to read in the >>> settings from a JSON file, and an option that makes it apply the settings >>> and quit. >>> >>> We could then do: >>> >>> powertop --write-tunables=tunables.txt --exit-immediately >>> >>> edit the file to make change the good/bad settings then: >>> >>> powertop --read-tunables=tunables.txt --exit-immediately >>> >>> >>> Cheers, >>> Keean. >>> >>> >>> >>> On 14 February 2011 23:23, Auke Kok <[email protected]> wrote: >>> >>>> On 02/08/11 03:59, Keean Schupke wrote: >>>> >>>>> Would it be possible to add a switch to the command line, that would >>>>> make powertop start, switch every possible tunable to "Good" and then quit >>>>> again? >>>>> >>>>> It would be really cool to include this in my boot scripts to make sure >>>>> all powersaving features are enabled. >>>>> >>>>> It would also allow people to automatically benefit from new >>>>> recommendations added in future versions of powertop? >>>>> >>>> >>>> This has been suggested with the 1.x version before, and, we're really >>>> reluctant to implement this. >>>> >>>> It's simple enough to break someone's machine with this ("oops, we just >>>> turned off your keyboard and mouse"), and, you don't want to do this with >>>> some fallback code etc. ("did this fail the last time? skip that step from >>>> now on then"). >>>> >>>> That just makes this too complicated to safely do, especially at >>>> startup. Which is why we don't. >>>> >>>> Powertop is a diagnostics tool. The tool should be used by your >>>> distribution to figure out default-good-out-of-the-box settings and include >>>> those in your distribution by default. That's really where you need to go >>>> and ask in the first place to tweak the knobs at boot time. >>>> >>>> Auke >>>> >>>> >>> >>> _______________________________________________ >>> Discuss mailing list >>> [email protected] >>> http://lists.lesswatts.org/listinfo/discuss >>> >>> >> >> >> -- >> The thing I hate about an argument is that it always interrupts a >> discussion. >> - G. K. Chesterton >> >> It is impossible to defeat an ignorant man in argument. >> - William G. McAdoo >> > > -- The thing I hate about an argument is that it always interrupts a discussion. - G. K. Chesterton It is impossible to defeat an ignorant man in argument. - William G. McAdoo
_______________________________________________ Discuss mailing list [email protected] http://lists.lesswatts.org/listinfo/discuss
