Comment 10 for bug 606706

Yes, I noticed the different output too and could reproduce the behaviour.

If I unplug the power cord after a fresh boot, wait until all pm-utils scripts are run and plug the cord in again, then I get the output as in comment 2 (scripts are run as being on battery). But if I quickly unplug and plug the power cord while the pm-utils scripts are still called, then it the scripts are run as in comment 8 - as long as I do the quickly unplugging and plugging.

But beside this problem of running the scripts with proper arguments when being on main power again, the wrong initial values are set on boot time already - on both computers I've tested it with (laptop and desktop).

*) On the laptop (a Dell Latitude D620 with a PATA harddrive), the initial APM_level (hdparm -B) is set to 1 - which is obviously too aggressive.

*) On the desktop computer (HP Pavilion with two SATA harddrives), there is no APM_level set (as it is not supported on these devices), but the write cache is disabled and the option "Device-initiated interface power management" is not set. The harddrives will spin down within some minutes as soon as the system is idle. Running the /usr/lib/pm-utils/power.d/harddrive hook manually, the write cache and "Device-initiated interface power management" are set again.