No that's not case. I have this is my /etc/rc.local file (not rclocal.d as I wrote earlier):
# Suggestion: Enable SATA ALPM link power management via: echo min_power > /sys/class/scsi_host/host0/link_power_management_policy # # Suggestion: increase the VM dirty writeback time from 5.00 to 15 seconds with: echo 1500 > /proc/sys/vm/dirty_writeback_centisecs And after bootup I can run cat /sys/class/scsi_host/host0/link_power_management_policy and it IS set to min_power. cat /proc/sys/vm/dirty_writeback_centisecs IS set to 1500, but as soon as I run Powertop from the same session it suggests these options and once chosen wakeups per second decreases dramatically (from red bar to mustard green). hal-disable-polling is a permanent setting that I do not have to keep setting after boot. --andrew On 19 March 2010 18:51, Auke Kok <[email protected]> wrote: > On 03/19/10 08:07, Andrew Henry wrote: > >> I got suggestions for enabling SATA link power management, writeback >> time and kill hal add-on storage when I run powertop, so I enabled >> all these suggestions at startup in /etc/rclocal.d, and upon reboot I >> can see that they have taken effect, but when I then run Powertop, it >> shows that wakeups per second are just as high as if I haden't set >> these options, and it pops up the same suggestions again. If I >> accept the suggestions when they popup by pressing W for writeback, S >> for sata link power mgmt and K for disable cdrom polling, then the >> wakeups per second drops dramatically. >> >> Why does this happen? Can Powertop not see that I already have these >> options set? >> > > It sees that they are not set, that's why it is (again) suggesting them. > From what you say, the settings are lost or not active (high amount of > wakeups) somewhere after boot? is perhaps sysctl unsetting some of these? > > Auke >
_______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
